09-28-2022 09:03 AM
Whenever I make changes to one of my WLANs, it causes the SSID to stop broadcasting from APs that it is assigned to. The only resolution I have discovered is to go into each AP and changed the policy tag to a different tag, save it, then change it back to the correct tag. Is there any way to either prevent this issue from happening, or globally force every AP to pull an updated config?
Solved! Go to Solution.
09-30-2022 05:26 PM - edited 09-30-2022 05:30 PM
We ran into an issue just a few days ago when we migrated some APs from AireOS to IOS-XE. Other groups of APs (different sites) went well. In one group, none of the APs were broadcasting anything. We dialed into one of the APs and used the command "sh dot11 wlan" and there was not a single SSID in them.
Using CLI, we removed and added SSIDs from the Policy Tag (several times) and it did not work, however, when we removed and then added the SSIDs into the Policy Tag using GUI, it started working.
This is why I was asking if the SSIDs in the Policy Tags were created using GUI or CLI.
9800 version: 17.6.4
09-28-2022 03:09 PM
Sounds very bug related. What version code you running
09-29-2022 07:07 AM
I am running 17.3.5a. After I posted this, I found CSCwa76898 which describes the same issue, however the workarounds did not work and 17.3.5a is listed under fixed releases.
09-28-2022 06:45 PM
Where the policy tags created using CLI or GUI?
09-29-2022 07:09 AM
It was a mix of both CLI or GUI, but this issue is affecting multiple different policy tags and I don't remember which were CLI and which were GUI.
09-30-2022 05:26 PM - edited 09-30-2022 05:30 PM
We ran into an issue just a few days ago when we migrated some APs from AireOS to IOS-XE. Other groups of APs (different sites) went well. In one group, none of the APs were broadcasting anything. We dialed into one of the APs and used the command "sh dot11 wlan" and there was not a single SSID in them.
Using CLI, we removed and added SSIDs from the Policy Tag (several times) and it did not work, however, when we removed and then added the SSIDs into the Policy Tag using GUI, it started working.
This is why I was asking if the SSIDs in the Policy Tags were created using GUI or CLI.
9800 version: 17.6.4
10-03-2022 08:05 AM
Removing add adding back the SSIDs to Policy Tags via gui fixed the issue.
09-29-2022 12:36 PM
@jake.hansen Did you write the tags to the AP's at least once in the past? If not please write the tags.
Lab-9800#ap name <AP name> write tag-config
Also if you are running 17.6.X or higher enable Ap tag persistency.
THen try to do changes and check whether this is creating an impact.
09-30-2022 11:06 AM
All APs starting broadcasting the missing SSID again after I removed and re-added the WLAN from the affect policy tags.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide