Yep, all v2c (see attached).

Maybe I was running discovery script without the proper options ?

Y.

Le 27/02/2017 22:15, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit :

We don't use snmpv3, it's all v2 by default.

Best regards.

> Le 27 févr. 2017 à 21:18, Michael obslist@smarsz.com a écrit : > > Your discovery debug output showed it was attempting to use SNMPv3. But here, you are using SNMPv2c. > > Can you check how you have your SNMP settings in Observium for those hosts. > > Michael > > > > > >> On 28 Feb 2017, at 2:27 am, Youssef BENGELLOUN - ZAHR ybzahr@prodware.fr wrote: >> >> Dear Michael, >> >> SNMP is perfectly responsive on those hosts : >> >> root@prod-monit-002:/opt/observium# snmpwalk -v 2c -c asp par01-esx2-bl2 sysDescr >> SNMPv2-MIB::sysDescr.0 = STRING: VMware ESXi 5.5.0 build-3568722 VMware, Inc. x86_64 >> >> I have attached a full snmwalk output from one of the host as an example. >> >> Best regards. >> >> >> >> Le 27/02/2017 16:19, « observium au nom de Michael » <observium-bounces@observium.org au nom de obslist@smarsz.com> a écrit : >> >> Looks to me like there's no data at all coming back from either of those esxi hosts. "WARNING: 0 devices discovered" >> >> Could you try the following query to see what comes back >> >> snmpwalk -v3 <your-snmpv3-details-here> par01-esx02-bl2 sysDescr >> >> I think you need to validate that your server is actually answering SNMP queries for you. >> >> VMware have long been reluctant to do much with SNMP (prefering to push people towards vCenter/vCOPS). As a result, their support for revealing lots of physical host information leaves a bit to be desired. >> >> Cheers, >> >> Michael >> >> >> >> >> >> >> >> >>> On 27 Feb 2017, at 9:35 pm, Youssef BENGELLOUN - ZAHR ybzahr@prodware.fr wrote: >>> >>> >>> Dear Observium, >>> >>> This is a request for information / enhancement, I hope you will find it relevant / useful. Actually running latest stable version 17.2.8364. >>> >>> We run quite a lot of blade chassis (DELL M1000e, IBM bladecenterH, IBM pureflex) and monitor the blades in the enclosures, more specifically the ESXi hosts servers. >>> >>> I recently noticed that we were not able to recover SNMP information about physical components’ status (CPU, memory DIMMs, etc.). We are more interested in memory DIMM status. >>> >>> I have run a discovery against a couple of hosts in debug mode and can see that recovered SNMP information is pretty basic (see attached). >>> >>> Do you think it would be possible / interesting to recover such information ? >>> >>> Thank you for your feedback. >>> >>> Best regards. >>> >>> >>> Youssef BENGELLOUN - ZAHR - Consultant Expert >>> Prodware France >>> T : +33 979 999 000 - F : +33 988 814 001 - ybzahr@prodware.fr >>> <image23bec5.PNG>Web : prodware.fr >>> >>> <image9b26f1.JPG> <image5c3e4c.JPG> <image0119e3.JPG> <imagee569c0.JPG> <image93eaa0.JPG> <image039eb0.JPG> >>> >>> >>> >>> <par01-esx02-bl2.txt><par01-esx03-bl2.txt> >> >> BENGELLOUN - ZAHR Youssef - Consultant Expert >> Prodware France >> T : +33 979 999 000 F : +33 988 814 001 - ybzahr@prodware.fr >> Web : prodware.fr >> >>

BENGELLOUN - ZAHR Youssef - Consultant Expert Prodware France T : +33 979 999 000 F : +33 988 814 001 - ybzahr@prodware.fr Web : prodware.fr

_______________________________________________ >>> observium mailing list >>> observium@observium.org >>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium >> >> _______________________________________________ >> observium mailing list >> observium@observium.org >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium >> >> >> <snmpwalk-esx-host.txt>_______________________________________________ >> observium mailing list >> observium@observium.org >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium > > _______________________________________________ > observium mailing list > observium@observium.org > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium