The VMware Cloud Foundation (VCF) 4.4.1 on Dell EMC VxRail release includes the following:
VMware Cloud Foundation 4.4.1 | 25 MAY 2022 | Build 19766960
VMware Cloud Foundation 18.104.22.168 | 30 JUN 2022 | Build 19948546
Check for additions and updates to these release notes.
The VMware 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||4.4.1||12 MAY 2022||19766960|
|SDDC Manager||4.4.1||12 MAY 2022||19766960|
|VxRail Manager||7.0.371||25 May 2022||n/a|
|VMware vCenter Server Appliance||7.0 Update 3d||29 MAR 2022||19480866|
|VMware ESXi||7.0 Update 3d||29 MAR 2022||19482537|
|VMware Virtual SAN Witness Appliance||7.0 Update 3c||27 JAN 2022||19193900|
|VMware NSXT||22.214.171.124.4||6 MAY 2022||19762317|
The following documentation is available:
The following limitations apply to this release:
You can install VMware Cloud Foundation 4.4.1 on Dell EMC VxRail as a new release or perform a sequential or skip-level upgrade to VMware Cloud Foundation 4.4.1.
If you deploy VMware Cloud Foundation 4.4.1 on Dell EMC VxRail with VxRail Manager 7.0.372, you must upgrade to VMware Cloud Foundation 126.96.36.199 on Dell EMC VxRail. See How to support VxRail 7.0.372 with VCF 4.4.1/188.8.131.52.
You can perform a sequential or skip level upgrade to VMware Cloud Foundation 4.4.1 on Dell EMC VxRail from VMware Cloud Foundation 4.4, 4.3.1, 4.3, 4.2.1, 4.2, 184.108.40.206, or 4.1. If your environment is at a version earlier than 4.1, you must upgrade the management domain and all VI workload domains to VMware Cloud Foundation 4.1 and then upgrade to VMware Cloud Foundation 4.4.1.
IMPORTANT: Before you upgrade a vCenter Server, take a file-based backup. See Manually Back Up vCenter Server.
NOTE: Scripts that rely on SSH being enabled on ESXi hosts will not work after upgrading to VMware Cloud Foundation 4.4.1, since VMware Cloud Foundation 4.4 disables the SSH service by default. Update your scripts to account for this new behavior. See KB 86230 for information about enabling and disabling the SSH service on ESXi hosts.
The following features are introduced in this release:
You can perform a sequential or skip-level upgrade to VMware Cloud Foundation 220.127.116.11 from Cloud Foundation 4.4.1, 18.104.22.168, 4.3.1, 4.3, 4.2.1, 4.2, 22.214.171.124, or 4.1. If your environment is at a version earlier than 4.1, you must upgrade the management domain and all VI workload domains.
To upgrade the management domain, apply the following bundles, in order:
NOTE: Before triggering upgrade to VCF 126.96.36.199, download all component upgrade/install bundles from VCF 4.4.1.
VMware Cloud Foundation on Dell EMC VxRail 188.8.131.52 contains the following BOM update:
|Software Component||Version||Date||Build Number|
|SDDC Manager||184.108.40.206||30 JUN 2022||19948546|
After you upgrade to VMware Cloud Foundation on Dell EMC VxRail 220.127.116.11, you can perform an out-of-band upgrade to VxRail Manager 7.0.372. VxRail Manager 7.0.732 includes security fixes for VxRail Manager and ESXi. See How to support VxRail 7.0.372 with VCF 4.4.1/18.104.22.168 for more information.
For VMware Cloud Foundation 4.4.1, see VMware Cloud Foundation 4.4.1 known issues. Some of the known issues may be for features that are not available on VMware Cloud Foundation on Dell EMC VxRail.
VMware Cloud Foundation 4.4.1 on Dell EMC VxRail Known Issues appear below:
VxRail plugin will not load in vSphere Client and displays the error "The provided vCenter credentials are not valid."
If the vCenter Server certificate is replaced more than once with same subject attributes with different root CA, then the connection between VxRail and the corresponding vCenter Server is lost.
Workaround: See Dell KB article Dell VxRail: VxRail plug-in displays error after replacing vCenter certificate in VCF on VxRail environment
VxRail bundle is available for an upgrade even though the NSX-T upgrade is still in-progress on VMware Cloud Foundation on VxRail 4.x environment.
VxRail bundle is available for upgrade in SDDC Manager UI Bundles page and Update/Patches tab even though NSX-T upgrade is still in-progress on VMware Cloud Foundation on VxRail 4.x environment.
Both NSX-T bundle and VxRail bundle can become available for upgrade in SDDC Manager UI Bundles page.
Workaround: Once you complete the NSX-T upgrade, the VxRail upgrade can be triggered. See VMware Knowledge Base article 88847 for more information.
vSphere Cluster Services (vCLS) VMs are moved to remote storage after a VxRail cluster with HCI Mesh storage is imported to VMware Cloud Foundation
When you configure HCI Mesh storage on a VxRail cluster and then import it to VMware Cloud Foundation, vCLS VMs are moved to the remote storage instead of being placed on the cluster's primary storage. This can result in errors when you unmount the remote storage for the cluster.
In the Hosts and Clusters tab, click the Cluster entity and check the URL.
The cluster morfId for this URL is 'domain-c10'.
Be default, vCLS property set to true:
Click Edit Settings, set the flag to 'false', and click Save.
Click Edit Settings, set the flag to 'true', and click Save.
Three vCLS VMs are displayed in the VMs and Templates tab.
The API does not support adding a host to a cluster with dead hosts or removing dead hosts from a cluster
The following flags appear in the API Reference Guide and API Explorer, but are not supported with VMware Cloud Foundation on Dell EMC VxRail.
forceHostAdditionInPresenceofDeadHosts: Use to add host to a cluster with dead hosts. Bypasses validation of disconnected hosts and vSAN cluster health.
forceByPassingSafeMinSize: Remove dead hosts from cluster, bypassing validations.