Tier-1 gateway not getting assigned as per failure domain preference

Products

• VMware NSX

Issue/Introduction

• Tier-1 gateway not getting assigned to preferred Edge node in Failure domain 
  
• When we run the get API call GET /api/v1/failure-domains/{failure-domain-id} we can see the  "preferred_active_edge_services" is set to True for 1 failure domain and False for another
  
  "results": [
        {
            "preferred_active_edge_services": true,
            "resource_type": "FailureDomain",
            "id": "<Edge_ID_1>",
            "display_name": "<Display_Name_Edge1>",
            "_create_time": 1634197403152,
            "_create_user": "admin",
            "_last_modified_time": 1703074258237,
            "_last_modified_user": "admin",
            "_system_owned": false,
            "_protection": "NOT_PROTECTED",
            "_revision": 4
        },
        {
            "preferred_active_edge_services": false,
            "resource_type": "FailureDomain",
            "id": "<Edge_ID_2>",
            "display_name": "<Display_Name_Edge2>",
            "_create_time": 1634197913105,
            "_create_user": "admin",
            "_last_modified_time": 1703074289221,
            "_last_modified_user": "admin",
            "_system_owned": false,
            "_protection": "NOT_PROTECTED",
            "_revision": 4
        },
  
  
  
• If we run the Get API call for the edge transport node GET api/v1/transport-nodes/<tn-id> we can see edge assigned to the non-preferred failure domain takes the active role

Environment

VMware NSX-T Datacenter 
VMware NSX 

Cause

• Tier-1 gateway was created before the failure domain was created or updated for the preferred active edge services.
• The creation time for failure domain can be verified with the API call GET /api/v1/failure-domains/{failure-domain-id}
• The creation time for the Tier-1 Gateway cane be verified with the API call GET /policy/api/v1/infra/tier-1s/<t1-id>
• This is an expected behavior and will be improved in upcoming release 

 

     Note: The time displayed would be in epoch

Resolution

Run the below API to reallocate edges on the Tier-1 Gateway 

POST https://{{nsx-manager-fqdn}}/api/v1/logical-routers/{{logical-router-id}}?action=reallocate

The request body should contain the following JSON: 

{
   "edge_cluster_id": "{{edge-cluster-id}}"
}

Logical-router-id and edge cluster-id can be found in NSX Manager UI