Wireless Network Configuration Use Cases

Wi-Fi 7 configuration use case

This section helps you understand the Wi-Fi 7 configuration use case for wireless networks.

Enable the Wi-Fi 7 configuration

Use this procedure to enable the Wi-Fi 7 configuration on Catalyst Center.

Before you begin

  • Ensure that the Wi-Fi 7 APs are available in the Provision > Inventory window.

    The Wi-Fi 7 APs include:

    • Cisco Catalyst 9176D1 Series Access Points,

    • Cisco Catalyst 9176I Series Access Points, and

    • Cisco Catalyst 9178I Series Access Points.

  • The devices must be running Cisco IOS XE Release 17.15.2 or later.

  • Wi-Fi 7 APs use CNS licenses. If these APs don't meet the license requirements, they are in worldwide safe mode (WWSM).

    Enable the CNS licenses on the License Manager window to disable WWSM and ensure that the license requirements are met. For more information, see "Manage Licenses" in the Cisco Catalyst Center Administrator Guide.

Procedure

Step 1

Enable the 802.11be status for the 2.4-GHz, 5-GHz, and 6-GHz radio bands in the Dot11be Status Configuration feature template.

You can use the existing default profiles or create custom profiles for each radio band. For more information, see Create a feature template for Dot 11be status configuration.

Step 2

Create an RF profile with the necessary settings and configure the required Wi-Fi 7 settings.

  • Enable preamble puncturing using the Preamble Puncturing toggle button for the 5-GHz and 6-GHz radio bands.

  • Use the DBS Channel Width slider to set the maximum channel width of 320 MHz for the 6-GHz radio band.

  • Check the corresponding check box to enable the 802.11be parameters for the 6-GHz radio band.

    • Downlink OFDMA

    • Uplink OFDMA

    • Downlink MU-MIMO

    • Uplink MU-MIMO

    • OFDMA Multi-RU

For more information, see Create a wireless radio frequency profile.

Step 3

Create a 802.11be profile for the 2.4-GHz and 5-GHz radio bands.

For more information, see Create an 802.11be profile.

Note

 

This 802.11be profile is mapped to the WLAN. It’s applicable only for the 2.4-GHz and 5-GHz radio bands. For the 6-GHz radio band, the 802.11be configuration is mapped from the corresponding settings in the RF profile.

Step 4

In the associated wireless network profile,

Step 5

(Optional) In the corresponding SSID, check the AP Beacon Protection check box to enable AP beacon protection.

For more information, see Create SSIDs for an enterprise wireless network and Create SSIDs for a guest wireless network.

Step 6

Configure the Wi-Fi 7 APs.

For more information, see Configure APs.

Step 7

Provision the Wi-Fi 7 APs with the associated network profile.

For more information, see Provision Cisco APs on day 1.

High availability use cases

These topics help you understand the high availability (HA) use cases for wireless networks.

Configure Cisco Wireless Controller HA

Cisco Wireless Controller HA allows you to use a wireless controller as a backup for a primary wireless controller. The active wireless controller handles all the APs, client traffic, and shares the AP and client database with the standby wireless controller. If there is a failover, the standby wireless controller takes over immediately, resulting in zero client service downtime and zero SSID outage.

Before you begin

  • Ensure that both the wireless controllers are of the same form factors.

  • Ensure that both the wireless controllers are running the same software version.

  • Wireless controller HA supports a maximum redundancy port link latency of 80 ms round-trip time (RTT), minimum bandwidth of 60 Mbps, and minimum maximum transmission unit (MTU) of 1500.

  • Ensure that you connect the redundancy ports of both the wireless controllers physically or through a Layer 2 virtual network. If you connect redundancy ports through a Layer 2 virtual network, ensure that the link latency, bandwidth, and MTU requirements are met.

  • For the Cisco Catalyst 9800-CL Wireless Controllers running on ESXi, KVM, and Hyper-V, ensure that the redundancy port connects to the same vswitch.

