This section explains the various reasons that can cause an ATM Switch Processor (ASP) Status LED to turn red. It also describes the power-on diagnostics (PoD), as well the various
show diag power-on command output fields.
Note: Individual line cards on your ATM switch also use LEDs to indicate status information. A red LED on line cards is not discussed in this document. Please refer to the ATM and Layer 3 Module Installation Guides to troubleshoot a red status LED on a specific line card.
By observing the LEDs of all ports during bootup, you can see that online tests are being conducted one at a time. The ATM Switch Processor (ASP) conducts various diagnostic tests. If an error is detected during the tests, the Status LED turns red. The Status LED usually changes color after bootup.
If the ASP Status LED turned red, then you can use the show diag power-on command to determine the precise reason. The output slightly varies depending on the feature card type.
The test is not performed systematically when the LightStream 1010 is booting. It is done when the box is powered up, but not when it is reloaded afterwards.
Typical Output on the ASP, PCQ (also known as FC1)
You can check the feature card (FC) type by using the
show hardware command as shown below:
LS1010# show hardware
LS1010 named LS1010, Date: 19:00:42 UTC Tue Mar 5 2002
Feature Card's FPGA Download Version: 10
Slot Ctrlr-Type Part No. Rev Ser No Mfg Date RMA No. Hw Vrs Tst EEP
---- ------------ ---------- -- -------- --------- -------- ------- --- ---
1/0 155MM PAM 73-1496-03 06 02180444 Jan 17 96 00-00-00 3.0 0 2
1/1 155MM PAM 73-1496-03 06 02202228 Jan 11 96 00-00-00 3.0 0 2
3/0 CE-T1 PAM 73-2176-02 A0 03669320 Feb 15 97 00-00-00 1.0 0 2
3/1 QUAD DS3 PAM 73-2197-02 A0 03816513 Jan 30 97 00-00-00 2.0 0 2
4/0 4CE1 FR-PAM 73-3040-02 A0 11667127 Feb 20 99 00-00-00 2.0 0 2
4/1 T1 PAM 73-2133-02 00 03669217 Feb 12 97 00-00-00 1.0 0 2
2/0 ATM Swi/Proc 73-1402-06 D0 07202996 Dec 20 97 00-00-00 4.1 0 2
2/1 FeatureCard1 73-1405-05 B0 07202788 Dec 20 97 00-00-00 3.2 0 2
DS1201 Backplane EEPROM:
Model Ver. Serial MAC-Address MAC-Size RMA RMA-Number MFG-Date
----- ---- -------- ------------ -------- --- ---------- -----------
LS1010 2 68018639 003080CE3A00 256 0 0 Sep 16 1999
You can also check the result of the PoD by using the
show diag power-on command:
You can also see that Frame Relay/ATM cards are displayed in a different way, which would also be seen with the PCQ.
Whatever the output type, the main indication is that the PoD passed. If it failed, the ASP Status LED will be red. If you see some recoverable errors during the tests, the tests will perform normally, but a warning will be displayed. For example:
The following tables explain only the fields related to the ports or memory. You can assume that any other test failures involve replacing the ASP. This includes diagnostics under the MMC, FC-PFQ, or feature card.
Performs validation on the files present in the CPU-board-resident flash file system. This includes checking the presence of file system and checksum validation for the bootflash resident files. If it fails, the bootflash is bad. Reformat it using the LS1010 and recopy the files using the copy tftp command.
PCMCIA-Slot[0 or 1]
Same as the bootflash test.
[CPU or Fcard]IDPROM
Performs validation of the CPU/Feature Card IDPROMS. If it fails, you will need to Return Material Authorization (RMA) the ASP.
Performs validation of the NVRAM. If it fails, try to configure the LS1010 using the IOS config mode commands. If it still fails, replace the ASP.
Performs Read/Write test on Static memory, which is 128K in size. If it fails, replace the ASP
Performs Read/Write test on Dynamic memory. Replace DRAM; if it still fails, replace ASP.
PS [1 or 2]
Performs validation on the backplane IDPROM. Replace the chassis.
Card-Specific Fields (FC-specific test skipped)
This test makes sure that the PHY-layer HW resident on the various port adapter module (PAM) cards in the system are accessible. If it fails, replace the PAM.
This test makes sure that the PHY-layer HW resident on the various PAM cards in the system are capable of interrupting the CPU under alarm condition. If it fails, replace the PAM.
Performs sourcing of unicast cells to the port and validates the received cells in loopback mode. If it fails, the connectivity is broken in the cell path. Try replacing the PAM first.
Same as loopback test for multicast cells. In other words, the CPU acts as the root of the point-to-multipoint connection.
The CPU sends a unicast cell to the first port in the list, which in turn multicasts it to the rest of the port and validates the result in loopback mode.
This test ensures the Ethernet port HW resident on the Ethernet controller present on the ASP is accessible. If it fails, the Ethernet controller is probably broken and the ASP needs to be replaced.
Performs Read/Write on the built-in Content Addressable Memory (CAM) on the Ethernet controller. If it fails, the Ethernet controller is probably broken and the ASP needs to be replaced.
Performs loopback test on the Ethernet port. If it fails, the Ethernet controller is probably broken and the ASP needs to be replaced.
Artificially loads the Ethernet port. If it fails, the Ethernet controller is probably broken and the ASP needs to be replaced.
SNAKE Test Failures on FC-PFQ
The SNAKE test sends a cell through all interfaces on the switch. This test ensures that all interfaces and associated fabric interfaces are functional. Cisco bug ID CSCdk54678 resolves a problem that causes the SNAKE test to fail on an LightStream 1010 running Cisco IOS® Software Release 11.3WA4 and using an FC-PFQ.
If you see a failed PoD caused by a PAM (from the
show diag power-on output), you should perform the following steps until the problem is resolved:
Upgrade the Cisco IOS software to a more recent release (version 12.0 or higher) since some bugs have been resolved.
Turn the LightStream 1010 off, re-seat the module, and turn the LightStream 1010 on again because an improperly-inserted PAM can definitely cause the tests to fail.
RMA the PAM.
RMA the ASP.
Finally, here is a typical example of a PoD that fails. It was solved by an RMA of the PAM. Similar issues have been solved by re-seating the PAM.