VMware vCloud NFV™ 2.0 Release Notes | 13 APR 2017

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

These release notes apply to vCloud NFV 2.0 and cover the following topics:

What's New in this Release

Introduction

VMware vCloud NFV is an ETSI compliant Network Functions Virtualization (NFV) platform for Communication Service Providers (CSPs) looking to radically reduce costs and increase service agility through a CSP-centric VMware Software Defined Data Center (SDDC) architecture.

The vCloud NFV platform enables a modular approach to NFV-based service deployment that is proven in production with CSPs globally, and delivers the shortest time to value while ensuring investment protection.

VMware vCloud NFV 2.0 is a purpose-built carrier grade cloud services platform, with significant NFV-focused features specifically designed to support CSP requirements. This version has been customized for the NFV segment with a focus on the following product themes:

  • Carrier Grade Platform. The VMware vCloud NFV platform delivers continuous availability, consistent performance, and pervasive security. The platform delivers critical functionality among individual components that work in concert to support application aware requirements, reliability, stability, and predictability for the Virtual Network Functions (VNFs).

    • Scalability and Manageability. In vCloud NFV 2.0, the virtualization platform is tailored to manage infrastructure at scale through multiple enhancements in VMware vSphere and VMware vCenter.
    • Pervasive Security. vCloud NFV 2.0 includes hardened security features such as native identity integration through vIDM, and comes with encryption and secure boot technology to protect VMs and images.
    • Improvements in Switching. Specifically for NFV use cases, VMware vSphere now comes with advanced performance settings and enhancements to networking that scales performance significantly.
    • Advanced Availability. New availability features empower administrators to minimize down time during infrastructure upgrade and maintenance windows.
    • Predictive Scaling. One of the key features of vCloud NFV is the native integration of VMware vRealize Operations Manager with VMware vSphere Distributed Resource Scheduler to enable dynamic scaling of workloads at runtime, and making active remediation available through northbound APIs.
  • Secure Multitenancy. Carriers can achieve complete service isolation for secure multitenant environments.
    • NSX Integration with the VIM Layer. Expanding on current integration between VMware vCloud Director and VMware NSX, vCloud NFV 2.0 delivers native NSX integration with the VIM layer used to configure several Edge Gateway features and isolate the services across tenant boundaries. vCloud Director now offers a single point of administration for configuration across the whole NFVI stack, increasing automation, security, and control in a full multitenant environment, which addresses issues such as micro-segmentation, policies, placement, and more.
    • Advanced Role-Based Access Control. vCloud Director introduces the ability to program advanced role-based access control into your network services. This offers full role separation between CRUD and management of all compute and network services provisioned through vCloud Director.
  • Operations Management and Intelligence
    • Integration with vRealize Operations Manager. Through native integration with vRealize Operations Manager and the Distributed Resource Scheduler embedded in VMware vSphere, vCloud NFV 2.0 delivers intent-based workload placement, strong operational monitoring, analytics, and an end-to-end policy-based predictive and reactive remediation platform through a single pane of glass.
    • VMware vRealize Network Insight. vCloud NFV 2.0 introduces vRealize Network Insight, a purpose built product that provides end-to-end topology discovery, visualization, and proactive and reactive 360o network and security analytics.
    • Domain Specific Analytics. The operations management framework is fully extensible and offers northbound integration with OSS/BSS and third-party management packs to provide domain specific analytics correlated across services, access, and network, on both physical and virtual layers.
  • Cloud Management and Service Automation
    • Dual VIM Capabilities. Through dual VIM capabilities, vCloud NFV supports the ability to program the deployment of virtual functions on top of compute, storage, and networking resources managed by vCloud Director. Customers can also use the OpenStack Ocata release as an endpoint through VMware Integrated OpenStack Carrier Edition. This is availabile as a separate product bundle — the vCloud NFV OpenStack Edition.
    • Flexible Automated VNF Life Cycle Management. vCloud NFV provides flexible, automated VNF on-boarding and full service life cycle management through capabilities across the stack.
    • Streamlined Deployment of VNF and NFVI Resources. CSPs can automate and streamline the process of deploying VNFs and NFVI resources including the configuration and provisioning of compute, storage, and networking resources. With policy-based provisioning, placement, and predictable resource consumption, vCloud NFV simplifies the resource allocation for VNFs.
    • Dynamic Policy-Based Scaling Operations at Runtime. Integration between vRealize Operations and VMware vSphere now gives customers the ability to perform dynamic policy-based scaling operations on VMs at runtime. Through northbound API exposure, vRealize Operations enables third-party tools and orchestrators to directly interact with the operational intelligence platform and configure, collect, and consume platform and operational analytics. Third parties can use this functionality to expose domain-specific analytics through management packs and dashboards specific to their VNFs.
    • Programmable VMware vCloud NFV Platform. VMware vCloud NFV offers service providers a programmable platform with open REST APIs easily integrating northbound to MANO systems that manage the complete NFV infrastructure deployment life cycle.
    • Choice of Multitenant VIMs. VMware vCloud NFV offers a choice of multitenant Virtual Infrastructure Managers (VIMs) with vCloud Director, and an easy to deploy OpenStack VIM with VMware Integrated OpenStack.

