Cisco SGE2000 Configuration Guide - Page 131

Troubleshooting the Link Interface Subsystem, SCE 2000, show ip, route, <host-ip-address&gt

Get Cisco SGE2000 PDF manuals and user guides View all Cisco SGE2000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 131 highlights

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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
8-11
Cisco SCE 2000 4xGBE Installation and Configuration Guide
OL-7824-06
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
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)
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
Connecting the
Management Interfaces
and Performing Initial
System Configuration
Refer to "
IP
Configuration
" in the
Cisco Service Control
Engine (SCE) Software
Configuration Guide.
CLI commands:
•
show
access-lists
•
show line vty
access-class
•
show ip
access-class
Host is not a member of
a valid access-list.
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
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>
Table 8-6
Troubleshooting the Management
Subsystem (continued)
Symptom
Diagnostic Action
Possible Cause
Possible Solution