System Administration > Configuration > Fabric > Edge Clusters > Edge Clusters

Relocate service contexts from edge and remove edge node from the edge-cluster

Relocate auto allocated service contexts from edge node at given index.
For API to perform relocate and remove action the edge node at given index must only have auto allocated service contexts.
If any manually allocated service context is present on the edge cluster member, then the task will not be performed.
Also, it is recommended to move edge node for which relocate and remove action is being performed into maintenance mode,
before executing the API. If edge is not not moved into maintenance mode, then API will move edge node into maintenance
mode before performing the actual relocate and remove task.To maintain high availability, Edge cluster should have at
least two healthy edge nodes for relocate and removal.
Once relocate action is performed successfully, the edge node will be removed from the edge cluster.

Request:

Method:
POST
URI Path(s):
/api/v1/edge-clusters/{edge-cluster-id}?action=relocate_and_remove
Request Headers:
n/a
Query Parameters:
n/a
Request Body:
EdgeClusterMemberIndex+

Example Request:

POST https://<nsx-mgr>/api/v1/edge-clusters/bf8d4daf-93f6-4c23-af38-63f6d372e14e?action=replace_transport_node { "member_index": 0 }

Successful Response:

Response Code:
200 OK
Response Headers:
n/a
Response Body:
n/a

Required Permissions:

crud

Feature:

nodes_edge_clusters

Additional Errors: