Cisco 10720 Internet Router Installation and Configuration Guide - Troubleshooting

Table Of Contents

Troubleshooting

Basic Troubleshooting RPR-IEEE for the Uplink Card

Using the show controller rpr-ieee Command

Using the show controllers rpr-ieee 1/1 transceiver Command

Using the show arp Command

Verifying Clocking

PASS-THRU Mode

Verifying the PASS-THRU Mode

Using the show rpr-ieee topology Command

Using the show rpr-ieee protection Command

Fiber Misconnection

Basic Troubleshooting SRP for the Uplink Card

Using the show controller srp Command

Using the show arp Command

Verifying Clocking

PASS-THRU Mode

Verify the PASS-THRU Mode

Using the show srp topology Command

Using the show srp ips Command

Fiber Misconnection

Alarm Messages

Alarm Messages

Basic Troubleshooting Ethernet for the Access Card

Verifying Interface Configuration

FastEthernet/GigabitEthernet Is up

Line Protocol Is up

Duplex Mode Setting

Speed Mode

Output Hang

CRC Field Counters

Late Collision

Carrier Signal

Cleaning the Fiber-Optic Connections

Troubleshooting

This section contains basic troubleshooting guidance for the Cisco 10720 Internet Router and components.

•Basic Troubleshooting RPR-IEEE for the Uplink Card

•Basic Troubleshooting SRP for the Uplink Card

•Alarm Messages

•Basic Troubleshooting Ethernet for the Access Card

Basic Troubleshooting RPR-IEEE for the Uplink Card

This section provides basic troubleshooting guidelines for RPR-IEEE on the RPR/SRP uplink card. For additional information about RPR-IEEE configurations, refer to the Cisco IOS Software Configuration for the Cisco 10720 Internet Router publication. For additional Cisco IEEE 802.17 related documentation, see the "Related Documentation" section on page xix.

The following sections present information on show commands, verification steps, and alarm messages:

•Using the show controller rpr-ieee Command

•Using the show arp Command

•Verifying Clocking

•PASS-THRU Mode

•Verifying the PASS-THRU Mode

•Using the show rpr-ieee topology Command

•Using the show rpr-ieee protection Command

•Fiber Misconnection

Using the show controller rpr-ieee Command

Verify the following using the show controller rpr-ieee command:

•RX optics readout values are within specifications. For example: RX readout values: -11 dBm - Within specifications, RX readout values: -15 dBm - Within specifications

•Error counters are not incrementing.

•There are no active defects or alarms. For example, Active Alarms: None

•Proper clocking configuration for each span (East and West). For example,
Clock source: Internal

•Proper hosts are on the proper side. For example, Remote span id: East, Remote span id: West

The following example shows sample output from this command:
Router# show controllers rpr-ieee 1/1
Interface RPR-IEEE1/1
Hardware is OC48 RPR-IEEE
RPR-IEEE1/1 - West Span (Ringlet0 RX, Ringlet1 TX)
SFP Module West is VALID
OPTICS
TX power -4 (+/- 3) dBm
RX power -5 (+/- 3) dBm
No Active Alarms
No Active Warnings
SECTION
  LOF = 0          LOS    = 0                            BIP(B1) = 0
LINE
  AIS = 0          RDI    = 0          FEBE = 0          BIP(B2) = 0
PATH
   AIS = 0          RDI    = 0          FEBE = 0          BIP(B3) = 0
   LOP = 0          NEWPTR = 0          PSE  = 0          NSE     = 0
Active Defects: None
Active Alarms:  None
Alarm reporting enabled for: SLOS SLOF PLOP 
Framing           : SONET
Rx SONET/SDH bytes: (K1/K2) = 0/0        S1S0 = 0  C2 = 0x16
Tx SONET/SDH bytes: (K1/K2) = 0/0        S1S0 = 0  C2 = 0x16  J0 = 0x1 
Clock source      : Internal
Framer loopback   : None
Path trace buffer : Stable 
  Remote hostname : EAST-D
 Remote interface: RPR-IEEE1/1
  Remote IP addr  : 1.1.1.1
  Remote side id  : EAST   
BER thresholds:           SF = 10e-3  SD = 10e-6
IPS BER thresholds(B3):   SF = 10e-3  SD = 10e-6
TCA thresholds:           B1 = 10e-6  B2 = 10e-6  B3 = 10e-6
biff (6:57:52 PM):  RPR-IEEE1/1 - East Span (Ringlet1 RX, Ringlet0 TX)
SFP Module East is VALID
OPTICS
TX power -4 (+/- 3) dBm
RX power -5 (+/- 3) dBm
No Active Alarms
No Active Warnings
SECTION
  LOF = 0          LOS    = 0                            BIP(B1) = 0
LINE
  AIS = 0          RDI    = 0          FEBE = 0          BIP(B2) = 0
PATH
  AIS = 0          RDI    = 0          FEBE = 0          BIP(B3) = 0
  LOP = 0          NEWPTR = 0          PSE  = 0          NSE     = 0
Active Defects: None
Active Alarms:  None
Alarm reporting enabled for: SLOS SLOF PLOP 
Framing           : SONET
Rx SONET/SDH bytes: (K1/K2) = 0/0        S1S0 = 0  C2 = 0x16
Tx SONET/SDH bytes: (K1/K2) = 0/0        S1S0 = 0  C2 = 0x16  J0 = 0x1 
Clock source      : Internal
Framer loopback   : None
Path trace buffer : Stable 
 Remote hostname : WEST-D
 Remote interface: RPR-IEEE1/1
 Remote IP addr  : 1.1.1.3
 Remote side id  : WEST   
