On Thu, Aug 28, 2008 at 03:24:58PM +0200, Morten Brekkevold wrote:
> On Tue, 19 Aug 2008 17:35:44 +0100 Tim Chown <tjc(a)ecs.soton.ac.uk> wrote:
> > 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: 22.214.171.124.126.96.36.199.188.8.131.52.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 184.108.40.206.220.127.116.11.18.104.22.168.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.
> 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.
Thanks for the explanation. What then is the recommended way to suppress
errors related to this OID? NAV kindly generates email alerts for errors
when querying devices, we just have a few too many related to this OID :)
Is there a recommended way to configure NAV to not poll our 3750 stacks
for temp data? I see there are config files under Cricket for generic
routers and switches with this OID, i.e.:
And also some reference in
It looks like Cricket generates the Defaults file and the config.db each night,
while cricketoids.txt is static, but it's not clear to us where those nightly
builds are driven from (i.e. where we could remove/suppress the temp entry).
It sounds like even using snmpwalk to grab the current indexed value wouldn't
help as it is liable to change.
The temperature queries work just fine for our Cisco 6509, so ideally we
wouldn't want to generically remove temp readings for everything.
A week ago I knew far less about OIDs and I think I was better for it :)