TLDR: Part 3 of 10. We configure Nautobot credentials, Nornir, compliance features, and Golden Config Plans, then deploy generated intent to 13 Cisco IOS-XE routers in CML. We finish by verifying IS-IS, MPLS LDP, VPNv4 and VPNv6 route reflection, and PE-to-CE BGP.
Where we left off
Part 2 rendered intended configurations for the full topology from Nautobot Source of Truth data. This walkthrough narrows the deployment to the 13 Cisco routers that make up the service-provider network:
Four P routers running IS-IS and MPLS
Two VPNv4 and VPNv6 route reflectors
One border router
Three service-provider edge routers
Three customer edge routers
The intended files are stored in Git, but nothing should reach a router until we can answer four questions:
Can the worker authenticate to every device?
Does compliance extract the right configuration sections?
Will those sections be sent in a dependency-safe order?
Can we prove that running configuration matches intent after deployment?
This walkthrough sets up each layer in that order.
Deployment workflow
Golden Config deployment depends on fresh output from every earlier stage:
Credentials + primary IP + network reachability
-> intended configuration
-> running-config backup
-> compliance rules
-> compliance results
-> Config Plan
-> review and approval
-> deployment
-> new backup and compliance runA Config Plan stores command text when it is created. If intent, backups, rules, or source-of-truth data change, generate a new plan.
