Release Notes for Cisco Virtual Application
Container Services, Release 5.3STV2.0
First Published: June 22, 2015
Last Updated: July 03, 2015
This document describes the features, limitations, and caveats for the Cisco Virtual Application
Container Services (Cisco VACS) software solution. Use this document in combination with the
documents listed in the Related Documentation and the Cisco VACS Documentation Matrix.
This document includes the following sections:
•
Overview, page 1
•
New Features and Enhancements in Release 5.3STV2.0, page 2
•
Software Compatibility, page 3
•
Limitations and Restrictions, page 4
•
Using the Bug Search Tool, page 6
•
Caveats, page 7
•
Related Documentation, page 8
•
Cisco VACS Documentation Matrix, page 10
•
Documentation Feedback, page 10
•
Obtaining Documentation and Submitting a Service Request, page 11
Overview
Cisco Virtual Application Container Services (Cisco VACS) is a software solution that automates the
coordinated licensing, installation, and deployment of multiple virtual services in your datacenter to
enable an easy and efficient setup of virtualized applications. Cisco VACS provides a fully customizable
extended application container abstraction to simplify deploying and provisioning the virtual services.
Cisco Systems, Inc.
www.cisco.com
New Features and Enhancements in Release 5.3STV2.0
Cisco VACS allows you to define extended application container templates and to instantiate them
through automated setup and provisioning of the underlying virtual components. Cisco UCS Director
provides the management interface to deploy, provision, and monitor the Cisco VACS solution.
Cisco VACS leverages the features in the following virtual components to build a secure multi-tenant
cloud and create application container templates:
•
Cisco Nexus 1000V
•
Cisco Prime Network Services Controller (PNSC)
•
Cisco Cloud Services Router (CSR) 1000V
•
Cisco Virtual Security Gateway (VSG)
•
Server Load Balancer (SLB)
Cisco VACS provides you with a choice of ready-to-use application container templates that define the
rules for deploying a collection of virtual machines (VMs) within a private network secured by a firewall.
An application container is a set of virtual services such as virtual switches, routers, firewalls, and other
network devices configured in a consistent manner to deploy different workloads. When you create and
instantiate an application container template, Cisco VACS deploys VMs, and configures networks, the
firewall, and virtual switches, and enables quick provisioning of network and security at the virtual layer.
Key features and benefits of Cisco VACS include:
•
Single workflow automation to logically isolate virtual application workloads at the virtual layer.
•
VMware vSphere support for interoperability across private cloud environments.
•
Consistent provisioning and orchestration experience across physical and virtual assets through
Cisco UCS Director.
New Features and Enhancements in Release 5.3STV2.0
This release of Cisco VACS contains the following new features and enhancement:
New Features
•
Supports Server Load Balancer in VACS containers.
•
Supports optional CSR 1000V, Cisco VSG, and Server Load Balancer deployments.
•
Provides embedded Online Help.
•
Support to the following software versions has changed to incorporate the respective component's
fix for the leap-second issue:
– Cisco Nexus 1000V Release 5.2(1)SV3(1.1) to Cisco Nexus 1000V Release 5.2(1)SV3(1.4)
– Cisco Prime Network Services Controller Release 3.2.2.b to Cisco Prime Network Services
Controller Release 3.4.1b
– Cisco Virtual Security Gateway Release 5.2(1)VSG2(1.1) to Cisco Virtual Security Gateway
Release 5.2(1)VSG2(1.3)
Enhancement
•
The Install PNSC wizard displays confirmation fields for the password and shared secret fields.
Release Notes for Cisco Virtual Application Container Services, Release 5.3STV2.0
2
Software Compatibility
Software Compatibility
The following table lists the compatibility information for Cisco VACS, Cisco UCS Director, and the
relevant Cisco VACS components.
Table 1
Software Compatibility
Cisco VACS
Release 5.3STV2.0
UCS Director
Cisco VACS Components
•
Release 5.3 or the 5.3.1.0 patch
•
VMware vSphere 5.1 or later
•
Release 5.2 or Release 5.2 based patch
releases
•
Cisco Nexus 1000V 5.2(1)SV3(1.4)
•
Cisco Prime Network Services
Controller 3.4.1b
•
Cisco Virtual Security Gateway
5.2(1)VSG2(1.3)
•
Cisco Cloud Services Router 1000V
XE 3.14.0
•
Server Load Balancer (SLB)
– Open Source HA-proxy, Release
1.5.2 1.5.2-2.el6 (on x86_64)
– Keepalived 1.2.15
Release 5.3STV1.1.2
•
Release 5.3
•
VMware vSphere 5.1 or later
•
Release 5.2
•
Cisco Nexus 1000V5.2(1)SV3(1.1)
•
Cisco Prime Network Services
Controller 3.2.2.b
•
Cisco Virtual Security Gateway
5.2(1)VSG2(1.1)
•
Cisco Cloud Services Router 1000V
XE 3.14.0
•
VMware vSphere 5.1 or later
•
Cisco Nexus 1000V 5.2(1)SV3(1.1)
•
Cisco Prime Network Services
Controller 3.2.2.b
•
Cisco Virtual Security Gateway
5.2(1)VSG2(1.1)
•
Cisco Cloud Services Router 1000V
XE 3.14.0
Note
Release 5.2STV1.1.1
Apply the Cisco UCS Director
maintenance patch (patch 1, which is
cucsd_patch_5_2_0_1.zip) before
installing or upgrading to Cisco
VACS Release 5.3STV1.1.2
•
Release 5.1
•
Release 5.2
Note
•
Apply the Cisco UCS Director
maintenance patch (patch 1, which is
cucsd_patch_5_2_0_1.zip) before
installing or upgrading to Cisco
VACS Release 5.3STV1.1.2
Release 5.1
Release Notes for Cisco Virtual Application Container Services, Release 5.3STV2.0
3
Limitations and Restrictions
Table 1
Software Compatibility (continued)
Cisco VACS
UCS Director
Release 5.2STV1.1
•
Note
•
Release 5.1STV1.0
Release 5.2
Apply the Cisco UCS Director
maintenance patch (patch 1, which is
cucsd_patch_5_2_0_1.zip) before
installing or upgrading to Cisco
VACS Release 5.3STV1.1.2
Release 5.1
Release 5.1
Cisco VACS Components
•
VMware vSphere 5.1 or later
•
Cisco Nexus 1000V 5.2(1)SV3(1.1)
•
Cisco Prime Network Services
Controller 3.2.2.b
•
Cisco Virtual Security Gateway
5.2(1)VSG2(1.1)
•
Cisco Cloud Services Router 1000V
XE 3.14.0
•
VMware vSphere 5.1 or later
•
Cisco Nexus 1000V 5.2(1)SV3(1.1)
•
Cisco Prime Network Services
Controller 3.2.2.b
•
Cisco Virtual Security Gateway
5.2(1)VSG2(1.1)
•
Cisco Cloud Services Router 1000V
XE 3.12.0
Limitations and Restrictions
This section describes the limitations and restrictions of Cisco VACS.
General VACS limitations
•
Cisco VACS supports the following:
– ESX versions 5.0 and later
– vCenter versions 5.1 and later
•
Only one PNSC can be deployed per vCenter, but there is no limitation on the number of vCenters
that can be managed as Virtual Account and the number of Cisco Nexus 1000V deployed per
vCenter.
•
All VXLAN VTEPs added per host using the add host operation should be configured to be in the
same subnet.
•
During the add host operation, do not migrate the VSM VMs to VEM.
•
The objectmenu option in the end user portal is visible in the UCS Director Release 5.2 (and the
patches) and Release 5.3. This dummy button will not be visible in the end user portal from UCS
Director Release 5.3.0.1 onwards.
•
If you upgrade to UCS Director patches after upgrading to the Cisco VACS Release 5.3STV2.0, you
must reapply the Cisco VACS patch.
•
Cisco VACS does not support multi-node UCS Director deployments.
•
After you upgrade Cisco VACS to Release 5.3STV2.0, you must manually upgrade the following
infra components: PNSC, VSUM, and Cisco Nexus 1000V. For all existing containers, you must also
manually upgrade Cisco VSG.
Release Notes for Cisco Virtual Application Container Services, Release 5.3STV2.0
4
Limitations and Restrictions
•
UCS Director supports only hosts or clusters under DC. It does not support any folder structures
under DC.
•
The add host operation could fail when you add a host which has a previous version of the Cisco
Nexus 1000V vib.
License limitations
•
Each Cisco Nexus 1000V is licensed with 1024 licenses.
•
When upgrading from Cisco VACS evaluation to Cisco VACS production licenses, note the
following:
– After installing the UCS Director production licenses, the Cisco VACS evaluation licenses are
invalid.
– After installing the UCS Director production licenses, only the Cisco VACS production licenses
are accepted.
– After installing the Cisco VACS production licenses, the existing Cisco Nexus 1000V that was
installed with the evaluation license does not get a permanent Cisco Nexus 1000V license.
After installing the Cisco VACS production licenses, you must deploy a new Cisco Nexus
1000V so that it gets a permanent license.
– A CSR 1000V deployed during the Cisco VACS evaluation licenses comes up with default
licenses and a maximum throughput of 100 Kbps.
– After installing the Cisco VACS production licenses, the existing CSR 1000V of deployed
containers is not automatically licensed with permanent licenses. If required, you must
manually apply the permanent licenses for the CSR 1000V.
– After installing the Cisco VACS production license and keying the CSR token ID, the CSR
1000V that belongs to the new container deployment has permanent licenses with a maximum
throughput of 10 Gbps.
– You require internet connectivity from the Cisco CSR 1000V to the Cisco Smart Licensing
server. The internet connectivity can be ensured by either providing a public IP pool for the CSR
management network or provide proxy settings for the CSR via the Add CSR option. For more
information, see the Installing the CSR 1000V License section in the Cisco Virtual Application
Container Services Installation and Upgrade Guide.
Configuration limitations
•
IP pool limitations:
– The IP pools used for management and uplink pools should have mandatory VLAN and
Gateway fields.
– The IP pools used for the port group-based VM networks in custom containers should not have
the Gateway field.
– The broadcast and network IP addresses should not be used as the IP addresses in the pool.
•
IP subnet pool limitations:
– The subnet cannot contain fewer than 4 IP addresses, or more than 1024 IP addresses.
•
IP address limitations when an IP needs to be entered for install actions, IP pools, and ERSPAN:
– Do not use broadcast and network, Experimental/Use in research IP addresses.
•
Cisco VACS does not configure the upstream switches and routers in the physical infrastructure.
Cisco VACS only configures the virtual infrastructure for PNSC, Cisco Nexus 1000V, and CSR.
Release Notes for Cisco Virtual Application Container Services, Release 5.3STV2.0
5
Using the Bug Search Tool
•
You must configure the upstream devices such that the path MTU between the VEMs has an MTU
of greater than or equal to 1600.
Container and container-related limitations
•
The container add-on operations such as add and delete VMs, configure SNAT and ERSPAN, and
power on/off a container cannot be executed in parallel. You must wait for the current task to
complete before you proceed with the next task.
•
Do not cancel the service request of any of the container add-on operations, such as add and delete
VMs, configure SNAT and ERSPAN, and power on/off a container.
•
You cannot resubmit failed service requests for the container deployment or container add-on
operations.
•
Rollback of container add-on operations is not supported. To undo, you must use the UI for the
add-on operation.
•
Currently, all the service options that are a part of PNSC are not available in UCS Director. The only
available service options are http and https. To access the other service options, you must enter the
appropriate standard port number by ignoring the type selection.
•
During container deployment, sometimes the storage policy selects storage that does not belong to
a shortlisted host from the compute policy.
•
For cluster mode compute policy deployments, all the hosts under the cluster must be a part of Cisco
Nexus 1000V and all the hosts should have same common storage.
Scale limitations
Cisco VACS has the following scale limitations:
Note
•
Number of containers: 50
•
Number of VMs per container: 20
•
Number of VMs per host: 50
•
Number of containers that can be deployed in parallel: 4
These scale limits are not the soft limits and can scale up based on the hardware and pool limits.
SLB Limitations
•
When workload VMs are added or deleted to the SLB zone, there will be a traffic impact for 2 to 3
seconds. This is because HAProxy needs to restart for the new configurations or modifications to be
effective.
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. This web-based
tool provides you with access to the Cisco bug tracking system, which maintains information about bugs
and vulnerabilities in this product and other Cisco hardware and software products.
For more information about the Bug Search Tool, see the Bug Search Tool Help & FAQ.
Release Notes for Cisco Virtual Application Container Services, Release 5.3STV2.0
6
Caveats
Step 1
Go to https://tools.cisco.com/bugsearch/.
Step 2
In the Log In screen, enter your registered Cisco.com username and password, and then click Log In.
The Bug Search page opens.
You must have a Cisco.com account to log in and access the Cisco Bug Search Tool. If you do
not have one, you can register for it at http://tools.cisco.com/RPF/register/register.do.
Note
Step 3
To search for a specific bug, enter the bug ID in the Search For field and press Return.
Step 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 Enter. (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 status, severity, modified date, and so forth.
Tip
To export the results to a spreadsheet, click the Export Results to Excel link.
Caveats
The following are descriptions of the open and resolved caveats in Cisco VACS Release 5.3STV2.0. The
bug ID links you to the Cisco Bug Search Tool.
Table 2
Open Caveats
Bug ID
Headline
CSCuo95017
When the workload VM includes a logical interface such as “virb0” in Linux, the ERSPAN feature does
not work.
CSCuo97734
The container deployment fails when the ESX host on which the VMs are deployed happen to be an offline
VEM module in the Cisco Nexus 1000V VSM.
CSCur34625
IP validations do not include a broadcast address.
CSCur45566
When the container is powered off and then powered on, the Cisco VSG data interface moves to a down
state.
CSCur91980
If the container name and the VM includes blank spaces and special characters such as % and $, the
container deployment fails because the Cisco Nexus 1000V does not create port profiles that include spaces
or special characters.
CSCus09994
When an Ubuntu version 14.04 template is used, correct IP address/hostname are not assigned to the IP
address/host. Hence, the IP addresses will not be reflected in the VMs.
CSCus17034
During the HA deployments, if the VSG deployment fails, the roll back will fail to delete stale IP addresses.
CSCus74629
The Add Host wizard occasionally does not display the VLAN ID for existing VMKNICs on the vSwitch.
CSCuu32360
When there is a SLB switchover, the existing traffic sessions will not be load-balanced efficiently.
CSCuu32387
Under heavy traffic flow, the web based SLB stats are not displayed properly.
Release Notes for Cisco Virtual Application Container Services, Release 5.3STV2.0
7
Related Documentation
Table 2
Open Caveats (continued)
Bug ID
Headline
CSCuu87503
When VMs are added to the container, via Add-VM, and one of the SLB HA VMs is not available, then
the config files of the SLB VMs will not be in sync.
CSCuu91764
When the container has both, ERSPAN and StaticNAT configured, the deletion or rollback of the container
fails. Resubmission of the rollback will delete the container successfully.
Table 3
Resolved Caveats
Bug ID
Headline
CSCus38107
While deleting the port profile, the rollback workflow fails.
CSCus74712
If the existing VLAN(s) of the VMKNICs are not added as part of the uplink port profile that is mapped to
the PNICs, the add host operation proceeds without errors, but fails with a VSUM error upon submission.
CSCus84389
If the VM is powered off, deleting a container or a VM and rolling back a service request workflow fails.
Related Documentation
This section lists the documents used with Cisco VACS and available at the following URL:
Cisco Virtual Application Container Services Documentation
General Information
Cisco Virtual Application Container Services Release Notes
Installation and Upgrade
Cisco Virtual Application Container Services Installation and Upgrade Guide
Configuration
Cisco Virtual Application Container Services Configuration Guide
User Information
Cisco Virtual Application Container Services Self-Service Portal User Guide
Cisco Nexus 1000V Documentation
Cisco Nexus 1000V for VMware vSphere Documentation
Cisco Prime Network Services Controller Documentation
Cisco Prime Network Services Controller Documentation
Cisco Cloud Services Router 1000V Documentation
Cloud Services Router 1000V Documentation
Release Notes for Cisco Virtual Application Container Services, Release 5.3STV2.0
8
Related Documentation
Cisco Virtual Security Gateway Documentation
Cisco Virtual Security Gateway Documentation
Cisco UCS Director Documentation
Cisco UCS Director Documentation
Release Notes for Cisco Virtual Application Container Services, Release 5.3STV2.0
9
Cisco VACS Documentation Matrix
Cisco VACS Documentation Matrix
Not all Cisco VACS guides are updated for each release. The following table lists the guides that
correspond to each Cisco VACS release.
Table 4
Cisco VACS Documentation Matrix
This Cisco VACS
Release
Corresponds with These Guides
5.3STV2.0
5.3STV1.1.2
5.2STV1.1.1
5.2STV1.1
5.2STV1.0
•
Cisco Virtual Application Container Services 5.3STV2.0 Release Notes
•
Cisco Virtual Application Container Services Installation and Upgrade Guide, Release 5.3STV2.0
•
Cisco Virtual Application Container Services Configuration Guide, Release 5.2STV2.0
•
Cisco Virtual Application Container Services Self-Service Portal User Guide, Release 5.2STV2.0
•
Cisco Virtual Application Container Services 5.3STV1.1.2 Release Notes
•
Cisco Virtual Application Container Services Installation and Upgrade Guide, Release 5.3STV1.1.2
•
Cisco Virtual Application Container Services Configuration Guide, Release 5.2STV1.1
•
Cisco Virtual Application Container Services Self-Service Portal User Guide, Release 5.2STV1.1
•
Cisco Virtual Application Container Services 5.2STV1.1.1 Release Notes
•
Cisco Virtual Application Container Services Installation and Upgrade Guide, Release 5.2STV1.1
•
Cisco Virtual Application Container Services Configuration Guide, Release 5.2STV1.1
•
Cisco Virtual Application Container Services Self-Service Portal User Guide, Release 5.2STV1.1
•
Cisco Virtual Application Container Services 5.2STV1.1 Release Notes
•
Cisco Virtual Application Container Services Installation and Upgrade Guide, Release 5.2STV1.1
•
Cisco Virtual Application Container Services Configuration Guide, Release 5.2STV1.1
•
Cisco Virtual Application Container Services Self-Service Portal User Guide, Release 5.2STV1.1
•
Cisco Virtual Application Container Services 5.1STV1.0 Release Notes
•
Cisco Virtual Application Container Services Installation Guide, Release 5.1STV1.0
•
Cisco Virtual Application Container Services Configuration Guide, Release 5.1STV1.0
•
Cisco Virtual Application Container Services Self-Service Portal User Guide, Release 5.1STV1.0
Documentation Feedback
To provide technical feedback on this document or report an error or omission, please send your
comments to:
•
[email protected]
We appreciate your feedback.
Release Notes for Cisco Virtual Application Container Services, Release 5.3STV2.0
10
Obtaining Documentation and Submitting a Service Request
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/c/en/us/td/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 delivers content directly to your desktop using a
reader application. The RSS feeds are a free service.
This document is to be used in conjunction with the documents listed in the “Related Documentation” section.
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.
© 2014-2015 Cisco Systems, Inc. All rights reserved.
Release Notes for Cisco Virtual Application Container Services, Release 5.3STV2.0
11
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Virtual Application Container Services, Release 5.3STV2.0
12