8-8
Cisco SCE8000 GBE Installation and Configuration Guide
Chapter 8 Troubleshooting
Problem Solving Using a Subsystems Approach
Troubleshooting the Power Subsystem
In the normally configured Cisco SCE 8000 platform with redundant power supply units, it is unlikely
that the device will not start at all. At startup, verify that both power supply units are operational. If the
Power LED on the front panel remains unlit when the Cisco SCE 8000 platform is powered up, consult
Table 8-5 to help isolate a problem in the power subsystem.
Note If the system powers off because of an environmental shutdown, wait at least 1 minute before manually
rebooting the system, otherwise it pauses indefinitely.
Troubleshooting the Firmware Package Installation
See Table 8-6 to help isolate a problem in the installation of the firmware package.
Problems related to the installation of the firmware package could be any of the following:
• File not found in the expected location.
• Wrong file type.
• Device to which the file is to be extracted is full.
Table 8-5 Troubleshooting the Power Subsystem
Symptom Possible Cause Possible Solution
Power LED on the front
panel and LEDs on the
power supply unit are not lit,
or do not remain lit
continuously.
Power cable not fully seated at system. Turn the power switch to the off position and reseat
the power cable in the system.
— Power cable not fully seated at source. Turn the switch to the off position and reseat the
power cable at the power source.
— Power source is faulty. Turn the switch to the off position, connect the
power cable to another power source, if available,
and turn the switch back on.
— Faulty power cable. Turn the switch to the off position, remove the cable
and replace it.
— Faulty power supply. If the system still fails to come up when the power
supply is connected to a different power source with
a new power cable, the power supply unit is
probably faulty. Contact a service representative.
Table 8-6 Troubleshooting the Firmware Package Installation
Diagnostic Action
Enter these CLI commands:
• configure
• boot system <filename>
Symptom Possible Cause Possible Solution