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

[Tore Anderson]

* Malte von dem Hagen

> we filed that as a PR for the EX-Series we updated from 9.1 to 9.2 a
> while ago, and got the response from JTAC that this is expected behaviour.

Unbelievable.  This provokes me!  I really hope that the idiot(s) that
made this design desicion are no longer working at Juniper.

Hey, Juniper, if you're reading this:  Do you think that I ENJOY wasting
hours of my to clear up the mess this «feature» has caused, you're sadly
mistaken!  Not only is it fscking annoying - I use the data in my graphs
for accounting too (and I think that's pretty common to do), so now
valuable data used for invoicing customers is lost forever.

And this was only for the MXes!  My EXes have 100s of graphs...  I don't
want to even think about the hassle it would be to fix all of those
manually.

> Public interfaces get snmp ifIndex numbers *after* private interfaces,
> so every time the private interfaces (whatever they exactly are) change,
> the index numbers of public interfaces will change as well. And yes,
> that is big PITA and very lame.

Jesus.  So reserve some room for the private interfaces and enumerate
public ones staring from ifIndex 100 or 1000 or whatever, then.  That
wasn't too hard now was it?

Juniper:  to simpy say that this is just «expected behaviour» is
COMPLETELY UNACCEPTABLE, it's a DEFECT, and it NEEDS to be FIXED.

*fumes*

-- 
Tore Anderson
Redpill Linpro AS - http://www.redpill-linpro.com/