An engineer edits a WLAN directly on a Catalyst 9800, and the next Catalyst Center provision puts the old WLAN settings back. Catalyst Center is provisioning this site. Where should the change be made so it sticks?
Select an answer to reveal the explanation.
Short Explanation
You changed the copy, and the system that owns the original wrote it back. Catalyst Center is provisioning this site, so your change has to live in that design or the next push will undo it. A note on the access point will not stop the push.
Full Explanation
When Catalyst Center is the provisioning source for a site, it pushes the wireless design to the controller. A manual edit on the 9800 lasts only until the next provision, which restores the design Catalyst Center holds. The change has to be made in that design so the push and the intent are the same. A note stored on an access point does not block provisioning, and access points are not the source of the WLAN definition. An RF tag description is a label on a radio profile binding. It does not disable provisioning for a WLAN, and editing the description leaves the WLAN design untouched. A guest anchor terminates guest sessions. It does not become the source of truth for employee WLANs just because it is in the path for guests. Exam caveat: if the site is intentionally managed only on the controller, stop provisioning it from Catalyst Center rather than fighting the push. Two owners will keep overwriting each other. Operational check: change the WLAN in the Catalyst Center design, provision once, and confirm the controller shows the new setting after the push.