T-1 gateway missing from the Edge Node

Products

• VMware NSX

Issue/Introduction

• T-1 gateway is missing from the one of the edges:
  
  
  
  
• On the Tier-1 gateway under Networking, clicking on HA mode would show that edge missing:
  
  
  
  
• Switching Edge cluster from Auto-Allocate to Manual Allocation and making the missing edge primary, the realization fails with java.lang.NullPointerException in the UI:
  
  
  
  
• Running the API command: GET https://<nsx-manager-ip>/api/v1/edge-cluster shows the member index of the edges:
  
  "members": [
          {
            "display_name": "EDGE02",
            "member_index": 1,     
            "transport_node_id": "0660####-####-####-####-####c0ed5d46"
          },
          {
            "display_name": "EDGE01",
            "member_index": 2,
            "transport_node_id": "c7df####-####-####-####-####5fcf1e6"
  
  
• However, the Logical Router shows different allocated edge cluster member indices such 0 and 1 using the API command GET https://<nsx-manager-ip>/api/v1/logical-routers/#####-T1:

display_name": "#####-T1",
        "edge_cluster_id": "22b1####-####-####-####-####7e60910",
        "edge_cluster_member_indices": [
          0,
          1       
        ],

which means that there is a stale ResourceAllocation object attached to the Tier-1 Logical Router, which needs to be removed.

Environment

VMware NSX-T 3.2.x
VMware NSX 4.x.x

Cause

Tier-1 gateway is allocated on an edge which was deleted and realization is failing while relocating it to a different edge.

Resolution

The issue will be resolved in VCF 9.1.

Workaround:

If you believe you have encountered this issue, please open a support case with Broadcom Support and refer to this KB article.

For more information, see Creating and managing Broadcom support cases.