Software Defined Networking (SDN)

The landscape of network management is changing quickly, driven by Software-Defined Networking (SDN). For CCNA-level networking, you’ll want a clear picture of what SDN changes (and what it doesn’t). The key ideas are:

• How traditional device-by-device networks differ from controller-based networks
• How SDN designs use underlay, overlay, and fabric
• Why separating the control plane from the data plane matters

Traditional networks versus controller-based networking

SDN makes the most sense when you compare it to how networks have traditionally been built and operated.

Traditional networks

In a conventional network, each device - Router, Switch, Firewall - operates largely on its own. The logic that decides where traffic should go (the Control Plane) lives on the same device as the hardware that forwards packets (the Data Plane). In practice, that means every network device independently calculates routes, builds forwarding tables, and processes network protocols.

Image

Image Title - Network devices operating autonomously in a traditional network architecture

Managing a traditional network usually means configuring devices one at a time, often through a Command-Line Interface (CLI). This distributed model works, but it becomes harder to operate as networks grow and change more frequently:

• Scaling can be slow because changes often require manual updates across many devices.
• The risk of configuration mistakes increases as the number of touch points increases.
• Keeping policies consistent across a large network can be difficult.

Controller-based networking

Controller-based networking (the architectural model behind SDN) takes a different approach. Instead of each device acting as its own “brain,” the network uses a centralized control mechanism, typically an SDN controller (for example, Cisco’s Catalyst Center). The controller maintains a network-wide view and provides a central place to define intent and policy.

Rather than configuring each device individually, administrators interact with the controller. The controller then translates higher-level policies into device-specific instructions.

Image

Image Title - Controller-based networking architecture

This centralized approach leads to several practical advantages:

• Simplified management: A single point of control streamlines monitoring, configuration, and troubleshooting.
• Enhanced automation and programmability: Policies can be defined once and applied programmatically across the infrastructure.
• Greater agility and scalability: The network can adapt and scale with fewer manual, device-by-device changes.
• Improved consistency: Policies are enforced uniformly, which makes network behavior more predictable.

Controller-based, software-defined architecture: overlay, underlay, and fabric

Cisco SDN solutions such as Software-Defined Access (SDA) and Software-Defined WAN (SD-WAN) are often described using three related terms: underlay, overlay, and fabric. These terms help you separate:

• The physical network that provides basic connectivity

• The virtual network services built on top of it

• The combined system managed by the controller

• Underlay Network: The underlay is the physical network infrastructure: Switches, Routers, and cabling. Its job is to provide reliable, high-performance IP connectivity between devices, typically using standard routing protocols (for example, OSPF) to ensure reachability. A useful mental model is a road system that carries all traffic.

• Overlay Network: The overlay runs logically on top of the underlay. It’s a virtualized network layer that uses encapsulation technologies such as Virtual Extensible LAN (VXLAN) to build virtual tunnels between devices. Those tunnels let you create segmented logical networks that don’t depend on the physical topology. The overlay is where features like micro-segmentation, policy enforcement, and virtual network functions are implemented.

  Image

  Image Title - Underlay and overlay network

• Fabric: The fabric is the complete SDN system: underlay + overlay, coordinated by the SDN controller. It’s the integrated network that delivers connectivity and services while enabling automated, policy-driven operations.

Separation of control plane and data plane

The core architectural idea behind SDN is separating the Control Plane from the Data Plane. This decoupling is what makes centralized management, programmability, and automation possible.

• Control Plane: The Control Plane provides the network’s “intelligence.” It decides how traffic should be handled and where it should go. In traditional networks, each device runs its own control-plane functions - for example, routing protocols, routing table construction, forwarding path decisions, and control messages such as OSPF Hellos and Spanning-Tree BPDUs. In SDN, much of this decision-making is centralized in the controller. The controller collects network-wide information, computes paths, and defines traffic policies.

• Data Plane: Also called the Forwarding Plane, the Data Plane forwards packets based on the Control Plane’s decisions. This includes packet switching (moving packets from an incoming port to the correct outgoing port), frame manipulation (Layer 2 Rewrite discussed in Chapter 3.3 Routers and IPv4 routing fundamentals), and applying Quality of Service (QoS). In SDN, physical devices (Switches and Routers) primarily keep this data-plane role, acting as high-speed forwarding elements that follow instructions from the controller.

With this separation, devices don’t need to independently run as much control-plane logic to make forwarding decisions. Instead, they can focus on fast, consistent forwarding based on controller-provided intent. This design leads to several benefits:

• Centralized intelligence: The controller has a real-time, network-wide view, which supports more coordinated traffic management.
• Enhanced programmability: You can adjust network behavior through software-driven policies.
• Reduced device complexity: Devices can focus on forwarding rather than complex distributed decision-making.
• Faster innovation cycles: Control-plane features can evolve through software updates without requiring hardware changes.

In practical terms, the controller decides how traffic should flow, and the devices carry out that forwarding. This separation is a cornerstone of modern network design because it supports the flexibility, automation, and scalability expected in today’s networks.