NSX stale properties in ESXI reappear even after the cleanup from ESXI host and NSX install fails

Products

• VMware NSX

Issue/Introduction

• NSX install fails with error "Failed to send the HostConfig message.xxxxxxxxx.."

• Resolve action or an attempt to reprepare the host fails.
• On the ESXi host, stale NSX properties are present from a previous install remain, even when there are no NSX VIBs.

[root@ESXi:~] net-dvs -l | grep -E "^switch|com.vmware.nsx.*.enable|com.vmware.common.alias|com.vmware.common.nsxUplink"
switch ## ## ## ## ## ## ## ## - ## ## ## ## ## ## ## ## (cswitch)
 com.vmware.common.alias = <DVS_name> ,         propType = CONFIG
 com.vmware.nsx.<property>.enabled = true ,         propType = CONFIG

• Cleaned up the stale properties from ESXI using command "net-dvs -u <property name> -p hostPropList <DVS name>" however these properties reappear after the host reboot.

Environment

VMware NSX

Cause

Even if the stale properties are removed from ESXI host, vCenter may push these stale properties to host after a host reboot as VC unexpectedly saves the NSX properties in its database.

Resolution

If you believe you have encountered this issue and are unable to upgrade, please open a support case with Broadcom Support NSX-T GSS and refer to this KB article. 

For more information, see Creating and managing Broadcom support cases

Additional Information

VM connectivity issues on ESXi host recently unprepared for NSX

NSX Host Preparation Error: "Failed to send the HostConfig message."