NSX Host Status Degraded with "teaming uplink unknown" after VDS Migration

Products

• VMware NSX

Issue/Introduction

After migrating an ESXi host to a new vSphere Distributed Switch (VDS), the host transport node status in NSX Manager displays as "Degraded".

While physical NICs (vmnics) appear "Up" in the vSphere Client, the NSX Monitor tab shows a "Down" bond status. 

Logs in ESXi host /var/run/log/nsx-syslog.log will show:

[Heatmap][GetSwitchPnicBondsStatus] get DvsPortset-1 (vswitch:true) pnic message
[Heatmap][KCPGetPSTeam] Got 2 uplinks and 0 LAGs
[Heatmap][KCPGetPSTeam] 2 pnics 0 lags
[Heatmap][GetNSXTeamingMap] <VDS_name> team has 2 ports
[Heatmap][GetNSXTeamingMap] teaming 0 uplink1
[Heatmap][GetNSXTeamingMap] teaming 1 uplink2
[Heatmap][GetSwitchPnicBondsStatus] Got pnic vmnic1 state up
[Heatmap][GetSwitchPnicBondsStatus] Got pnic vmnic2 state up
[Heatmap][GetSwitchPnicBondsStatus] teaming uplink1 unknown
[Heatmap][GetSwitchPnicBondsStatus] teaming uplink2 unknown
[Heatmap][GetSwitchPnicBondsStatus] teaming down

Environment

VMware NSX

Cause

The issue is caused by an inconsistent or stale mapping between the new VDS portset and the NSX Transport Node teaming profile. When the host is moved to a new VDS, the NSX management agents on the ESXi host may fail to correctly associate the new physical uplinks with the existing teaming policy, resulting in an "unknown" status for the bond.

Resolution

To resolve the stale mapping, the NSX configuration must be detached and the management services restarted before re-associating the host with the VDS.

1. 1. 1. Evacuate VMs: Move all running virtual machines from the affected ESXi host using vMotion.
      2. Detach VDS in NSX:
         • Log in to NSX Manager.
         • Navigate to System > Fabric > Hosts.
         • Select the affected host and click Configure NSX.
         • Remove the VDS configuration from the NSX transport node settings.
      3. Remove Host from VDS in vCenter:
         • Log in to the vSphere Client.
         • Navigate to Networking, select the VDS, and remove the ESXi host from the switch.
      4. Restart NSX Services:
         • Log in to the ESXi host via SSH as root.
         • Run the following commands to restart the management agents:
         • /etc/init.d/nsx-opsagent restart
/etc/init.d/nsx-proxy restart
            
      5. Re-add to VDS: In the vSphere Client, add the ESXi host back to the VDS and map the physical vmnics to the correct uplinks.
      6. Re-configure NSX:
         • Return to NSX Manager (System > Fabric > Hosts).
         • Select the host and click Configure NSX.
         • Re-add the VDS to the NSX configuration using the appropriate Transport Node Profile or manual settings.