BER thresholds:           SF = 10e-3  SD = 10e-6
IPS BER thresholds(B3):   SF = 10e-3  SD = 10e-6
TCA thresholds:           B1 = 10e-6  B2 = 10e-6  B3 = 10e-6
Using the show controllers rpr-ieee 1/1 transceiver Command

Use the transceiver keyword to display additional information about the status of the small form-factor pluggable (SFP) module used in an RPR port.
Router# show controllers rpr-ieee 1/1 transceiver
Show Transceiver: West Span
Static information
ID: SFP transceiver
Extended ID: 4
Connector: LC
SONET compliance: OC48SR
Gigabit Ethernet compliance: unspecified
Fibre Channel link length: unspecified
Fibre Channel transmitter technology: unspecified
Fibre Channel transmission media: unspecified
Fibre Channel speed: unspecified
Encoding: reserved
Bit Rate: 2500 Mbps
Single mode fiber supported length: 2 km
Upper bit rate limit: unspecified
Lower bit rate limit: unspecified
Date code (yyyy/mm/dd): 2004/04/21
Vendor PN: SCP6828-C5-BNE
Vendor revision number: D
Vendor serial number: ECL0817001L
Transceiver status information
Diagnostics calibration is external
Temperature 39 (+/-3 Celsius)
Voltage in transceiver 3232600 uV (+/- 10 mV)
TX bias 8940 uA (+/- 100uA)
TX power 316000 nW / -5 dBm (+/- 3dBm)RX power 300200 nW / -5 dBm (+/- 3dBm)
No Active Alarms
No Active Warnings
Alarm Thresholds:
						high                     low
Temperature               96 C                   -44 C
Voltage              4000000 uV                    0 uV
TX bias                70000 uA                    0 uA
TX power             1000000 nW / 0   dBm      50100 nW / -13 dBm
RX power             1008300 nW / 0   dBm   unspecified
Warning Thresholds:
                        high                     low
Temperature               91 C                   - 9 C
Voltage              3600000 uV              3000000 uV
TX bias                60000 uA                    0 uA
TX power              630900 nW / -2  dBm      79400 nW / -11 dBm
RX power             1008300 nW / 0   dBm   unspecified
Show Transceiver: East Span
Static information
ID: SFP transceiver
Extended ID: 4
Connector: LC
SONET compliance: OC48SR
Gigabit Ethernet compliance: unspecified	
Fibre Channel link length: unspecified
Fibre Channel transmitter technology: unspecified
Fibre Channel transmission media: unspecified
Fibre Channel speed: unspecified
Encoding: reserved
Bit Rate: 2500 Mbps
Single mode fiber supported length: 2 km
Upper bit rate limit: unspecified
Lower bit rate limit: unspecified
Date code (yyyy/mm/dd): 2004/04/21
Vendor PN: SCP6828-C5-BNE
Vendor revision number: D
Vendor serial number: ECL0817001M
Transceiver status information
Diagnostics calibration is external
Temperature 38 (+/-3 Celsius)
Voltage in transceiver 3230800 uV (+/- 10 mV)
TX bias 8724 uA (+/- 100uA)
TX power 285600 nW / -5 dBm (+/- 3dBm)
RX power 309900 nW / -5 dBm (+/- 3dBm)
No Active Alarms
No Active Warnings
Alarm Thresholds:
                        high                     low
Temperature               96 C                   -44 C
Voltage              4000000 uV                    0 uV
TX bias                70000 uA                    0 uA
TX power             1000000 nW / 0   dBm      50100 nW / -13 dBm
RX power             1008300 nW / 0   dBm   unspecified
Warning Thresholds:
                        high                     low
Temperature               91 C                   - 9 C
Voltage              3600000 uV              3000000 uV
TX bias                60000 uA                    0 uA
TX power              630900 nW / -2  dBm      79400 nW / -11 dBm
RX power             1008300 nW / 0   dBm   unspecified
Using the show arp Command

Use the show arp command to verify that the correct Address Resolution Protocol (ARP) table is loaded.

The following example shows sample output from this command:
Router# show arp
Protocol Address      Age (min)   Hardware            Addr Type      Interface 
Internet 1.1.1.1           154    0001.0001.0001      RPR-IEEE-W     RPR-IEEE1/1 
Internet 1.1.1.3           155    0003.0003.0003      RPR-IEEE-E     RPR-IEEE1/1 
Internet 1.1.1.2             -    0002.0002.0002      RPR-IEEE       RPR-IEEE1/1 
Internet 200.1.1.1           -    0001.64ff.0601      ARPA           GigabitEthernet2/1 
Router# 
Verifying Clocking

There are two modes of clocking for the rpr-ieee interface, LINE and INTERNAL. Clocking works over dark fiber.

•INTERNAL means that the rpr-ieee interface uses its internal 20ppm or Stratum-3 clock. LINE means it takes timing from the other span of the line.

•Having both spans with clocking set to INTERNAL is the default configuration and results in normal operation.

•Having both spans with clocking set to LINE is not advised and will result in bit interleaved parity (BIP) errors over time.

•Pairing opposite spans of a connection with one spans INTERNAL and one span LINE is acceptable, but not necessary.

Ideal clocking is achieved when all interfaces have the clocking set to INTERNAL. The following example shows this configuration:
router(config)# interface rpr-ieee 1/1
router(config-if)# rpr-ieee clock-source internal East
router(config-if)# rpr-ieee clock-source internal West
PASS-THRU Mode

The rpr-ieee line card acts as an optical regenerator when it is operating in PASS-THRU mode. PASS-THRU mode isolates the node. This mode is activated when the interface is placed in shutdown mode, or the node is not receiving layer 2 keepalives on span East or span West.

Use the shutdown interface configuration command to place the router rpr-ieee interface in PASS-THRU mode.

PASS-THRU mode is a useful troubleshooting tool for isolating which node on the ring is faulty.

