The problem with the CLI
Everything so far was typed into one device at a time. That's fine for a lab, but a real network has hundreds of devices. Configuring each by hand is slow, and above all inconsistent: a typo on one switch, a forgotten line on another, and you have an outage that's hard to find. Automation makes change fast, consistent and repeatable, and it records exactly what was done.
The control plane and the data plane
Every network device does two jobs:
| Plane | Job | Examples |
|---|---|---|
| Control plane | Decides where traffic should go (builds the tables) | OSPF, STP, ARP, building the routing and MAC tables |
| Data plane | Forwards the actual packets, as fast as possible, using those tables | Switching a frame out a port, routing a packet to a next hop |
On a traditional router or switch, both planes live in the same box. Software-defined networking (SDN) pulls the control plane out into a central controller: the controller decides, and the devices just forward. One place to see and change the whole network.
| Traditional | Controller-based (SDN) | |
|---|---|---|
| Control plane | In each device | Centralised in a controller |
| Configuration | Box by box, CLI | Once, on the controller, pushed everywhere |
| View of the network | Per device | Whole network at once |
| Change | Manual, error-prone | Programmatic, consistent |
Remember: Control plane = decides (routing/STP/ARP). Data plane = forwards packets. SDN centralises the control plane in a controller.