releaseSiteDeviceDhcpLease
Releases an active DHCP lease.
Preferred authentication method for automation and integrations. Send the API token in the HTTP Authorization header.
Format:
Authorization: Token {apitoken}
Notes:
- An API token generated for a specific admin has the same privileges as that admin
- An API token is automatically removed if it is not used for more than 90 days
- SSO admins cannot generate admin API tokens. Use organization API tokens when scoped Org/Site privileges are needed.
In: header
Path Parameters
uuiduuidRequest Body
application/json
Note:
- valid combinations for Junos:
port_idmacs+network
- valid combinations for SSR:
port_idmacs+networkport_id+networknetwork
- if network or port_id is specified and macs is empty, it means all clients under network or port_id
Client MAC addresses whose DHCP leases should be released
DHCP network containing the leases to release
HA cluster node on which to release DHCP leases. enum: node0, node1.
Value in
- "node0"
- "node1"
Network interface containing the DHCP leases to release
1 <= lengthResponse Body
curl -X POST "https://example.com/api/v1/sites/000000ab-00ab-00ab-00ab-0000000000ab/devices/000000ab-00ab-00ab-00ab-0000000000ab/release_dhcp_leases" \ -H "Content-Type: application/json" \ -d '{ "port_id": "ge-0/0/1.10" }'readoptSiteOctermDevice POST
For the octerm devices, the device ID must come from fpc0. However, for a VC, the users may change the original fpc0 from CLI. To fix the issue, the readopt API could be used to trigger the readopt process so the device would get the correct device ID to connect the cloud.
readoptSiteOctermDevice POST
To force one device to reprovision itself again.