Cisco VXLAN EVPN & Microsoft 2016 DHCP RFC3527 issue

[LynK]

Have any of you ran into an issue when using a VXLAN EVPN network with option 82 on the DHCP server? We have this running live in our environment now. Client are able to get addresses through the option 82, but when a device goes to another site with a different subnet they are not getting the new IP addresses, but rather sticking to the old address.



Config has been verified with Cisco, and I am going to have to contact Microsoft on Monday. But in the meantime have any of you experienced this, and what was your workaround?

At first we had two DHCP servers configured (a primary & secondary) and what we saw happening was the original DHCP primary server was responding to the client (which on the new subnet was actually the secondary server) after the actual primary server received 2 DHCP requests for its old IP address.

So we removed DHCP failover, and removed the secondary DHCP server and tested... and the problem still arose. The good news is it was now talking to the proper server, the bad news is it looks like Microsoft was not responding correctly with the proper subnet and IP address for that subnet.

[LynK]

found the fix. enable option 82 on WLC, and DHCP proxying.

[wintermute000]

um mind clarifying? What's a WLC got to do with it again? Where is the client and where is the server in relation to the VXLAN EVPN network?