VMs can not connect to NSX ports after ESXi reboot

Products

• VMware NSX

Issue/Introduction

• VMs connected to NSX segments lost network connectivity after ESXi was booted and VMs were powered on.
• The VMs stayed on the ESXi when it shut down.
• You can not manually connect the vNICs.
• vNICs connected to non-NSX portgroups are connected.
• You find the following messages that indicates some ports were not loaded on boot.
  

  hostd log
  <Timestamp> info hostd[2100341] [Originator@6876 sub=Vmsvc.vm:<vmx path>] Failure in LoadDVPorts : Fault cause: vim.fault.PlatformConfigFault

  vmkernel log
  <Timestamp> cpu0:2100341)WARNING: NetDVS: 10004: Set connectee <UUID> for port <UUID> error Busy
<Timestamp> cpu0:2100341)WARNING: NetDVS: 1855: Set connectee(swID <DVS UUID> port <UUID>) with error Busy

Environment

VMware NSX-T 3.x

ESXi 7.0

Cause

Due to a race condition, ESXi fails to load NSX ports on boot.

Resolution

The race condition is resolved in ESXi 8.0.

To prevent the issue in ESXi 7.0, migrate VMs to other hosts when rebooting ESXi.

If the port is removed, connect the vNIC to another portgroup and connect it back to the original NSX segment.