Components of vCloud NFV 2.0

Included in the vCloud NFV Hard Bundle

  • VMware ESXi 6.5a
  • VMware vSphere Replication 6.5
  • VMware vSphere Data Protection 6.1.4
  • VMware vSAN 6.5 (Standard Edition) (Binaries are distributed as part of a vSphere download. Requires a separate activation license key that is included as part of the vCloud NFV Suite.)
  • VMware vRealize Orchestrator Appliance 7.2
  • VMware vRealize Operations Manager 6.5 (Advanced Edition)
  • VMware vRealize Log Insight 4.3 (Full Edition)
  • vCloud Director for Service Providers 8.20

 Mandatory Add-On Components (Not Part of the vCloud NFV Bundle; Additional License Required)

  • VMware NSX for vSphere 6.3.1
  • VMware vCenter Server 6.5b

Optional Add-On Components (Not Part of the vCloud NFV Bundle; Additional License Required)

  • VMware Site Recovery Manager 6.5
  • VMware vRealize Network Insight 3.3

Important Notes

  • VMware Integrated OpenStack 3.1 is no longer available to new customers. Existing customers must have a valid Support and Subscription (SnS) agreement for continued suppord until End of General Support, as published in the VMware Lifecycle Product Matrix.
  • For VMware Integrated OpenStack 3.1 (and prior versions) End of Availability (EOA), see KB 2149711.

vCloud NFV 2.0 Component Details

VMware vSphere 6.5 (ESXi 6.5a, vCenter Server 6.5b)

VMware vSphere® 6.5 introduces over 650 new features along the following themes:

  • Scale and Performance
    • Scale Improvements Throughout the vSphere Platform. These improvements include the number of hosts per cluster (32 to 64), VMs per cluster (4000 to 8000), CPUs per host (320 to 480), RAM per host (4 TB to 12 TB), VMs per host (512 to 1024), vCPUs per VM (64 to 128), and vRAM per VM (1 TB to 4 TB).
    • Latency Sensitivity Support for Receive Thread SysContext. Latency sensitivity support provides faster data plane performance.
    • SplitTx Mode. SplitTx mode is used to support more CPU resources for data plane intensive workload VNF components.
    • Native Intel Ixgben NIC Driver. The native Intel ixgben NIC driver improves data throughput and reduces latency.
    • Native Hypervisor Support for 2 MB HugePages. Native hypervisor support allows guest HugePages to be backed by hypervisor 2 MB pages as well. HugePages provides a significant performance boost for memory intensive applications.
  • Support for Paravirtual Remote Direct Memory Access (PVRDMA). The technology facilitates exceptionally efficient and fast data transfer between Virtual Network Functions (VNF) components.
  • Move Running Virtual Machines. Running virtual machines can now be moved instantly.
  • Long Distance vMotion. Perform reliable migrations between hosts separated by high network round-trip latency times. vMotion migrations are supported for up to 150 ms round-trip time (RTT).
  • Cross-vCenter vMotion. Cross-vCenter vMotion is now enabled.
  • Simplified Management
    • Content Library Management. The content library provides simple and effective management for content including VM templates, ISO images, and scripts.
    • Content Centrally Located. Content can be shared using a publish/subscribe model and is available from a central location.

