Hi all!
I'd want to add in that Alcatel Lucent Enterprise seems to have the same sort of implementation as Brocade so we are missing neighbor data from the last version as well. I haven't got the time to investigate more on this yet but it sure looks the same with the information from this discussion.
Regards, Pär
-----Ursprungligt meddelande----- Från: nav-users-request@uninett.no nav-users-request@uninett.no För Morten Brekkevold Skickat: den 9 maj 2018 11:44 Till: Zhi-Wei Lu zwlu@ucdavis.edu Kopia: nav-users@uninett.no Ämne: Re: netmap and lag
On Fri, 27 Apr 2018 23:52:40 +0000 Zhi-Wei Lu zwlu@ucdavis.edu wrote:
I'd kick Brocade in the shin to see if they would fix their issue, but I'm all ears if you have a suggestion for a workaround at the NMS level :)
Is it possible to have a manual/GUI way to set the connections, once set manually, the automatic updating would leave it along, if cdp/lldp finds discrepancy, warn about the inconsistency.
Not at the moment, no. It would be possible with some code modifications.
I believe old versions of NAV may have allowed interface descriptions to override topology, given various description string conventions. Using interface description strings to override or give more information about links and VLANs have been integral to NAV since its inception, so it would perhaps be our preferred way to implement (or reimplement) some support for this.
But again, I would also support a workaround for Brocade, in which the topology detector would not consider remote interface identifiers that aren't unique on the remote end.
-- Morten Brekkevold Uninett