Send netdisco-users mailing list submissions to
        netdisco-users@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/netdisco-users
or, via email, send a message with subject or body 'help' to
        netdisco-users-requ...@lists.sourceforge.net

You can reach the person managing the list at
        netdisco-users-ow...@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:

   1. Meraki switches - MAC-to-port mapping issues (Ashley Jeff)
   2. Re: Meraki switches - MAC-to-port mapping issues (Ashley Jeff)
--- Begin Message ---
Netdisco Team,

We've successfully added various Cisco and Juniper devices to a new install of 
Netdisco, but we're having trouble getting our Meraki cloud-managed switches 
added such that we can search and find MAC to port mappings. We believe the 
problem is that they're not being discovered as layer2 or layer3 devices (They 
can function as either, but we're just using them as layer 2 devices). They 
support direct SNMP connections, and they support dot1dTpFdbTable queries. 
Here's output from snmpwalk from another server showing a Meraki device 
returning MAC table info.

snmpwalk -v 2c -c xxxxxx x.x.x.x 1.3.6.1.2.1.17.4.3.1.1

SNMPv2-SMI::mib-2.17.4.3.1.1.0.0.192.0.0.0 = Hex-STRING: 00 00 C0 00 00 00
SNMPv2-SMI::mib-2.17.4.3.1.1.0.1.230.64.4.22 = Hex-STRING: 00 01 E6 40 04 16
etc.

Here's the result of the netdisco-do debug command that we've read about in the 
forums. We're guessing the issue is that they don't support sysServices, and 
the resulting layers output shows 00000000.

~netdisco/bin/netdisco-do show -DI -d x.x.x.x -e bp_inde

[56339] 2021-03-29 22:48:03  info App::Netdisco version 2.047005 loaded.
[56339] 2021-03-29 22:48:03  info show: [x.x.x.x]/bp_inde started at Mon Mar 29 
16:48:03 2021
[56339] 2021-03-29 22:48:03 debug show: running with timeout 600s
[56339] 2021-03-29 22:48:03 debug => running workers for phase: check
[56339] 2021-03-29 22:48:03 debug -> run worker check/_base_/0
[56339] 2021-03-29 22:48:03 debug Show is able to run
[56339] 2021-03-29 22:48:03 debug => running workers for phase: main
[56339] 2021-03-29 22:48:03 debug -> run worker main/_base_/100
[56339] 2021-03-29 22:48:03 debug snmp reader cache warm: [x.x.x.x]
[56339] 2021-03-29 22:48:03 debug [x.x.x.x:161] try_connect with ver: 2, class: 
SNMP::Info::Layer3::Cisco, comm: <hidden>
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(layers) NOSUCHOBJECT at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Transport/SNMP.pm line 245.
SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 : .1.3.6.1.2.1.1.1.0
Device doesn't implement sysServices but did return sysDescr. Might give 
unexpected results.
 at /home/netdisco/perl5/lib/perl5/App/Netdisco/Transport/SNMP.pm line 223.
SNMP::Info::_global id : SNMPv2-MIB::sysObjectID.0 : .1.3.6.1.2.1.1.2.0
SNMP::Info 3.71
SNMP::Info::device_type() layers:00000000 id:29671 sysDescr:"Meraki MS225-48FP 
Cloud Managed PoE Switch"
SNMP::Info::_validate_autoload_method(bp_inde) Unable to resolve method.
undef
[56339] 2021-03-29 22:48:03  info show: finished at Mon Mar 29 16:48:03 2021
[56339] 2021-03-29 22:48:03  info show: status done: Showed bp_inde response 
from x.x.x.x