For more information refer to the VMware ESXi 6.5.0a Release Notes and the vCenter Server 6.5.0b Release Notes.

VMware vSphere Replication 6.5

  • 5 Minute Recovery Point Objective (RPO) Support for Additional Data Store Types. This version of vSphere Replication extends support for the 5 minute RPO setting to the following new data stores: VMFS 5, VMFS 6, NFS 3, NFS 4.1, VVOL, and vSAN 6.5. This allows customers to replicate virtual machine workloads with an RPO setting as low as 5 minutes between the various data store options.

For more information refer to the VMware vSphere Replication 6.5 Release Notes.

VMware vSphere Data Protection 6.1.4

  • VMware vSphere Data Protection (VDP) 6.1.4. VMware vSphere Data Protection 6.1.4 is primarily a bug fix release. This release addresses some of the compatibility issues between vCenter and VDP in the areas of security, interoperability, and upgrade.

For more information refer to the vSphere Data Protection 6.1.4 Release Notes.

  • VMware vSphere Data Protection Life Cycle. VMware vSphere Data Protection will be discontinued. VMware vSphere 6.5 is the last release that will include vSphere Data Protection.

For more information on support and end-of-life details, refer to the vSphere Data Protection End of Availability FAQ and the related vSphere Data Protection End of Availability blog entry.

VMware vSAN 6.5

VMware vSAN™ 6.5 is distributed as part of the VMware vSphere download. However, the product requires a separate activation license key, included as part of the vCloud NFV Suite.

VMware vSAN 6.5 introduces the following new features and enhancements:

  • iSCSI Target Service. The vSAN iSCSI target service enables physical workloads that are outside the vSAN cluster to access the vSAN datastore. An iSCSI initiator on a remote host can transport block-level data to an iSCSI target on a storage device in the vSAN cluster.
  • 2 Node Direct Connect with Witness Traffic Separation. vSAN 6.5 provides support for an alternate VMkernel interface to communicate with the witness host in a stretched cluster configuration. This support enables you to separate witness traffic from vSAN data traffic, with no routing required from the vSAN network to the witness host. You can simplify connectivity to the witness host in certain stretched cluster and 2 Node configurations. In 2 Node configurations, you can make one or more node-to-node, direct connections for vSAN data traffic, without using a high speed switch. Using an alternate VMkernel interface for witness traffic is supported in stretched cluster configurations, but only when it is connected to the same physical switch as the interface used for vSAN data traffic.
  • PowerCLI Support. VMware vSphere PowerCLI adds command line scripting support for vSAN, to help you automate configuration and management tasks. vSphere PowerCLI provides a Windows PowerShell interface to the vSphere API. PowerCLI includes cmdlets for administering vSAN components.
  • 512e Drive Support. vSAN 6.5 supports 512e magnetic hard disk drives (HDDs) in which the physical sector size is 4096 bytes, but the logical sector size emulates a sector size of 512 bytes.

For more information, refer to the VMware Virtual SAN 6.5 Release Notes.

