Use the information in this chapter to determine whether a problem originates with the hardware or the software. For further assistance, contact your service representative.

Note Cisco ACNS software does not support the use of a keyboard or mouse (Personal System/2 [PS/2] or Universal Serial Bus [USB]) for Linux and ACNS software troubleshooting. However, the keyboard and mouse are supported by the BIOS for power-on self-test (POST) and 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 a disk drive, for example, are invalid because the device does not include a disk drive in the hardware configuration.

Tests for peripheral devices (such as mouse, keyboard, and monitor) and ports (such as the USB port) that are not supported by ACNS software are also invalid.

Caution Customer-replaceable components include the Fibre Channel adapter and hard disk drives. All other components that are not orderable as spare hardware options can only be replaced by a qualified service technician. Once you have identified a faulty component, contact Cisco Technical Support. (See the
"Obtaining Documentation" section.)

Checking Connections and Switches

Improperly set switches and controls and loose or improperly connected cables are the most likely source of problems for the chassis or other external equipment. A quick check of all the switches, controls, and cable connections can easily solve these problems. (See Figure 1-2 for the location of front panel controls and indicators. See Figure 1-3 for the location of back panel connectors on the system.)

To check all the connections and switches, follow these steps:

Step 1 Power down the system, including any attached peripherals such as external drives. Disconnect all the power cables from their electrical outlets.

Step 2 If the system is connected to a power strip (or power distribution unit), turn the power strip off and then on again.

Using the System Diagnostic Programs

The device diagnostic programs are stored in upgradable read-only memory (ROM) on the system board. These programs are the primary method of testing the following major components of the device: the system board, Ethernet controller, RAM, serial ports, and hard disk drives. You can also use the diagnostic programs to test some external devices. See the "Diagnostic Programs and Error Messages" section.

If you cannot determine whether a problem is caused by the hardware or by the software, you can run the diagnostic programs to confirm that the hardware is working properly.

When you run the diagnostic programs, a single problem might cause several error messages. When this occurs, work to correct the cause of the first error message. After the cause of the first error message is corrected, the other error messages might not occur the next time you run the test.

When troubleshooting, note the following points:

•If multiple error codes are displayed, diagnose the first error code that is displayed.

Your device has LEDs to help you identify problems with device components. These LEDs are part of the Light Path Diagnostics that are built into your device. By following the path of LEDs, you can quickly identify the type of system error that occurred. See the "Using Light Path Diagnostics" section for more information.

•Error symptom charts

These charts list problem symptoms, along with suggested steps to correct the problems. See the "Error Symptoms" section for more information.

POST

When you power up the device, it performs a series of tests to check the operation of device components and some of the hardware options installed in the device. This series of tests is called the power-on self-test, or POST.

If POST finishes without detecting any problems, a single beep sounds, and the first screen of your operating system or application program appears.

Note If you have a power-up password or administrator password set, you must enter the password and press Enter when prompted, before POST will continue.

Note A single problem might cause several error messages. When this occurs, work to correct the cause of the first error message. After you correct the cause of the first error message, the other error messages usually will not occur the next time that you run the test.

The POST error log contains the three most recent error codes and messages that the system generated during POST. The system error log contains all messages issued during POST and all system status messages from the service processor.

You can view the contents of the system error log from the diagnostic programs.

Diagnostic Programs and Error Messages

The device diagnostic programs are stored in upgradable ROM on the system board. These programs are the primary method of testing the major components of your device.

Diagnostic error messages indicate that a problem exists; they are not intended to be used to identify a failing part. Troubleshooting and servicing of complex problems that are indicated by error messages should be performed by trained service personnel.

Sometimes the first error to occur causes additional errors. In this case, the device displays more than one error message. Always follow the suggested action instructions for the first error message that appears.

The following sections contain the error codes that might appear in the detailed test log and summary log when the diagnostic programs are run.

The error code format is as follows:

fff-ttt-iii-date-cc-text message

The following are the meanings of the error message elements:

Error Message Element

Explanation

fff

3-digit function code that indicates the function being tested when the error occurred. For example, function code 089 is for the microprocessor.

ttt

