Port Discovery with LLDP and CDP

The GigaVUE H Series is capable of snooping Link Layer Discovery Protocol (LLDP) packets and Cisco Discovery Protocol (CDP) packets. If the devices in your network use either of these protocols, a GigaVUE H Series node can identify its immediate neighbors and their capabilities. Snooped LLDP and CDP information includes the remote port and chassis IDs, as well as other selected information, if it is included by the sender. This information can be used to determine the origin of traffic flows.

All GigaVUE H Series and TA Series nodes support LLDP and CDP port discovery,

LLDP and CDP are physical topology discovery protocols (Layer 2). The protocols are unidirectional. Devices send their identity and capabilities in a packet. The GigaVUE H Series node receives the packet and extracts information from it, such as the chassis ID and port ID of a neighbor. The information from the neighbors varies depending on what is sent in the packet.

An LLDP packet supports the following capabilities in a type-length-value (TLV) structure. The first four capabilities are mandatory.

• Chassis ID
• Port ID
• Time-to-Live (TTL)
• End of TLVs
• Port description
• System name
• System description
• System capabilities available
• System capabilities enabled
• VLAN name
• Management address
• Port VLAN ID
• Management VLAN ID
• Link Aggregation port ID
• Link Aggregation status
• Maximum Transmission Unit (MTU)

A CDP packet supports the following capabilities in a TLV structure:

• Device ID
• Port ID
• Platform
• Software version
• Native VLAN ID
• Capabilities
• Network prefix address
• Network prefix mask
• Interface address
• Management address

The LLDP/CDP discovery packets are copied and parsed by the GigaVUE H Series node, and the neighbor information is cached. Discovery packets are not terminated on the GigaVUE H Series node, nor are they removed from the ingress data stream.

Notes:

• Port discovery can be enabled on network, tool, and circuit type ports.
• Use port discovery on ports fed by SPAN ports or aggregators with caution.
LLDP/CDP information received from a SPAN port may be misleading, depending on how it is configured. When a large range of ports are SPANed, different and conflicting LLDP/CDP information may be received. LLDP/CDP is best used on TAPed network interfaces.