The following example shows sample output from this command:
Router# configure terminal 
Enter configuration commands, one per line. End with CNTL/Z. 
Router(config)#interface RPR-IEEE 1/1 
Router(config-if)#shutdown 
Router(config-if)#end 
Router# 
3d06h: %SYS-5-CONFIG_I: Configured from console by tty1 
3d06h: %LINK-5-CHANGED: Interface RPR-IEEE1/1, changed state to administratively down 
3d06h: %LINEPROTO-5-UPDOWN: Line protocol on Interface RPR-IEEE1/1, changed state to down
Verifying the PASS-THRU Mode

Use the show rpr-ieee ips EXEC command to verify that the rpr-ieee node is in PASS-THRU mode, which occurs when the interface is administratively down.

The following example shows sample output from this command:
Router# show rpr-ieee protection
RPR-IEEE1/1 is administratively down 
Router#
Using the show rpr-ieee topology Command

Use the show rpr-ieee topology EXEC command to verify that topology is valid.

The following example shows sample output from this command:
Router# show rpr-ieee topology 
Ring Topology: CLOSED (STABLE)
  Configured protection mode: WRAPPING 
  Jumbo preference: SET (ring supports JUMBOS)
  Number of nodes on
      ringlet0: 3       ringlet1: 3
  Checksum: 0x001800D6
  Index (Ri 0)       MAC        IP Address       Edge W/E    Request W/E
       1        0001.0001.0001    1.1.1.1          NO/NO      IDLE/IDLE
       2        0003.0003.0003    1.1.1.3          NO/NO      IDLE/IDLE
       3        0002.0002.0002    1.1.1.2          NO/NO      IDLE/IDLE
  Index (Ri 1)       MAC        IP Address       Edge W/E    Request W/E
       1        0003.0003.0003    1.1.1.3          NO/NO      IDLE/IDLE
       2        0001.0001.0001    1.1.1.1          NO/NO      IDLE/IDLE
       3        0002.0002.0002    1.1.1.2          NO/NO      IDLE/IDLE
Using the show rpr-ieee protection Command

The show rpr-ieee protection command displays the status of the 802.17 topology-protection. It contains information such as the neighbors found on each ringlet, the protection mode/status and the topology checksum values/status.

The following example shows sample output from this command:
Router# show rpr-ieee protection
Protection Information for Interface RPR-IEEE1/1
 MAC Addresses
   West Span (Ringlet 0 RX) neighbor 0001.0001.0001
   East Span (Ringlet 1 RX) neighbor 0003.0003.0003
   Station MAC address 0002.0002.0002
 TP frame sending timers:
     fast timer: 10 msec
     slow timer: 1x100 msec (100 msec)
 Protection holdoff timers:
     L1 Holdoff                         Keepalive Detection
     West Span  0x10 msec (  0 msec)    West Span   3 msec
     East Span  0x10 msec (  0 msec)    East Span   3 msec
  Configured protection mode: WRAPPING 
 Protection Status
   Ring is IDLE
   Protection WTR period is 10 sec. (timer is inactive)
     Self Detected Requests               Remote Requests
     West Span IDLE                       West Span IDLE 
     East Span IDLE                       East Span IDLE 
     Distant Requests                                    
     East Span IDLE                       West Span IDLE
   West Span Failures: none East Span Failures: none
If the ring reports an "OPEN" state in the topology, there is a link failure in the ring, the details in the ringlet indices will pinpoint the failure location by indicating the Edge location and the Request (reason) for the Edge.
Fiber Misconnection

Use the show rpr-ieee EXEC command to check for misconnected fiber cables, for example, span East to span East or TX to TX. The message, "Misconnection Alarm" shows at the top of the show rpr-ieee command output when there is a fiber misconnection.

•One alarm—the problem is with another node on the ring. For example, span East connected to span East.

•Two alarms—the problem is your node. For example, span East to span East and span West to span West.

Basic Troubleshooting SRP for the Uplink Card

This section provides basic troubleshooting guidelines for SRP on the DPT, POS/DPT, and RPR/SRP uplink cards. For additional information about SRP configurations, refer to the Cisco IOS Software Configuration for the Cisco 10720 Internet Router publication. For additional Cisco SRP-related documentation, see the "Related Documentation" section on page xix.

The following sections present information on show commands, verification steps, and alarm messages:

•Using the show controller srp Command

•Using the show arp Command

•Verifying Clocking

•PASS-THRU Mode

•Verify the PASS-THRU Mode

•Using the show srp topology Command

•Using the show srp ips Command

•Fiber Misconnection

Using the show controller srp Command

Verify the following using the show controller srp command:

•RX optics readout values are within specifications. For example: RX readout values: -11 dBm - Within specifications, RX readout values: -15 dBm - Within specifications

•Error counters are not incrementing.

•There are no active defects or alarms. For example, Active Alarms: None

•Proper clocking configuration for each side (A and B). For example,
Clock source : Internal

•Proper hosts are on the proper side. For example, Remote side id : A,
Remote side id : B
Router# show controllers srp
Interface SRP1/1
Hardware is OC48 SRP
SRP1/1 - Side A (Outer RX, Inner TX)
OPTICS
RX readout values: -11 dBm    - Within specifications
SECTION
  LOF = 0          LOS    = 0                            BIP(B1) = 0
LINE
  AIS = 0          RDI    = 0          FEBE = 0          BIP(B2) = 0
PATH
  AIS = 0          RDI    = 0          FEBE = 0          BIP(B3) = 0
  LOP = 0          NEWPTR = 0          PSE  = 0          NSE     = 0
