Table Of Contents
Troubleshooting the Gigabit Ethernet SPA
General Troubleshooting Information
Performing Basic Interface Troubleshooting
Verifying the Line Protocol is Up
Understanding SPA Automatic Recovery
When Automatic Recovery Occurs
Configuring the Interface for Internal Loopback
Configuring the Interface for Internal Loopback
Configuring the Interface for External Loopback
Using the Cisco IOS Event Tracer to Troubleshoot Problems
Preparing for Online Insertion and Removal of a SPA
Troubleshooting the Gigabit Ethernet SPA
This chapter describes techniques that you can use to troubleshoot the operation of your GigabitEthernet SPAs.
It includes the following sections:
•
General Troubleshooting Information
•
•
•
•
•
The first section provides information about basic interface troubleshooting. If you are having a problem with your SPA, use the steps in the "Performing Basic Interface Troubleshooting" section to begin your investigation of a possible interface configuration problem.
To perform more advanced troubleshooting, see the other sections in this chapter.
General Troubleshooting Information
This section describes general information for troubleshooting SIPs and SPAs. It includes the following sections:
Using Debug Commands
Along with the other debug commands supported on the Cisco 12000 Series Router, you can obtain specific debug information for SPAs on the Cisco 12000 Series Router using the debug hw-module subslot privileged exec command.
The debug hw-module subslot command is intended for use by Cisco Systems technical support personnel. For more information about the debug hw-module subslot command, see Chapter 19, "SIP and SPA Command Reference."
Caution
For information about other debug commands supported on the Cisco 12000 Series Router, refer to the Cisco IOS Debug Command Reference and any related feature documents for the applicable Cisco IOS Release.
Using show Commands
There are several show commands that you can use to monitor and troubleshoot the SIPs and SPAs on the Cisco 12000 Series Router. This chapter describes using the show interfaces and show controllers commands to perform troubleshooting of your SPA.
For more information about show commands to verify and monitor SIPs and SPAs, see the following chapters of this guide:
•
•
•
Performing Basic Interface Troubleshooting
You can perform most of the basic interface troubleshooting using the show interfaces gigabitethernet command and examining several areas of the output to determine how the interface is operating.
The following example shows output from the show interfaces gigabitethernet command with some of the significant areas of the output to observe shown in bold:
Router# show interfaces gigabitethernet 3/0/0GigabitEthernet3/0/0 is up, line protocol is upHardware is GigMac 1 Port 10 GigabitEthernet, address is 0008.7db3.8dfe (bia )Internet address is 10.0.0.2/24MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec, rely 255/255, load 1/255Encapsulation ARPA, loopback not setKeepalive set (10 sec)Full Duplex, 10000Mbps, link type is autonegotiation, media type is Toutput flow-control is on, input flow-control is onARP type: ARPA, ARP Timeout 04:00:00Last input 00:00:01, output 00:00:01, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 dropsAvailable Bandwidth 10000000 kilobits/sec30 second input rate 0 bits/sec, 0 packets/sec30 second output rate 0 bits/sec, 0 packets/sec11 packets input, 1154 bytes, 0 no bufferReceived 1 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 watchdog, 0 multicast, 0 pause input67 packets output, 20951 bytes, 0 underruns0 output errors, 0 collisions, 1 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier, 0 pause output0 output buffer failures, 0 output buffers swapped outTo verify that your interface is operating properly, complete the steps in Table 6-1:
For more information about the verification steps in and possible responses to correct detected problems, see the following sections:
•
•
•
•
Verifying the Interface is Up
In the output from the show interfaces gigabitethernet command, verify that the interface is up. If the interface is down, perform the following corrective actions:
•
•
•
•
Verifying the Line Protocol is Up
In the output from the show interfaces gigabitethernet command, verify that the line protocol is up. If the line protocol is down, the line protocol software processes have determined that the line is unusable.
Perform the following corrective actions:
•
•
•
Verifying Output Hang Status
In the output from the show interfaces gigabitethernet command, observe the value of the output hang field.
The output hang provides the number of hours, minutes, and seconds since the last reset caused by a lengthy transmission. When the number of hours the field exceeds 24 hours, the number of days and hours is shown. If the field overflows, asterisks are printed. The field shows a value of never if no output hangs have occurred.
Verifying the CRC Counter
In the output from the show interfaces gigabitethernet command, observe the value of the CRC counter. Excessive noise will cause high CRC errors accompanied by a low number of collisions.
Perform the following corrective actions if you encounter high CRC errors:
•
•
Verifying Late Collisions
In the output from the show interfaces gigabitethernet command, observe the value of the late collision counter.
Perform the following corrective actions if you encounter late collisions on the interface:
•
•
Verifying the Carrier Signal
In the output from the show interfaces gigabitethernet command, observe the value of the carrier signal counters. The lost carrier counter shows the number of times that the carrier was lost during transmission. The no carrier counter shows the number of times that the carrier was not present during transmission.
Carrier signal resets can occur when an interface is in loopback mode or shut down.
Perform the following corrective actions if you observe the carrier signal counter incrementing outside of these conditions:
•
•
Understanding SPA Automatic Recovery
When the Gigabit Ethernet SPAs encounter thresholds for certain types of errors and identifies a fatal error, the SPA initiates an automatic recovery process.
You do not need to take any action unless the error counters reach a certain threshold, and multiple attempts for automatic recovery by the SPA fail.
The GigabitEthernet SPAs might perform automatic recovery for the following types of errors:
•
•
•
•
Note
When Automatic Recovery Occurs
If the SPI4 errors occur more than 25 times within 10 milliseconds, the SPA automatically deactivates and reactivates itself. Error messages are logged on the console indicating the source of the error and the status of the recovery.
If Automatic Recovery Fails
If the SPA attempts automatic recovery more than five times in an hour, then the SPA deactivates itself and remains deactivated.
To troubleshoot automatic recovery failure for a SPA, perform the following steps:
Step 1
Step 2
Step 3
Configuring the Interface for Internal Loopback
Loopback support is useful for testing the interface without connectivity to the network, or for diagnosing equipment malfunctions between the interface and a device. The Gigabit Ethernet SPAs supports both an internal and an external loopback mode. The external loopback mode requires the use of a loopback cable and implements a loopback through the transceiver on the SPA.
You can also configure an internal loopback without the use of a loopback cable that implements a loopback at the PHY device internally on a Gigabit Ethernet interface port, or at the MAC device internally on a Gigabit Ethernet interface port. By default, loopback is disabled.
Configuring the Interface for Internal Loopback
To enable internal loopback at the PHY device for an interface on a SPA, use the following commands beginning in interface configuration mode:
Step 10
Router(config-if)# loopback internal
Enables an interface for internal loopback on the Gigabit Ethernet SPA.
Configuring the Interface for External Loopback
Before beginning external loopback testing, remember that the external loopback mode requires the use of a loopback cable.
To enable external loopback, use the following commands beginning in interface configuration mode:
Router(config-if)# loopback external
Enables an interface for external loopback on the Gigabit Ethernet SPA.
Verifying Loopback Status
To verify whether loopback is enabled on an interface port on a SPA, use the show interfaces gigabitethernet privileged EXEC command and observe the value shown in the "loopback" field.
The following example shows that loopback is disabled for interface port 0 (the first port) on the SPA installed in the top (0) subslot of the SIP that is located in slot 3 of the Cisco 12000 Series Router:
Router# show interfaces gigabitethernet 3/0/0GigabitEthernet3/0/0 is up, line protocol is upHardware is GigMac 1 Port 10 GigabitEthernet, address is 0008.7db3.8dfe (bia )Internet address is 10.0.0.2/24MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec, rely 255/255, load 1/255Encapsulation ARPA,loopback not set...Using the Cisco IOS Event Tracer to Troubleshoot Problems
Note
The Event Tracer feature provides a binary trace facility for troubleshooting Cisco IOS software. This feature gives Cisco service representatives additional insight into the operation of the Cisco IOS software and can be useful in helping to diagnose problems in the unlikely event of an operating system malfunction or, in the case of redundant systems, route processor switchover.
Event tracing works by reading informational messages from specific Cisco IOS software subsystem components that have been preprogrammed to work with event tracing, and by logging messages from those components into system memory. Trace messages stored in memory can be displayed on the screen or saved to a file for later analysis.
The SPAs currently support the "spa" component to trace SPA OIR-related events.
For more information about using the Event Tracer feature, refer to the following URL:
Preparing for Online Insertion and Removal of a SPA
The Cisco 12000 Series Router supports online insertion and removal (OIR) of the SIP, in addition to each of the SPAs. Therefore, you can remove a SIP with its SPAs still intact, or you can remove a SPA independently from the SIP, leaving the SIP installed in the router.
This means that a SIP can remain installed in the router with one SPA remaining active, while you remove another SPA from one of the SIP subslots. If you are not planning to immediately replace a SPA into the SIP, then be sure to install a blank filler plate in the subslot. The SIP should always be fully installed with either functional SPAs or blank filler plates.
