The VxRail Bundle 8.0.000 including vSphere 8.0 and vSAN 8.0 is available for download since a few days now:
https://www.dell.com/support/home/en-us/product-support/product/vxrail-software/drivers
Before initiating a prematurely upgrade I’d like to advise to have a look at the Release Notes first – especially the Key Differences section:
https://www.dell.com/support/manuals/en-us/vxrail-appliance-series/vxrail_release_notes_8.0/what-is-new-in-vxrail-8.0.000?guid=guid-8693278b-2280-47e0-88d9-4b37a7628cf2&lang=en-us
(some of the) Key Differences:
VxRail based on the Quanta hardware platform and VxRail E460/F, P470/F, S470, V470 are not supported for VxRail 8.0.000.
VMware has discontinued support for Trusted Platform Module (TPM) 1.2 in VMware vSphere 8.0. VxRail does not allow the upgrade for clusters containing nodes with active TPM 1.2 modules. In order to upgrade to VxRail 8.0, disable TPM 1.2 or replace the TPM 1.2 modules with TPM 2.0. TPM 1.2 can be disabled to perform the upgrade, provided TPM is not in use by VMware features, like secure boot. See the VxRail VxRail TPM and Secure Boot Tech Note for instructions to disable TPM.
NOTE: If your environment requires the continued use of secure boot with TPM 2.0, you should not upgrade at this time.
RecoverPoint for Virtual Machines is not supported on vSphere 8.0. Do not upgrade to VxRail 8.0.000 if you are using RecoverPoint for Virtual Machines.
DPUs are not supported in VxRail version 8.0.000.
If you are running SmartFabric Services (SFS) with VxRail, you should not upgrade to VxRail 8.0.000.
Before the upgrade, generate the appropriate VxRail upgrade in SolVe for the software update bundle.
Customer-managed VMware vCenter Server plugin:
If you are using a customer-managed VMware vCenter Server environment, you must upgrade the VMware vCenter Server environment to VMware vSphere 8.0 before upgrading your VxRail to VxRail 8.0.000.
If you are using a customer-managed VMware vCenter Server environment, see KB 000204712 after updating your VMware vCenter environment to VMware vSphere 8.0 to resolve a known issue with the VxRail plugin failing to deploy.
VMware vSphere 8.0 license keys are required for a cluster to run on VMware vSphere 8.0:
The lifecycle management pre-check will not stop a user from upgrading without VMware vSphere 8.0 license keys.
Without vSphere 8.0 license keys, the nodes run on 60-day evaluation license keys. Go to VMware Customer Connect to determine if VMware vSphere 8.0 license keys are required for the clusters and to obtain them.
NOTE Due to limited availability of GPU drivers for VMware ESXi 8.0, the GPU will be validated post-VxRail 8.0.000 release. Clusters with GPUs should not be upgraded to VxRail 8.0.000 until they are confirmed.
Another thing to mention is that vCenter localos users won’t be supported any more in vSphere 8.0. If you have deployed a VxRail Cluster with an internal vCenter Server the automatically created VxRail Management user is a localos user. You will have to add a new VxRail Manangement user @vsphere.local during the upgrade (you can find this information in the Solve Procedure).
vSphere 8.0 does not support local OS user and group accounts used in VxRail-managed vCenter deployments
Deprecation of localos accounts: Support for use of localos accounts as an identity source is deprecated. VMware plans to discontinue support for use of the local operating system as an identity source. This functionality will be removed in a future release of vSphere.
https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u3c-release-notes.html#product-support-notices-6
If you have read up to this point, I hope my article was helpful to you. Feel free to share if you like…
// footnotes:
Date: 06.02.2023
Version: 1.1