|
|
Use Table 3-1 to identify problems with the modules and take the appropriate corrective action.
| Symptom | Possible Causes | Corrective Action |
|---|---|---|
Thumbscrews have not been tightened. | Tighten thumbscrews. | |
| ||
| Port is initializing, it was disabled by management or an address violation, or it was blocked by Spanning Tree Protocol. | |
Port is experiencing error frames. This could be due to a duplex mismatch caused by autonegotiation, collisions, CRC errors, or alignment errors. | ||
Port LED is off. | Device has no power. | Ensure that the switch and the target device have power. |
| Wrong cable type. | Verify that the cable is correct: crossover or straight-through. |
| Bad cable. No cable. | Replace with a known good cable. Insert and connect cable. |
Expansion slot LED is amber. | Module failed POST. | Ensure that the switch is running an IOS software release that supports the module. (See "Key Features" in "Overview.") If the IOS software release is correct, call Cisco Systems to replace the module. |
Switch crashes or reboots | Removed the module before disconnecting the module port cables. | Reset switch (if the switch doesn't reset itself). When hot swapping the module, disconnect the cable from the module port before removing the module from the switch. |
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Tue May 23 17:44:32 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.