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. new user - initial setup instruction needed. (Weisbrod, Christoph)
2. device neighbors showing up multiple times (Chris Stromsoe)
3. Re: new user - initial setup instruction needed. (Oliver Gorwits)
4. Re: device neighbors showing up multiple times (Oliver Gorwits)
--- Begin Message ---
Hi netdisco user group,
I am new to NetDisco and downloaded the container version from here to try it
out first:
https://github.com/sheeprine/docker-netdisco
I already have the webinterface open and adjusted the SNMP community in the
deployment.yml but I am still not succeeding in discovering devices (see below).
Do you know of any good instructions/tutorials on how to initially setup,
configure and use the tool so I can discover my network/devices?
The snmp part of the deployment.yml looks like this:
...
# SNMP community string(s)
# ````````````````````````
snmp_auth:
- community: mycommunitystring
...
But I still get the following error every time I want to discover a device:
root@42870187eb50:/netdisco/environments# netdisco-do -D discover -d xxx
[55] 2017-12-21 18:04:45 info discover: started at Thu Dec 21 18:04:45 2017
[55] 2017-12-21 18:04:45 debug [xxx] try_connect with ver: 2, class:
SNMP::Info, comm: <hidden>
MIB search path:
Cannot find module (UCD-DLMOD-MIB): At line 0 in (none)
Cannot find module (MTA-MIB): At line 0 in (none)
Cannot find module (NETWORK-SERVICES-MIB): At line 0 in (none)
Cannot find module (UCD-DISKIO-MIB): At line 0 in (none)
Cannot find module (LM-SENSORS-MIB): At line 0 in (none)
Cannot find module (HOST-RESOURCES-MIB): At line 0 in (none)
Cannot find module (HOST-RESOURCES-TYPES): At line 0 in (none)
Cannot find module (SNMPv2-MIB): At line 0 in (none)
Cannot find module (IF-MIB): At line 0 in (none)
Cannot find module (IP-MIB): At line 0 in (none)
Cannot find module (TCP-MIB): At line 0 in (none)
Cannot find module (UDP-MIB): At line 0 in (none)
Cannot find module (NOTIFICATION-LOG-MIB): At line 0 in (none)
Cannot find module (DISMAN-EVENT-MIB): At line 0 in (none)
Cannot find module (DISMAN-SCHEDULE-MIB): At line 0 in (none)
Cannot find module (UCD-SNMP-MIB): At line 0 in (none)
Cannot find module (UCD-DEMO-MIB): At line 0 in (none)
Cannot find module (SNMP-TARGET-MIB): At line 0 in (none)
Cannot find module (NET-SNMP-AGENT-MIB): At line 0 in (none)
Cannot find module (SNMP-MPD-MIB): At line 0 in (none)
Cannot find module (SNMP-USER-BASED-SM-MIB): At line 0 in (none)
Cannot find module (SNMP-FRAMEWORK-MIB): At line 0 in (none)
Cannot find module (SNMP-VIEW-BASED-ACM-MIB): At line 0 in (none)
Cannot find module (SNMP-COMMUNITY-MIB): At line 0 in (none)
Cannot find module (IPV6-ICMP-MIB): At line 0 in (none)
Cannot find module (IPV6-MIB): At line 0 in (none)
Cannot find module (IPV6-TCP-MIB): At line 0 in (none)
Cannot find module (IPV6-UDP-MIB): At line 0 in (none)
Cannot find module (IP-FORWARD-MIB): At line 0 in (none)
Cannot find module (NET-SNMP-PASS-MIB): At line 0 in (none)
Cannot find module (NET-SNMP-EXTEND-MIB): At line 0 in (none)
Cannot find module (SNMP-NOTIFICATION-MIB): At line 0 in (none)
Cannot find module (SNMPv2-TM): At line 0 in (none)
Cannot find module (NET-SNMP-VACM-MIB): At line 0 in (none)
[55] 2017-12-21 18:04:45 debug [xxx] try_connect with ver: 1, class:
SNMP::Info, comm: <hidden>
[55] 2017-12-21 18:04:45 debug [xxx] try_connect with ver: 2, class:
SNMP::Info, comm: <hidden>
[55] 2017-12-21 18:04:45 debug [xxx] try_connect with ver: 1, class:
SNMP::Info, comm: <hidden>
[55] 2017-12-21 18:04:45 info discover: finished at Thu Dec 21 18:04:45 2017
[55] 2017-12-21 18:04:45 info discover: status error: discover failed: could
not SNMP connect to xxx
root@42870187eb50:/netdisco/environments#
I can ping and telnet 161 to the host and a snmpwalk with the same community
works too.
Thanks for your help.
Christoph
--- End Message ---
--- Begin Message ---
I'm seeing a strange issue where devices are being graphed with multiple
copies of the same neighbor. Eg, switch-X is shown with router-1 as a
neighbor two or more times.
Searching for the devices by name ends up returning multiple results for
the same device with different management IP addresses.
It looks like ND is picking up the v4 management address as a device, and
is then adding an additional device with the v6 address from all of the
dual-stack v4/v6 interfaces that link to downstream .
In at least one case, I have a router listed 50 times: once with the v4
loopback address, and 49 additional times with v6 address from interfaces
linking downstream devices.
App::Netdisco is 2.37.3 and SNMP::Info is 3.39.
-Chris
--- End Message ---
--- Begin Message ---
Hi Christoph
The Netdisco MIBs bundle is not installed. On the Netdisco homepage
there are instructions which will help.
I suggest you ask the creator of that docker image for assistance - this
is sheeprine?
regards,
oliver.
On 2017-12-22 15:49, Weisbrod, Christoph wrote:
Hi netdisco user group,
I am new to NetDisco and downloaded the container version from here to
try it out first:
https://github.com/sheeprine/docker-netdisco
I already have the webinterface open and adjusted the SNMP community
in the deployment.yml but I am still not succeeding in discovering
devices (see below).
Do you know of any good instructions/tutorials on how to initially
setup, configure and use the tool so I can discover my
network/devices?
The snmp part of the deployment.yml looks like this:
...
# SNMP community string(s)
# ````````````````````````
snmp_auth:
- community: mycommunitystring
...
But I still get the following error every time I want to discover a
device:
root@42870187eb50:/netdisco/environments# netdisco-do -D discover -d
xxx
[55] 2017-12-21 18:04:45 info discover: started at Thu Dec 21 18:04:45
2017
[55] 2017-12-21 18:04:45 debug [xxx] try_connect with ver: 2, class:
SNMP::Info, comm: <hidden>
MIB search path:
Cannot find module (UCD-DLMOD-MIB): At line 0 in (none)
Cannot find module (MTA-MIB): At line 0 in (none)
Cannot find module (NETWORK-SERVICES-MIB): At line 0 in (none)
Cannot find module (UCD-DISKIO-MIB): At line 0 in (none)
Cannot find module (LM-SENSORS-MIB): At line 0 in (none)
Cannot find module (HOST-RESOURCES-MIB): At line 0 in (none)
Cannot find module (HOST-RESOURCES-TYPES): At line 0 in (none)
Cannot find module (SNMPv2-MIB): At line 0 in (none)
Cannot find module (IF-MIB): At line 0 in (none)
Cannot find module (IP-MIB): At line 0 in (none)
Cannot find module (TCP-MIB): At line 0 in (none)
Cannot find module (UDP-MIB): At line 0 in (none)
Cannot find module (NOTIFICATION-LOG-MIB): At line 0 in (none)
Cannot find module (DISMAN-EVENT-MIB): At line 0 in (none)
Cannot find module (DISMAN-SCHEDULE-MIB): At line 0 in (none)
Cannot find module (UCD-SNMP-MIB): At line 0 in (none)
Cannot find module (UCD-DEMO-MIB): At line 0 in (none)
Cannot find module (SNMP-TARGET-MIB): At line 0 in (none)
Cannot find module (NET-SNMP-AGENT-MIB): At line 0 in (none)
Cannot find module (SNMP-MPD-MIB): At line 0 in (none)
Cannot find module (SNMP-USER-BASED-SM-MIB): At line 0 in (none)
Cannot find module (SNMP-FRAMEWORK-MIB): At line 0 in (none)
Cannot find module (SNMP-VIEW-BASED-ACM-MIB): At line 0 in (none)
Cannot find module (SNMP-COMMUNITY-MIB): At line 0 in (none)
Cannot find module (IPV6-ICMP-MIB): At line 0 in (none)
Cannot find module (IPV6-MIB): At line 0 in (none)
Cannot find module (IPV6-TCP-MIB): At line 0 in (none)
Cannot find module (IPV6-UDP-MIB): At line 0 in (none)
Cannot find module (IP-FORWARD-MIB): At line 0 in (none)
Cannot find module (NET-SNMP-PASS-MIB): At line 0 in (none)
Cannot find module (NET-SNMP-EXTEND-MIB): At line 0 in (none)
Cannot find module (SNMP-NOTIFICATION-MIB): At line 0 in (none)
Cannot find module (SNMPv2-TM): At line 0 in (none)
Cannot find module (NET-SNMP-VACM-MIB): At line 0 in (none)
[55] 2017-12-21 18:04:45 debug [xxx] try_connect with ver: 1, class:
SNMP::Info, comm: <hidden>
[55] 2017-12-21 18:04:45 debug [xxx] try_connect with ver: 2, class:
SNMP::Info, comm: <hidden>
[55] 2017-12-21 18:04:45 debug [xxx] try_connect with ver: 1, class:
SNMP::Info, comm: <hidden>
[55] 2017-12-21 18:04:45 info discover: finished at Thu Dec 21
18:04:45 2017
[55] 2017-12-21 18:04:45 info discover: status error: discover
failed: could not SNMP connect to xxx
root@42870187eb50:/netdisco/environments#
I can ping and telnet 161 to the host and a snmpwalk with the same
community works too.
Thanks for your help.
Christoph
------------------------------------------------------------------------------
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 Chris
Unfortunately it's tricky for Netdisco to deduplicate completely
automagically - it tries using serial number and lldpRemChassisId but
sometimes this is not enough.
The best approach is to use the devices_only configuration (or
devices_no) if you know the management IPs of your devices, and thereby
limit Netdisco to only the interfaces you wish. This also keeps the
poller working well as it avoids unnecessary workload.
You can also use the device_identity setting to achieve similar result
by steering Netdisco to the interface on the box that you want as its
primary identity - and if that's the same as another device, Netdisco
will deduplicate at that point.
Either approach works, and in fact I use both in production together.
There is an Admin report for duplicate devices where you can remove them
(only one at a time, though).
regards,
oliver.
On 2017-12-22 16:41, Chris Stromsoe wrote:
I'm seeing a strange issue where devices are being graphed with
multiple copies of the same neighbor. Eg, switch-X is shown with
router-1 as a neighbor two or more times.
Searching for the devices by name ends up returning multiple results
for the same device with different management IP addresses.
It looks like ND is picking up the v4 management address as a device,
and is then adding an additional device with the v6 address from all
of the dual-stack v4/v6 interfaces that link to downstream .
In at least one case, I have a router listed 50 times: once with the
v4 loopback address, and 49 additional times with v6 address from
interfaces linking downstream devices.
App::Netdisco is 2.37.3 and SNMP::Info is 3.39.
-Chris
------------------------------------------------------------------------------
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 ---
------------------------------------------------------------------------------
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