vCloud Director for Service Providers 8.20

  • Advanced Edge Gateway and Distributed Firewall Configuration via the vCloud Director Tenant Portal. This release introduces the vCloud Director tenant portal with an initial set of controls you can use to configure Edge Gateway instances and NSX Distributed Firewalls in your organization. The tenant portal is a pure HTML5 user interface that can be used in conjunction with the legacy vCloud Director Web Console.
  • A New vCloud Director API for NSX. This release introduces a new proxy API that enables vCloud API clients to make requests to the NSX API. Unlike the NSX API, which is designed to address NSX objects in a global scope such as that of a VMware vCenter data center, the vCloud Director API for NSX is designed to address NSX objects within the scope of a vCloud Director tenant organization.
  • Role Administration at the Organization Level. In previous releases, roles were global objects created by system administrators and available to all organizations. Beginning with vCloud Director 8.20, role objects exist in each organization in the system. System administrators can use the vCloud Director Web Console or the vCloud API to create roles in any organization. Organization administrators can use the vCloud API to create roles that are local to their organization. During upgrade, existing global roles are mapped to local roles with the same names and rights. After upgrade, organization administrators can modify these roles or add new ones for use within their organization. When the system administrator creates an organization, it includes the default set of pre-defined roles and the rights they contain. A system administrator can grant additional rights to an organization. A system administrator can create roles in the system organization and in other organizations, but roles are no longer global to the system.
  • Automatic Discovery and Import of vCenter VMs. Organization VDCs automatically discover vCenter VMs that exist in any resource pool that backs the VDC. A system administrator can use the vCloud API to specify vCenter resource pools for the VDC to adopt. vCenter VMs that exist in an adopted resource pool become available as discovered vApps in the new VDC.
  • Virtual Machine Host Affinity. A system administrator can create groups of VMs in a resource pool, then use VM-host affinity rules to specify whether members of a VM group should be deployed on members of a vSphere host DRS group.
  • Multi-Cell Upgrade. The upgrade utility now supports upgrading all the cells in your server group with a single workflow.

For more details specific to vCloud Director, please consult the vCloud Director for Service Providers 8.20 Release Notes.

VMware NSX for vSphere 6.3.1

NSX 6.3.1 fixes several issues relevant to NFV use cases. New features can be divided into the following categories:

Platform and Compliance Features

  • Cross-vCenter NSX Active-Standby DFW Enhancements
    • Multiple Universal Distributed Firewall (DFW) Sections are Now Supported. Both universal and local rules can consume universal security groups in Source, Destination, and AppliedTo fields.
    • Universal Security Groups. Universal security group membership can be defined in a static or dynamic manner. Static membership is achieved by manually adding a universal security tag to each VM. Dynamic membership is achieved by adding VMs as members based on dynamic criteria, such as the VM name.
    • Universal Security Tags. You can now define universal security tags on the primary NSX Manager and mark them for universal synchronization with secondary NSX Managers. Universal security tags can be assigned to VMs statically, based on unique ID selection, or dynamically, in response to criteria such as antivirus or vulnerability scans.

Operations Enhancements

  • Troubleshooting Dashboard. NSX Dashboard is updated in NSX 6.3.1 to include more features such as service deployment status, NSX Manager backup status, and Edge appliance notifications.
  • Security Tagging. This allows assigning and clearing multiple tags for a given VM through API calls.
  • Syslog Enhancements. A new syslog update is available specifically for Load Balancer.
  • Role-Based Access Control. This feature restricts user management to Enterprise Administrators only. As a result, the NSX Administrator will no longer have permission to create new users or assign roles to new users. From a security standpoint, this helps in creating a clear demarcation of the two administrative roles.
  • Drain State for Load Balancer Pool Members. You can now put pool members into the Drain state, which forces the server to shutdown gracefully for maintenance. Setting a pool member to drain state removes the backend server from load balancing, but still allows the server to accept new, persistent connections.

Service and Routing Enhancements

  • 4-Byte ASN Support for BGP. BGP configuration with 4-byte ASN support is made available along with backward compatibility for pre-existing 2-byte ASN BGP peers.
  • NAT Enhancement for 5-Tuple Match. In order to offer more granular configuration and flexibility for NAT rules, 5-tuple match support is available for NSX 6.3.1.
    • Match criteria is on the basis of five parameters including protocol, source IP, source port, destination IP, and destination port.
    • User interface (UI) changes have been provided to help you more easily specify SNAT/DNAT configurations. When changing DNAT/SNAT configurations on older Edge versions, the UI continues to display the old style of panes.
  • Improved Layer 2 VPN Performance. Performance for Layer 2 VPN has been improved. This allows a single Edge appliance to support up to 1.5 Gb/s throughput, an improvement from the previous 750 Mb/s.
  • Improved Configurability for OSPF. While configuring OSPF on an Edge Services Gateway (ESG), translation of type-7 LSA to type-5 LSA at NSSA boundaries is now possible.
  • IS-IS Removed from NSX Edge. From NSX 6.3.1, you cannot configure IS-IS protocol from the Routing tab.

