CCNA lab 6 of 46
Validate network documentation with CDP and LLDP
Audit a site's cabling records against what the devices themselves report with CDP and LLDP, correct three documentation errors, label every link and switch discovery off where it leaks information.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 4,096 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNA 200-301 guided labs, then 06 - Validate network documentation with CDP and LLDP
- Level
- Beginner
- Time
- About 40 minutes
- Nodes need
- 4 vCPU, 4,096 MB
- Smallest plan
- Lite
The scenario
You've joined Kestrel Logistics as their first in-house network engineer. Before changing anything, your manager wants the site documentation checked. The records below were written by a contractor years ago, and nobody trusts them. Discovery protocols let the devices tell you what is really connected, so you'll use CDP and LLDP to audit every link, correct the records and label the interfaces properly.
The contractor's documentation (contains errors):
| Local device | Local port | Remote device | Remote port |
|---|---|---|---|
| R1 | Gi0/1 | S1 | Gi0/0 |
| R2 | Gi0/1 | S1 | Gi0/3 |
| S1 | Gi0/1 | S2 | Gi0/1 |
| S1 | Gi0/3 | S2 | Gi0/3 |
| R1 | Gi0/0 | R2 | Gi0/0 (WAN, provider-managed) |
| Device | Model | Software | Management address |
|---|---|---|---|
| R1 | IOSv | 15.9 | 10.6.0.1 |
| R2 | Cisco 2911 | 15.4 | 10.6.0.6 |
| S1 | IOSvL2 | 15.2 | 10.6.0.11 |
| S2 | IOSvL2 | 15.2 | 10.6.0.12 |
What you’ll practise
- Map a network from show cdp neighbors and show cdp neighbors detail
- Enable LLDP and compare it with CDP
- Find and correct cabling and inventory errors in documentation
- Write accurate interface descriptions from discovery data
- Disable discovery protocols on an untrusted interface and tune their timers
The tasks
- Map the network with CDP
- Get the details
- Correct the cabling records
- Label every link
- Turn on LLDP and compare
- Stop discovery where it leaks information
- Tune the timers on the switches
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- R1
Gi0/1to S1Gi0/0 - R2
Gi0/1to S2Gi0/0 - S1
Gi0/1to S2Gi0/1 - S1
Gi0/2to S2Gi0/2 - R1
Gi0/0to R2Gi0/0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 1,024 MB |
| R2 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 1,024 MB |
| S1 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 1,024 MB |
| S2 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
CCNA 200-301 guided labs.Open
06 - Validate network documentation with CDP and LLDPand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More CCNA labs
Related labs in other courses
CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.