On Thu, 01 Mar 2012 13:36:54 +0100 Ingeborg Hellemo ingeborg.hellemo@uit.no wrote:
For several switches I get
[01-Mar-2012 13:21:16*] Received SNMP response with error code noSuchName. OID: 1.3.6.1.4.1.9.9.13.1.3.1.3.1
This OID is not listed as supported when I check the "Report > IP Device SNMP OID support" for the boxes.
And it wouldn't be; this OID is CISCO-ENVMON-MIB::ciscoEnvMonTemperatureStatusValue.1 - NAV claims to have found a temperature sensor in CISCO-ENVMON-MIB with the particular snmp id of 1.
This sensor should be listed in the sensor database table for this netbox. Can you confirm this?
After upgrading to 3.11.0 this has magically corrected itself, but for one box.
In 'sensor' I find two rows with oid=.1.3.6.1.4.1.9.9.13.1.5.1.3.[12]. So I guess if I just remove these everything will be OK?
A second bug is an ups which is missing read only community. Still a /sensors-subtree is created with the line snmp-community =
This makes cricket-compile to report an error: [01-Mar-2012 13:13:58*] Missing equals sign at (or before) /usr/local/cricket/cricket-config/sensors/mv110-c107-ups.infra.uit.no/navTarget s line 6.
Well, that is certainly stupid. The sensors configuration plugin doesn't verify that the community is set (it probably should), but then it only picks netboxes in which NAV has found environment sensors. Did the UPS at one point have an SNMP community set in NAV?
I guess the SNMP community has once been set. And I would like to set it again, but when I edit the device I get
TypeMismatchError at /seeddb/netbox/edit/1853/
Octet-stream parse error at Pdus
Request Method: POST Request URL: https://nav.uit.no/seeddb/netbox/edit/1853/ Django Version: 1.3.1 Exception Type: TypeMismatchError Exception Value:
Octet-stream parse error at Pdus
Exception Location: /usr/local/lib/python2.7/site-packages/pysnmp/asn1/encodin g/ber/base.py in berDecode, line 370 Python Executable: /usr/local/bin/python Python Version: 2.7.2
If I use a wrong community I get this error after "Continue" on the first page of /seeddb/netbox/edit/1853/. If I use the correct community I do not get the error until I press "Save" on the second page.
As a fix for now I will set the community directly into the database.
--Ingeborg