Our Commitment to Innovation, Choice, and Openness in Next Generation Virtual Switching – Part 2

August 24, 2017 - 4 Comments

As many of you may have read on Monday in Tom Edsall’s blog post, Cisco announced our intent to put Cisco ACI into the public cloud – AWS, Microsoft Azure, and Google. This allows our customers to place policy anywhere.  And now, with ACI Virtual Edge (AVE), we will continue to fulfill our ‘ACI Anywhere’ promise.

As outlined in my blog post in May, we at Cisco are committed to innovation, choice, and openness for customers in the wake of VMware’s decision to cease support for the third party virtual switch APIs in vSphere 6.5U2 and beyond.

I’m excited to announce that we are following through on our commitment. We will soon begin Early Field Trials (EFT) of the ACI Virtual Edge (AVE), our next generation of the Application Virtual Switch (AVS) for ACI environments. We are on schedule to ship by the end of this year. The ACI Virtual Edge is hypervisor independent, offering consistent policy control across multiple hypervisors, with our initial version targeted for VMware ESXi.

Cisco understands the burden of operational change. We have designed the ACI Virtual Edge for an easy transition with minimal operational disruption. Current customers can continue to use the AVS and move to the AVE at their convenience. We will continue support for the AVS to alleviate customer concern. With this solution, customers can maintain their existing policies and operational procedures.

Stay tuned as we will continue to reveal more in the coming weeks. If you are attending VMworld, please seek out the Cisco team or prearrange a meeting through your account team. We’ll be happy to reveal more and show you a live demo.

In an effort to keep conversations fresh, Cisco Blogs closes comments after 60 days. Please visit the Cisco Blogs hub page for the latest content.


  1. Very important enhancement towards making ACI more matured SDN.

  2. It’s good we will get more advanced but still lot of changes with ACI IN ON premises ACI as very limited support for micro segmentation like container etc.

    • Hi Narottam,

      With IP Based EPG you can do micro-segmentation with containers too. Would be interested to understand your specific use case.


    • Narottam,

      you should check the release notes for ACI 3.0 (shipping). It already supports Kubernetes natively without requiring any new controller or installing proprietary virtual switches on the kubernetes nodes: it uses OVS with OpFlex. You can define granular container security using Kubernetes APIs which will be implemented via APIC and you can also consume user-defined contracts for containers.

      I really do not understand what you mean that ACI has limited support for micro segmentation 🙂 … quite the contrary.