After ESXi host upgrade vMotion is blocked due to error: "Currently connected network interface uses Network .. NSX port group ..(nsxa down), which is not accessible"

Products

• VMware NSX

Issue/Introduction

• vMotion of virtual machines from NSX backed port groups and distributed switch port groups is blocked after ESXi host upgrade.
• vMotion of virtual machines is blocked with error:
  "Currently connected network interface" 'Network adapter X' uses network 'DVSwitch[50 3e ## ## ## ## ## ##-## ## ## ## ## ## 42 4e] NSX port group [dvportgroup-#####](nsxa down)', which is not accessible."
• Compatibility alert observed when migrating virtual machines on NSX managed port group:

Environment

VMware NSX

VMware NSX-T Data Center

Cause

This issue can occur if there is a version mismatch between ESXi host and the version of ESXi on NSX.

Resolution

First verify that the ESXi host version has been successfully updated with the NSX VIBs.

• Hosts with a version mismatch will also report host preparation failures on the NSX Manager UI.
• Example:
  
  • Node has invalid version 4.1.1.0.0-7.0.22224315 of software nsx-monitoring
    
• Here the host was upgraded to 8.0 version but the VIBs still showed ESXi host version 7.0

If there's a version discrepancy between the ESXi host and the NSX VIBs, kindly follow the following kb article to resolve the issue: Error: "Node has invalid version <vib version> of <vib name>"

Additional Information

If the underlying cause does not match the cause provided on this kb then kindly refer the following kb article to further troubleshoot the issue: vMotion is blocked due to error "Currently connected network interface ... uses network (nsxa down), which is not accessible"