December 2021 - Nav-dev - lister.unit.no

Re: How to add sensorgateway probes to nav ?
by Morten Brekkevold 21 Dec '21

21 Dec '21

On Fri, 17 Dec 2021 13:08:58 +0100 (CET) "FOUR Ludovic (EXT)" <ludovic.four(a)unistra.fr> wrote: > Hi Morten, > > Thanks for the reply. I know how to use SNMP OID's but I must admit > i'm not really comfortable yet with MIB schemas. I've learned > something with OBJECT IDENTIFIER and ::= { enterprises } in the MIB > file today ! Thanks a lot ! :) No problem :) > I can check SNMP connectivity in seedDB IP devices but there's still > nothing in collected info Type Found no new type in SeedDB (unknown > empty) > > If I remove one of the devices from Seed Database, and add it again > but nothing happens. Still no sensor graph The ipdevpoll `inventory` job needs to run successfully for the device to be identified first (and, unfortunately, the sensor may not be added on the first inventory run. The first run sets the device type, so that the sensors plugin has that value available only on the second run - and by default, successful runs are on 6 hour intervals). You should see all succesful/failing jobs in the job status box in the ipdevinfo page of your sensor device (just search for it in the navbar). If the jobs aren't running at all, are you sure ipdevpoll is running? You can also run these jobs manually from the command line: ipdevpolld -J inventory -n <name-of-sensor-device> Run it twice, and see if the sensor appears in ipdevinfo. Once it does, the 1minstats plugin should collect data from the registered sensors every 60 seconds. > Another point with serverscheck sensor : if I use snmpwalk to > interrogate my sensor temperature, i get this : > iso.3.6.1.4.1.17095.3.2.0 = STRING: "22.07" > > It appears that the sensor value format is STRING, not as integer. Is > that a problem ? I think it should be fine; as long as you do not provide a precision value in the sensor record, the string would be sent raw to Graphite. SNMP doesn't really have a data type for floating point numbers, so there are usually only two ways to go about this: Use strings, or provide a scaled value. -- sincerely, Morten Brekkevold Uninett Uninett is merging with Unit and NSD to form the new Norwegian Agency for Shared Services in Education and Research, and will stop trading under its own name per 1 January 2022.

1 0

Re: How to add sensorgateway probes to nav ?
by Morten Brekkevold 17 Dec '21

17 Dec '21

On Tue, 14 Dec 2021 15:16:16 +0100 (CET) "FOUR Ludovic (EXT)" <ludovic.four(a)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. -- sincerely, Morten Brekkevold Uninett Uninett is merging with Unit and NSD to form the new Norwegian Agency for Shared Services in Education and Research, and will stop trading under its own name per 1 January 2022.

1 0

Re: How to add sensorgateway probes to nav ?
by Morten Brekkevold 17 Dec '21

17 Dec '21

On Tue, 14 Dec 2021 15:16:16 +0100 (CET) "FOUR Ludovic (EXT)" <ludovic.four(a)unistra.fr> wrote: > Hello, > > I'm using NAV 5.2 and I would like to add a couple of Serverscheck temperature probes that monitor our network racks > Product reference is detailed here : https://serverscheck.com/sensors/baseunit.asp > > I'm trying to add the probes by following the adding AKCP probe tutorial. I made this : First off, I suggest moving this entire discussion to the nav-dev mailing list (if you're not already subscribed). I've Cc-ed it, and will post a full reply there. > 1/ Translate the sensorgateway.mib into SERVERSCHECK-MIB.py with smidump command > 2/ Copy the python file to folder /opt/venvs/nav/lib/python3.7/site-packages/nav/smidumps > > There's a ServersCheck module used in MIB file, that i'm using to interrogate directly the probe > I can get the temperature value with 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 > > > 3/ Create the file serverscheck_mib.py with those lines to /opt/venvs/nav/lib/python3.7/site-packages/nav/mibs > > from twisted.internet import defer > from nav.mibs import reduce_index > from nav.mibs.mibretriever import MibRetriever > from nav.smidumps import get_mib > > class ServerCheckMib(MibRetriever): > mib = get_mib('SERVERSCHECK-MIB') > @defer.inlineCallbacks > def get_all_sensors(self): > result = [ > { > 'oid': '.1.3.6.1.4.1.17095.3.2.0', > 'unit_of_measurement': 'celsius', > 'precision': 1, > 'scale': None, > 'description': "Ambient temperature", > 'name': "Ambient temperature", > 'internal_name': "Ambient temperature", > 'mib': 'SERVERSCHECK-MIB', > } > ] > defer.returnValue(result) > > > - 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 > > 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 > > Any ideas of what I'm doing wrong ? -- sincerely, Morten Brekkevold Uninett Uninett is merging with Unit and NSD to form the new Norwegian Agency for Shared Services in Education and Research, and will stop trading under its own name per 1 January 2022.

1 0