NSX Host upgrade pre-checks failed for the ESXi hosts that no longer exist in the vCenter inventory.

Products

• VMware NSX

Issue/Introduction

• An upgrade pre-check failed and caused the upgrade process to pause.
  
  

• An ESXi host was removed from vCenter without first removing it from NSX.

•  The Host is not visible under the Host and Cluster section of the UI: System > Fabric > Hosts > Clusters or Standalone.

• Running the GET API '/api/v1/transport-nodes/########-9886-ac8a-65fa-############/state' reveals the following results:

    "node_deployment_state" : {
      "state" : "disconnected",
      "details" : [ {
        "sub_system_id" : "########-9886-ac8a-65fa-############",
        "state" : "disconnected",
        "failure_message" : "Heartbeating between NSX management node and host "########-9886-ac8a-65fa-############ is down. ",
        "failure_code" : 26021
      } ]
    },
    "deployment_progress_state" : {
      "progress" : 100,
      "current_step_title" : "Configuration complete"

Environment

VMware NSX

Cause

When an ESXi host is removed directly from vCenter without first removing NSX, it can result in entries for that host remaining in the NSX database.

Resolution

See https://knowledge.broadcom.com/external/article/392879 for steps to resolve.

The correct procedure to remove NSX from a single host:

 Uninstall NSX Data Center from a Managed Host in a vSphere Cluster