ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

hp DL380 g4 overtemperror leds in MB

omar abdullah
Frequent Advisor

hp DL380 g4 overtemperror leds in MB

Hi

I have hp dl380 g4

ihave red leds in panel and OVERTEMP in Main Board (CR22)

please giv me your advice for this problem


Regards
A.Omar
3 REPLIES
David Claypool
Honored Contributor

Re: hp DL380 g4 overtemperror leds in MB

You should get some better information from the System Management Homepage, or if the system isn't powering up, connect to iLO and check the IML.
omar abdullah
Frequent Advisor

Re: hp DL380 g4 overtemperror leds in MB

Hi my Dear;

the server not startup
when the switch on no action on the server
only fans on and off and RED leds in pannel
I think this problem of power
I change the power supply ; the same errors
what about the power interface sp/n(361667-001)

Regards
A. Omar
TarunJain
Respected Contributor

Re: hp DL380 g4 overtemperror leds in MB

There are two health LEDs on front panel of DL380 G4 server. One is internal health (wave sign inside box) which points any internal device failure and second is External health (wave sign without any box) which points to power supply status.
Power on the server and check Which one is red?

If external health led is red then check the server on single power supply.

If the internal health led is red then that shouldn't be be a power related issue.
The ILO doesn't require the server to be powered on, only power cable should be connected.

Check the status after these steps:
1. remove the power from server, let the server cool down for 5 minutes
2. Remove any optional card and disconnect the optional devices and network cables
3. Re-fix the riser cage
3. Connect local monitor and keyboard
4. Power on the server and check the LED status on front panel and system board
5. Confirm the status of fans and match the error LEDs with the diagram on the top cover of the server.
These steps should be enough to find out the cause of the issue.
POST again with the observations or log a call with hp as this seems to be a h/w issue

Regards,
TarunJain