Cisco 9800 - AP Tag Difference in GUI and CLI

[TsvetanV]

Hi Experts,

Here is one interesting find.

I had to transfer AP Tag config from one WLC to another. Lets call them WLC1 and WLC2. I decided to check the show run, get the output from there any easily paste it in the cli of the WLC2. However, I've found out that the current tag config on the APs from the CLI is different for some of the APs than the tag config, that I am currently seeing on the GUI of the WLC1.

Most of the APs on WLC1 have been configured using the CLI and then we had to change tags and profiles, which we did via the GUI and I am wondering if this might be the reason?

Does anyone know what might be the reason for this? This doesn't look normal to me and I am wondering if this is a case for Cisco TAC/ bug or I am missing something. APs appear to be working fine.
Is it possible that if you configure tags by CLI, then change them via the GUI this change is not reflected in the configuration?

WLC is running: 17.3.4 and configuration has been saved.

Looking forward to your reply. 

Thanks!
Tsvetan

[Arshad Safrulla]

Have you tried "write tags" for APs and then compared the output. Can you paste the output for "wireless config validate" from the WLC where you have this TAG misconfig issue.

Also mention the AP models which you are having issues with. For sure this is not normal, I would suggest you try with different browsers as well.

[TsvetanV]

Hi Arshad,

Thanks for the reply.

I don't have "write tags" command. Not sure how to use it actually.
But when I do wireless config validate, nothing comes up. No output.
The APs are 1702 and 1832.

It's not so about the browser it would seem, because the APs are operating with the new tags. (proven by the channels that they are using with the new RF profile, that were not used in the previous one) Only that the configuration was showing different.

I had saved the configuration before, and now when I Checked the Show Diff output from the GUI it was showing the proper configuration actually. Then I saved the config again and now it is showing the proper tags configuration. 

I have no idea how that happened and I am really sorry that I didn't save the output so that I can show it to TAC.

Cheers!

[JPavonM · Accepted solution]

If the TAG config on the running config is the good one, then APs should be using that as per the Tag source order. f the AP is having another one different, then maybe missing that AP Tag config in the WLC.

As @Arshad Safrulla told before, if Tag config on running config is the good one, then use "ap name APNAME write tag-config" command to prim APs with such Tags. when doing that, then you don't need to copy/paste all AP-2-tag config to WLC2, as APs are carrying the proper Tag config.

[TsvetanV]

HI JPavonM,

Thanks for the reply.

The TAG Config that I was seeing in GUI was the good one. The one I was seeing in the configuration was not the same. Thats what got me scared.
Wow thanks for the command, that's a great piece of advice. I will immediately do that, much appreciated!

Cheers!

[eagle05]

Does anyone know what is DNAC API call that will go out to 6 different controllers to see if a new AP was installed and is seating in a default-tag state for any of these options "Policy Tag", "Site Tag", "RF Tag".

cli command from controller is = show ap tag summary

DNAC ver = 2.3.5.6-70143

Controller ver = 17.9.5

Thank you.