VMware vCloud® NFV™ 3.2.1 Release Notes | 5 Dec 2019

NOTE: These Release Notes do not provide the terms applicable to your license. Consult the VMware Product Guide and VMware End User License Agreement for the license metrics and other license terms applicable to your use of VMware vCloud NFV.

Check for additions and updates to these Release Notes.

What's in the Release Notes

The release notes cover the following topics:

What's New in This Release

Carrier-Grade Resilient Networking

VMware NSX-T Data Center 2.5 provides the following new features:

  • Automatic l-core Assignment: To get the best possible performance from N-VDS (E), the VM’s vNIC and the l-core attached to the vNIC and pNIC must be NUMA aligned. This feature ensures that N-VDS (E) vSwitch automatically NUMA aligns the three entities. It also automatically allocates Rx and Tx of the VM’s vNIC to different l-cores (NUMA aligned) to increase the overall throughput processed by the vNIC.
  • Edge Features
    • Tier-1 Placement Inside Edge Cluster Based on Failure Domain: Enables NSX-T Data Center to automatically place Tier-1 gateways based on failure domains defined by the user. This feature increases the reliability of Tier-1 gateways across availability zones, racks, or hosts, even when using automatic Tier-1 gateway placement.
    • Support for Mellanox ConnectX-4 and ConnectX-4 LX on Bare Metal Edge Node: Bare Metal Edge nodes now support Mellanox ConnectX-4 and ConnectX-4 LX physical NICs in 10/25/40/50/100 Gbps.
    • Bare Metal Edge PNIC Management - Provides the option to select the physical NICs (p-NICs) to be used as dataplane NICs (fastpath). The number of p-NICs supported on the Bare Metal Edge node is increased from 8 to 16.
  • IPV6 Support is introduced in this vCloud NFV release for dual stack routing, forwarding, and security using static IPv6 for workloads or DHCP relays on gateway interfaces. IPV6 is supported across all interfaces, single or multi-stacked Edge Nodes, Edge Firewall, Distributed Firewall rules for NSX micro-segmentation, and MP-BGP. Additionally, the following IPv6 use cases are supported:
    • IPv6 SLAAC (Stateless Address Autoconfiguration): Provides IPv6 addresses to virtual machines automatically.
    • IPv6 Router Advertisement: NSX-T gateway provides IPv6 parameters through Router Advertisement.
    • IPv6 DAD, NSX-T gateways detect the duplicate IPv6 address allocation.
    • Note: Some of these features are currently available at the infrastructure level and may not be available at the VIM level.

Multi Tenancy Management

VMware vCloud Director 9.7.0.3 for Service Providers Express Patch Release provides bug fixes and updates the vCloud Director appliance base OS and the vCloud Director open-source components. This release resolves CVE-2019-11477 and CVE-2019-11478. For more information, see https://www.vmware.com/security/advisories.

Workload Compute Performance

vSphere 6.7 U3 includes the following performance and processor support updates:

  • vCloud NFV 3.2.1 introduces vSphere 6.7 U3 that primarily includes the following performance improvement updates for operational efficiency of workloads:
    • ixgben driver update
    • VMXNET3 and bnxtnet driver enhancements
  • New SandyBridge microcode: ESXi 6.7 Update 3 adds new SandyBridge microcode to the cpu-microcode VIB to bring the SandyBridge security up to par with other CPUs and fix per-VM Enhanced vMotion Compatibility (EVC) support. For more information, see the KB article 1003212.

Components of vCloud NFV 3.2.1 Standard Edition:

Components of vCloud NFV 3.2.1 Advanced Edition:

Mandatory Add-On Components

Note: This component is required for both Standard Edition and Advanced Edition; additional license is required.

Optional Add-On Components

Note: These components are recommended for Advanced Edition; additional license is required.

Support Resources

To access product documentation and additional support resources, go to the VMware vCloud NFV Documentation page.

Resolved Issues

  • Newly created Tier 0 and Tier 1 routers go to uninitialized state if an Edge cluster has no Edge nodes

    This issue is fixed in NSX-T Data Center 2.5. With this fix, an edge cluster cannot be created without any Edge node in it.

  • Unable to create the in-band management interface on a bare metal NSX-T Edge

    This issue is fixed in NSX-T Data Center 2.5.

  • NSX-V backed network pools available for use when creating NSX-T backed Org VDCs in the HTML UI

    This issue is fixed in vCloud Director for Service Providers 9.7.0.3.

  • Unable to access the VCD HTML UI using Cell FQDN if the public interface is not configured

    This issue is fixed in vCloud Director for Service Providers 9.7.0.3.

  • Network configuration of the VRNI appliance may fail during the first attempt

    This issue is fixed in vRealize Network Insight 4.2.

Known Issues

  • Deletion of Custom Entities in the vCloud Director UI fails

    Attempting to delete the custom entities in the vCloud Director UI fails.

    Workaround: Use CloudAPI to delete custom entities.

  • Unable to access vCloud Director due to insufficient disk space in PostgreSQL Database

    The vCloud Director for Service Providers 9.7.0.3 UI is not accessible, if the PostgreSQL database of the vCloud Director appliance has insufficient disk space.

    WorkaroundIncrease the capacity of the Embedded PostgreSQL Database on the vCloud Director Appliance.

  • Traceflow is not working for Subinterfaces in Guest Intervlan Routing in NSX-T Data Center

    Traceflow from one subinterface IP to another does not work in Guest intervlan routing in NSX-T Data Center.

    Workaround: None

  • Encountering issue while merging PVDCs

    Occasionally the Provider vDCs (PVDCs) cannot be merged due to the stale entries of non-elastic OrgVDCs present in PVDCs.

    Workaround: Contact VMware Technical Support.

  • Patching VCHA-enabled vSphere 6.7 Update 1 to Update 3 may fail

    Patching VCHA-enabled vSphere 6.7 Update 1 to Update 3 may fail.

    Workaround: Remove VCHA before starting the Update/Patch and then reconfigure VCHA after update. For more information, see the vSphere KB article 55938.

  • VM not reflecting its CPU or memory reservation when deployed from a vApp template (imported into catalog) with CPU or memory reservation

    The VM deployed using a vApp template from the content library does not reflect its CPU or memory reservation configuration in a reservation model-based Org VDC. This issue occurs if an OVF template with CPU or memory reservation is imported into a catalog and then the VM is deployed from that vApp template.

    Workaround: Use one of the following:

    • Reserve CPU or memory for the deployed VM manually from the vCloud Director HTML5 UI (OrgVDC > Virtual Machine > Details > Advanced).
    • Import the OVF template directly to deploy the VM instead of using a catalog.
check-circle-line exclamation-circle-line close-line
Scroll to top icon