Cisco ACI Virtual Pod Release Notes, 4.0(1h)
Available Languages
Cisco ACI Virtual Pod Release Notes, Release 4.0(1h)
This document describes the features, bugs, and limitations for the Cisco Application Centric Infrastructure (ACI) Virtual Pod (vPod) switch 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:
Release notes are sometimes updated with new information about restrictions and bugs. See this website for the most recent version of this document.
Table 1 shows the online change history for this document.
Table 1 Online History Change
| Date |
Description |
| 2018-10-24 |
Cisco ACI vPod Release 4.0(1h) became available. |
Contents
This document includes the following sections:
Cisco ACI vPod Software Compatibility
About Cisco ACI vPod
Cisco Application Centric Infrastructure (ACI) Virtual Pod (vPod) is a software-only solution that enables you to virtually extend the Cisco ACI fabric into bare-metal cloud environments and other remote locations. It is a new feature in Cisco APIC Release 4.0(1h).
Note: Cisco ACI Virtual vPod is in limited availability in Cisco APIC Release 4.0(1h). Contact your Cisco account team before using Cisco ACI vPod or Cisco ACI Virtual Edge as part of Cisco ACI vPod.
You can deploy Cisco ACI vPod wherever you have at least two servers on which you can run the ESXi hypervisor. It allows you to use Cisco ACI Virtual Edge where you do not have a physical leaf.
Cisco ACI vPod and its components—a pair of virtual spines (vSpines), a pair of virtual leafs (vLeafs), and Cisco ACI Virtual Edge—run on the ESXi hypervisor. The vSpines and vLeafs handle control plane management, and the Cisco ACI Virtual Edge handles packet forwarding, policy enforcement, and all data plane management.
Cisco ACI vPod manages a data center defined by the VMware vCenter Server. You can have up to eight instances of Cisco ACI Virtual Edge in each Cisco ACI vPod in the remote location. You use Cisco APIC to manage Cisco ACI vPod nodes and enforce Cisco ACI policy in the virtual data center.
Cisco ACI vPod communicates with a physical, on-premises pod or multipod over an interpod network. You configure the physical pod or multipod, the interpod connection, and Cisco ACI vPod in Cisco APIC. You then use the Cisco ACI vCenter plug-in, a Python script, or PowerCLI to deploy Cisco ACI vPod component virtual machines (VMs).
Cisco ACI vPod is compatible with any server hardware listed in the VMware Hardware Compatibility Guide.
Note: When you install or configure Cisco ACI vPod, you may see Cisco ACI vPod options labeled vPod.
Cisco ACI vPod Software Compatibility
VMware vSphere Compatibility
Cisco ACI Virtual Pod Release 4.0(1h) is supported for Cisco APIC with releases 6.0, 6.5, and 6.7 of VMware vSphere.
Cisco ACI vPod and Cisco APIC Compatibility
Cisco ACI vPod Release 4.0(1h) is compatible with Cisco APIC 4.0(1h) and later versions.
See the Cisco APIC and ACI Virtual Edge Support Matrix for details.
Virtualization Compatibility Information
The Cisco ACI Virtualization Compatibility Matrix provides interoperability information for Cisco ACI components and configurations that have been tested and validated by Cisco, by Cisco partners, or both.
Compatibility and Upgrade/Downgrade Considerations
Support Matrix
The Cisco APIC and ACI Virtual Edge Support Matrix is an interactive tool that enables you to choose an APIC version and view the compatible Cisco ACI vPod, Cisco ACI Virtual Edge, vSphere, and compatible Cisco APIC versions.
Limitations and Restrictions
Scalability
For Cisco ACI Virtual Edge scalability information, see the Verified Scalability Guide for Cisco ACI for the relevant Cisco APIC release.
Cisco ACI vPod Installation
We recommend that you install Cisco ACI vPod management components—vSpine and vLeaf pairs—on two different hosts. Deploy each pair on two separate hosts with one vSpine and one vLeaf on each host.
At initial release, each instance of Cisco ACI vPod supports two vSpines and two vLeafs—one vSpine and one vLeaf on each host.
Cisco ACI vPod management should be in a separate management cluster from any instance of Cisco ACI Virtual Edge.
Hypervisor Availability
Cisco ACI vPod is available only on the VMware ESXi hypervisor at initial release.
Cisco ACI Multi-Site Support
Cisco ACI vPod is not supported for Cisco ACI Multi-Site environments.
Cisco ACI vPod Deployment
■ The server where you install Cisco ACI Virtual Edge must have an Intel Nehalem CPU or later. You also must set the cluster Enhanced vMotion Compatibility (EVC) to a Nehalem CPU or later. See the knowledge base article Enhanced vMotion Compatibility (EVC) processor support (1003212) on the VMware web site.
■ Only one Cisco ACI Virtual Edge per host is supported.
■ Removing Cisco ACI Virtual Edge or the ESXi host from the VMware vCenter and then adding it back in is not supported. If you do that, Cisco ACI Virtual Edge loses password, infra VLAN, IP address, and other key configuration. You should instead delete the original Cisco ACI Virtual Edge and deploy a new one.
■ After you deploy Cisco ACI Virtual Edge, if the Cisco ACI Virtual Edge VM is moved across VMware vCenter, all the configurations that you made during deployment are lost.
■ We recommend that you install Cisco ACI vPod vSpines and vLeafs on a dedicated VMware cluster.
Management Interface IP Address
If you configure a management interface IP address, the Cisco ACI vPod vSpines and vLeafs must have IPv4 addresses.
VMware vSphere vMotion Support
Cisco ACI vPod vSpines and vLeafs are not supported for VMware vSphere vMotion.
Note: 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.
Remote Leaf
Remote leaf is not supported for Cisco ACI vPod in this release.
Features Not Supported for Cisco ACI Virtual Edge in Cisco ACI vPod Mode
Cisco ACI Virtual Edge is not supported for the following features when it is part of Cisco ACI vPod:
■ VXLAN load balancing
■ Enhanced LACP
■ VMware vSphere Proactive HA
■ Microsegmentation with Cisco ACI (microsegmented EPGs)
■ SPAN and ERSPAN
■ Subnets configured under EPGs
■ Bridge domain-to-VRF mapping change
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 2 lists the open bugs for Cisco ACI vPod for the 4.0(1.x) release:
| Bug ID |
Headline |
| CSCvk05859 |
Contract statistics are not pushed to Cisco APIC from Cisco ACI Virtual Edge. |
| CSCvk65897 |
After a change of Internal VLAN blocks, Cisco ACI Virtual Edge is not updated. |
| CSCvk75907 |
Traffic loss for 40 seconds on flood traffic upon designated Cisco ACI Virtual Edge failover. |
| CSCvk76834 |
Make vem-support commands work for admin accounts. |
| CSCvm35936 |
FT failover leads to loss of traffic. Coop not updated. |
| CSCvm40755 |
CLI support for Cisco ACI vPod creation is not present for Cisco APIC 4.0(1h). |
| CSCvm73818 |
Bounce entry is deleted prematurely if last endpoint on the bridge domain is vMotioned out. |
| CSCvm76280 |
VPOD1 ESX1 is shut down; VMs are vMotioned to ESX2 and become unreachable for 1800 seconds from VPOD2. |
| CSCvm89047 |
L3out contracts Cid for subnet 0.0.0.0/0 is not programmed on DP after deleting or adding trigger. |
| CSCvm89062 |
XR entries for physical pod endpoints point to the old routable unicast TEP pool. |
| CSCvm89089 |
Inventory update fails when migrating across the VMM within Cisco ACI vPod. |
| CSCvm89101 |
Decommissioning a vLeaf or vSpine and then registering the vLeaf with a different IP address causes OpFlex to go down. |
Documentation
Related Documentation for Cisco APIC
Cisco APIC documentation is available at the following URL:
Cisco APIC documentation includes the Cisco ACI Virtualization Guide, which provides detailed information about Distributed Firewall with Cisco ACI.
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.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)