Troubleshoot Startup Problems

Table Of Contents

Troubleshoot Startup Problems

SCE 2000 Operational Status

Identifying Startup Problems

CLI Commands for Troubleshooting

Troubleshoot Startup Problems

• SCE 2000 Operational Status

• Identifying Startup Problems

• CLI Commands for Troubleshooting

SCE 2000 Operational Status

The following table lists the operational states of the SCE 2000 . The Status LED on the SCE 2000 Front Panel reflects the current SCE 2000 operational status. The operational status can be displayed using CLI command show system operation-status.

Table 9-1 SCE 2000 Operational States

SCE 2000 Operational Status

Description

Status LED State

Booting

Initial state after reset

Orange

Operational

SCE 2000 becomes operational after completing the following process:

•Boot is completed

•Power self-tests are completed without failure

•Platform configuration is applied

Flashing green

Warning

SCE 2000 is fully operational (as above) but one of the following occurred:

•Line ports (GBE ports) to the link are down

•Management port link is down

•Temperature raised above threshold

•Voltage not in required range

•Fans problem

•Power supply problem

•Insufficient space on the disk

Note If the condition that caused the SCE 2000 to be in Warning state is resolved (for example, link is up) the SCE 2000 reverts to Operational state.

Flashing orange

Failure

System is in Failure state after Boot due to one of the following conditions:

•Power on test failure

•Three abnormal reboots in less than 20 minutes

•Platform configured to enter Failure mode consequent to failure-induced reboot (this is configurable using CLI command)

Note Depending on the cause of failure, the management interface and the platform configuration may or may not be active/available.

Red

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 Connect the Local Console to verify that the 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 systemcommand.

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.

Following is a sample output from the show interface Mngcommand.

ip address: 10.1.6.145 subnet mask: 255.255.0.0 Configured speed: auto, configured duplex: auto AutoNegotiation is On, link is Up, actual speed: 100, actual duplex: half
–show ip default-gateway — Displays the IP address of the configured default gateway.

Following is a sample output from the show ip default-gateway command.

Default gateway: 10.1.1.1
–show ip route — Displays the entire routing table and the destination of last resort (default-gateway).

Following is a sample output from the show ip route command.

gateway of last resort is 10.1.1.1
–show access-lists — Shows all access-lists or a specific access list.

Following is a sample output from the show access-lists command.

Standard IP access list 1 Permit 10.1.1.0, wildcard bits 0.0.0.255 deny any
–show telnet — Displays the status of the telnet server daemon ( status) or any active Telnet sessions ( sessions).

Following is a sample output from the show telnet command.

show telnet sessions There is 1 active telnet session: Index | Source ================ 0 | 10.1.1.201 show telnet status Telnet deamon is enabled.
–show line vty timeout — Shows the timeout configured for Telnet sessions.

Following is a sample output from the show line vty timeout command.

Timeout is 30 minutes
•Troubleshooting the link interface subsystem:

–show interface GigabitEthernet 0/# — Displays information for a specific GBE Interface.

Following is a sample output from the show interface command.

ip address: 10.1.6.145 subnet mask: 255.255.0.0 Configured duplex: auto AutoNegotiation is On, link is Up, actual duplex: half
–show interface GigabitEthernet 0/# counters — Displays the values of counters of a GBE interface.

Following is a sample output from the show interface counterscommand.

In total octets: 191520 In good unicast packets: 560 In good multicast packets: 0 In good broadcast packets: 0 In packets discarded: 0 In packets with CRC/Alignment error: 0 In undersized packets: 0 In oversized packets: 0 Out total octets: 0 Out unicast packets: 0 Out non unicast packets: 0 Out packets discarded: 0

Refer to The User Log for an explanation of commands related to the user log.

SCE 2000 Operational Status	Description	Status LED State
Booting	Initial state after reset	Orange
Operational	SCE 2000 becomes operational after completing the following process: •Boot is completed •Power self-tests are completed without failure •Platform configuration is applied	Flashing green
Warning	SCE 2000 is fully operational (as above) but one of the following occurred: •Line ports (GBE ports) to the link are down •Management port link is down •Temperature raised above threshold •Voltage not in required range •Fans problem •Power supply problem •Insufficient space on the disk Note If the condition that caused the SCE 2000 to be in Warning state is resolved (for example, link is up) the SCE 2000 reverts to Operational state.	Flashing orange
Failure	System is in Failure state after Boot due to one of the following conditions: •Power on test failure •Three abnormal reboots in less than 20 minutes •Platform configured to enter Failure mode consequent to failure-induced reboot (this is configurable using CLI command) Note Depending on the cause of failure, the management interface and the platform configuration may or may not be active/available.	Red