Remediate of NSX 4.2.1 prepared stateless Hosts fails

Products

• VMware NSX

Issue/Introduction

• NSX install fails for the stateless hosts with NSX 4.2.1 installed on them.
• A reboot of stateless host can cause this issue.
• This issue may also trigger when the ESXi host patching or upgrade performed.
• In the process of upgrading the NSX VIBs on the ESXi host where Host profiles are utilized to remediate the following error is encountered: 

  "Host profile apply failed with error: NSX Switch configuration failed in NSX. Please check transport node realization status in NSX for current status and error details."

•  Log lines similar to the below are encountered in the /var/run/log/nsxaVim.log in the ESXi support bundle:

  nsxaVim: [2107567]: ERROR Failed to fetch or update ports dvs (## ## ## ## ## ## ## ## ## ## ## ##): {'fault': 'NotFound', 'msg': 'The object or item referred to could not be found.', 'faultMessage': []}^@
  
  nsxaVim: [1052597]: INFO Result msg:[b"Port opaque data validation failed on VDS: ['## ## ## ## ## ## ## ## ## ## ## ##']"]^@

Environment

VMware NSX

VMware NSX-T Data Center

Cause

The ESXi are NSX prepared and are stateless, so they need an auto-deploy server to provide the required start files when hosts power on.
The code assumes that there DVS and ports exist on the host but at this time, the stateless host only has the temporary DVS (with prefix M-), and fails as a result of this.

Resolution

This issue is resolved in VMware NSX 4.2.2, available at Broadcom downloads.

If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.

Workaround

1. Place the ESXi host into Maintenance mode, move the host to the Data Center level of the vCenter Inventory.
2. Once the ESXi host has been removed from the cluster it should begin uninstalling NSX from the host automatically. 
3. To confirm that NSX VIBs have been removed, run the below command on the ESXI shell:

   esxcli software vib list | grep nsx

4. Place the ESXi back into the NSX prepared cluster.
5. Now use Host-profiles to remediate the ESXi host.