Troubleshooting The Link Interface Subsystem - Cisco SCE 1000 Installation And Configuration Manual

Problem Solving Using a Subsystems Approach
Telnet connection CLI commands:
terminates
• show line
automatically
•
show line vty
timeout

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).
In CLI commands of GigabitEthernet interfaces, # stands for the number of the interface. This
Note
can be 1 or 2.
Problems in the link interface subsystem could be any of the following:
•
•
•
Table 8-7
Symptom Diagnostic Action
• Link is down.
CLI command:
(LINK LED not
• show interface
lit)
GigabitEthernet
• Status is
0/# counters
WARNING
(Status LED is
flashing orange)
• Output counters
not incrementing.
Cisco SCE 1000 2xGBE Installation and Configuration Guide
8-14
Telnet connection may be
timing out.
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)
Troubleshooting the Link Interface Subsystem
Possible Cause
Connector is not connected to
the platform or to the network
GBE cable is broken
Chapter 8
Reconfigure line timeout.
timeout <time in
seconds>
Possible Solution
Reconnect the cable to the GBE
port and to network.
Reconnect / replace the cable to
the GBE port.
If GBE counters are
incrementing, this indicates
LED problem. Contact
customer support.
Troubleshooting
OL-7821-04