HI, Again thanks for your time, yes it is a mlag configuration, but the strange thing, it's that is not the only one, but is the unique having this problem.
So, I guess again my only chance is the feature to choose the right neighbor. Any advice will be appreciated. Thanks Best Regards Marco V. Bifolco System Engineer Office (+39) 0694320122 | Mobile (+39) 3519666252 marco.bifo...@sferanet.net assiste...@sferanet.net sferanet.net -----Messaggio originale----- Da: Morten Brekkevold <morten.brekkev...@sikt.no> Inviato: venerdì 21 ottobre 2022 13:29 A: Marco Valerio Bifolco <marco.bifo...@sferanet.net> Cc: nav-users@lister.sikt.no; Isaia Mammano <isaia.mamm...@sferanet.net> Oggetto: Re: R: [Nav-users] Nav - LLDP Missing on some FS model On Wed, 5 Oct 2022 14:29:45 +0000 Marco Valerio Bifolco <marco.bifo...@sferanet.net> wrote: > But now I got an other issue, s3900 model that I'm sure is working due > 6 of them with same firmware are working fine, seems to be isolated, > but looking on candidate it has 2 lldp neighbour that it is not using The exact reason NAV isn't using it is because there are *2* instead of *1*. NAV's topology model will only allow a single neighbor on any port - and this port reports *2* neighbors. How can `Trunk1` have *2* neighbors? Is a virtual MLAG port? -- 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-le...@lister.sikt.no
