On Thu, 16 Feb 2012 12:59:35 +0100 Ingeborg Hellemo ingeborg.hellemo@uit.no wrote:
Nav version 3.10.2 Django debug is intentionally turned on
We need to monitor uptime on our printers and add them to NAV in category OTHER.
When we add snmp-enabled SafeCom controllers (http://www.betasoft.co.uk/safeco m/safecom_ext_controller.htm) seeddb barfs while talking snmp to the device with
[snip]
It is quite possible that the SNMP-implementation on these devices are odd, but seeddb should be able to cope in a more elegant way.
Attached is the output of snmpwalk of the device without any fancy flags. Let me know if you need more info.
I need to do some in-depth testing if I want to get to the bottom of the SNMP issue, but I agree that SeedDB should be more graceful. Please report the bug at https://bugs.launchpad.net/nav/+filebug .
Also, you may still be able to add your printers to NAV by bulk importing them; bulk import doesn't perform any SNMP verification.
You should, however, keep an eye on ipdevpoll.log after adding them, to see if that SNMP implementation barfs too (I hope not, since it's based on NetSNMP).