[ixpmanager] Discovered MAC Addresses Issue

[Nick Hilliard (INEX)]

Ahmed Al-Saruri wrote on 02/01/2019 09:46:
> 1- When I specify vlan ID so only MAC addresses of that vlan are 
> discovered, it fails and goes for  BRIDGE-MIB instead:

are you sure this is the correct ID?  If you go into the IXP Manager web 
interface and click on "VLANs" on the left hand side, the ID you need to 
use here is in the "DB ID" field.  It's not necessarily the same as the 
802.1q VLAN tag.

> /usr/local/bin/update-l2database.pl 
> <http://update-l2database.pl/> --vlanid 2 --debug
> 
> DEBUG: xxx: started query process
> DEBUG: xxx: pre-emptively trying Juniper jnxExVlanTag to see if we're on 
> a J-EX box (.1.3.6.1.4.1.2636.3.40.1.5.1.5.1.5)
> DEBUG: xxx: this isn't a Juniper EX
> DEBUG: xxx: this isn't a Juniper running an ELS image
> DEBUG: xxx: attempting to retrieve dot1qVlanFdbId mapping (.1.3.6.1.2.1.17.7.1.4.2.1.3)
> DEBUG: xxx: got mapping index: 3610 maps to 3610

In theory, that means that Q-BRIDGE-MIB is supported.

> DEBUG: xxx: attempting Q-BRIDGE-MIB (.1.3.6.1.2.1.17.7.1.2.2.1.2.3610)
> DEBUG: xxx: failed to retrieve Q-BRIDGE-MIB. falling back to BRIDGE-MIB

This shouldn't happen.  Can you attempt the following commands on your 
switch:

% snmpwalk -v 2c -c snmpcomm switchname .1.3.6.1.2.1.17.7.1.2.2.1.2

% snmpwalk -v 2c -c snmpcomm switchname .1.3.6.1.2.1.17.7.1.2.2.1.2.3610

Obviously you need to replace "snmpcomm" and "switchname" with values 
for your device.

If the first query returns "No Such Instance currently exists at this 
OID", then the switch doesn't support Q-BRIDGE-MIB.  If it returns lots 
of values and the second command returns "No Such Instance", then the 
Huawei SNMP implementation is broken, and we'll need to write some code 
to work around it.

> DEBUG: xxx: attempting BRIDGE-MIB (.1.3.6.1.2.1.17.4.3.1.2)
> DEBUG: xxx: BRIDGE-MIB query successful
 > [...]
> 2- When I run the script with no vlan id specified it detects around
> 270 MAC addresses only while the switch has around 2000 MAC:

That's probably because it's using BRIDGE-MIB instead of Q-BRIDGE-MIB.

Nick