Procedure

Step 1

Ensure that you have the wireless controller in your inventory. For more information, see About Inventory and Add a network device.

If the wireless controller isn’t available in the inventory, use the Discovery feature to discover it. For more information, see Discover Your Network.

Step 2

Ensure that both the wireless controllers are in the Managed state in the inventory. For more information, see Display information about your inventory.

Step 3

Use the show redundancy command to verify that the operating redundancy mode is Non-redundant on both the wireless controllers.

Step 4

From the main menu, choose Provision > Inventory.

Step 5

Check the check box next to the required wireless controller, and then click Actions > Provision > Configure WLC HA.

Step 6

Enter the Redundancy Management IP and the Peer Redundancy Management IP addresses.

You must configure the IP addresses used for redundancy management IP and peer redundancy management IP in the same subnet as the management interface of the wireless controller. Ensure that these IP addresses are unused IP addresses within that subnet range.

Step 7

Enter the Netmask.

Step 8

From the Select Secondary WLC drop-down list, choose the secondary wireless controller.

Step 9

Since the Cisco Catalyst 9800-CL Wireless Controller doesn't have a dedicated redundancy port, choose the interface that will be used for the redundancy port.

Note

 

Appliance-based Cisco Catalyst 9800 Series Wireless Controllers have dedicated redundancy ports, and redundancy port interface selection isn’t necessary for these devices.

Step 10

Click Configure HA.

What to do next

To verify the status of HA, use the show redundancy command. This is a sample output of the command:

Sample show redundancy output.

To verify the Priority of the primary wireless controller, use the show chassis command. The Priority of the primary wireless controller is changed to 2 to ensure that its role is Active. This is a sample output of the command:

Sample output of show chassis command.

Configure Cisco Wireless Controller N+1 HA

Cisco Wireless Controller N+1 HA allows you to use a wireless controller as a backup for multiple primary wireless controllers. Catalyst Center doesn't support stateful switchover for N+1 HA and each wireless controller must be managed separately.


Note

  • Catalyst Center supports N+1 HA configurations for primary and secondary wireless controllers. Catalyst Center doesn't support tertiary wireless controller configurations.

  • If you edit the primary wireless controller configuration, reprovision the secondary wireless controller manually with the updated configurations.

Procedure

Step 1

Ensure that you have the wireless controller in your inventory. For more information, see About Inventory and Add a network device.

If the wireless controller isn’t available in the inventory, use the Discovery feature to discover it. For more information, see Discover Your Network.

Step 2

Ensure that both the wireless controllers are in the Managed state in the inventory. For more information, see Display information about your inventory.

Step 3

Create enterprise and guest wireless SSIDs. For more information, see Create SSIDs for an enterprise wireless network and Create SSIDs for a guest wireless network.

Step 4

If you created a wireless network profile during SSID creation, assign it to the primary wireless controller-managed site. From the main menu, choose Design > Network Profiles, and then click the corresponding Assign Site option for the wireless network profile.

Step 5

Provision the primary wireless controller. Choose the role as Active Main WLC. For more information, see Provision a Cisco AireOS Controller and Provision a Cisco Catalyst 9800 Series Wireless Controller.

Step 6

Provision the secondary wireless controller. Choose the role as Active Main WLC and choose the secondary managed AP location same as the managed AP location for the primary wireless controller. For more information, see Provision a Cisco AireOS Controller and Provision a Cisco Catalyst 9800 Series Wireless Controller.

Step 7

Provision the APs. For more information, see Provision Cisco APs on day 1.

Wireless mobility use cases

These topics help you understand the mobility configuration use cases for wireless networks.

Configure wireless mobility

