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. Device link takes me to the wrong device (Thomas Portmann)
   2. Re: Device link takes me to the wrong device (Oliver Gorwits)
--- Begin Message ---

Hello all,

I have a strange problem on a new install (Devuan 5, Daedalus) and Netdisco 2.64.1 with one Cisco Nexus device. Globally, everything seems to get discovered correctly. However, searching for one particular device name ({lu__11}) results in 2 devices:
- {la__11}, management IP {_._.240.49}
- {lu__11}, management IP {_._.78.9}

The details in the table are correct for both, even the links to the devices seem correct. However the link to the lu__11 device http://localhost:5000/device?q={_._.78.9} takes me to the device {la__11}.

So, my questions are:
1. Why do I get two matches when I should get just one when searching?
2. Why does the seemingly correct URL take me to another device?
3. Where can I start investigating this?

Thank you in advance and best regards


        Tom



--- End Message ---
--- Begin Message ---
Hi Tom

So it looks like you have what we call a "duplicate device". (I guess it is
the same Nexus device.)

In the Admin menu there is a Duplicate Devices report which might show
these two entries. That report looks for serial numbers which are shared
between devices.

This can happen because Netdisco runs a lot of work in parallel in the
background, including device discovery, and sometimes the same device is
discovered twice at the same time (from different directions, if you
imagine). Normally Netdisco can do a good job of deduplicating, but it can
still occasionally happen this way and Netdisco tries to be conservative
and not make an assumption (which is why we have the report, so you can
decide).

You can probably safely delete one of the devices and you'll never hear
about it again.

There are some config things you can do to help avoid this (depending on
how much it happens, you might not bother). You can make sure the LLDP
advertised Management IP is the same on all interfaces on the Nexus, so
wherever it's seen from, it has the same identity. You can also use
Netdisco's "device_identity" configuration setting to steer Netdisco to use
the best canonical IP for the device (
https://github.com/netdisco/netdisco/wiki/Configuration#device_identity).
Both of these tactics can help avoid duplicates.

Finally, the reason Netdisco takes you to another device when you click the
link is because the duplicate situation is wrong, and it confuses Netdisco.

With the above I assumed you have the one Nexus and it's a duplicate. But
it was not fully clear in your email. If you in fact have two devices and
that's legitimate, then my best guess is that you have the same IPs
configured on the two devices (many protocols support this) and it's
confusing Netdisco. I suggest the "device_identity" config is used to make
clear to Netdisco that they are different.

Hope this helps!

Oliver.



On Fri, 4 Aug 2023 at 09:56, Thomas Portmann via netdisco-users <
netdisco-users@lists.sourceforge.net> wrote:

>
> Hello all,
>
> I have a strange problem on a new install (Devuan 5, Daedalus) and
> Netdisco 2.64.1 with one Cisco Nexus device. Globally, everything seems
> to get discovered correctly. However, searching for one particular
> device name ({lu__11}) results in 2 devices:
> - {la__11}, management IP {_._.240.49}
> - {lu__11}, management IP {_._.78.9}
>
> The details in the table are correct for both, even the links to the
> devices seem correct. However the link to the lu__11 device
> http://localhost:5000/device?q={_._.78.9} takes me to the device {la__11}.
>
> So, my questions are:
> 1. Why do I get two matches when I should get just one when searching?
> 2. Why does the seemingly correct URL take me to another device?
> 3. Where can I start investigating this?
>
> Thank you in advance and best regards
>
>
>         Tom
>
>
> _______________________________________________
> 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

Reply via email to