Table 5-4

Advanced Entry Class Troubleshooting

 

 

 

Step

Symptom/Condition

Action

 

 

 

6

Cannot read the system event

System event logging has stopped due to a presumed BMC

 

log from the system console.

malfunction (system health is steady green, internal health is steady

 

 

green, external health is steady green, and power is steady green).

 

 

1.

Examine the console messages for any EFI errors or warnings

 

 

 

about BMC operation or communications.

 

 

2.

Examine the BMC heartbeat LED; if it is not flashing green,

 

 

 

replace the core I/O board FRU. See “Management Subsystem ”

 

 

 

(page 170) for information.

 

 

3.

Test the operation of the BMC by toggling the UID locator switch

 

 

 

LED on the front panel. The blue LED is turned on/off by the

 

 

 

BMC when the switch is toggled

The problem is fixed when the BMC heartbeat LED is flashing green, and the system event log resumes logging.

7OS is non-responsive (hung). Front panel LEDs indicate that the server power is turned on, and it is either booting or running the OS ( system health is steady green, internal health is steady green, external health is steady green, and power is steady green).

Nothing may be logged for this condition.

1.Reset the system using one of the following methods: a. Use the iLO 2 MP to reset the system:

From the command menu of text interface via SSH or Telnet, use the TC command.

From the web GUI, Reset through INIT or TOC signal from the Power & Reset menu on the Virtual Devices tab.

For more information see the HP Integrity iLO 2 MP Operations

Guide.

b.Use a tool (such as a ACX-10 Torx screwdriver or appropriately size allen wrench) to depress the INIT button on the front panel to start system initialization.

2.Reboot the OS.

3.Obtain the system hardware status dump for root cause analysis.

4.Examine the iLO 2 MP logs for entries related to processors, processor power modules (PPMs), shared memory, and core I/O devices. See “Errors and Reading Error Logs” (page 154) for information.

The problem is fixed when the root cause has been determined, and the OS is running normally.

146 Troubleshooting