• DHCP Auto Logout Overview on page 333
• Configuring Address-Assignment Pools on page 318
• Configuring an Address-Assignment Pool Name and Addresses on page 319
• Configuring a Named Address Range for Dynamic Address Assignment on page 320
• Configuring Static Address Assignment on page 320
• Configuring DHCP Client-Specific Attributes on page 325
• DHCP Attributes for Address-Assignment Pools on page 321
• Configuring How the Extended DHCP Local Server Determines Which
Address-Assignment Pool to Use on page 322
• Guidelines for Configuring Interface Ranges on page 327
Guidelines for Configuring Interface Ranges
This topic describes guidelines to consider when configuring interface ranges for named
interface groups for a DHCP local server. The guidelines refer to the following configuration
statement:
user@host# set interface interface-name upto upto-interface-name
•
The start subunit, interface interface-name, serves as the key for the stanza. The
remaining configuration settings are considered attributes.
•
If the subunit is not included, an implicit .0 subunit is enforced. The implicit subunit is
applied to all interfaces when autoconfiguration is enabled. For example, interface
ge-2/2/2 is treated as interface ge-2/2/2.0.
•
Ranged entries contain the upto option, and the configuration applies to all interfaces
within the specified range. The start of a ranged entry must be less than the end of the
range. Discrete entries apply to a single interface, except in the case of
autoconfiguration, in which a 0 (zero) subunit acts as a wildcard.
•
Interface stanzas defined within the same router context are dependent and can
constrain each other—both DHCP local server and DHCP relay are considered. Interface
stanzas defined across different router contexts are independent and do not constrain
one another.
•
Each interface stanza, whether discrete or ranged, has a unique start subunit across a
given router context. For example, the following configuration is not allowed within
the same group because ge-1/0/0.10 is the start subunit for both.
interface ge-1/0/0.10 upto ge-1/0/0.30
interface ge-1/0/0.10
•
Two groups cannot share interface space. For example, the following configuration is
not allowed because the three stanzas share the same space and interfere with one
another—interface ge-1/0/0.26 is common to all three.
dhcp-relay group diamond interface ge-1/0/0.10 upto ge-1/0/0.30
dhcp-local-server group ruby interface ge-1/0/0.26
327Copyright © 2017, Juniper Networks, Inc.
Chapter 10: Configuring DHCP Client and DHCP Server