Chapter 8
Troubleshooting
Table 8-6
Symptom
Telnet connection
terminates
automatically
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:
•
•
OL-7824-06
Troubleshooting the Management Subsystem (continued)
Diagnostic Action
CLI command: show ip
route
<host-ip-address>
CLI commands:
•
•
•
CLI commands:
•
•
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)
Possible Cause
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).
Host is not a member of
a valid access-list.
show access-lists
show line vty
access-class
show ip
access-class
Telnet connection may
be timing out.
show line
show line vty
timeout
Cisco SCE 2000 4xGBE Installation and Configuration Guide
Troubleshooting Overview
Possible Solution
Check / reconfigure
routing tables. See
Connecting the
Management Interfaces
and Performing Initial
System Configuration
Refer to " IP
Configuration " in the
Cisco Service Control
Engine (SCE) Software
Configuration Guide.
See
Connecting the
Management Interfaces
and Performing Initial
System Configuration
Refer to " Access
Control Lists " in the
Cisco Service Control
Engine (SCE) Software
Configuration Guide
Reconfigure line
timeout.
timeout <time
in seconds>
8-11