Chapter 8 Troubleshooting
Problem Solving Using a Subsystems Approach
Telnet connection | CLI commands: |
terminates | • show line |
automatically | |
| • show line vty |
| timeout |
Telnet connection may be timing out.
Reconfigure line timeout.
timeout <time in seconds>
Troubleshooting the Link Interface Subsystem
Check the following to help isolate a problem in the link interface subsystem.
In general, the case where no traffic is coming out of the SCE 1000 is often caused by link problems or GBE interface configuration. Note that in some cases, the problem which seems as a transmit problem could be in the Rx (no traffic is being received by the SCE 1000 or there is actually no traffic on the line, which could be a normal situation).
Note In CLI commands of GigabitEthernet interfaces, # stands for the number of the interface. This can be 1 or 2.
Problems in the link interface subsystem could be any of the following:
•Link is down. (LINK LED not lit and system status is WARNING)
•Peer does not receive traffic from SCE 1000 (GBE link is lit and Tx LED is flashing)
•GBE link is up but not receiving from peer (GBE link is lit, but Rx LED is not flashing)
| Table | Troubleshooting the Link Interface Subsystem | ||
|
|
|
| |
Symptom | Diagnostic Action | Possible Cause | Possible Solution | |
|
|
|
|
|
• Link is down. | CLI command: |
| Connector is not connected to | Reconnect the cable to the GBE |
(LINK LED not | • show interface |
| the platform or to the network | port and to network. |
lit) |
|
|
| |
GigabitEthernet |
|
| ||
• Status is | 0/# counters |
|
|
|
WARNING |
|
|
|
|
(Status LED is |
|
|
|
|
flashing orange) |
|
|
|
|
• Output counters |
|
|
|
|
not incrementing. |
|
|
|
|
|
|
|
|
|
|
|
| GBE cable is broken | Reconnect / replace the cable to |
|
|
|
| the GBE port. |
|
|
|
|
|
|
|
|
| If GBE counters are |
|
|
|
| incrementing, this indicates |
|
|
|
| LED problem. Contact |
|
|
|
| customer support. |
|
|
|
|
|
Cisco SCE 1000 2xGBE Installation and Configuration Guide
| ||
|
|
|
