It is now with 2.3.0 very easy to try if it is working with Redfish API as the needed Python modules and the Redfish MKP is included inside CMK.
The only problem what i saw was a very inconsistent behavior, between different iLO5 systems. All had the same 3.04 firmware but shown different behaviors.
It looks like that different used storage controllers, have the most impact if it is running smoothly or not.
In the end i would say, if you see your storage controller inside iLO web interface then you can also retrieve the data over the REST API. I had also 1 or 2 systems where the storage controller data was missing inside web and then there where also no data over API.
More than 3 months after HPE introduced this problem, and still no final fix. Amazing.
If there is one hardware piece you would like to know a correct status of, it’s your storage controller…
Support for Fan speed in terms of percentage from SNMP OID Get and Walk.
Fixes for specific SNMP OIDs for RDE capable storage controllers for controller, physical drive, and logical drive properties.
I can acknowledge that some drives a are back. But there are a lot of changes in the dicovery. And the following services changed to crashed (I think it’s about the changes with the “Support for Fan speed”:
I can confirm this, ILO5 firmware version 3.05 still has issues.
The drives (logical & physical are now detected correctly.
But the hardware controller & fan checks now crash.
Amazing that this takes so long to fix. The quality of the releases is below par.
Hi folks,
I am currently looking into this. The ‘fans’-map is not the only one that needs updating; I know I have to exend this one with ~15 more entries. But I doubt that we have 30+ distict named descriptions of how fast the fan is going . @KluthR , can you elaborate? Or, even better, point me to resources? It makes very much sense, but how do you know it’s percentage?
According to HPE’s latest MIBs, the OID in question should still report the states other(1), normal(2) and high(3), rather than percentage values. It seems that their latest firmware release introduced some bugs though:
“REMOVED The Release version of iLO 5 v3.05 has exposed a bug, when the host server is installed with NS204i boot controllers. A new iLO 5 version fixing the issue will be released in the next couple of days.”
Therefore, the situation is rather unstable at the moment. We’ve already contacted HPE. Until we get further information from them, we’ll stick to the information from the official MIB.
I realized that from time to time I had ‘not monitored drives’ in CheckMK from my ILOs. They probably appeared magically, because nobody changed the drives in the servers.
Hi, we are still waiting for a definite statement from HPE.
Unfortunately, they introduced breaking changes with their latest firmware updates which aren’t documented in their latest MIB. At the moment, they are investigating if these changes have been applied intentionally or not.
Therefore, the ball is in their court at the moment. We’ll keep you posted – as soon as we receive any further feedback from them, we’ll act on it.