Scribd
Upload
13 views19 pages

Introduction to Controller-Based Networking

Chapter 16 of CCNA 200-301 discusses controller-based networking, focusing on the roles of network components, characteristics of network topologies like spine-leaf, and the impact of automation on network management. It contrasts traditional networks with controller-based architectures, detailing the separation of control and data planes, and introduces various APIs. The chapter also compares OpenFlow, ACI, and APIC Enterprise in terms of control plane centralization and management capabilities.

Uploaded by

gaurav
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
13 views19 pages

Introduction to Controller-Based Networking

Chapter 16 of CCNA 200-301 discusses controller-based networking, focusing on the roles of network components, characteristics of network topologies like spine-leaf, and the impact of automation on network management. It contrasts traditional networks with controller-based architectures, detailing the separation of control and data planes, and introduces various APIs. The chapter also compares OpenFlow, ACI, and APIC Enterprise in terms of control plane centralization and management capabilities.

Uploaded by

gaurav
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

CCNA 200-301, Volume 2

Chapter 16
Introduction to Controller-Based
Networking
Objectives
• Explain the role and function of network components
▫ Endpoints
▫ Servers
• Describe characteristics of network topology architectures
▫ Spine-leaf
• Explain how automation impacts network management
• Compare traditional networks with controller-based
networking
• Describe controller-based and software defined architectures
(overlay, underlay, and fabric)
▫ Separation of control plane and data plane
▫ Northbound and southbound APIs
Data Plane Processing on Routers:
Basics
Control and Data Planes of Routers—
Conceptual
Management Plane for Configuration
of Control and Data Plane
Key Internal Processing Points in a
Typical Switch
Centralized Control Plane and a
Distributed Data Plane
Java API: Java Application
Communicates with Controller
Process Example of a GET Using a REST
API
Architecture of NBI, Controller
Internals, and SBI to Network Devices
Spine-Leaf Network Design
Endpoints Found on the Leaf Switches
Only
Endpoint Groups (EPGs) and Policies
Architectural View of ACI with APIC
Pushing Intent to Switch Control Plane
Controlling the ACI Data Center
Network Using the APIC
APIC-EM Controller Model
Points of Comparison: OpenFlow, ACI,
and APIC Enterprise
Criteria OpenFlow ACI APIC
Enterprise
Changes how the device control plane works Yes Yes No
versus traditional networking
Creates centralized point from which humans Yes Yes Yes
and automation control the network
Degree to which the architecture centralizes Mostly Partially None
the control plane
SBIs used OpenFlow OpFlex CLI/SNMP
Controllers mentioned in this chapter OpenDaylight APIC APIC-EM

Organization that is the primary ONF Cisco Cisco


definer/owner
Small Output from a Switch Command
Python Dictionary with Variables Set to
Needed Values

You might also like