Thank you, Morten, for pointing out debugging resources for trouble shooting topology issue.
I think that I may have found the reason why we are getting bad topology.
We are a "Brocade" (Foundry->Brocade->Ruckus&Extreme now) shop. When we enabled lldp on routers, the lldp chassis ID and port ID was populated with a single MAC address, typically the first interface MAC address. It turns out every physical port becomes a candidate port! The discerning information, however, is contained in the port description such as GigabitEthernet3/1, which is probably not being used for NAV topology processing yet. For our Brocade edge switches, the port ID indeed matches the MAC address of the port, it detects the topology just fine.
Thanks again!
Zhi-Wei Lu IET-CR-Network Operations Center University of California, Davis (530) 752-0155
-----Original Message----- From: Morten Brekkevold morten.brekkevold@uninett.no Sent: Monday, March 19, 2018 4:02 AM To: Zhi-Wei Lu zwlu@ucdavis.edu Cc: nav-users@uninett.no Subject: Re: netmap and lag
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 er_interface_descriptions [2] https://github.com/UNINETT/nav/issues/1669 [3] https://nav.uninett.no/doc/4.8/howto/debugging-topology.html
-- Morten Brekkevold UNINETT