Chapter 3 Troubleshooting
Diagnosing Problems
•Verify that you are using the correct cable type. See Appendix B, “Connector and Cable Specifications,” for more information.
•Test for loose connections. Sometimes a cable appears to be seated, but is not. Disconnect and then reconnect the cable.
SFP Module Port Issues
Use only Cisco small
•Bad or wrong SFP module. Exchange the suspect module with a known, good module. Verify that this module supports this platform. See the “Cisco TwinGig Converter Module” section on page
•Use the show interfaces privileged EXEC command to determine the port or module
•Make sure that all
Port and Interface Settings
Verify that the port or interface is not disabled or for some reason powered down. If a port or interface is manually shut down on one or the other side of the link, the link does not come up until you
Ping the End Device
Test the end device by pinging it from the directly connected switch module first, and then work your way back port by port, interface by interface, trunk by trunk, until you find the source of the connectivity issue. Make sure that each switch module can identify the end device MAC address in its
Spanning Tree Loops
Spanning Tree Protocol (STP) loops can cause serious performance issues that might appear to be port or interface problems. In this situation, the switch module bandwidth is used repeatedly by the same frames, crowding out legitimate traffic.
A unidirectional link can cause loops. This occurs when the traffic that the switch module sends is received by its neighbor, but the switch module does not receive the traffic that is sent from the neighbor. A broken
You can enable the UniDirectional Link Detection (UDLD) protocol on the switch module to help identify
Cisco Catalyst Blade Switch 3120 for HP Hardware Installation Guide
|
| |
|