The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The Cisco Application Policy Infrastructure Controller - Enterprise Module (APIC-EM) is Cisco's Software Defined Networking (SDN) Controller for Enterprise Networks (Access, Campus, WAN and Wireless).
The platform hosts multiple applications (SDN apps) that use open northbound REST APIs that drive core network automation solutions. The platform also supports a number of south-bound protocols that enable it to communicate with the breadth of network devices that customers already have in place, and extend SDN benefits to both greenfield and brownfield environments.
The Cisco APIC-EM platform supports both wired and wireless enterprise networks across the Campus, Branch and WAN infrastructures. It offers the following benefits:
Creates an intelligent, open, programmable network with open APIs
Saves time, resources, and costs through advanced automation
Transforms business intent policies into a dynamic network configuration
Provides a single point for network wide automation and control
The following table describes the features and benefits of the Cisco APIC-EM.
You can install Cisco APIC-EM using any one of the following methods:
Appliance Installation—As a dedicated Cisco APIC-EM physical appliance purchased from Cisco with an ISO image pre-installed. For information about this type of installation, see About the Appliance Installation.
Bare-Metal Hardware Installation—As a downloadable ISO image that you can burn to a dual-layer DVD or a bootable USB flash drive, and then use either the DVD or flash drive to install the ISO image onto a server. For information about this type of installation, see About the Bare-Metal Hardware Installation.
Note that this platform (bare-metal hardware) is recommended over the following virtual machine option
Virtual Machine Installation—As a downloadable ISO image that you can install into a virtual machine within a VMware vSphere environment. For information about this type of installation, see About the Virtual Machine Installation.
The following are the primary components required for a Cisco APIC-EM installation:
The Cisco Cisco APIC-EM software either pre-installed on a Cisco appliance or provided as an ISO image downloaded from the Cisco website.
Supported Cisco routing and switching platforms
Ubuntu 14.04 LTS 64-bit
Open-VM-Tools
Cisco APIC-EM services
Grapevine Elastic Services Platform, consisting of a Grapevine root and client template
Note | Open-VM-Tools is only installed if the ISO image is installed within a virtual machine running on vSphere. The tools will not be installed if the ISO image is installed on a bare-metal or on a hypervisor from another vendor. |
The Cisco APIC-EM makes use of the Ubuntu operating system environment and Linux containers (LXC). The Grapevine root runs within the host's operating system. The Grapevine clients run in LXCs within the host. The Cisco APIC-EM services that run on the Grapevine Elastic Services Platform provide the controller with its core functionality. For information about the services, see Cisco Application Policy Infrastructure Controller Enterprise Module Administrator Guide.
The Cisco APIC-EM communicates with its supported platforms using the following protocols:
Note | Currently, the Cisco APIC-EM supports IPv4 only. IPv6 support is planned for a future release. |
For information about the supported Cisco platforms and software releases, see the following documentation:
The Cisco APIC-EM provides northbound REST APIs that you can use to that you can use to issue requests to the controller and exchange data with the controller in a platform-agnostic way. For detailed information about supported northbound REST APIs, see the internal, interactive documentation located within the GUI itself. Click the API button at the top right of the GUI to view this documentation.