We're read through other posts suggesting modifications to the Info.pm file, 
and based on that, we've added these lines to the sections listed, which we 
think is reflected in the above output.

    my %l3sysoidmap = (
        29671 => 'SNMP::Info::Layer3::Cisco',

    # These devices don't claim to have Layer1-3 but we like em anyways.
    truncated ... (Added in the middle of the section)
    # Meraki MS225
        $objtype = 'SNMP::Info::Layer3::Cisco'
            if ( $desc =~ /Meraki MS225-48FP Cloud Managed PoE Switch/i );

Nothing so far has resulted in the devices showing L2 or L3 capabilities in the 
debug output or the GUI. We are able to run discovery on groups of Meraki 
devices, assumedly using SNMP discovery on one device and then CDP to discover 
other connected devices that subsequently get populated with SNMP info. We also 
do see MAC addresses listed on ports on the Meraki switches in the Netdisco 
GUI, but when we search for those MAC addresses in the main search window, they 
show up on the trunk port on the parent Juniper device rather than the Meraki 
device that they're directly plugged into - and to confirm, that's based on a 
MAC address search and not an IP/arp search. MIB support for Meraki devices is 
pretty limited, but we're hoping we can pull the general info from the 
SNMPv2-MIBs and get searchable MAC addresses down to the Meraki ports. Is there 
a way to get these devices to populate that info into Netdisco?

Thanks for the help,
Jeff

--- End Message ---
--- Begin Message ---
Netdisco Team,

We believe we figured out how to get this to work. We found information in 
other mailing list posts that suggested adding lines like these to the 
~netdisco/perl5/lib/perl5/SNMP/Info.pm.

*** Under the my %l3sysoidmap section:
        29671 => 'SNMP::Info::Layer3::Meraki',

*** Under the # Layer 3 Supported section:
        # Meraki MS225
        $objtype = 'SNMP::Info::Layer3::Meraki'
          if $desc =~ /^Meraki\sMS225/;

Then we created a pm file in the ~netdisco/perl5/lib/perl5/SNMP/Info/Layer3 
directory that includes a section like this:

sub layers {
    return '00000110';
}

After re-running the discovery process on a group of Meraki switches, they now 
show up as Layer2 and Layer3 devices, and the MAC-to-IP per switch port 
functionality is working.

Jeff Ashley
Infrastructure Services

 Jefferson County Public Schools
1829 Denver West Dr. #27
Golden, CO 80401
PH 303-982-2219
Website: http://www.jeffcopublicschools.org

________________________________
From: Ashley Jeff
Sent: Monday, March 29, 2021 5:49 PM
To: netdisco-users@lists.sourceforge.net <netdisco-users@lists.sourceforge.net>
Subject: Meraki switches - MAC-to-port mapping issues

Netdisco Team,

We've successfully added various Cisco and Juniper devices to a new install of 
Netdisco, but we're having trouble getting our Meraki cloud-managed switches 
added such that we can search and find MAC to port mappings. We believe the 
problem is that they're not being discovered as layer2 or layer3 devices (They 
can function as either, but we're just using them as layer 2 devices). They 
support direct SNMP connections, and they support dot1dTpFdbTable queries. 
Here's output from snmpwalk from another server showing a Meraki device 
returning MAC table info.

snmpwalk -v 2c -c xxxxxx x.x.x.x 1.3.6.1.2.1.17.4.3.1.1

SNMPv2-SMI::mib-2.17.4.3.1.1.0.0.192.0.0.0 = Hex-STRING: 00 00 C0 00 00 00
SNMPv2-SMI::mib-2.17.4.3.1.1.0.1.230.64.4.22 = Hex-STRING: 00 01 E6 40 04 16
etc.

Here's the result of the netdisco-do debug command that we've read about in the 
forums. We're guessing the issue is that they don't support sysServices, and 
the resulting layers output shows 00000000.

~netdisco/bin/netdisco-do show -DI -d x.x.x.x -e bp_inde

[56339] 2021-03-29 22:48:03  info App::Netdisco version 2.047005 loaded.
[56339] 2021-03-29 22:48:03  info show: [x.x.x.x]/bp_inde started at Mon Mar 29 
16:48:03 2021
[56339] 2021-03-29 22:48:03 debug show: running with timeout 600s
[56339] 2021-03-29 22:48:03 debug => running workers for phase: check
[56339] 2021-03-29 22:48:03 debug -> run worker check/_base_/0
[56339] 2021-03-29 22:48:03 debug Show is able to run
[56339] 2021-03-29 22:48:03 debug => running workers for phase: main
[56339] 2021-03-29 22:48:03 debug -> run worker main/_base_/100
[56339] 2021-03-29 22:48:03 debug snmp reader cache warm: [x.x.x.x]
[56339] 2021-03-29 22:48:03 debug [x.x.x.x:161] try_connect with ver: 2, class: 
SNMP::Info::Layer3::Cisco, comm: <hidden>
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(layers) NOSUCHOBJECT at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Transport/SNMP.pm line 245.
SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 : .1.3.6.1.2.1.1.1.0
Device doesn't implement sysServices but did return sysDescr. Might give 
unexpected results.
 at /home/netdisco/perl5/lib/perl5/App/Netdisco/Transport/SNMP.pm line 223.
SNMP::Info::_global id : SNMPv2-MIB::sysObjectID.0 : .1.3.6.1.2.1.1.2.0
SNMP::Info 3.71
SNMP::Info::device_type() layers:00000000 id:29671 sysDescr:"Meraki MS225-48FP 
Cloud Managed PoE Switch"
SNMP::Info::_validate_autoload_method(bp_inde) Unable to resolve method.
undef
[56339] 2021-03-29 22:48:03  info show: finished at Mon Mar 29 16:48:03 2021
[56339] 2021-03-29 22:48:03  info show: status done: Showed bp_inde response 
from x.x.x.x

We're read through other posts suggesting modifications to the Info.pm file, 
and based on that, we've added these lines to the sections listed, which we 
think is reflected in the above output.

    my %l3sysoidmap = (
        29671 => 'SNMP::Info::Layer3::Cisco',

    # These devices don't claim to have Layer1-3 but we like em anyways.
    truncated ... (Added in the middle of the section)
    # Meraki MS225
        $objtype = 'SNMP::Info::Layer3::Cisco'
            if ( $desc =~ /Meraki MS225-48FP Cloud Managed PoE Switch/i );

Nothing so far has resulted in the devices showing L2 or L3 capabilities in the 
debug output or the GUI. We are able to run discovery on groups of Meraki 
devices, assumedly using SNMP discovery on one device and then CDP to discover 
other connected devices that subsequently get populated with SNMP info. We also 
do see MAC addresses listed on ports on the Meraki switches in the Netdisco 
GUI, but when we search for those MAC addresses in the main search window, they 
show up on the trunk port on the parent Juniper device rather than the Meraki 
device that they're directly plugged into - and to confirm, that's based on a 
MAC address search and not an IP/arp search. MIB support for Meraki devices is 
pretty limited, but we're hoping we can pull the general info from the 
SNMPv2-MIBs and get searchable MAC addresses down to the Meraki ports. Is there 
a way to get these devices to populate that info into Netdisco?

Thanks for the help,
Jeff

--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to