VMware Cloud Foundation 3.9.1 on Dell EMC VxRail | 14 JAN 2020 | Build 15345960
Check regularly for additions and updates to these release notes.
VMware Cloud Foundation on Dell EMC VxRail is a solution offering that provides best-in-class serviceability and lifecycle management capabilities for customers looking to automate the deployment and management of the full VMware Software Defined Datacenter (SDDC) stack on Dell EMC VxRail.
The release notes cover the following topics:
This release has the following features:
- Application Virtual Networks (AVNs): Enable vRealize Suite deployment in NSX overlay networks. AVNs provide benefits for portability and failover for planned migration or disaster recovery. New installations of Cloud Foundation 3.9.1 deploy vRealize Suite components to VXLAN-backed AVNs. If you upgrade to Cloud Foundation 3.9.1, vRealize Suite components continue to get deployed on a VLAN-backed Distributed Port Group. To enable AVNs and migrate vRealize Suite components to AVNs for an upgraded system, contact VMware Support. For more information about AVNs, see http://blogs.vmware.com/cloud-foundation/2020/01/14/application-virtual-networks-with-VCF.
- Password management for VxRail Manager and ESXi: You can update or rotate the password for the
mysticusers of the VxRail Manager and the
rootuser of ESXi hosts using the SDDC Manager.
- Automation for L3 stretch clusters: Provides automation for the setup of Layer 3 vSAN stretch clusters.
- Cloud Builder improvements: The Cloud Builder UI includes several workflow improvements and provides access to a deployment report that details the tasks performed during bring-up.
- SSO Management Domain Convergence: Provides the ability to link between the SSOs (PSCs) of two or more VMware Cloud Foundation instances so that the management and the VI workload domains are visible in each of the instances.
- BOM Updates: Updated Bill of Materials with new product versions.
The Cloud Foundation software product is comprised of the following software Bill-of-Materials (BOM). The components in the BOM are interoperable and compatible.
|Software Component||Version||Date||Build Number|
|Cloud Builder VM||18.104.22.168||14 JAN 2020||
|SDDC Manager||3.9.1||14 JAN 2020||
|VMware vCenter Server Appliance||vCenter Server 6.7 Update 3b||05 DEC 2019||
|VMware vSphere (ESXi)||ESXi 6.7 Update 3b||05 DEC 2019||
6.7 Update 3b
|05 DEC 2019||
|VMware NSX Data Center for vSphere||6.4.6||10 OCT 2019||14819921|
|VMware NSX-T Data Center||2.5||19 SEP 2019||14663974|
|VMware Enterprise PKS||1.5||20 AUG 2019||14878150|
|VMware vRealize Suite Lifecycle Manager||2.1 Patch 2||04 MAY 2020||16154511|
|VMware vRealize Log Insight||4.8||11 APR 2019||13036238|
|vRealize Log Insight Content Pack for NSX for vSphere||3.9||n/a||n/a|
|vRealize Log Insight Content Pack for Linux||2.0.1||n/a||n/a|
|vRealize Log Insight Content Pack for vRealize Automation 7.5+||1.0||n/a||n/a|
|vRealize Log Insight Content Pack for vRealize Orchestrator 7.0.1+||2.1||n/a||n/a|
|vRealize Log insight Content Pack for NSX-T||3.8.2||n/a||n/a|
|vSAN content pack for Log Insight||2.2||n/a||n/a|
|VxRail Manager||4.7.410||17 DEC 2019||n/a|
|vRealize Operations Manager||7.5||11 APR 2019||13165949|
|vRealize Automation||7.6||11 APR 2019||13027280|
|Horizon 7||7.10.0||17 SEP 2019||14584133|
- vRealize Log Insight Content Packs are deployed during the workload domain creation..
- VMware Solution Exchange and the vRealize Log Insight in-product marketplace store only the latest versions of the content packs for vRealize Log Insight. The software components table contains the latest versions of the packs that were available and automation at the time VMware Cloud Foundation released. When you deploy the VMware Cloud Foundation components, it is possible that the version of a content pack within the in-product marketplace for vRealize Log Insight is newer than the one used for this release.
The following documentation is available:
The following limitations apply to this release:
The Cloud Foundation 3.9.1 API supports multiple combinations of vSphere Distributed Switches (vDS) and N-VDS switches using up to six physical NICs. VMware Cloud Foundation on Dell EMC VxRail does not include this support.
For VMware Cloud Foundation 3.9.1 known issues, see Cloud Foundation 3.9.1 known issues.
VMware Cloud Foundation 3.9.1 on Dell EMC VxRail known issues and limitations appear below:
Management VMs are unavailable in AZ2 when AZ1 is down
When you have a stretched cluster on the management domain and Availability Zone 1 (AZ1) goes down, if the L2 management network is not stretched you will not be able to manage your environment until AZ1 is back online. Although the management VMs are available on Availability Zone 2 (AZ2), their port groups are not configured correctly and the VMs cannot be accessed.
Workaround: None. You must wait until AZ1 is back online to access the management VMs.
VMware Cloud Foundation on Dell EMC VxRail bring-up fails with error
Failed to apply default vSAN policy
If bring-up fails when deploying the second Platform Services Controller (psc-2), retrying bring-up will fail with the error
Failed to apply default vSAN policy. The cause is that the original deployment of psc-2 was not removed from the vCenter Server inventory.
- Log in to the vCenter Server.
- Delete the psc-2 VM.
- Rename the psc-2 (1) VM to psc-2.
- Retry bring-up.
Bring-up fails with a password error
Bring-up fails with the error
password must contain only alphanumerics and special characters. The error is the result of different password requirements for VxRail and VMware Cloud Foundation.
Workaround: Make sure that VxRail clusters use passwords that meet the Cloud Foundation requirements for the following users:
- Default Single-Sign On Domain User (email@example.com): 8-20 characters. At least 1 uppercase, 1 lowercase, 1 number, and 1 special character (@, !, #, $, %, ?, ^).
- vCenter Server and Platform Services Controller Virtual Appliances root account: 8-12 characters. At least 1 uppercase, 1 lowercase, 1 number, and 1 special character (@, !, #, $, %, ?, ^).
Adding a VxRail cluster to a VxRail workload domain fails
When creating a VxRail VI workload domain, adding a VxRail cluster to the workload domain fails with the error
Install VMCA certificate VxRail Manager.
Workaround: When creating the VxRail cluster, you should use the same VxRail Manager credentials that you used for bring-up. Contact VMware Support to update the credentials in the SDDC Manager database and retry the task.
Deleting a cluster from an NSX-T workload domain fails
If multiple clusters in the workload domain have similar names, deleting one of the clusters can fail with the error
Can't find the TransportNodeProfile for the Cluster: <cluster name>.
- Log in to the NSX Manager for the workload domain with admin privileges.
- Navigate to System > Fabric > Profiles > Transport Node Profiles > Edit.
- Record the names of all the transport node profiles.
- Rename the transport node profiles for all clusters with names similar o the cluster you want to delete.
- In the SDDC Manager Dashboard, delete the cluster.
- Log in to the NSX Manager and rename the transport node profiles back to their original names.
If you use the special character underscore (_) in the vCenter host name for the workload domain create operation, the vCenter deployment fails.
The vCenter deployment fails with the "
ERROR > Section 'new_vcsa', subsection 'network', property 'system_name' validation" error message.
Workaround: None. This is an issue in the vCenter product installer where the installer pre-validation fails. You should create the workload domain by providing valid vCenter host names.
The VxRail vCenter Plugin UI options may disappear after the OpenSSL/Microsoft certificate replace operations of all the components or just VxRail Manager
The certificate replace operation involves changes in VxRail Manager and the vCenter VMs. Sometimes the vCenter plugin download might fail as the communication can happen with invalid thumbprint and the VxRail plugin UI option might disappear from vCenter. As a result, the user cannot invoke the add hosts and the remove hosts operations from vCenter.
Workaround: Reload the plugin by opening the VxRail Manager page which redirects to vCenter and make sure the VxRail UI options are visible in the vCenter UI.