Contents

• Introduction
• Cisco VTS Features
• Limitations and Restrictions
• Known and Resolved Problems
• Using the Cisco Bug Search Tool
• Related Documentation
• Obtaining Documentation and Submitting a Service Request

First Published: August 24, 2017

Introduction

---

This Release Notes document provides information about the new features in Cisco VTS 2.5. It also describes how to access information about the known and resolved issues in Cisco VTS 2.5 and Cisco VTS 2.5 SR3, using Cisco Bug Search Tool.

Cisco VTS Features

Cisco VTS 2.5 supports the following new features:

• Multi VMM Integration—You can integrate Cisco VTS with multiple Virtual Machine Managers while managing a single data center fabric. See Integrating Cisco VTS with Multiple Virtual Machine Managers section in the Cisco VTS 2.5 User Guide for details.

• IPv6 Support for VTS Management Plane— Supports IPv6 in features including L2 High Availability, Inventory, Discovery, Remote authentication, VMM registration.

• Support for Hybrid Overlays (Physical to Virtual), Software Overlays (Virtual to Virtual) with IPv6.

• Support for L2 High Availability (HA). Dual stack clusters are supported for L2 HA.

• Support for Static Multicast in Virtual Topology Forwarded (VTF).

• Support for Open Stack Shared Networks and Provider Router.

• Support for L3VPN to EVPN route stitching. See Enabling L3VPN to EVPN Route Stitching section in the Cisco VTS 2.5 User Guide for details.

• L2 QoS Service Extension Templates—See the Managing Templates chapter in the Cisco VTS 2.5 User Guide for details.

• Support for Underlay Service Extension templates. See the Managing Templates chapter in the Cisco VTS 2.5 User Guide for details about Service Extension Templates.

• VPLS via service extension templates—See the Managing Templates chapter in the Cisco VTS 2.5 User Guide for details.

• Upgrade from Cisco VTS 2.4.1 and Cisco VTS 2.4.2.

  Note	Review the Limitations and Restrictions section for important information related to some of the new features.

Limitations and Restrictions

This release has the following limitations / restrictions:

• Known limitations in Multi VMM feature:

  • Upon 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

  • Cisco VTS 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.

  • External networks are not eligible to be Multi VMM networks.

  • If you have a Multi-VMM setup with two vCenter VMMs, Static Multi Homing across VMMs is not supported.
• Known limitations related to Upgrade:

  • Interface Groups feature for Cisco Nexus 7000 devices and the Service Extension features supported in Cisco VTS 2.4.1 are not migrated as part of the upgrade to Cisco VTS 2.5.

  • If you upgrade to Cisco VTS 2.5 from Cisco VTS 2.4.2, and want to use IPV6 management function:
    • You must change the network settings in VTC by adding following configuration, to register a VMM with IPv6 address or to add TORs/Computes with IPV6 address:

      # vi /etc/network/interfaces
      iface eth0 inet6 static
      address 2001:420:10e:2015:c00::201
      netmask 70
      gateway 2001:420:10e:2015:c00::1
      dns-nameservers 2001:420:200:1::a
      dns-search cisco.com
      # sudo ip -6 route add 2001:420:10e:2015:c00::/70 dev eth0
      

    • You need to uninstall the previous L2HA, and reinstall with both IPV4 and IPV6 address, by creating a new cluster.conf file. See Installing VTS in High Availability Mode section of the Cisco VTS 2.5 Installation Guide for details.

    Note	The V solution, with VTSR/VTF, will still operate only with IPv4 for out of band management function.

• You may 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.

• Selecting vts-default as auth group when you add devices to inventory throws an error. You need to use the default-map auth group

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

• IPv4/IPv6 LLDP 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 655535.

• While you specify the VTF credentials when you install VTF via Host Inventory, you must not use root as the username. Choosing root as username will not allow you to log in to the VTF, after installation. You may choose a username other than root.

• 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]

  To support 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)

  For example:

  # nova flavor-list
  | 9592ec23-0118-4d91-8a71-51375de9e025 | m1.medium | 2048      | 40   | 0         |      | 2     | 1.0         | True      |
  +--------------------------------------+-----------+-----------+------+-----------+------+-------+-------------+-----------+
  # nova flavor-show 9592ec23-0118-4d91-8a71-51375de9e025
  +----------------------------+----------------------------------------------------+
  | Property                   | Value                                              |
  +----------------------------+----------------------------------------------------+
  | OS-FLV-DISABLED:disabled   | False                                              |
  | OS-FLV-EXT-DATA:ephemeral  | 0                                                  |
  | disk                       | 40                                                 |
  | extra_specs                | {"hw:mem_page_size": "2048", "hw:numa_nodes": "2"} |
  | id                         | 9592ec23-0118-4d91-8a71-51375de9e025               |
  | name                       | m1.medium                                          |
  | os-flavor-access:is_public | True                                               |
  | ram                        | 2048                                               |
  | rxtx_factor                | 1.0                                                |
  | swap                       |                                                    |
  | vcpus                      | 2                                                  |
  +----------------------------+----------------------------------------------------+
  
  

  Compute log:
  # ls /sys/devices/system/node/node*
  node0  node1
  # cat /sys/devices/system/node/node*/hugepages/hugepages-2048kB/free_hugepages
  9985
  9985

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

• If TACACS+ 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 Authentication Settings).

• 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

• There is a known issue in OpenStack where live migration without shared storage fails after upgrading to a Kilo version between 2015.1.2-18.1 and 2015.1.3-7. As a workaround, you may need to downgrade to OpenStack version 2015.1.2-18 or upgrade to OpenStack version 2015.1.3-8. For additional details, see the following Red Hat Bugzilla link .

• While discovering 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 Loopback number.

• 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 details.

Known and Resolved Problems

You can get details related to the known and resolved issues in Cisco VTS 2.5 and Cisco VTS 2.5 SR3, using the Cisco Bug Search tool. See Using the Cisco Bug Search Tool for information about how to search for bugs.

Using the Cisco Bug Search Tool

Use the Bug Search tool to search for a specific bug or to search for all bugs in a release.

Procedure

---

Step 1	Go to Bug Search Tools & Resources on Cisco.com.
Step 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 https:/​/​tools.cisco.com/​IDREG/​guestRegistration.do.
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: Click the Search Bugs tab and specify the following criteria: In the Search For field, enter product name and press Return. (Leave the other fields empty.) 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. To export the results to a spreadsheet, click the Export All to Spreadsheet link. For more details on the tool overview and functionalities, check out the help page, located at http:/​/​www.cisco.com/​web/​applicat/​cbsshelp/​help.html.

---

Related Documentation

The Cisco VTS documentation set consists of:

• Cisco Virtual Topology System Installation Guide

• Cisco Virtual Topology System User Guide

• Cisco Virtual Topology System Developer Guide

• Cisco Virtual Topology System Release Notes

These docs are available on Cisco.com.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at http:/​/​www.cisco.com/​c/​en/​us/​td/​docs/​general/​whatsnew/​whatsnew.html.

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.

Copyright © 2017, Cisco Systems, Inc. All rights reserved.