On Tue, 14 Dec 2021 15:16:16 +0100 (CET) "FOUR Ludovic (EXT)" ludovic.four@unistra.fr wrote:

I'm trying to add the probes by following the adding AKCP probe tutorial.

Cool! Glad to see it's of use to someone :)

snmpwalk -c community -v1|2c <IP of the probe> ServersCheck:sensor1Name.0

If I translate into OID with snmptranslate command, I get this OID .1.3.6.1.4.1.17095.3.2.0

• Add the following lines to /etc/nav/ipdevpoll.conf (note sure of

iana code of serverscheck manufacturer. should be 25432)

25432 = ServersCheckMib SERVERSCHECK = SERVERSCHECK-MIB

Actually, from the MIB it appears the vendor/enterprise id for your device is 17095, not 25342. 17095 is registered to Microchip Technology Inc.

At this point i'm stuck (ipdevpoll log empty) and I still can't get sensors readings into NAV and it doesn't recognize the probe type into collected info of the seedDB probe page

First of all, are you able to verify SNMP connectivity with the device through the SeedDB IP device form?

The sysObjectID of your probe device is most likely unknown to NAV, so regardless of your new implementation, ipdevpoll should auto-create a type entry for the probe the first time the inventory job runs. This type record will just have the sysObjectID as its name, and the type description will be fetched from the sysDescr object. This type record should be edited in SeedDB once it appears, so you can give it a more human-friendly name and description.

Any ideas of what I'm doing wrong ?

I assume the hard-coded sensor return value in your get_all_sensors() implementation is just for testing purposes - it should at least cause ipdevpoll to try to fetch this value for all devices with an enterprise id of 25432.

Most likely, your problem is that you've used the wrong enterprise id in the ipdevpoll config.