Chapter 5 Troubleshooting the System Hardware

Identifying System Problems

Note The WAAS software does not support the use of a keyboard or mouse (Personal System/2 [PS/2] or Universal Serial Bus [USB]) for Linux and WAAS software troubleshooting. However, the keyboard and mouse are supported by the BIOS for power-on self-test (POST) and the diagnostic programs that are located in the device ROM.

When console redirection is enabled, all the tests available from a keyboard are accessible through the console connection as well. (Mouse support, however, is not available through the console connection.)

You can run all the diagnostics and tests that are supported by the BIOS, with a few exceptions. Tests for ports (such as the systems-management Ethernet connector and the SAS connector) that are not supported by the WAAS software are invalid.

Identifying System Problems

To identify system problems, follow these steps:

Step 1 Check the front panel LED indicators. (See Table 5-10 on page 5-13.) Step 2 Power down the device and all external devices.

Step 3 Check all cables and power cords. (See the “Checking Connections and Switches” section on page 5-3.)

Step 4 Power up all external devices.

Step 5 Power up the device.

Step 6 Record any POST error messages that are displayed on the screen. If an error is displayed, look up the first error in the “Power-On Self Test (POST)” section on page 5-12.

Step 7 If you hear one or more beeps, find the beep code in the “Interpreting POST Diagnostic Front Panel LEDs and Beep Codes” section on page 5-16. If necessary, see the “Undetermined Problems” section on page 5-6.

 

Cisco Wide Area Virtualization Engine 274 and 474 Hardware Installation Guide

5-2

OL-17739-01

Page 54
Image 54
Cisco Systems 474, 274 manual Identifying System Problems