Devices Introducing Themselves
LLDP — the Link Layer Discovery Protocol — is a vendor-neutral layer-2 protocol whose entire job is letting network devices announce their identity and capabilities to whatever is directly connected to them. At a regular interval, each device sends a small advertisement out each of its ports saying, in effect, "here is who I am, which port this came from, and what kind of device I am." Anything on the other end of that link receives the message and stores it.
The key word is directly connected. LLDP advertisements are not forwarded — they travel exactly one hop and stop. A switch learns about its immediate neighbours, not the whole network. By collecting these neighbour relationships from every device, though, a management system can assemble the complete physical topology, link by link. It is a discovery protocol, not a routing one: it tells you what connects to what, and influences nothing about how traffic flows.
What LLDP Tells You
Each advertisement carries a set of facts encoded as TLVs — type-length-value fields, a flexible format where each piece of information states its type, its length, and then its value. This structure lets LLDP carry a mix of mandatory and optional details, and lets vendors add extensions without breaking the format. The core information includes:
| Field | What it tells the neighbor |
|---|---|
| Chassis ID | An identifier for the device (often its MAC address or name) |
| Port ID | The exact port the advertisement was sent from |
| System name | The device's configured hostname |
| System description | Model and software details |
| Capabilities | What the device is — switch, router, access point, phone |
| Management address | The address to reach the device for administration |
Together, the chassis ID and port ID are the pair that makes LLDP so useful for cabling: they tell you precisely which device and which port sits at the far end of a given link. Optional extensions push further, advertising things like the VLAN in use or power-over-Ethernet requirements.
LLDP vs CDP
If you have worked with network gear you may have met CDP, the Cisco Discovery Protocol, which does much the same job. The distinction is straightforward and matters in mixed environments:
| LLDP | CDP | |
|---|---|---|
| Standard | Open IEEE standard | Cisco proprietary |
| Interoperability | Works across all vendors | Cisco devices only |
| Best for | Mixed-vendor networks | All-Cisco networks |
CDP predates LLDP and is functionally similar, but because it is proprietary it only speaks between Cisco devices. LLDP is the open standard that any vendor can implement, making it the interoperable choice in networks that mix equipment from different manufacturers. In practice many devices run both, using CDP among Cisco gear and LLDP to talk to everything else — so a neighbour table may show entries learned by either protocol.
A Note on VoIP Phones
One especially common use of LLDP deserves a mention because it is everywhere in offices: VoIP phone provisioning. A desk phone, when plugged in, needs to know which voice VLAN to use and how much power it may draw over the Ethernet cable. Using an LLDP extension known as LLDP-MED (Media Endpoint Discovery), the switch advertises exactly that, and the phone configures itself automatically — joining the right VLAN and negotiating power without anyone touching its settings. It is LLDP quietly doing the unglamorous work that makes plug-and-play network phones possible.
Why It Matters: Self-Documenting Networks
The deeper value of LLDP is that it makes a network self-documenting. Cabling records go stale the moment someone moves a patch lead; LLDP reflects reality as it is right now. Read a switch's neighbour table and you can see, port by port, what is actually attached — invaluable for verifying cabling, locating a device, or untangling a wiring closet. Network monitoring and topology-mapping tools lean heavily on LLDP for exactly this reason: they poll devices for their neighbour information and stitch it into an accurate live map without any manual record-keeping.
That visibility is also why LLDP is sometimes deliberately disabled on ports facing untrusted networks — the same information that helps an administrator map the network would also help an attacker who gained a foothold understand the layout. On internal infrastructure, though, the trade-off overwhelmingly favours having it on: faster troubleshooting, accurate topology, and automatic provisioning of devices like phones. It is a small, constant background chatter that pays for itself the first time someone needs to know what is on port 12. For how switches themselves move traffic once the topology is known, see how a switch switches.
Frequently Asked Questions
What is LLDP?
The Link Layer Discovery Protocol — a vendor-neutral layer-2 protocol that lets devices advertise their identity and capabilities to directly connected neighbors. Each device periodically sends information like its name, the link's port, and its device type, so equipment learns about its immediate neighbors automatically.
What does LLDP advertise?
Details about the sending device and port: the device identifier and name, the exact egress port, a system description, and capabilities such as switch or router. These are carried as TLV fields, and extensions can add VLAN, power-over-Ethernet, and management address information.
What is the difference between LLDP and CDP?
Both discover directly connected neighbors, but CDP is Cisco-proprietary and works only between Cisco devices, while LLDP is an open IEEE standard supported across vendors. LLDP is the interoperable choice in mixed networks. Many devices run both — CDP among Cisco gear, LLDP across the rest.
Is LLDP a routing protocol?
No. LLDP exchanges no routes and does not affect forwarding. It is purely a discovery and information protocol at layer 2 that tells devices about their immediate neighbors. Its advertisements stay on the local link, building a picture of direct connections rather than network-wide paths.
Why is LLDP useful?
It makes networks self-documenting. Administrators and tools can read neighbor information to map which device connects to which port, verify cabling, and troubleshoot faster. It also helps VoIP phones learn their voice VLAN and power settings automatically, and lets monitoring systems build an accurate live topology.