Table of Contents
Advertisement
Identifying Startup Problems
Startup problems are commonly due to the source power or to a poor cable connection.
This section contains a detailed description of the normal startup sequence and describes the steps to take if the system
does not perform that sequence as expected. LEDs indicate all system states in the startup sequence. By checking the state
of the LEDs, you can determine when and where the system failed in the startup sequence. Use the following descriptions
to isolate the problem to a subsystem, and then proceed to the appropriate sections to try to resolve the problem.
When you start up the system by turning on the power supply switch, the following should occur:
You should immediately hear the fans operating.
•
When all LEDs come on to indicate that the system has booted successfully, the initial system banner should be
•
displayed on the console screen. If it is not displayed, see
terminal is set correctly and that it is properly connected to the console port.
If the banner is displayed, but the Status LED is flashing orange, indicating a warning state, check the user log:
•
At the prompt, type: more user log
If any of the following warning messages appear, turn the SCE 2000 platform off and call technical support.
"voltage problem:"
•
"fans problem"
•
"abnormal raise in interior temperature:"
•
If the following warning message appears, delete unneeded files from the disk.
"insufficient disk space:"
•
CLI Commands for Troubleshooting
Use the following commands to provide information to help you troubleshoot installation of your SCE 2000 platform.
Refer to Cisco Service Control Engine (SCE) Software Configuration Guide or the Cisco Service Control Engine (SCE)
CLI Command Reference for more information.
Note
Remember that if the management interface is not operational, you should connect the SCE 2000 platform to a local
console so that you can enter CLI commands for troubleshooting.
•
Troubleshooting firmware package installation:
Boot system <filename> — Specifies and verifies the package file to be installed. Error messages or
•
other output identify problems with the package file.
Following is a sample output from the Boot system command.
SCE 2000(config)#boot system ftp://vk:vk@10.1.1.230/downloads/SENum.pkg.pkg
Verifying package file SENum.pkg.pkg...
Package file verified OK.
Troubleshooting the management subsystem:
•
show interface Mng — Displays IP address and auto-negotiation information for the management interfaces.
•
Following is a sample output from the show interface Mng command.
Connect the Local Console
(on page 15) to verify that the
55
Advertisement
Table of Contents