3-digit failure code that indicates the exact test failure that was encountered. (These codes are for trained service personnel; see the "Diagnostic Error Codes" section.)

Message that indicates the reason for the problem.The format is as follows:

Function Name: Result (test-specific string)

where:

Function Name is the name of the function being tested when the error occurred. This corresponds to the function code (fff) shown in the error code format in the previous section.

Result can be one of the following:

•Passed—This result occurs when the diagnostic test is completed without any errors.

•Failed—This result occurs when the diagnostic test discovers an error.

•User Aborted—This result occurs when you stop the diagnostic test before it is complete.

•Not Applicable—This result occurs when you specify a diagnostic test for a device that is not present.

•Aborted—This result occurs when the test could not proceed, for example, because of the system configuration.

•Warning—This result occurs when a possible problem is reported during the diagnostic test, such as when a device driver is not found.

•Test-specific string—This is additional information that you can use to analyze the problem.

Starting the Diagnostic Programs

To start the diagnostic programs, follow these steps:

Step 1 Power up the device and watch the console.

Note To run the diagnostic programs, you must start the device with the highest level password that is set. That is, if an administrator password is set, you must enter the administrator password, not the power-up password, to run the diagnostic programs.

Step 2 Press F2 when this message appears:

F2 for Diagnostics

Step 3 Enter the appropriate password and then press Enter.

Step 4 From the top of the window, choose either Extended or Basic.

Step 5 When the Diagnostic Programs window appears, choose the test that you want to run from the list that appears. Follow the instructions in the window:

•Press F1 while running the diagnostic programs to obtain help information. You also can press F1 from within a help window to obtain online documentation from which you can choose different categories. To exit from the help information and return to your last location, press Esc.

•If the device stops during testing and you cannot continue, restart the device and try running the diagnostic programs again. If the problem remains, the component that was being tested when the device stopped needs to be replaced.

•If you run the diagnostic programs with either no mouse or a USB mouse attached to your device, you will not be able to navigate between test categories using the Next Cat and Prev Cat buttons. All other functions provided by mouse-selectable buttons are also available using the function keys.

Note Cisco ACNS software does not support USB peripheral devices.

•You can view device configuration information (such as system configuration, memory contents, interrupt request [IRQ] use, direct memory access [DMA] use, device drivers, and so on) by choosing Hardware Info from the top of the window.

If the diagnostic programs do not detect any hardware errors but the problem persists during normal device operations, a software error might be the cause. If you suspect a software problem, see the information that comes with your software package.

Viewing the Test Log

When the tests are completed, you can view the test log by choosing Utility > View Test Log.

Note You can view the test log only while you are in the diagnostic programs. When you exit the diagnostic programs, the test log is cleared. The Save Logoptionin the diagnostic programs window is not supported because the device does not support a disk drive.

Viewing Diagnostic Error Message Tables

Note Depending on your device configuration, some of the error messages might not appear when you run the diagnostic programs.

Note If diagnostic error messages appear that are not listed in the tables, make sure that your device has the latest levels of BIOS and diagnostics microcode installed.

Checking the Power Subsystem

Power problems can be difficult to solve. For example, a short circuit can exist anywhere on any of the power distribution buses. Usually a short circuit will cause the power subsystem to shut down because of an overcurrent condition.

To perform a general procedure for troubleshooting power problems, follow these steps:

Step 1 Power down the device and disconnect all AC power cords.

Step 2 Check for loose cables in the power subsystem. Also check for short circuits, for example, if there is a loose screw causing a short circuit on a circuit board.

Step 3 Remove adapters and disconnect the cables and power connectors to all internal and external devices until the device is at the minimum configuration required to start it.

Step 4 Reconnect all AC power cords and power up the device. If the device starts up successfully, replace adapters and devices one at a time until the problem is isolated. If the device does not start up from the minimal configuration, replace components of a minimal configuration one at a time until the problem is isolated.

To use this method, it is important to know the minimum configuration required for a system to start.

Note The following are the minimum operating requirements:

•One power supply

•Power cage assembly

•System board

•One microprocessor and voltage regulator module (VRM)

•Memory module (with a minimum of two 128-MB DIMMs)

Troubleshooting the Ethernet Controller

