Discovering Neighbors with CDP and LLDP

This episode uses Discovering Neighbors with CDP and LLDP to build practical networking judgment. The key ideas are: neighbor protocols report direct adjacencies; local and remote port identities must be read together; and live evidence should be compared with the intended topol…

Today's lesson is Discovering Neighbors with CDP and LLDP. Cisco Discovery Protocol, or CDP, is Cisco's Layer Two neighbor-discovery protocol for directly connected Cisco devices. Layer Two is important here. CDP is concerned with the local connection between neighboring devices, not with tracing an end-to-end route across the network.

If two participating Cisco devices are directly connected and exchanging CDP information, each can learn information about the neighbor on the other end of that connection. This lesson turns on three relationships. First, neighbor protocols report direct adjacencies. Second, local and remote port identities must be read together.

Third, live evidence should be compared with the intended topology. Use those relationships to organize the scenario and to decide what the evidence can actually prove. Begin with the mental model. Think of the resulting neighbor entry as evidence about an adjacency.

It can associate a neighboring device identity with the local interface where that neighbor was heard. It can also expose the neighboring port associated with the connection. That combination is useful because a device name alone doesn't tell you how the cable is attached. A local port and a remote port turn a general statement such as switch one connects to switch two into a specific port relationship that you can compare with the intended topology.

Link Layer Discovery Protocol, or LLDP, serves a similar neighbor-discovery purpose but is vendor-neutral. That distinction matters when the directly connected neighbor isn't a Cisco device, or when you want a standards-based discovery protocol across a mixed-vendor environment. LLDP still operates within the local neighbor relationship. Vendor-neutral doesn't mean end to end, and it doesn't mean every device must participate.

The protocol must be enabled and exchanged on the relevant connection before its neighbor information can describe that relationship. CDP and LLDP can both contribute useful evidence on a Cisco network. Their names and configuration controls differ, but the central question is the same: what device is directly connected here, and which local and remote interfaces form that connection? If the expected neighbor doesn't appear, you don't yet know that the neighbor is unreachable across the entire network.

You know that the expected discovery relationship hasn't been observed in the output you checked. That narrower statement keeps your troubleshooting tied to the evidence. That prediction gives the configuration a purpose. You're not enabling a protocol merely because its command appears in a study guide.

You're enabling neighbor discovery so that the participating devices can exchange local adjacency information, and then you're checking whether the resulting table matches the expected device and port relationship. A command that the device accepts is only a configuration input. The operational neighbor entry is the evidence that the relationship is actually being observed. LLDP also has a global control, represented by LLDP run.

At the interface level, LLDP transmission and reception can be controlled separately with LLDP transmit and LLDP receive. That separation gives you a more precise prediction. A device must transmit for its neighbor to receive its advertisement. It must receive to learn the advertisement sent by the neighbor.

If reception isn't operating on switch one, switch one won't build the expected LLDP neighbor information from that connection even if switch one is still transmitting information of its own. The companion reference preserves source-derived technical detail related to sample CDP and LLDP tables, interface names, and topology map. Use it at a screen or in a lab rather than trying to memorize the exact display by ear. Read one requirement at a time, predict the expected state, and compare that prediction with the artifact in front of you.

Now connect that model to observable behavior. Start with the local interface. If you're checking switch one's first interface, find the neighbor associated with that local port. Then identify the reported neighboring device and the remote port associated with it.

Compare all three pieces with the cable map. A matching device name with a mismatched remote port is still a discrepancy. A matching port number attached to an unexpected device is also a discrepancy. Verification means reconciling the complete relationship, not scanning until one familiar value appears.

Now consider the opposite result. The cable map says the devices are connected, but no expected neighbor appears. Check the protocol whose output you're interpreting. A missing CDP entry doesn't by itself prove that the cable is absent, especially if the neighbor isn't a participating Cisco device.

LLDP may be the appropriate vendor-neutral choice for that connection. If the protocol is appropriate, compare the expected configuration with the operational state. Check the global control, the relevant interface participation, and, for LLDP, the required transmit and receive directions. This is where changing one supported variable at a time matters.

If you simultaneously enable both protocols everywhere, alter several interfaces, and move a cable, a neighbor might appear without telling you which change corrected the condition. Instead, state the smallest difference that could explain the evidence. If LLDP is globally enabled but reception is disabled on the local interface, correct that reception setting and repeat the same neighbor verification. A new entry then has a clear relationship to the change you made.

