delete-binding-on-renegotiation (DHCP Local Server and Relay Agent)
Syntax
delete-binding-on-renegotiation;
Hierarchy Level
[edit forwarding-options dhcp-relay overrides], [edit forwarding-options dhcp-relay dhcpv6 overrides], [edit forwarding-options dhcp-relay group group-name overrides], [edit forwarding-options dhcp-relay dhcpv6 group group-name overrides], [edit logical-systems logical-system-name ...], [edit logical-systems logical-system-name routing-instances routing-instance-name...], [edit routing-instances routing-instance-name ...], [edit system services dhcp-local-server overrides], [edit system services dhcp-local-server dhcpv6 overrides], [edit system services dhcp-local-server group group-name overrides], [edit system services dhcp-local-server dhcpv6 group group-name overrides]
Description
Configure DHCP to override the default behavior when the local server or relay agent receives a DHCPv4 Discover or DHCPv6 Solicit message while in a bound state. In this case, DHCP drops the message and it is not processed. On a DHCP relay agent, the agent sends a Release message to the local server. DHCP cleans up the existing session and deletes the existing client entry, removing the binding. When a second Discover or Solicit message is received from the client, the message is processed and DHCP negotiation proceeds.
A consequence of the override behavior is that the time to complete a DHCP negotiation is prolonged if the client begins negotiation before the existing client entry is expired. The delay can be up to several seconds.
The default behavior (this statement is not configured) is that DHCP maintains the client entry if it receives a Discover or Solicit message that has a client ID that matches the existing client. DHCP then processes the new message using the existing client entry and responds to the client with an Offer or Advertise message.
In releases earlier than Junos OS Release 15.1, the default behavior for DHCPv6 local server and relay agent is the same as the override behavior in Junos OS Release 15.1 and later. For any release, the default behavior for DHCPv4 local server and relay agent is to maintain the existing client entry and respond without waiting for a second Discover or Solicit message.
Required Privilege Level
system—To view this statement in the configuration.
system-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 15.1.