centreon-plugins
centreon-plugins copied to clipboard
[hardware::server::hp::proliant::snmp::plugin] RAID controller check for ILO5 (firmware 3.0) does not work in "hardware" mode
Hello.
For the plugin "hardware::server::hp::proliant::snmp::plugin" in "hardware" mode, after updating the ILO5 microcode to the latest version 3.00, polling the SmartArray RAID controller stops working
# ./centreon_plugins.pl' '--plugin=hardware::server::hp::proliant::snmp::plugin' '--mode=hardware' '--change-perfdata' '.*,,eval(%(label) =~ s/(\ |\/)/_/g)' '--change-perfdata' '.*,,eval(%(label) =~ s/#hardware//g)' '--change-perfdata' '.*,,eval(%(label) =~ s/(\d)[.](\d)/\1_\2/g)' '--filter' 'psu,0.3' '--filter' 'psu,0.4' '--filter' 'fca,0' '--filter' 'fca,1' '--filter' 'fca,2' '--filter' 'fca,3' '--filter-perfdata-adv' 'not (%(label) =~ /\.(count)/)' '--filter-uom' 'null' '--hostname' 'ilo071.holding.com' '--snmp-community' 'public' '--snmp-force-getnext' '--snmp-version' '2c'
UNKNOWN: da logical drive '0.1' is other - da physical drive '0.3' is other - da physical drive '0.4' is other |
'0_1.powersupply.power.watt'=105;;1600;; '0_1.powersupply.voltage.volt'=222;;;; '0_2.powersupply.power.watt'=166;;1600;; '0_2.powersupply.voltage.volt'=223;;;; '0_1~ambient.temperature.celsius'=21;;0:42;; '0_2~cpu.temperature.celsius'=40;;0:70;; '0_3~cpu.temperature.celsius'=40;;0:70;; '0_6~memory.temperature.celsius'=36;;0:90;; '0_8~memory.temperature.celsius'=37;;0:90;; '0_10~memory.temperature.celsius'=36;;0:90;; '0_12~memory.temperature.celsius'=35;;0:90;; '0_22~system.temperature.celsius'=35;;0:60;; '0_24~system.temperature.celsius'=23;;0:60;; '0_26~system.temperature.celsius'=34;;0:115;; '0_27~system.temperature.celsius'=36;;0:115;; '0_28~system.temperature.celsius'=27;;0:115;; '0_29~system.temperature.celsius'=27;;0:115;; '0_30~system.temperature.celsius'=29;;0:115;; '0_31~system.temperature.celsius'=30;;0:115;; '0_32~system.temperature.celsius'=29;;0:115;; '0_33~system.temperature.celsius'=29;;0:115;; '0_34~system.temperature.celsius'=25;;0:115;; '0_35~system.temperature.celsius'=26;;0:115;; '0_36~system.temperature.celsius'=26;;0:115;; '0_37~system.temperature.celsius'=27;;0:115;; '0_38~ambient.temperature.celsius'=23;;0:60;; '0_39~system.temperature.celsius'=23;;0:75;; '0_40~system.temperature.celsius'=40;;0:100;; '0_41~system.temperature.celsius'=58;;0:110;; '0_42~system.temperature.celsius'=30;;0:90;; '0_43~system.temperature.celsius'=48;;0:100;; '0_44~system.temperature.celsius'=29;;0:85;; '0_45~ioBoard.temperature.celsius'=56;;0:100;; '0_46~system.temperature.celsius'=33;;0:90;; '0_48~ioBoard.temperature.celsius'=29;;0:90;; '0_50~ioBoard.temperature.celsius'=30;;0:90;; '0_52~ioBoard.temperature.celsius'=30;;0:90;; '0_53~ioBoard.temperature.celsius'=57;;0:100;; '0_54~ioBoard.temperature.celsius'=28;;0:90;; '0_56~ioBoard.temperature.celsius'=29;;0:90;; '0_58~ioBoard.temperature.celsius'=29;;0:90;; '0_63~system.temperature.celsius'=30;;0:75;; '0_64~powerSupply.temperature.celsius'=23;;0:0;; '0_65~powerSupply.temperature.celsius'=30;;0:0;; '0_68~powerSupply.temperature.celsius'=40;;0:0;; '0_69~powerSupply.temperature.celsius'=40;;0:0;; '0_72~powerSupply.temperature.celsius'=32;;0:75;; '0_73~powerSupply.temperature.celsius'=28;;0:100;; '0_74~system.temperature.celsius'=29;;0:75;; '0_75~cpu.temperature.celsius'=39;;0:0;; '0_76~cpu.temperature.celsius'=37;;0:0;;
If we downgrade the iLO5 microcode to the previous version 2.99, then the problem disappears and the plugin works and shows the status of the RAID controller and disks.
There is a suspicion that in the latest version 3.0 iLO5 microcode there have been some changes in SNMP
# snmpwalk -ObentU -v 2c -c public iLo5_2_99_server 1.3.6.1.4.1.232.3.2.2.1.1.6.0
.1.3.6.1.4.1.232.3.2.2.1.1.6.0 = INTEGER: 2
# snmpwalk -ObentU -v 2c -c public iLo5_3_00_server 1.3.6.1.4.1.232.3.2.2.1.1.6.0
.1.3.6.1.4.1.232.3.2.2.1.1.6.0 = No Such Instance currently exists at this OID
What can be done about this problem?
Last HPE iLO5 firmware 3.04 (19 Apr 2024) - problem persists
It appears that the new ILO5 microcode version 3.05 (21 Jun 2024) resolves the issue.