Lab C19: SD-Access, step by step
Northgate Freight's new Building C has its switches racked and cabled, and Catalyst Center knows none of them. A campus fabric is built from the controller, not from the switches: you tell it which switches exist, what part each plays, which routing domains there are and what a port should do with whoever plugs in, and it writes the configuration. This lab builds the smallest fabric that carries a user, one piece per step. Each step says what must be true and where in the controller it lives. The hosts are already plugged in: staff, a contractor, the finance server and the video recorder, each known to the identity server with a group.
What you will do
- Tell the controller the switches exist
- A site, three roles, one virtual network
- Ports that admit only who the identity server knows
- Inside one virtual network, a line
- A way out
- Read one packet
New in this lab: discovery, fabric, onboarding, segmentation, handoff.
How it is checked
Each of the 6 tasks is checked on the devices themselves as you finish it: the bench reads how the network is configured and what it does, not what you typed. The lab is done when all 6 pass.
The lessons it follows
It opens after these, and uses what they teach:
- Manual underlay
- LAN automation and PnP
- Device discovery and management
- Extended nodes
- LISP and BGP control planes, host onboarding
- VXLAN data plane
- TrustSec policy plane
- L2 flooding
- Native multicast
- Single-site campus design
- Multisite design and transits
- Fabric in a box
- Authentication templates
- Port configuration
- Multisite remote border
- Border priority
- Adding devices to fabric
- Transit handoffs
- Peer device and the fusion router
- Layer 2 border handoff
- Macro segmentation
- Micro segmentation
Open the lab benchIt needs a computer: phones and tablets are not supported.
