3-2
Troubleshooting
Basic Troubleshooting Tips
Ensure all devices connected to the switches are configured to auto
negotiate, or are configured to connect at half duplex (all hubs are
configured this way, for example).
■ Faulty or loose cables. Look for loose or obviously faulty connections.
If the cables appear to be OK, make sure the connections are snug. If that
does not correct the problem, try a different cable.
■ Non-standard cables. Non-standard and miswired cables may cause
network collisions and other network problems, and can seriously impair
network performance. Use a new correctly-wired cable or compare your
cable to the cable in appendix A, “Cabling and Technology Information
Specifications” for pinouts and correct cable wiring. A category 5 cable
tester is a recommended tool for every 100Base-TX and 1000Base-T
network installation.
■ Improper Network Topologies. It is important to make sure you have
a valid network topology. Common topology faults include excessive
cable length and excessive repeater delays between end nodes. If you have
network problems after recent changes to the network, change back to
the previous topology. If you no longer experience the problems, the new
topology is probably at fault. Sample topologies are shown at the end of
chapter 2 in this book, and some topology configuration guidelines can
be found online at the ProCurve Web site, www.hp.com/go/procurve.
In addition, you should make sure that your network topology contains
no data path loops. Between any two end nodes, there should be only
one active cabling path at any time. Data path loops will cause broadcast
storms that will severely impact your network performance.
For more information on possible network problems and their solutions, refer
to the technical note “Troubleshooting LAN Performance and Intermittent
Connectivity Problems”, which can be found on the ProCurve Web site,
www.hp.com/go/procurve, in the Reference Library section, A-Z Index.
To Next Page
Loading...
