Page 2 of 2
Re: Issue in monitoring Hardware health using check_ilo2_hea
Posted: Sat Aug 19, 2017 12:14 pm
by bsivavani
Yes. I am able to access Web interface.
Re: Issue in monitoring Hardware health using check_ilo2_hea
Posted: Mon Aug 21, 2017 8:50 am
by tgriep
If you are accessing the device using https then you may have to add the SSL options to the check.
-s, --sslv3
Use sslv3 for connection.
--sslopts
Sets IO::Socket:SSL Options, defaults to 'SSL_verify_mode => SSL_VERIFY_NONE'.
Some firmware may need --sslopts 'SSL_verify_mode => SSL_VERIFY_NONE, SSL_version => "TLSv1"'.
Other than that, you would have to contact the author of the plugin for further support.
Re: Issue in monitoring Hardware health using check_ilo2_hea
Posted: Mon Aug 21, 2017 12:54 pm
by bsivavani
Tried by passing with -s option, receiving SSL connect attempt failed error
[root@s930l3301 Nagios_agent]# /usr/local/nagios/libexec/check_ilo2_health.pl -H s930e0130.rwe.com -u XXXX -p XXXX -t 30 -3 -g -d -v -s
hostname is s930l3301
retry: 0
ILO2_HEALTH UNKNOWN - ERROR: Failed to establish SSL connection with s930e0130.rwe.com:443 SSL connect attempt failed because of handshake problems.
[root@s930l3301 Nagios_agent]#
Re: Issue in monitoring Hardware health using check_ilo2_hea
Posted: Mon Aug 21, 2017 2:13 pm
by dwhitfield
You may need to install lynx, but from the XI server, can you show us a screenshot of what lynx gives when you run lynx s930e0130.rwe.com
Re: Issue in monitoring Hardware health using check_ilo2_hea
Posted: Tue Aug 22, 2017 3:23 pm
by gwakem
For what it's worth, I can recreate the reply you're getting on my iLO.
Code: Select all
# ./check_ilo2_health2.pl -H xxxxxxxx -u xxxxxxxx -p xxxxxxxxxx -t 30 -3 -g -d -v -s
hostname is xxxxx
retry: 0
ILO2_HEALTH2 UNKNOWN - ERROR: Failed to establish SSL connection with xxxxxxxxxx:443 IO::Socket::IP configuration failed SSL connect attempt failed because of handshake problems error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure.
If I remove the forcing of SSL/TLS via the
-s flag, I get a full readout of all data on the ilo as expected. If I then remove the
-v flag (for unformatted verbosity), I get a much cleaner readout with perfdata included:
Code: Select all
# ./check_ilo2_health2.pl -H xxxxxxxxxxxx -u xxxxxxxxxxxx -p xxxxxxxxxx -t 30 -3 -g -d
ILO2_HEALTH2 OK - (ProLiant DL380p Gen8 - Serial: xxxxxxxx - iLO FW 2.50 Sep 23 2016 - Servername: xxxxxxxx) Temperatures: 01-Front_Ambient (OK): 26, 02-CPU_1 (OK): 40, 07-P1_DIMM_10-12 (OK): 39, 12-HD_Max (OK): 35, 13-Chipset (OK): 52, 14-P/S_1 (OK): 40, 15-P/S_2 (OK): 41, 16-P/S_2_Zone (OK): 42, 17-VR_P1 (OK): 47, 18-VR_P2 (OK): 45, 19-VR_P1_Mem (OK): 43, 20-VR_P1_Mem (OK): 44, 21-VR_P2_Mem (OK): 43, 22-VR_P2_Mem (OK): 41, 23-VR_P1Vtt_Zone (OK): 42, 24-VR_P2Vtt_Zone (OK): 42, 25-HD_Controller (OK): 85, 26-iLO_Zone (OK): 46, 27-LOM_Card (OK): 65, 34-PCI_1_Zone (OK): 39, 35-PCI_2_Zone (OK): 40, 36-PCI_3_Zone (OK): 40, 40-I/O_Board_1 (OK): 42, 42-VR_P1_Zone (OK): 38, 43-BIOS_Zone (OK): 54, 44-System_Board (OK): 43, 45-SuperCap_Max (OK): 34, 46-Chipset_Zone (OK): 45, 47-Battery_Zone (OK): 45, 48-I/O_Zone (OK): 45, 49-Sys_Exhaust (OK): 42, 50-Sys_Exhaust (OK): 46 | 01-Front_Ambient=26;50;55 16-P/S_2_Zone=42;75;80 17-VR_P1=47;115;120 18-VR_P2=45;115;120 19-VR_P1_Mem=43;115;120 20-VR_P1_Mem=44;115;120 21-VR_P2_Mem=43;115;120 22-VR_P2_Mem=41;115;120 23-VR_P1Vtt_Zone=42;90;95 24-VR_P2Vtt_Zone=42;90;95 26-iLO_Zone=46;90;95 34-PCI_1_Zone=39;70;75 35-PCI_2_Zone=40;70;75 36-PCI_3_Zone=40;70;75 40-I/O_Board_1=42;75;80 42-VR_P1_Zone=38;95;100 43-BIOS_Zone=54;90;95 44-System_Board=43;80;85 46-Chipset_Zone=45;75;80 47-Battery_Zone=45;75;80 48-I/O_Zone=45;75;80 49-Sys_Exhaust=42;75;80 50-Sys_Exhaust=46;75;80
I know that doesn't look clean, but I encourage anyone with an iLO to compare the -v output with one that excludes -v.
Finally, this iLO is set up with TLS enabled but I leave off the -s and it does still pull the data. To get around the fact that this is inherently insecure, I have a read only account on the ilo with zero special permissions. I use that account to query. The TLS error may be due to a cert mismatch, but that's really beyond the ability to diagnose with current output.
Re: Issue in monitoring Hardware health using check_ilo2_hea
Posted: Wed Aug 23, 2017 5:50 am
by bsivavani
Please find Lynx output.
[root@Nagios ]# lynx XXESXIhostXX
Looking up XXESXIhostXX first
Can't Access `
http://XXESXIhostXX/'
Alert!: Unable to access document.
lynx: Can't access startfile
[root@Nagios ]#
Re: Issue in monitoring Hardware health using check_ilo2_hea
Posted: Wed Aug 23, 2017 8:58 am
by scottwilkerson
Have you tried removing the -s flag like @gwakem suggested?
gwakem wrote:If I remove the forcing of SSL/TLS via the -s flag, I get a full readout of all data on the ilo as expected. If I then remove the -v flag (for unformatted verbosity), I get a much cleaner readout with perfdata included:
Re: Issue in monitoring Hardware health using check_ilo2_hea
Posted: Wed Aug 23, 2017 11:49 am
by bsivavani
Yes. I tried.
[root@nagios ]# /usr/local/nagios/libexec/check_ilo2_health.pl -H XXXX -u XXXX -p XXXX -t 30 -3 -g -d
Use of uninitialized value $ln in length at /usr/local/nagios/libexec/check_ilo2_health.pl line 893.
ILO2_HEALTH UNKNOWN - ERROR: No parseable output.
[root@nagios ]#
Re: Issue in monitoring Hardware health using check_ilo2_hea
Posted: Wed Aug 23, 2017 3:44 pm
by dwhitfield
Can you post a screenshot of the URL you use to log into the ilo web interface? It looks like you are using the wrong URL. Perhaps there is a proxy or load-balancer in front of it?
Can you also try using https before the server in lynx?