VM port blocked state on NSX segment prevents connectivity

Products

• VMware NSX

Issue/Introduction

A virtual machine appears in a blocked state on an NSX segment port. The affected VM cannot establish network connectivity despite being configured identically to other functional VMs on the same segment. The VM shows as connected to the NSX segment in vCenter.

Error messages may include:

• Port showing as "blocked" status in ESXi diagnostics.
• NSX Controllers and Manager were connected, and NESTdb service was up.
• Network connectivity failures from the affected VM.
• Virtual machines may have issues with their IP allocation with DHCP 

 

Below error message is seen on NSX Manager UI in NSX Configuration Status:

NSX Install Failed.

         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

 

While attempting to migrate a virtual machine (VM) to a host configured with NSX, the following error may be observed during the "Select Networks" step:

Currently connected network interface 'Network adapter 1' uses network 'DVSwitch[...] NSX port group (dvportgroup-XXX)(vdz is down)', which is not accessible.

Additional observations:

• Host appears under NSX Manager as "Install upgrade”.  

Environment

VMware NSX

Cause

This issue occurs because the host is not fully configured with NSX and cannot access or present the NSX-backed segment (port group).

Resolution

Verify if the node has invalid version  software VIB install. For more information, see  Using VLCM to upgrade vSphere and NSX it fails with "Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-monitoring..."

Verify if the hosts appears under NSX Manager as "install Failed". For more information, see   VM Migration Fails with "Network Not Accessible" Error Due to NSX Segment Inaccessibility on Partially Configured Host

 

Additional Information

Please review and verify you are not on JDK affected versions