keep-incoming-remote-id (DHCP Relay Agent)
Syntax
keep-incoming-remote-id ;
Hierarchy Level
[edit forwarding-options dhcp-relay dhcpv6 relay-agent-remote-id], [edit forwarding-options dhcp-relay relay-option-82 circuit-id], [edit logical-systems logical-system-name forwarding-options dhcp-relay dhcpv6 relay-agent-remote-id], [edit logical-systems logical-system-name forwarding-options dhcp-relay relay-option-82 XXXcircuit-id], [edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-options dhcp-relay dhcpv6 relay-agent-remote-id], [edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-options dhcp-relay relay-option-82 circuit-id], [edit routing-instances routing-instance-name forwarding-options dhcp-relay dhcpv6 relay-agent-remote-id], [edit routing-instances routing-instance-name forwarding-options dhcp-relay relay-option-82 circuit-id],
Description
Specify that the jdhcpd process keeps
the incoming remote ID and prepends the ID with the locally generated
ID (in the format, generated-id + incoming-id) before sending
the leasequery packet to the DHCPv6 server.
This configuration is required for leasequery and bulk leasequery operations when subscriber authentication is based on the remote ID, and enables leasequery and bulk leasequery to restore the agent circuit identifier/agent remote identifier (ACI/ARI) pair and to use the remote ID to authenticate subscribers.
Use the statement at the [edit ... dhcpv6] hierarchy
level to configure DHCPv6 support.
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 16.1.