zNetLaB › Guided labs › Enterprise
CDP and LLDP — discover the neighbours, document the links
Enterprise Beginner 3 devices 4 checked tasks 100 points Free lab
Nobody labelled the cables. Use CDP to see who is on each port, turn on LLDP so the non-Cisco kit can be seen too, and put what you found into the interface descriptions on both ends. You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This is a free lab: it stays open on the free plan. It needs an account, which keeps your progress.
The scenario
Nobody labelled the cables. Use CDP to see who is on each port, turn on LLDP so the non-Cisco kit can be seen too, and put what you found into the interface descriptions on both ends.
Your role: a network engineer on the enterprise team. Level: Beginner Done when: all 4 goals show as passed (100 points).
Network status
Devices: 2 routers, 1 switch, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. R1 starts with addresses (G0/0 10.0.0.1/24). R2 starts with addresses (G0/0 10.0.0.2/24). SW1 starts with an empty configuration. Known problems
None: nothing is misconfigured. The network is simply not finished: what the goals list is what you have to build or secure. Goals
LLDP runs on R1 and on the switch (25 pts) R1’s uplink description names SW1 (25 pts) The switch ports name R1 and R2 (30 pts) R1 and R2 still reach each other (20 pts) The activity, in order
LLDP runs on R1 and on the switch Why: Each goal is a state the lab can check on the running device. Verify with: show running-config R1’s uplink description names SW1 Why: Each goal is a state the lab can check on the running device. Verify with: show running-config The switch ports name R1 and R2 Why: Each goal is a state the lab can check on the running device. Verify with: show running-config R1 and R2 still reach each other Why: A ping needs a route in BOTH directions. This is the end-to-end proof that everything before it worked. Verify with: ping 10.0.0.2 Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong. Why this matters
Nobody labelled the cables. Use CDP to see who is on each port, turn on LLDP so the non-Cisco kit can be seen too, and put what you found into the interface descriptions on both ends.
What you will be able to do
LLDP runs on R1 and on the switch
R1’s uplink description names SW1
The switch ports name R1 and R2
R1 and R2 still reach each other
The network
ISR 2911, Catalyst 2960-24TT — 3 devices in all, already cabled.
Gi0/0 10.0.0.1/24 Gi0/1 Gi0/0 10.0.0.2/24 Gi0/2 R1 SW1 R2 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
R1 ISR 2911 configure it SW1 Catalyst 2960-24TT configure it R2 ISR 2911 configure it
Cabling
R1 Gi0/0 ↔ SW1 Gi0/1 R2 Gi0/0 ↔ SW1 Gi0/2
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
R1 interface g0/0
ip address 10.0.0.1 255.255.255.0
no shutdown
exit R2 interface g0/0
ip address 10.0.0.2 255.255.255.0
no shutdown
exit Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 LLDP runs on R1 and on the switch 25 Checked automatically against the device’s live state (lldpOn). and Checked automatically against the device’s live state (lldpOn). 2 R1’s uplink description names SW1 25 Checked automatically against the device’s live state (ifaceDesc). 3 The switch ports name R1 and R2 30 Checked automatically against the device’s live state (ifaceDesc). and Checked automatically against the device’s live state (ifaceDesc). 4 R1 and R2 still reach each other 20 On R1: ping 10.0.0.2 must succeed.
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
R1 lldp run
interface g0/0
description Uplink to SW1 Gi0/1
exit SW1 lldp run
interface g0/1
description R1 Gi0/0
exit
interface g0/2
description R2 Gi0/0
exit Where this is examined
This lab practises these topics in the zNetLaB certification courses:
Related labs
Where to start
The lessons all guided labs plans
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.