This section provides troubleshooting information for problems that might occur with the 10/100/1000-Mbps Ethernet controller.

Network Connection Problems

If the Ethernet controller cannot connect to the network, check the following conditions:

•Make sure that the cable is installed correctly.

The network cable must be securely attached at all connections. If the cable is attached but the problem remains, try a different cable.

If you set the Ethernet controller to operate at either 100 Mbps or 1000 Mbps, you must use Category 5 or higher cabling.

•Determine whether the hub supports autonegotiation. If it does not, try configuring the integrated Ethernet controller manually to match the speed and duplex mode of the hub.

•Check the Ethernet controller LEDs on the device back panel. (See Figure 1-3.)

These LEDs indicate whether a problem exists with the connector, cable, or hub.

–The Ethernet activity LED is on when the Ethernet controller sends or receives data over the Ethernet network. If the Ethernet activity LED is off, make sure that the hub and network are operating and that the correct device drivers are installed.

–The Ethernet link status LED is on when the Ethernet controller receives a link pulse from the hub. If the LED is off, there might be a defective connector or cable or a problem with the hub.

•Make sure that you are using the correct device drivers that are supplied with your device.

•Check for operating system-specific causes for the problem.

•Make sure that the device drivers on the client and the device are using the same protocol.

•Test the Ethernet controller.

The method used to test the Ethernet controller depends on which operating system you are using (see the Ethernet controller device driver README files).

Ethernet Controller Troubleshooting Chart

Use Table 5-1 to find solutions to 10/100/1000-Mbps Ethernet controller problems that have definite symptoms.

Table 5-1 Ethernet Troubleshooting Chart

Ethernet Controller Problem

Actions

Ethernet link status LED does not work.

Check the following:

•Make sure that the hub is powered on.

•Check all connections at the Ethernet controller and the hub.

•Use another port on the hub.

•If the hub does not support autonegotiation, manually configure the Ethernet controller to match the hub.

•If you manually configured duplex mode, make sure that you also manually configure the speed.

•Run diagnostics on the LEDs.

•Reseat or replace the adapter.

The Ethernet activity LED does not work.

Check the following:

•The network might be idle. Try sending data from this device.

•Run diagnostics on the LEDs.

Data is incorrect or sporadic.

Check the following:

•Make sure that you are using Category 5 or higher cabling when operating the device at 100 Mbps or 1000 Mbps.

•Make sure that the cables do not run close to noise-inducing sources such as fluorescent lights.

The Ethernet controller stopped working when another adapter was added to the device.

Check the following:

•Make sure that the cable is connected to the Ethernet controller.

•Make sure that your PCI system BIOS code is current.

•Reseat the adapter.

•Determine if the interrupt (IRQ) setting assigned to the Ethernet adapter is also assigned to another device in the system. Use the configuration/setup utility program to determine if this is the case.

•Although interrupt sharing is allowed for PCI devices, some devices do not function well when they share an interrupt with a dissimilar PCI device. Try changing the IRQ assigned to the Ethernet adapter or the other device.

•Reseat or replace the adapter.

The Ethernet controller stopped working without apparent cause.

Check the following:

•Run diagnostics for the Ethernet controller.

•Try a different connector on the hub.

•Reseat or replace the adapter.

Identifying Problems Using Trouble Indicators and Status LEDs

If the system error LED on the front of the device is on, one or more LEDs inside the device or on the power supply will be on. Your device has LEDs to help you identify problems with some device components. These LEDs are part of the Light Path Diagnostics feature built into the device. By following the path of lights, you can quickly identify the type of system error that occurred.

Your device is designed so that any LEDs that are on remain on when the device shuts down as long as the AC power source is good and the power supply can supply +5 VDC current to the device. This feature helps you isolate the problem if an error causes the device to shut down. (See Table 5-4.)

Power Supply LEDs

The AC power LED on the power supply provides status information about the power supply. Table 5-2 describes the AC power LED.

3. The power supply has failed and needs to be replaced. Have the system serviced.

System Error LED

If the system error LED on the front of the device is on, one or more LEDs inside the device might be on. Use the Light Path Diagnostic panel to quickly identify the type of error that occurred. For LED locations, see Figure 5-1.