Active Defects: None
Active Alarms:  None
Alarm reporting enabled for: SLOS SLOF PLOP 
Framing           : SONET
Rx SONET/SDH bytes: (K1/K2) = 0/0        S1S0 = 0  C2 = 0x16
Tx SONET/SDH bytes: (K1/K2) = 0/0        S1S0 = 0  C2 = 0x16  J0 = 0x1 
Clock source      : Internal
Framer loopback   : None
Path trace buffer : Stable 
  Remote hostname : M0415B
  Remote interface: SRP2/0
  Remote IP addr  : 48.1.1.2
  Remote side id  : B
BER thresholds:           SF = 10e-3  SD = 10e-6
IPS BER thresholds(B3):   SF = 10e-3  SD = 10e-6
TCA thresholds:           B1 = 10e-6  B2 = 10e-6  B3 = 10e-6
SRP1/1 - Side B (Inner RX, Outer TX)
OPTICS
RX readout values: -15 dBm    - Within specifications
SECTION
  LOF = 0          LOS    = 0                            BIP(B1) = 0
LINE
  AIS = 0          RDI    = 0          FEBE = 0          BIP(B2) = 0
PATH
  AIS = 0          RDI    = 0          FEBE = 0          BIP(B3) = 0
  LOP = 0          NEWPTR = 0          PSE  = 0          NSE     = 0
Active Defects: None
Active Alarms:  None
Alarm reporting enabled for: SLOS SLOF PLOP 
Framing           : SONET
Rx SONET/SDH bytes: (K1/K2) = 0/0        S1S0 = 0  C2 = 0x16
Tx SONET/SDH bytes: (K1/K2) = 0/0        S1S0 = 0  C2 = 0x16  J0 = 0x1 
Clock source      : Internal
Framer loopback   : None
Path trace buffer : Stable 
  Remote hostname : M0415B
  Remote interface: SRP2/0
  Remote IP addr  : 48.1.1.2
  Remote side id  : A
BER thresholds:           SF = 10e-3  SD = 10e-6
IPS BER thresholds(B3):   SF = 10e-3  SD = 10e-6
TCA thresholds:           B1 = 10e-6  B2 = 10e-6  B3 = 10e-6
Router#
Using the show arp Command

Use the show arp command to verify that the correct Address Resolution Protocol (ARP) table is loaded.
Router# show arp
Protocol  Address          Age (min)  Hardware Addr   Type   Interface
Internet  48.1.1.2              181   0001.6340.9100  SRP-B  SRP1/1
Internet  48.1.1.10               -   0001.64ff.3100  SRP2   SRP1/1
Internet  194.16.3.1             68   0001.64ff.3103  ARPA   FastEthernet2/3
Internet  194.16.2.1              123   0001.64ff.3102  ARPA   FastEthernet2/2
Internet  194.16.1.1              -   0001.64ff.3101  ARPA   FastEthernet2/1
repetitive output removed
Router#
Verifying Clocking

There are two modes of clocking for the SRP interface, LINE and INTERNAL. Clocking works over dark fiber.

•INTERNAL means that the SRP interface uses its internal 20ppm or Stratum-3 clock. LINE means it takes timing from the other side of the line.

•Having both sides with clocking set to INTERNAL is the default configuration and results in normal operation.

•Having both sides with clocking set to LINE is not advised and will result in bit interleaved parity (BIP) errors over time.

•Pairing opposite sides of a connection with one side INTERNAL and one side LINE is acceptable, but not necessary.

Ideal clocking is achieved when all interfaces have the clocking set to INTERNAL. The following example shows this configuration:
router(config)# interface srp 1/1
router(config-if)# srp clock-source internal A
router(config-if)# srp clock-source internal B
PASS-THRU Mode

The SRP line card acts as an optical regenerator when it is operating in PASS-THRU mode. PASS-THRU mode isolates the node. This mode is activated when the interface is placed in shutdown mode, or the node is not receiving layer 2 keepalives on side A or side B.

Use the shutdown interface configuration command to place the router SRP interface in PASS-THRU mode.

PASS-THRU mode is a useful troubleshooting tool for isolating which node on the ring is faulty.
Router# config terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)# interface srp 1/1
Router(config-if)# shutdown
Router(config-if)# end
Router#
23:42:25: %SYS-5-CONFIG_I: Configured from console by console
23:42:27: %LINK-5-CHANGED: Interface SRP1/1, changed state to administratively down
23:42:28: %LINEPROTO-5-UPDOWN: Line protocol on Interface SRP1/1, changed state to down
Verify the PASS-THRU Mode

Use the show srp ips EXEC command to verify that the SRP node is in PASS-THRU mode, which occurs when the interface is administratively down.
Router# show srp ips
SRP1/1 is administratively down
Router#
Using the show srp topology Command

Use the show srp topology EXEC command to verify that the topology packets are being sent and received.
router# show srp topology
Topology Map for Interface SRP1/1
Topology pkt. sent every 5 sec. (next pkt. after 0 sec.)
Last received topology pkt. 00:00:04
Nodes on the ring: 3
Hops (outer ring)      MAC       IP Address     Wrapped Name
      0             0001.64ff.1580 48.1.1.3       No    M0426C
      1             0001.6347.9700 48.1.1.2       No    M0426B
      2             00b0.c280.cf00 48.1.1.1       No    M0426A
By default, the maximum acceptable time for the last topology packet to be received is 5 seconds. If the last received packet value is higher than 5 seconds, topology packets are being lost on the ring.

Using the show srp ips Command

