Hi Yep got all those in place - its for a rare occurance on Junipers - and have done much googling where Juniper essentially say "yeah and???"
Wouldn't mind to much but its customer related stuff Have found a way of storing the ifindex file on the Juniper and then pulling it back post upgrade but this is another team to do and they may not nescessarily do that On Mon, Mar 21, 2011 at 1:36 PM, Kenneth Kirchner <[email protected]> wrote: > Does your device support something like: > > Router(config)# *snmp-server ifindex persist* > > * > * > * > http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080134eec.shtml > * > * > * > *To hold them at their initial index value?* > * > * > *-Ken* > * > * > On Mar 20, 2011, at 5:22 PM, Garry Harst wrote: > > Hi > As far as I can see out spectrum is setup to model ports on the ifindex. > This is fine except when a couple of devices decided to do a semi reindex > of ports on an IOS upgrade > Rather irritating > > Is it possible to model the ports on another attribute on the device? Like > ifdescr maybe? > > > > - --To unsubscribe from spectrum, send email to [email protected] with > the body: unsubscribe spectrum [email protected] > > > > - --To unsubscribe from spectrum, send email to [email protected] with > the body: unsubscribe spectrum [email protected] > > --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
