Understanding the Extended DHCP Relay Agent for EX Series Switches
You can configure a Juniper Networks EX Series Ethernet switch to act as an extended DHCP relay agent. This means that a locally attached host can issue a DHCP request as a broadcast message and the switch configured for DHCP relay relays the message to a specified DHCP server. Configure a switch to be an extended DHCP relay agent if you have locally attached hosts and a remote DHCP server.
You can use DHCP relay in carrier edge applications such as video/IPTV to obtain configuration parameters, including an IP address, for your subscribers.
DHCP relay supports the attachment of dynamic profiles. You can attach dynamic profiles on a global basis or for a specific group of interfaces.
EX Series switches also support the DHCPv6 relay agent.
This topic covers:
Extended DHCP Relay and Legacy DHCP/BOOTP Relay
The extended DHCP relay agent options configured with the dhcp-relay statement are incompatible with the DHCP/BOOTP relay agent options configured with the bootp statement. Therefore, you cannot enable both the extended DHCP relay agent and the legacy DHCP/BOOTP relay agent on a switch at the same time.
For information about the legacy DHCP/BOOTP relay agent, see DHCP/BOOTP Relay for Switches Overview.
Interaction Among the DHCP Relay Agent, DHCP Client, and DHCP Servers
The following steps describe, at a high level, how the DHCP client, DHCP relay agent, and DHCP server interact in a configuration that includes two DHCP servers:
The DHCP client sends a discover packet to find a DHCP server in the network from which to obtain configuration parameters, including an IP address, for the subscriber.
The DHCP relay agent receives the discover packet and forwards copies of the discover packets to each of the two DHCP servers. The DHCP relay agent then creates an entry in its internal client table to keep track of the client’s state.
In response to receiving the discover packet, each DHCP server sends an offer packet to the client. The DHCP relay agent receives the offer packets and forwards them to the DHCP client.
On receiving the offer packets, the DHCP client selects the DHCP server from which to obtain configuration information. Typically, the client selects the server that offers the longest lease time on the IP address.
The DHCP client sends a request packet that specifies the DHCP server from which to obtain configuration information.
The DHCP relay agent receives the request packet and forwards copies of this packet to each of the two DHCP servers.
The DHCP server requested by the client sends an acknowledgement (ack) packet that contains the client’s configuration parameters.
The DHCP relay agent receives the ack packet and forwards it to the client.
The DHCP client receives the ack packet and stores the configuration information.
If configured to do so, the DHCP relay agent installs a host route and Address Resolution Protocol (ARP) entry for this client.
After establishing the initial lease on the IP address, the DHCP client and the DHCP server use unicast transmission to negotiate lease renewal or release. The DHCP relay agent snoops all of the packets unicast between the client and the server that pass through the relay agent to determine when the lease has expired or been released. This process is referred to as lease shadowing or passive snooping.