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

Jonas Frey (Probe Networks) jf at probe-networks.de
Fri Mar 8 10:33:43 EST 2013


Hello,

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. When doing the ISSU it brought down FPC-1 (which is
a MPC Type 2). Maybe thats why the ifIndex were changed.
(We are running mixed DPCE and MPC)
Anyway now i do have the problem that some of the interfaces do no
longer have a snmp ifIndex at all:

user at router> show interfaces ge-1/0/2.1 
  Logical interface ge-1/0/2.1 (Index 333) (SNMP ifIndex 0)
    Description: C28711
    Flags: SNMP-Traps VLAN-Tag [ 0x8100.141 ]  Encapsulation: ENET2
    Input packets : 6785935 
    Output packets: 4257005
    Protocol inet, MTU: 1500
      Flags: No-Redirects, Sendbcast-pkt-to-re
[...]
(this is a interface on the MPC card)

I saw some posts about this happening on EX but none on MX.

How do i get the ifIndex right? The workaround for EX doesnt help as
there is no such process to restart on MX series.

Best regards,
Jonas



-------------- 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/5052fedf/attachment.sig>


More information about the juniper-nsp mailing list