Access points in one bank branch join a lab controller. Their site tag uses an AP join profile whose primary controller address is the lab. Other branches with a different join profile join production. What should change?
Select an answer to reveal the explanation.
Short Explanation
This branch is doing what its join profile says, and that profile still points at the lab. Your other branches prove production is fine. Change the primary controller on this profile, not the antenna.
Full Explanation
An AP join profile, attached by the site tag, can name the primary controller an access point should join. This branch's profile still has the lab address, so those access points join the lab while other branches with a production profile join production. The fix is the primary controller in that join profile. The guest SSID is a client network. It does not select the controller an access point joins, and the site tag's join profile is the object that does. The antenna model shapes RF. It does not store a controller address. The beacon interval is not an IP address and the access point does not read it as one. Discovery and the join profile supply controller addresses. The beacon interval does not supply one. Exam caveat: access points that have already joined the lab may stay there until they rediscover. Changing the profile affects the next join, and you may need to move the current ones. Operational check: update the primary address, restart one branch access point, and confirm it joins the production controller.