Verifying and Troubleshooting Line Card Installation
After installing the hardware, you need to look at the LEDs to verify that the line card was installed correctly. If it was not, you need to troubleshoot to find the problem. The following sections provide information about how to verify and troubleshoot line card installations:
NoteAll new line cards are designated asadministratively down by default. Port Status LEDs are off until you configure the interfaces and use the no shutdown command.
During a typical line card boot process, the following events occur:
1. The line card receives power and begins executing initialization software.
2. The line card performs internal checks, and prepares to accept the Cisco IOS XR software from the RSP.
3. The RSP loads the line card with its Cisco IOS XR software.
To verify that the line card is working properly:
Step 1 Check that the Card Status LED is on (green) to verify that the card is operating normally.
Step 2 Check that the Port Status LED for the port of interest is on (green or blinking) to verify that the port is active. If the Port Status LED is not on, verify that the associated interface is not shut down.
You can use the Card Status LED or the Port Status LEDs on the line card front panels to verify proper operation or troubleshoot a failure (see Table 2-1).
Table 2-1 Port Status and Line Card Status LEDs
Port Status LEDs (one per port)
Port state is up and a valid physical layer link is established.
Line activity is occurring. The LED blinks green-amber-green.
Port state is up, but there is a link loss or SFP/XFP failure.
Port is administratively shut down.
Card Status LED (one per card)
Line card has booted properly, and is ready to pass or is passing traffic.
Line card boot process is underway. When the Cisco IOS XR software finishes loading, the LED turns green.
Software configuration error has occurred that prevents the line card from passing traffic. It is possible that the line card is still passing traffic, but there is some degradation.
Line card has encountered a hardware error, and is not passing traffic.
Line card is powered off. The LED might turn off momentarily when switching between the states described above, although the line card has not powered off.
Modular Port Adapter LEDs
The modular port adapters have two types of LEDs: an A/L LED for each individual port and a STATUS LED for the modular port adapter.
Table 2-2 describes the modular port adapter LEDs.
Table 2-2 Modular Port Adapter LEDs
Port is not enabled.
Port is enabled and the link is up. The MPA A/L LED will blink green when there is traffic activity.
Port is enabled and the link is down.
Modular port adapter power is not enabled.
Modular port adapter is configure as link down.
Modular port adapter power is on and there is activity.
Modular port adapter is ready and operational, there is no activity.
Troubleshooting the Installation
NoteAll new line cards are designated asadministratively down by default. Status LEDs are off until you configure the interfaces and use the no shutdown command.
If the Card Status LED or a Port Status LED does not go on, there is either a problem with the line card installation or a hardware failure. To verify that the line card is installed correctly, follow these steps:
Step 1 If a Port Status LED fails to go on (no activity), but the Card Status LED is on, verify that the initialization sequence has completed successfully. If this is the case, verify that the interface is not shut down. If the interface is not shut down, suspect a circuitry problem with the Port Status LED and contact a service representative for further assistance.
Step 2 If the Card Status LED fails to go on, check the router connections as follows:
a. Verify that the line card board connector is fully seated in the backplane. Loosen the captive installation screws and firmly pivot the ejector levers toward each other until both are parallel to the line card front panel. Tighten the captive installation screws.
b. Verify that all power cords and data cables are firmly connected at both ends.
c. Verify that all components on the card are fully seated and secured to their sockets.
After the line card reinitializes, the Card Status LED on the line card should go on. If the Card Status LED goes on, the installation is complete; if the Card Status LED does not go on, proceed to the next step.
Step 3 If the Card Status LED still fails to go on, remove the line card and try installing it in another available line card slot.
If the Card Status LED goes on when the line card is installed in the new slot, suspect a failed backplane port in the original line card slot.
If the Card Status LED still does not go on, halt the installation. Contact a service representative to report the faulty equipment and obtain further instructions.
Step 4 If an error message displays on the console terminal during the line card initialization, see the appropriate reference publication for error message definitions.
If you experience other problems that you cannot solve, contact a Cisco service representative for assistance.
Note If you perform online insertion or removal of the SFP or XFP module without shutting down the interface, a warning message is displayed on the console device.
Configuring and Troubleshooting Line Card Interfaces
After the person who installed the hardware verifies that the new line card is installed correctly by examining the LEDs, the network administrator can configure the new interface. The following sections provide information on configuring and troubleshooting the line cards:
Table 2-3 lists the default interface configuration parameters that are present when an interface is enabled on a Gigabit Ethernet or 10-Gigabit Ethernet line card. See Cisco IOS XR software documentation for complete information about these parameters.
Table 2-3 Line Card Configuration Default Values
Configuration File Entry
egress on ingress off
1514 bytes for normal frames
1518 bytes for IEEE 802.1Q tagged frames
1522 bytes for Q-in-Q frames
Hardware burned-in address (BIA)
Line Card Interface Address
A Cisco ASR 9000 Series Router identifies an interface address by its rack number, line card slot number, instance number, and port number, in the format rack/ slot /instance/ port . The rack parameter is reserved for multirack systems, so it is always 0 (zero) for the Cisco ASR 9000 Series. The line card slots are numbered from 0 to 7 (Cisco ASR 9010 Router) or 0 to 3 (Cisco ASR 9006 Router).
Instance numbers are reserved for cards that have subslots. This parameter is currently always 0 (zero) for line cards in the Cisco ASR 9000 Series. The ports on the line card are numbered 0, 1, 2, and so on. For example, the rack/ slot /instance/ port address of the fourth port of a line card installed in line card slot 1 is 0/1/0/3. Even if the line card contains only one port, you must use the rack/ slot /instance/ port notation.
Using Configuration Commands
The command line interface (CLI) for Cisco IOS XR software is divided into different command modes. To configure a line card, you enter the correct mode and then enter the commands you need.
When you first log in, you are automatically in EXEC mode. Next, enter the configure command to access configuration mode. Then, enter the interface command to enter interface configuration mode and specify the interface. You are now in the command mode where you can configure the new interface. Be prepared with the information you will need, such as the interface IP address.
Basic Line Card Configuration
The following procedure is for creating a basic configuration—enabling an interface and specifying IP routing. You might also need to enter other configuration subcommands, depending on the requirements for your system configuration.
The following example shows one way to configure the basic parameters of a line card:
Step 1 Enter EXEC mode:
Step 2 Check the status of each port by entering the show interface command:
RP/0/RSP0/CPU0:router# show interface
Step 3Enter global configuration mode and specify that the console terminal will be the source of the configuration commands:
Step 4 At the prompt, specify the new interface to configure by entering the interface command, followed by the type (for example, gigabitethernet or tengige) and rack/ slot /instance/ port (line card rack, slot number, subslot number, port number). Remember that Cisco ASR 9000 Series rack and subslot values are always 0 (zero). For example, to configure port 4 on an 8-Port 10-Gigabit Ethernet line card in line card slot 1:
RP/0/RSP0/CPU0:router# interface tengige 0/1/0/3
You are now in interface configuration mode.
Step 5 Assign an IP address and subnet mask to the interface with the ipv4 address configuration subcommand, as in the following example:
Step 9 When you have included all the configuration subcommands to complete the configuration, enter the commit command to commit all changes you made to the running configuration.
Step 10 Enter Ctrl-Z to exit configuration mode. If you did not enter the commit command, you will be prompted to do so:
Uncommitted changes found, commit them before exiting(yes/no/cancel)? [cancel]:
Answer yes to commit, no to exit without a commit, or cancel to cancel the exit (default).
Step 11 Write the new configuration to memory:
RP/0/RSP0/CPU0:router# copy run disk0:/config/running/alternate_cfg:/router.cfg
Destination file name (control-c to abort): [/router.cfg]?
The destination file already exists. Do you want to overwrite? [no]: yes
223 lines built in 1 second
The system displays an OK message when the configuration has been stored.
Verifying the Transceiver Modules
Use the show inventory all command to display SFP or XFP module information for all transceiver modules currently installed in the router. To display SFP or XFP module information for a particular module, you can use the show inventory location <slot ID> command.
The output of these commands lists such information as the slot ID, transceiver type, description, product ID, version, and serial number.
For example, to list module information for all modules in the router:
NAME: "module 0/0/CPU0", DESCR: "16-Port 10GE DX Medium Queue Line Card, Requires SFPs"
PID: A9K-16T/8-B , VID: V01, SN: FOC135180R6
NAME: "module mau GigabitEthernet0/0/CPU0/5", DESCR: "10GBASE-LR SFP+ Module for SMF"
PID: SFP-10G-LR , VID: N/A, SN: ECL121900JA
NAME: "module mau GigabitEthernet0/0/CPU0/13", DESCR: "10GBASE-LR SFP+ Module for SMF"
PID: SFP-10G-LR , VID: V01 , SN: ECL1338022R
NAME: "module 0/2/CPU0", DESCR: "16-Port 10GE DX Medium Queue Line Card, Requires SFPs"
PID: A9K-16T/8-B , VID: V01, SN: FOC135180R9
NAME: "module mau GigabitEthernet0/2/CPU0/0", DESCR: "10GBASE-LR SFP+ Module for SMF"
PID: SFP-10G-LR , VID: N/A, SN: ECL121900JZ
NAME: "module mau GigabitEthernet0/2/CPU0/1", DESCR: "10GBASE-LR SFP+ Module for SMF"
PID: SFP-10G-LR , VID: N/A, SN: ECL121900JY
NAME: "module mau GigabitEthernet0/2/CPU0/3", DESCR: "10GBASE-LR SFP+ Module for SMF"
PID: SFP-10G-LR , VID: V01 , SN: ONT132600B5
NAME: "module mau GigabitEthernet0/2/CPU0/5", DESCR: "10GBASE-LR SFP+ Module for SMF"
PID: SFP-10G-LR , VID: V01 , SN: ECL132603DM
NAME: "module mau GigabitEthernet0/2/CPU0/7", DESCR: "10GBASE-LR SFP+ Module for SMF"
PID: SFP-10G-LR , VID: N/A, SN: ECL121900JM
NAME: "module mau GigabitEthernet0/2/CPU0/8", DESCR: "10GBASE-LR SFP+ Module for SMF"
PID: SFP-10G-LR , VID: N/A, SN: ECL121900KS
NAME: "module mau GigabitEthernet0/2/CPU0/9", DESCR: "10GBASE-LR SFP+ Module for SMF"
PID: SFP-10G-LR , VID: N/A, SN: ECL121900KN
NAME: "module mau GigabitEthernet0/2/CPU0/10", DESCR: "10GBASE-LR SFP+ Module for SMF"
PID: SFP-10G-LR , VID: N/A, SN: ECL121900JJ
NAME: "module mau GigabitEthernet0/2/CPU0/14", DESCR: "10GBASE-LR SFP+ Module for SMF"
PID: SFP-10G-LR , VID: N/A, SN: ECL121900JR
Advanced Line Card Troubleshooting
This section briefly describes advanced troubleshooting commands that can be used if a line card fails.
NoteThis section assumes that you possess basic proficiency in the use of Cisco IOS XR software commands.
By using the commands listed in this section, you should be able to determine the nature of the problems you are having with your line card. The first step is to identify the cause of the line card failure or console errors that you are seeing.
To discover which card may be at fault, it is essential to collect the output from the following commands:
show diag slot
show context location slot
Along with these show commands, you should also gather the following information:
Console Logs and Syslog Information—This information is crucial if multiple symptoms are occurring. If the router is configured to send logs to a Syslog server, you may see some information on what has occurred. For console logs, it is best to be directly connected to the router on the console port with logging enabled.
Additional Data—The show tech-support command is a compilation of many different commands, including show version, show running-config, show tech ethernet , show tech pfi , and show stacks. This information is required when working on issues with the Cisco Technical Assistance Center (Cisco TAC).
For examples of how to use these commands and the resulting output, see the Cisco ASR 9000 Series Troubleshooting Guide.
NoteIt is important to collect the show tech-support command data before doing a reload or power cycle. Failure to do so can cause all information about the problem to be lost. Output from these commands varies slightly depending on which line card you are using, but the basic information is the same.
Regulatory, Compliance, and Safety Information
This section contains information on laser safety.
For other regulatory, compliance, and safety information, including translated safety warnings, see the Cisco ASR 9000 Series Aggregation Services Router Regulatory Compliance and Safety Information publication.
Single-mode Ethernet line cards (all of the line cards) are equipped with a Class 1 laser. Multimode Ethernet line cards (Gigabit Ethernet) are equipped with a Class 1 LED. These devices emit invisible radiation. Do not stare into operational line card ports. The following laser warnings apply to the line cards: