From vSphere the DVPGs already have an active LAG configured.
From the SDDC Logs you see the correct LAG configuration: /var/log/vmware/vcf/domainmanager/domainmanager.log
======================================================================================
2026-05-07T13:52:24.293+0000 INFO [vcf_dm,69fc991817e942348ab9651dc5b15c4b,765e] [c.v.e.s.c.c.v.vsphere.VcManagerBase,dm-exec-5] Setting uplink teaming policy as failover_explicit for portgroup ##-##-###-##, Active uplinks: ["uplink1","uplink2"], Standby Uplinks: []
2026-05-07T13:52:26.320+0000 INFO [vcf_dm,69fc991817e942348ab9651dc5b15c4b,765e] [c.v.v.c.c.f.a.i.BaseCreatePortGroupAction,dm-exec-5] Created portgroup ##-##-###-##, for moid dvportgroup-28
2026-05-07T13:52:26.443+0000 INFO [vcf_dm,69fc991817e942348ab9651dc5b15c4b,765e] [c.v.e.s.c.c.v.vsphere.VcManagerBase,dm-exec-5] Setting uplink teaming policy as failover_explicit for portgroup ##-##-###-##, Active uplinks: ["uplink1","uplink2"], Standby Uplinks: []
2026-05-07T13:52:28.470+0000 INFO [vcf_dm,69fc991817e942348ab9651dc5b15c4b,765e] [c.v.v.c.c.f.a.i.BaseCreatePortGroupAction,dm-exec-5] Created portgroup ##-##-###-##, for moid dvportgroup-29
A similar error is observed in the SDDC Manager domainmanager.log /var/log/vmware/vcf/domainmanager/domainmanager.log======================================================================================2026-05-14T15:44:43.955+0000 DEBUG [vcf_dm,6a05d8845f34376506cb3f6925503ac8,263a] [c.v.v.c.f.p.n.p.s.i.PolicyTransportNodeCollectionServiceImpl,dm-exec-3] Current state of cluster preparation IN_PROGRESS2026-05-14T15:44:43.955+0000 DEBUG [vcf_dm,6a05d8845f34376506cb3f6925503ac8,263a] [c.v.v.c.f.p.n.p.s.i.PolicyTransportNodeCollectionServiceImpl,dm-exec-3] NSX validation error(s): null2026-05-14T15:44:43.955+0000 DEBUG [vcf_dm,6a05d8845f34376506cb3f6925503ac8,263a] [c.v.v.c.f.p.n.h.NsxtCommonOperations,dm-exec-3] Timeout waiting for NSX cluster prepartion to be completed2026-05-14T15:44:43.956+0000 ERROR [vcf_dm,6a05d8845f34376506cb3f6925503ac8,263a] [c.v.v.c.f.p.n.p.a.TransportNodeCollectionResolver,dm-exec-3] Error occurred while resolving Transport Node Collection Errors on attempt 2 with exceptioncom.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Unable to create transport node collection with profile ########-####-####-####-######## on compute collection ##-### through nsxmanager ###-###-###.###.###
VMware Cloud Foundation 9.x
An error was occurred during the bringup which caused NSX to incorrectly parse through the LAG configuration.
Please open a support request with VMware Support