v1910 switch wrong vlan name
Expected Behavior
show correct vlan name:

netdisco@netdisco:~$ bin/netdisco-do show -d 192.168.200.97 -e v_name [11065] 2019-02-12 08:17:48 info App::Netdisco version 2.040003 loaded. [11065] 2019-02-12 08:17:49 info show: [192.168.200.97]/v_name started at Tue Feb 12 09:17:49 2019 \ { 1 "VLAN 0001", 2 "VLAN 0002", 3 "VLAN 0003" }
conf in v1910 24g switch:

Your Environment
App::Netdisco | 2.40.3 SNMP::Info | 3.64
seems like that device is not storing the vlan name where snmp::info expects to find it.
can you run netdisco-do again but with debugging active?
netdisco-do show -d 192.168.200.97 -e v_name -DI
yes you are right:
netdisco@netdisco:~$ netdisco-do show -d 192.168.200.97 -e v_name -DI [14777] 2019-03-27 07:03:15 info App::Netdisco version 2.040003 loaded. [14777] 2019-03-27 07:03:16 info show: [192.168.200.97]/v_name started at Wed Mar 27 08:03:16 2019 [14777] 2019-03-27 07:03:16 debug show: running with timeout 600s [14777] 2019-03-27 07:03:16 debug => running workers for phase: check [14777] 2019-03-27 07:03:16 debug -> run worker check/base/0 [14777] 2019-03-27 07:03:16 debug Show is able to run [14777] 2019-03-27 07:03:16 debug => running workers for phase: main [14777] 2019-03-27 07:03:16 debug -> run worker main/base/100 [14777] 2019-03-27 07:03:16 debug snmp reader cache warm: [192.168.200.97] [14777] 2019-03-27 07:03:16 debug [192.168.200.97:161] try_connect with ver: 2, class: SNMP::Info::Layer3::H3C, comm:
SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance : .1.3.6.1.2.1.1.3.0 SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0 SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 : .1.3.6.1.2.1.1.1.0 SNMP::Info::_global id : SNMPv2-MIB::sysObjectID.0 : .1.3.6.1.2.1.1.2.0 SNMP::Info 3.64 SNMP::Info::device_type() layers:01001110 id:25506 sysDescr:"HPE V1910-24G Switch Software Version 5.20, Release 1519P03 Copyright(c) 2010-2017 Hewlett Packard Enterprise Development, L.P." SNMP::Info::_load_attr v_name : Q-BRIDGE-MIB::dot1qVlanStaticName : .1.3.6.1.2.1.17.7.1.4.3.1.1 \ { 1 "VLAN 0001", 2 "VLAN 0002" } [14777] 2019-03-27 07:03:17 info show: finished at Wed Mar 27 08:03:17 2019 [14777] 2019-03-27 07:03:17 info show: status done: Showed v_name response from 192.168.200.97
so only hpe can fix this problem right?
hm, perhaps they just store it in a different place, but it's hard to say without an snmpdump. could you provide us with one?
https://github.com/netdisco/snmp-info/wiki/Simulating-Agents#21-snmpsim--snmprec-version
do note the privacy note, if you do not want to make the dump public, you can create a private github repo and provide access where needed.
Hi,
i have found "wlan" here:
.1.3.6.1.4.1.25506.8.35.2.1.1.1.1.1 = INTEGER: 1 .1.3.6.1.4.1.25506.8.35.2.1.1.1.1.2 = INTEGER: 2 .1.3.6.1.4.1.25506.8.35.2.1.1.1.2.1 = STRING: "VLAN 0001" .1.3.6.1.4.1.25506.8.35.2.1.1.1.2.2 = STRING: "wlan" .1.3.6.1.4.1.25506.8.35.2.1.1.1.3.1 = Hex-STRING: FF FF FF 0F 00 00 00 00 00 00 00 00 00 00 00 00
catching up on the open tickets.
it seems we just need to add a mapping (and perhaps update mibs) to the private oid to fix this issue. i'll try & whip up a patch in the comming days.
it seems we just need to add a mapping (and perhaps update mibs) to the private oid to fix this issue. i'll try & whip up a patch in the comming days.
@JeroenvIS made some comments in the other related issues with points of attention i'll need to have a look at first.