This resolve by self. With more uptime, it could learning.
Other similar issues has appear.
Could I remove an erroneous neighbor? I will try on interface table ;)
Ok. The better solution is turn on LLDP on all sw and this trunk ports...
Em 22/05/2023 10:44, Morten Brekkevold escreveu:
On Mon, 8 May 2023 22:51:21 -0300 Marcos Tadeu marcos@telecom.uff.br wrote:
Copper0/25 at GRA-A-CPD-HP1905
To IP device 172.30.3.30
And the click on Direct neighborship candidates
on Copper0/25 returns empty list !
On 172.30.3.30 has no reference to GRA-A-CPD-HP1905
All this means is that NAV has resolved 172.30.3.30 as a neighbor on port Copper0/25, but has not been able to detect which port is connected on the other end. Typical if this topology was detected using CAM data with no reciprocity.
The question is: What is *actually* on the other end of Copper0/25 ?