CCNA v2.0, section 5.0, lab 1, in slides: give R1, R2 and R3 an NTP server in Packet Tracer, by hand over SSH and through the network controller, whose inventory is read in its web page and through its REST API; read the same change as an Ansible playbook and as a pull request, compare the approaches on a worksheet; then break the change in four ways (the NTP service off, Telnet only, a wrong controller credential, a drift) and see which approach finds each one.
The slides
The lab is twenty slides in four parts, after an introduction, one step each.
- Introduction: what the lab does, and what it needs.
- 1. By hand: SRV1's NTP service, the NTP server added to each router over SSH, the routers synchronizing, and a drift made and found.
- 2. Through a controller: the network controller NC1, its web page, a CDP discovery, its inventory, and its REST API.
- 3. Automation and code: the change as an Ansible playbook, as a pull request, and a worksheet comparing the approaches.
- 4. Fault round: the NTP service off, Telnet only on R3, a wrong credential in the controller, and a drift on R2.
The files
- The network it starts from:
lab4-6.pkt, the company network as section 4.0's last lab,
Lab 4.6, left it; the lab saves lab5-1.pkt. - The configurations it builds, and the controller's API exchanges, as plain text, in the
ccna repository.
- What Packet Tracer cannot do: run Ansible or a Git pipeline, so those two views are prepared; the controller's API exchanges are prepared output too.
- The lesson:
Network Management Approaches.