NSX Transport Nodes in "Partial Success" state after reboot with error message "Incorrect value;"

Products

• VMware NSX

Issue/Introduction

• In a NSX 4.x environment, an ESXi transport node is rebooted for other unrelated maintenance task. Upon reboot completion, the ESXi host is showing up as "partial success" in NSX UI.
• This may have impacts on VM network connectivities on the transport node. 
• The ESXi host might show a red exclamation mark and the details of the host showing as "Out of Sync Error" as below:
• 
• After clicking on "Sync" on the above message, the ESXi host is going through the re-resync process but fails at about 64% and becomes "partial success". 
• NSX manager syslog may have the following log entries:
• 2025-12-11T20:47:38.809Z <NSX-Manager> NSX 6182 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updating the DeploymentProgress from: DeploymentProgress [ id=<UUID>, deploymentType=HOST_TN, operationType=UPDATE, progress=68, stateDescription=deployment.progress.tn.create.sending_host_config, removeNsxFlag=false] to DeploymentProgress [ id=<UUID>, deploymentType=HOST_TN, operationType=UPDATE, progress=68, stateDescription=deployment.progress.tn.create.waiting_for_host_config_reply, removeNsxFlag=false] 2025-12-11T20:47:38.816Z <NSX-Manager> NSX 6182 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP8817" level="ERROR" subcomp="manager"] Some error occured when configuring host switch on host: Incorrect value; 2025-12-11T20:47:38.816Z <NSX-Manager> NSX 6182 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP8700" level="ERROR" subcomp="manager"] Incorrect value;
• When trying to remediate this issue by reinstalling the NSX to the host, the old NSX VIBs persist.
• Running command on the ESXi host "nsxcli -c del nsx" would not remove the NSX VIBs and the error message is pointing to "Unable to update switch configuration". Similar symptom to this KB 

Environment

VMware NSX 4.x

Cause

The issue is introduced when the vCenter incorrectly retrieves NSX properties from the ESXi host, and saves these entries into vCenter's Postgres Database.

Resolution

To resolve the issue, please follow the below workaround:

1. Place the affected host into maintenance mode if possible
2. SSH into the affected ESXi host as root
3. Determine which DVS(s) switch is affected by this issue:
   • # net-dvs -l | grep -E "com.vmware.common.alias|com.vmware.nsx.vdl2.enabled"
   • Example output:
     • com.vmware.common.alias = <DVS name> ,        propType = CONFIG
     • com.vmware.nsx.vdl2.enabled = down ,    propType = CONFIG
4. Run the following command on the ESXi host for any DVS showing up from the above step:
   • # net-dvs -s com.vmware.common.opaqueDvs.status.component.vswitch=up -p hostPropList <DVS name>
5. Immediately after executing the above command, return to NSX UI and click "Sync" in the following screen when click on the ESXi host name under "System", "Fabric", "Hosts":
   • 
6. The host should now be synced properly
7. Repeat above steps for all impacted hosts

If above workaround does not resolve the issue, please open a Broadcom Support Request with NSX manager logs from all three nodes, a few of the affected ESXi hosts logs, and reference this KB. 

Additional Information

Uninstalling NSX-T from ESXi host failing with error "Failed to remove all host switches or logical switches"

vDS out of sync, NSX vibs removal failure or Host Transport Node is in "Partial Success" state after its re-prepared for NSX

Uninstalling NSX-T from a Host Transport Node fails: Unable to clear DVS propertycom.vmware.nsx.vdl2.enabled: Status(bad0004)= Busy