Can't vMotion VMs to a host after NSX VIBs are updated on an ESXi host outside of the NSX Upgrade workflow

Products

• VMware NSX

Issue/Introduction

• NSX VIBs were updated on ESXi hosts outside of the NSX Upgrade workflow.
• The newly updated VIBs are at a newer release version from the NSX Managers.
• DVS status is DOWN on hosts not receiving migrated VMs.
• NSX Manager var/log/proton/nsxapi logging reports messages like:

INFO L2HostConfigTaskExecutor1 TransportNodeAsyncServiceImpl ##### FABRIC [nsx@#### comp="nsx-manager" level="INFO" subcomp="manager"] TransportNode/########-####-####-####-############ setting NsxaDown true as fabric is down

• NSX Manager var/log/syslog logging reports messages like:

NSX ##### FABRIC [nsx@#### comp="nsx-manager" level="INFO" subcomp="manager"] Updated managed_resource {####  display_name: "hostname.example.com"####  intent_path: "/infra/sites/default/enforcement-points/default/host-transport-nodes/hostname.example.com"#####}#####transport_node_id {#####  string_id: "########-####-####-####-############"####}####host_id {####  value: "########-####-####-####-############"####}####transport_zone_id {####  left: #######################  right: #######################}###host_config_status: CONFIG_STATUS_PENDING###failure_message {###  value: "Waiting for fabric-node installation failure to be fixed: Software status file does not exists on the host ########-####-####-####-############. Verify that nsx-sfhc is running on host.

Cause

NSX Managers detect a version mismatch between the host Transport Node and the NSX Managers when this process is used.  This mismatch can lead to the host nsxa status set to DOWN and the DVS not allowing new connections.

 

Resolution

Follow the Upgrading NSX workflow to upgrade the Host Transport Nodes, Edge Transport Nodes, and NSX Managers.