We have some HP DL360 servers that are detected in LibreNMS with OS of Windows Server.
However the ‘Hardware’ section shows: Intel x64.
When running a ./discovery.php against the host I get the following (snapshot of relevant items hopefully:
| Hardware: Intel64 Family 6 Model 79 Stepping 1 AT/AT COMPATIBLE - Software: Windows Version 6.3 (Build 14393 Multiprocessor Free) | .126.96.36.199.4.1.3188.8.131.52.1.3 |
Attempting to initialize OS: windows
OS initialized: LibreNMS\OS\Windows
OS: Microsoft Windows (windows)
SNMP[’/usr/bin/snmpbulkwalk’ ‘-v2c’ ‘-c’ ‘COMMUNITY’ ‘-OQUs’ ‘-m’ ‘HOST-RESOURCES-MIB’ ‘-M’ ‘/opt/librenms/mibs:/opt/librenms/mibs/dell’ ‘-t’ ‘10’ ‘udp:HOSTNAME:161’ ‘hrDeviceDescr’]
hrDeviceDescr.1 = Microsoft XPS Document Writer v4
hrDeviceDescr.2 = Microsoft Print To PDF
hrDeviceDescr.3 = Unknown Processor Type
hrDeviceDescr.4 = Unknown Processor Type
hrDeviceDescr.5 = Unknown Processor Type
hrDeviceDescr.6 = Unknown Processor Type
Thanks for the response.
The commands you supplied work if you use the hostname or or IP.
I think you are right, there appears to be something in the curl command using the " | ./pbin.sh" of the command.
Any ideas on the curl component to install/update to fix this?
The interesting thing is that this only seems to affect HP servers running Windows, Dell devices capture their device info properly as below:
Is there just an issue with the vendor hardware MIB support or the way it’s being read?
I can’t see anything windows OS support link you included that references either vendor so believe that this isn’t an OS issue.
However happy to add and dev the Windows functionality, huge opportunity there and as I understand, a deadline on SNMP support for Windows until this will become a limiting factor for the solution.
Are you focusing on Check_MK or NSClient++ for WIndows integration?
I’ve just run an SNMP discovery again and I believe it’s related to the exposure of system information through iLO on an HP device, for some reason the system information does return through a standard SNMP test.
Allowing passthrough SNMP from the iLO also doesn’t pass the necessary information through.
It’d be interesting to see if anyone else on the forum has found similar and a workaround.