DHCPv4 Relay Supported Scenarios

The following examples illustrate the network environments where the DHCPv4 Relay Agent can be deployed.

Click to expand in new window
DHCP Relay Deployments
DHCP Relay Deployment Scenarios
Local DHCP Server
DHCP Client and DHCP Server 1 (172.20.1.100) are on the same subnet (same broadcast domain). A DHCP Relay Agent is not required in this scenario, because the server receives broadcast discover messages from the client directly. A configured DHCP Relay Agent in this scenario is redundant because the DHCP Relay Agent relays (unicast) the received DHCP packet again to the destination DHCP Server or DHCP Client. As a result, both parties receive multiple packets.
Remote DHCP Server
DHCP Clients and DHCP Server 2 (172.30.1.100) are on different subnets but are directly linked through a DHCP Relay Agent.
DHCP Servers in a Network
DHCP Clients and DHCP Server are on different subnets and connected through relay chaining (relay multi-hops). This scenario is not depicted in the image.
Multiple DHCP Servers
DHCP Server 2 (172.30.1.100) and DHCP Server 3 (172.10.1.100) are two server addresses on different subnets configured at Router 1 (172.20.1.1) which is a DHCP Relay Agent.
DHCP Server in Different VRFs
DHCP Clients and DHCP Server are on different VRFs. This scenario is not depicted in the image.