|
Symptom |
Possible Cause |
Resolution |
Poor performance or excessive errors.
|
Duplex autonegotiation mismatch.
|
Refer to the switch software configuration guide for information about identifying autonegotiation mismatches.
|
Cabling distance exceeded.
- Port statistics show excessive FCS,1 late-collision, or alignment errors.
|
- Refer to the switch software configuration guide for information about displaying port statistics.
|
- For 10BASE-T, 100BASE-TX, and 1000BASE-T connections:
- The distance between the port and the attached device exceeds 328 feet
(100 meters).
|
- Reduce cable length to within the recommended distances.
|
- If the switch is attached to a repeater, the total distance between the two end stations exceeds the cabling guidelines.
|
- Refer to your repeater documentation for cabling guidelines.
|
- For GBIC2 module port connections: The distance between the GBIC module port and the attached device exceeds the GBIC cabling guidelines.
|
- Refer to your GBIC module documentation for cabling guidelines.
|
- For SFP3 module port connections: The distance between the SFP module port and the attached device exceeds the SFP cabling guidelines.
|
|
Poor performance or excessive errors (continued).
|
Bad adapter in attached device.
- Excessive errors found in port statistics.
|
- Run adapter card diagnostic utility.
|
STP4 checking for possible loops.
|
Wait 30 seconds for port status LED to turn green.
|
No connectivity.
|
Incorrect or bad cable.
|
|
No link at both ends.
|
|
- A crossover cable was used when a straight-through was required, or the reverse.
|
|
- The cable is wired incorrectly.
|
- Replace it with a tested good cable.
|
- STP checking for possible loops.
|
- Wait 30 seconds for port status LED to turn green.
|
Switch not recognizing a GBIC module.
|
Refer to your GBIC module documentation for more information.
|
Switch not recognizing an SFP module.
|
Refer to your SFP module documentation for more information.
|
Unreadable characters on the management console.
|
Incorrect baud rate.
|
Reset the terminal-emulation software to 9600 baud.
|
System LED is amber, and all port LEDs are off.
|
Corrupted software.
|
Attach a monitor to the serial port to display the switch boot loader. For more information, refer to the switch software configuration guide.
|
System LED is amber.
|
- Internal fan fault detected.
|
- Check if the fan has failed by using the show env fan privileged EXEC command.
If the fan has failed, call Cisco Systems.
|
- Nonfatal or fatal POST error detected.
|
- Use the show post privileged EXEC command to see which POST test failed.
|
Switch placed in error-disabled state after CWDM5 GBIC or SFP module is inserted.
|
Bad or non-Cisco-approved CWDM GBIC module or SFP module.
|
Remove the CWDM GBIC or SFP module from the switch, and replace it with a Cisco-approved module. Use the errdisable recovery cause gbic-invalid global configuration command to verify port status, and enter a time interval to recover from the error-disabled state.
Refer to the switch software configuration guide for information about the errdisable recovery command.
|
STAT LED on Catalyst 2950 LRE6 switch is not on.
|
Telephone cable is loose or is not connected properly.
|
Reseat telephone cable into the telephone wall jack and the Cisco LRE CPE7.
|
Telephone cable is defective.
|
Replace the telephone cable.
|
Cable trunking defective.
|
Repair the cable trunking, or select an alternative pair of cables.
|
Cisco LRE CPE is not communicating with Catalyst 2950 LRE switch, or Cisco LRE CPE might be attempting to exceed the rate or the reach selected by the switch.
|
- Reduce cable length to within the recommended distances. (See the "LRE Port" section for LRE cabling guidelines.)
- Refer to the switch software configuration guide for information about verifying LRE port link status.
|
Catalyst 2950 LRE switch does not support the Cisco LRE CPE.
|
See the compatibility matrix, Table 2-1, for more information.
|
