Hello,
So I looked at several nodes on both ends. They do show up on either end as a “Candidate neighbor.” However, it does appear that it is using CDP instead of LLDP. Is there a way to force NAV to use LLDP only?
Thanks, Will From: nav-users-request@uninett.no [mailto:nav-users-request@uninett.no] On Behalf Of Sigmund Augdal Sent: Monday, December 4, 2017 12:12 AM To: nav-users@uninett.no Subject: Re: Netmap
Hi,
NAV 4.8 includes various changes to the topology analysis code in NAV. One change cleans up previously deducted topology when ports has been re-used for other purposes. The other fixes some buges where NAV would incorrectly deduce that certain port pairs were connected when they in fact were not, and this in term caused NAV to fail to detect the proper topology. Both of these changes could lead to isolated nodes in cases were NAV is not able to detect the correct topology. In order to resolve these issues it would be very useful to have some information about the topology candidates nav has gathered for the ports in question.
Go to the reports overview and click "Report List" and then "Direct neighborship candidates". Click "Filter" and type the sysname of an isolated node in the sysname field and the name of an uplink port in the interface field and press filter. Does the expected upstream device show up in the list? What is in the "source" column.
Then repeat for the expected port on the upstream device. If you could send us the lists of candidates for both ends it would be of great help to debug.
In order to get the best topology results we recommend using lldp on all topology ports, and to _not_ use CDP in mixed Cisco/HP networks
Best regards Sigmund Augdal UNINETT AS
On 01. des. 2017 18:29, William Daly - Network Specialist, VUSD Technology wrote: Hello,
I am also having issues with isolated nodes in netmap. I updated to 4.8.1, and now I have unconnected nodes.
From: nav-users-request@uninett.nomailto:nav-users-request@uninett.no [mailto:nav-users-request@uninett.no] On Behalf Of Erik Kemper Sent: Friday, December 1, 2017 2:50 AM To: nav-users@uninett.nomailto:nav-users@uninett.no Subject: RE: Netmap
Hi,
They show up when I select “isolated” in the view. But how they got isolated, I cannot figure out?
Met vriendelijke groet/ Kind regards,
Erik Kemper Senior Datacenter Engineer
[cid:TWCBFHKXFKRH.IMAGE_1.BMP]
Quaker Chemical B.V. I Industrieweg 7 I 1422 AH Uithoorn I The Netherlands T: +31 (0)297 544430 I F: +31 (0)297 544694 kempere@quakerchem.commailto:kempere@quakerchem.com I quakerchem.comhttp://www.quakerchem.com/ Commercial Register Amsterdam No: 33.109.151 I VAT no: NL 001277613 B01
From: nav-users-request@uninett.nomailto:nav-users-request@uninett.no [mailto:nav-users-request@uninett.no] On Behalf Of Erik Kemper Sent: Friday, December 1, 2017 11:25 To: nav-users@uninett.nomailto:nav-users@uninett.no Subject: RE: Netmap
Hi,
Okido, will do!
(Did not see that HowTo.. 😊)
Met vriendelijke groet/ Kind regards,
Erik Kemper
Senior Datacenter Engineer
Quaker Chemical B.V. I Industrieweg 7 I 1422 AH Uithoorn I The Netherlands
T: +31 (0)297 544430 I F: +31 (0)297 544694
kempere@quakerchem.commailto:kempere@quakerchem.com I quakerchem.com
Commercial Register Amsterdam No: 33.109.151 I VAT no: NL 001277613 B01
-----Original Message----- From: Morten Brekkevold [mailto:morten.brekkevold@uninett.no] Sent: Friday, December 1, 2017 11:12 To: Erik Kemper <kempere@quakerchem.commailto:kempere@quakerchem.com> Cc: nav-users@uninett.nomailto:nav-users@uninett.no Subject: Re: Netmap
On Fri, 1 Dec 2017 09:46:42 +0000 Erik Kemper <kempere@quakerchem.commailto:kempere@quakerchem.com> wrote:
Nothing special, just the regular weekly update run?
I don't know what "the regular weekly update run" entails, so I still don't know what changed.
The minimum amount of information we need to make sense of a problem report is at least the NAV version in use.
In your case, I'd suggest reading through [1] and come back with some more detailed information about your system and your symptoms.
[1] https://nav.uninett.no/doc/howto/debugging-topology.htmlhttps://urldefense.proofpoint.com/v2/url?u=https-3A__nav.uninett.no_doc_howto_debugging-2Dtopology.html&d=DwMGaQ&c=F5qNGIc8vBNKKqPbpKxOcFhXsOwF7YYLtYbYjCsgcyQ&r=LAbkUnAQd69GuespFDkbTRHs9hRt_gzLVbEy3tsSudk&m=BDeQW03YSOlSf_bZ8ZgnsEToRGk2qupwxypGRysCt1k&s=o7VDldPaIv9uVodAiV56c2zJvJMnlKr6-WaOIFP1mwE&e=
--
Morten Brekkevold
UNINETT
QUAKER CHEMICAL CORPORATION DISCLAIMER: This message is intended only for the use of the individual or entity to which it is directed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by reply e-mail and delete the message and any attachments.