Hi,

My HP proliant DL380G6 is got rebooted twice in a day. I checked with vendor, they are saying this is OS issue. redhat 5 64bit is insaltted on it.
I don't think there is os issue.
Can any one guide me to install hardware log software on proliant (cpu, memory, disk, netwowrk, power) and save the log any location before reboot.
please help.

Have you looked at /var/log/messages to see what was being logged before the boot occurred?

If there is a panic causing the boot (which it sounds like) then there is no way to trap the information - a panic means it can't continue on with any operations so has to stop - no logging or any other information would be available.

If you can get in front of the console quickly enough to hit "Ctrl-S" to lock the screen you may be able to record the panic information displayed then hit "Ctrl-Q" to unlock the screen. (This may not work for a panic though.) If you have a KVM that has a GUI interface (e.g. web) you might be able to do a screen shot of that interface from another system.

I have chacked nothing inside the messages log file. and also it does not generate panic error. Yesterday I installed fresh OS, and it was working fine.
This server is remote location. and does not have kvm/ilo configured.

I have installed hpasmcli, it shows the the server details. but want to set with third party tool(nagios) so we can get alert or save the harware log before rebooting.

Nagios will certainly let you do monitoring of the server but it isn't going to "save the hardware log" for you when the server boots. You can however see history of what it was seeing before the boot.

Nagios is a great monitoring tool but it requires you to install Nagios and standard plugins on a master server. You can use it to check nrpe (which requires NRPE Plugin be added to both the master and the client you want to monitor), snmp (check_snmp plugin) can probably query various hardware snmp things for you from hardware level or you can use your own canned scripts doing simple ssh connections.

Additionally you might want to look at sending syslog output from the remote server to a local server so you're getting all the messages in a central log you can examine while the reboot is underway.