Campus Configuration

Now that the compiled output is available to use for validation, safely move forward using the data models and dynamic templates to take full control of the network configurations. At this point, there are changes that will be made in the first run of this playbook. Changes may have been performed manually to ensure parity between intent-based configurations and live running-configurations.

Either way, the next playbook should be executed with caution. Use verbose check mode and limit the device scope at first. This is to ensure there is awareness of the configuration changes the playbook will make.

Execute playbook

First, a playbook that serially executes tasks in order device-by-device is shown. The first task is to gather facts, followed by the modular configuration tasks to be performed on each device. It is important to understand these tasks run on each device in sequence, as opposed to running to completion on a device, then configuring the next device.

Finally, we will perform a copy running-configuration startup configuration command, committing all changes to the device. The advantages and disadvantages of this approach are discussed after examining the playbook in action.