H3C VLAN information is not working due to wrong MIB

Hi,

For some H3C switches, Q-BRIDGE-MIB cannot get the vlan information from the switches.

The vlan information is stored in HH3C-LswVLAN-MIB.

Is there any way to enable this “HH3C-LswVLAN-MIB” for H3C switches?

The reference so far I got from the internet is -

netdisco/snmp-info#267

Let me know if more information is needed.

Hi @sajiby3k
All is possible, you should describe as much as possible your device, attach as many snmpwalks from different devices showing the issue, and wait until somebody has spare time to develop it (or develop it yourself).
You can start collecting details here, and when everything is gathered, you will create a gihub Issue.
Bye

Three are some outputs when I run discovery from Librenms -

ver version1 SNMP[’/usr/bin/snmpbulkwalk’ ‘-v2c’ ‘-c’ ‘COMMUNITY’ ‘-OQUs’ ‘-m’ ‘Q-BRIDGE-MIB’ ‘-M’ ‘/opt/librenms/mibs’ ‘udp:HOSTNAME:161’ ‘dot1qVlanStaticName’]

dot1qVlanStaticName = No Such Object available on this agent at this OID

SNMP[’/usr/bin/snmpbulkwalk’ ‘-v2c’ ‘-c’ ‘COMMUNITY’ ‘-OQUs’ ‘–hexOutputLength=0’ ‘-m’ ‘Q-BRIDGE-MIB’ ‘-M’ ‘/opt/librenms/mibs’ ‘udp:HOSTNAME:161’ ‘dot1qVlanCurrentEgressPorts’]

dot1qVlanCurrentEgressPorts = No Such Object available on this agent at this OID

SNMP[’/usr/bin/snmpbulkwalk’ ‘-v2c’ ‘-c’ ‘COMMUNITY’ ‘-OQUs’ ‘–hexOutputLength=0’ ‘-m’ ‘Q-BRIDGE-MIB’ ‘-M’ ‘/opt/librenms/mibs’ ‘udp:HOSTNAME:161’ ‘dot1qVlanCurrentUntaggedPorts’]

dot1qVlanCurrentUntaggedPorts = No Such Object available on this agent at this OID

But If I do manual snmpwalk -

snmpwalk -Os -v 2c -c XXXX 10.10.10.10 1.3.6.1.4.1.25506.8.35.2.1.1.1.2

enterprises.25506.8.35.2.1.1.1.2.1 = STRING: “defaultvlan”
enterprises.25506.8.35.2.1.1.1.2.100 = STRING: “VLAN100
enterprises.25506.8.35.2.1.1.1.2.200 = STRING: “VLAN200
enterprises.25506.8.35.2.1.1.1.2.300 = STRING: “VLAN300

Let me know if any more info is needed.

You should now create an issue in GitHub, following the template of “new device” and adding the issue description. Also add all the mandatory attachements of an issue.

From that, somebody can do the dev.