The show srp ips command displays the status of the IPS protocol. It contains information such as the direct neighbors' address, the wrap state, the failures state and the latest transmitted and received IPS packets of the SRP node. It also indicates that the interface is administratively up and not in PASS-THRU mode. (See the "PASS-THRU Mode" section.)
router# show srp ips
IPS Information for Interface SRP1/1
 MAC Addresses
   Side A (Outer ring RX) neighbor 00b0.c280.cf00 
   Side B (Inner ring RX) neighbor 0001.6347.9700 
   Node MAC address 0001.64ff.1580
 IPS State
   Side A not wrapped
   Side B not wrapped
   Side A (Inner ring TX) IPS pkt. sent every 1 sec. (next pkt. after 1 sec.)
   Side B (Outer ring TX) IPS pkt. sent every 1 sec. (next pkt. after 1 sec.)
   inter card bus enabled
   IPS WTR period is 60 sec. (timer is inactive)
   Node IPS State: idle
IPS Self Detected Requests           IPS Remote Requests
   Side A IDLE                          Side A IDLE
   Side B IDLE                          Side B IDLE
 IPS messages received
   Side A (Outer ring RX) {00b0.c280.cf00,IDLE,SHORT}, TTL 128
   Side B (Inner ring RX) {0001.6347.9700,IDLE,SHORT}, TTL 128
 IPS messages transmitted
   Side A (Outer ring RX) {0001.64ff.1580,IDLE,SHORT}, TTL 128
   Side B (Inner ring RX) {0001.64ff.1580,IDLE,SHORT}, TTL 128
Any status other than IDLE, SHORT indicates that errors are present.

If the value "none" is present in IPS packets received, there is a problem on the ring.

Fiber Misconnection

Use the show srp EXEC command to check for misconnected fiber cables, for example, side A to side A or TX to TX. The message, "Misconnection Alarm" shows at the top of the show srp command output when there is a fiber misconnection.

•One alarm—the problem is with another ring on the node. For example, side A connected to side A.

•Two alarms—the problem is your node. For example, side A to side A and side B to side B.

Alarm Messages

The following alarm messages display on the console. The suggested solutions cover the most commonly observed errors.

See the following tables for specific alarms and solutions.

Alarm Messages

The following alarm messages report to the console. See Table 4-1 through Table 4-8 for specific alarms and solutions.

The suggested solutions listed below are to the most commonly observed errors:

•Keepalive Alarm Messages for All Uplink Cards, Table 4-1

•IEEE 802.17 RPR Wrap Messages, Table 4-2

•IEEE 802.17 RPR Unwap Messages, Table 4-3

•Other IEEE 802.17 RPR Alarm Messages, Table 4-6

•SRP Wrap Messages, Table 4-7

•SRP Unwrap Message, Table 4-8

Table 4-1 Keepalive Alarm Messages for All Uplink Cards

Alarm

Description

Solution

SRP1/1 Side A Keepalive Failure (MAC)

MAC failure is detected

Check transport span for problems.

Typically SRP ring traverses a SONET layer connection, creating this error.

SRP1/1 Side A Keepalive Failure (SLOS)

SONET section loss of signal

Check fiber for breaks, power level, and connectivity.

This is a SONET layer 1 issue with fiber.

SRP1/1 Side A Keepalive Failure (SLOF)

SONET section loss of frame

Check the fiber for degradation in (power level) or clocking (internal versus line).

SRP1/1 Side A Keepalive Failure (LSD)

SONET line signal degrade

Check the affected fiber, transmit and receive ports. Check power level.

This is a SONET layer 1 issue with signal degrade.

SRP1/1 Side A Keepalive Failure (LSD)

SONET line signal degrade

Check the neighbor node/transport/regenerator for SONET layer 1 issues (LOS, LSF).

This is a SONET layer 1 issue with an intermediate unit (usually transport connection or regenerator) forwarding an AIS.

SRP1/1 Side A Keepalive OK

Keepalive failure removed; Layer 2 Keepalive receiving correctly

None.

RPR-IEEE1/1 span WEST Keepalive
Failure (MAC)

MAC failure is detected

Check transport span for problems.

Typically RPR ring traverses a SONET layer connection, creating this error.

RPR-IEEE1/1 span WEST Keepalive Failure (SLOS)

SONET section loss of signal

Check fiber for breaks, power level, and
connectivity.

This is a SONET Layer 1 issue with fiber.

RPR-IEEE1/1 span WEST Keepalive
Failure (SLOF)

SONET section loss of frame

Check the fiber for degredation in (power level) or clocking (interval versus line).

RPR-IEEE1/1 span WEST Keepalive
Failure (LSD)

SONET line signal degrade

Check the affected fiber transmit (TX) and receive (RX) ports. Check the power level.

This is a SONET Layer 1 issue with signal degradation.

RPR-IEEE1/1 span WEST Keepalive
Failure (LSF)

SONET line signal failure

Check the neighboring node/transport/regenerator for SONET layer 1 issues (LOS, LSF).

This is a SONET Layer 1 issue with an intermediate unit (usually transport connection or regenerator) forwarding an AIS.

RPR-IEEE1/1 span WEST Keepalive
Failure OK

Keepalive signal removed, Layer 2 Keepalive receiving correctly

None.

Table 4-2 IEEE 802.17 RPR Wrap Messages

Alarm

Description

Solution

RPR-IEEE1/1 wrapped on span East (span WEST User Request Forced Switch)

User initiated forced switch on span WEST on node

User initiated, none.

RPR-IEEE1/1 wrapped on span EAST (span WEST User Request Manual Switch)

User initiated manual switch on span WEST on node

User initiated, none.

RPR-IEEE1/1 wrapped on span EAST (span WEST Self Detect Signal Fail)

SONET Layer 1 signal fail detected

Investigate Keepalive failure. Wrap occurred.

Keepalive failure—SLOS, SLOF, LSF, or LAIS.

RPR-IEEE1/1 wrapped on span EAST (span WEST Span Neighbor Signal Degrade)

SONET Layer 1 signal fail detected

Investigate Keepalive failure. Wrap occurred.

