We are currently running 5.1R2 but are in the process of moving to 5.3R1.
The only indexes which don't appear to change are the permanent interfaces
(fxp's, tap, pimd, etc) the GigE and Sonet interfaces seem to jump around
quite a bit (especially on RE failovers).
Shane
-----Original Message-----
From: Greg Ketell [mailto:gketell@juniper.net]
Sent: Thursday, June 27, 2002 5:03 PM
To: Julian Eccli; Owens, Shane (EPIK.ORL); juniper-nsp@puck.nether.net
Subject: RE: SNMP Index Changes
Actually it should remain stable across reboots and reconfigurations unless
there is HW change.
This was not always the case, though. What release are you running?
GK
At 09:42 AM 6/27/2002, Julian Eccli wrote:
>Shane,
>
>For SNMP the sequence of interface indices is determined by the
>sequence those devices get initialized. Once the system is up and
>running, the indices will remain fixed and stable, provided there is no
>hot swap, reboot, or reconfiguration (sighup).
>
>You should be able to setup MRTG to track by interface IP.
>
>
>-Julian
>
> > -----Original Message-----
> > From: Owens, Shane (EPIK.ORL) [mailto:sowens@epik.net]
> > Sent: Thursday, June 27, 2002 6:12 AM
> > To: juniper-nsp@puck.nether.net
> > Subject: SNMP Index Changes
> >
> >
> > Does anyone else have a problem with Juniper re-indexing the
> > interfaces after reboot, software loads, RE-switches etc? We seem
> > to re-index after
> > each of these event even with no physical port changes to the
> > equipment
> > which wreaks havoc on backend trending systems like Concord and MRTG.
> >
> > Shane
> >
> >
> >
This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:36 EDT