Week 12 · Lesson 1

Automation in Network Management

Networks used to be configured one device at a time, by hand, over a console. That does not scale, and it is where most outages come from. This lesson explains why the industry moved to automation — and the two ideas, configuration drift and idempotency, that underpin every automation tool you will meet this week.

CCNA 200-301 Domain 6.0 Automation and Programmability Verified 2026-10-11
Part 1

Why automate the network?

For 30 years the standard way to configure a Cisco device was to open a terminal, connect over the console or SSH, and type commands into the command-line interface (CLI). Each command changed the running configuration of exactly one device. That works well for one router, and breaks down the moment you have hundreds or thousands of devices.

Network automation is the practice of driving devices with programs and data instead of by hand. It replaces a sequence of human keystrokes with a repeatable, testable, version-controllable process. The benefits are usually summarised in four points.

Four benefits · select one to highlight it

Definition — network automation. The use of software to configure, provision, verify, and operate network devices with little or no human interaction, so that changes are repeatable, consistent, and auditable.

The key insight is that human typing is the risk. Every manual command is a chance to make a mistake — a wrong wildcard mask, a mistyped VLAN, a shut interface that should be up. Research on outages repeatedly finds human error during change as the leading cause. Automation does not eliminate human judgement; it eliminates human typing, and typing is where most mistakes happen.

Part 2

The hidden cost of manual configuration

Consider a simple change: add a new VLAN to a campus of 200 access switches. Manually, an engineer must connect to each switch, enter configuration mode, type the VLAN, verify it, save it, and move on. That is 200 repetitions of the same six steps.

Manual vs automated change · drag the device count

Automation attacks every one of these failure modes. A script holds the authoritative list of devices, applies the same change to all of them, records what it did, and can be run again safely if it is interrupted. The list of devices and the change itself become data — stored in a file, reviewed like code, and versioned with Git.

Exam tip. If a question asks for the primary reason organisations adopt network automation, the expected answer is usually reducing human error / increasing consistency and repeatability, not “because it is faster”. Speed is a benefit, but the exam frames consistency and the elimination of manual mistakes as the driving motive.
Part 3

Configuration drift

A device configured by hand, then by another engineer, then by a third, slowly stops matching the standard. Somebody adds a static route during an incident and forgets to remove it. Somebody changes a description string. Somebody disables an unused interface, but only on the switches reachable that night. The configuration has drifted from the intended state.

Definition — configuration drift. The gradual, unintended divergence of a device’s actual configuration from the intended (desired) configuration, usually caused by ad-hoc manual changes that are never propagated or documented.
Intended state source of truth SW1 SW2 SW3 matches matches drifted manual edits

Drift is dangerous precisely because it is invisible. The network still works after a change, so nothing flags the problem — until you apply the next change and it behaves differently on one device than on the other 199. The remedy is continuous reconciliation: a tool regularly reads each device’s actual configuration, compares it with the intended configuration, and reports or repairs any difference.

Drift detection · pick a moment

Part 4

Idempotency — the core idea

Traditional CLI configuration is imperative: you issue commands that describe how to change the device, and each command performs an action. If you run the same sequence twice, the second run may fail (“VLAN already exists”) or, worse, do something you did not intend.

Automation tools work differently: you describe the desired end state, and the tool figures out the commands needed to reach it.

Definition — idempotency. A property of an operation meaning that running it once or many times produces the same result. If the desired state is already present, an idempotent operation makes no further changes.
Run it twice · imperative vs declarative

Imperative CLIIdempotent / declarative
You specifyHow to change the device (commands)The state the device must be in
Re-runningMay error or duplicate workSafe; makes no change when already correct
Drift handlingNone — what is there stays thereDetected and corrected on the next run
Examplevlan 10 then name DATA“VLAN 10 named DATA must exist”
Note. Not every network operation can be idempotent. Some actions are inherently imperative or one-directional — rebooting a device, clearing counters, or reloading software. Good tooling separates the declarative desired state from the few imperative actions that cannot be expressed as state.
Part 5

CI/CD at a high level

Software teams solved a very similar problem decades ago: how to make frequent changes safely. The answer was CI/CD — continuous integration and continuous delivery. Network teams have borrowed the same pipeline, treating the network configuration as code.

Exam tip. Remember the pipeline in order: commit → test → deploy → verify. CI is about integration and testing; CD is about delivering the validated change. A question that asks where configuration is validated is pointing at the CI/test stage, not deployment.

The practical effect is that a network change becomes a reviewable pull request rather than a midnight SSH session. Peers can review it, automated tests can reject it, and if it does go wrong, reverting the commit restores the previous intended state and the next run pushes that state back out to the devices.

Part 6

The automation tool landscape

You do not need to master any tool for the CCNA, but you should know that tooling falls into three broad families. The rest of this week covers each in turn.

FamilyWhat it doesExamples later this week
ControllersCentralise management and drive devices through APIs.Cisco DNA Center / Catalyst Center, SDN controllers
Configuration-management toolsDeclaratively push and enforce device state.Ansible, Puppet, Chef
Scripts and APIsTalk to devices directly over REST or SSH.Python, REST APIs, JSON

The next lesson contrasts the traditional per-device model with a controller-based model, which is the architectural change that makes most modern automation possible. Keep the four benefits (consistency, scale, speed, fewer errors) and the two definitions (drift, idempotency) in mind: everything else in Domain 6.0 is built on them.

Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Key termMeaning
Network automationUsing software to configure, provision, verify, and operate devices with minimal human interaction.
Configuration driftUnintended divergence of a device’s actual configuration from its intended configuration.
IdempotencyRunning an operation repeatedly yields the same result as running it once.
DeclarativeDescribing the desired end state; the tool determines the commands to reach it.
ImperativeDescribing the exact steps or commands to perform; order matters and re-running may fail.
CI/CDContinuous integration (test/validate) and continuous delivery/deployment (apply) of changes.
Source of truthThe authoritative intended configuration held in version control.
Version controlA system (commonly Git) that tracks every change to configuration code.
Sources & references
  1. Cisco. CCNA (200-301) Exam Topics, Domain 6.0 Automation and Programmability. cisco.com.
  2. Cisco. Cisco DevNet: Network Automation (learning track). developer.cisco.com.
  3. Hunt, D. & others. Git documentation: About version control. git-scm.com/doc.
  4. Red Hat. What is CI/CD? redhat.com.
Sources

Sources & references

  1. Cisco. CCNA (200-301) Exam Topics, Domain 6.0 Automation and Programmability. cisco.com.
  2. Cisco. Cisco DevNet: Network Automation (learning track). developer.cisco.com.
  3. Hunt, D. & others. Git documentation: About version control. git-scm.com/doc.
  4. Red Hat. What is CI/CD? redhat.com.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.