Cisco Application Virtual Switch Release Notes, Release 5.2(1)SV3(4.1)

 

This document describes the features, bugs, and limitations for the Cisco Application Virtual Switch (AVS) software.

Note: Use this document in combination with the Cisco Application Policy Infrastructure Controller (APIC) Release Notes, which you can view at the following location:

http://www.cisco.com/c/en/us/support/cloud-systems-management/application-policy-infrastructure-controller-apic/tsd-products-support-series-home.html

Release notes are sometimes updated with new information about restrictions and caveats. See the following website for the most recent version of this document:

 http://www.cisco.com/c/en/us/support/switches/application-virtual-switch/products-release-notes-list.html

Table 1 shows the online change history for this document.

Table 1 Online History Change

 

 

Contents

This document includes the following sections:

Introduction: Cisco AVS

Cisco AVS Software Compatibility

New and Changed Information

Limitations and Restrictions

Bugs (Caveats)

Documentation

 

Introduction: Cisco AVS

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 Guide.

Cisco AVS Software Compatibility

Cisco AVS Release 5.2(1)SV3(4.1) is supported as a vLeaf for Cisco APIC with releases 5.5, 6.0, and 6.5 of the VMware ESXi hypervisor.

Note: When you choose a Cisco AVS VIB, you must choose the one compatible with the version of VMware ESXi hypervisor that you use. ESXi 5.5 uses xxxx.3.2.1.vib, ESXi 6.0 uses xxxx.6.0.1.vib, and ESXi 6.5 uses xxxx.6.5.1.vib.

Cisco APIC Compatibility and Upgrade/Downgrade Information

Cisco AVS 5.2(1)SV3(4.1) is compatible with Cisco APIC 4.0(1h) and later versions.

See the Cisco APIC and AVS Support Matrix for details about Cisco APIC and Cisco AVS compatibility, including compatible versions for upgrades and downgrades.

For compatibility and other information about Cisco AVS releases earlier than 5.2(1)SV3(2.1), see the Cisco AVS Release Notes on Cisco.com for the specific release.

Virtualization Compatibility Information

The Cisco ACI Virtualization Compatibility Matrix for interoperability information for Cisco ACI components and configurations that have been tested and validated by Cisco, by Cisco partners, or both. 

New and Changed Information

Cisco AVS Release 5.2(1)SV3(4.1) supports all of the features that were introduced in 5.2(1)SV3(1.10), 5.2(1)SV3(1.10a), 5.2(1)SV3(1.15), 5.2(1)SV3(1.16), 5.2(1)SV3(1.16a), 5.2(1)SV3(1.16b), 5.2(1)SV3(1.20), 5.2(1)SV3(1.20a), 5.2(1)SV3(1.25), 5.2(1)SV3(2.1), 2(1)SV3(2.1a), 5.2(1)SV3(2.2), 5.2(1)SV3(2.5), 5.2(1)SV3(2.14), 5.2(1)SV3(3.2), 5.2(1)SV3(3.5), 5.2(1)SV3(3.8), 5.2(1)SV3(3.10), 5.2(1)SV3(3.20), 5.2(1)SV3(3.21), 5.2(1)SV3(3.25), 5.2(1)SV3(3.27), and 5.2(1)SV3(3.28).For details, see the Cisco Application Virtual Switch Release Notes for these releases.

Remote Leaf support

This release adds support for Cisco AVS in Remote Leaf deployments. Cisco AVS is supported both with VLAN encapsulation and VXLAN encapsulation.

See the chapter “Remote Leaf Switches” in the Cisco APIC Layer 3 Networking Configuration Guide.

Limitations and Restrictions

For Cisco AVS scalability information, see the Verified Scalability Guide for Cisco ACI for the relevant Cisco APIC release.

Changing the MTU VTEP Interface while Decommissioning Cisco APIC

If you are decommissioning a Cisco APIC, do not change the maximum transmission unit (MTU) Virtual Tunnel Endpoint (VTEP) at the same time. If you do so, when you recommission the Cisco APIC, the lease does not appear available although the leaf still has the VTEP entry.

Intra-EPG Isolation of Microsegment EPGs not Supported

Using intra-EPG isolation on a Cisco AVS microsegment (uSeg) EPG is not currently supported. Communication will be possible between two endpoints that reside in separate uSeg EPGs if either has intra-EPG isolation enforced, regardless of any contract that exists between the two EPGs.

Distributed Firewall when Using Direct Service Return with Load Balancing

You should disable Distributed Firewall if you are using direct service return with load balancing. If Distributed Firewall is enabled, an HTTP session will not be established.

Features not Supported for Cisco AVS with Multipod

The following features are not supported for Cisco AVS with multipod in the Cisco APIC 2.0(1.x) release:

■        L3 Multicast

■        Storage vMotion with two separate NFS in two separate PODs

■        ERSPAN destination in different PODs

■        Distributed Firewall syslog server in different PODs

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.

Number of Cisco AVS Instances on ESX or ESXi Host

You can connect a single ESX or ESXi host to only one Cisco AVS at a time. You cannot add multiple Cisco AVS to a single ESX or ESXi host.

Stale VM Entry After Cross-Data Center VMware vMotion

After you migrate VMs using cross-data center VMware vMotion in the same VMware vCenter, you may find a stale VM entry under the source DVS. This stale entry can cause problems, such as host removal failure. The workaround for this problem is to enable "Start monitoring port state" on the vNetwork DVS. See the KB topic "Refreshing port state information for a vNetwork Distributed Virtual Switch" on the VMware Web site for instructions.

Bugs

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.

1.     Go to http://tools.cisco.com/bugsearch.

2.     At the Log In screen, enter your registered Cisco.com username and password; then, click Log In. The Bug Search page opens.
Note: If you do not have a Cisco.com username and password, you can register for them at http://tools.cisco.com/RPF/register/register.do.

3.     To search for a specific bug, enter the bug ID in the Search For field and press Return.

4.     To search for bugs in the current release:

a.     In the Search For field, enter a problem, feature, or a product name and press Return. (Leave the other fields empty.)

b.     When the search results are displayed, use the filter tools to find the types of bugs you are looking for. You can search for bugs by modified date, status, severity, and so forth.

5.     To export the results to a spreadsheet, click the Export Results to Excel link.

Open Bugs

Table 3 lists the open bugs in Cisco AVS Release 5.2(1)SV3(4.1):

Table 3 – Open Cisco AVS bugs

 

Documentation

Related Documentation for Cisco AVS

Cisco AVS documentation is available at the following URL:

http://www.cisco.com/c/en/us/support/switches/application-virtual-switch/tsd-products-support-series-home.html

For information about guides and videos for Cisco AVS, see the Cisco Application Virtual Switch Documentation Overview.

Related Documentation for Cisco APIC

Cisco APIC documentation is available at the following URL:

http://www.cisco.com/c/en/us/support/cloud-systems-management/application-policy-infrastructure-controller-apic/tsd-products-support-series-home.html

Cisco APIC documentation includes the Cisco ACI Virtualization Guide, which provides detailed information about Distributed Firewall and Microsegmentation with Cisco AVS.

Documentation Feedback

To provide technical feedback on this document or report an error or omission, please send your comments to avs-docfeedback@cisco.com. We appreciate your feedback.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.

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.

© 2018 Cisco Systems, Inc. All rights reserved.