topic Re: DL380 G4 Power Supply Unit monitoring from Linux? in ProLiant Servers (ML,DL,SL)

DL380 G4 Power Supply Unit monitoring from Linux?

Joost Lek_1 — Fri, 15 Jul 2005 01:47:33 GMT

Hello,

we are currently in progress of testing a DL380 G4 unit from HP, with redundant power supplies. Using the Proliant Support Pack we were able to view the status of the raid controller and it's containers. We are unable to monitor the status of the power supply using any of the utilities in the PSP.
Can anyone point me to a tool or command that would allow me to view the status of the power supplies?

Thanks in advance.

Re: DL380 G4 Power Supply Unit monitoring from Linux?

Ross Minkov — Sat, 16 Jul 2005 08:00:43 GMT

Joost,

You can use hplog, the hp ProLiant Integrated Management Logging (IML) utility, that comes with the PSP for Linux to display current power data:

# /sbin/hplog -p
ID TYPE LOCATION STATUS REDUNDANT
1 Standard Pwr. Supply Bay Nominal Yes
2 Standard Pwr. Supply Bay Nominal Yes

See hplog(8) for more information.

Part of the PSP for Linux is the hp Server Management Drivers and Agents (hpasm -- stands for hp Advanced System Management) package. hpasm is a collection of driver and tools which enable monitoring of fans, power supplies, temperature and other management events.

One of the features supported by hpasm is monitoring the system fault tolerant power supply.

For more information visit the PSP website at http://www.hp.com/servers/psp.

Regards,
Ross

Re: DL380 G4 Power Supply Unit monitoring from Linux?

Mahesh Kumar Malik — Sun, 17 Jul 2005 00:55:26 GMT

Hi Joost

PSP has limited functionality in terms of hardware monitoring. Use System Insight manager for monitoring of harware components in DL380G4. Visit the following link for Overview and free download

http://h18013.www1.hp.com/products/servers/management/hpsim/index.html

Regards
Mahesh

Re: DL380 G4 Power Supply Unit monitoring from Linux?

Joost Lek_1 — Mon, 18 Jul 2005 04:14:15 GMT

Thank you both for your replies, the answers were very helpful. Eventually i solved the problem with this howto (our systems run debian sarge).
http://debian.catsanddogs.com/forum/index.php/topic,4.0.html