Error 609680 when updating Transport Node Profile in VMware NSX

Products

• VMware SDDC Manager / VCF Installer
• VMware NSX

Issue/Introduction

When attempting to change the default Transport Node Profile (TNP) for a cluster in a VMware Cloud Foundation (VCF) 9.x environment following a Workload Domain import, the operation fails with the following error in the NSX Manager UI:

Error: HostSwitchMode update on Transport node profile ... is disallowed on cluster ... to avoid HostSwitchMode updates. Make HostSwitchMode changes on each Transport Node within the cluster before updating it in TransportNodeProfile. (Error code: 609680)

This issue typically occurs in 'brownfield' import scenarios where the new NSX deployment associates a default TNP that does not match the desired final configuration, particularly regarding the number of defined uplinks.

Environment

• VMware Cloud Foundation 9.x
• VMware NSX 4.x / 9.x
• Brownfield vCenter Import

Cause

NSX prevents the application of a Transport Node Profile if the target profile's Host Switch configuration (such as the number of uplinks) differs from the current configuration realized on the individual transport nodes. For example, if the active configuration has 4 uplinks defined but the new TNP only defines 2, the realization fails to avoid datapath disruption.

Resolution

Align the individual host transport node (HTN) configurations with the target Transport Node Profile requirements before reapplying the profile to the cluster.

1. Identify the discrepancy between the current host configuration and the target TNP (e.g., number of uplinks or HostSwitchMode).
2. Navigate to System > Fabric > Nodes > Host Transport Nodes.
3. For each host in the affected cluster, manually update the network configuration to match the specifications of the new TNP.
4. Once the host-level configurations are aligned, re-attempt to associate the new Transport Node Profile with the cluster.
5. Monitor the realization status to ensure all nodes reach a Success state.

 

Workaround: Remove and Re-add NSX Configuration

This is the most efficient method when changing core topology (like reducing uplink counts) during a brownfield import.

1. Log in to the NSX Manager UI.
2. Navigate to System > Fabric > Nodes > Host Transport Nodes.
3. Select the affected Cluster.
4. Click Actions and select Remove NSX.
   • Note: Ensure you have a maintenance window as this will impact networking for VMs on those hosts unless they are moved first.
5. Once NSX is removed and the hosts show as 'Not Configured',
6. Select the cluster again and click Configure NSX.
7. Select the target Transport Node Profile (with the 2 uplinks) and click Save.

Additional Information

For software downloads and updates, refer to  Broadcom Support Downloads.

If the issue persists, contact Broadcom Support. To speak with a customer representative or a Support Engineer, see Contact Broadcom support.

For defects and enhancements, subscribe to this article to be updated on fix status. See Subscribe to a Broadcom knowledge article by article or product