Access Point Tag Persistency

Access point tag persistency

Access point tag persistency allows mapped tags to be saved on the APs.

  • Enabled globally on the controller from Cisco IOS XE Bengaluru 17.6.1 onwards.

  • Eliminates the need to write tag configurations individually on each AP.

Supporting reference information

Access point tag persistency is disabled by default. When APs join a controller with tag persistency enabled, the mapped tags are saved on the APs.

Configure access point tag persistency (GUI)

The purpose of this task is to enable tag persistency on access points, allowing them to retain their tag mapping information without requiring individual configuration after reconnection.

Follow these steps to configure AP Tag Persistency using GUI

Procedure

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.

The AP tag persistency is enabled, allowing access points to retain their tag configurations even after disconnections.

What to do next

Save tags on an AP.

Save tags on an access point (GUI)

This task guides you on how to save tags, including policy, site, and RF tags, on an access point using the graphical user interface (GUI). Saving tags ensures the access point remembers its configuration across different controllers.

Procedure

Step 1

Choose Configuration > Wireless > Access Points.

Step 2

Click an AP from the list.

The Edit AP page is displayed.

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.

Upon completion, the access point will have saved the specified tags and configurations, allowing seamless operation even if the AP is transferred between controllers.

Delete saved tags on an access point (GUI)

The purpose of this task is to guide you to delete saved tags on an access point through the GUI.

Use these steps to delete saved tags on an access point:

Procedure

Step 1

Choose Configuration > Wireless > Access Points.

Step 2

Click an AP from the list of APs.

The Edit AP window is displayed.

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.

The access point is updated and all saved tags are cleared.

Configure access point tag persistency (CLI)

The purpose of this task is to configure access point tag persistency to ensure APs maintain their assigned tags when connecting to different controllers, which aids in redundancy scenarios.

Before you begin

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 to which the AP connects. 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 "New Configuration Model" chapter in Cisco Catalyst 9800 Series Wireless Controller Software Configuration Guide.


Note

Once enabled, AP tag persistency takes effect during the AP joining process. Therefore, if there are any APs that are already joined to the controller, those APs must rejoin the controller.

Procedure

Step 1

Enter global configuration mode.

Example:

Device# configure terminal

Step 2

Configure AP tag persistency

Example:

Device(config)# ap tag persistency enable

Step 3

Exit configuration mode and return to privileged EXEC mode.

Example:

Device(config)# end

After completing these steps, the AP tag persistency feature will be enabled on the controller, ensuring APs keep their tag assignments when moving to different controllers.

Verify access point tag persistency

To verify AP tag persistency in the primary controller, use this 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 this 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.