Your device is designed so that LEDs remain on when the device shuts down as long as the power supply is operating properly. This feature helps you to isolate the problem even if an error causes the device to shut down.

Figure 5-1 System Board LED Locations

1

DIMM 1 Error LED

8

DIMM 8 Error LED

2

DIMM 2 Error LED

9

Microprocessor 1 Error LED

3

DIMM 3 Error LED

10

Microprocessor 2 Error LED

4

DIMM 4 Error LED

11

3V Battery Error LED

5

DIMM 5 Error LED

12

NVRAM Battery Error LED

6

DIMM 6 Error LED

13

System Board Error LED

7

DIMM 7 Error LED

14

VRM Error LED

Diagnostic Panel LEDs

Figure 5-2 shows the LEDs on the diagnostic panel inside the device. See Table 5-4 for information about identifying problems using these LEDs.

An error occurred on an adapter in PCI-X slots 1 or 2 or one of the integrated PCI devices on the system board.

ISMP BUS

Service processor failure.

PCI BUS B

An error occurred on an adapter in PCI-X slots 3 or 4.

FAN

A fan (1, 2, 3, 4, 5, 6, 7, or 8) failed or is operating slowly.

CPU/VRM MISMATCH

The service processor detected a CPU or VRM mismatch.

PCI BUS C

An error occurred on an adapter in PCI slot 5.

TEMP

System temperature exceeded maximum rating.

Note The device supports a maximum of three PCI buses.

Remind Button

You can use the Remind button to place the front panel system error LED into the Remind mode. By pressing the button, you acknowledge the failure but indicate that you will not take immediate action. If a new failure occurs, the system error LED comes on again.

In the Remind mode, the system error LED flashes every 2 seconds. The system error LED remains in the Remind mode until one of the following situations occurs:

•All known problems are resolved.

•The system is restarted.

•A new problem occurs.

You can use the Remind button to delay device maintenance until a later time. Also, resetting the system error LED enables the LED to react to another error. If the LED is still flashing from the first error, it masks additional errors.

Using Light Path Diagnostics

The system error LED on the front of the device is on when certain system errors occur. If the system error LED on your device is on, use Table 5-4 to help determine the cause of the error and the action needed. These actions should only be performed by qualified service personnel.

Table 5-4 Light Path Diagnostics

System Error LED (on the Outside Front Panel)

Diagnostic Panel LED

Cause

Action

On

A system error was detected. Check to see which LEDs on the diagnostic panel inside the device are on.

None

The system error log is 75% or more full or a PFA alert was logged.

Check the system error log and correct any problems. Disconnecting the device from all power sources for at least 20 seconds turns off the system error LED.

On

CPU

One of the microprocessors has failed, or a microprocessor is installed in the wrong socket.

1. Check the microprocessor error LEDs on the system board. If a microprocessor error LED is on for a microprocessor socket that is empty, the microprocessors are not installed in the correct order.

2. If the problem remains, the microprocessor needs to be reseated or replaced.

Have the system serviced.

On

VRM

One of the microprocessor VRMs has failed.

1. Check the microprocessor VRM connectors on the system board to locate the error LED next to the failing component.

2. If the problem remains, the microprocessor VRM needs to be reseated or replaced.

Have the system serviced.

On

MEMORY

A memory error occurred.

1. Check the DIMM error LEDs on the system board.

2. The DIMM indicated by the DIMM error LED needs to be replaced.

Have the system serviced.

On

PCI BUS A

PCI BUS B

PCI BUS C

An error occurred on PCI bus A, B, or C. An adapter in PCI slot 1, 2, 3, 4, or 5 or the system board caused the error.

1. Check the adapter slots to locate the error LED next to the failing bus.

2. Check the error log for additional information.

3. If you cannot identify the problem from the error LED or information in the error log, try to identify the failing adapter by removing one adapter at a time from PCI bus A (PCI-X slots 1 or 2), PCI bus B (PCI-X slots 3 or 4), or PCI bus C (PCI slot 5) and restarting the device after each adapter is removed.

On

DASD

A hard disk drive has failed on SCSI channel B.

The error pertains to DASD devices, which are not supported in Cisco ACNS software.

On

NMI