Mobility configuration in Catalyst Center allows you to establish a tunnel between Cisco Wireless Controllers in a network allowing them to communicate with each other and dynamically share information. The mobility tunnel enables seamless roaming of clients within a wireless network. This procedure describes the steps to configure a mobility tunnel between wireless controllers for these use cases:

  • Two newly added wireless controllers with the same mobility group: The two wireless controllers are newly added to Catalyst Center and are not yet provisioned.

  • Two existing wireless controllers with the same mobility group: The wireless controllers are already added and provisioned on Catalyst Center and have the same mobility group name.

  • Two existing wireless controllers with different mobility group: The wireless controllers are already added and provisioned on Catalyst Center and have different mobility group name.

  • Two existing wireless controllers with a third wireless controller: Adding a new wireless controller to an existing mobility group between two wireless controllers.

Before you begin

Procedure

Step 1

For newly added wireless controllers with the same mobility group, do these steps:

  1. Run the show wireless mobility summary command to verify that there’s no existing mobility tunnel between the controllers.

  2. Choose one of the wireless controllers and configure the mobility group, adding the other wireless controller as the peer. For more information, see Configure mobility group.

  3. Verify the configurations before provisioning.

  4. Provision the wireless controller.

    Note

     

    You don't have to provision the second wireless controller. Adding it as a peer for the first wireless controller automatically provisions it with the same mobility group name and peer configurations.

Step 2

For two existing wireless controllers with same mobility group, do these steps:

  1. Verify that the wireless controllers have the same mobility group name configured. For more information, see About Inventory and Display information about your inventory.

  2. Choose one of the wireless controllers and configure the mobility group, adding the other wireless controller as the peer. For more information, see Configure mobility group.

  3. Verify the configurations before provisioning.

  4. Provision the wireless controller.

    Note

     

    You don't have to provision the second wireless controller. Adding it as a peer for the first wireless controller automatically provisions it with the same mobility group name and peer configurations.

Step 3

For two existing wireless controllers with different mobility group, do these steps:

  1. Verify that the wireless controllers have the mobility group name configured. For more information, see About Inventory and Display information about your inventory.

  2. Choose one of the wireless controllers and configure the mobility group, adding the other wireless controller as the peer. For more information, see Configure mobility group.

  3. Verify the configurations before provisioning.

  4. Provision the wireless controller.

    Note

     

    You don't have to provision the second wireless controller. Adding it as a peer for the first wireless controller automatically provisions it with the same mobility group name and peer configurations.

Step 4

For adding a new wireless controller to an existing mobility group between two wireless controllers, do these steps:

  1. Verify that the existing wireless controllers have the mobility tunnel established between them by checking the mobility group name and the mobility peer information in the Mobility tab. For more information, see About Inventory and Display information about your inventory.

  2. Choose the newly added wireless controller and configure the mobility group, adding the other two existing wireless controllers as peers. For more information, see Configure mobility group.

  3. Verify the configurations before provisioning.

  4. Provision the wireless controller.

    Note

     

    You don't have to provision the existing two wireless controllers. Adding them as a peer for the newly added wireless controller automatically provisions it with the same mobility group name and peer configurations.

What to do next

After provisioning, run the show wireless mobility summary command on each of the controllers to verify the mobility tunnel status. This is a sample output of the command:

Show wireless mobility summary command output

Configure anchor and foreign wireless mobility

The anchor and foreign wireless configuration on Catalyst Center allows you to establish wireless mobility between Cisco Wireless Controllers on different wireless networks. In an anchor and foreign setup, the foreign wireless controller encapsulates the client L3 traffic in the mobility tunnel and forwards it to the anchor wireless controller. The anchor wireless controller decapsulates the tunnel and switches the client traffic. This procedure describes the steps to configure anchor/foreign wireless mobility for these use cases:

  • Configuring two newly added wireless controllers - one anchor and one foreign wireless controller.

  • Configuring three newly added wireless controllers - one anchor and two foreign wireless controllers.

  • Configuring three newly added wireless controllers - one foreign and two anchor wireless controllers.

  • Deleting the anchor/foreign setup.

