On Tue, 23 Jan 2018 09:08:33 +0100 Cristina Caselles firstname.lastname@example.org wrote:
We upgraded from 4.7.3 release and we are not sure that all links were correct before upgrading (newbies to NAV).
Ok, apologies for the late feedback - I've been travelling and completely forgot about this thread.
Our DNS infrastructure it is a bit untidy. What could we do? ( for instance, stopping some jobs?)
You could clean it up, perhaps? :-)
As our environment it is not a pure one we have both protocols enabled (CDP & LLDP). However the most problems are in Cisco Environment. Some discovered issues:
That could really get you intro trouble, then. CDP packets will pass right through non-Cisco devices, rendering them invisible from the viewpoint of the Cisco devices. As an added complication, some vendors (HP is one example) can pick up passing CDP packets and reflect them in their LLDP neighbor list, causing further mayhem (this functionality is optional in HP switches, as far as I know).
I would advise against CDP in a heterogenous environment - you should preferably only be using LLDP.
- Although in the NetMap view there is a switch connected to a pair of
Cisco (HSRP), the IP Device Info (Neighbors Tab) only see one of these link.
When you say "Netmap", are you viewing a layer 2 or 3 topology map? The latter infers topology from IP layer links (based on subnet addresses), while the former is the one that cares about ethernet-based connections, as discovered through LLDP/CDP or CAM tables.
- We deleted one device from BBDD and later created it again (waiting
to be discovered properly). Unfortunately now the device shows none of the two links.
By BBDD, I assume you mean the "Seed Database" (or SeedDB) tool?
Replace CDP with LLDP. I would also clean up DNS, but it should not strictly be necessary for topology to work, as LLDP idenfication can be made from device addresses.
Please read through this guide and see what you find: https://nav.uninett.no/doc/4.8/howto/debugging-topology.html
(I see that guide needs a slight update: The "Direct neighborship candidate" report is now available directly as a hyperlink when browsing a specific port in ipdevinfo.