[c-nsp] CISCO-ENVMON-MIB initial Index change in in SXH2a?

[David Freedman]

As far as I'm aware these indices are not in the ENTITY-MIB , I've
confirmed this by walking it on both SXF and SXH boxes.

I know you can't rely on index persistance in all cases and to do so for
such indices would be silly, but I'm sure the algorithm for generating
these must have changed here.


Phil Mayers wrote:
> David Freedman wrote:
>> My SHX2a boxes are showing a shift from small to large initial index
>> numbers (ciscoEnvMonTemperatureStatusIndex) in CISCO-ENVMON-MIB in the
>> ciscoEnvMonTemperatureStatusTable, release notes mention nothing about
>> this, bugtool turns up a blank, has anybody else seen this? is it
>> intentional?
> 
> I believe those indices are ENTITY-MIB values, so they'll be variable. I
> don't think there is the equivalent of a "snmp ifindex persist" for
> entity indices.
> 
>>
>> SXF box and below:
>>
>> SNMPv2-SMI::enterprises.9.9.13.1.3.1.2.1 = STRING: "VTT 1 outlet
>> temperature"
>> SNMPv2-SMI::enterprises.9.9.13.1.3.1.2.2 = STRING: "VTT 2 outlet
>> temperature"
>> SNMPv2-SMI::enterprises.9.9.13.1.3.1.2.3 = STRING: "VTT 3 outlet
>> temperature"
>>
>>
>> SHX2a box:
>>
>> SNMPv2-SMI::enterprises.9.9.13.1.3.1.2.40010 = STRING: "VTT 1 outlet
>> temperature"
>> SNMPv2-SMI::enterprises.9.9.13.1.3.1.2.40020 = STRING: "VTT 2 outlet
>> temperature"
>> SNMPv2-SMI::enterprises.9.9.13.1.3.1.2.40030 = STRING: "VTT 3 outlet
>> temperature"
>>
>>
>> Whilst it is entirely correct that one should first walk the
>> ciscoEnvMonTemperatureStatusTable in order to retrieve the index ,
>> I've always been able to use the static OID
>> .1.3.6.1.4.1.9.9.13.1.3.1.3.1 to get VTT 1 outlet temperature.
> 
> I think you've been lucky; I've seen them change across reboots when
> modules have been inserted.
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>