Tags: #◇Computer Science #◇NSCOM02 #◇Conceptual #◇SDN
◇Overview
Software-Defined Networking (SDN) is a modern network architecture that separates the network control plane (how routing decisions are made) from the data plane (how packets are forwarded). By decoupling these layers, SDN provides centralized, programmable, and dynamic control of network behavior, bypassing the rigid limitations of traditional, distributed routing protocols.
◇Key Definitions
- Control Plane: The "brains" of the network, responsible for calculating paths and building routing tables.
- Data Plane (Forwarding Plane): The "muscle," responsible for actually moving packets from input ports to output ports.
- SDN Controller: The centralized software application that dictates the control plane logic for the entire network.
- Southbound API: Interfaces that bridge the SDN controller and the forwarding devices (e.g., OpenFlow).
- Northbound API: Interfaces that bridge the SDN controller and the overlying software applications/network administrators.
◇Theoretical Framework / Core Concepts
The Separation of Planes
In traditional networking, every router runs its own control plane (OSPF, BGP) and data plane. SDN extracts the control plane and centralizes it in the SDN Controller.
The individual switches become "dumb" forwarding devices.
OpenFlow Architecture
OpenFlow is the most prominent Southbound API protocol. Instead of traditional routing tables, OpenFlow uses Flow Tables.
Flow table entries consist primarily of two parts:
- Match Fields: Criteria like Source IP, Destination MAC, VLAN ID, or TCP Port used to identify a packet.
- Actions: What to do with the matched packet (e.g., forward out port 2, drop, modify header).
◇Worked Examples / Protocol Walkthroughs / Calculations
OpenFlow Packet Processing
When a packet arrives at an SDN switch:
- The switch checks its flow tables.
- If the packet header matches an existing rule (Match Field), the switch executes the associated Action (e.g., forward out Port 3).
- If there is no match (table miss), the switch typically encapsulates the packet and sends it to the SDN Controller via the Southbound API to ask for instructions.
◇Summary & Key Takeaways
- SDN cleanly abstracts the network control plane from the data plane.
- Centralized control allows network-wide programmability and automation.
- Southbound APIs (like OpenFlow) communicate with switches.
- Northbound APIs allow software apps to define network logic.
- Flow tables dictate forwarding based on Match Fields and Actions.
◇References & Navigation
- Previous Topic: ◇BGP and Interdomain Routing
- Next Topic: ◇Network Management, ICMP, and SNMP
- Related Notes: ◇Network Layer, ◇BGP and Interdomain Routing
ACTIVE RECALL VERIFICATION
Select an answer to verify conceptual comprehension and reveal the technical rationale.
In a Software-Defined Network (SDN), what function is completely removed from the individual switches?
What is the primary role of the Data Plane in a network device?
Which protocol serves as the standard Southbound API between an SDN controller and the forwarding switches?
What interface does a network administrator or software application use to program network logic into the centralized SDN controller?
In an OpenFlow switch, what two primary components make up a flow table entry?
What is a primary advantage of utilizing SDN in a modern enterprise network?
Which plane is responsible for actually modifying packet headers if instructed?
What happens in an OpenFlow switch if a packet doesn't match any existing flow entries?
In the SDN paradigm, traditional routing protocols (like OSPF or BGP) are typically:
What connects the Application Plane to the Control Plane in SDN?