NSX uninstallation on the managed host failed due to inaccessible vSAN File Service VM

Products

• VMware NSX
• VMware vSAN

Issue/Introduction

• vSAN File Service VM is connected to NSX segment.
• The host was placed in maintenance mode to remove the NSX configuration. The vSAN File Service VM remains inaccessible and connected to the NSX segment, as designed.
• NSX uninstallation on the managed host failed due to inaccessible vSAN File Service VM. The error message appeared in the NSX UI.
  
  Error: Can not delete Transport Node /infra/sites/default/enforcement-points/default/host-transport-nodes/esxiXXXXhost-XX because 1 VM(s) on it is/are attached to logical port(s). Please use the object name or UUID in Global Search to find all linked objects. (Error code: 9497)

Environment

VMware NSX 4.x
VMware vSAN 8.x

Resolution

Please note that if NSX is removed from the host, the vSAN File Service VM cannot be rebuilt after the host exits maintenance mode, as the corresponding NSX segment will no longer exist. Stop and open a Broadcom support case if the vSAN File Service VM needs to be rebuilt. Refer Creating and managing Broadcom support cases

Solution:
Right click on inaccessible vSAN File Service VM and click 'Remove from Inventory'. Then, remove NSX from host follow document Uninstall NSX from a Managed Host in a vSphere Cluster