Filter
Top Products
Chapter 8 Troubleshooting
Problem Solving Using a Subsystems Approach
SCE 2000 4xGBE Installation and Configuration Guide
8-14 OL-7824-02
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 2000 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 2000 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
through 4.
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 2000 (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 8-7 Troubleshooting the Link Interface Subsystem
Symptom Diagnostic Action Possible Cause Possible Solution
• Link is down. (LINK
LED not lit)
• Status is WARNING
(Status LED is
flashing orange)
• Output counters not
incrementing.
CLI command:
• show interface
GigabitEtherne
t 0/# counters
Connector is not connected to
the platform or to the network
Reconnect the cable to the GBE
port and to network.
GBE cable is broken
Reconnect / replace the cable to
the GBE port.
If GBE counters are
incrementing, this indicates
LED problem. Contact customer
support.
Check output of show
interface
GigabitEthernet
0/# counters
command for: “In
good unicast packet”
and “Out unicast
packet”. These
counters should be
constantly
incrementing.
Auto-negotiation may be
incorrectly configured.
Check auto-negotiation
("Configuring the GBE
Interface Parameters" on page 6-
7) configuration in the SCE
2000 and in its peers.