This Release Notes
document provides information about the new features in Cisco VTS 2.5.2. It
also describes how to access information about the known and resolved issues in
Cisco VTS 2.5.2, using Cisco Bug Search Tool.
Cisco VTS 2.5.2
supports the following new features:
Support for Auto Discoery
with auto reconciliation. For details about this features and enhancements in
the discovery framework, See the
Inventory chapter in the
Cisco VTS 2.5
Support for vCenter 6.5.
Support for SRIOV Trunk
Support for direct upgrade
from Cisco VTS 2.5.1 to Cisco VTS 2.5.2. If you need to upgrade from versions
earlier than 2.5.0, you need to first upgrade to Cisco VTS 2.5.1, and then
upgrade to Cisco VTS 2.5.2.
Support for OpenStack
Support for Red Hat
Enterprise Linux OpenStack Platform director
Support for Open vSwitch
(OVS) on OpenStack
Support for OpenStack
Support for VTF as L2
Single Root I/O Virtualization (SR-IOV) enabled interfaces
IPv6 Support for VTSR —
VTSR registration is supported over IPv6.
Limitations and Restrictions section for important information related to some
of the new features.
This release has the
following limitations / restrictions:
vCenter-based setups, Cisco VTS supports only discovery using the CSV option.
Auto Discovery using seed IP is not supported for vCenter-based setups.
VTF L2 mode is supported
only on OpenStack Newton.
Migration from OVS to VTF
is not supported.
group range reverts back to default range when you edit the interface group by
adding new modules or devices. However, in physical interface group, the custom
range is retained even though you update the interface group with additional
Cursor does not
show up in username and password text boxes on the Cisco VTS login page. This
happens only when Cisco VTS UI is accessed using Google Chrome browser, after
Cisco VTS is restarted or upgraded, or when it comes up for the first time.
Waiting for few minutes gets the focus on the credentials text box on login
page. Also, you can still go ahead and enter the credentials which will still
show up in the appropriate box.
Known limitations in Multi
register vCenter as a VMM, and, for the first time, perform a publish operation
to publish a tenant and multiple networks to this vCenter VMM, the tenant and
networks fail to get published to the VMM. The error next to the policy
certificate shows exception related to SSL handshake. Click the Retry button to
get the tenant and networks published to the VMM.
publishing, Cisco VTS does not create the users for a tenant that it creates in
OpenStack. To view the tenant project, user has to be assigned to the project.
The OpenStack user has to attach a user to the tenant
publishes networks to OpenStack as network type = vxlan. Before performing a
publish operation, make sure that the plugin.ini, which is located at
/etc/neutron/plugin.ini, has the following properties with network type vxlan
as one of the values, for example:
type_drivers = vxlan, <network_type2>, <network_type3> … <network_type_n> [comma
separated list of network types]
tenant_network_types = vxlan, <network_type2>, <network_type3> ….<network_type_n>
[comma separated list of network types]
In order to
delete a published network/subnet, you have to first unpublish the network, and
then perform the delete operation.
When you create an overlay
network/subnet from VTS, publish from VTS to a target VMM (OpenStack Liberty),
perform port attach operations, and then unpublish the network from the target
VMM, the network and subnet are deleted from target VMM. Cisco VTS throws an
exception during the deletion. You can ignore this exception.
networks are not eligible to be Multi VMM networks.
delete a network or subnet from Cisco VTS after a publish operation. You need
to delete the publish operation before you change network or subnet from the
source VMM or VTS. If you update from source VMM, the target VMM will nor get
affected. If you update from the VTS GUI, the update will fail.
If you have a Multi-VMM
setup with two vCenter VMMs, Static Multi Homing across VMMs is not supported.
Cisco VTS supports only one
domain setup in Openstack. Otherwise, there might be confusing operation done
to other domains in in the same OpenStack environment.
encounter a string conversion error in ncs-java-vm.log, while adding a physical
device to a device group. This error occurs when Cisco VTS checks whether a
device is a VTF and identifies that it is not, and, therefore, not defined by
an IP address. You may ignore this error.
You must create separate
DVS Switches on vCenter for port interfaces connected in V-host and P-host.
Otherwise, you may face P2V connectivity issues with the port group with cisco
Nexus 7000 devices. Cisco VTS does not support VM migration across DVS.
support is not available for Cisco ASR 9000 devices. Cisco VTS auto discovery
does not work for Cisco ASR 9000 devices with IPv4/IPv6.
For VMM registration,
Cisco VTS does not support dual stack configuration on VTC and VMM. Ensure that
the same IP version (either IPv4 or IPv6) is used on VTC and the VMM.
The IPV6 hostname added in
the vCenter should match with the hostname you added to the inventory through
using CSV or Discovery. If is does not match, you will encounter mac-binding
issues when you do a port attach.
If you add a TACACS+ server
with IPv6 address in the Cisco VTS UI, and on the TACACS+ server if IPv6 TACACS
port is disabled, the TACACS+ server will not be reachable. Even if the IPv4
TACACS port is enabled on the server, the server will be unreachable as there
is no support for roll back to IPv4 when IPv6 fails.
VRF name change from VTS
GUI is not supported for VTSR. Cisco VTS does not allow changing the name of a
router if it connects to a port on a V node.
If you are using VTSR,
then BGP ASN value you set should be between 0 and 65535.
specify the VTF credentials when you install VTF via Host Inventory, you must
the username. Choosing
username will not allow you to log in to the VTF, after installation. You may
choose a username other than
When you add
bulk VMs on a vhost compute, one VM fails to spawn because of lack of free
hugepage. You will see the below log in /var/log/neutron/server.log:
[Insufficient free host memory pages available to allocate guest RAM]
vhost-user mode, numa_nodes and mem_page_size in the OpenStack flavor
configuration should be changed as follows:
# nova flavor-key m1.medium set hw:numa_nodes=2 (This number is based on the numa nodes you have on the compute, if you have one set it to 1, if you have two nodes set it to 2)
# nova flavor-key m1.medium set hw:mem_page_size=large (You can do this customized setting with any flavor)
When you add
multiple TACACS+ servers via
Administration > Remote Authentication Settings,
and click the
Save, some times the Cisco VTS UI does not show all
the TACACS+ servers you have added. You many need to refresh the page to view
all the TACACS+ servers added. Clear the browser cache to solve this issue.
When you log in
using the vCenter VTC plugin, ensure that you log in as a Cisco VTS local admin
user, even if you have enabled TACACS+ based external authentication and
authorization and have users with Cisco VTS admin privileges configured in the
TACACS+ server. Only a Cisco VTS admin user present in the Cisco VTS local
database is allowed to log in via the vCenter plugin.
server IP, port, and key attributes are updated through REST API, the changes
will not have any effect on the AAA functions. You need to update these
parameters via the Cisco VTS UI (Administration > Remote
In Cisco VTS,
you can add two entries for the same TACACS+ server—one with the IP address,
and the other with the Hostname. However, you can enable accounting only on one
of these servers.
Cisco Nexus 7000
TORs with TACACS+ configuration is not supported on Cisco VTS. This is due to a
limitation in the platform.
In an OpenStack Liberty
environment, bulk port attach causes errors and multiple VMs fails to spawn
while you try to attach multiple ports to networks. You need to edit the
libvirtd.conf file to increase the keep alive interval. The following
configuration is recommended for creation of ten VMs.
# vi /etc/libvirt/libvirtd.conf
keepalive_interval = 5
keepalive_count = 100
Cisco ASR 9000 series routers using the Discovery feature, Cisco VTS gets the
IP address of the interface which is connected to the neighbor device (spine or
border leaf), and not the management interface IP address. You need to manually
edit the discovery table to provide the management interface IP address, to
ensure that the device is added to the inventory.
When performing bulk port
attach for tenant VMs spawned across multiple hosts with vCenter Web Client
using the networking tab, some of the port attach events are missed and not
captured or processed. Bulk port attach for a maximum of 8 tenant VMs in the
same scenario works without any events being missed. If you need to perform a
bulk port attach for more than eight tenant VMs, it would work only if this is
being done for tenant VMs on the same host. This is due to a vCenter networking
issue, and a case has been opened with VMware to resolve this issue
Do not use special
characters while creating Tenant/Network/Router via vCenter VTS plugin. VTS GUI
does not support this, and the name will not show up in the GUI.
For V-side tenant VMs, if V2V
migrations are performed, you need to perform ARP flush and then ping the
gateway for MAC-to-IP binding to be complete.
In the VTS GUI,
Loopback IP address is retrieved automatically in network inventory using the
Cisco Nexus 9000
Series switches running NX-OS version 7.0(3)I2(1) and later do not support VTEP
connected to FEX host interface ports.
After migrating a
VM to a different host, Cisco Nexus 9000 switch still shows old host details in
the MAC table. However, the BGP routing table (show bgp l2vpn evpn) has the
correct details. See
CSCuy77657 for more
Known and Resolved
You can get details
related to the known and resolved issues in Cisco VTS 2.5.2, using the Cisco
Bug Search tool. See
the Cisco Bug Search Tool for information about how to search for bugs.
Using the Cisco Bug
Use the Bug Search
tool to search for a specific bug or to search for all bugs in a release.
Subscribe to the
What’s New in Cisco
Product Documentation as an RSS feed and set content to be delivered
directly to your desktop using a reader application. The RSS feeds are a free
service. Cisco currently supports RSS Version 2.0.