Hi,
I noticed our cricket cron is generating errors on one SNMP OID, i.e.
[14-Aug-2008 14:40:01 ] Retrieved data for b1-l1-cat1 (): U,U,U,U,U,U,U,U [14-Aug-2008 14:40:01 ] Some data is missing for b1-l1-cat1 (). [14-Aug-2008 14:40:01*] Received SNMP response with error code noSuchName. OID: 1.3.6.1.4.1.9.9.13.1.3.1.3.1
Error and the lines leading up to it: [14-Aug-2008 14:40:01 ] Some data is missing for b1-l1-cat1 (). [14-Aug-2008 14:40:01*] Received SNMP response with error code noSuchName. OID: 1.3.6.1.4.1.9.9.13.1.3.1.3.1
And yet if I look at the SNMP OID support listed for the device as reported by NAV I see:
b1-l1-cat1 tempInlet 1.3.6.1.4.1.9.9.13.1.3.1.3.1 CISCO-ENVMON-MIB ciscoEnvMonTemperatureStatusValue 21600
which implies the OID is supported, and is the device inlet temperature.
Is there some additional IOS config required to make this particular data available to Cricket? Being new to OIDs, I'm confused as to why it seems to be available according to NAV, yet Cricket's getting an error.
Thanks :)
On Tue, 19 Aug 2008 17:35:44 +0100 Tim Chown tjc@ecs.soton.ac.uk wrote:
I'm sorry to say that NAV's support for monitoring temperatures on Cisco devices is hopelessly broken.
The abovementioned OID refers to the temperature value of a temperature sensor indexed as 1 in the proprietary CISCO-ENVMON-MIB. NAV assumes this is the inlet temperature sensor. However, the MIB definition states that the sensor indices are arbitrarily chosen by the device, and have no intrinsic meaning. The name of each sensor must be read from a different column of the temperature table.
The equipment base this was written for (several years ago) may very well have had their inlet sensors indexed as 1 in the temperature table, but recent IOS versions seem to have changed things.
b1-l1-cat1 may have indexed one of its temperature sensors as 1 during the initial import into NAV, and then changed its mind at a later time. That would account for the problem you're having.
Now, for some good news:
John-Magne Bredal has published a contrib tool to NAV which adds new temperature monitoring functionality to NAV. The contrib can also monitor temperatures for devices that support the RFC-standardized ENTITY-SENSOR-MIB. HP equipment seems to readily support this.
The tool is not yet an official part of NAV because of the way the list of temperature sensors is collected from devices, but at some point it will become official.
A branch with John-Magne's contrib can be found at [1]. The contrib itself is located in the source tree as contrib/cricket-temperature/ . It has a README file which explains how to install and use the tool.