The Cisco AVS is a customized Cisco Nexus 1000V switch that is integrated with the Cisco Application Centric Infrastructure (ACI) and managed by the Application Policy Infrastructure Controller (APIC). Cisco AVS implements the OpFlex protocol for control plane communication.
The Cisco AVS supports two modes of traffic forwarding: local switching (LS) mode and Cisco FEX mode. The forwarding mode is selected during Cisco AVS installation.
The Cisco AVS is supported as a vLeaf for the Cisco APIC with the VMware ESXi hypervisor. It manages a data center defined by the vCenter Server.
The Cisco AVS is compatible with any upstream physical access layer switch that complies with the Ethernet standard, including Cisco Nexus switches. The Cisco AVS is compatible with any server hardware listed in the VMware Hardware Compatibility List (HCL).
Cisco AVS Software Compatibility
The Cisco AVS is supported in Release 4.2(1)SV2(2.3) and later releases.
The Cisco AVS Release 4.2(1)SV2(2.3) is supported as a vLeaf for the Cisco APIC with releases 5.1 and 5.5 of the VMware ESXi hypervisor.
The Cisco AVS supported in Release 4.2(1)SV2(2.3) is compatible with the Cisco Application Policy Infrastructure Controller (APIC) Release 1.0(1e), 1.0(1h), 1.0(1k), and 1.0(1n).
Cisco AVS Software Restrictions
Choosing Encapsulation Type and Switching Mode
The encapsulation type (VXLAN versus VLAN) and the switching mode (FEX Enable, also known as No Local Switching mode, versus FEX Disable, also known as Local Switching mode) must be selected at the time of VMM Domain creation. Changing these selections after the VMM Domain is created is not supported. If you want to change the encapsulation or the switching mode, you must destroy the VMM domain and the corresponding DVS from the VMware VCenter and then recreate the VMM domain with the desired selection.
Configuring SPAN or ERSPAN with a UCS B Series Server
If you want to configure Switched Port Analyzer (SPAN) or encapsulated remote SPAN (ERSPAN) on Cisco AVS, and the Cisco AVS hosts are running on a UCS B Series server, you must configure a port channel (PC) interface policy group with MAC pinning for the interfaces connecting to the fabric interconnects. This is because the virtual source (vsource) and virtual destination (vdestination) groups are specified only on PC policy groups.
No Direct Upgrade to Release 5.2(1)SV3(1.5)
You cannot upgrade Cisco AVS Release 4.2(1)SV2(2.3) directly to Release 5.2(1)SV3(1.5). If you want to upgrade to Release 5.2(1)SV3(1.5) you must upgrade Cisco AVS to Release 5.2(1)SV3(1.3) or Release 5.2(1)SV3(1.3b) and then upgrade Cisco AVS to Release 5.2(1)SV3(1.5).
Related Documentation for Cisco AVS
This section lists the documents used with the Cisco AVS and available at the following URL:
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.