On Wed, 5 Feb 2020 10:52:35 +0100 (CET) jaumeramos@iesebre.com wrote:

First post here, hope it's the right place to ask questions.

You've come to the right place, welcome :-)

I'm trying NAV to document my network, it's a state college due to professional trainin with 600+ computers. My network equipment are mostly d- link switches, with mikrotik routers and some Cisco stuff.

After enabling SNMP and LLDP i got an approximate map of the network, but the trunk connections using LACP protocol does not show in the map.

Is there some additional configuration needed to make NAV detect them.

Not really, no. But proper detection can depend on several factors.

First off, NAV does not (currently) support multi-LAG. An interface in NAV can only be registered with a single neighboring device.

The detection of neighbors when LAG (LACP) is involved also depends on how a device reports its LLDP records. Some vendor/device combos will report LLDP records for the individual physical ports in an aggregate, while other will report LLDP records for the conceptual aggregate port itself. A third category will report LLDP records for all of the involved interfaces, both physical and virtual.

I see you mention Mikrotik. Please be aware that Mikrotik has known issues with their implementation of LLDP-MIB. I don't know which devices or software versions are involved, as we don't have any Mikrotik devices, but there are some details about these problems in a NAV bug report from November [1].

Also, be aware of bug #2106 [2], which may affect the correctness of your topology, regardless of LACP or Mikrotik.

Thanks for such a great piece of software.

Thanks for you kind words :-)

[1] https://github.com/Uninett/nav/issues/2015 [2] https://github.com/Uninett/nav/issues/2106