Discussion:
ipdevpoll does not set sysname unless snmp is enabled
Ingeborg Hellemo
2011-08-31 08:20:12 UTC
Permalink
During migration from old NAV (3.5.6) to new NAV (3.9.1) I "Bulk import"-ed
all our hosts. I notice that ipdevpoll does not set correct sysname on hosts
that does not run a configured snmpd.

nav=> select * from netbox where ip='129.242.5.142';
netboxid | ip | roomid | typeid | deviceid | sysname | catid
----------+---------------+--------+--------+----------+---------------+-------
1100 | 129.242.5.142 | ma | | 87934 | 129.242.5.142 | SRV

This means I now have several hundred boxes (mostly windows servers, virtual
IPs and misc "stuff") lacking a proper sysname, even though they are
registered i DNS.

ipdevpoll.log:
2011-08-31 10:07:02,584 [WARNING plugins.dnsname.dnsname] [inventory
129.242.5.142] Box dnsname has changed from u'129.242.5.142' to
'radius1.uit.no'
2011-08-31 10:07:36,612 [ERROR jobs.jobhandler] [inventory 129.242.5.142] Job
'inventory' for 129.242.5.142 aborted: SNMP request timed out


If I edit the host via the Seed DB web interface the correct sysname is saved:

nav=> select * from netbox where ip='129.242.5.142';
netboxid | ip | roomid | typeid | deviceid | sysname |
catid
----------+---------------+--------+--------+----------+----------------+------
-
1100 | 129.242.5.142 | ma | | 87934 | radius1.uit.no | SRV



I presume this is a bug.



--Ingeborg
--
Ingeborg Østrem Hellemo -- ingeborg.hellemo-***@public.gmane.org
Dep. of Information Technology --- Univ. of Tromsø
Morten Brekkevold
2011-11-14 09:53:24 UTC
Permalink
Post by Ingeborg Hellemo
During migration from old NAV (3.5.6) to new NAV (3.9.1) I "Bulk import"-ed
all our hosts. I notice that ipdevpoll does not set correct sysname on hosts
that does not run a configured snmpd.
[snip]
Post by Ingeborg Hellemo
I presume this is a bug.
The fact is that this has always been so with NAV; even getDeviceData
did not update data for devices that weren't SNMP-monitored.

This issue has come up multiple times lately, so I do think we should
label it a bug and fix it, yes. See
https://bugs.launchpad.net/nav/+bug/890142
--
Morten Brekkevold
UNINETT
Loading...