Before you begin

  • Ensure that you have the Cisco Wireless Controllers in your inventory and they are in Managed state. For more information, see About Inventory and Display information about your inventory.

  • Use the show wireless mobility summary command to verify that there’s no existing mobility tunnel between the wireless controllers.

Procedure

Step 1

Create an SSID for the wireless network and associate it with a new wireless network profile. For more information, see Create SSIDs for an enterprise wireless network or Create SSIDs for a guest wireless network.

In the Associate SSID to Profile step, choose the Add Profile option and complete this configuration:

  • Profile Name: Enter a name for the profile.

  • Fabric: Choose No.

  • Do you need Anchor for this SSID?: Choose Yes.

Step 2

For a scenario with one anchor and one foreign wireless controller, do these steps:

  1. Assign the newly created wireless profile to the site managed by the foreign wireless controller.

    To assign a site:

    • From the main menu, choose Design > Network Profiles

    • Choose the profile and click Assign Site. For information on creating sites, see Create, edit, and delete a site.

  2. Provision the anchor wireless controller.

    • Choose the wireless controller role as Anchor WLC and select the anchor Managed AP location(s).

    • Configure the interface details.

    • Configure other advance settings, if required, and deploy.

    For more information on provisioning wireless controllers, see Provision a Cisco Catalyst 9800 Series Wireless Controller or Provision a Cisco AireOS Controller.

  3. Provision the foreign wireless controller.

    • Choose the wireless controller role as Active Main WLC and select the Managed AP location(s).

    • Configure other advance settings, if required, and deploy.

    For more information on provisioning wireless controllers, see Provision a Cisco Catalyst 9800 Series Wireless Controller or Provision a Cisco AireOS Controller.

  4. Provision the APs under the wireless controllers.

    Ensure that APs have the correct SSID. For more information on AP provisioning, see Provision Cisco APs on day 1.

Step 3

For a scenario with one anchor and two foreign wireless controllers, do these steps:

  1. Assign the newly created wireless profile to the sites managed by the foreign wireless controllers.

    • From the main menu, choose Design > Network Profiles

    • Choose the profile and click Assign Site. For information on creating sites, see Create, edit, and delete a site.

  2. Provision the anchor wireless controller.

    • Choose the wireless controller role as Anchor WLC and select the Managed AP location(s) (select both foreign sites).

    • Configure the interface details.

    • Configure other advance settings, if required, and deploy.

    For more information on provisioning wireless controllers, see Provision a Cisco Catalyst 9800 Series Wireless Controller or Provision a Cisco AireOS Controller.

  3. Provision the foreign wireless controllers.

    • Choose the wireless controller role as Active Main WLC and select the Managed AP location(s).

    • Configure other advance settings, if required, and deploy.

    For more information on provisioning wireless controllers, see Provision a Cisco Catalyst 9800 Series Wireless Controller or Provision a Cisco AireOS Controller.

  4. Provision the APs under the wireless controllers.

    Ensure that APs have the correct SSID. For more information on AP provisioning, see Provision Cisco APs on day 1.

Step 4

For a scenario with one foreign and two anchor wireless controllers, do these steps:

  1. Assign the newly created wireless profile to the sites managed by both wireless controllers (foreign and anchor).

    • From the main menu, choose Design > Network Profiles

    • Choose the profile and click Assign Site. For information on creating sites, see Create, edit, and delete a site.

  2. Provision the foreign wireless controller.

    • Choose the wireless controller role as Active Main WLC and select the Managed AP location(s) (select both foreign and anchor sites).

    • Configure other advance settings, if required, and deploy.

    For more information on provisioning wireless controllers, see Provision a Cisco Catalyst 9800 Series Wireless Controller or Provision a Cisco AireOS Controller.

  3. Provision the anchor wireless controllers.

    • Choose the wireless controller role as Anchor WLC and select the Managed AP location(s).

    • Configure the interface details.

    • Configure other advance settings, if required, and deploy.

    For more information on provisioning wireless controllers, see Provision a Cisco Catalyst 9800 Series Wireless Controller or Provision a Cisco AireOS Controller.

  4. Provision the APs under the wireless controllers.

    Ensure that APs have the correct SSID. For more information on AP provisioning, see Provision Cisco APs on day 1.

