interface (DHCP Relay Agent)
Syntax
interface dhcp-interface-name {
access-profile profile-name;
exclude;
overrides {
allow-no-end-option
allow-snooped-clients;
always-write-giaddr;
always-write-option-82;
asymmetric-lease-time seconds;
asymmetric-prefix-lease-time seconds;
client-discover-match <option60-and-option82 | incoming-interface>;
client-negotiation-match incoming-interface;
disable-relay;
dual-stack dual-stack-group-name;
interface-client-limit number;
layer2-unicast-replies;
no-allow-snooped-clients;
proxy-mode;
relay-source
replace-ip-source-with;
send-release-on-delete;
trust-option-82;
}
service-profile dynamic-profile-name;
short-cycle-protection <lockout-min-time seconds> <lockout-max-time seconds>;
trace;
upto upto-interface-name;
}
Hierarchy Level
[edit forwarding-options dhcp-relay dhcpv6 group group-name], [edit forwarding-options dhcp-relay group group-name], [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 ...]
Description
Enabling tracing can adversely impact scale and performance and may increase security risk. We strongly recommend using the trace, tracing, or traceoptions commands only under the guidance of a JTAC support engineer. After collecting the debug information, immediately disable tracing to minimize risk and restore normal system performance.
Specify one or more interfaces, or a range of interfaces,
that are within a specified group on which the DHCP or DHCPv6 relay
agent is enabled. You can repeat the interface interface-name statement to specify multiple interfaces within a group, but
you cannot specify the same interface in more than one group. Also,
you cannot use an interface that is being used by the DHCP local server.
Use the statement at the [edit ... dhcpv6] hierarchy levels
to configure DHCPv6 support.
EX Series switches do not support DHCPv6.
DHCP values are supported in integrated routing and bridging (IRB) configurations. When you configure an IRB interface in a network that is using DHCP, the DHCP information (for example, authentication, address assignment, and so on) is propagated in the associated bridge domain. This enables the DHCP server to configure client IP addresses residing within the bridge domain. IRB currently only supports static DHCP configurations. .
Options
exclude—Exclude an interface
or a range of interfaces from the group. This option and the overrides option are mutually exclusive.
interface-name—Name of
the interface. You can repeat this option multiple times.
overrides—Override the specified default configuration
settings for the interface. The overrides statement is described
separately.
upto-interface-name—Upper
end of the range of interfaces; the lower end of the range is the
interface-name entry. The interface device name of the upto-interface-name must be the same as the device
name of the interface-name.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details.
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 8.3.
Options upto and exclude introduced in
Junos OS Release 9.1.
Support at the [edit ... dhcpv6] hierarchy levels
introduced in Junos OS Release 11.4.