After migrating an NSX Edge VM from one cluster and vSphere Distributed Switch (VDS) to another, a recurring failed task appears in the vSphere Client

Products

• VMware NSX

Issue/Introduction

• Failed task Name: Reconfigure Virtual Machine
  • Status: A specified parameter was not correct: spec.deviceChange.device.port.switchUuid Host <hostname> is not a member of VDS <vDS-Name>
• The host noted in the Status of the failed Task will reflect whichever host the edge VM is running on.
• The alarm may retrigger periodically (e.g., every 5 to 30 minutes).
• Rebooting the edge VM does not resolve the issue.
• Migrating the edge VM to different hosts in the new cluster does not resolve the issue.
• Changing the edge VM's network configuration to use portgroups on a standard switch and then changing back to the desired portgroups does not resolve the issue.
• Unregistering the edge VM from the vCenter inventory and re-registering it does not resolve the issue.
• The hosts in the new cluster are not members of the VDS to which the edge VM used to belong.
• This may not affect all edge VMs in the new cluster/VDS. Other edge VMs might migrate to the new cluster/VDS without issue.
• No alarms related to the edge's health are raised in the NSX UI and the status and tunnels are all healthy.

Environment

• VMware NSX 4.x / 3.x
• VMware vSphere 7.x / 8.x
• NSX Edge VMs being migrated between clusters and/or VDS instances.

Cause

The state of the Edge VM is not in sync with the NSX Manager. NSX is not aware that the Edge VM has been moved to a new cluster or VDS. Consequently, NSX attempts to push an invalid or outdated configuration change to vCenter (targeting the old VDS, of which the new hosts are not members).

Resolution

To resolve this issue, you must synchronize the Edge Node configuration to update NSX with the current VM location and network settings.

1. Log in to the NSX Manager UI.
2. Navigate to System > Fabric > Nodes > Edge Transport Nodes.
3. Select the affected Edge Node.
4. Click Actions and select Sync Node (or Sync Edge Node Configuration).
5. Monitor the vSphere Client to ensure the 'Reconfigure Virtual Machine' task now succeeds or is no longer initiated.
6. If the alarm persists, reboot the Edge VM to force a full refresh of the virtual hardware and network port assignments.