Hi, Thanks for your support,
I can't really say if that model as lldp-mib (I'll ask the vendor) . But now I got an other issue, s3900 model that I'm sure is working due 6 of them with same firmware are working fine, seems to be isolated, but looking on candidate it has 2 lldp neighbour that it is not using . [cid:image001.png@01D8D8D6.D4F31110] [cid:image002.png@01D8D8D7.341A80B0]
[cid:image003.png@01D8D8D7.341A80B0] [cid:image004.png@01D8D8D7.341A80B0]
I don’t know why this is happening, as you can see in this case nav in able to retrieve lldp info, but not using them. So if it’s not possible to solve it, I would suggest to add the possibility on candidate neighbours a button “choose this as elected neighbor” or something like .
Many thanks again
Marco V. Bifolco
System Engineer
Office (+39) 0694320122 | Mobile (+39) 3519666252
marco.bifolco@sferanet.net
assistenza@sferanet.net
sferanet.net
-----Messaggio originale----- Da: Morten Brekkevold morten.brekkevold@sikt.no Inviato: giovedì 29 settembre 2022 15:51 A: Marco Valerio Bifolco marco.bifolco@sferanet.net Cc: nav-users@lister.sikt.no; Isaia Mammano isaia.mammano@sferanet.net Oggetto: Re: [Nav-users] Nav - LLDP Missing on some FS model
On Wed, 28 Sep 2022 14:25:29 +0000 Marco Valerio Bifolco <marco.bifolco@sferanet.netmailto:marco.bifolco@sferanet.net> wrote:
First of all thanks for your job, we really appreciate nav solution.
Thank you for using it :)
We noticed that some of our FS.COM switch, (we got, cisco, hp, dlink,
fs) does not work as expected. Nav doesn’t get LLDP information, and
for this it is wrongly populating the net map.
I assume the switches *do* support LLDP, then. You need to confirm whether the switches support the LLDP-MIB, as specified in IEEE Std 802.1AB-2005. This is currently the only API NAV supports for getting LLDP information from a device.
The FS model working properly are s3900, s5850; But not so lucky with
s2800, s1400, s3400 .
I have no experience with FS.COM equipment, so I cannot really comment as to why that seems to be the case.
It's possible to force nav to choose a neighbor from cam candidate? Or
set it manually?
Not really, although that could be a viable feature request.
NAV will trust LLDP or CDP over CAM information - but relying on CAM information isn't foolproof, since a MAC address will be "visible" on many switch ports. An algorithmic reduction of the possible candidates per port must take place over the entirety of the collected layer 2 information. If the collected information isn't complete, there will sometimes be incorrect neighbor guesses.
Or is it possible to make these switch works with nav? Maybe passing
mib somehow?
Again, you need to verify which MIBs are supported by the FS devices.
--
Sincerely,
Morten Brekkevold
Sikt – Norwegian Agency for Shared Services in Education and Research