snmpwalk to "1.3.6.1.4.1.232" failed on HP ProLiant DL360 Gen9 with Windows

[PeggyQi_2021]

Hardware: HP ProLiant DL360 Gen9 

OS: Windows Server 2019

When I ran snmpwalk command to this Windows server for OID "1.3.6.1.4.1.232" or its sub-OIDs I got "Timeout: No Response from xx.xx.xx.xx". After that snmpwalk to other OIDs would also fail with timeout. Around 90 seconds later, snmpwalk to other OIDs would work but once I ran snmpwalk to "1.3.6.1.4.1.232" or its sub-OIDs, every request would result in timeout again.

Please see below for details:

[root@LinuxServer ~]# snmpwalk -On -v 2c -c EDGE_snmp 10.35.xx.xx 1.3.6.1.4.1.67.4.3.8.1.1
.1.3.6.1.4.1.67.4.3.8.1.1.0 = STRING: "EDGEBEI0002"
[root@LinuxServer ~]# snmpwalk -On -v 2c -c EDGE_snmp 10.35.xx.xx 1.3.6.1.4.1.232.2.2.2.1.0
Timeout: No Response from 10.35.xx.xx
[root@LinuxServer ~]# date
Tue Nov 16 04:12:24 GMT 2021
[root@LinuxServer ~]# snmpwalk -On -v 2c -c EDGE_snmp 10.35.xx.xx 1.3.6.1.4.1.67.4.3.8.1.1
Timeout: No Response from 10.35.xx.xx
[root@LinuxServer ~]# date
Tue Nov 16 04:13:49 GMT 2021
[root@LinuxServer ~]# snmpwalk -On -v 2c -c EDGE_snmp 10.35.xx.xx 1.3.6.1.4.1.67.4.3.8.1.1
.1.3.6.1.4.1.67.4.3.8.1.1.0 = STRING: "EDGEBEI0002"
[root@LinuxServer ~]# snmpwalk -On -v 2c -c EDGE_snmp 10.35.xx.xx 1.3.6.1.4.1.232.2.2.2.1.0
Timeout: No Response from 10.35.xx.xx

I have several servers with different hardware (Gen8 ,Gen 9, Gen10) and different OS (WS 2012R2, WS2019), but I only observe this issue for DL360 Gen9 with WS2019.

Could you please advise what might be the root cause?

Additional FYI: 

• “1.3.6.1.4.1.232” is the top level for Compaq;
• “1.3.6.1.4.1.232.2.2.2.1” refers to cpqSiSysSerialNum(1), i.e. the serial number of the system unit.

Best Regards,

Peggy

[Parvez_Admin]

Hello @PeggyQi_2021 

As there is no response from the Community for the query yet, I would recommend to directly contact technical support and log a support call for quicker resolution.

https://support.hpe.com/help/en/Content/supportAndOtherResources.html

https://www.hpe.com/psnow/doc/A00039121ENW

[lslamp]

Did you ever get a resolution to this issue.

I have an HP Proliant DL360 and am trying to monitor SNMP from zabbix.

I am having exactly the same issue when running snmpwalk to the server gies no results. In fact if I try to manipulate the OID, I cannot seem to extract info like Hareware Infor or Network info.fact if I run snmpwalk to the server using the following.

I cut off the OID at .232 .... as shown below. I get nothing back. I would then assume thatt he OID for the HP device is non existant.

snmpwalk -v 1 -c {communityname} {ip address} | grep 3.6.1.4.1.232

In

I look forward to your soonect reply.

Thanks

Lawrence

[PeggyQi_2021]

Hi Lawrence, sorry I haven't got a resolution to this issue yet. My testing shows that the issue exists for DL360 Gen 9 with WS2019; I haven't observed the same issue on other Hardware & OS pairs. As "1.3.6.1.4.1.232" is the top level for HP Compaq, the issue looks to be related to a combination of particular Hardware / OS. My current workaround is to bypass "1.3.6.1.4.1.232" and only focus on our product specific OIDs.

[lslamp]

This completely screws up my raid monitoring. I have downloaded a template from the zabbix library and just will not load because of this issue.
In fact I have an ticket open with the creators of the template asking them for suggestions, but if the OID is not working on the hardware then none of the monitoring that I want to carry out can be done.

Can you suggest a way for me to view and manage the raid disks on the server?

Thanks
Lawrence

[PeggyQi_2021]

Hi Lawrence, sorry I'm not HPE support. I'm also contacting HPE Support for solutions but haven't got it yet. Please reach out to HPE Support for further assistance.