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. Re: device neighbors showing up multiple times (Chris Stromsoe)
2. Re: device neighbors showing up multiple times (Oliver Gorwits)
3. New Ubiquiti MIBs (Josep Manel Andr?s Moscard?)
4. Re: New Ubiquiti MIBs (Owen Mann)
--- Begin Message ---
Thanks. For the short term, I'm using devices_no to skip my entire IPv6
network range, but that will pose problems as a long-term solution when
single-stack v6 devices come on-line.
I assume you meant serial number and lldpLocChassisId for de-duplication,
not lldpRemChassisId.
Where in the code does the de-duplication happen? It seems to be working
fine for IPv4 (I have a single entry for an IPv4 device). It's just
failing for IPv6, where every IPv6 reachable interface is showing up as a
separate device. (The problem interfaces are all dual-stack and their v4
addresses do not show up as devices.)
-Chris
On Fri, 22 Dec 2017, Oliver Gorwits wrote:
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
------------------------------------------------------------------------------
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,
By any chance is there an SNMP view ACL running on the v6 interfaces?
(perhaps a vendor default) This might make the devices seem different to
Netdisco as it cannot poll all data from the target.
lldpRemChassisId is used when the devices are seen by neighbors to
deduplicate at the job queue level before running jobs. We do not yet
use lldpLocChassisId but I imagine, could do so.
It might be useful to start with a clean/empty DB and discover a v4 and
a v6 interface (both from blank) and compare what Netdisco is receiving
via SNMP and storing in the DB. There must be a difference somewhere. I
appreciate that this is a bit of work (although NETDSICO_DBNAME env at
the CLI can help).
regards,
Oliver
On 2018-01-02 16:43, Chris Stromsoe wrote:
Thanks. For the short term, I'm using devices_no to skip my entire
IPv6 network range, but that will pose problems as a long-term
solution when single-stack v6 devices come on-line.
I assume you meant serial number and lldpLocChassisId for
de-duplication, not lldpRemChassisId.
Where in the code does the de-duplication happen? It seems to be
working fine for IPv4 (I have a single entry for an IPv4 device).
It's just failing for IPv6, where every IPv6 reachable interface is
showing up as a separate device. (The problem interfaces are all
dual-stack and their v4 addresses do not show up as devices.)
-Chris
On Fri, 22 Dec 2017, Oliver Gorwits wrote:
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
------------------------------------------------------------------------------
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, I've got a question about including new MIBS in Netdisco, I want to
include Ubiquiti MIBS but when following the manual
(https://github.com/netdisco/netdisco-mibs/wiki/Updating-MIBs), I get
the following:
xemacs@samaruc ~/codi-serveis/netdisco-mibs (jmam-ubiquiti-newmibs) $
MIBHOME=/home/xemacs/codi-serveis/netdisco-mibs
xemacs@samaruc ~/codi-serveis/netdisco-mibs (jmam-ubiquiti-newmibs) $ cd
$MIBHOME
xemacs@samaruc ~/codi-serveis/netdisco-mibs (jmam-ubiquiti-newmibs) $
EXTRAS/scripts/setmaxtcerror: must define $MIBHOME (where the MIB dirs live)
Any Idea why it isn't taking the right env variable?
Thanks.
--
------------------------------------------------
Josep Manel Andrés Moscardó
System Administrator
IMIM-Hospital del Mar Research Institut
--- End Message ---
--- Begin Message ---
You need to export it:
MIBHOME=/home/xemacs/codi-serveis/netdisco-mibs; export MIBHOME
Or just:
export MIBHOME=/home/xemacs/codi-serveis/netdisco-mibs
On Tue, Jan 2, 2018 at 11:54 AM, Josep Manel Andrés Moscardó <
[email protected]> wrote:
> Hi, I've got a question about including new MIBS in Netdisco, I want to
> include Ubiquiti MIBS but when following the manual (
> https://github.com/netdisco/netdisco-mibs/wiki/Updating-MIBs), I get the
> following:
>
>
> xemacs@samaruc ~/codi-serveis/netdisco-mibs (jmam-ubiquiti-newmibs) $
> MIBHOME=/home/xemacs/codi-serveis/netdisco-mibs
>
> xemacs@samaruc ~/codi-serveis/netdisco-mibs (jmam-ubiquiti-newmibs) $ cd
> $MIBHOME
>
> xemacs@samaruc ~/codi-serveis/netdisco-mibs (jmam-ubiquiti-newmibs) $
> EXTRAS/scripts/setmaxtcerror: must define $MIBHOME (where the MIB dirs live)
>
>
> Any Idea why it isn't taking the right env variable?
>
> Thanks.
>
> --
> ------------------------------------------------
> Josep Manel Andrés Moscardó
> System Administrator
> IMIM-Hospital del Mar Research Institut
>
> ------------------------------------------------------------
> ------------------
> 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
>
--
Owen Mann
Linux Systems Engineer
[email protected]
iZotope, Inc.
www.izotope.com
--- 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