Security Enhancements

There are several improvements in the Distributed Firewall:

  • DFW Timers. NSX 6.3.1 introduces session timers that define how long a session is maintained on the firewall after inactivity. When the session timeout for the protocol expires, the session closes. On the firewall, you can define timeouts for TCP, UDP, and ICMP sessions and apply them to a user defined set of VMs or vNICs. See Session Timers in the NSX Administration Guide.
  • New Features to Support Micro-Segmentation. To support micro-segmentation in visibility and planning tools, two new features have been introduced.
    • Application Rule Manager simplifies the process of creating security groups and allowing firewall rules for existing applications.
    • Endpoint Monitoring allows an application owner to profile their application and identify processes making network connections.

Cloud Management Platform (CMP) and Partner Integration

  • Scale and Performance Improvements. NSX NetX 6.3.1 provides scale and performance improvements related to service insertion.
  • New API Updates. NSX 6.3.1 ends support of several APIs and replaces them with newer APIs.

For more details, see NSX for vSphere 6.3.0 Release Notes and NSX for vSphere 6.3.1 Release Notes.

VMware vRealize Operations Manager 6.5

Patches to Address Security Advisory

Recently, a critical severity privilege escalation was disclosed in vRealize Operations Manager that is documented in VMSA-2017-0004.7. To address this issue, install the public patch documented in KB 2149591.

Product Enhancements

vRealize Operations Manager 6.5 focuses on enhancing product scalability limits and troubleshooting capabilities.

  • Additional Monitoring Capabilities
    • Adds ability to increase memory and increase the scope of monitoring within the same environment.
    • Enables you to monitor larger environments with the same footprint through platform optimization.
    • XL size node enables you to monitor more objects and process more metrics.
  • Automatic Upgrade of Endpoint Operations Agents
    • The new Endpoint Operations Agent upgrade bundle allows you to automatically upgrade the agent through the vRealize Operations Manager user interface.
  • Enhanced Troubleshooting Capabilities
    • Quickly correlates logs and metrics in context for any monitored object using Log Insight within vRealize Operations Manager.
    • Creates custom metric groups that enable you to focus on the most relevant metrics.
  • Improved Collaboration
    • Simplifies export and import of custom groups and eases dashboard sharing between different vRealize Operations Manager installations.
  • Predictive Remediation
    • Predictive DRS enables vRealize Operations to provide long-term forecast metrics to augment the short-term placement criteria of the vSphere Distributed Resource Scheduler (DRS).

For more information on these enhancements, see What’s New: VMware vRealize Operations 6.5 and the vRealize Operations Manager 6.5 Release Notes.

VMware vRealize Log Insight 4.3

vRealize Log Insight delivers the best real-time and archive log management for VMware environments. Machine learning-based Intelligent Grouping and high-performance search enables faster troubleshooting across physical, virtual, and cloud environments. vRealize Log Insight can analyze terabytes of logs, discover structure in unstructured data, and deliver enterprise-wide visibility using a modern Web interface.

  • Server Features
    • Host table entries now expire after they are idle for three months (after the last ingested event)
    • New upgrade APIs
  • Agent Features
    • New FIPS-140-2 compliance

For additional information see the VMware vRealize Log Insight 4.3 Release Notes.

VMware vRealize Network Insight 3.3

This product is currently offered as an optional add-on to the vCloud NFV bundle. VMware vRealize Network Insight delivers intelligent operations for software-defined networking and security. It helps optimize network performance and availability with converged visibility across virtual and physical networks, and provides planning and recommendations for implementing micro-segmentation based security and operational views to quickly and confidently manage and scale VMware NSX deployment.

  • Enhanced Event Management Experience and New NSX Events. New configuration and inter-communication checks have been added for checking and reporting on NSX manager, controller, and data plane services deployment and production issues. Additionally, all events have been enriched with a new set of information that includes name, severity, category (event tags), and best practice remediation recommendations.
  • Enhanced Visibility into Planning Micro-Segmentation Topology. The expansion of shared wedges into groups is introduced to provide increased visibility into the traffic pattern and improve micro-segmentation planning.
  • NSX for vSphere Firewall Rules Enhancements.
    • The firewall rule negation configuration is supported.
    • The VNIC in source, destination, and Applied To configuration of a firewall rule is supported.
    • The raw IP and port configuration in a firewall rule is supported.
    • The process of configuring the direction (IN/OUT/INOUT) in a firewall rule is supported.
  • NAT Improvements. Users can better visualize the NAT communication between virtual machines when running any VM-VM path trace or path troubleshooting queries. This improved visualization helps in quickly resolving NAT configuration and NAT data path issues. Enhancements have been made in the handling of IPFIX flow records to filter out NAT affected flows.

