cc/td/doc/product/lan/cat4224
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Troubleshooting

Troubleshooting

This section describes how to troubleshoot the Catalyst 4224 Access Gateway Switch. This section describes the LEDs that indicate port connectivity problems and overall switch performance.

Note   You can obtain statistics about your switch from the browser interface, from the command-line interface (CLI), or from a Simple Network Management Protocol (SNMP) workstation. Refer to the Cisco IOS Desktop Switching Software Configuration Guide, the Cisco IOS Desktop Switching Command Reference (online only), or the documentation that came with your SNMP application for details.

Common switch problems fall into the following categories:

Table 5-1 describes how to detect and resolve these common problems.

Table 5-1   Common Problems and Solutions

Symptom Possible Cause Resolution
Poor performance or excessive errors.

Duplex auto-negotiation mismatch.

Refer to the Cisco IOS Desktop Switching Software Configuration Guide for information on identifying auto-negotiation mismatches.

Cabling distance exceeded.
  • Port statistics show excessive frame check sequence (FCS), late-collision, or alignment errors.
  • For 100BaseTX connections:
    • The distance between the port and the attached device exceeds 100 meters.
    • If the switch is attached to a repeater, the total distance between the two end stations exceeds the 100Base-T cabling guidelines.
  • For 10BaseT connections: The distance between the port and the attached device exceeds 100 meters.

 

  • Refer to the Cisco IOS Desktop Switching Software Configuration Guide for information on displaying port statistics.
  • Reduce the cable length to within the recommended distances.

Refer to your 100BaseT repeater documentation for cabling guidelines.




  • Reduce the cable length to within the recommended distances.
Bad adapter in attached device.
  • Excessive errors are found in port statistics.
  • Spanning Tree Protocol is checking for possible loops.

 

  • Run the adapter card diagnostic utility.
  • Wait 30 seconds for the LED to turn green.
No connectivity. Incorrect or bad cable.

The following causes are indicated by no link at both ends:

  • A crossover cable was used when a straight-through cable was required, or vice-versa.
  • The cable is wired incorrectly.
  • Spanning Tree Protocol is checking for possible loops.
Unreadable characters on the management console.

Incorrect baud rate was detected.

Reset the emulation software to 9600 baud.

System LED is amber.

LED is amber until the system is online. Once online, the LED is green.

If the POST fails or the system is overheating, the status LED is red.

Check the POST errors logged on the console.

System LED is red.
  • Switch is overheating.


 

 






 

  • Nonfatal or fatal POST error detected.
  • Use the show env command to check if an over-temperature condition exists. If it does:
    • Place the switch in an environment that is within 32 to 113°F (0 to 45°C).
    • Make sure fan intake and exhaust areas are clear.

If a multiple-fan failure is causing the switch to overheat, replace the switch.

  • Check the POST errors logged on the console.
Cisco IP Phone fails to power on when connected to a Catalyst 4224.

Improper cabling.

Make sure the switch is connected to the LAN-to-phone jack on the Cisco IP Phone.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Sat Jan 18 13:42:07 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.