A-Class Server Trouble Shooting

Overview

	NOTE: The information in this section is meant for users who have at least a minimum level of hardware troubleshooting experience. Some System Administrator-level knowledge of the HP-UX operating system is also required.

A-Class Server Selftest Failures/Warnings

	NOTE: Warnings will include a brief description of the fault.

Troubleshooting with Light-Emitting Diode (LED) Interpretation

Successful Power-on Selftest.

When power is applied to the server, the green POWER icon will light upon successful completion of the power supply selftest, which takes approximately 2 seconds. If the green POWER LED fails to light, check the power source. If the power source is valid, the problem is usually in the A-Class server power supply. Power supply failures are repaired by replacing the A-Class Exchange Base Unit (EBU). Refer to the "Replacing an A-Class Server Exchange Base Unit (EBU)" section. After the green POWER icon comes on, both the amber HEARTBEAT and amber LAN ACTIVITY icons will momentarily light and go out. When selftest is complete, the firmware Main Menu screen will display on the console, and the green POWER icon will emit a steady light. LED icon states will appear as shown below:

The following table shows how to interpret front panel LED blinking codes when selftest has failed and the firmware Main Menu screen is inaccessible. During the conditions shown in this table, the green POWER icon is ON.

	NOTE: The LED pattern is only valid if the Firmware Main Menu is not displayed at the Console.

		LAN LED	Heartbeat LED	Indication
		Random Blink Pattern	Heartbeat Blink Pattern	Normal Operation (Under HP-UX)
		Off	Off	2nd Level Cache SIMM fault
		On (Steady)	Off	Memory SIMM fault
		On (Steady	On (Steady)	I/O Subsystem or I/O Board fault
		Off	On (Steady)	System board fault, HPMC or Unknown fault
		Blinking	On (Steady)	I/O HPMC fault
		Blinking opposite of Heartbeat LED	Blinking opposite of LAN LED	Memory HPMC fault (When LAN is ON, Heartbeat is OFF. When Heartbeat is ON, LAN is OFF)
		Off	Heartbeat Blink pattern	2nd Level Cache HPMC fault

Second Level Cache/RAM Memory Module Faults

Second Level Cache Memory Module Fault.

This fault occurs when a Second Level Cache (SLC) failure prevents the system from completing selftest. Chassis codes provided by the HSC Remote Management card are useful in troubleshooting this type of error. For example, the fault FLT 2120 chassis code message indicates: "Second Level cache selftest" failure.

	NOTE: SIMM is an acronym for Single Inline Memory Module. A SIMM has components on one side of the card, only.DIMM is an acronym for Dual Inline Memory Module. A DIMM has components on both sides of the card.The acronym SIMM will be used throughout this section to refer to either SIMM or DIMM.

Electrostatic Discharge Precautions.

The procedures in this section require opening the server and exposing the system to electrostatic discharge. Always observe all electrostatic precautions when working with components inside or out of the server. Failure to follow these precautions may result in component damage or loss of system reliability.

• Use a grounding mat and an anti-static wrist strap.

• Wear the anti-static wrist strap to ensure that any accumulated electrostatic charge is discharged from your body to ground.

Before You Do Anything...

• Power down the system.

• Unplug the server.

  	NOTE: Cabinet-mounted servers must be removed from the cabinet before proceeding.

• Remove the top of the server by unscrewing the knurled captive screws on each side of the rear of the server. Slide the top back, lift it off, and set it aside.

General SLC SIMM Troubleshooting.

	NOTE: A-Class servers can only use Cache Memory SIMMs with part number A5182-60002. Using Cache Memory SIMMs with any other part number may result in the server failing it's selftest.

1. Remove both SLC SIMMs and place on an ESD mat.

2. Power up and observe LEDs

3. If fault does not recur, the problem is with the SLC SIMMs. Either replace both SLC SIMMs, or proceed to the "Single SLC SIMM Troubleshooting." subsection below.

4. If the fault recurs, the problem is with the system board. To replace the system board, replace the A-Class Exchange Base Unit (EBU). Refer to the "Replacing an A-Class Server Exchange Base Unit (EBU)" section.

Single SLC SIMM Troubleshooting.

To troubleshoot SLC faults to a single SIMM, a known-good SLC SIMM is required.

1. Install the known-good SLC SIMM in slot A and install one of the original SLC SIMMs in slot B of the pair that failed. Power up and observe front panel LEDs.

2. If the fault does not recur, the problem was caused by the SIMM that is not presently installed. Boot the system and resume normal operations. If the fault recurs, proceed to step 3.

3. Replace the SLC SIMM in slot B with the other original SLC SIMM. Power up and observe front panel LEDs.

4. If the fault does not recur, the problem is with the SLC SIMM previously installed in slot B. Boot the system and resume normal operations.

5. If the fault recurs, the problem is with the system board. To change the system board, you must replace the A-Class Exchange Base Unit (EBU). Refer to the "Replacing an A-Class Server Exchange Base Unit (EBU)" section.

Random Access Memory (RAM) Module Fault.

This fault occurs when a RAM failure prevents the system from completing selftest. Chassis codes provided by the HSC Remote Management card are useful in troubleshooting this type of error. For example, FLT 7xxx indicates a failure in the memory selftest.

	NOTE: SIMM is an acronym for Single Inline Memory Module. A SIMM has components on one side of the card, only.DIMM is an acronym for Dual Inline Memory Module. A DIMM has components on both sides of the card.The acronym SIMM will be used throughout this section to refer to either SIMM or DIMM.

Electrostatic Discharge Precautions.

The procedures in this section require opening the server and exposing the system to electrostatic discharge. Always observe all electrostatic precautions when working with components inside or out of the server. Failure to follow these precautions may result in component damage or loss of system reliability.

• Use a grounding mat and an anti-static wrist strap.

• Wear the anti-static wrist strap to ensure that any accumulated electrostatic charge is discharged from your body to ground.

Before You Do Anything...

• Power down the system.

• Unplug the server.

  	NOTE: Cabinet-mounted servers must be removed from the cabinet before proceeding.

• Remove the top of the server by unscrewing the knurled captive screws on each side of the rear of the server. Slide the top back, lift it off, and set it aside.

General RAM Module Troubleshooting.

1. List which size SIMMs are installed in which slots.

2. Remove all RAM SIMMs except for slot 0a and 0b (0a/b). Plug in and power up the server, and observe the front panel LEDs.

3. If fault does not recur, the SIMMs installed in slot 0a and 0b are not the cause of the RAM SIMM fault. Power down the server, refer to the memory configuration list (step 1) and install the next pair of SIMMs. Power up the server and observe the front panel LEDs.

4. Repeat step 3 until the RAM SIMM fault recurs. Note which pair of SIMMs caused the RAM SIMM failure. Either replace both memory SIMMs or continue to troubleshoot to a single SIMM.

For example: When RAM was reinstalled in slots 2a/b, the RAM SIMM fault returned. Therefore, the problem is with one of the two RAM SIMMs installed in slot 2a/b.

Single RAM Module Troubleshooting.

To troubleshoot RAM faults to a single SIMM, a known-good RAM SIMM is required.

1. Install the known-good RAM SIMM in slot A and install one of the original RAM SIMMs in slot B. Power up the server and observe the front panel LEDs.

2. If the fault does not recur, the problem was caused by the SIMM that is not presently installed. Boot the system and resume normal operations. If the fault recurs, proceed to step 3.

3. Power down the server and replace the RAM SIMM in slot B with the other original RAM SIMM. Power up and observe front panel LEDs.

4. If the fault does not recur, the problem is with the RAM SIMM that was previously installed in slot B. Boot the system and resume normal operations.

5. If the fault recurs, the problem is with the system board. To change the system board, you must replace the A-Class Exchange Base Unit (EBU). Refer to the "Replacing an A-Class Server Exchange Base Unit (EBU)" section.

Firmware Warning Messages

Firmware is the name given to the system boot instructions and selftest software that is imbedded into a computer chip instead of stored on disk. Firmware also includes warnings and error messages that are displayed on the console when selftest finds an error. Those warnings and messages, and a brief description or action requirement of each, is shown in the table included below:

Chassis Code Summary

Operating Status (OSTAT) and chassis codes are generated by A-Class server firmware. OSTAT and chassis codes can be read from stored locations or viewed 'real time' via the HSC Remote Management card.

Chassis codes displayed during selftest only appear at the console. They will appear on either the ASCII console or the Web console. Below is an example of how chassis codes appear in response to a 'control b' key sequence:

The HSC Remote Management card shows status information on the console just above the function key display (shown above) and is followed by the CM> prompt. The information displayed is shown below:

CM>

HSC Remote Management status information is defined as follows:

For more information on the HSC Remote Management card, refer to the HSC Remote Management/Access Port Card information in the Reference section.

During selftest, OSTAT and chassis codes are generated and stored by the server firmware. These chassis codes can be viewed even if an HSC Remote Management card is not installed. To view power on chassis codes, either type ser cc at the firmware main menu, or change to the Service Menu and type cc.

A display of OSTAT and chassis codes are shown in the following example:

Chassis codes used in conjunction with the OSTAT value represent the status of the system:

Service Menu: Enter command > cc CHASSIS CODES INFORMATION Chassis Code INIT C4CC INIT C4CD INIT 3002 TEST 30BC INIT 30BC INIT C300 TEST 1030<Press any key to continue (q to quit)> qService Menu: Enter command >

If a fault prevents the server from completing selftest, the OSTAT FLT is used and the Chassis Code displays the test number that failed. If the server stops responding while performing a test, the OSTAT value will be INIT or TEST and the chassis code represents the test that was running when the server failed.

Refer to the table below to determine which tests were active when the system either faulted or stopped responding during selftest, and the corrective action to take in response to the problem.

Troubleshooting the ASCII Console

The ASCII Console is typically a "dumb" monochrome terminal that serves as the communication link between the A-Class server and the system operator. At power on, the server's selftest software tests server internal components and external peripherals to determine the operational status of each. The ASCII Console displays the operational status of all components and peripherals, including its own, on the console screen. The screen will display selftest data output in one of two ways:

If the ASCII console does not respond to input or does not display any output:

If you have an HSC Remote Management card installed and the ASCII console works but the control B function does not, check the position of the SERVICE/NORMAL switch on the HSC Remote Management card. This switch must be in the SERVICE position to enable the control B function. If the control B function does not restore, replace the HSC Remote Management card. Refer to the "A-Class Server I/O Card Removal and Replacement " section.

	NOTE: The control B function is unique to the HSC Remote Management card. If you do not have an HSC Remote Management card installed, the control B function is not available.

Troubleshooting the Secure Web Console

The Secure Web Console is typically a "dumb" monochrome terminal that can serve as the communication link between the A-Class server and the system operator, as a substitute for the ASCII Console. At power on, the server's selftest software tests server internal components and external peripherals to determine the operational status of each. The Secure Web Console displays the operational status of all components and peripherals, including its own, on the console screen. The screen will display selftest data output in one of two ways:

	NOTE: The Integrated LAN Web Console will be referred to as the Web console in this section. The A-Class server front panel LEDs do not indicate Web console failures. There are no blinking codes to show the source of a web console fault.

To troubleshoot the Web console:

	NOTE: If you can access the console but do not get a prompt, it may be that you do not have write access to the console. Multiple users may have access to the console (read access) at the same time, but only one user can write to the console at a time. To see which user has write access to the console, look at the Web console main screen. The user whose name is underlined has write access to the console. Write access can only be taken, not given. To acquire write access, press ctrl F12. Your username will now be underlined and you will be able to enter commands into the Web console system. Everyone else is excluded from writing to the console, but everyone on the system has read access.

Troubleshooting Embedded Disks

The A-Class server will support a maximum of two internally installed and connected disk drives, commonly referred to as embedded disks. Embedded disks contain both the server's startup (bootstrap) software and Operating System software. Though embedded disks are installed internally, the server's front panel LEDs do not reflect disk status and therefore will not blink in a code pattern to indicate an embedded disk selftest failure. Also, embedded disks do not have an individual fault LED to show operational status.

If the system cannot boot from an embedded disk, an Input/Output Dependent Code (IODC) error occurs. The example provided below starts with entry of the boot command and shows the messages that will be displayed on the console.

Main Menu: enter command > bo pri

Interact with IPL (Y, N, or Cancel)? > y

Booting...
Cannot find ENTRY_TEST


Failed to initialize.


ENTRY_INIT
Status = -10

FFFFFFF6 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000012 00000000 00000000 454E4841 00000000 00000000 454E4841
00000000 00000000 00000000 00000000 00000100 00000000 00000000 00000000

Failed to Initialize

Off-line Diagnostic Environment (ODE) and Support Tools Manager (STM) software can also be used to troubleshoot embedded disk faults. Use mapping utilities (Mapper) to verify that the disks are recognized by the server. Password-protected disk expert tools are available via ODE and STM.

	NOTE: Only licensed self-maintenance technicians and HP service personnel have access to the diagnostic passwords required for access to ODE and STM software, and disk expert tools.

Troubleshooting LAN

When connected to a hub, the 10 Base-T LAN on A-Class servers should automatically negotiate the proper speed. If this auto-negotiation fails, the server will not connect to the hub. Should this symptom occur, replace the EBU. Be sure to use an EBU with part number A5182-69101 or later.