For additional informaiton, see the VMware vRealize Network Insight 3.3 Release Notes and the VMware vRealize Network Insight Datasheet.

VMware Integrated OpenStack 3.1

Important Notes

  • VMware Integrated OpenStack 3.1 and older releases have been discontinued. Customers with an active support subscription may still use VMware Integrated OpenStack 3.1 (VIO 3.1) only until its end of support date, identified according to the VMware Lifecycle Product Matrix, provided they have an active support subscription for the component products.
  • The upgrade path for an existing NFV will be to VMware Integrated OpenStack Carrier Edition 4.0, available as part of VMware vCloud NFV OpenStack Edition 2.0, which can be purchased separately. Other upgrade options are also available. For further details refer to the VMware vCloud NFV OpenStack Edition 2.0 Release Notes.

VMware Integrated OpenStack 3.1 is based on the OpenStack Mitaka release and provides the following new features and enhancements:

  • Support for the Latest Versions of VMware Products. VMware Integrated OpenStack 3.1 supports and is fully compatible with VMware vSphere 6.5 and VMware NSX for vSphere 6.3.1.
  • NSX Policy Support in Neutron. NSX administrators can define security policies shared by the OpenStack cloud administrator with cloud users. Users can either create their own rules bounded with the predefined ones that can't be overridden, or they can only use the predefined rules, depending on the policy set by the OpenStack cloud administrator. This feature can also be used by cloud administrators to insert third-party network services.
  • New NFV Features. You can now import VMware vSphere VMs with NSX network backing into VMware Integrated OpenStack. Another new feature is full pass-through support, using VMware DirectPath I/O.
  • Seamless Update from Compact Mode to High Availability Mode. If you are updating from VMware Integrated OpenStack 3.0 deployed in compact mode to 3.1, you can seamlessly transition to an High Availability deployment during the update.
  • Specify Adapter Type for Empty Volumes. You can now change the default adapter type by modifying the vmware_adapter_type option for newly created volumes.
  • Profiling Enhancements. You can use VMware vRealize Log Insight as the trace store for the OpenStack profiling tool OSProfiler.

For details, see the VMware Integrated OpenStack 3.1 Release Notes.

VMware vRealize Orchestrator Appliance 7.2

vRealize Orchestrator 7.2 introduces a number of improvements, bug fixes, and extends the automated configuration with new options:

  • Improved Usability of Control Center. This includes localization in Spanish, French, German, Traditional Chinese, Simplified Chinese, Korean, and Japanese.
  • vRealize Orchestrator Plug-In Included. The vRealize Orchestrator plug-in for vRealize Automation is now included in the Orchestrator platform.
  • vRealize Orchestrator 7.2 Ships with vSphere 6.5 Compatible vCenter Server Plug-In. vRealize Orchestrator 7.2 is shipped with a version of the vCenter Server plug-in that is compatible with vSphere 6.5. A redesigned vRealize Orchestrator vCenter Server plug-in is available as a separate download package for vRealize Orchestrator 7.2. This plug-in is compatible with vSphere 6.5 and vRealize Orchestrator 7.2 and in future releases will replace the version of the vCenter Server plug-in currently shipped with the Orchestrator platform. The new vCenter Server plug-in has the following features:
    • Simplified maintenance and faster troubleshooting, compared to the earlier versions of the plug-in.
    • Improved performance thanks to optimized communication with the VMware vSphere Server instances and changes in the caching schema.
    • Maximum compatibility of the scripting API and content compatibility with VMware vSphere products for version 5.5 and later.

