AP regex filter does not work - cisco 9800

[Plam-b]

Hi,

For better segmentation I need to modify policy-tag on many APs through 9800. I'm going to do it through AP regex filter as I found it the easiest and fastest one. Before doing it on live network I did some tests that it looks like it is not working properly.

This is the process I do

"ap filter name apinstall
ap name-regex ^install.*
tag policy Policy-tag-install
tag rf rf-tag-typical
tag site site-tag-typical

ap filter priority 20 filter-name apinstall "

I give a off/on to the AP but when it loads up it couldn't catch the config I mentioned in the policy. But, when I want to do the config for a new AP with no configuration on it (through other filter-regex config) , it is working and no problem on it.

Thanks for your comments and helps.

[Leo Laohoo]

Why is there a double-quote at the start and end?

[Plam-b]

It is just to mention it is a piece of code. Of course it is not part of the code I applied to the device.

[Leo Laohoo]

What firmware is the WLC on?

Ok, so what are the name of the AP that is meant to hit this filter?  Please provide a sample. 

We use AP filters and I am not seeing anything wrong with it.  

[Plam-b]

Hi Leo,

thanks for your reply,

As a test environment I tested these names: installXX and install-XX (the X is random number).

And of course I used this regex syntax for the - one, ^install*\-.*$

The firmware version: 17.9.3

As I mentioned when I use it for the AP with no configuration that its name is "APmac" everything works fine. Problem is for the APs that currently are provisioned and existed in the controller.

Thanks

[Leo Laohoo]

ap name-regex ^install

Try that.

[MHM Cisco World]

AP will automatically use IOS ver. Install??

İ don't think so, that why the filter not work. 

MHM

[Simon Blomqvist · Accepted solution]

Perhaps the AP is stuck with statically configured tags. Could potentially work if you go to tags > ap > static and delete the AP from there and then do a reload of AP. If that doesn't work I'd do a factory reset of the AP.

[eglinsky2012]

You can verify how the AP is getting its existing tags in Configuration > Wireless > Access Points, and in the table, there's a column for Tag Source (static/filter/AP/location/default).

If the source is Filter, there may be another filter with a higher (lower number) priority that the AP is hitting instead of the one you're testing. You'll have to remove or modify that other filter, or change priorities so the desired one is higher than the other one.