DRS should be Enabled and Fully automated for the cluster containing host (<hostname>). Alternatively, put the host in vSphere maintenance mode manually.
search cancel

DRS should be Enabled and Fully automated for the cluster containing host (<hostname>). Alternatively, put the host in vSphere maintenance mode manually.

book

Article ID: 422205

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • NSX upgrade pre-checks are run as part of upgrade routine.
  • Host pre-check is flagging DRS inconsistency on all Host Transport Nodes in the cluster:
    DRS should be Enabled and Fully automated for the cluster containing host (<ESXi hostname>, <ESXi UUID>). Alternatively, put the host in vSphere maintenance mode manually.
  • In the vCenter, DRS is enabled and set to fully automated.
  • In NSX logs, you can see that DRS status is not read correctly:
    /var/log/cm-inventory/cm-inventory.log
    2025-12-03T12:52:40.203Z  INFO pool-50-thread-9 ESXMaintenanceModeHelper 338034 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="upgrade-coordinator"] [HUT] DRS behaviour for the cluster of the host  (########-####-####-####-########e064, <host TN hostname>) is manual

Environment

VMware NSX

Cause

NSX manager is silently out of sync with the vCenter.

Resolution

This is a condition that may occur in a VMware NSX environment.

Workaround:

  1. In NSX UI, browse to System - Fabric - Compute Managers.
  2. Identify the Compute Manager (vCenter) which the host transport nodes in question are connected to.
  3. Select the vCenter.
  4. Use the EDIT button.
  5. Edit the "FQDN or IP address" of the vCenter - don't change anything, enter administrator account (typically [email protected]) and the password.
  6. Use the "SAVE" button to save the changes. 
    This will initiate full sync up of NSX Manager with the vCenter. 
  7. Re-run the upgrade pre-checks for Hosts. 
Powered by Wolken Software