NSX Manager Upgrade Failure Due to Maintenance Mode Issue

Products

• VMware NSX

Issue/Introduction

• The NSX upgrade failed because the NSX manager was unable to enter maintenance mode.
• The /var/log/cbm/access_log.log file recorded the following error, confirming the maintenance mode failure:
  
  2025-10-29T23:41:56.725Z 127.0.0.1 - "POST /api/v1/cluster-manager/nodes/a35#####-e###-4###-9###-72##########?action=maintenance_mode_on HTTP/1.1" 500 253 45 44
2025-10-30T04:39:02.699Z 127.0.0.1 - "POST /api/v1/cluster-manager/nodes/a35#####-e###-4###-9###-72##########?action=maintenance_mode_on HTTP/1.1" 500 253 50 49
2025-10-29T23:41:56.699Z ERROR http-nio-127.0.0.1-7989-exec-10 ClusterBootManagerFacadeImpl 75569 - [nsx@6876 comp="nsx-manager" errorCode="MP36728" level="ERROR" subcomp="cbm"] Failed to set maintenance mode to maintenance_mode_on State
com.vmware.nsx.cbm.exception.CbmException:
 at com.vmware.nsx.cbm.rpc.impl.SetMaintenanceModeRequestHandler.setMaintenanceMode(SetMaintenanceModeRequestHandler.java:95) ~[libcbm.jar:?]
  
  
• Further examination of the /var/log/cbm/gmle.log confirmed the absence of the NSX Manager record for the node, which prevented its transition to maintenance mode.
  2025-10-30T04:39:02.673Z ERROR http-nio-127.0.0.1-7989-exec-5 NodeAdministratorImpl 3775 - [nsx@6876 comp="nsx-manager" errorCode="GML173" level="ERROR" s2comp="node-admin" subcomp="cbm"] MaintenanceModeRequest record for node id a35#####-e###-4###-9###-72########## does not exist.

Environment

VMware NSX

Cause

The upgrade cannot proceed because the NSX manager node cannot be placed in maintenance mode, as the node is missing from the Corfu table MaintenanceModeRequest.

Resolution

To resolve the issue, we need to review and modify the NSX database. Therefore, please raise a support request with Broadcom.

Creating and managing Broadcom support request (SR) cases

Additional Information

Related article:

VMware NSX upgrade fails to place manager node in maintenance mode