Keepalive failure—LSD.

RPR-IEEE1/1 wrapped on span EAST (span WEST Self Detect Wait to Restore [WTR])

Wrap cleared, node initiated; Wait to Restore (WTR) state

WTR period is 10 to 360 seconds (user configured), node will unwrap at end of WTR. None.

RPR-IEEE1/1 wrapped on span EAST (span WEST Span Neighbor Forced Switch)

Neighbor node Forced Switch initiated by user. Node wrap to protect failed span

User initiated, none.

RPR-IEEE1/1 wrapped on span EAST (span WEST Span Neighbor Manual Switch)

Neighbor node Manual Switch initiated by user. Node wrap

User initiated, none.

RPR-IEEE1/1 wrapped on span EAST (span WEST Span Neighbor Signal Fail)

Neighbor node wrapped due to signal fail

Investigate the signal degrade on neighbor node.

RPR-IEEE1/1 wrapped on span EAST (span WEST Span Neighbor Signal Degrade)

Neighbor node wrapped due to signal degrade

Investigate the signal degrade on neighbor node.

RPR-IEEE1/1 wrapped on span EAST (span WEST Span Neighbor WTR)

Wrap cleared, node initiated; Wait to Restore state

WTR period is 0 to 1440, or never (user configured), node will unwrap at end of WTR. None. Setting WTR to never will prevent the node from unwrapping.

RPR-IEEE1/1 wrapped on span EAST (span WEST Long Request Forced Switch)

Neighbor node Forced Switch initiated by user; Node wrap to protect failed span; Secondary problem on the short path

Investigate why the short path request was not received.

Check other problems on the short span as indicated on the neighbor node.

RPR-IEEE1/1 wrapped on span EAST (span WEST Long Request Manual Switch)

Neighbor node Manual Switch initiated by user; Node wrap to protect failed span; Secondary problem on the short path

Investigate why the short path request was not received.

Check other problems on the short span as indicated on the neighbor node.

RPR-IEEE1/1 wrapped on span EAST (span WEST Long Request Signal Fail)

Neighbor node wrapped due to signal fail

Investigate signal fail on neighbor node.

Investigate why the short path request was not received.

Check other problems on the short span as indicated on the neighbor node.

RPR-IEEE1/1 wrapped on span EAST (span WEST Long Request Signal Degrade)

Neighbor node wrapped due to signal degrade

Investigate signal degrade on neighbor node. Investigate why short path request was not received.

Check other problems on the short span as indicated on the neighbor node.

RPR-IEEE1/1 wrapped on span EAST (span WEST Long Request WTR)

Wrap cleared; Wait to Restore timer expired

None.

Table 4-3 IEEE 802.17 RPR Unwap Messages

Alarm

Description

Solution

RPR-IEEE1/1 unwrapped on span EAST (wrap cause cleared)

Wrap cleared; Wait to Restore timer expired.

None.

Table 4-4 IEEE 802.17 RPR Steer Messages

Alarm

Description

Solution

RPR-IEEE1/1 protected on span East (span WEST User Request Forced Switch)

User initiated forced switch on span WEST on node

User initiated, none.

RPR-IEEE1/1 protected on span EAST (span WEST User Request Manual Switch)

User initiated manual switch on span WEST on node

User initiated, none.

RPR-IEEE1/1 protected on span EAST (span WEST Self Detect Signal Fail)

SONET Layer 1 signal fail detected

Investigate Keepalive failure. Wrap occurred.

Keepalive failure—SLOS, SLOF, LSF, or LAIS.

RPR-IEEE1/1 protected on span EAST (span WEST Span Neighbor Signal Degrade)

SONET Layer 1 signal fail detected

Investigate Keepalive failure. Wrap occurred.

Keepalive failure—LSD.

RPR-IEEE1/1 protected on span EAST (span WEST Self Detect Wait to Restore [WTR])

Wrap cleared, node initiated; Wait to Restore (WTR) state

WTR period is 10 to 360 seconds (user configured), node will unwrap at end of WTR. None.

RPR-IEEE1/1 protected on span EAST (span WEST Span Neighbor Forced Switch)

Neighbor node Forced Switch initiated by user. Node wrap to protect failed span

User initiated, none.

RPR-IEEE1/1 protected on span EAST (span WEST Span Neighbor Manual Switch)

Neighbor node Manual Switch initiated by user. Node wrap

User initiated, none.

RPR-IEEE1/1 protected on span EAST (span WEST Span Neighbor Signal Fail)

Neighbor node protected due to signal fail

Investigate the signal degrade on neighbor node.

RPR-IEEE1/1 protected on span EAST (span WEST Span Neighbor Signal Degrade)

Neighbor node protected due to signal degrade

Investigate the signal degrade on neighbor node.

RPR-IEEE1/1 protected on span EAST (span WEST Span Neighbor WTR)

Wrap cleared, node initiated; Wait to Restore state

WTR period is 0 to 1440, or never (user configured), node will unwrap at end of WTR. None. Setting WTR to never will prevent the node from unwrapping.

RPR-IEEE1/1 protected on span EAST (span WEST Long Request Forced Switch)

Neighbor node Forced Switch initiated by user; Node wrap to protect failed span; Secondary problem on the short path

Investigate why the short path request was not received.

Check other problems on the short span as indicated on the neighbor node.

RPR-IEEE1/1 protected on span EAST (span WEST Long Request Manual Switch)

Neighbor node Manual Switch initiated by user; Node wrap to protect failed span; Secondary problem on the short path

Investigate why the short path request was not received.

Check other problems on the short span as indicated on the neighbor node.

RPR-IEEE1/1 protected on span EAST (span WEST Long Request Signal Fail)

Neighbor node protected due to signal fail

