Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Dynamic Host Configuration Protocol

  • Support for persistent storage of DHCPv4 and DHCPv6 bindings over EVPN IRB (ACX5448, ACX5448-D, and ACX5448-M)—Starting in Junos OS Release 21.2R1, ACX5448, ACX5448-D, and ACX5448-M routers that are configured to function as a DHCP relay agent can also be configured to preserve the DHCPv4 and DHCPv6 subscriber bindings across reboots. Existing bindings are written to a local file in /var/preserve. After reboot, the binding table is populated with the contents of the file, and the router identifies each subscriber that was on the deleted interface, and resumes normal packet processing for subscribers when the interface is restored. To preserve the subscriber binding information, enable the perisistent-storage statement at the [edit system services dhcp-local-server] hierarchy level.

    [See Preserving Subscriber Binding Information and DHCPv6 Relay Agent Overview.]

  • DHCP relay support—Starting in Junos OS Release 21.2R1, Junos fusion for provider edge supports the forwarding of DHCP messages between DHCP servers and clients. Junos fusion for provider edge supports DHCPv4 and DHCP relay on EVPN-MPLS networks. Junos fusion for provider edge does not support DHCP relay on EVPN-MPLS network over segment routing. You can configure the satellite devices to support the DHCP relay agent from the aggregation device.

    [See DHCP Relay Agent .]

  • Relay agent information options for stateless DHCP relay (QFX Series)—Starting in Junos OS Release 21.2R1, QFX Series switches support the configuration of relay agent information options for stateless DHCP relay. These options enable the relay agent to add information to DHCP client requests that the relay agent forwards to the DHCP server. The remote ID and circuit ID options are supported for both DHCPv4 and DHCPv6 stateless relay.

    [See DHCP Relay Agent.]