Networking · Episode 01 · 4:05

Identify neighbors with ARP, CDP and LLDP

Match CDP and LLDP neighbor output to the devices and ports on your canvas, enable and save LLDP on both endpoints, and inspect an ARP address mapping after a real traffic test. Remove the cable to diagnose a failed connection, then reconnect the same ports and verify discovery and reachability. This walkthrough uses three prepared routers, including an unconnected control device. Supported syntax varies by device; cached ARP alone does not prove current reachability.

English narration and on-screen explanations. Read the narration transcript.

Chapters
Open MP4

Narration transcript

The English narration in this video. Select a time to watch that moment.

  1. Start with the cable and ports

  2. R1 and R2 are connected. R3 has no cable.

  3. Check the selected devices before changing a connection.

  4. Neighbor output should match the devices and ports on this canvas.

  5. Identify the directly connected neighbor

  6. The Device ID identifies the directly connected neighbor: R2.

  7. Local Intrfce is the port on R1. Port ID is the port on R2.

  8. R3 is absent because it is not connected to this link.

  9. Enable and inspect LLDP

  10. This lab starts with LLDP disabled. Use privileged EXEC before configuring it.

  11. Return to EXEC mode and save the change on each device.

  12. LLDP reports the same neighbor and the same pair of physical ports.

  13. Match an IP address to a MAC address

  14. Test the directly connected address: 10.0.12.2.

  15. The warm test must show 100 percent replies on this healthy link.

  16. ARP maps the peer IP address to its MAC address on Gi0/0.

  17. A cached address mapping alone does not prove that the link is working.

  18. Diagnose a disconnected cable

  19. Disconnect asks you to confirm which connection will be removed.

  20. The address is still configured, but the interface and line protocol are down.

  21. The disconnected device is no longer reported as an adjacent neighbor.

  22. The traffic test now fails. Check the cable before changing IP settings.

  23. Restore the link and verify

  24. Reconnect the same devices on the same Gi0/0 ports.

  25. Both discovery protocols identify R2 again. R3 remains unconnected.

  26. Confirm 100 percent replies after the link is restored.

  27. Check the cable, neighbor identity, address mapping, then actual traffic.

Back to all Networking videos