Featured Blog Post: Application Policy Language Differentiates Cisco ACI from Typical SDN

As IT departments look to software-defined networking (SDN) to reduce operating costs and increase business agility, the strengths and drawbacks of different SDN architectures stops becoming an academic debate and starts becoming an actual business decision.

Cisco believes the success of an IT or cloud automation solution depends on the business policies that can be carried out by the infrastructure through the SDN architecture. In a recent post, Cisco Senior Solution Marketing Manager Gary Kinghorn talked about how the company’s Application Centric Infrastructure (ACI) supports a business-relevant application policy language that provides greater scalability and network visibility than systems based on typical SDN architectures.

Kinghorn’s blog is the first of a four-part series that will compare the critical architectural components of Cisco ACI and typical SDN. Rather than centralize network control functions on the SDN Controller as most SDN architectures do, ACI is based on a declarative model that uses the OpFlex southbound API to communicate policies between the controller and various network devices.

Cisco’s approach to SDN is so different that some have debated whether it’s actually SDN at all, but Kinghorn says SDN and Cisco ACI share essentially the same IT automation objectives, we well as some fundamental baseline architectural features:

Kinghorn compares the capabilities allowed in the Cisco ACI policy model to those of existing virtual overlay solutions. Future installments in the series will compare critical protocols and components in Cisco ACI with VMware NSX to contrast Cisco ACI against software overlay networks.