Firmware Bug with SNMP (ILO5 since FW 3.05?) regarding System Status OIDs

[SearchForTheCod]

Hello

We have many systems in monitoring via SNMP and since upgrade from 3.03 to newer FW versions on a Gen10 ILO5 system, we ran into serveral problems regarding SNMP.

Previously the the following OIDs contained Overall Status information on all elements:

But since Firmware > 3.05 these status "array' return only zeros. 

Name/OID: .1.3.6.1.2.1.1.1.0; Value (OctetString): Integrated Lights-Out 5 3.07 Aug 09 2024

0x00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

In comparison to the return prior 3.05,

Name/OID: .1.3.6.1.4.1.232.11.2.10.7.0; Value (OctetString): 0x02 02 02 02 02 02 02 02 02 02 00 02 00 00 01 02 02 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Is this known? is this a bug in the firmware like here? Any help / ideas apprechiated

https://community.hpe.com/t5/proliant-servers-ml-dl-sl/firmware-bug-with-snmp-ilo-5-3-0-0-proliant-dl380-gen10-hpe/td-p/7204699

[support_s]

System recommended content:

1. HPE iLO 4 2.82 User Guide | iLO SNMP management

2. HPE iLO 5 Scripting and Command Line Guide | Non-iLO firmware commands

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[SearchForTheCod]

this does not help @support_s . This is just basic information on how to use SNMP, not about the bug mentioned above..

[TVVJ]

Hello,

Please test by installing the latest version of the MIB kit and see if it helps.

Regards,

[SearchForTheCod]

We did! MIBs are not something "to install". They are just documents which OIDs can be called. This does not change that the values a device delivers...

[Suvamay]

Please try with latest ILO5 Version 
https://internal.support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-2dc80c4ae4b943fa&tab=releaseNotes

[SearchForTheCod]

"Name/OID: .1.3.6.1.2.1.1.1.0; Value (OctetString): Integrated Lights-Out 5 3.07 Aug 09 2024"

I provided the snmp walk resulst and as you can see, the latest firmware is installed already, but the range this error occurs is since 3.05, but it also includes all latest versions..

[Suvamay]

Can you please log a support ticket with HPE 

[Throwaway]

wondering if we are the only ones seeing this issue?? no one else using snmp?
did you get anywhere with HPE support?

[SearchForTheCod]

Yeah , weird. You can see the status here.. Besides KI bot help with not helpful advice nothing. I adviced the customer to make a support ticker, but this should be a global issue. 

[Henkezan]

Just posting here to bump thread. We ran into this issue today after applying latest 2024.09 SPP and powercycle of host(s). I've pushed latest SPP to many machines, but rarely do powercycle..
Tested upgrading to latest 3.09 (with powercycle aswell), but that did not solve it.
Downgrading iLO to 3.04 solved it (no powercycle needed) .

# snmpwalk -v2c -c public iloip 1.3.6.1.4.1.232.11.2.10.7
SNMPv2-SMI::enterprises.232.11.2.10.7.0 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

downgrade...:
# snmpwalk -v2c -c public iloip 1.3.6.1.4.1.232.11.2.10.7
SNMPv2-SMI::enterprises.232.11.2.10.7.0 = Hex-STRING: 02 02 02 02 02 02 02 02 02 01 00 02 00 00 01 02
02 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00

/Henrik

[SearchForTheCod]

Thanks for clarifying its an ongoing issue still and not resolved in any newer firmware!