duplicate-clients-in-subnet (DHCP Local Server and DHCP Relay Agent)
Syntax
duplicate-clients-in-subnet (incoming-interface | option-82);
Hierarchy Level
[edit forwarding-options dhcp-relay], [edit logical-systems logical-system-name forwarding-options dhcp-relay], [edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-options dhcp-relay], [edit routing-instances routing-instance-name forwarding-options dhcp-relay], [edit logical-systems logical-system-name routing-instances routing-instance-name system services dhcp-local-server], [edit logical-systems logical-system-name system services dhcp-local-server], [edit routing-instances routing-instance-name system services dhcp-local-server], [edit system services dhcp-local-server]
Description
Configure how the router distinguishes between duplicate clients in the same subnet. Duplicate clients are defined as clients that have the same hardware address or client ID.
You must configure the duplicate-clients-in-subnet statement identically for both the DHCP local server ([edit
forwarding-options dhcp-relay]) and the DHCP relay agent ([edit system services dhcp-local-server]).
Options
| incoming-interface | Use the incoming interface information in packets to differentiate between duplicate clients. |
| option-82 | Use the option 82 information to differentiate between duplicate clients. Starting in Junos OS Release 16.1R5, 16.2R2, 17.1R2, and 17.2R1, only the ACI (suboption 1) and ARI (suboption 2) are used. Other suboptions, such as Vendor-Specific (suboption 9) are ignored. |
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 13.3.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.