NSX-T Data Center REST API
Reallocate edge cluster and members of given DHCP profile. (Deprecated)
As changing edge-cluster-id of a DhcpProfile by a PUT is disallowed,this re-allocate API is used to modify the edge-cluster-id and members
of a given DhcpProfile.
Only the edge-cluster-id and the edge-cluster-member-indexes fields will
be picked up by this re-allication API. The othere fields in the payload
will be ignored.
If the edge-cluster-id in the payload DhcpProfile is different from the
current edge-cluster-id of the profile, the referencing DHCP server(s) will
be re-allocated to the new edge cluster. If the edge-cluster-id is not
changed, the referencing DHCP server(s) will be re-allocated to the
given edge members in the edge cluster. In this case, this REST API will
act same as that of updating a DhcpProfile.
If the edge cluster member indexes are provided, they should exist in the
given edge cluster. If the indexes are not specified in the DhcpProfile,
edge members will be auto-allocated from the given edge cluster.
Please note that re-allocating edge-cluster will cause lose of all exisitng
DHCP lease information. This API is used only when loosing DHCP leases is
not a real problem, e.g. cross-site migration or failover and all client
hosts will be reboot and get new IP addresses.
Request:
Method:
POST
URI Path(s):
/api/v1/dhcp/server-profiles/{server-profile-id}?action=reallocate
Request Headers:
n/a
Query Parameters:
n/a
Request Body:
DhcpProfile+
Example Request:
{ "edge_cluster_id" : "0748d3ce-2bdc-40ba-90d2-639a7dfe6cfe", "edge_cluster_member_indexes" : [0, 1] }Successful Response:
Response Code:
200 OK
Response Headers:
Content-type: application/json
Response Body:
DhcpProfile+