VxRail: How to Upgrade 14G Nodes from TPM 1.2 to TPM 2.0 Without Temporarily Disabling TPM

Summary: VxRail 14G nodes with an active Trusted Platform Module (TPM) version 1.2 cause a precheck error ("VxRail Update ran into a problem"), showing incompatibility, and requiring a TPM 2.0 upgrade. Reimaging the nodes through a professional service engagement is required as part of this procedure. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

This article explains how to upgrade an active TPM 1.2 module to TPM 2.0 without disabling it. 
Because the TPM remains active, node reimaging through a professional service engagement is required.

Cause

This article is one method for dealing with VxRail: Clusters with 14g Nodes That Have an Active TPM 1.2 Module Upgrading to VxRail 8.X. LCM Precheck Fails with an Error Message or Give a Warning.

Above article covers VxRail 14G clusters with an active TPM 1.2 module failing the Lifecycle Management (LCM) precheck with the error 'VxRail Update ran into a problem.

If you would rather not reimage, see VxRail: 14G Nodes Disable an Active TPM 1.2 Module Permanently or Upgrade to a TPM 2.0 Module by Temporarily Disabling the TPM 1.2 for an alternate method of handling active TPM 1.2 modules.

Resolution

Prerequisites:

  • You must procure (contact Dell Sales) a TPM 2.0 Module for every node you want to upgrade.
  • The TPM 1.2 Modules in the current nodes must be functioning (no hardware errors). 
  • Confirm in the vCenter Managed Object Browser (MOB) that the TPM Version is 1.2:
    1. Go to https://<vcenter_ip>/mob and browse to your VMware vCenter’s Managed Object Browser (MOB).
    2. When prompted for a username and password enter the same credentials you would use to access your vCenter Web Client. Ensure that this account has administrator access.
    3. Select the active link in the value column for each of the following items: content > rootFolder > childEntity > hostFolder > childEntity.
    4. This page displays a host value. The Managed Object ID (MOID) for each host displays next to host. In the example below they are highlighted in yellow.
      Error: API_ERROR: BadRequestError: Error code: 400 - {'error': {'message': 'cannot identify image file <_io 
    5. Complete the following steps for each node in the cluster:
      1. Browse to https://<vcenter_ip>/mob/?moid=<Node_MOID>&doPath=capability
      2. Check the tpmVersion on this page.
  • If the value is Unset, the TPM Module is disabled on the host. This KB is not required.
  • If the value is 2.0, the TPM Module is active and at a supported version for vSphere 8.0. This KB is not required.
  • If the value is 1.2, the TPM Module is active. If you do not want to temporarily turn off this module, continue to the next step of this KB.
  • Verify that the vSAN cluster is in a healthy state.
Log in to your vCenter and navigate to VxRail Cluster > Monitor > vSAN > Skyline Health and ensure the vSAN is healthy.  If there are any errors or warnings, resolve them before continuing. The only exception to this would be if you are using a system that is not connected to the Internet and the errors are related to Internet access.

Resolution Steps:

Reimaging the nodes through a professional service engagement is required as part of this procedure.

 
Article Properties
Article Number: 000207727
Article Type: Solution
Last Modified: 09 Feb 2026
Version:  7
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.