The problem was indeed solved by configuring the neighbors in the underlying BGP network. We discovered this problem because we created a new Edge Cluster using the static protocol and saw that it was created without any problems. We then reviewed the failed tasks, retried (leaving the neighbors correctly configured), and the edge cluster was set to "ACTIVE."
Regards.
-------------------------------------------
Mensaje original:
Enviado: Jun 27, 2025 04:00 PM
De: Shen88
Sujeto: Edge cluster in "Activating" state
@Guillermo Argañaras,
I've come across this, failing at this subtask suggests that SDDC Manager couldn't associate the VLAN-backed transport zone with the cluster, even though NSX-T completed its part. Most likely, NSX-T Manager may have created the segments, but SDDC Manager's internal inventory might be out of sync or could be the Edge nodes were partially configured or failed mid-deployment, they may not have completed the activation handshake. I had rebooted the edge nodes in my case and then re-run the task which completed the workflow successfully.
------------------------------
If you find this answer right, please 'Recommend' this post.
Thank you!
Regards,
Shen
Original Message:
Sent: May 28, 2025 04:43 PM
From: Guillermo Argañaras
Subject: Edge cluster in "Activating" state
Dear all, good afternoon.
Has this ever happened to you? My Edge Clusters are stuck in an "Activating" state. This happened after creating some AVNs for deploying Aria Suite. The AVNs for SDDC Manager failed in the task: "Deploying VLAN AVNs for default cluster of management domain" and subtask "Create VLAN transport zone - cluster association inventory." The strange thing is that in the NSX-T Manager, I see the created segments as OK.
thank you so much.
