Regex tagging stopped working

[lcaruso]

Doing an AP build out running 17.6.4 code on physical 9800-40 units and suddenly the tagging stopped working with no changes to the configuration. Probably need to open a TAC case but wondering if anyone has seen this, maybe a bug. Thanks. 

[Scott Fella]

I have used that for a while and never ran into that issue.  You probably should open a TAC case.  Have you tried to reapply the regex, or do you know when it stopped working?  Do you have another unit that is still working?

Also, is your filter moved up in priority above static, location, ap?

[lcaruso]

Hi Scott, thanks for responding. I have not tried to reapply the regex but that is a good idea thanks much. If that does not work, I will open a TAC case and just manually tagging for now. Small site, only two controllers in HA SSO, so no others to compare.  

[lcaruso]

Hi Scott, thanks for responding. I have not tried to reapply the regex but that is a good idea thanks much. If that does not work, I will open a TAC case and just manually tagging for now. Small site, only two controllers in HA SSO, so no others to compare.

[Scott Fella]

Just make sure you look at the order you have set.  This can also be why it may not be working, especially if it was statically set as an example.

[Leo Laohoo]

---

@lcaruso wrote:
Doing an AP build out running 17.6.4 code on physical 9800-40 units and suddenly the tagging stopped working with no changes to the configuration.

---

We found this strange "quirk" about tagging:  It is case sensitive but the system will allow the operator to assign a Policy Profile that does not exist into a Policy Tag.  

So when the AP is assigned a Policy Profile, it is not broadcasting the correct SSID (or not broadcasting the SSID at all).  

[Rich R]

@lcaruso did you solve this problem?

[lcaruso]

What we figured out was a capwap reset was not enough to get the regex naming to function, we had to delete the AP and force it to rejoin the controller, so yes, it was solved. Thanks.

[Leo Laohoo]

I have a 9800 with an uptime of 127 days and the filters have stopped working.  I vividly remembered that when an un-configured AP joins the WLC and subsequently gets renamed, the filter will kick in. 

In the last 3 weeks or so, I have noticed that it has stopped working.  Because I did not have the time to do some more tinkering, if I reboot the newly re-named AP, the filters will start to work.

[Rich R]

What exactly do you mean by "delete the AP" - did you have a static tag assignment for the AP?
If so that will always take precedence over the filters:
9800#sh ap tag sources
Priority Tag source
--------------------------------
0 Static
1 Location
2 Filter
3 AP
4 Default
In that case it's not that the filters weren't working but that you were overriding them with static tag assignments.

[lcaruso]

By deleting, I believe it was command line "no ap mac-address" was the solution and wait for ap reboot. I had a wireless CCIE who actually did the work so let me see if he is willing to chime in on what exactly he recalls. 

[lcaruso]

The sequence as I recall was new APs were not getting tagged after renaming correctly even though filters were in place. Since we were prepping for cutover and did not have time to figure out, I started tagging them manually. Then one everything was tagged manually and we had time to step back and regroup, we wanted all aps to have the same tag source/priority. But not sure what the CCIE did differently if anything. I will find out. 

[Rich R]

@Leo Laohoo I only started using them recently (17.9.2) and found a CAPWAP restart was needed after renaming the AP before the filters got applied.

[Leo Laohoo]

Update to my previous response:  I have tested this on another 9800 (WLC#2), same firmware version, 161 days uptime, and the filters work.  

• WLC#1 has 2k APs (4800, 1560 & 9130)
• WLC#2 only has 74 APs.