VMware Cloud Foundation 3.9 on Dell EMC VxRail | 24 OCT 2019 | Build 14866160
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:
- Multiple pNIC Selection: Enables the user to select the pNICs used for the NSX-T Virtual Distributed Switch (N-VDS) from the UI in the Add Cluster workflow.
- Cluster-Level Upgrade Support: Provides an option to select the individual clusters within a workload domain for the VMware ESXi upgrades.
- Stretching of Clusters in NSX-T Workload Domain: Enables the manual stretching of a cluster over a Layer 3 network in an NSX-T workload domain. You can also expand and shrink the stretched cluster.
- Improved NSX Data Protection: SDDC Manager can configure NSX Managers to back up on a SFTP server in a separate fault zone. It is recommended that you register a SFTP server with SDDC Manager after upgrade or bring-up.
- L3 Aware IP Addressing: NSX-T based VI workload domains now support the ability to use hosts from different L2 domains to create or expand clusters.
- Multi-Instance Management: Allows you to manage multiple VMware Cloud Foundation instances from a single console.
- 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||220.127.116.11||24 OCT 2019||
|SDDC Manager||3.9||24 OCT 2019||
|VMware vCenter Server Appliance||vCenter Server 6.7 Update 3||20 AUG 2019||
|VMware vSphere (ESXi)||ESXi 6.7 Update 3||20 AUG 2019||
6.7 Update 3
|20 AUG 2019||
|VMware NSX Data Center for vSphere||6.4.5||18 APRIL 2019||13282012|
|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||02 JUL 2019||14062628|
|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||1.0||n/a||n/a|
|vRealize Log Insight Content Pack for vRealize Automation 7.3+||2.2||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||n/a||n/a|
|vSAN content pack for Log Insight||2.1||n/a||n/a|
|VxRail Manager||4.7.300||18 SEP 2019||n/a|
|vRealize Operations Manager||7.5||11 APR 2019||13165949|
|vRealize Automation||7.6||11 APR 2019||13027280|
|Horizon7||7.9.0||25 JUN 2019||13956742|
- 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 known issues and limitations for are as follows:
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.
In some cases, the vLAN & the overlay NSX-T Transport Zones are not added to the nodes of the second NSX-T workload domain
Post the second NSX-T workload domain deployment, the add primary cluster operation to the NSX-T domain workflow succeeds. However, the nodes corresponding to the new cluster added to the new domain are not added to the vLAN and the overlay transport zones.
Workaround: Manually configure the nodes and add both overlay and VLAN zones to them.
The NIOC profile and LLDP profile are not added as a part of the transport node profile
For creating the transport node, you have to create a transport node profile. While creating the transport node profile, the various profiles except that of NIOC and LLDP are created and applied.
Workaround: Manually add the LLDP and NIOC profiles through the UI. The NIOC profile is already created by the work flow. You just have to select it.
VxRail Manager is not added to the exclusion list of NSX-V Firewall in the management domain.
Generally all the VMs in the management domain are made part of the exclusion list of the NSX-V firewall in the management domain. However, the VxRail Manager VM in the management domain is not added to the exclusion list.
Workaround: Manually add VxRail Manager to the exclusion list of the NSX-V firewall in the management domain.
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.
For the secondary cluster, the port group names for the VM port group and vCenter should follow a format
For the secondary cluster creation, the port group needs to follow a particular format as follows:
- The VM port group name should contain
- The vCenter Server network port group name should contain
vCenter Server Network.
Workaround: None. Ensure that you perform this operation before the creation of the secondary cluster.
- The VM port group name should contain