HP LH4r HP Netserver LXr 8000 Installation Guide - Page 120
If the System Will Not Power On, If the System Powers On but Fails the POST Power-On Self Test
View all HP LH4r manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 120 highlights
Chapter 12 Troubleshooting If the System Will Not Power On Follow these steps: (add rack steps) 1. On the control panel, check to see if the LCD screen's backlight is lit. If it is, the system is receiving AC power. If it is not lit, make sure that the server's power cord in connected. 2. Check the HP NetServer's power supplies. Each power supply has three LEDs. The top LED, PWR, should glow a steady green when the system's DC power has been switched on and will blink green if the DC power is switched off but AC is properly connected. If the PWR LED is not steady green or blinking green, reseat the power supply. If the System Powers On but Fails the POST (Power-On Self Test) Check for the following problems: • If no message is displayed on the control panel LCD, remove and reseat the control board. • If the front panel is operating normally but no message appears on the server's monitor, check for a POST passcode on the control panel LCD. See Chapter 2 for instructions on checking the error log from the control panel LCD. • If the control panel LCD displays post code FF, the system board could be bad. Contact your support representative for assistance. • If the post code on the control panel LCD changes from 00 to C0, and there is no video display, make sure that the video board is properly seated. • If the monitor is working, check the POST passcode it displays. If the code is between #0 and 3Ah, and the code does not change, reseat the system's processor and memory boards. Then reboot the system. • If none of the above measures works, clear CMOS and see if the system boots. (Check the HP NetServer's reference label for instructions on clearing CMOS.) If this does not solve the problem, see "If the System Passes the Post but Will Not Function" later in this chapter. • Run the Event Log Report Utility. 112