Enable DHCP Relay on NSX Distributed Router (dLR)

A quick post to show how to Enable DHCP Relay on a Distributed Router (dLR). My topology:

Select the dLR, tab Manage > DHCP Relay > Edit

Under IP Addresses insert the IP address of your DHCP server

Under DHCP Relay Agents click the + symbol and specify the interface from which DHCP requests will come from, in my example is the Web LIF.
The gateway IP address is used so that the DHCP server can identify from which subnet the DHCP request is coming from.

My DHCP Server is configured with a Scope for the subnet 172.16.10.0/24

Monitoring my ESG for traffic destined to port 67 (DHCP Server) you can see the DHCP request arriving from 172.16.10.254 and 192.168.1.50 replying back:

EGW01-0> EGW01-0> debug packet display interface vNic_1 dst_port_67
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vNic_1, link-type EN10MB (Ethernet), capture size 65535 bytes
21:59:03.856914 IP 172.16.10.254.67 > 192.168.1.50.67: BOOTP/DHCP, Request from 00:50:56:a1:fc:32, length 300
21:59:03.857169 IP 172.16.10.254.67 > 192.168.1.50.67: BOOTP/DHCP, Request from 00:50:56:a1:fc:32, length 300
21:59:03.873199 IP 192.168.1.50.67 > 172.16.10.254.67: BOOTP/DHCP, Reply, length 303
21:59:03.874915 IP 172.16.10.254.67 > 192.168.1.50.67: BOOTP/DHCP, Request from 00:50:56:a1:fc:32, length 300
21:59:03.875000 IP 172.16.10.254.67 > 192.168.1.50.67: BOOTP/DHCP, Request from 00:50:56:a1:fc:32, length 300
21:59:03.877303 IP 192.168.1.50.67 > 172.16.10.254.67: BOOTP/DHCP, Reply, length 303

And here the lease is visible

Leave a Comment Cancel reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

4 Trackbacks