[ixpmanager] Issue in Discovering MAC addresses with the script

[Ahmed Al-Saruri]

Hello Nick,

Thank you very much for your assistance.

On Thu, Sep 19, 2019 at 4:10 PM Nick Hilliard (INEX) <nick at inex.ie> wrote:

> Ahmed Al-Saruri wrote on 19/09/2019 13:07:
> > Currently there is one Core LACP configured on the following
> > interfaces (xe1, xe2, xe3, xe4, xe5, xe6, xe7) and one peering member on
> > xe9.
> >
> > Please find attached the results for the snmp.
>
> Your logs show:
>
> > % snmpwalk -c XX -v2c columba  .1.3.6.1.2.1.17.7.1.2.2.1.2
> >
> > SNMPv2-SMI::mib-2.17.7.1.2.2.1.2.3210.96.222.243.117.76.74 = INTEGER:
> 5009
> > SNMPv2-SMI::mib-2.17.7.1.2.2.1.2.3210.224.151.150.72.79.176 = INTEGER:
> 5009
> > SNMPv2-SMI::mib-2.17.7.1.2.2.1.2.3210.224.151.150.72.79.187 = INTEGER:
> 5009
>
> This means that bridge port id 5009 with VLAN id 3210 is populated with
> 3 MAC addresses: 60def3754c4a, e09796484fb0 and e09796484fbb.
>
> Separate to this, the switch also reports:
>
> > % snmpwalk -c XX -v2c columba  .1.3.6.1.2.1.2.2.1.2
> > IF-MIB::ifDescr.5009 = STRING: xe9
>
> This means that switch interface 5009 is associated with physical
> interface xe9.
>
> The important thing here is that the SNMP bridge port ID is not the same
> as the switch interface ID.  These two ID numbers should be linked using
> the dot1dBasePortIfIndex OID, which shows:
>
>  > SNMPv2-SMI::mib-2.17.1.4.1.2.9 = INTEGER: 5009
>
> This is wrong, because the .9 doesn't match the value from
> dot1qTpFdbPort above.
>
> So OcNOS should be reporting either:
>
> > SNMPv2-SMI::mib-2.17.7.1.2.2.1.2.3210.96.222.243.117.76.74 = INTEGER:
> 5009
> > SNMPv2-SMI::mib-2.17.7.1.2.2.1.2.3210.224.151.150.72.79.176 = INTEGER:
> 5009
> > SNMPv2-SMI::mib-2.17.7.1.2.2.1.2.3210.224.151.150.72.79.187 = INTEGER:
> 5009
> > SNMPv2-SMI::mib-2.17.1.4.1.2.5009 = INTEGER: 5009
> > IF-MIB::ifDescr.5009 = STRING: xe9
>
> or more probably:
>
> > SNMPv2-SMI::mib-2.17.7.1.2.2.1.2.3210.96.222.243.117.76.74 = INTEGER: 9
> > SNMPv2-SMI::mib-2.17.7.1.2.2.1.2.3210.224.151.150.72.79.176 = INTEGER: 9
> > SNMPv2-SMI::mib-2.17.7.1.2.2.1.2.3210.224.151.150.72.79.187 = INTEGER: 9
> > SNMPv2-SMI::mib-2.17.1.4.1.2.9 = INTEGER: 5009
> > IF-MIB::ifDescr.5009 = STRING: xe9
>
> You should open up a ticket with IP Infusion about this, and refer to
> the following document for how the BRIDGE-MIB indexing mechanism works:
>
>  >
>
> https://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/44800-mactoport44800.html
>
> OcNOS's implementation of Q-BRIDGE-MIB should work the same way as
> BRIDGE-MIB which is described in that document.
>
> Nick
>
>

-- 

Warm Regards,
Ahmed Alsaruri
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20190920/9644f1ff/attachment.htm>