Wireless Access

In Access Points > Remote APs, I try to reprovision an AP by changing the name or AP group. After it reboots, it goes back to the same name/group. We have other controllers on the same mobility master that do not do this, any clue on to what the issue could be?

Check the Allowlist.

While i only work with campus aps, i suspect it works the same for Remote APs.

The name set in the Allowlist takes precedence, the same for the AP Group if it is set there.

You would have to change the name and group in the Allowlist first, and then re-provision it with the new name and group.

In Access Points > Remote APs, I try to reprovision an AP by changing the name or AP group. After it reboots, it goes back to the same name/group. We have other controllers on the same mobility master that do not do this, any clue on to what the issue could be?

This is definitely coming from the AP allow list.

Check the Allowlist.

While i only work with campus aps, i suspect it works the same for Remote APs.

The name set in the Allowlist takes precedence, the same for the AP Group if it is set there.

You would have to change the name and group in the Allowlist first, and then re-provision it with the new name and group.

In Access Points > Remote APs, I try to reprovision an AP by changing the name or AP group. After it reboots, it goes back to the same name/group. We have other controllers on the same mobility master that do not do this, any clue on to what the issue could be?

To add more detail, the RAP currently has a different name from the whitelist and is in a different AP group specified in the whitelist. I can successfully change the AP group and name on all other controllers managed by the MM managed network except for this controller. If I reboot the controller, then I can see the new AP name and group. Same also happens if I remove it from L2 redundancy and add it back. I'm wondering why it isn't working for just this controller but it works for all other controllers.

This is definitely coming from the AP allow list.

Check the Allowlist.

While i only work with campus aps, i suspect it works the same for Remote APs.

The name set in the Allowlist takes precedence, the same for the AP Group if it is set there.

You would have to change the name and group in the Allowlist first, and then re-provision it with the new name and group.

In Access Points > Remote APs, I try to reprovision an AP by changing the name or AP group. After it reboots, it goes back to the same name/group. We have other controllers on the same mobility master that do not do this, any clue on to what the issue could be?