Send netdisco-users mailing list submissions to
        netdisco-users@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/netdisco-users
or, via email, send a message with subject or body 'help' to
        netdisco-users-requ...@lists.sourceforge.net

You can reach the person managing the list at
        netdisco-users-ow...@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:

   1. Re: How to troubleshoot device connections (Damian R. Cleveland)
--- Begin Message ---
Thanks, Christian. You were right. So, applying an LLDP profile permitting the 
needed TLVS and a management address has the palo sending the required 
information to the switches. 
The problem I'm facing now is inconsistency; whenever a discover all is run, 
something different is reported. The firewall has four switches hanging from 
it. I can't consistently get ND to report them as neighbors; I get random 
combinations.

Is anyone familiar with this behavior? Is there anything I can do to make 
things more predictable?

-------
Damian Cleveland
Networking Engineering
Institute For Defense Analyses, Princeton, NJ
Office:609-279-6265
Mobile:609-235-8870
--------

----- Original Message -----
From: "Christian Ramseyer" <ramse...@netnea.com>
To: "Damian R. Cleveland" <dcl...@idaccr.org>, "netdisco-users" 
<netdisco-users@lists.sourceforge.net>
Sent: Monday, January 6, 2025 2:04:00 PM
Subject: Re: [Netdisco] How to troubleshoot device connections

On 06.01.2025 19:42, Damian R. Cleveland wrote:
> Hi.
> I'm digging.
> When I execute "sh lldp neighbor detail" from the cisco device, I get 
> the following output:
> 
> Time remaining: 102 seconds
> System Capabilities: O,P,B,R
> Enabled Capabilities: O,R
> Management Addresses - not advertised
> Auto Negotiation - not supported
> Physical media capabilities - not advertised
> Media Attachment Unit type - not advertised
> Vlan ID: - not advertised
> Peer Source MAC: e898.6db9.9a10
> 
> 
> Are those "not advertised" the problem?
> 

Yes most likely the Addresses not advertised are the issue, Netdisco 
will use this to form the neighbor relation.

Cheers
Christian



--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to