A nonmaskable interrupt occurred. The PCI BUS LED will probably also be on.

If the PCI BUS LED is on, follow the instructions for those LEDs.

If the PCI BUS LED is not on, restart the device.

On

SP BUS

The service processor has failed.

The service processor needs to be replaced.

Have the system serviced.

On

POWER SUPPLY 1

The power supply in bay 1 has failed.

The power supply in bay 1 needs to be replaced.

Have the system serviced.

On

POWER SUPPLY 2

The power supply in bay 2 has failed.

The power supply in bay 2 needs to be replaced.

Have the system serviced.

On

NON-RED

The device is operating in a nonredundant power mode and one of these two conditions exists:

•Two power supplies are installed in the device, and one power supply has either failed or is not connected to a functioning AC electrical outlet.

•The system has exceeded the power capabilities of one of the redundant power supplies.

Note This LED will not be on if your device has only one power supply; however, the power is not redundant with only one power supply installed.

Check the power supply LEDs to identify the failing power supply.

1. Check the power supply connections.

2. If a power supply has failed, it needs to be replaced. Have the system serviced.

3. If neither LED is on, you can remove optional devices from the device to restore redundancy.

On

FAN

One of the fans has failed or is operating too slowly.

The LED on the failing fan is on.

Note A failing fan can also cause the TEMP LED to be on.

The fan needs to be replaced. Have the system serviced.

On

TEMP

The system temperature has exceeded the maximum rating.

1. Check to see whether a fan has failed. If it has, the fan needs to be replaced.

Note Any component that is internal to the device, with the exception of customer-replaceable adapters, must be serviced by a licensed service technician. Contact your service representative.

Step 4 Power up the device. If the problem remains, suspect the following parts in the order listed:

a. Power supply

b. Power cage assembly

c. System board

Note If the problem goes away when you remove an adapter from the system, and replacing that adapter does not correct the problem, suspect the system board.

Note If you suspect a networking problem and all the system tests pass, suspect a network cabling problem external to the system.

Problem-Solving Tips

Because of the variety of hardware and software combinations that can be encountered, use the following information to assist you in identifying the problems. If possible, have this information available when requesting technical assistance.

•Machine type and model

•Microprocessor or hard disk upgrades

•Failure symptom

–Do diagnostics fail?

–What, when, where; single or multiple systems?

–Is the failure repeatable?

–Has this configuration ever worked?

–If it has been working, what changes were made before it failed?

–Is this the original reported failure?

•Diagnostics type and version level

•Hardware configuration

–Print (print screen) configuration currently in use

–BIOS level

•Operating system software type and version level

To eliminate confusion, identical systems are considered identical only if they meet all these conditions:

•Are the exact machine type and models

•Have the same BIOS level

•Have the same adapters or attachments in the same locations

•Have the same address jumpers, terminators, and cabling

•Have the same software versions and levels

•Have the same diagnostics code

•Have the same configuration options set in the system

•Have the same setup for the operating system control files

Comparing the configuration and software setup in working and nonworking systems often leads to resolution of the problem.

Symptoms and Solutions

This section lists symptoms, errors, and the possible causes. The most likely cause is listed first. Use this symptom-to-solution index to help you decide which components your service representative needs to have available when servicing the system.

The first column of the three-column tables in this section lists the error code or message, the second column describes the error, and the third column lists one or more suggested actions or components that need to be reseated or replaced. Use the table to identify possible causes for the error message and then call your service representative.

The POST BIOS code displays POST error codes and messages on the screen.

Beep Symptoms

Beep symptoms are short tones or a series of short tones separated by pauses (intervals without sound). See the examples in the following table.

Beeps

Description

1-2-3

1. One beep

2. A pause (or break)

3. Two beeps

4. A pause (or break)

5. Three beeps

4

Four continuous beeps

One beep after a successful POST indicates that the system is functioning properly.

Table 5-5 lists the beep symptoms, describes the error, and suggests causes and possible actions to solve the problems. The most likely cause of the symptom is listed first.

System Error LED and the Diagnostic Panel LEDs

The system error LED is on when an error is detected. If the system error LED is on, remove the cover and check the diagnostic panel LEDs. Table 5-3 lists all the diagnostic panel LEDs followed by the component or action for correcting the problem. The information in the table is valid only when the system error LED is on.