What to do next

After provisioning, Catalyst Center automatically creates a mobility tunnel between the anchor and foreign wireless controllers. Use the show wireless mobility summary command on each of the controllers to verify the mobility tunnel status. This is a sample output of the command:

Show wireless summary command output for anchor/foreign wlc

Verify these mobility configurations on the wireless controllers:

  • Both wireless controllers have the same WLAN and policy profile.

  • The policy tag is created on foreign wireless controller and mapped to the AP.

  • The VLAN interface is created for the anchor wireless controller and is mapped to the policy profile.

Delete the anchor/foreign setup

To delete the anchor and foreign setup, do these steps:

  1. Ensure that the mobility tunnel between the anchor and foreign wireless controllers is in up state.

  2. Delete the SSID that was created for the wireless network.

    1. From the main menu, choose Design > Network Settings

    2. Click the Wireless tab.

    3. From the left hierarchy tree, choose Global.

    4. In the SSID table, choose the SSID and click Delete.

  3. Provision the foreign wireless controllers.

    In the provision Summary window, ensure that the SSID details are removed.

    After provisioning, Catalyst Center automatically deletes the mobility tunnel between the anchor and foreign wireless controllers and the WLAN and policy profile is deleted on all the wireless controllers.

AP management use cases

These topics help you understand the AP management use cases for wireless networks.

AP configuration

You can do these tasks for APs in Catalyst Center:

  • Configure AP-level parameters and radio-level parameters for APs.

  • Schedule recurring events for APs.

  • Configure APs using existing templates.

For more information, see AP configuration in Catalyst Center.

AP refresh

You can replace old AP models with new AP models using Catalyst Center. You can replace both provisioned and unprovisioned old APs with new ones in Catalyst Center. For more information, see AP Refresh workflow.

Skip AP provision during wireless controller provisioning

When you provision a wireless controller, by default, Catalyst Center also provisions the associated APs that are already provisioned. Based on the available number of devices, provisioning all the APs associated with the wireless controller may take several minutes.

Catalyst Center uses policy tags, site tags, and RF tags to push the wireless network configurations to individual APs through Cisco Catalyst 9800 Series Wireless Controllers.

For the first-time provisioning, Catalyst Center configures both the custom and Catalyst Center-generated site tags, policy tags, and RF tags only during the AP provisioning. For more information about the tag and flex profile configurations, see Overview of AP groups, flex groups, site tags, and policy tags.

This figure shows how Catalyst Center processes the tags.

Catalyst Center tag processing for Cisco 9800 Series Wireless Controllers

For information about the tags on the wireless controller, see Understand Catalyst 9800 Wireless Controllers Configuration Model.

This table lists the tags and the associated tag information during the first-time provisioning of wireless controller and APs:

Tag

Design window

Wireless Controller provision (with the Skip AP Provision unchecked)

AP provision

Policy tag

Design > Network Settings > Wireless > SSIDs

Autogenerated names for WLAN profile and policy profile are created.

Policy tags with the required WLAN profiles are created.

Site tag

AP profile: Design > Network Settings > Wireless > AP Profiles

Custom site tag and flex profile: Design > Network Profiles > Add Profile > Wireless > Advanced Settings > Provision Group

For nonflex configurations, an AP profile mapped to the custom site tag is created.

Note

 

The site tag is created and associated with the AP profile during AP provisioning.

For nonflex:

  • Site tags are created.

  • Nondefault AP profile is generated for ROW APs.

  • Nondefault AP profile is generated for mesh and OEAP sites.

