8-10
Cisco SCE8000 Installation and Configuration Guide, Rel 3.1.7
OL-16478-03
Chapter 8 Troubleshooting
Troubleshooting Overview
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 Cisco SCE8000 is often caused by link problems
or the 10GBE 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 Cisco SCE8000 or there is actually no
traffic on the line, which could be a normal situation).
Note In CLI commands for TenGigabitEthernet interfaces, # stands for the number of the SPA module
(SCE8000-SIP subslot). This can be 0 through 3.
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 Cisco SCE8000 (LINK LED is lit and Tx LED is flashing)
• 10GBE link is up but not receiving from peer (LINK LED is lit, but Rx LED is not flashing)
CLI command: show ip route
<host-ip-address>
Routing tables are incorrectly
configured (when the host
used as client is not in the
same network as the SCE
Platform, and there is more
than one gateway on the SCE
Platform network).
Check / reconfigure routing
tables. See Initial Setup
Parameters, page 5-2
Refer to "IP Configuration"
in the Cisco SCE8000
Software Configuration
Guide.
CLI commands:
• show access-lists
• show ip access-class
Host is not a member of a
valid access-list.
See Initial Setup Parameters,
page 5-2
Refer to "Access Control
Lists “ in the Cisco SCE8000
Software Configuration
Guide.
Telnet connection terminates
automatically
CLI commands:
• show line
• show line vty timeout
Telnet connection may be
timing out.
Reconfigure line timeout.
timeout <time in seconds>
Figure 8-4 Troubleshooting the Management Subsystem (continued)
Symptom Diagnostic Action Possible Cause Possible Solution
To Next Page
Loading...
Need help?
General