When checking the diagnostic panel LEDs, note the following information:

•If a diagnostic panel LED is on and the front panel system error LED is off, there is probably an LED problem. Run the LED diagnostics.

•The DIMM error LEDs, microprocessor error LEDs, and VRM error LEDs on the system board go off when the system is powered down.

Table 5-7 provides the diagnostic panel LED error definitions. The third column lists one or more suggested actions or components that need to be reseated or replaced. Use this table to identify possible causes for the error message and then call your service representative.

Table 5-7 Diagnostic Panel LED Error Definitions

Diagnostic Panel LED

Description

Cause and Action

All LEDs off

Check system error log for error condition and then clear the system error log when the problem is found.

1. System error log is 75% full; clear the log.

2. PFA alert; check log for failure; clear PFA alert; disconnect AC power for at least 20 seconds, reconnect, and then power up the system.

b. System is over recommended temperature for CPU x (where x is 1 or 2) (CPU LED is also on).

Check CPU x.

Check the system board.

5. If the CPU LED on the diagnostic panel is also on, one of the microprocessors has caused the error.

Fan LED on

When the LED is lit, a fan has failed or is operating too slowly. A failing fan can also cause the TEMP LED to be lit.

When the LED flashes, an invalid fan configuration has occurred.

1. Check individual fan LEDs.

2. Have the respective fan replaced.

3. Check the fan cable.

4. Check the system board.

5. Check the power cage assembly.

Diagnostic Error Codes

In the following error codes, if XXX is 000, 195, or 197, do not replace a component. The descriptions for these error codes are as follows:

•000—The test passed.

•195—The Esc key was pressed to stop the test.

•197—Warning; a hardware failure might not have occurred.

For all remaining error codes, the solution is to check the component or take the action indicated. Table 5-8 lists all the diagnostic error codes. Use this table to identify a faulty component, and then call your service representative for assistance.

Table 5-8 Error Code Definitions

Error Code

Problem

Action

001-XXX-000

Failed core tests.

Check the system board.

001-XXX-001

Failed core tests.

Check the system board.

001-250-000

Failed system board ECC.

Check the system board.

001-250-001

Failed system board ECC.

Check the system board.

005-XXX-000

Failed video test.

The video feature is not supported in the Wide Area Application Engine 7326.

1. Check the system board cable connectors J4 and J10. Move switch 7 of SW1 to bypass power control. If the DC good LED is on, press Ctrl+Alt+Delete. Watch the console for any POST errors. Check the system error log for any listed problems. If the system starts with no errors, your service technician should reseat or replace the following items:

a. Power switch assembly

b. System board

On

Off

(continued)

2. Remove the adapters and disconnect the cables and power connectors to all internal and external devices. Power up the system. If the DC good LED is on, replace the adapters and devices one at a time until you isolate the problem.

The system is able to communicate to the system management processor, but the system management processor failed to respond at the start of POST.

1. Complete the following steps before replacing a FRU:

a. Remove the AC power to the device, and wait 20 seconds.

a. Reconnect the AC power and wait 30 seconds.

b. Power up the device.

c. Flash update the system management processor.

2. Check the system board.

1602

Cable for optional service processor adapter not installed.

Disconnect all device and hardware option power cords from the device, wait 30 seconds, reconnect, and retry.

1762

Hard disk configuration error.

1. Check the hard disk drive.

2. Check the hard disk cables.

3. Check the hard disk adapter.

4. Check the SCSI backplane.

5. Check the system board.

178X

Fixed disk error.

1. Check the hard disk cables.

2. Run diagnostics.

3. Check the hard disk adapter.

4. Check the hard disk drive.

5. Check the system board.

1800

No more hardware interrupts available for PCI adapter.

1. Check for failing adapter.

2. Check the system board.

1962

Drive does not contain a valid boot sector.

1. Verify that a startable operating system is installed.

2. Run diagnostics.

3. Check the hard disk drive.

4. Check the SCSI backplane.

5. Check the cable.

6. Check the system board.

2400

Video controller test failure.

The video feature is not supported in the Wide Area Application Engine 7326.

