Unable to add Re-installed NSX Transport Node to vRNI NSGroup Due to Stale Entries.

Products

• VMware NSX

Issue/Introduction

A newly re-installed NSX transport node cannot be added to an existing vRealize Network Insight (vRNI) NSGroup. This failure is observed because stale host entries(old UUID) still present within that NSGroup.

Environment

VMware NSX

Cause

Persistence of stale host entries within the vRNI NSGroup. These entries correspond to the previous installation of the NSX transport node, and they were not automatically removed or updated upon re-installation. When attempting to add the re-installed transport node (which now has a new UUID), the NSGroup's configuration conflicts with these outdated records, preventing the successful addition of the re-installed ESXi host.

Resolution

To resolve this issue, the stale host entries must be manually removed from the vRNI NSGroup using the NSX API.

Retrieve the current NSGroup configuration:
Use an API GET request to fetch the existing configuration of the affected NSGroup.

GET /api/v1/ns-groups/{ns-group-id}

Copy
Note: Replace {ns-group-id} with the actual ID of the vRNI NSGroup. You can find this ID from NSX UI.
Edit the retrieved configuration:
In the JSON body returned by the GET request, locate the stale transport node entries. For each stale entry, ' is_valid: false' property is seen.
Remove the stale entries.
Submit the modified JSON body back to the NSGroup using an API PUT request.

PUT /api/v1/ns-groups/{ns-group-id}

Note: Ensure the full, modified JSON body (including all other unchanged parameters) is sent with the PUT request.