For flex configurations, intent configurations defined in the feature template with IP Overlap enabled and native VLAN configurations are created.

For flex, a nondefault flex profile is created.

RF tag

Design > Network Settings > Wireless > RF Profiles

No change

RF tag and RF profiles are created.

If you modify any configuration that needs wireless controller reprovisioning but doesn’t need an AP reprovision (for example, if you add a new building to an existing area), you can use the Skip AP Provision option to avoid the longer processing time while reprovisioning the wireless controller. If you check the Skip AP Provision check box during the wireless controller reprovisioning, Catalyst Center doesn't reprovision the existing APs and the APs managed by the wireless controller. However, the newly added APs are provisioned.

This table lists the tags and the associated tag information during the wireless controller and AP reprovisioning:

Tag

Design window

Wireless Controller provision (with the Skip AP Provision unchecked)

AP provision

Policy tag

Design > Network Settings > Wireless > SSIDs

  • WLAN profile and policy profile mappings are configured.

  • Updates to policy tags are configured for the provisioned APs.

  • Updates to the policy tag name are configured for the provisioned APs.

  • Policy tags with the required profiles are configured.

  • Updates to the policy tag name are configured.

Site tag

AP profile: Design > Network Settings > Wireless > AP Profiles

Custom site tag and flex profile: Design > Network Profiles > Add Profile > Wireless > Advanced Settings > Provision Group

Updates to site tags are configured for the provisioned APs.

Site tag, flex profile, and AP profile are created or configured.

RF tag

Design > Network Settings > Wireless > RF Profiles

Updates to the RF profile are configured.

RF tags are configured.


Note

If there are no provisioned APs on a floor, tags aren’t configured on the floor during the wireless controller reprovisioning.

Automated tagging for flapping APs

Catalyst Center supports automated tagging for flapping APs. When an AP flaps more than 10 times in 6 minutes, Catalyst Center assigns the AUTO_INV_EVENT_SYNC_DISABLED tag to the AP automatically. When the AP is assigned with this tag, any event on that AP is discarded. This tag prevents the unnecessary wireless controller synchronization to update the AP information for flapping APs.

If this AP doesn't flap for 10 minutes, Catalyst Center removes the AUTO_INV_EVENT_SYNC_DISABLED tag automatically.

You can view the logs for the tagging and untagging of APs on the Audit Logs window.

After the underlying cause of the AP flapping is resolved, we recommend that you perform a manual synchronization to immediately reflect the most current AP details. Alternatively, wait for the next scheduled synchronization to update the AP information.

Configure ROW APs

Use this procedure to configure the Rest of World (ROW) domain APs.

Procedure

Step 1

Create an AP profile with the necessary country code and configure custom site tags. For more information, see Configure additional settings for an AP profile for Cisco IOS XE devices and Add AP groups, flex groups, site tags, and policy tags to a network profile.

Note

 

If you don't create an AP profile, Catalyst Center automatically generates the AP profile with the country code of the selected site and site tags for the ROW AP during AP provisioning or AP PnP onboarding.

Step 2

Add support for the country of operation to the country list on the wireless controller. You must configure at least one site from the country of operation as the managed AP location for the wireless controller. For more information, see Provision a Cisco Catalyst 9800 Series Wireless Controller.

Step 3

If the wireless controller is not already provisioned with the configurations in Step 1 and Step 2, provision the wireless controller. For more information, see Provision a Cisco Catalyst 9800 Series Wireless Controller.

Step 4

Configure the AP parameters. For more information, see Configure APs.

Step 5

Provision the AP. For more information, see Provision Cisco APs on day 1.

Note

 

Onboarding a ROW AP to a site with existing APs may disrupt the services of the existing APs for a brief period.

What to do next

To verify the AP configuration, use the show ap summary command. This is a sample output of the command.

This command displays the country code (CC) and regulatory domain (RD) for the APs. For ROW APs, the regulatory domain is -RW.


Note

For a ROW AP, if the country code in the command output is --, it indicates that the country code is not available for the AP. The operational status of all the radios for the ROW APs without a country code is down. You must provision the ROW AP to configure the country code for the ROW AP.

Configure wireless mesh network

In a Cisco wireless mesh network architecture, APs operate in one of these ways:

  • Root APs (RAP): Connected to the wired network.

  • Mesh APs (MAP): Communicates with other MAPs and RAPs using wireless connections.

The workflow for configuring a wireless mesh network involves these main steps:

  1. Wireless controller provisioning: Configure a mesh profile, configure the AP authorization list and provision the wireless controller.

  2. AP configuration: Configure AP in bridge mode and deploy.

  3. AP provisioning: Configure the mesh role for AP (RAP or MAP) and provision the AP.

Before you begin

All APs are configured and shipped as MAPs. To use the AP as a RAP, you must reconfigure it as a RAP during AP provisioning. A mesh network must contain at least one RAP. For more information on Cisco Wireless Controller configuration and AP configuration for wireless mesh networks, see About wireless mesh networks.

Procedure

Step 1

In the Catalyst Center device inventory (Provision > Inventory), ensure that the wireless controllers and APs are in managed state and assigned to the respective sites.

Step 2

Create an AP profile with mesh settings. For more information, see Configure mesh settings for an AP profile for Cisco IOS XE devices and Configure mesh settings for an AP profile for Cisco AireOS devices.

Step 3

Add the AP Ethernet MAC address to the AP authorization list. For more information, see Create an AP authorization list.

Step 4

Provision the Cisco Wireless Controller. For more information, see Provision a Cisco Catalyst 9800 Series Wireless Controller and Provision a Cisco AireOS Controller.

In the provision configuration window, select the AP Authorization List defined in Step 3 and choose the option for authorizing only the mesh access points.

Step 5

(Optional) In the Configure Access Points workflow, select the APs and change the AP mode to Bridge/Flex+Bridge mode if they are in Local/Flexconnect mode. For more information, see Configure APs.

Step 6

Provision the APs. For more information, see Provision Cisco APs on day 1.

  • For RAPs, choose the Mesh Role as RAP (Root AP).

  • For MAPs, choose the Mesh Role as MAP (Mesh AP).

What to do next

You can verify the mesh configurations on the Cisco Wireless Controller using these commands:

  • AP Ethernet MAC address: show run | inc username.

  • AP mesh role (MAP/RAP) after provisioning: show wireless mesh ap summary.

  • Site tag details: show wireless tag site detailed <site tag name>.

  • AP profile: show run | section ap profile.

  • Wireless mesh configurations:

    • show wireless profile mesh summary

    • show wireless profile mesh detailed <mesh profile name>

AP replacement using RMA workflow

You can replace a faulty access point in the network using the Catalyst Center Return Material Authorization (RMA) feature. The RMA workflow lets you replace failed devices quickly, thus improving productivity and reducing operational expense. For wireless APs, the replacement device is assigned to the same site, provisioned with primary wireless controller, RF profile, and AP group settings, and placed on the same floor map location in Catalyst Center as the failed AP.

For more information, see Replace a faulty access point.

Wireless controller migration use case

This topic helps you understand the migration use case for Cisco Wireless Controllers.

Migrate Cisco AireOS Wireless Controller to Cisco Catalyst 9800 Series Wireless Controller

You can migrate from Cisco AireOS Wireless Controller to Cisco Catalyst 9800 Series Wireless Controller using the Learn Device Configurations workflow on Catalyst Center. Migration is achieved by using the workflow to learn the device configurations from the wireless controller to be migrated and provisioning the new wireless controller with the learned configurations.


Note

This workflow is being deprecated.

For more information, see Migrate Cisco AireOS Controller to Cisco Catalyst 9800 Series Wireless Controller using Catalyst Center.