2462

Video memory configuration error.

The video feature is not supported in the Wide Area Application Engine 7326.

5962

IDE CD-ROM drive configuration error.

1. Check the CD-ROM drive.

2. Check the CD-ROM power cable.

3. Check the IDE cable.

4. Check the system board.

5. Check the battery.

8603

Pointing device error.

This feature is not supported in Cisco ACNS software.

0001200

Machine check architecture error.

1. Check microprocessor 1.

2. Check optional microprocessor 2.

00012000

Microprocessor machine check.

1. Check the microprocessor.

2. Check the system board.

00019501

Microprocessor 1 is not functioning.

1. Check VRM and microprocessor LEDs.

2. Check VRM 1.

3. Check microprocessor 1.

4. Check the system board.

00019502

Microprocessor 2 is not functioning.

1. Check VRM and microprocessor LEDs.

2. Check VRM 2.

3. Check the microprocessor 2.

00019701

Microprocessor 1 failed.

1. Check microprocessor 1.

2. Check the system board.

00019702

Microprocessor 2 failed.

1. Check microprocessor 2.

2. Check the system board.

00180100

A PCI adapter has requested memory resources that are not available.

1. Reorder the adapters in the PCI slots. It is important that your startup device is positioned early in the startup device order so that it is run by POST.

2. Ensure that the PCI adapter and all other adapters are set correctly in the configuration/setup utility program. If the memory resource settings are not correct, change the settings.

3. If all memory resources are being used, you might need to remove an adapter to make memory available for the PCI adapter. Disabling the adapter BIOS on the adapter might correct the error. (Refer to the documentation provided with the adapter.)

00180200

No more I/O space available for PCI adapter.

1. Check the adapter.

2. Check the system board.

00180300

No more memory (above 1 MB) for PCI adapter.

1. Check the adapter.

2. Check the system board.

00180400

No more memory (below 1 MB) for PCI adapter.

1. Move the failing adapter to slot 1.

2. Check the adapter.

3. Check the system board.

00180500

PCI option ROM checksum error.

1. Remove the failing PCI card.

2. Check the system board.

00180600

PCI to PCI bridge error.

1. Move the failing adapter to slot 1.

2. Check the adapter.

3. Check the system board.

00180700, 00180800

General PCI error.

1. Check the system board.

2. Check the PCI card.

00181000

PCI error.

1. Check the adapter.

2. Check the system board.

01295085

ECC checking hardware test error.

1. Check the system board.

2. Check the microprocessor.

01298001

No update data for microprocessor 1.

1. Ensure that all processors have the same cache size.

2. Check microprocessor 1.

01298002

No update data for microprocessor 2.

1. Ensure that all processors have the same cache sizes, dock speeds, and clock frequencies.

2. Check microprocessor 2.

01298101

Bad update data for microprocessor 1.

1. Ensure that all processors have the same cache sizes, dock speeds, and clock frequencies.

2. Check microprocessor 1.

01298102

Bad update data for microprocessor 2.

1. Ensure that all processors have the same cache sizes, dock speeds and clock frequencies.

2. Check microprocessor 2.

19990301

Hard disk sector error.

1. Check the hard disk drive.

2. Check the SCSI backplane.

3. Check the cable.

4. Check the system board.

19990305

Hard disk sector error, no operating system installed.

Install operating system on the hard disk.

19990650

AC power has been restored.

1. Check the power cable.

2. Check for interruption of power.

1ACNS software does not support keyboards. No keyboard errors are expected; however, if a keyboard error appears during bootup, contact the Cisco Technical Assistance Center.

2 ACNS software does not support disk drives. No disk drive errors are expected; however, if a disk drive error appears during bootup, contact the Cisco Technical Assistance Center.

Service Processor Error Codes

When viewed from POST, service processor error codes appear in hexadecimal form (generally beginning with A2, A3, A4, A5, A6, A7, AD, AE, or E1). However, when viewed from the system error log, the messages appear as text. To identify a possible error condition for the service processor, see the system error log. (See the "Diagnostic Programs and Error Messages" section.)

SCSI Errors

Note If your device does not have a hard disk drive, ignore any message that indicates that the BIOS is not installed.