- Running NSX Federation environment (4.1.0 or older versions)
- Onboarded multiple sites with similar prefixes such as "site2" and "site2_new"
- Configured Tier-0 gateway on "site2_new" on the Global manager UI
- Tried to stretch T0 gateway by adding another site "site2" on the Global manager UI
- When this configuration is saved, the T0 gateway does not reflect the change on the Global manager UI.
VMware NSX-T 3.x
VMware NSX 4.0.x
VMware NSX 4.1.0
When sites with similar IDs exist, pattern matching logic fails in the UI causing this issue.
The issue has been resolved in NSX 4.1.1 and later versions.
Workaround:
The customer can use the following API to stretch gateway by creating locale service:
PUT https://<gm-ip>/global-manager/api/v1/global-infra/tier-0s/<tier-0-id>/locale-services/<locale-service-id>
Payload:
{
"edge_cluster_path": "/global-infra/sites/<site-id>/enforcement-points/<enforcement-point-id>/edge-clusters/<edge-cluster-id>"
}