Saturday, November 29, 2025

Software-Defined Networking (SDN)

 In Software-Defined Networking (SDN), the controller is responsible for coordinating the Virtual Tenant Networks (VTNs). Multi-tenancy is one of the advantageous features provided by SDN when compared to traditional networks. With multi-tenancy, multiple entities can run their services and applications separately and independently while consuming the same network infrastructure resources.

The network devices stream telemetry data to the controller. This telemetry data is analyzed by the controller or third-party application so that anomalies can be detected and so that security threats can be proactively avoided.

The northbound application programmable interface (API) is responsible for providing extensibility. The northbound API enables third-party applications to connect to the SDN controller. These applications are usually used for orchestration.

The southbound API is used by the controller to manage the network devices.


If you want, I can turn this into a CCNA-ready SDN summary sheet, or quiz you on these mappings.

You said:
a CCNA-ready SDN summary sheet
ChatGPT said:

Here you go, Lou — a clean, exam-ready SDN Summary Sheet, written exactly in the style Wendell Odom expects you to know for CCNA 200-301 v1.1.

No fluff. No CCNP detail. Pure CCNA-level mastery.


CCNA SDN Summary Sheet

(Software-Defined Networking – Exam-Level Essentials)


1. SDN Architectural Layers (3-Tier Model)

A. Application Layer

  • Contains orchestration tools, analytics platforms, automation tools, security applications.

  • Communicates downward to the controller via northbound APIs.

  • Purpose: Define intent, push policies, request services.

B. Control Layer (Controller)

  • The central brain of SDN.

  • Maintains global network view (topology, policies, paths).

  • Makes forwarding decisions (“intent → configuration”).

  • Coordinates Virtual Tenant Networks (VTNs).

  • Communicates:

    • Upward via northbound API

    • Downward via southbound API

C. Infrastructure Layer (Data Plane)

  • Physical or virtual network devices: switches, routers, APs, firewalls.

  • Forward traffic (data plane).

  • Stream telemetry to the controller.

  • Enforce configuration received from the controller.


2. SDN APIs — Know These Cold

Northbound API

  • Controller → Applications (orchestration layer).

  • Purpose: Extensibility.

  • Common form: REST API, JSON/HTTPS.

  • Enables apps to:

    • Read topology

    • Push security policies

    • Create automation workflows

    • Integrate 3rd-party platforms

Southbound API

  • Controller → Network devices.

  • Purpose: Deliver configuration + gather operational data.

  • Examples:

    • OpenFlow (CCNA favorite term)

    • NETCONF/YANG

    • gNMI / gRPC (telemetry)


3. SDN Benefits (CCNA-Level Talking Points)

  • Centralized control plane
    Controller holds full network intelligence.

  • Automation and programmability
    Intent → configuration without touching each device.

  • Consistent policy enforcement
    One central source of truth.

  • Multi-tenancy
    VTNs allow separate logical networks over shared hardware.

  • Real-time telemetry
    Devices stream data for:

    • Security analysis

    • Troubleshooting

    • Predictive maintenance


4. Key CCNA Exam Definitions

TermCCNA Definition
SDNDecoupling control plane from data plane; controlled by a central controller
ControllerSoftware platform with global view; coordinates VTNs; programs devices
Northbound APIInterface enabling applications to communicate with controller; provides extensibility
Southbound APIInterface enabling controller to send config to devices; manages network elements
TelemetryReal-time data streamed from devices to controller
VTN (Virtual Tenant Network)Logical network segmentation for multi-tenancy
OpenFlowSouthbound protocol used to program forwarding tables
ProgrammabilityAbility to automate management via APIs

5. CCNA Exam Traps to Watch For

1. “Which API provides extensibility?”

Northbound API

2. “Which component streams telemetry?”

Network devices

3. “Which component orchestrates VTNs?”

Controller

4. “Which component actually forwards packets?”

Infrastructure layer (network devices)

5. “Which protocol is associated with SDN southbound APIs?”

OpenFlow (CCNA’s favorite)

6. “Is SDN about data-plane centralization?”

❌ No.
Control plane gets centralized.
✔ Data plane remains distributed.


6. Memorization Mini-Chart (High-Speed Recall)

SDN Flow of Intent

App → (Northbound API) → Controller → (Southbound API) → Devices → Traffic Forwarding


7. One-Sentence Summary for Exam Memory

“Apps talk down to the controller via northbound APIs, the controller programs devices via southbound APIs, and devices forward packets while streaming telemetry back.”

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.

LWAPP (Lightweight Access Point Protocol)

  LWAPP was Cisco’s original tunneling + control protocol used between lightweight APs and a Wireless LAN Controller (WLC) before CAPWAP bec...