New store access points keep joining a decommissioned lab controller. DHCP option 43 on the store scope points at the production controller. Each access point has a static controller address set to the lab. Why is option 43 ignored?
Select an answer to reveal the explanation.
Short Explanation
The access point already has a controller written on it, and that address is the lab. Your option 43 can be perfect and still sit unused. Clear the static lab address if you want the store to follow the scope.
Full Explanation
A statically configured controller address is explicit. These access points are set to the lab, and they join the lab, so they are following that static address rather than DHCP option 43. Option 43 pointing at production does not override a static lab address that the access point is already using. The claim that a static address is only a last resort after option 43 and DNS fail does not match this result. They join the lab while option 43 says production. The lab controller does not answer option 43 on behalf of production. Option 43 is supplied by DHCP in the store scope, and the static address is what is in use. Option 43 can name production and still lose to a static lab address that is already configured on the access point. Exam caveat: after you clear the static address, a DNS name or a broadcast can still send an access point somewhere unexpected. Confirm which method it actually used on the next join. Operational check: clear the static lab address on one access point, renew DHCP, and confirm it joins the production controller named in option 43.