On Fri, 16 Mar 2018 17:45:49 +0000 Zhi-Wei Lu zwlu@ucdavis.edu wrote:
We have a very limited test envioronment for NAV, our environment are Foundry based (->Brocade-> Arris and Extreme now). We have enabled lldp on edge switches, but not on ALL upstream routers. Even on connections with lldp on, the map does not show LAG ports correctly, it seems. Is there a manual way to fix netmap problem for those it fails to correctly identify the connections?
The supported router interface description conventions [1] do allow for specifically setting a `to_router` value - but I do not think the modern topology detector uses this information.
However, what exactly is wrong when "the map does not show LAG ports correctly"? What is your expectation vs. what does NAV actually show?
There is currently an open issue related to topology detection for LAG ports and LLDP [2], but if you haven't enabled LLDP everywhere, this may not be your problem. You might want to refer to the topology troubleshooting guide [3] (because Netmap is not always an accurate depiction of the topology information NAV has gathered).
[1] https://nav.uninett.no/wiki/subnetsandvlans#guide_lines_for_configuring_rout... [2] https://github.com/UNINETT/nav/issues/1669 [3] https://nav.uninett.no/doc/4.8/howto/debugging-topology.html