- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- ML30 Gen10 ILO5 SNMP is different from ILO5's scr...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2023 11:43 AM - last edited on 04-17-2023 05:21 PM by support_s
04-06-2023 11:43 AM - last edited on 04-17-2023 05:21 PM by support_s
ML30 Gen10 ILO5 SNMP is different from ILO5's screens.
This is a bit long winded, the upshot is, something, somewhere is buggy.
I have just spent a few hours puzzling over this mess, so I thought I would see if anyone else has noticed or can provide an explanation.
That or I am doing something wrong and should clearly go play with Dell hardware instead. If anyone has any insights into what I am doing wrong, please let me know. Note, I didn't try the RestAPI stuff, so I have no idea if that gives a different answer.
All of this should be trivially reproducible even if I was running a <cough-splurt> SUPPORTED OPERATING SYSTEM. I get the same results from a nearby box running ubuntu pointing at this server.
Exhibit 1, the Temperatures Page from an ML30 Gen10 ilo5 2.78
Exhibit 2, the lightly formatted output of telegraf running on the same server, looking at the ILO and specifically: "cpqHeTemperatureIndex, cpqHeTemperatureCelcius, cpqHeTemperatureThreshold" taken within a few seconds of the above screenshot.
Index=1, cpqHeTemperatureLocale=11 cpqHeTemperatureCelsius=23i, cpqHeTemperatureThreshold=42i ## 01-Inlet Ambient
Index=2, cpqHeTemperatureLocale=6 cpqHeTemperatureCelsius=40i, cpqHeTemperatureThreshold=0i ## 02-CPU
Index=3, cpqHeTemperatureLocale=7 cpqHeTemperatureCelsius=33i, cpqHeTemperatureThreshold=87i ## 03-P1 DIMM
Index=4, cpqHeTemperatureLocale=3 cpqHeTemperatureCelsius=35i, cpqHeTemperatureThreshold=60i ## 04-HD Max
Index=5, cpqHeTemperatureLocale=3 cpqHeTemperatureCelsius=41i, cpqHeTemperatureThreshold=105i ## 05-Chipset
Index=6, cpqHeTemperatureLocale=10 cpqHeTemperatureCelsius=40i, cpqHeTemperatureThreshold=0i ## 06-PS1
Index=7, cpqHeTemperatureLocale=10 cpqHeTemperatureCelsius=40i, cpqHeTemperatureThreshold=0i ## 07-PS2
Index=8, cpqHeTemperatureLocale=10 cpqHeTemperatureCelsius=35i, cpqHeTemperatureThreshold=0i ## 08-PS1 Inlet
Index=9, cpqHeTemperatureLocale=10 cpqHeTemperatureCelsius=36i, cpqHeTemperatureThreshold=0i ## 09-PS2 Inlet
Index=10, cpqHeTemperatureLocale=10 cpqHeTemperatureCelsius=30i, cpqHeTemperatureThreshold=75i ## 10-PS Zone
Index=11, cpqHeTemperatureLocale=3 cpqHeTemperatureCelsius=31i, cpqHeTemperatureThreshold=115i ## 11-VR P1
Index=13, cpqHeTemperatureLocale=3 cpqHeTemperatureCelsius=67i, cpqHeTemperatureThreshold=105i ## 14-BMC
Index=14, cpqHeTemperatureLocale=3 cpqHeTemperatureCelsius=33i, cpqHeTemperatureThreshold=100i ##
Index=15, cpqHeTemperatureLocale=5 cpqHeTemperatureCelsius=61i, cpqHeTemperatureThreshold=100i ##
Index=19, cpqHeTemperatureLocale=5 cpqHeTemperatureCelsius=35i, cpqHeTemperatureThreshold=60i ## 20-PCI 1 Zone
Index=20, cpqHeTemperatureLocale=5 cpqHeTemperatureCelsius=36i, cpqHeTemperatureThreshold=64i ## 21-PCI 2 Zone
Index=21, cpqHeTemperatureLocale=5 cpqHeTemperatureCelsius=33i, cpqHeTemperatureThreshold=62i ## 22-PCI 3 Zone
Index=22, cpqHeTemperatureLocale=5 cpqHeTemperatureCelsius=32i, cpqHeTemperatureThreshold=61i ## 23-PCI 4 Zone
Index=24, cpqHeTemperatureLocale=3 cpqHeTemperatureCelsius=31i, cpqHeTemperatureThreshold=60i ## 26-M2
Index=25, cpqHeTemperatureLocale=3 cpqHeTemperatureCelsius=34i, cpqHeTemperatureThreshold=60i ##
Index=26, cpqHeTemperatureLocale=3 cpqHeTemperatureCelsius=32i, cpqHeTemperatureThreshold=60i ##
Index=27, cpqHeTemperatureLocale=3 cpqHeTemperatureCelsius=29i, cpqHeTemperatureThreshold=60i ##
I've added the ones I have been able to positively identify based on temp/threshold
And just for completeness, Exhibit 3, trimming out evertyhing except these
snmpwalk -m +ALL -M /usr/local/share/snmp/mibs/ -v 2c -c public ml30-ilo . > ml30b.txt
cpqHeTemperatureLocale.0.1 = INTEGER: ambient(11)
cpqHeTemperatureLocale.0.2 = INTEGER: cpu(6)
cpqHeTemperatureLocale.0.3 = INTEGER: memory(7)
cpqHeTemperatureLocale.0.4 = INTEGER: system(3)
cpqHeTemperatureLocale.0.5 = INTEGER: system(3)
cpqHeTemperatureLocale.0.6 = INTEGER: powerSupply(10)
cpqHeTemperatureLocale.0.7 = INTEGER: powerSupply(10)
cpqHeTemperatureLocale.0.8 = INTEGER: powerSupply(10)
cpqHeTemperatureLocale.0.9 = INTEGER: powerSupply(10)
cpqHeTemperatureLocale.0.10 = INTEGER: powerSupply(10)
cpqHeTemperatureLocale.0.11 = INTEGER: system(3)
cpqHeTemperatureLocale.0.13 = INTEGER: system(3)
cpqHeTemperatureLocale.0.14 = INTEGER: system(3)
cpqHeTemperatureLocale.0.15 = INTEGER: ioBoard(5)
cpqHeTemperatureLocale.0.19 = INTEGER: ioBoard(5)
cpqHeTemperatureLocale.0.20 = INTEGER: ioBoard(5)
cpqHeTemperatureLocale.0.21 = INTEGER: ioBoard(5)
cpqHeTemperatureLocale.0.22 = INTEGER: ioBoard(5)
cpqHeTemperatureLocale.0.24 = INTEGER: system(3)
cpqHeTemperatureLocale.0.25 = INTEGER: system(3)
cpqHeTemperatureLocale.0.26 = INTEGER: system(3)
cpqHeTemperatureLocale.0.27 = INTEGER: system(3)
cpqHeTemperatureCelsius.0.1 = INTEGER: 24
cpqHeTemperatureCelsius.0.2 = INTEGER: 40
cpqHeTemperatureCelsius.0.3 = INTEGER: 33
cpqHeTemperatureCelsius.0.4 = INTEGER: 35
cpqHeTemperatureCelsius.0.5 = INTEGER: 42
cpqHeTemperatureCelsius.0.6 = INTEGER: 40
cpqHeTemperatureCelsius.0.7 = INTEGER: 40
cpqHeTemperatureCelsius.0.8 = INTEGER: 35
cpqHeTemperatureCelsius.0.9 = INTEGER: 36
cpqHeTemperatureCelsius.0.10 = INTEGER: 30
cpqHeTemperatureCelsius.0.11 = INTEGER: 31
cpqHeTemperatureCelsius.0.13 = INTEGER: 69
cpqHeTemperatureCelsius.0.14 = INTEGER: 33
cpqHeTemperatureCelsius.0.15 = INTEGER: 61
cpqHeTemperatureCelsius.0.19 = INTEGER: 35
cpqHeTemperatureCelsius.0.20 = INTEGER: 36
cpqHeTemperatureCelsius.0.21 = INTEGER: 33
cpqHeTemperatureCelsius.0.22 = INTEGER: 32
cpqHeTemperatureCelsius.0.24 = INTEGER: 31
cpqHeTemperatureCelsius.0.25 = INTEGER: 34
cpqHeTemperatureCelsius.0.26 = INTEGER: 32
cpqHeTemperatureCelsius.0.27 = INTEGER: 29
cpqHeTemperatureThreshold.0.1 = INTEGER: 42
cpqHeTemperatureThreshold.0.2 = INTEGER: 0
cpqHeTemperatureThreshold.0.3 = INTEGER: 87
cpqHeTemperatureThreshold.0.4 = INTEGER: 60
cpqHeTemperatureThreshold.0.5 = INTEGER: 105
cpqHeTemperatureThreshold.0.6 = INTEGER: 0
cpqHeTemperatureThreshold.0.7 = INTEGER: 0
cpqHeTemperatureThreshold.0.8 = INTEGER: 0
cpqHeTemperatureThreshold.0.9 = INTEGER: 0
cpqHeTemperatureThreshold.0.10 = INTEGER: 75
cpqHeTemperatureThreshold.0.11 = INTEGER: 115
cpqHeTemperatureThreshold.0.13 = INTEGER: 105
cpqHeTemperatureThreshold.0.14 = INTEGER: 100
cpqHeTemperatureThreshold.0.15 = INTEGER: 100
cpqHeTemperatureThreshold.0.19 = INTEGER: 60
cpqHeTemperatureThreshold.0.20 = INTEGER: 64
cpqHeTemperatureThreshold.0.21 = INTEGER: 62
cpqHeTemperatureThreshold.0.22 = INTEGER: 61
cpqHeTemperatureThreshold.0.24 = INTEGER: 60
cpqHeTemperatureThreshold.0.25 = INTEGER: 60
cpqHeTemperatureThreshold.0.26 = INTEGER: 60
cpqHeTemperatureThreshold.0.27 = INTEGER: 60
Exhibit 4, mouse over the PCI 1 card:
Is it unrealistic to expect SNMP to give the same results as the ILO5 screen?
For example.
- ILO says LOM is 53'c, nothing is even close on SNMP.
- SNMP says 14 is 33'c, is that so?
- ILO says PCI 1 is 44'c, SNMP hasn't a clue, mouse over says 64'c.
- SNMP says 14 + 15 have a Threshold of 100'c, ILO has nothing with a threshold of 100'c
- ILO says 26, 27, 28, 29 are all M2 Zone. This is rather neat as I didn't see 4 M2 zones at all, only the ILO card one. It's a bit moot, I have no M2 card, just the ILO's dedicated port card.
- ILO has Critical temperatures, SNMP only has Cautions.
I would suspect that this is a feature, likely a long standing one that exists simply because no-one tried compare and contrast.
- Tags:
- Port
- Prolaint server
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2023 01:01 AM
04-12-2023 01:01 AM
Re: ML30 Gen10 ILO5 SNMP is different from ILO5's screens.
Greetings!
Confirm the Operating System being used for testing.
Configure SNMP by referring to the web link provided: https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=emr_na-a00026111en_us
Ensure the latest MIBs are installed: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c04272529
Update the iLO firmware to the latest revision, which is 2.81.
Verify the functionality of another agent, apart from telegraf.
I am an HPE employee.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
![Accept or Kudo](/html/assets/hpe_banner_SME_signature.png)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2023 03:58 AM - last edited on 04-14-2023 03:17 AM by Sunitha_Mod
04-12-2023 03:58 AM - last edited on 04-14-2023 03:17 AM by Sunitha_Mod
Re: ML30 Gen10 ILO5 SNMP is different from ILO5's screens.
1) Confirm the Operating system being used.
This is Freebsd 13.1, but that is neither here no there.
I have a spare ML10 but until I can completely erase the firmware and turn it back into an HP, it's a boatanchor.
2) Configure SNMP ... link
Because you do not support FreeBSD, there is in AMS to install, As such, I expect to see the elements on the LEFT column under that URL.
3) Ensure the latest MIBs are installed.
The second URL gives me "upd11,80mib.tar.gz" Which is full of lots of files. I'll get to that in a second.
4) Update the ILO firmware...
Update the ILO from 2.78 to 2.81. Note that the Revision History says nothing what so ever about SNMP being wrong.
5) Verify the functionality of another agent, apart from telegraph.
I do hope you are prepared to lose a point. Nothing has changed.
BELOW, a screenshot from the ILO after being updated. Compare with the original one, a few minor changes in ambient.
next, an agent other than telegraf.
SNMPWALK.
snmpwalk -m +ALL -M /usr/local/share/snmp/mibs/ -v 2c -c public ml30-ilo . > ml30c.txt
A quick diff with 2.78 shows no real changes but here are the relevant ones:
< SNMPv2-MIB::sysDescr.0 = STRING: Integrated Lights-Out 5 2.81 Mar 07 2023
> SNMPv2-MIB::sysDescr.0 = STRING: Integrated Lights-Out 5 2.78 Dec 16 2022
< DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (50300) 0:08:23.00
> DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (166967600) 19 days, 7:47:56.00
No changes in temperatures reported.
CPQHLTH-MIB::cpqHeTemperatureLocale.0.1 = INTEGER: ambient(11)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.2 = INTEGER: cpu(6)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.3 = INTEGER: memory(7)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.4 = INTEGER: system(3)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.5 = INTEGER: system(3)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.6 = INTEGER: powerSupply(10)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.7 = INTEGER: powerSupply(10)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.8 = INTEGER: powerSupply(10)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.9 = INTEGER: powerSupply(10)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.10 = INTEGER: powerSupply(10)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.11 = INTEGER: system(3)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.13 = INTEGER: system(3)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.14 = INTEGER: system(3)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.15 = INTEGER: ioBoard(5)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.19 = INTEGER: ioBoard(5)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.20 = INTEGER: ioBoard(5)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.21 = INTEGER: ioBoard(5)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.22 = INTEGER: ioBoard(5)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.24 = INTEGER: system(3)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.25 = INTEGER: system(3)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.26 = INTEGER: system(3)
CPQHLTH-MIB::cpqHeTemperatureLocale.0.27 = INTEGER: system(3)
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.1 = INTEGER: 25
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.2 = INTEGER: 40
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.3 = INTEGER: 34
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.4 = INTEGER: 35
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.5 = INTEGER: 42
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.6 = INTEGER: 40
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.7 = INTEGER: 40
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.8 = INTEGER: 35
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.9 = INTEGER: 35
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.10 = INTEGER: 31
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.11 = INTEGER: 31
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.13 = INTEGER: 68
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.14 = INTEGER: 34
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.15 = INTEGER: 62
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.19 = INTEGER: 36
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.20 = INTEGER: 38
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.21 = INTEGER: 35
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.22 = INTEGER: 34
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.24 = INTEGER: 33
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.25 = INTEGER: 35
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.26 = INTEGER: 33
CPQHLTH-MIB::cpqHeTemperatureCelsius.0.27 = INTEGER: 30
Note, if the LOM is at 54'c, it doesn't want to tell anyone.
Have any of the MIBS changed? That's a bit of a merge nightmare as there are lots of filename differences. But no real change from the above.
SSH to the ILO, that's not telegraf is it?
This is the sensors from ssh, you can see that DeviceID matches except for 15-LOM, where the temperature reported by SSH is 34 but the image shows 54.
/system1/sensor1
Targets
Properties
DeviceID=01-Inlet Ambient
ElementName=Ambient
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=25
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=42
oemHPE_CriticalValue=46
Verbs
cd version exit show
/system1/sensor2
Targets
Properties
DeviceID=02-CPU 1
ElementName=CPU
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=40
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=Not Applicable
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor3
Targets
Properties
DeviceID=03-P1 DIMM 1-4
ElementName=Memory
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=34
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=87
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor4
Targets
Properties
DeviceID=04-HD Max
ElementName=System
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=35
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=60
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor5
Targets
Properties
DeviceID=05-Chipset
ElementName=System
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=43
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=105
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor6
Targets
Properties
DeviceID=06-P/S 1
ElementName=Power Supply
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=40
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=Not Applicable
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor7
Targets
Properties
DeviceID=07-P/S 2
ElementName=Power Supply
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=40
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=Not Applicable
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor8
Targets
Properties
DeviceID=08-P/S 1 Inlet
ElementName=Power Supply
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=36
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=Not Applicable
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor9
Targets
Properties
DeviceID=09-P/S 2 Inlet
ElementName=Power Supply
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=35
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=Not Applicable
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor10
Targets
Properties
DeviceID=10-P/S Zone
ElementName=Power Supply
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=31
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=75
oemHPE_CriticalValue=80
Verbs
cd version exit show
/system1/sensor11
Targets
Properties
DeviceID=11-VR P1
ElementName=System
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=32
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=115
oemHPE_CriticalValue=120
Verbs
cd version exit show
/system1/sensor12
Targets
Properties
DeviceID=13-Stor Batt
ElementName=System
OperationalStatus=Not Installed
RateUnits=Celsius
CurrentReading=N/A
SensorType=Temperature
HealthState=Not Installed
oemHPE_CautionValue=Not Applicable
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor13
Targets
Properties
DeviceID=14-BMC
ElementName=System
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=68
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=105
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor14
Targets
Properties
DeviceID=15-LOM
ElementName=System
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=34
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=100
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor15
Targets
Properties
DeviceID=16-PCI 1
ElementName=I/O Board
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=62
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=100
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor16
Targets
Properties
DeviceID=17-PCI 2
ElementName=I/O Board
OperationalStatus=Not Installed
RateUnits=Celsius
CurrentReading=N/A
SensorType=Temperature
HealthState=Not Installed
oemHPE_CautionValue=Not Applicable
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor17
Targets
Properties
DeviceID=18-PCI 3
ElementName=I/O Board
OperationalStatus=Not Installed
RateUnits=Celsius
CurrentReading=N/A
SensorType=Temperature
HealthState=Not Installed
oemHPE_CautionValue=Not Applicable
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor18
Targets
Properties
DeviceID=19-PCI 4
ElementName=I/O Board
OperationalStatus=Not Installed
RateUnits=Celsius
CurrentReading=N/A
SensorType=Temperature
HealthState=Not Installed
oemHPE_CautionValue=Not Applicable
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor19
Targets
Properties
DeviceID=20-PCI 1 Zone
ElementName=I/O Board
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=36
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=60
oemHPE_CriticalValue=65
Verbs
cd version exit show
/system1/sensor20
Targets
Properties
DeviceID=21-PCI 2 Zone
ElementName=I/O Board
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=38
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=64
oemHPE_CriticalValue=69
Verbs
cd version exit show
/system1/sensor21
Targets
Properties
DeviceID=22-PCI 3 Zone
ElementName=I/O Board
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=35
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=62
oemHPE_CriticalValue=67
Verbs
cd version exit show
/system1/sensor22
Targets
Properties
DeviceID=23-PCI 4 Zone
ElementName=I/O Board
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=34
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=61
oemHPE_CriticalValue=66
Verbs
cd version exit show
/system1/sensor23
Targets
Properties
DeviceID=24-M2
ElementName=System
OperationalStatus=Not Installed
RateUnits=Celsius
CurrentReading=N/A
SensorType=Temperature
HealthState=Not Installed
oemHPE_CautionValue=Not Applicable
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor24
Targets
Properties
DeviceID=26-M2 Zone
ElementName=System
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=33
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=60
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor25
Targets
Properties
DeviceID=27-M2 Zone
ElementName=System
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=35
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=60
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor26
Targets
Properties
DeviceID=28-M2 Zone
ElementName=System
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=34
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=60
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor27
Targets
Properties
DeviceID=29-M2 Zone
ElementName=System
OperationalStatus=Ok
RateUnits=Celsius
CurrentReading=30
SensorType=Temperature
HealthState=Ok
oemHPE_CautionValue=60
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
/system1/sensor28
Targets
Properties
DeviceID=30-AHCI HD Max
ElementName=System
OperationalStatus=Not Installed
RateUnits=Celsius
CurrentReading=N/A
SensorType=Temperature
HealthState=Not Installed
oemHPE_CautionValue=Not Applicable
oemHPE_CriticalValue=Not Applicable
Verbs
cd version exit show
As they say, a picture is worth 1000 words.
Spot the difference.
All these values were obtained from the ILO directly. OS INDEPENDENT.
Left copied from the ILO web page. Right, from SSH.
simple excel.
My statement stands. "Something, somewhere is buggy."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2023 05:14 PM
04-17-2023 05:14 PM
Re: ML30 Gen10 ILO5 SNMP is different from ILO5's screens.
Greetings!
If you see mismatch in temperature readings across iLO SSH and GUI, then kindly log a support ticket and share logs for further insvestigation.
I am an HPE employee.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
![Accept or Kudo](/html/assets/hpe_banner_SME_signature.png)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2023 11:47 PM - edited 04-19-2023 11:48 PM
04-19-2023 11:47 PM - edited 04-19-2023 11:48 PM
Re: ML30 Gen10 ILO5 SNMP is different from ILO5's screens.
Query ID 27787, Case 5372674064
I think.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-24-2023 03:36 AM
04-24-2023 03:36 AM
Re: ML30 Gen10 ILO5 SNMP is different from ILO5's screens.
I guess the case number you mentioned is a free case and not tied to the serial numbers of your product because serial number is confidential information and should not be shared in public forums. The reason why they do not show up in support center also. , So they recommend calling tech support to perform proper analysis. I got this info and I hope this helps you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2023 10:32 AM
07-26-2023 10:32 AM
Re: ML30 Gen10 ILO5 SNMP is different from ILO5's screens.
I'm seeing similar things on HPE ProLiant Gen10 servers with iLO5. Case number is 5374517319.
Apparently this is expected. According to the support engineer,
"I checked with the engineering team regarding this issue and as per there update.
The Temperatures on ILO5 GUI and SNMP MIB would not match.
The reason being, ILO5 used a Adjusted / Optimized Temperature readings than the RAW Temperature readings from the temperature sensors.ILO5 GUI is an aggregation of different sensor outputs. There will be a slight variation on the values. This is normal.
We would always recommend to rely on ILO temp than any sensor results from SNMP or third party tools. ILO better knows HPE Hardware
"
I was a bit surprised by this, as SNMP is an age-old protocol which you would think would have an accurate value regardless of what new features are added.
I asked to see if I could be provided with whatever the adjusted/optimized temperature reading formula is, but the response I got was "This is something Internal Logic to ILO5 for managing the server cooling. I guess, there is nothing we can share on this aspect.".
The recommendation was to use Redfish/the RESTful API to get the temperature values: https://support.hpe.com/hpesc/public/docDisplay?docId=c04423967
From the monitoring perspective, I now need to look into how to build these temperature checks in-house to get a reliable reading, instead of using built-in SNMP checks that are offered by practically all monitoring vendors out of the box. Totally understand the desire to improve/attempt to replace an older technology but at what cost to the customer?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2023 12:47 AM
07-28-2023 12:47 AM
Re: ML30 Gen10 ILO5 SNMP is different from ILO5's screens.
I appreciate you trying to find answers too.
It is unusual that the ILO gives different results depending on how you ask it. Different values, or even completely fictitious sensors.
The reasoning seems bizarre since this implies that the ILO is about as honest and trustworthy as a voting machine.
And why would I want to use a heavyweight Redfish API that seems to be part of the HTTP with everything cult when I already have working SNMP from telegraf. To quote from that documentation: "The RESTfulAPI is designed using a REST architecture called HATEOS" They have that right.
Most people would have no need for Redfish in any shape, size or form, it's too complicated and too painful for J. Random Citizen.
And that's before we even mention the fictitious sensors showing up in the web interface *and* different ones in SNMP.