Filter
Top Products
Chapter 8 Troubleshooting
Troubleshooting Overview
SCE 2000 4xGBE Installation and Configuration Guide
8-2 OL-7824-02
The following table shows the general troubleshooting strategy described in this chapter. Refer to
this table, as necessary, to follow the steps to isolate problems to a specific subsystem and resolve
the problem if possible.
Table 8-1 Troubleshooting Strategy for Startup Problems
Action Yes No
Step 1
Turn power on. Go to Step 2
Step 2
Power A/Power B LEDs on? Go to Step 3 Troubleshoot power system
and go to Step 3.
Step 3
Status LED red (failure) Troubleshoot
software
installation and go
to Step 4.
Go to Step 4
Step 4
Management interface
operational?
Go to Step 5 Troubleshoot management
system and go to Step 4.
Step 5
Link interfaces operational? Go to Step 6 Troubleshoot link interface
system and go to Step 5.
Step 6
System startup successful (all
interfaces operating normally).
⎯ ⎯
Troubleshooting Tools
There are three tools that will help you to successfully troubleshoot your SCE 2000 installation:
• CLI Commands for Troubleshooting (on page 8-2)
• The User Log (on page 8-4)
• Check the LEDs (on page 8-7)
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.