statement at the [edit routing-instances routing-instance-name system services
dhcp-local-server] hierarchy level.
•
Alternatively, to enable dynamic reconfiguration for only the DHCP clients serviced by
a specified group of interfaces, include the reconfigure statement at the [edit system
services dhcp-local-server group group-name] hierarchy level for DHCPv4 clients. In a
routing instance, include the reconfigure statement at the [edit routing-instances
routing-instance-name system services dhcp-local-server group group-name] hierarchy
level
You can optionally modify the behavior of the reconfiguration process by including the
appropriate statements at the [edit system services dhcp-local-server reconfigure]
hierarchy level for all DHCPv4 clients. To override this global configuration for only the
DHCP clients serviced by a specified group of interfaces, you can include the statements
with different values at the [edit system services dhcp-local-server group group-name
reconfigure] hierarchy level for DHCPv4 clients.
In a routing instance, you can optionally modify the behavior of the reconfiguration process
by including the appropriate statements at the [edit routing-instances
<routing-instance-name> system services dhcp-local-server reconfigure] hierarchy level
for all DHCPv4 clients. To override this global configuration for only the DHCP clients
serviced by a specified group of interfaces, you can include the statements with different
values at the [edit routing-instances <routing-instance-name> system services
dhcp-local-server group group-name reconfigure] hierarchy level for DHCPv4 clients.
Include the attempts statement to specify how many times the local server sends the
forcerenew or reconfigure message to initiate client reconfiguration. Include the timeout
statement to set the interval between the first and second attempts. The interval between
each subsequent attempt doubles the previous value. For example, if the first value is 2,
the first retry is attempted 2 seconds after the first attempt fails. The second retry is
attempted 4 seconds after the first retry fails. The third retry is attempted 8 seconds
after the second retry fails, and so on.
By default, the DHCP client’s original configuration is restored if all of the reconfiguration
attempts fail. Include the clear-on-abort statement to delete the client instead.
You can force the local server to initiate the reconfiguration process for clients by issuing
the request dhcp server reconfigure command for DHCPv4 clients. Command options
determine whether reconfiguration is then attempted for all clients or specified clients.
Events that take place while a reconfiguration is in process take precedence over the
reconfiguration. Table 39 on page 343 lists the actions taken in response to several different
events.
Table 39: Action Taken for Events That Occur During a Reconfiguration
ActionEvent
Server drops packet and deletes client.Server receives a discover message from the client.
DHCPv4—Server sends NAK message and
deletes client.
Server receives a request, renew, rebind, or init-reboot
message from the client.
343Copyright © 2017, Juniper Networks, Inc.
Chapter 10: Configuring DHCP Client and DHCP Server