Investigate signal fail on neighbor node.

Investigate why the short path request was not received.

Check other problems on the short span as indicated on the neighbor node.

RPR-IEEE1/1 protected on span EAST (span WEST Long Request Signal Degrade)

Neighbor node protected due to signal degrade

Investigate signal degrade on neighbor node. Investigate why short path request was not received.

Check other problems on the short span as indicated on the neighbor node.

Table 4-5 IEEE 802.17 RPR Un-Steer Messages

Alarm

Description

RPR-IEEE1/1 unprotected on span EAST (protection cause cleared)

Protection cleared; Wait to Restore timer expired.

Table 4-6 Other IEEE 802.17 RPR Alarm Messages

Alarm

Description

Solution

RPR-IEEE1/1 Ringlet1 reserved A0 bandwidth has exceeded line rate

The amount of total A0 bandwidth on Ringlet1 reserved by all nodes on the ring exceeds the line rate

Check current A0 allocations on each station using the show rpr-ieee rate-limit command.

Change the A0 allocation on the ring by using the rpr-ieee tx-traffic reserved CLI command.

RPR-IEEE1/1 Ringtlet0 reserved A0 bandwidth has exceeded line rate

The amount of total A0 bandwidth on Ringlet0 reserved by all nodes on the ring exceeds the line rate

Check current A0 allocation on each station using the show rpr-ieee rate-limit command.

Change the A0 allocation on the ring by using the rpr-ieee tx-traffic reserved CLI command.

RPR-IEEE1/1 MAX Stations Exceeded

Too many stations have been discovered in the topology (maximum number of ring stations is 255)

Execute the show rpr-ieee topology commandto verify stations. Reduce the numer of stations in the ring.

RPR-IEEE1/1 Effective jumbo pref on ring is set for jumbo frames

All stations on the ring now support jumbo frame preference, MTU for the ring has been changed to JUMBO MTU (9100 bytes).

None. Remove jumbo preference on stations to revert to REGULAR MTU (1500 bytes)

RPR-IEEE1/1 Effective jumbo pref on ring is set for regular frame

At least one station on the ring does not support jumbo frame preference, MTU for the ring has been changed to REGULAR MTU (1500 bytes).

None. Configure jumbo preference on all stations to change support to JUMBO MTU (9100 bytes).

RPR-IEEE1/1 Effective protection mode on station is now steering

Protection preference has been changed. Protection mode for this station is now steering.

None.

RPR-IEEE1/1 Effective protection mode on station is now wrapping

Protection preference has been changed. Protection mode for this station is now wrapping.

None.

Configured protection mode is inconsistent with other stations on ring

Not all stations in the ring support the same protection preference (wrapping or steering). This inconsistency will create failures in a protection event.

Change all stations to support the same protection preference, all stations must support wrapping or steering. Use the show rpr-iee topology command to verify protection preference. Use the rpr protection preference wrap or no rpr protection preference wrap configuration command to change the preference.

Table 4-7 SRP Wrap Messages

Alarm

Description

Solution

SRP1/1 wrapped on side B (side A User Request Forced Switch)

User-initiated forced switch on side A on node

User initiated, none.

SRP1/1 wrapped on side B (side A User Request Manual Switch)

User-initiated manual switch on side A on node

User initiated, none.

SRP1/1 wrapped on side B (side A Self Detect Signal Fail)

SONET layer 1 signal fail detected

Investigate Keepalive failure. Wrap occurred.

Keepalive failure—SLOS, SLOF, LSF, or LAIS.

SRP1/1 wrapped on side B (side A Span Neighbor Signal Degrade)

SONET layer 1 signal fail detected

Investigate Keepalive failure. Wrap occurred.

Keepalive failure—LSD.

SRP1/1 wrapped on side B (side A Self Detect Wait to Restore [WTR])

Wrap cleared, node initiated Wait to Restore (WTR) state

WTR period is 10 to 360 seconds (user configured), node will unwrap at end of WTR. None.

SRP1/1 wrapped on side B (side A Span Neighbor Forced Switch)

Neighbor node Forced Switch initiated by user; Node wrap to protect failed span

User initiated, none.

SRP1/1 wrapped on side B (side A Span Neighbor Manual Switch)

Neighbor node Manual Switch initiated by user; Node wrap

User initiated, none.

SRP1/1 wrapped on side B (side A Span Neighbor Signal Fail)

Neighbor node wrapped due to signal fail

Investigate the signal fail on neighbor node.

SRP1/1 wrapped on side B (side A Span Neighbor Signal Degrade)

Neighbor node wrapped due to signal degrade

Investigate the signal degrade on neighbor node.

SRP1/1 wrapped on side B (side A Span Neighbor WTR)

Wrap cleared, node initiated Wait to Restore state

WTR period is 10 to 360 seconds (user configured), node will unwrap at end of WTR. None.

SRP1/1 wrapped on side B (side A Long Request Forced Switch)

Neighbor node Forced Switch initiated by user; Node wrap to protect failed span; Secondary problem on the short path

Investigate why the short path request was not received.

Check other problems on the short span as indicated on the neighbor node.

SRP1/1 wrapped on side B (side A Long Request Manual Switch)

Neighbor node Manual Switch initiated by user; Node wrap to protect failed span; Secondary problem on the short path

Investigate why the short path request was not received.

Check other problems on the short span as indicated on the neighbor node.

SRP1/1 wrapped on side B (side A Long Request Signal Fail)

Neighbor node wrapped due to signal fail

Investigate signal fail on neighbor node. Investigate why the short path request was not received.

Check other problems on the short span as indicated on the neighbor node.

SRP1/1 wrapped on side B (side A Long Request Signal Degrade)

Neighbor node wrapped due to signal degrade

