Page 3 of 3
Re: Monitoring HP Proliant ILO 4 on Nagiosxi
Posted: Tue Jul 23, 2019 6:16 am
by rdandekar
Hello Team,
Thanks For Update.
we will do and update you for the same.
Re: Monitoring HP Proliant ILO 4 on Nagiosxi
Posted: Tue Jul 23, 2019 7:52 am
by scottwilkerson
You can also try the following if you still have issues:
Code: Select all
cp /usr/local/nagios/libexec/check_ilo2_health.pl /tmp
sed -i -e 's/Nagios::Plugin/Nagios::Monitoring::Plugin/g' /usr/local/nagios/libexec/check_ilo2_health.pl
Re: Monitoring HP Proliant ILO 4 on Nagiosxi
Posted: Wed Jul 24, 2019 3:56 am
by rdandekar
Hi Team,
We have ran below suggested command,
./check_ilo2_health.pl -V
we got below output, Please find the attached screenshot for the same.
check_ilo2_health.pl 1.63
Please tell us what next steps we have to do.
Re: Monitoring HP Proliant ILO 4 on Nagiosxi
Posted: Wed Jul 24, 2019 6:28 am
by scottwilkerson
Follow the plugin help and this doc to get the command running from the command line and then add into XI
Nagios XI Managing Plugins
Re: Monitoring HP Proliant ILO 4 on Nagiosxi
Posted: Thu Jul 25, 2019 2:27 am
by rdandekar
Hello Team,
We are runing the command ./check_ilo2_health.pl -u $USER1$ -p $USER2$ -H $HOSTADDRESS$ -c -3
and we got the below output
ILO2_HEALTH OK - (Board-Version: ILO>=3) Temperatures: 01-Inlet_Ambient (OK): 16, 02-CPU_1 (OK): 40, 03-CPU_2 (OK): 46, 04-P1_DIMM_1-6 (OK): 30, 05-P1_DIMM_7-12 (OK): 33, 06-P2_DIMM_1-6 (OK): 41, 07-P2_DIMM_7-12 (OK): 30, 08-HD_Max (OK): 35, 10-Chipset (OK): 42, 11-PS_1_Inlet (OK): 32, 12-PS_2_Inlet (OK): 31, 13-VR_P1 (OK): 44, 14-VR_P2 (OK): 48, 15-VR_P1_Mem (OK): 31, 16-VR_P1_Mem (OK): 31, 17-VR_P2_Mem (OK): 37, 18-VR_P2_Mem (OK): 32, 19-PS_1_Internal (OK): 40, 20-PS_2_Internal (OK): 40, 23-PCI_3 (OK): 57, 27-HD_Controller (OK): 58, 29-LOM (OK): 52, 30-Front_Ambient (OK): 27, 31-PCI_1_Zone. (OK): 33, 32-PCI_2_Zone. (OK): 34, 33-PCI_3_Zone. (OK): 35, 37-HD_Cntlr_Zone (OK): 38, 38-I/O_Zone (OK): 34, 39-P/S_2_Zone (OK): 39, 40-Battery_Zone (OK): 38, 41-iLO_Zone (OK): 43, 43-Storage_Batt (OK): 23, 44-Fuse (OK): 37
Our primary requirement is to monitor the status of the HDD installed on these remote servers. With the above script and its output we are not able to get the status of HDD. Therefore, we require you assistance to get the status of the HDD status from these remote servers on NAGIOS XI GUI
Regards,
Rahul Dandekar
Re: Monitoring HP Proliant ILO 4 on Nagiosxi
Posted: Thu Jul 25, 2019 6:46 am
by scottwilkerson
Can you run it as the following and show the output
Code: Select all
./check_ilo2_health.pl -u $USER1$ -p $USER2$ -H $HOSTADDRESS$ -c -3 -v
Re: Monitoring HP Proliant ILO 4 on Nagiosxi
Posted: Tue Aug 06, 2019 8:28 am
by rdandekar
Hello Team,
We tried to run the command
./check_ilo2_health.pl -u $USER1$ -p $USER2$ -H $HOSTADDRESS$ -c -3 -v
and we got the below output,
ILO2_HEALTH OK - (Board-Version: ILO>=3) Temperatures: 01-Inlet_Ambient (OK): 17, 02-CPU_1 (OK): 40 , 03-CPU_2 (OK): 40, 04-P1_DIMM_1-6 (OK): 34, 05-P1_DIMM_7-12 (OK): 38, 06-P2_DIMM_1-6 (OK): 27, 07 -P2_DIMM_7-12 (OK): 32, 08-HD_Max (OK): 35, 10-Chipset (OK): 49, 11-PS_1_Inlet (OK): 28, 12-PS_2_In let (OK): 28, 13-VR_P1 (OK): 39, 14-VR_P2 (OK): 32, 15-VR_P1_Mem (OK): 32, 16-VR_P1_Mem (OK): 35, 1 7-VR_P2_Mem (OK): 29, 18-VR_P2_Mem (OK): 29, 19-PS_1_Internal (OK): 40, 20-PS_2_Internal (OK): 40, 27-HD_Controller (OK): 65, 30-Front_Ambient (OK): 28, 31-PCI_1_Zone. (OK): 35, 32-PCI_2_Zone. (OK): 37, 33-PCI_3_Zone. (OK): 37, 37-HD_Cntlr_Zone (OK): 50, 38-I/O_Zone (OK): 39, 39-P/S_2_Zone (OK): 32, 40-Battery_Zone (OK): 38, 41-iLO_Zone (OK): 44, 43-Storage_Batt (OK): 23, 44-Fuse (OK): 33
Please assist us further as we are looking for your valuable reply.
Kind Regards,
Rahul Dandekar
Re: Monitoring HP Proliant ILO 4 on Nagiosxi
Posted: Tue Aug 06, 2019 9:13 am
by scottwilkerson
Are you sure you had the
-v on there?
I'm looking at the code and there should be a lot more output, including the first line which should start with:
We don't have this equipment, nor are the authors of this plugin so have no way of testing it.
You may need to reach out to the plugin author.