update_device_dhcp_server
Modify an existing DHCP server scope on a managed FortiManager device by scope ID, changing only specified fields and requiring start and end IPs together for lease range changes.
Instructions
Update a device-DB DHCP server scope by id. Only provided fields change.
The lease range is replaced as a whole, so start_ip and end_ip must be given together.
Args: device: Managed device name dhcp_server_id: Numeric scope id (see list_device_dhcp_servers) start_ip: New first address of the lease range end_ip: New last address of the lease range netmask: New scope netmask default_gateway: New gateway handed to clients dns_servers: Up to three DNS servers; replaces the served set lease_time: New lease time in seconds vdom: VDOM the scope lives in (default "root")
Returns: Update result
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"device": "<device>",
"dhcp_server_id": "<dhcp_server_id>"
},
"name": "update_device_dhcp_server"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| vdom | No | root | |
| device | Yes | ||
| end_ip | No | ||
| netmask | No | ||
| start_ip | No | ||
| lease_time | No | ||
| dns_servers | No | ||
| dhcp_server_id | Yes | ||
| default_gateway | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||