For more information on the changes in the new vCenter Server plug-in for vRealize Orchestrator 7.2, see What's New in the New vCenter Server Plug-In. For more information about vRealize Orchestrator 7.2 refer to the VMware vRealize Orchestrator 7.2 Release Notes.

Validated Patches

  • VMware vRealize Operations 6.5 patch to address CVE-2017-5638, see KB 2149591.
  • VMware ESXi 6.5, Patch Release ESXi650-201703002, see KB 2149572.
  • VMware ESXi 6.5 EP04, Patch Release ESXi650-201710401, see KB 2151081.
  • VMware vCenter Server 6.5.0f, see its Release Notes.

Release Notes Change Log

This section describes updates to the Release Notes.

Date Change
14 DEC 2017
  •  Added VMware vCenter Server 6.5.0f to the Validated Patches section.
  •  Added ESXi 6.5 EP04, Patch Release ESXi650-201710401 to the Validated Patches section.
28 SEPT 2017  Updated information about VMware Integrated OpenStack 3.1 EOA.
19 SEPT 2017  VMware Integrated OpenStack 3.1 reached EOA. See KB 2149711 for more information.
03 MAY 2017  Clarified the editions for VMware vSAN, vRealize Operations Manager, and vRealize Log Insight.

Support Resources

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

Resolved Issues

  • Unable to Create Custom Group When Invoking vRealize Operations Manager API.

    After installing a Dell, HP, or NSX adapter in vRealize Operations Manager 6.3 or earlier, the process to create a custom group from within the adapter fails with an exception error. The error indicates a problem with the Java language bindings of the vRealize Operations Manager REST API.

    Fixed in vRealize Operations Manager 6.5.

Known Issues

  • Horizon became inaccessible after changing and reverting the DNS IP address in VIO.

    After changing and then again reverting back the DNS server IP in VMware Integrated OpenStack plugin, the Horizon became inaccessible.

    Refer to VMware Integrated OpenStack 3.1 Release Notes.

  • vSphere Replication appliance VAMI blue screen does not appear after upgrading from 6.1.1 to 6.5.

    After upgrading the vSphere Replication appliance from 6.1.1 to 6.5, the VAMI blue screen does not appear in the console. A blank screen is displayed.

    Refer to vSphere Replication 6.5 Release Notes.

  • Context Help links to the vCloud Director 8.20 User's Guide are broken.

    Context Help links to the User's Guide are broken in 8.20.

    If your production environment is impacted by this issue, please raise a Support Request. A VMware Support Engineer will work with you to assess your environment and outline all available options.

  • Slowness observed in workflow 'opening VM Properties' and 'opening the Add to My Cloud' dialogues.

    After VCD upgrade, users observed that certain elements of the vCloud Director Web UI have a slower response time than previously.

    If your production environment is impacted by this issue, please raise a Support Request. A VMware Support Engineer will work with you to assess your environment and outline all available options.

  • ImportServiceImpl NPE when using import VC VM into existing vApp.

    When attempting to add a VM into an existing application it failed. This issue only occurs when adding the VM from vSphere into an existing vApp. If manually adding it into a new vApp it works.

    If your production environment is impacted by this issue, please raise a Support Request. A VMware Support Engineer will work with you to assess your environment and outline all available options.

  • VCD logs have errors.

    VcListener is getting an update from VC that a VM is moved from one resource pool (RP) to another. The following message is logged many times, 'Property changes map indicated a delta in resource pool of a VM, but the values are missing'.

    If your production environment is impacted by this issue, please raise a Support Request. A VMware Support Engineer will work with you to assess your environment and outline all available options.

  • A failure to deploy a VM in compute fabric does not do the appropriate cleanup, it causes VM to go to pending state upon deletion.

    If a VM deployment failed in compute fabric deployment phase, the required cleanup was missed.

    If your production environment is impacted by this issue, please raise a Support Request. A VMware Support Engineer will work with you to assess your environment and outline all available options.

check-circle-line exclamation-circle-line close-line
Scroll to top icon