Automation & Programmability // Lesson 02

Traditional vs Controller-Based.

Compare distributed device-by-device networking with controller-based policy, abstraction and centralised management.

Distributed controlControllerIntentSouthboundScale
01 // Mental model

Start with the big picture.

Devices run distributed control protocols and are often configured individually through their own management interfaces.

CCNA focus: Controller-based does not mean the controller forwards every user packet. Keep management, control and data-plane responsibilities distinct.
02 // Building blocks

Know what each part does.

01

Traditional

Devices run distributed control protocols and are often configured individually through their own management interfaces.

02

Controller-based

A controller presents a central policy and automation point while infrastructure still forwards traffic.

03

Abstraction

Operators express intent through a model rather than reproducing low-level commands on every device.

04

Not magic

Controller availability, scale, security, underlay reachability and device support still require sound design.

03 // Compare and recognise

Read the clues.

ItemWhat to remember
Management planeInterfaces used to configure, monitor and operate the system.
Control planeBuilds forwarding knowledge and makes path decisions.
Data planeForwards packets using programmed tables.
Controller clusterProvides scale and resilience for central services.
04 // Change comparison

Change comparison.

Traditional:
  log in to device A -> configure -> verify
  log in to device B -> configure -> verify

Controller-based:
  define policy once -> controller validates intent
  -> controller programs supported devices
  -> assurance checks observed state

Read the example from top to bottom, then verify the resulting state. Configuration is only complete when the output matches the intended design.

05 // Exam and troubleshooting

Turn facts into a method.

  • Interfaces used to configure, monitor and operate the system.
  • Builds forwarding knowledge and makes path decisions.
  • Forwards packets using programmed tables.
  • Provides scale and resilience for central services.
Exam checkpoint: Controller-based does not mean the controller forwards every user packet. Keep management, control and data-plane responsibilities distinct.
06 // Check yourself

Traditional vs Controller-Based quiz.

1. Which plane forwards user packets?

2. What advantage does a controller provide?

3. Do controller-based networks eliminate distributed protocols entirely?

4. What does intent describe?

5. What should a controller cluster provide?

Score: 0 / 5