[j-nsp] SNMP ifIndex 0 on MX after ISSU

Jonas Frey (Probe Networks) jf at probe-networks.de
Fri Mar 8 13:16:56 EST 2013


Hi,

btw, i already tried restart mib-proess and restart snmp, none of both
were of any help.
Also i can actually see the ifIndex in /var/db/dcd.snmp_ix (which is 560
for this interface) but while trying to read via snmp it always returns
0 despite carrying traffic.



Am Freitag, den 08.03.2013, 17:42 +0100 schrieb Tobias Heister:
> Hi,
> 
> Am 08.03.2013 16:33, schrieb Jonas Frey (Probe Networks):
> > did anyone ever notice problems with wrong/changed SNMP ifIndex settings
> > after ISSU?
> > We ISSU upgraded a MX from 10.4R9.2 to 11.4R7.5 and after this some of
> > the ifIndex changed.
> 
> We had that a couple of time with the MX series (with and without ISSU), the last time it happened from 9.6RX to 10.4RX on a couple of systems.
> We will soon go from 10.4RX to 11.4RX so i am expecting it to happen again.
> 
> > How do i get the ifIndex right? The workaround for EX doesnt help as
> > there is no such process to restart on MX series.
> 
> I am not aware of a way to fix that. We usually have to fix it in our NMS, which is really annoying every time it happens.
> 
> regards
> Tobias
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20130308/e41b5622/attachment.sig>


More information about the juniper-nsp mailing list