dhcp-relay
Syntax
dhcp-relay {
idle-timeout seconds;
peer-address address;
timeout seconds;
topology-discovery;
}
attempts number-of-attempts;
timeout seconds;
}
idle-timeout seconds;
peer-address address;
timeout seconds;
topology-discovery;
}
attempts number-of-attempts;
timeout seconds;
trigger automatic;
}
logical-system <current | default | logical-system-name>;
routing-instance <current | default | routing-instance-name>;
}
logical-system <current | default | logical-system-name>;
routing-instance <current | default | routing-instance-name>;
}
exclude;
upto upto-interface-name;
}
}
failure-action (clear-binding | clear-binding-if-interface-up | log-only);
max-consecutive-retries number;
transmit-interval interval;
}
}
}
equals (ascii
ascii-string | hexadecimal
hexadecimal-string) {
}
starts-with (ascii
ascii-string | hexadecimal
hexadecimal-string) {
}
}
}
attempts number-of-attempts;
timeout seconds;
}
failure-action (clear-binding | clear-binding-if-interface-up | log-only);
max-consecutive-retries number;
transmit-interval interval;
}
}
}
equals (ascii
ascii-string | hexadecimal
hexadecimal-string) {
}
starts-with (ascii
ascii-string | hexadecimal
hexadecimal-string) {
}
}
server-group-name {
server-ip-address;
}
}
}
circuit-id circuit-id;
mac-address mac-address;
remote-id remote-id;
}
failure-action (clear-binding | clear-binding-if-interface-up | log-only);
max-consecutive-retries number;
transmit-interval interval;
}
}
}
}
logical-system <current | default | logical-system-name>;
routing-instance <current | default | routing-instance-name>;
}
logical-system <current | default | logical-system-name>;
routing-instance <current | default | routing-instance-name>;
}
logical-system <current | default | logical-system-name>;
routing-instance <current | default | routing-instance-name>;
}
exclude;
failure-action (clear-binding | clear-binding-if-interface-up | log-only);
}
upto upto-interface-name;
}
equals (ascii
ascii-string | hexadecimal
hexadecimal-string) {
}
starts-with (ascii
ascii-string | hexadecimal
hexadecimal-string) {
}
}
}
attempts number-of-attempts;
timeout seconds;
}
failure-action (clear-binding | clear-binding-if-interface-up | log-only);
max-consecutive-retries number;
transmit-interval interval;
}
}
}
equals (ascii
ascii-string | hexadecimal
hexadecimal-string) {
}
starts-with (ascii
ascii-string | hexadecimal
hexadecimal-string) {
}
}
}
server-group-name {
server-ip-address;
}
}
}
Hierarchy Level
[edit forwarding-options],
[edit logical-systems logical-system-name forwarding-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-options],
[edit routing-instances routing-instance-name forwarding-options]
Release Information
Statement introduced in Junos
OS Release 8.3.
Description
Configure extended Dynamic Host Configuration
Protocol (DHCP) relay and DHCPv6 relay options on the router or switch
to enable the router (or switch) to function as a DHCP relay agent.
A DHCP relay agent forwards DHCP request and reply packets between
a DHCP client and a DHCP server.
DHCP relay supports the attachment of dynamic profiles and also
interacts with the local AAA Service Framework to use back-end authentication
servers, such as RADIUS, to provide subscriber authentication or client
authentication. You can attach dynamic profiles and configure authentication
support on a global basis or for a specific group of interfaces.
The extended DHCP and DHCPv6 relay agent options
configured with the dhcp-relay and dhcpv6 statements
are incompatible with the DHCP/BOOTP relay agent options configured
with the bootp statement. As a result, the extended DHCP
or DHCPv6 relay agent and the DHCP/BOOTP relay agent cannot both be
enabled on the router (or switch) at the same time.
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.