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

Hangu Jeong netcops at gmail.com
Mon Oct 27 01:20:30 EDT 2008


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
>


More information about the juniper-nsp mailing list