Multiple definitions are found for the named teaming policies: [<TeamingPolicy1>, <TeamingPolicy2>, <TeamingPolicy3>, <TeamingPolicy4>] specified on the VLAN transport zone: nsx-vlan-transportzone across the uplink profiles:
Log snippets:
YYYY-MM-DDTHH:MM:SS:MSZ.755+0000 DEBUG [vcf_dm] [c.v.v.c.f.p.n.h.NsxtNamedTeamingUtil,dm-exec-1] Names of named teaming policies extracted from uplink profiles are: [<TeamingPolicy1>, <TeamingPolicy2>, <TeamingPolicy3>, <TeamingPolicy4>, <TeamingPolicy1>, <TeamingPolicy2>, <TeamingPolicy3>, <TeamingPolicy4>, <TeamingPolicy1>, <TeamingPolicy2>, <TeamingPolicy3>, <TeamingPolicy4>, <TeamingPolicy1>, <TeamingPolicy2>, <TeamingPolicy3>, <TeamingPolicy4>]
YYYY-MM-DDTHH:MM:SS:MSZ.756+0000 DEBUG [vcf_dm,] [c.v.v.c.f.p.n.h.NsxtNamedTeamingUtil,dm-exec-1] Names of duplicate named teaming policy found are: [<TeamingPolicy1>, <TeamingPolicy2>, <TeamingPolicy3>, <TeamingPolicy4>]
YYYY-MM-DDTHH:MM:SS:MSZ.756+0000 DEBUG [vcf_dm,] [c.v.v.c.n.s.c.c.ApiConnection,dm-exec-1] Closed ApiClient connection.
YYYY-MM-DDTHH:MM:SS:MSZ.761+0000 ERROR [vcf_dm,] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-1] [30HB6] NAMED_TEAMING_POLICIES_WITH_SAME_NAME_BUT_MULTIPLE_DEFINITIONS Multiple definitions are found for the named teaming policies: [<TeamingPolicy1>, <TeamingPolicy2>, <TeamingPolicy3>, <TeamingPolicy4>] specified on the VLAN transport zone: nsx-vlan-transportzone across the uplink profiles:
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Multiple definitions are found for the named teaming policies: [<TeamingPolicy1>, <TeamingPolicy2>, <TeamingPolicy3>, <TeamingPolicy4>] specified on the VLAN transport zone: nsx-vlan-transportzone across the uplink profiles:
at com.vmware.vcf.common.fsm.plugins.nsxt.helpers.NsxtNamedTeamingUtil.removeDuplicateNamedTeamingPolicies(NsxtNamedTeamingUtil.java:631)
In the above log snippet, the following policies are causing the conflict as the Uplink Profile used by a Transport Node (Host or Edge) contains named teaming policies that are duplicated
There are 2 resolution options, depending on the VCF Version deployed:
Identify the Misconfiguration:
The named teaming policies in the Uplink Profile must precisely match the names, active, and standby uplink definitions mapped in the VLAN Transport Zone.
Edit the Uplink Profile:
Go to System > Fabric > Profiles > Uplink Profiles.
Find the profile used by your Transport Nodes.
Review the Named Teaming Policies section.
Resolve Duplication:
Remove or rename the duplicate entries [<TeamingPolicy1>, <TeamingPolicy2>, <TeamingPolicy3>, <TeamingPolicy4>].
Ensure each policy name is unique within the profile.
Verify VLAN Transport Zone Mapping:
Check the VLAN Transport Zone and ensure these specific policies (<TeamingPolicy1>, <TeamingPolicy2>, etc.) are correctly mapped to physical NICs (e.g., pNIC1, pNIC2).
Re-apply Configuration:
Save the updated Uplink Profile.
If you are using a Transport Node Profile (TNP), re-apply it to the cluster to clear the validation error.
Verify the Uplink Profile Exists in NSX. Before kicking off the Add Cluster workflow, make sure the uplink profile you plan to use is already set up in NSX Manager.
Log in to NSX Manager with an admin account.
Go to System → Fabric → Profiles → Uplink Profiles.
Find the uplink profile you intend to use and confirm the following:
The profile name is exactly what you'll enter in the cluster spec (names are case-sensitive).
The uplink count matches the NIC count on the new cluster's hosts.
The named teaming policy definitions cover all required network functions (e.g., DMZ, BACKUP).
The teaming policy (active/standby uplinks and policy type) aligns with the physical NIC layout of the hosts.
Copy the exact display name of the uplink profile — you'll need it in the next step.
Don't have an uplink profile yet? Create one first. Go to System → Fabric → Profiles → Uplink Profiles → Add Profile, configure the appropriate teaming policies and uplink count for your hosts, save it, and then use that name in the cluster creation
Specify the Uplink Profile in the Add Cluster Workflow
Option A: Via SDDC Manager UI
In SDDC Manager, go to Inventory → Workload Domains, select the target domain, and click Add Cluster.
Fill in the cluster configuration (hosts, vSphere settings, etc.) and navigate to the NSX Network Configuration section.
In the NSX Host Switch / Uplink Profile field, enter or select the exact name of the uplink profile from Step 1.
This field maps to nsxTHostSwitchConfigs → uplinkProfile → name in the API payload. Use the dropdown if available, or paste the exact name into the free-text field.
Finish the remaining configuration and submit.
Submit the Workflow and Confirm Success
Submit the Add Cluster workflow.
In SDDC Manager, monitor progress under Administration → Workflow Management (or the task panel in the domain view). Watch for the "Generate NSX Input Data" task — this is the step that previously failed with the multi-definition error. If it completes successfully, the bypass is working as expected.
Let the workflow run to completion and watch for these key tasks:
"Create NSX Uplink Host Switch Profile" — should confirm the existing profile was found and reused by ID (no new profile created).
"Create Transport Node Profile" — should complete successfully, referencing the reused profile's ID.
Once the workflow finishes, verify the following:
The cluster appears in SDDC Manager with a Healthy status.
In NSX Manager under System → Fabric → Profiles → Uplink Profiles, the original profile is intact and unchanged.
Under System → Fabric → Profiles → Transport Node Profiles, the new cluster's TNP references the correct uplink profile.
All hosts show realization status: Success under System → Fabric → Nodes → Host Transport Nodes.
Alternative Path: Out-of-Band Profile Creation After a Failed Attempt
If the cluster creation has already failed with the multi-definition error and the uplink profile doesn't exist yet, you can still recover without modifying the cluster spec:
From the failure details in SDDC Manager, note the auto-generated uplink profile name.
For example: vcenter-1-NewCluster-SDDC-Dswitch-Private.
Why this approach works well: Since you created the uplink profile manually with the correct settings, the new cluster's Transport Node Profile immediately references the intended policies — no follow-up edits in NSX required.