Scribd
Upload
35 views3 pages

Devnet-Python-Apic-Em: SDN Architecture With Centralized Control Plane

Uploaded by

Ihor Zinchenko

This document discusses SDN and the Cisco APIC-EM controller. It explains that the APIC-EM takes a different SDN approach than traditional SDN by keeping the control plane on each network device rather than centralizing it. This allows the network to remain distributed and scalable while still providing centralized management. The APIC-EM abstracts the physical network and provides applications with easy access to network services through its northbound REST API. It can automate network configuration based on business policies and provides inventory, topology discovery, and applications for common network tasks.

Copyright:

© All Rights Reserved
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt

Devnet-Python-Apic-Em: SDN Architecture With Centralized Control Plane

Uploaded by

Ihor Zinchenko
35 views3 pages
This document discusses SDN and the Cisco APIC-EM controller. It explains that the APIC-EM takes a different SDN approach than traditional SDN by keeping the control plane on each network device rather than centralizing it. This allows the network to remain distributed and scalable while still providing centralized management. The APIC-EM abstracts the physical network and provides applications with easy access to network services through its northbound REST API. It can automate network configuration based on business policies and provides inventory, topology discovery, and applications for common network tasks.

Original Title

Less 5

Copyright

© © All Rights Reserved

Available Formats

DOCX, PDF, TXT or read online from Scribd

Did you find this document useful?

Is this content inappropriate?

This document discusses SDN and the Cisco APIC-EM controller. It explains that the APIC-EM takes a different SDN approach than traditional SDN by keeping the control plane on each network device rather than centralizing it. This allows the network to remain distributed and scalable while still providing centralized management. The APIC-EM abstracts the physical network and provides applications with easy access to network services through its northbound REST API. It can automate network configuration based on business policies and provides inventory, topology discovery, and applications for common network tasks.

Copyright:

© All Rights Reserved
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt
35 views3 pages

Devnet-Python-Apic-Em: SDN Architecture With Centralized Control Plane

Uploaded by

Ihor Zinchenko
This document discusses SDN and the Cisco APIC-EM controller. It explains that the APIC-EM takes a different SDN approach than traditional SDN by keeping the control plane on each network device rather than centralizing it. This allows the network to remain distributed and scalable while still providing centralized management. The APIC-EM abstracts the physical network and provides applications with easy access to network services through its northbound REST API. It can automate network configuration based on business policies and provides inventory, topology discovery, and applications for common network tasks.

Copyright:

© All Rights Reserved
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt
You are on page 1/ 3

DevNet-Python-APIC-EM

1. With the networking devices that we are familiar with, you may tend to think of a router
or switch as a single device. However, the major functions of these devices can be
divided into two planes:
● Control plane - Makes forwarding decisions. The control plane contains Layer 2
and Layer 3 route forwarding mechanisms. Information sent to the control plane is
processed by the CPU.
● Data plane - Also called the forwarding plane, this plane is used to forward traffic
flows. Routers and switches use information from the control plane to forward
incoming traffic out the appropriate egress interface.
By separating the control plane and data plane, network programmers can centralize
information that devices use to make forwarding decisions and perform other functions.
2. Traditional Architecture

In Software-Defined Networking (SDN), the control plane is centralized in an SDN


controller, as shown in Figure 2. The SDN controller is a logical entity that enables
network administrators to manage and dictate how the data plane of routers and
switches should handle network traffic. SDN uses the OpenFlow protocol to
communicate between the controller and network devices.
SDN Architecture with Centralized Control Plane

3. A different SDN approach is represented by the Cisco APIC or APIC-EM SDN


controllers. These controllers create abstraction from the physical network fabric at the
bottom to applications at the top.

In this case, the control plane does not need to be decoupled from the data plane. The control
plane still resides in every device, which provides local distributed intelligence where it is
needed. This approach removes the potential for the controller to become the bottleneck of the
network. Existing network devices such as routers and switches continue to be used to build
scalable and high performance distributed networks.
In the past, network staff have had to spend a lot of time on the infrastructure at the bottom of
the diagram -- the switches and the routers -- connecting them together to build a network
architecture. Where people really need to be spending their time -- what digital business
thrives on -- is this application layer at the top of the diagram.
DevNet-Python-APIC-EM

The SDN controller in this case is very important, because it reconciles the two organizational
needs. It presents the application layer with abstractions of the network that is underneath.
Because of this, applications can very easily consume network services. This is critical
because the digital enterprise is entirely application driven. These software applications control
orchestration, automation, collaboration, policy, and security so that network staff can work
with the abstract and easy to use representation of the network fabric.
4. Cisco APIC-EM SDN controller communicates with the physical topology using standard
Southbound API protocols such as SNMP, SSH and Telnet rather than a protocol like
OpenFlow. This makes an easy to use abstraction of the network fabric available to
applications using a standard REST API interface.
These applications can run from big “all in one” orchestration tools to simple scripts that
use a single API call to answer a question such as, “How many computers are
connected to our network?” Imagine answering that question with a CCENT level
knowledge from your computer by SSHing to every router and switch and entering
commands at the CLI like “show ip route”, “show ip arp”, and “show mac address-table."
Then imagine trying to make some sense of all that output to create a meaningful
answer to the simple question.

5. The Cisco Application Policy Infrastructure Controller Enterprise Module (APIC-EM) is


an SDN controller that has the following characteristics:
● Enterprise network SDN controller
● Can be either a virtual software only appliance or a physical appliance
● Creates an intelligent, open, programmable network with open APIs
● Can transform business-intent policies into dynamic network configuration
● Provides a single point for network-wide automation and control

Important places on the home page include:


● Services - The APIC-EM discovers the devices on the network and places them in
host and device inventory tables where details for each device can be viewed. The
APIC-EM also creates a topology.
● Applications - APIC-EM applications allow configuration of the network and testing
of network connectivity. Applications include:
DevNet-Python-APIC-EM

○ IWAN - Simplifies WAN deployments by providing an intuitive, policy-


based interface that helps IT abstract network complexity and design for
business intent.
○ Path Trace - Greatly eases and accelerates the task of connection
monitoring and troubleshooting.
○ Network Plug and Play - Provides a unified approach to provision
enterprise networks comprised of Cisco routers, switches, and wireless
access points with a near-zero-touch deployment experience.
○ Easy QoS - Provides a simple way to classify and assign application
priority.
● API documentation - A link where you can access information about the API that is
essential to network programmers.

You might also like