Investigate signal degrade on neighbor node. Investigate why short path request was not received.

Check other problems on the short span as indicated on the neighbor node.

SRP1/1 wrapped on side B (side A Long Request WTR)

Wrap cleared, Wait to Restore timer expired

None.

Table 4-8 SRP Unwrap Message

Alarm

Description

Solution

SRP1/1 unwrapped on side B (side A Wrap cause cleared)

Wrap cleared, Wait to Restore timer expired

None.

Note The solutions provided do not cover all possible problems related to specific alarms.

Basic Troubleshooting Ethernet for the Access Card

This section provides some basic troubleshooting guidelines for Fast Ethernet and Gigabit Ethernet interfaces on the access card. For additional information about troubleshooting Ethernet configurations, refer to the Cisco IOS Software Configuration for the Cisco 10720 Internet Router publication. For additional Cisco Ethernet-related documentation, refer to "Related Documentation" section on page xix.

The following sections present basic troubleshooting tips for hardware and simple software tasks.

•Verifying Interface Configuration

•FastEthernet/GigabitEthernet Is up

•Line Protocol Is up

•Duplex Mode Setting

•Speed Mode

•Output Hang

•CRC Field Counters

•Late Collision

•Carrier Signal

Verifying Interface Configuration

Use the show interfaces FastEthernet slot/port command to verify the configuration of a Fast Ethernet interface.
Router# show interfaces FastEthernet 2/1
FastEthernet2/1 is up, line protocol is up 
  Hardware is Fast Ethernet, address is 0001.64ff.3101 (bia0001.64ff.3101)
  Internet address is 194.16.1.1/24
  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255,  
load 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Auto-duplex, Auto Speed, 100BaseTX/FX
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input never, output 00:00:04, output hang never
  Last clearing of "show interface" counters 00:00:13
  Queueing strategy: PXF First-In-First-Out
  Output queue 0/8192, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     0 packets input, 0 bytes
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 0 multicast
     0 input packets with dribble condition detected
     1 packets output, 64 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out
Router#
Use the show interfaces GigabitEthernet slot/port command to verify the configuration of a Gigabit Ethernet interface.
Router# show interfaces GigabitEthernet 2/1
GigabitEthernet2/1 is up, line protocol is up 
Internet address is 195.16.1.1/16
MTU 9100 bytes, BW 1000000 Kbit, DLY 10 usec, rely 255/255, load 0/255
Encapsulation ARPA, loopback not set
Keepalive not set
Full-duplex mode, link type is autonegotiation, media type is SX
output flow-control is off, input flow-control is off
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:02, output 00:00:00, output hang never
Last clearing of "show interface" counters 03:41:33
Queueing strategy: PXF First-In-First-Out
Output queue 0/8192, 0 drops; input queue 0/75, 0 drops
30 second input rate 0 bits/sec, 0 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
1 packets output, 64 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
Router#
FastEthernet/GigabitEthernet Is up

If the interface is down, check the following conditions:

•The cable is fully connected.

•The cable is bent or damaged. If the cable is bent or damaged, the signal will be degraded.

•A hardware failure has not occurred. Observe the LEDs or use the show commands to determine if a failure has occurred. If the hardware has failed, replace the card or cable.

•If the interface is administratively down, use the no shutdown command to enable the interface.

See the "Verifying Interface Configuration" section for an example output that shows interface status.

Line Protocol Is up

Check to see if the status is line protocol is up, in the first line of the output; see the "Verifying Interface Configuration" section. The status of the interface follows the slot/port configuration:

•The line protocol software processes determine that the line is unusable. Swap the cable.

•Check local or remote interface for misconfiguration.

•Swap interface module when there is a hardware failure.

Duplex Mode Setting

The local interface duplex mode configuration should match the remote interface configuration. See the "Verifying Interface Configuration" section for an example output that shows duplex settings. Confirm that duplex settings are the same on both ends of the connection.

Speed Mode

The local interface speed mode field should match the remote interface configuration. See the "Verifying Interface Configuration" section for an example output that shows speed settings. Speed setting display is shown in the following line:
10/100/auto
Output Hang

The output hang provides the number of hours, minutes, and seconds since the last reset caused by a lengthy transmission. For example, the output hang data is located on line 9 of the show interfaces GigabitEthernet 2/1 router output:
Last input never, output 00:00:04, output hang never
See the "Verifying Interface Configuration" section for a complete example output that shows output hang data.

CRC Field Counters

Excessive noise will cause high CRC errors accompanied by a low number of collisions. Perform the following checks if you encounter high CRC errors:

•Check the cables for damage.

•Verify that the correct cables are being used for the appropriate access card. For cabling specifications, refer to the Cisco 10720 Internet Router Access Card Installation and Configuration publication.

Late Collision

The console will display the following message when late collisions are detected:
Port 2/X - Late collision detected. Possible duplex mismatch.
Late collisions result from either of the following conditions:

•Ethernet cables are too long.

•Duplex mode does not match the remote interface.

For example, the late collisions data is located on line 22 of the show interfaces FastEthernet 2/1 router output:
0 babbles, 0 late collision, 0 deferred
See the "Verifying Interface Configuration" section for a complete example of the output that identifies late collisions.

Carrier Signal

The lost carrier, no carrier numbers track the number of lost carrier detect signals that have occurred.

•If the transmit clock signal is not active, check the interface for malfunction.

•Check for a cable problem.

•Carrier signal resets can occur when an interface is in one of the following states:

–Looped back.

–Shut down.

Cleaning the Fiber-Optic Connections

For information about cleaning fiber-optic cable connectors and receptacles, see the Inspection and Cleaning Procedures for Fiber-Optic Connections document. It provides detailed illustrations and photos of procedures and equipment required to properly clean fiber-optic connections.