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. Mikrotik and Neighbors (o...@leferguson.com)
2. Re: Mikrotik and Neighbors (Michael Butash)
--- Begin Message ---
Mikrotik now (probably for sometime but I just noticed, running 7.15.2)
supports both LLDP and CDP for neighbor discovery, and SNMP.
I have a Netgear switch between all the mikrotik devices.
Both Netgear and Mikrotik see their neighbors in their own display, but
Netdisco does not show them as neighbors (other than netgear to netgear which
works, at the moment I have no Mikrotik to Mikrotik).
I've been down the rathole of figuring neighbor issues out and it can be a long
one so with apologies in advance for not yet doing my homework....
Has anyone chased this particular rat yet, and knows the situation and/or
workaround or settings?
If not, when I get some time will try to find out.
Linwood
--- End Message ---
--- Begin Message ---
If older Netgears work but newer doesn't, I suspect they have a bug in the
newer snmp implementation that is indexing them wrong or missing
information now.
I'd snmpwalk old and new for LLDP-MIB and see what each looks like, making
sure they index the same and provide the same sort of data comparing
side-by-side.
snmpwalk -m ALL -c $community -v 2c $sw-hostname .1.0.8802.1.1.2
Might care to drop LLDP-MIB into your ~/.snmp/mibs dir first along with
ifmib and others if needed to resolve these to be human readable more than
ASN fodder.
HTH!
-mb
On Tue, Jul 2, 2024 at 7:45 AM o...@leferguson.com <o...@leferguson.com> wrote:
> Well, my electricians are 2 hours late and still not here so I spent a
> few minutes trying to figure this out, and I do see one thing.
>
>
>
> When accessing my core Netgear switch I get a Netdisco error.
>
>
>
> SNMP::Info 3.970001
>
> SNMP::Info::device_type() layers:01001111 id:4526 sysDescr:"NETGEAR
> 24-Port Gigabit PoE+ Smart Managed Pro Switch with 4 SFP Ports (GS728TPv2),
> Software Version 6.0.10.20, Boot Version 1.0.0.5"
>
> [1756991] 2024-07-02 14:30:18 debug [192.168.130.2] neigh - removed 0
> outdated manual topology links
>
> [1756991] 2024-07-02 14:30:18 debug [192.168.130.2] neigh - setting
> manual topology links
>
> SNMP::Info::_global lldp_sys_cap : LLDP-MIB::lldpLocSysCapEnabled.0 :
> .1.0.8802.1.1.2.1.3.6.0
>
> SNMP::Info::_global(lldp_sys_cap) NOSUCHOBJECT at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Discover/Neighbors.pm
> line 120.
>
> SNMP::Info::_load_attr lldp_rem_id : LLDP-MIB::lldpRemChassisId :
> .1.0.8802.1.1.2.1.4.1.1.5
>
>
>
> This is on what I think is current, version 2.76.5
>
>
>
>
> That line is here:
>
>
>
> sub store_neighbors {
>
> my $device = shift;
>
> my @to_discover = ();
>
>
>
> my $snmp = App::Netdisco::Transport::SNMP->reader_for($device)
>
> or return (); # already checked!
>
>
>
> # first allow any manually configured topology to be set
>
> # and do this before we cache the rows in vars->{'device_ports'}
>
> set_manual_topology($device);
>
>
>
> if (!defined $snmp->has_topo) {
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Line 120
>
> debug sprintf ' [%s] neigh - neighbor protocols are not enabled',
> $device->ip;
>
> return @to_discover;
>
> }
>
>
>
> I struggle with perl so am not sure if that means the object $snmp is not
> found (I think so), or that a OID it is referencing is not found.
>
>
>
> What’s odd is that this switch DOES show neighbors (two other netgears),
> but when I run:
>
>
>
> ~/bin/netdisco-do discover::neighbors -d closetsw.leferguson.com -DIS
>
>
>
> At the end it shows
>
>
>
> [1770671] 2024-07-02 14:41:29 info discover::neighbors: status info:
> [192.168.130.2] neigh - processed 0 neighbors
>
>
>
> If I compare the run to the other netgears (much older devices), those do
> not get the above error and do show this switch as a neighbor.
>
>
>
> I’m not sure what to look for though if that’s a perl error. Note that
> netdisco does a fine job of discovering this switch in general, the details
> page looks right, the ports page right (the uplink port to the AP shows the
> AP by name and IP). So… not sure what “not found” means.
>
>
>
>
>
> *From:* o...@leferguson.com
> *Sent:* Tuesday, July 2, 2024 9:44 AM
> *To:* netdisco-users@lists.sourceforge.net
> *Subject:* Mikrotik and Neighbors
>
>
>
> Mikrotik now (probably for sometime but I just noticed, running 7.15.2)
> supports both LLDP and CDP for neighbor discovery, and SNMP.
>
>
>
> I have a Netgear switch between all the mikrotik devices.
>
>
>
> Both Netgear and Mikrotik see their neighbors in their own display, but
> Netdisco does not show them as neighbors (other than netgear to netgear
> which works, at the moment I have no Mikrotik to Mikrotik).
>
>
>
> I’ve been down the rathole of figuring neighbor issues out and it can be a
> long one so with apologies in advance for not yet doing my homework….
>
>
>
> Has anyone chased this particular rat yet, and knows the situation and/or
> workaround or settings?
>
>
>
> If not, when I get some time will try to find out.
>
>
>
> Linwood
>
>
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
