6.1 Explain how automation impacts network management

The problem with doing everything by hand

Imagine you are the network administrator for a company with 300 switches. The security team asks you to add a new NTP server and change the syslog destination on every switch. The “traditional” way is to SSH to each switch one at a time, paste the commands, save the configuration, and move on. If each device takes three minutes, that is fifteen hours of tedious, error-prone work. Somewhere around switch 140 you will fat-finger an IP address, and you may not discover it for months.

Now imagine that every one of those switches is described in a text file, and you run a single script that pushes the change to all 300 devices in a few minutes, then verifies that each one accepted it. That is network automation, and it changes how networks are managed in several important ways.

Benefits of automation

Benefit	What it means	Why it matters
Consistency	Every device is configured from the same template	No two switches drift into slightly different configs
Fewer human errors	Software does not mistype addresses or skip steps	Typos are the leading cause of outages caused by change
Speed	Hundreds of devices can be changed in minutes	Faster response to security incidents and business needs
Scale	The effort to manage 3,000 devices is close to the effort for 30	Large networks become manageable by small teams
Repeatability	The same task can be re-run any time with the same result	Rebuilding a failed device becomes a push-button job
Documentation	The automation files are the documentation	The network’s intended state is always written down
Cost	Less engineer time per change	Lower operational expense (OpEx)

Configuration drift

Configuration drift is what happens when devices that started out identical slowly become different because of years of one-off manual changes. One switch has an extra VLAN, another has an ACL that was “temporarily” added in 2019, a third has a typo in its SNMP community. Drift makes troubleshooting slow (“why does this one behave differently?”) and makes outages more likely. Automation tools attack drift in two ways: they push a known-good configuration to every device, and many of them can periodically compare the device’s running configuration to the desired configuration and report (or fix) any differences.

Intent-based networking (IBN)

Traditional configuration describes how to do something: “on interface GigabitEthernet1/0/5, set switchport mode access, set access VLAN 20, enable PortFast.” Intent-based networking lets you describe what you want: “all printers must be in the Printers segment and must not be able to reach the finance servers.” A controller (such as Cisco Catalyst Center) translates that intent into the specific configuration on every device that needs it, pushes it out, and then continuously verifies that the network is actually delivering the intent. If a device is replaced, the controller re-applies the intent to the new device automatically. IBN is the goal that controller-based networking and automation are working toward.

How automation changes the administrator’s job

Automation does not eliminate network engineers; it changes what they do. Instead of typing configuration, an engineer writes templates, defines policies on a controller, reviews the changes a tool proposes before they are applied, and investigates the exceptions and alerts that the automation surfaces. Skills such as reading JSON, understanding what an API is, and being able to follow a simple Python script or Ansible playbook become part of the job. The remaining objectives in this domain teach exactly those skills.