WARNING - this email is originated from outside the City of East Grand Forks email system. Do not click any link and do not open attachments unless you can confirm the sender.

On Wed, 28 Sep 2022 14:25:29 +0000 Marco Valerio Bifolco <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
_______________________________________________
Nav-users mailing list -- nav-users@lister.sikt.no
To unsubscribe send an email to nav-users-leave@lister.sikt.no