The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains general troubleshooting information to help isolate the cause of any difficulties you might encounter during the installation and initial startup of the system.
Although an overtemperature condition is unlikely at initial startup, environmental monitoring functions are included in this chapter because they also monitor internal voltages.
Troubleshooting the installation is presented in the following sections:
•Troubleshooting the Power Subsystem
•Troubleshooting the Processor Subsystem
•Troubleshooting the Cooling Subsystem
This section describes the methods used in troubleshooting the router. The troubleshooting methods are organized according to the major subsystems in the router.
If you are unable to solve a problem on your own, you can contact a Cisco customer service representative for assistance. When you call, have the following information ready:
•Date you received the router and the chassis serial number (located on a label on the back of the chassis).
•Installed line cards.
–Use the show hardware command to determine which line cards are installed if possible.
•Cisco software release number.
–Use the show version command to determine this information if possible.
•Brief description of the symptoms and steps you have taken to isolate and solve the issue.
•Maintenance agreement or warranty information.
To solve a system problem, try to isolate the problem to a specific subsystem. Compare current router behavior with expected router behavior. Because a startup issue is usually attributable to one component, it is most efficient to examine each subsystem, rather than trying to troubleshoot each router component.
For troubleshooting purposes in this chapter, the router consists of the following subsystems:
•Power subsystem—Includes the following components:
–AC-input or DC-input power supplies, also called power entry modules (PEMs). The router chassis is shipped with fully-redundant PEMs installed in the chassis.
•Chassis backplane power distribution. -48 VDC power from the power supplies is transferred to the chassis backplane and is distributed to all of the cards through the backplane connectors. The blower module receives power from the chassis backplane through a wiring harness and passes MBus data back to the chassis backplane.
•Processor subsystem—Includes the RP, up to nine line cards (when no optional, redundant RP is installed), and two alarm cards. The RP and line cards are equipped with onboard processors. The RP downloads a copy of the Cisco software image to each line card processor. The system uses an alphanumeric display (on each line card and RP) t o display status and error messages, which can help in troubleshooting.
•Cooling subsystem—Consists of a blower module, which circulates air through the card cages to cool the cards, and a fan in each of the power modules, which circulates cooling air through the power module.
You can generally determine when and where the router failed during the startup sequence by checking the status LEDs on the power modules, and the alphanumeric displays on the RP and line cards.
In a normal router startup sequence, the following sequence of events and conditions occur:
1. The fans in the blower module receive power and begin drawing air through the chassis.
The blower module OK indicator is on.
2. The fan in each PEM receives power and begins drawing air through the power supply.
The power supply Pwr OK indicator is on.
3. As the power on and boot process progresses for the RP and each installed line card, the status of each card appears on the alphanumeric display on the front panel of the card:
–The upper row of the display is powered by the DC-to-DC converter on the card.
–The lower row of the display is powered by the +5 VDC provided through the backplane.
Table 4-1 shows the contents of the alphanumeric displays on the RP and the line cards, as well as the normal LED states on the alarm card, the power entry modules (AC or DC), and the blower module after a successful system startup.
This section contains information to troubleshoot the power subsystems:
•Troubleshooting the AC-Input Power Subsystem
•Troubleshooting the DC-Input Power Subsystem
•Troubleshooting the Power Distribution System
AC-input power supplies are monitored for internal temperature, voltage, and current load by the MBus module on the alarm cards, and by the master MBus module on the RP. If the router detects an extreme condition, it generates an alarm on the alarm card and logs the appropriate warning messages on the console.
Figure 4-1 identifies the components of an AC PEM.
Figure 4-1 AC PEM Components
|
Status indicators |
|
Ejector lever |
|
Handle |
|
Power On/Off switch (shown in the ON/1 position) |
Use the following procedure to troubleshoot the AC power supply if it is not operating properly.
Step 1 Make sure the power supply is seated properly.
•Eject and reseat the PEM. Check that:
–The captive screw on the ejector lever is tightened securely.
–The power switch is set to the on (1) position.
Step 2 Make sure the router is powered on and that all power cords are connected properly. Check that the:
•Power cords on the horizontal trough on the back of the chassis are secured in place with their retention clips.
•Power cords at the power source end are securely plugged into their own AC power outlet.
•Source AC circuit breaker is switched on.
Step 3 Check the power supply status LED indicators.
•Pwr OK (green)—Indicates that the power supply is operating normally, and both the source AC input voltage of 200 VAC to 240 VAC, and the -48 VDC output voltage to the backplane are within the nominal operating range. This indicator lights when the power switch is set to the on (1) position.
–If the Pwr OK indicator remains off after checking all of the power sources, replace the power supply with a spare.
–If the spare power supply does not work, replace its power distribution unit (PDU).
•Fault (yellow)—Indicates that the system has detected a fault within the power supply. This indicator remains off during normal operation.
If the indicator is on:
–Toggle the power switch off and then on. If the indicator remains on after several attempts to power it on, replace the power supply with a spare.
–If the spare power supply also fails, the problem could be a faulty power shelf backplane connector. Power off the router and contact a Cisco service representative for assistance.
•Temp (yellow)—Indicates that the power supply is in an overtemperature condition, causing a shut-down to occur.
Note If the temp indicator is on, the fault indicator is also on.
–Verify that the power supply fans are operating properly.
–Verify that the blower module is operating properly.
If the power supply fans and the blower module are operating properly, replace the existing power supply with a spare.
•Ilim—Indicates the power supply is operating in a current-limiting condition.
–Make sure that each power cord is connected to a dedicated AC power source.
–Each AC power supply operating in the nominal range of 200 to 240 VAC requires a minimum service of 20 A, North America (or 13 A, international).
Because the AC-input power subsystems use redundant power supplies, a problem with the DC output voltage to the backplane from only one power supply should not affect router operation. When the router is equipped with two AC power supplies, it powers on and operates even if one power supply fails.
DC-input power supplies are monitored for internal temperature, voltage, and current load by the MBus module on the alarm cards, and by the master MBus module on the RP. If the router detects an extreme condition, it generates an alarm on the alarm card and logs the appropriate warning messages on the console.
Figure 4-2 identifies the components of a DC PEM.
Figure 4-2 2800 Watt DC PEM Components
|
Power on/off switch |
|
Handle |
|
Status indicators |
|
Ejector lever |
Use the following procedure to troubleshoot a 2800 W DC PEM if it is not operating properly.
Step 1 Make sure the PEM is seated properly:
•Eject and reseat the PEM. Make sure:
–The captive screw on the ejector lever is tightened securely.
–The power switch is set to the on (1) position.
Step 2 Check the PEM status indicators:
•F1LO (feeder 1 low) (flashing yellow)—Indicates that input connections to the PDU (feeder 1) are loose or not connected, or the input voltage is below the minimum. This indicator remains off during normal operation. Make sure that:
–Power cords are securely attached to their PDU terminal studs.
–Power cords are securely attached at the DC source end.
–The source DC circuit breaker is switched on.
–Measure the voltage across the terminals to verify the source DC voltage is within nominal operating range.
If the indicator is still flashing after you perform the above checks, replace the power supply.
•F2LO (feeder2 low) (flashing yellow)—Indicates that input connections to the PDU (feeder 2) are loose or not connected, or the input voltage is below the minimum. This indicator remains off during normal operation. Make sure that:
–Power cords are securely attached to their PDU terminal studs.
–Power cords are securely attached at the DC source end.
–The source DC circuit breaker is switched on.
–Measure the voltage across the terminals to verify the source DC voltage is within nominal operating range.
If the indicator is still flashing after you perform the above checks, replace the power supply.
•RPF1 (reverse polarity feeder 1) (flashing yellow)—The (feeder 1) PDU is miswired. For wiring instructions see the "Connecting Power to a DC-Powered Router" section on page 3-46. This indicator remains off during normal operation.
•RPF2 (reverse polarity feeder 2) (flashing yellow)—The (feeder 2) PDU is mis-wired For wiring instructions see the "Connecting Power to a DC-Powered Router" section on page 3-46. This indicator remains off during normal operation.
•FAIL (red)—Lights in conjunction with the following indicators (which flash) to show the type of power supply failure:
–F1LO (Feeder 1 Low)
–F2LO (Feeder 2 Low)
–OC (Over Current)
–OT (Over Temperature)
•OC (over current) (flashing red)—Indicates the input or output current has exceeded its limit and that an overload or short has occurred.
–Set the power supply switch to off (0) and then back to the on (1) position.
–If the indicator is still flashing, eject and reseat the power supply.
–If the indicator is still flashing, replace the power supply.
•OT (over temperature) (steady or flashing red)—Indicates that the power supply is in an overtemperature condition, causing a shut-down to occur.
–Flashing red indicates a locked power supply fan. Replace the power supply.
–Steady red indicates a true overtemperature condition. Make sure that all blower module fans are operating properly.
Replace the power supply if the blower module is operating properly.
Replace the blower module if one or more of the blower module fans are not working.
•INOK (green)—Indicates that the power supply is operating normally, and the source DC voltage is within the nominal operating range of -48 to -60 VDC. This indicator lights when the power switch is set to the on (1) position.
–If the INOK indicator is off, replace the power supply.
•DCOK (green)—Indicates that the power supply is operating normally, and is within the nominal operating range. This indicator lights a few seconds after the INOK indicator lights.
–If the DCOK indicator is off, replace the power supply.
Because there are redundant power supplies, a problem with the DC output voltage to the backplane from only one PEM should not affect router operation. When the router is equipped with two DC power supplies, it powers on and operates even if one power supply fails.
This section contains additional troubleshooting information to help you isolate the cause of a power problem.
The MBus modules powering the alphanumeric displays on the RP and line cards are powered by +5 VDC from the backplane. The blower modules use -48 VDC from the backplane. If both the RP and the blower modules are operating, all internal correct DC voltages are present.
Enter the show environment command at the user EXEC mode prompt to display temperature and voltage information for each installed card, blower module, and PEM as shown in this example:
router#show environment
Slot # Hot Sensor Inlet Sensor
(deg C) (deg C)
1 38.0 32.5
3 36.5 39.0
5 37.0 37.0
7 36.0 32.0
16 26.0 26.0
17 27.5 27.5
18 27.0 27.5
19 0.0 0.0
20 27.0 27.5
21 28.0 28.0
22 28.0 28.0
24 47.0 NA
29 NA 22.0
Slot # PEM Over Temperature Sensors
24 PEM1 OK
PEM2 OK
Slot # Hot Sensor Inlet Sensor
(deg C) (deg C)
29 NA 22.0
Slot # 3V 5V MBUS 5V
(mv) (mv) (mv)
1 3296 5016 5048
3 3284 4976 5000
5 3308 5008 5048
7 3296 5016 5000
16 3300 NA 5064
17 3308 NA 5064
18 3292 NA 5056
19 3300 NA 5072
20 3288 NA 5056
21 3296 NA 5072
22 3292 NA 5064
24 NA NA 5096
29 NA NA 4920
Slot # 48V AMP_48
(Volt) (Amp)
24 PEM1 56 2
PEM2 55 2
Slot # Fan 0 Fan 1 Fan 2
(RPM) (RPM) (RPM)
29 3021 3090 2997
The power distribution system consists of:
•AC or DC PEMs which supply -48 VDC to the backplane,
•The chassis backplane which carries voltage to chassis components.
•DC-to-DC converters which convert -48 VDC from the backplane to the correct voltages required by the line cards.
Use the following procedure to troubleshoot the power distribution system.
Step 1 Check each power supply to make sure that:
•The ejector lever is fully closed and properly secured by the its captive screw.
•The Pwr OK indicator is on.
•The Fault and Temp indicators are both off.
If the power supplies meet the above criteria, then the correct source power is present and within tolerance. The power supplies are functioning properly.
Step 2 Make sure the blower module is operating.
•If the blower module is functioning, then the -48 VDC from the chassis backplane and the cables from the backplane to the blower module are functioning properly.
•If the blower module is not functioning, there may be a problem with either the blower module itself, or the -48 VDC power supplied to the blower module. Eject and reseat the blower module.
•If the blower module is still not operating there could be a problem with the blower module controller card or cable. Replace the blower module.
•Contact your Cisco representative if replacing the blower module does not fix the problem.
The router processor subsystem consists of the route processor, line cards, and alarm cards. The RP and the line cards have two onboard processors; one serves as the main (or master) processor, and the other serves as the MBus module processor. The MBus module processor monitors the environment and controls the onboard DC-to-DC converters.
Note A minimally configured router must have an RP installed in slot 9 of the card cage to operate. If the router is equipped with a redundant RP, the redundant RP must be installed in slot 8 of the card cage.
This section contains information to troubleshoot the processor subsystem, including:
•Performance Route Processor Overview
•Troubleshooting the Route Processor
•Troubleshooting Using the Alarm Display
The performance route processor (PRP) uses a Motorola PowerPC 7450 CPU that runs at an external bus clock speed of 133 MHz and has an internal clock speed of 667 MHz.
Figure 4-3 identifies the slots, ports, and LEDs on the PRP front panel.
Figure 4-3 Performance Route Processor Front Panel
Figure 4-4 Performance Route Processor 3 (PRP-3) Front Panel
Table 4-2 PRP-3 Front Panel Hardware Components
|
|
---|---|
1 |
Ejecter Lever |
2 |
Handle |
3 |
External Compact Flash |
4 |
Reset button |
5 |
Alphanumeric LEDs |
Detail
PRP-3 is the route processor for the Cisco XR 12404 and 12804 Router chassis running Cisco IOS XR Software Release 3.8.0 or a later release. The PRP-3 is available as product number PRP-3 or PRP-3= for a primary route processor and is available as PRP-3/R for a redundant route processor. PRP-3 has significant improvements over PRP-2. These improvements include increased speed, improved scalability, higher system memory, faster packet processing. Because PRP-3 does not support Cisco IOS, the bootflash memory no longer exists in PRP-3. PRP-3 ROMMON has software intelligence to download a Cisco IOS XR image without the support of bootflash memory.
Note PRP-3 supports Cisco XR 12410 (10 G per slot fabric) and Cisco XR 12810 (40 G per slot fabric) Router chassis only. PRP-3 does not support Cisco XR 12004, 12006, 12010, and 12016 Router chassis (2.5 G low-speed fabric).
Two PCMCIA card slots (slot 0 and slot 1) provide the PRP with additional flash memory capacity. All combinations of different flash devices are supported by the PRP. You can use ATA flash disks, Type 1 or Type 2 linear flash memory cards, or a combination of the two.
Note The PRP only supports +5.2 VDC flash memory devices. It does not support +3.3 VDC PCMCIA devices.
Status LEDs (Slot-0/Slot-1) indicate when the flash memory card in that slot is accessed (see Figure 4-3). Each slot has an eject button (located behind the cover) to remove a flash card from the slot.
The PRP has two 8-pin media-dependent interface (MDI) RJ-45 ports for either IEEE 802.3 10BASE-T (10 Mbps) or IEEE 802.3u 100BASE-TX (100 Mbps) Ethernet connections. These ports are labeled ETH 0 and ETH 1.
The transmission speed of the Ethernet port is not user-configurable. You set the speed through an autosensing scheme on the PRP which is determined by the network that the Ethernet port is connected to. However, even at an autosensed data transmission rate of 100 Mbps, the Ethernet port can only provide a usable bandwidth of substantially less than 100 Mbps. You can expect a maximum usable bandwidth of approximately 20 Mbps when using an Ethernet connection.
The following LEDs on the front panel indicate traffic status and port selection (Figure 4-5):
•LINK, EN, TX, RX—Indicate link activity (LINK), port enabled (EN), data transmission (TX), and data reception (RX).
•PRIMARY—Indicates which Ethernet port is selected (ETH 0 or ETH 1).
Note Because both ports are supported on the PRP, ETH 0 is always on. ETH 1 lights when it is selected.
Figure 4-5 Port Activity LEDs—Partial Front Panel
LINK |
Indicates link activity |
---|---|
EN |
Indicates the port is enabled |
TX |
Indicates data transmission |
RX |
Indicates data reception |
Figure 4-6 PRP-3 LEDs
The auxiliary and console ports on the PRP are EIA/TIA-232 (also known as RS-232) asynchronous serial ports connect external devices to monitor and manage the system.
•Auxiliary port—A (male) plug that provides a data terminal equipment (DTE) interface. The auxiliary port supports flow control and is often used to connect a modem, a channel service unit (CSU), or other optional equipment for Telnet management.
•Console port—A (female) receptacle that provides a data circuit-terminating equipment (DCE) interface for connecting a console terminal.
Access to the (soft) reset switch is through a small opening in the PRP front panel (see Figure 4-3). To press the switch, insert a paper clip or similar small pointed object into the opening.
Pressing the reset switch causes a non-maskable interrupt (NMI) and places the PRP in ROM monitor mode. When the PRP enters ROM monitor mode, its behavior depends on the setting of the PRP software configuration register. For example, if the boot field of the software configuration register is set to:
•0x0—The PRP remains at the ROM monitor prompt (rommon>) and waits for a user command to boot the system manually.
•0x1—The system automatically boots the first Cisco IOS XR image found in flash memory on the PRP.
The alphanumeric message displays are organized in two rows of four LED characters each (Figure 4-7).
Figure 4-7 Alphanumeric Message Displays—Partial Front Panel
The alphanumeric message displays show router status messages during the boot process, and after the boot process is complete.
•During the boot process, the message displays are controlled directly by the MBus module.
•After the boot process, the message displays are controlled by Cisco IOS XR software (through the MBus).
The alphanumeric message displays also provide information about different levels of system operation, including the status of the PRP, router error messages, and user-defined status and error messages
Note A list of all system and error messages appears in the Cisco IOS XR System Error Messages publication.
When the router is powered on, the alphanumeric display on the RP indicate the following (Figure 4-8):
•Upper row—Indicates which RP software component is running. At the end of a successful boot process, this display reads MSTR.
•Lower row—Indicates the current phase of the boot process. At the end of a successful boot process, this display reads PRP.
Figure 4-8 RP Alphanumeric Display
You can use the alphanumeric display to isolate a problem with the RP. The two rows on the alphanumeric display are powered separately:
•The upper row receives power from the DC-to-DC converters on the RP.
•The lower row is powered directly from the MBus on the RP through the chassis backplane.
–If the lower row is not operating, the MBus module may be malfunctioning.
–If the MBus module is operating, the lower row could be on even if the RP failed to powered on.
•If neither the upper nor the lower row is on, but the power modules and the blower modules are operational, the RP may not be installed properly, or the +5 VDC output from the chassis backplane is faulty.
–Make sure that the system is powered on.
–Initialize the RP by ejecting it from the chassis backplane and then reseating it.
•If both the upper and the lower displays are operating, check the meaning of the messages (see Table 4-3).
When the DC-to-DC converters are powered-on by the MBus module, the RP processor begins the boot process and displays various status messages. Some messages appear briefly; while others appear for several seconds. If the messages appear to stop at a particular point, the boot process may be halted.
–Make a note of the message.
–Turn off power to the router, then turn on the power again to reset the router and start the boot process. If the router halts again, replace the RP (see "Removing and Replacing Cards from the Line Card and RP Card Cage" section on page 5-38).
The following section discusses the alphanumeric LED messages and the console output displayed in sequence for a single PRP-3 and for dual PRP-3. The alphanumeric LED messages help in identifying the state of the route processor and accordingly troubleshooting the problems faced.
Table 4-4 displays the alphanumeric LED messages and the console output when the chassis is powered on or when the PRP-3 board is inserted into the slot.
Table 4-4 Single
PRP-3 Alphanumeric Display LED—Chassis Is Powered ON/Inserting PRP-3
Table 4-5 displays the alphanumeric LED messages and the console output when the chassis is loaded from ROMMON.
Table 4-5 Single PRP-3 Scenario — Chassis loaded from ROMMON
If dual PRP-3 is installed and the chassis is powered on or a board is inserted, all the LED messages are same as for a single PRP-3, except for an LED message `1404/MRAM' that is displayed on the front panel when the console display is as follows:
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
Cisco IOS XR Software for the Cisco XR PRP, Version 3.8.0.15I
Copyright (c) 2008 by Cisco Systems, Inc.
RP/0/2/CPU0:Sep 10 16:34:19.351: syslogd_helper: [84]: dsc_event_handler: Got SysMgr dSC event : 1
Tip The LED message "I404/MRAM" is displayed between RDY/RP and RUN/IOX alphanumeric messages.
Table 4-6 displays the LED alphanumeric messages on a standby PRP-3, if the current active PRP-3 is reloaded.
Table 4-6 Dual PRP-3 Scenario
When the line card is powered on, the display on the line card indicates the following (Figure 4-9):
•Upper row—Indicates which software component is running. At the end of a successful boot process, this display reads IOS XR.
•Lower row—Indicates the current phase of the boot process. At the end of a successful boot process, this display reads RUN.
Figure 4-9 Line Card Alphanumeric Display
You can analyze the alphanumeric displays to isolate a problem with the line card. The two rows of the alphanumeric display are powered separately:
•The upper row receives power from the DC-to-DC converters on the line card.
•The lower row is powered directly from the MBus on the line card through the chassis backplane.
–If the lower row is not operating the MBus module may be malfunctioning.
–If the MBus module is operating, the lower row could be on even if the RP failed to powered on.
•If neither the upper or lower row is on, but the power modules and the blower modules are operational, the line card may not be installed properly, or the +5 VDC output from the chassis backplane is faulty.
–Make sure that the system is powered on.
–Initialize the line card by ejecting it from the chassis backplane and then reseating it.
•If both the upper and lower rows are operating, check the status messages (see Table 4-7).
When the DC-to-DC converters are powered-on by the MBus module, the line card processor begins the boot process and displays various status messages. Some messages appear briefly; while others appear for several seconds.
|
|
|
---|---|---|
MROM |
MBus microcode executing; where nnnn is the microcode version number. |
MBus controller |
LMEM |
Low memory on the line card is being tested. |
Line card ROM monitor |
LROM |
Low memory test is complete. |
Line card ROM monitor |
BSS |
Main memory is being initialized. |
Line card ROM monitor |
RST |
Contents of the reset reason register are being saved. |
Line card ROM monitor |
IO |
Reset I/O register is being accessed. |
Line card ROM monitor |
EXPT |
Interrupt handlers are being initialized. |
Line card ROM monitor |
TLB |
TLB is being initialized. |
Line card ROM monitor |
CACH |
CPU data and instruction cache is being initialized. |
Line card ROM monitor |
MEM |
Size of the main memory on the line card is being discovered. |
Line card ROM monitor |
LROM |
ROM is ready for a software download attempt. |
Line card ROM monitor |
ROMI |
ROM image is being loaded into line card memory. |
RP IOS XR software |
ROM |
ROM image is receiving a response. |
RP IOS XR software |
FABI |
Line card is waiting for the fabric downloader.2 |
RP IOS XR software |
FABM |
Line card is waiting for the Fabric Manager to report that the fabric is usable. |
RP IOS XR software |
FABL |
Fabric downloader is being loaded into line card memory. |
RP IOS XR software |
FABL |
Fabric downloader is being launched. |
RP IOS XR software |
FABL |
Fabric downloader is launched and running. |
RP IOS XR software |
IOS XR |
Cisco IOS XR software is being downloaded into line card memory. |
RP IOS XR software |
IOS XR |
Cisco IOS XR software is waiting for the fabric to be ready. |
RP IOS XR software |
IOS XR |
Line card is obtaining the Cisco IOS XR release. |
RP IOS XR software |
IOS XR |
Line card is enabled and ready for use. |
RP IOS XR software |
IOS XR |
Cisco IOS XR software is being launched. |
RP IOS XR software |
IOS XR |
Cisco IOS XR software is transitioning to active. |
RP IOS XR software |
IOS XR |
Cisco IOS XR software is running. |
RP IOS XR software |
1 The LED initialization sequence shown in Table 4-7 may occur too quickly for you to read; therefore, the sequence is provided in this tabular form as a baseline for how a line card should function at startup. 2 The fabric downloader loads the Cisco IOS XR software image onto the line card. 3 This LED sequence only appears in Cisco IOS XR OL-17441-01 or later. |
|
|
|
---|---|---|
MAL |
Line card malfunction reported by field diagnostics. |
RP |
MISM |
Line card type mismatch in paired slots. |
RP |
PWR |
Line card is newly powered on. |
RP |
PWR |
Line card is powered on. |
RP |
IN |
System is resetting. |
RP |
RSET |
System reset complete. |
RP |
MBUS |
MBus agent is downloading. |
RP |
MBUS |
MBus agent download complete. |
RP |
ROMI |
Acquisition of ROM image complete. |
RP |
MSTR |
Waiting for mastership determination. |
RP |
CLOK |
Waiting for slot clock configuration. |
RP |
CLOK |
Slot clock configuration complete. |
RP |
FABL |
Load of fabric downloader2 complete. |
RP |
IOS XR |
Downloading of Cisco IOS XR software is complete. |
RP |
BMA |
Cisco IOS XR software BMA error. |
RP |
FIA |
Cisco IOS XR fabric interface ASIC configuration error. |
RP |
CARV |
Buffer carving failure. |
RP |
DUMP |
Line card requesting a core dump. |
RP |
DUMP |
Line card dumping core. |
RP |
DUMP |
Line card core dump complete. |
RP |
DIAG |
Diagnostic mode. |
RP |
DIAG |
Downloading field diagnostics over the MBus. |
RP |
DIAG |
Downloading field diagnostics over the fabric. |
RP |
DIAG |
Launching field diagnostics. |
RP |
DIAG |
Cancel field diagnostics. |
RP |
DIAG |
Running field diagnostics tests. |
RP |
DIAG |
Field diagnostics completed successfully. |
RP |
POST |
Launching power-on self-test (POST). |
RP |
UNKN |
Unknown state. |
RP |
ADMN |
Line card is administratively down. |
RP |
SCFG |
Incorrect hw-module slot srp command entered. |
RP |
SCFG1 |
Required hw-module slot srp command not entered. |
RP |
1 This LED sequence only appears in Cisco IOS XR OL-17441-01 or later. 2 The fabric downloader loads the Cisco IOS XR software image onto the line card. |
If you experience critical, major, or minor alarms you can use the alarm display to troubleshoot those conditions. The following connectors and indicators are on the front panel of the alarm display (Figure 4-10):
•Cable connections for the two alarm cards (labeled Alarm A and Alarm B).
•Critical (red), Major (red), and Minor (yellow) indicators that identify system level alarm conditions detected by the system through the MBus. These indicators are normally off.
•Alarm card indicators (labeled MBus) that correspond to alarm cards connected to Alarm A and Alarm B:
1. ENABLED (green)—Alarm card is operational and functioning properly.
2. FAIL (yellow)—Alarm card in that slot is faulty.
•Two status LEDs that correspond to each of the CFC and SFC card slots in the switch fabric and alarm card cage:
–ENABLED (green)
On—The card installed in that slot is operational and functioning properly.
Off—Either the slot is empty or the card installed in that slot is faulty.
–FAIL (yellow)—The card in that slot is faulty.
Figure 4-10 Status LEDs on the Alarm Display
The alarms can warn of an overtemperature condition:
•On a component in the card cage
•A fan failure in a blower module
•An overcurrent condition in a power supply
•An out-of-tolerance voltage on one of the cards
The alarm LEDs are controlled by MBus software, which sets the threshold levels for triggering the different stages of alarms.
The RP continuously polls the system for temperature, voltage, current, and fan speed values. If a threshold value is exceeded, the RP sets the appropriate alarm severity level on the alarm card which lights the corresponding LED, and energizes the appropriate alarm display relays to activate any external audible or visual alarms wired to the alarm display. The RP also logs a message about the threshold violation on the system console.
Note If one or more of the alarm LEDs is on, check the system console for messages describing the alarm.
You may need to troubleshoot the cooling subsystem if an overtemperature condition occurs. The cooling subsystem of the router consists of a blower module in the chassis and a fan in each of the power supplies. The blower module and the power supply fans circulate air to maintain acceptable operating temperatures within the router (Figure 4-11).
This section contains information to troubleshooting the cooling subsystem and includes:
•Isolating Cooling Subsystem Problems
Figure 4-11 Cooling Air Flow
The blower module maintains acceptable operating temperatures for the internal components by drawing cooling air through a replaceable air filter into the switch fabric and alarm card cage, and then through the line card and RP card cage (see Figure 4-11). The blower module occupies a bay at the top of the router and receives power from the chassis backplane through a wiring harness.
The blower module contains three fans, a controller card, and two front panel status LEDs. A snap-on plastic front cover fits over the front panel, but the LEDs are visible through the front covers.
–Green—The blower module is functioning properly.
–Red—There is a fault detected in the blower module.
•If the air temperature inside the chassis rises, blower speed increases to provide additional cooling air to the internal components.
•If the internal air temperature continues to rise beyond the specified threshold, the system environmental monitor shuts down all internal power to prevent equipment damage due to excessive heat.
•If the system detects that one or more of the fans in the blower module has failed, it displays a warning message on the system console and displays a blower failure message on the RP alphanumeric display. In addition, the remaining fans go to full speed to compensate for the loss of the failed fan.
Each AC or DC power supply is equipped with a fan that draws cooler air in through the front of the power module and forces warmer out the back of the power shelf.
•If the power source is within the required range, the power supply fan remains on.
•If the fan fails:
–Power supply detects an internal overtemperature condition
–Fault and Temp indicators light
–Power supply sends an overtemperature warning to the system and then shuts down the system.
For additional power supply troubleshooting information, see the "Troubleshooting the Power Subsystem" section
The following console error message indicates that the system has detected an overtemperature condition or out-of-tolerance power value inside the system:
Queued messages:
%ENVM-1-SHUTDOWN: Environmental Monitor initiated shutdown
The preceding message could also indicate a faulty component or temperature sensor. Enter the show environment command or the show environment all command at the user EXEC prompt to display information about the internal system environment. The information generated by these commands include:
•Voltage measurements on each card from the DC-to-DC converter
•The +5 VDC for the MBus module
•The operating voltage for the blower module.
•Temperature measurements received by two sensors on each card (one for inlet air temperature and one for the card's hot-spot temperature), as well as temperature measurements from sensors located in each power supply.
If an environmental shutdown results from an overtemperature or out-of-tolerance condition, the Fault indicator on the power supply lights before the system shuts down.
Although an overtemperature condition is unlikely at initial system startup, make sure that:
•Heated exhaust air from other equipment in the immediate environment is not entering the chassis card cage vents.
•You allow sufficient air flow by maintaining a minimum of 6 inches (15.24 cm) of clearance at both the inlet and exhaust openings on the chassis and the power modules to allow cool air to enter freely and hot air to be expelled from the chassis.
Use the following procedure to isolate a problem with the chassis cooling system if you have an overtemperature condition.
Step 1 Make sure the blower module is operating properly when you power on the system.
•To determine if a blower module is operating, check the two LED indicators on the blower module front panel:
–OK (green)—The blower module is functioning properly and receiving -48 VDC power, indicating that the cables from the chassis backplane to the blower module are good.
–Fail (red)—A fault is detected in the blower module. Replace the blower module.
–If neither indicator is on and the blower is not operating, there may be a problem with either the blower module or the -48 VDC power supplied to the blower module. Go to Step 2.
Step 2 Eject and reseat the blower module making sure the captive screws are securely tightened.
If the blower module still does not function, go to Step 3.
Step 3 Check for -48 VDC power by looking at the LED indicators on each power supply:
•If the Pwr OK indicator is on and the Fault indicator is off on each power supply, it indicates that the blower is receiving -48 VDC.
–If the blower module is still not functioning, there could be a problem with the blower module controller card or an undetected problem in the blower module cable. Replace the blower module.
–If the new blower module does not function, contact a Cisco customer service representative for assistance.
•If the Fault indicator is on, the power supply is faulty. Replace the power supply.
•If the Temp and Fault indicators are on, an overtemperature condition exists.
–Verify that the power supply fan is operating properly.
–If the fan is not operating, replace the power supply.
Contact your Cisco representative if replacing the power supply does not fix the problem.