1 / 33

Troubleshooting Tools

Troubleshooting Tools. Kyle Broussard and Alexandra Mikolai. Hardware Tools. Broken Cables. Broken cables cause permanent disconnections, not slowdowns Types of broken cables Open circuit Short Wire map problem Crosstalk Noise Impedance mismatch. Cable Testers, TDRs, and OTDRs.

adelie
Download Presentation

Troubleshooting Tools

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Troubleshooting Tools Kyle Broussard and Alexandra Mikolai

  2. Hardware Tools

  3. Broken Cables • Broken cables cause permanent disconnections, not slowdowns • Types of broken cables • Open circuit • Short • Wire map problem • Crosstalk • Noise • Impedance mismatch

  4. Cable Testers, TDRs, and OTDRs • Cable testers tell you if there’s a continuity problem or if a wire map is incorrect • TDR and OTDR tell where the break in the cable is • TDR = time domain Reflectometers • OTDR = optical time domain reflectometers

  5. Cable Certifiers • Certifiers test cable to ensure it can handle its rated capacity • Should use when there is a slowdown or to eliminate cabling as the problem

  6. Voltage Event Recorder/ Temperature Monitor • Heat and power problems can manifest as intermittent problems • Use to monitor server rooms over time to detect and record issues with electricity and heat

  7. Protocol Analyzers • Monitor the different protocols running at different layers on the network • Helps to determine slowdowns on a network by giving an idea of excess or unexpected traffic

  8. Cable Strippers, Snips, and Crimpers • Used to make UTP cables

  9. Multimeters • Test voltage, resistance and continuity • Only tool to read amount of voltage on a line • Used also for continuity testing if cable tester is unavailable

  10. Tone Probes/Generators • Used together to help locate a particular cable

  11. Butt Sets • Used to test whether a particular phone line is working or not

  12. Punchdown Tools • Put UTP wires into 66- and 110-blocks. • Only used diagnostically to repunch a connection

  13. Software Tools

  14. Built-In Software

  15. The traceroute Command

  16. Trace all routers between two points • Diagnose where the problem lies when unable to reach remote system • Many routers block ICMP packets

  17. The mtr Command

  18. The ipconfig and ifconfig Commands

  19. The ping and arping Commands

  20. Ping • Uses ICMP packets to query by IP or name • Works across routers • Arping • Use if ping doesn’t work • Uses ARP frames instead of ICMP packets • ARP frames do not cross routers, can only be used within broadcast domains • UNIX based systems

  21. The nslookup/dig Commands

  22. The hostname Command

  23. The route Command

  24. The nbtstat Command

  25. Windows only program • Should always be ran with a switch • Most useful switch is –n which shows the local NetBIOS names • Useful way to see what systems are on your network

  26. The netstat Command

  27. Third-Party Software

  28. Packet Sniffer

  29. Also called protocol analyzers • Intercepts and logs packets • Wireshark

  30. Port Scanners

  31. Probes ports on other systems • Used to look for unintentionally opened ports • Used by hackers • Nmap

  32. Throughput Testers

  33. Measures data flow in a network • Speedtest.net

More Related