Cisco AVS is a hypervisor-resident distributed virtual switch that is specifically designed for Cisco Application Centric Infrastructure (ACI) and managed by the Application Policy Infrastructure Controller (APIC). Cisco AVS implements the OpFlex protocol for control plane communication.
Cisco AVS supports two modes of traffic forwarding: local switching and no local switching. The forwarding mode is selected during Cisco AVS installation.
Cisco AVS is supported as a vLeaf for Cisco APIC with the VMware ESXi hypervisor. It manages a data center defined by the vCenter Server.
Cisco AVS is compatible with any upstream physical access layer switch that complies with the Ethernet standard, including Cisco Nexus switches. Cisco AVS is compatible with any server hardware listed in the VMware Hardware Compatibility List.
Cisco AVS Software Compatibility
Cisco AVS Release 5.2(1)SV3(1.10) is supported as a vLeaf for Cisco APIC with releases 5.1, 5.5, and 6.0 of the VMware ESXi hypervisor.
Note When you choose a Cisco AVS VIB, you need to choose the one compatible with the version of VMware ESXi hypervisor that you use. ESXi 5.1 uses xxxx.3.1.1.vib, ESXi 5.5 uses xxxx.3.2.1.vib, and ESXi 6.0 uses xxxx.6.0.1.vib.
The following table lists the compatibility of Cisco AVS with Cisco APIC.
Support for vCenter 6.0 is a new feature in Cisco AVS Release 5.2(1)SV3(1.10). Procedures for choosing the version of vCenter remain largely unchanged; vCenter 6.0 is among the versions that you can choose in the GUI. VMM domains are now created under the Inventory tab in the GUI; previously VMM domains were created under the Policies tab.
For information about choosing vCenter 6.0, see the Cisco AVS chapter of the Cisco ACI Virtualization Guide and the Cisco Application Virtual Switch Installation Guide.
Layer 4 to Layer 7 Service Graphs
Beginning with Cisco AVS Release 5.2(1)SV3(1.10), Layer 4 to Layer 7 service graphs are supported for Cisco AVS. Layer 4 to Layer 7 service graphs for Cisco AVS can be configured for virtual VMs only and with VLAN encapsulation only.
For information about Layer 4 to Layer 7 service graphs, see the Cisco APIC Layer 4 to Layer 7 Services Deployment Guide. When you follow the instructions in the guide, configure services for Cisco AVS instead of VMware Distributed Virtual Switch (DVS).
Support for IPv6 as well as IPv4 is a new feature in Cisco AVS Release 5.2(1)SV3(1.10). Procedures for configuring an IP address remain unchanged.
For information about configuring IP addresses, see the Cisco AVS chapter of the Cisco ACI Virtualization Guide.
Distributed Firewall Logging
Distributed Firewall logging is a new feature in Cisco AVS Release 5.2(1)SV3(1.10). Cisco AVS reports the flows that are denied by Distributed Firewall to the system log (syslog) server. You can configure parameters for the flows and then view detailed information about the flows to further security.
For information about Distributed Firewall logging, see the Cisco ACI Virtualization Guide.
Collection of Debug Log Files
Beginning with Cisco AVS Release 5.2(1)SV3(1.10), Cisco APIC supports the collection of debug log files on Cisco AVS and the export of those files to a remote server. The files are placed into a single compressed.tar file, which is copied to the remote server using the Secure Copy Protocol (SCP).
For information about collection of debug log files, see the Cisco AVS Troubleshooting Guide.
Static VMM Encapsulation Mode
Static virtual machine monitor (VMM) encapsulation mode enables you to statically allocate the VLAN encapsulation for a VMM domain endpoint group (EPG). Using a static VLAN pool or a static VLAN block within an already existing pool is required for the VLANs defined in this feature.
For information about allocating static VLAN encapsulation, see the Cisco ACI Virtualization Guide.
Tested Layer 4 to Layer 7 Service Deployments
The following Cisco Adaptive Security Virtual Appliance (ASAv) firewall and F5 load balancer services have been qualified with Cisco AVS using adjacency type as the L2 mode for all deployments:
ASAv Firewall as transparent mode
ASAv Firewall as routed mode
F5 Load Balancer as 1-arm mode
F5 Load Balancer as 2-arm mode
1-node and 2-node deployments
Standalone and HA modes
Limitations and Restrictions
VMotion Between Data Centers and Across vCenters not Supported in vCenter 6.0
VMotion migration between data centers and across vCenters is not supported for Cisco AVS in vCenter 6.0.
VXLAN Load Balancing and Microsegmentation with Cisco AVS not Supported on the Same vCenter Domain
If VXLAN load balancing is enabled in the VMware vCenter domain profile, Microsegmentation with Cisco AVS cannot be enabled on the domain. However, enabling Microsegmentation with Cisco AVS in such cases will be supported when Cisco AVS Release 5.2(1)SV3(1.10) is released.
Pre-provisioning not Supported for EPG Resolution Immediacy
When you set EPG resolution immediacy, Cisco AVS does not support pre-provisioning, which downloads a policy to a switch before the switch is installed.
Using the Bug Search Tool
Use the Bug Search tool to search for a specific bug or to search for all bugs in a release.
Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.