|
| Chapter 8 | Troubleshooting |
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Problem Solving Using a Subsystems Approach |
| |
|
|
|
|
|
|
|
|
|
|
|
|
| CLI command: | Too many Telnet | Close one or more of the open Telnet | ||
|
|
|
| show telnet | connections (up to 5 | sessions. | ||
|
|
|
| concurrent sessions are |
|
|
| |
|
|
|
| sessions | supported). |
|
|
|
|
|
|
| CLI command: | Default gateway is incorrect | Check / reconfigure default gateway. | ||
|
|
|
| show ip default- | (when the host used as client | See Initial System Configuration (on | ||
|
|
|
| is not in the same network | ||||
|
|
|
| gateway | as the SCE Platform). | page | ||
|
|
|
|
|
| Refer to "IP Configuration" in the | ||
|
|
|
|
|
| Cisco Service Control Engine (SCE) | ||
|
|
|
|
|
| Software Configuration Guide. | ||
|
|
|
|
|
|
|
|
|
|
|
|
| CLI command: | Routing tables are | Check / reconfigure routing tables. | ||
|
|
|
| show ip route | incorrectly configured | See Initial System Configuration (on | ||
|
|
|
| (when the host used as client | ||||
|
|
|
|
| is not in the same network | page | ||
|
|
|
|
| as the SCE Platform, and | Refer to "IP Configuration" in the | ||
|
|
|
|
| there is more than one | Cisco Service Control Engine (SCE) | ||
|
|
|
|
| gateway on the SCE | Software Configuration Guide. | ||
|
|
|
|
| Platform network). |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CLI commands: | Host is not a member of a | Check / reconfigure | ||
|
|
|
| • show access- | valid | See Initial System Configuration (on | ||
|
|
|
|
| ||||
|
|
|
| lists |
| page | ||
|
|
|
| • show line vty |
| Refer to "Access Control Lists" in | ||
|
|
|
|
| the Cisco Service Control Engine | |||
|
|
|
| • show ip access- |
| (SCE) Software Configuration Guide. | ||
|
|
|
|
|
|
|
| |
|
|
|
| class |
|
|
|
|
Telnet connection |
| CLI commands: | Telnet connection may be | Reconfigure line timeout. | ||||
terminates |
| • show line | timing out. | timeout <time in | ||||
automatically |
|
| ||||||
|
|
|
| • show line vty |
| seconds> | ||
|
|
|
| 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 2000 is often caused by link problems or FE 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 FastEthernet 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)
Cisco SCE 2000 4/8xFE Installation and Configuration Guide
| ||
|
|
|
