[j-nsp] MX80: SNMP BRIDGE-MIB broken?

Lars Erik Utsi Gullerud lerik at nolink.net
Thu Aug 9 05:32:50 EDT 2012


We see this behaviour on our MX80's running 11.1 and 11.2, but it works 
normally in 11.4 (tested on 11.4R2.14 specifically, which is currently 
on our lab box). So it seems to be a known (and resolved) issue, JTAC 
should be able to provide you with details about exact versions where 
this is fixed if you can't find it in a PR search.

Regards,
Lars Erik


On 09.08.2012 10:30, Emmanuel Halbwachs wrote:
> Hello,
>
> We use a MX80 and a MX240 as core LAN routers and use netdisco. But
> the Bridge MIB seem to be broken from the start:
>
>  From NMS:
>
>      $ snmpwalk -v1 -c public router .1.3.6.1.2.1.17
>      BRIDGE-MIB::dot1dBaseBridgeAddress.0 = Hex-STRING: 80 71 1F C7 F1 D0
>      BRIDGE-MIB::dot1dBasePort.41 = INTEGER: 41
>      BRIDGE-MIB::dot1dBasePort.41 = INTEGER: 41
>      Error: OID not increasing: BRIDGE-MIB::dot1dBasePort.41
>       >= BRIDGE-MIB::dot1dBasePort.41
>
>  From the router itself:
>
>      router> show snmp mib walk ascii .1.3.6.1.2.1.17
>      dot1dBaseBridgeAddress.0 = 80 71 1f c7  f1 d0
>      dot1dBasePort.41 = 41
>      dot1dBasePort.41 = 41
>      dot1dBasePort.41 = 41
>      dot1dBasePort.41 = 41
>      etc.
>      ^C
>      ---(more)---[abort]
>      
> Bug seen on MX80 in 10.4R3.4 and in 11.2R5.4 after a fresh upgrade
> this morning.
>
> Work like a charm on a MX240 (10.1R1.8).
>
> I have open a case at my reseller who should go with JTAC but
> I would like to know if anyone here hit this same issue.
>
> Thanks,
>



More information about the juniper-nsp mailing list