You should also resist treating configuration text as the final answer. Seeing CDP run in the configuration cannot confirm that a particular interface is participating or that a neighbor is exchanging CDP there. Seeing LLDP run does not demonstrate that both directional controls are operating on the relevant interface. Configuration tells you what the device has been instructed to do.

Neighbor output tells you whether the directly connected discovery relationship is observable. You need both views when the result doesn't match your prediction. Next, separate similar-looking causes. The most important scope limit appears when someone says, I can see the neighbor, so the application should work.

That conclusion goes beyond the evidence. A CDP or LLDP neighbor entry confirms discovery information about a directly connected relationship where the protocol is being exchanged. It isn't an end-to-end path test. It doesn't demonstrate application reachability through every later device and connection in the network.

The reverse mistake is also possible. An absent neighbor entry doesn't automatically prove that all communication over the connection has failed. Neighbor discovery depends on the relevant protocol being enabled and exchanged. If discovery is disabled, the expected entry may be absent even though the physical connection is present.

Stay with what the observation supports. No entry means you haven't observed that protocol's neighbor relationship in the checked output. It doesn't, by itself, settle every other question about the link or the wider path. A disciplined troubleshooting sequence begins with the expected relationship.

Name the local device, local port, neighboring device, remote port, and discovery protocol. Then collect the output that directly represents that protocol. If the result differs, isolate the smallest relevant configuration or state difference. Make one justified correction and repeat the original verification.

Reusing the same check matters because it lets you compare before and after states. The goal isn't simply to make a symptom disappear. It's to produce a repeatable neighbor result that agrees with the intended connection. Now reconcile the port information.

The first entry agrees with switch one's local interface but reports a remote interface different from the map. The second entry reports the expected neighboring device and remote port. That gives you one matching relationship and one mismatch. Don't average them into a vague conclusion that the topology is mostly right.

Each adjacency stands on its own. The matching entry supports its direct relationship. The mismatch tells you exactly which documented port relationship needs investigation. Finally, turn the evidence into one justified action.

This method also protects you from overreading device identity. A neighbor name is useful, but the topology inference becomes stronger when you pair identity with the local and remote ports. If switch two appears on an unexpected local interface, you may still have discovered the correct device through a different connection than intended. If the expected local interface reports another neighbor, the live adjacency differs from the plan.

The neighbor table helps locate the discrepancy because it connects who was discovered with where the discovery was heard. For the current CCNA version covered in this season, the published objective asks you to configure and verify the two Layer Two discovery protocols. That wording calls for more than matching a definition to an acronym. You should be able to translate a requirement into an expected configuration state, predict the neighbor relationship, apply the appropriate controls, and verify the resulting identity and port mapping.

When the result is wrong, use the same model to identify the smallest difference that explains it. The sequence is consistent whether you're checking CDP or LLDP. First decide which protocol fits the requirement and the directly connected devices. Next decide where it must operate and, for LLDP, which transmission and reception behavior the relationship requires.

Then predict the neighbor entry before looking for it. Finally, compare the live device identity and port relationship with the intended map. That process turns a table of neighbor information into an operational check rather than a collection of values to memorize. Back at switch one, you can now answer the original question precisely.

The cable map records what should be connected. The neighbor output supplies current discovery evidence about what participating devices report on that local relationship. If switch one and switch three report matching local and remote port relationships, you have strong observed operating state of that direct adjacency, while the disagreement with the map remains something to investigate. You haven't proved why they differ, and you haven't proved end-to-end application reachability.

You have identified the exact neighboring relationship that the available evidence supports. Finish by applying the model. CDP and LLDP make directly connected relationships observable. CDP focuses on participating Cisco neighbors, while LLDP provides a vendor-neutral option.

In either case, useful verification connects a neighbor's identity with the local and remote ports, then compares that live relationship with the intended topology. If the result doesn't match, check the relevant protocol state and correct one evidence-supported difference at a time. Most importantly, keep the conclusion proportional to the evidence. A neighbor entry can validate a local adjacency where discovery information is exchanged.

It cannot, on its own, prove that an application is reachable through the rest of the network. Knowledge check: What conclusion can a neighbor entry support, and what broader conclusion can it not support? Pause here and answer in your own words.

Name the relevant relationship, the evidence you would inspect, and the conclusion that evidence would support. Thanks for listening. This lesson was produced by Bare Metal Cyber dot com.

Discovering Neighbors with CDP and LLDP

headphones Listen Anywhere

More Options »
Broadcast by