netdisco-users Digest, Vol 138, Issue 5

Fri, 05 Jan 2018 01:09:02 -0800 

Send netdisco-users mailing list submissions to
        [email protected]

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
        [email protected]

You can reach the person managing the list at
        [email protected]

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

Today's Topics:

   1. Mikrotik Neighbor Discovery (Lindsay Druett)
   2. Re: Discover multiple device - subnet (Jeroen van Ingen)
   3. Re: Mikrotik Neighbor Discovery (Jeroen van Ingen)
--- Begin Message --- 
Kiaora,


I've been deploying Netdisco on a Mikrotik network over the last couple of
days as a project but having issues with neighbor discovery even though
Mikrotik supports LLDP.

Is there some known issues with Mikrotik, lack of Mikrotik support, or is
there something I'm missing ?

Here is the output for the debugging...

SNMP::Info::_global lldp_sys_cap : LLDP-MIB::lldpLocSysCapEnabled.0 :
.1.0.8802.1.1.2.1.3.6.0
SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasSONMP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasFDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasEDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasAMAP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasSONMP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasFDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasEDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasAMAP) Unable to resolve method.
SNMP::Info::_load_attr lldp_rem_pid : LLDP-MIB::lldpRemPortId :
.1.0.8802.1.1.2.1.4.1.1.7
SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasSONMP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasFDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasEDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasAMAP) Unable to resolve method.
SNMP::Info::_load_attr lldp_rem_desc : LLDP-MIB::lldpRemPortDesc :
.1.0.8802.1.1.2.1.4.1.1.8
SNMP::Info::_load_attr lldp_rem_pid_type : LLDP-MIB::lldpRemPortIdSubtype :
.1.0.8802.1.1.2.1.4.1.1.6
SNMP::Info::_load_attr lldp_rem_sysdesc : LLDP-MIB::lldpRemSysDesc :
.1.0.8802.1.1.2.1.4.1.1.10
SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasSONMP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasFDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasEDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasAMAP) Unable to resolve method.
SNMP::Info::_load_attr lldp_rem_id_type : LLDP-MIB::lldpRemChassisIdSubtype
: .1.0.8802.1.1.2.1.4.1.1.4
SNMP::Info::_load_attr lldp_rem_id : LLDP-MIB::lldpRemChassisId :
.1.0.8802.1.1.2.1.4.1.1.5
SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasSONMP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasFDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasEDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasAMAP) Unable to resolve method.
SNMP::Info::_load_attr lldp_rem_sysname : LLDP-MIB::lldpRemSysName :
.1.0.8802.1.1.2.1.4.1.1.9
SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasSONMP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasFDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasEDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasAMAP) Unable to resolve method.
SNMP::Info::_load_attr lldp_rem_cap_spt : LLDP-MIB::lldpRemSysCapSupported
: .1.0.8802.1.1.2.1.4.1.1.11
SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasSONMP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasFDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasEDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasAMAP) Unable to resolve method.
SNMP::Info::_load_attr lldp_rman_addr : LLDP-MIB::lldpRemManAddrIfSubtype :
.1.0.8802.1.1.2.1.4.2.1.3
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve method.
SNMP::Info::_load_atrr: BULKWALK Unknown Object Identifier at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Discover/Neighbors.pm
line 120.
SNMP::Info::_load_attr lldp_rman_addr : LLDP-MIB::lldpRemManAddrIfSubtype :
.1.0.8802.1.1.2.1.4.2.1.3
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve method.
SNMP::Info::_load_atrr: BULKWALK Unknown Object Identifier at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Discover/Neighbors.pm
line 121.
[8301] 2018-01-04 23:00:00 debug  [10.25.1.14] neigh - port for IID:1 not
resolved, skipping
[8301] 2018-01-04 23:00:00 debug  [10.25.1.14] neigh - port for IID:2 not
resolved, skipping
[8301] 2018-01-04 23:00:00 debug  [10.25.1.14] neigh - port for IID:3 not
resolved, skipping
[8301] 2018-01-04 23:00:00 debug  [10.25.1.14] neigh - port for IID:4 not
resolved, skipping
[8301] 2018-01-04 23:00:00 debug  [10.25.1.14] neigh - port for IID:5 not
resolved, skipping
[8301] 2018-01-04 23:00:00 debug  [10.25.1.14] neigh - processed 0 neighbors


-- 
Lindsay Druett.


Wired Networks Ltd
[email protected]
+64-7-974 9301
+64-21-92 90 92

--- End Message ---
--- Begin Message --- 
Hi,
The "already queued" lines don't look right. Might be an issue with scheduling / queue system? I see similar lines on my install, updated yesterday afternoon. 


Regards,

Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands


On 04-01-18 22:43, Deshong, Ken wrote:

Yes, the switches can see their neighbors.  I've provided an attachment with my 
discovery inside.  Possibly you can tell what's happening by that.

Thanks for the tip regarding the subnet scan.  I'll try that next time

/Ken


-----Original Message-----
From: Oliver Gorwits [mailto:[email protected]]
Sent: Thursday, January 4, 2018 3:57 PM
To: [email protected]
Subject: Re: [Netdisco] Discover multiple device - subnet

Hi Ken

On 2018-01-03 16:43, Deshong, Ken wrote:

In the older versions, I could discover one device and automatically
it would discover all neighbor devices as well within a site. The
newest version doesn't seem to do this. Am I doing something wrong?


Are you running neighbor protocols on the switches such as LLDP? This is needed 
by Netdisco. Are the switches able to show their neighbors at the command line? 
(show lldp neigh)

Alternatively you could run a discover for 10.119.1.0/24 by entering that at 
the Netdisco web homepage.

regards,
oliver.


Let's say I have a small site with 30 switches wanted to discover all
30 devices (all within 10.119.1.0/24). Per the directions to discover
one device: netdisco-do -D discover -d 10.119.1.1. After this single
device is complete, it stops.

Ken DeShong

Network Engineer
  University of South Florida

Desk: 813-396-9472

Fax: 813-974-5198


----------------------------------------------------------------------
-------- Check out the vibrant tech community on one of the world's
most engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most engaging tech 
sites, Slashdot.org! http://sdm.link/slashdot 
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

--- End Message ---
--- Begin Message --- 
Hi,
Looks like the SNMP::Info module for Mikrotik (which is used by Netdisco) doesn't support LLDP. Could be that Mikrotik devices didn't support SNMP back when this module was written.
Can you open a ticket for this at https://github.com/netdisco/snmp-info/issues ? 


Regards,

Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands


On 05-01-18 00:09, Lindsay Druett wrote:

Kiaora,
I've been deploying Netdisco on a Mikrotik network over the last couple of days as a project but having issues with neighbor discovery even though Mikrotik supports LLDP.
Is there some known issues with Mikrotik, lack of Mikrotik support, or is there something I'm missing ? 

Here is the output for the debugging...
SNMP::Info::_global lldp_sys_cap : LLDP-MIB::lldpLocSysCapEnabled.0 : .1.0.8802.1.1.2.1.3.6.0 
SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasSONMP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasFDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasEDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasAMAP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasSONMP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasFDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasEDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasAMAP) Unable to resolve method.
SNMP::Info::_load_attr lldp_rem_pid : LLDP-MIB::lldpRemPortId : .1.0.8802.1.1.2.1.4.1.1.7 
SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasSONMP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasFDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasEDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasAMAP) Unable to resolve method.
SNMP::Info::_load_attr lldp_rem_desc : LLDP-MIB::lldpRemPortDesc : .1.0.8802.1.1.2.1.4.1.1.8 SNMP::Info::_load_attr lldp_rem_pid_type : LLDP-MIB::lldpRemPortIdSubtype : .1.0.8802.1.1.2.1.4.1.1.6 SNMP::Info::_load_attr lldp_rem_sysdesc : LLDP-MIB::lldpRemSysDesc : .1.0.8802.1.1.2.1.4.1.1.10 
SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasSONMP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasFDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasEDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasAMAP) Unable to resolve method.
SNMP::Info::_load_attr lldp_rem_id_type : LLDP-MIB::lldpRemChassisIdSubtype : .1.0.8802.1.1.2.1.4.1.1.4 SNMP::Info::_load_attr lldp_rem_id : LLDP-MIB::lldpRemChassisId : .1.0.8802.1.1.2.1.4.1.1.5 
SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasSONMP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasFDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasEDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasAMAP) Unable to resolve method.
SNMP::Info::_load_attr lldp_rem_sysname : LLDP-MIB::lldpRemSysName : .1.0.8802.1.1.2.1.4.1.1.9 
SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasSONMP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasFDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasEDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasAMAP) Unable to resolve method.
SNMP::Info::_load_attr lldp_rem_cap_spt : LLDP-MIB::lldpRemSysCapSupported : .1.0.8802.1.1.2.1.4.1.1.11 
SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasSONMP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasFDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasEDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasAMAP) Unable to resolve method.
SNMP::Info::_load_attr lldp_rman_addr : LLDP-MIB::lldpRemManAddrIfSubtype : .1.0.8802.1.1.2.1.4.2.1.3 
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve method.
SNMP::Info::_load_atrr: BULKWALK Unknown Object Identifier at /home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Discover/Neighbors.pm line 120. SNMP::Info::_load_attr lldp_rman_addr : LLDP-MIB::lldpRemManAddrIfSubtype : .1.0.8802.1.1.2.1.4.2.1.3 
SNMP::Info::_validate_autoload_method(CARP_TRACE) Unable to resolve method.
SNMP::Info::_load_atrr: BULKWALK Unknown Object Identifier at /home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Discover/Neighbors.pm line 121. [8301] 2018-01-04 23:00:00 debug  [10.25.1.14] neigh - port for IID:1 not resolved, skipping [8301] 2018-01-04 23:00:00 debug  [10.25.1.14] neigh - port for IID:2 not resolved, skipping [8301] 2018-01-04 23:00:00 debug  [10.25.1.14] neigh - port for IID:3 not resolved, skipping [8301] 2018-01-04 23:00:00 debug  [10.25.1.14] neigh - port for IID:4 not resolved, skipping [8301] 2018-01-04 23:00:00 debug  [10.25.1.14] neigh - port for IID:5 not resolved, skipping 
[8301] 2018-01-04 23:00:00 debug  [10.25.1.14] neigh - processed 0 neighbors


--
Lindsay Druett.


Wired Networks Ltd
[email protected] <mailto:[email protected]>
+64-7-974 9301
+64-21-92 90 92

--- End Message ---
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to