[j-nsp] SNMP interface index change after upgrade to 9.2

[David Ball]

  thanks, Hangu.  Unfortunately it appears as though the contents of
this file (must) have changed between 9.1R1.8 and 9.2R2.15.
Unfortuately, I'm not sure I can confirm that, as I have no more
T-640s running 9.1.  I have an MX running 9.1, but its file will
certainly differ, as there are completely different interfaces.  May
open ticket with JNPR.  Thnx folks.

David


On 26/10/2008, Hangu Jeong <netcops at gmail.com> wrote:
> Your assumption is correct, actually router maintain snmp index as below
> file,
> So there is no snmp index changes across reboots.
>
> router# file show /var/db/dcd.snmp_ix
> /* file-format-version:  1  */
> /*
>  * mib2d-generated /var/db/dcd.snmp_ix
>  * Version: MIB2D release 9.2R1.10 built by builder on 2008-08-07 07:24:26
> UTC
>  * Written: Mon Oct 27 13:16:51 2008
>
> -Hangu
>
> On Mon, Oct 27, 2008 at 1:24 PM, David Ball <davidtball at gmail.com> wrote:
>
>>  I thought Juniper had sorted out their interface SNMP index
>> numbering such that they would remain the same, even following a
>> reboot?  I've been running a simple MRTG instance to monitor some
>> 10Gig core links since 8.4 with no problems.  I recently upgraded from
>> 9.1R1.8 to 9.2R2.15 on my T-Series and most (note: not ALL) of the
>> core 10Gig links I was monitoring (MRTG) all had a change in their
>> SNMP index number.  For example, ge-0/0/0 was previously SNMP index
>> #32, but now appears as #355.
>>  Anyone else notice this?  Am I incorrect in my previous assumption
>> that Juniper had solved this issue of SNMP index changes across
>> reboots?
>>
>> David
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>