VMs were unable to migrate to ESXi host after NSX upgrade

Products

• VMware NSX

Issue/Introduction

VMs were unable to migrate to the ESXi host after the NSX upgrade

Host /var/run/log/nsx-syslog.log has the following after reboot:

nsx-syslog nsx-opsagent[###]: NSX 263521703 - [nsx@6876 comp="nsx-esx" subcomp="opsagent" s2comp="nsxa" tid="####" level="INFO"] Executed cmd [/opt/vmware/nsx-cli/bin/scripts/nsxcli --cmd "set maintenance-mode enabled"] with return code [0] and reply [Maintenance Mode: enabled]

This issue will occur only when the ESX or OpsAgent is rebooted when the ESX host is in NSX Maintenance mode.

Environment

VMware NSX

Cause

NSX Manager set the ESXi host to NSX maintenance mode, but due to the ESXi host reboot, the opsagent service was restarted. Despite NSX maintenance mode being enabled, an issue caused nsxa to be marked as “up”, leading to a situation where vMotion occurred even though NSX maintenance mode was still active. This inconsistency in the nsxa status prevented CCP connectivity from being restored with NSX Manager.

Resolution

This issue is fixed in NSX 4.2.2.2, 9.0.1, and 9.1

Work Around:

1. From the GUI, enable and then disable NSX maintenance mode.
2. Confirm via logs that CCP connectivity has been restored.
3. Then exit ESXi maintenance mode.