The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
From Cisco IOS XE Bengaluru 17.6.1 onwards, AP tag persistency is enabled globally on the controller. When APs join a controller with tag persistency enabled, the mapped tags are saved on the APs without having to write the tag configurations on each AP, individually.
|
Step 1 |
Choose Configuration > Tags & Profiles > Tags. |
|
Step 2 |
Click the AP tab. |
|
Step 3 |
In the Tag Source tab, check the Enable AP Tag Persistency check box to configure AP Tag persistency globally. When APs join a controller with the tag persistency enabled, the mapped tags are saved on the AP without having to write the tag configurations on each AP individually. |
|
Step 4 |
Click Apply to Device. |
Save tags on an AP.
|
Step 1 |
Choose Configuration > Wireless > Access Points. |
|
Step 2 |
Click an AP from the list. |
|
Step 3 |
Click the General tab. |
|
Step 4 |
In the Tags section, specify the appropriate policy, site, and RF tags that you created in the Configuration > Tags & Profiles > Tags page. |
|
Step 5 |
From the Policy drop-down list, select a value. |
|
Step 6 |
From the Site drop-down list, select a value. |
|
Step 7 |
From the RF drop-down list, select a value. |
|
Step 8 |
Check the Write Tag Config to AP check box to push the tags to the AP so that the AP can save and remember this information even when the AP is moved from one controller to another. |
|
Step 9 |
Click Update & Apply to Device. |
|
Step 1 |
Choose Configuration > Wireless > Access Points. |
|
Step 2 |
Click an AP from the list of APs. |
|
Step 3 |
In the Edit AP window, choose the Advanced tab. |
|
Step 4 |
In the Set to Factory Default section, check the Clear Resolved Tag Config check box to clear the saved tags on an AP. |
|
Step 5 |
Click Update & Apply to Device. |
For an AP to preserve its policy tag, site tag, and RF tag configured from the primary controller, these tags must also exist on the other controllers that the AP connect to. If all the three tags do not exist, the AP applies the default policy tag, site tag, and RF tag. Similarly, the tag policy is applicable even if one or two tags exist. AP tag persistency helps in priming an AP in N+1 redundancy scenarios. For more information about configuring tags, see https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-6/config-guide/b_wl_17_6_cg/m_config_model.html.
 Note |
After being enabled, AP tag persistency is performed during AP join. Therefore, if there are any APs that are already joined to the controller, those APs must rejoin the controller. |
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
configure terminal Example: |
Enters global configuration mode. |
|
Step 2 |
ap tag persistency enable Example: |
Configures AP tag persistency. |
|
Step 3 |
end Example: |
Exits configuration mode and returns to privileged EXEC mode. |
To verify AP tag persistency in the primary controller, use the following command:
Device# show ap tag summary
Number of APs: 1
AP Name AP Mac Site Tag Name Policy Tag Name RF Tag Name Misconfigured Tag Source
--------------------------------------------------------------------------------------------------------------------------------
Cisco01_AP xxxx.xxxx.xxxx default-site-tag OpenRoaming default-rf-tag No Static
Note |
If the Tag Source displays Static or Filter, it means that the AP tag mappings were configured on the primary controller. If the source displays Default, it means that the AP received the default tags when joining the controller. |
To verify the AP tag persistency in the secondary controller, use the following command:
Device# show ap tag summary
Number of APs: 1
AP Name AP Mac Site Tag Name Policy Tag Name RF Tag Name Misconfigured Tag Source
--------------------------------------------------------------------------------------------------------------------
Cisco01_AP xxxx.xxxx.xxxx default-site-tag OpenRoaming default-rf-tag No AP
Note |
If the Tag Source displays AP, it means that the policy tag, site tag, and RF tag match what was configured on the primary controller, indicating that the AP tags have persisted across controllers. |
Feedback