Global Use Access Points

Global use access points

Global use access points (APs) are network devices that

  • enable usage in both Meraki cloud native networks and Catalyst on-premise controller-based networks

  • involve a single product ID (PID) for simplified logistics, and

  • decouple PID or SKU from regulatory domains and boot modes.

Previously, the Cisco Catalyst AP portfolio comprised around 16 product IDs (PIDs), each tailored to a specific regulatory domain supported by Cisco. The Rest of World (RoW) AP introduction has streamlined this to nine PIDs, with RoW APs allowing country-specific configurations. Non-RoW PIDs are designed for regions with stringent rules against end-user configurations.

Regulatory compliance and global use AP

The pivotal aspects that the Global Use AP addresses for Catalyst and Meraki Cloud setups are the AP mode of operation and the adherence to Cisco Regulatory Domain requirements, ensuring compliance with regulatory standards on radio channel usage and power limits across different geographical bands.

Best practice: Global use AP benefits

Global use APs offer numerous advantages that enhance network management efficiency and flexibility. The benefits of global use APs are

  • One PID to order Cisco Catalyst or Meraki mode APs

  • Seamless provisioning

  • Easily transition from Catalyst mode to Meraki mode to meet network needs

  • Reduce complexity with no reliance on country-specific SKUs

AP mode of operation

You can easily provision your APs to operate for Cisco Meraki Cloud or Cisco Catalyst on-premise mode deployments. You can do so at the time of initial deployment or even after the deployment.

Definition and role of Cloud ID in device workflows

This document explains the concept of Cloud ID, its origin, and its role in the Meraki device claim workflow.

What is Cloud ID?

Cloud ID refers to the identifier used in the Meraki device claim workflow starting from the Cisco Wireless 917x series AP onward. It represents the Meraki Serial Number and is crucial for the Meraki device claim process.

Key attributes of Cloud ID

  • The Cloud ID is prominently displayed on the AP label, AP packaging, QR code, and other materials.

  • It serves an integral role in the workflow for device claims within Meraki-managed networks.

Onboarding processes for Wi-Fi 7 APs

This section describes how to connect Cisco Catalyst 917x Wi-Fi 7 APs (CW917x) to the Meraki Dashboard and the Cisco Catalyst 9800 Wireless LAN Controller.

Summary

This process involves connecting the APs to the Meraki Dashboard and migrating them to the Cisco Catalyst 9800 Wireless LAN Controller.

The key components involved in the process are

  • Cisco Catalyst 917x Wi-Fi 7 APs (CW917x): They need to be connected to the Meraki Dashboard.

  • Meraki Dashboard: Initial management platform for onboarding APs.

  • Cisco Catalyst 9800 Wireless LAN Controller: Final migration destination for managing APs.

Workflow

These stages describe connecting the APs to the Meraki Dashboard and migrating to the Cisco Catalyst 9800 Wireless LAN Controller.

  1. Stage 1: Connecting the APs to the Meraki Dashboard
    • Claim devices on the dashboard using either an order number, Cloud ID, or MAC address and power on the CW917x series APs through PoE or a Power Injector.
    • The Meraki Dashboard lists the APs when they start up.

    Note

    Ensure there are no DHCP, DNS, or PnP configurations that can lead the CW917x AP to the controller.
  2. Stage 2: Migrating the APs to Cisco Catalyst 9800 Wireless LAN Controller
    • Option 1: If there is internet connectivity from the CW917x series APs and you have a Meraki dashboard account, ensure the APs join the Meraki Dashboard, and then migrate the APs to the controller.
    • Option 2: Offline Migration or Fast Offline Migration is used when the CW917x APs join the controller without internet connection.
      • Offline Migration uses DHCP/DNS options and requires zero change on the existing network.
      • Fast Offline Migration uses new DHCP/DNS options and bypasses checking the Meraki cloud prior to looking for a controller.

    Note

    When there is no Fast Offline Migration, the CW917x AP searches for the cloud for eight minutes. At the end of the eighth minute, it checks and confirms the presence of the controller with the IP address obtained through DHCP and DNS through CAPWAP Discovery/Response before migrating to controller management mode.

    The 8-minute window is only for Day-0 mode when the AP is trying to discover a cloud or controller. Any subsequent reboots, for example, an image upgrade scenario, do not involve a wait time. You can use the Fast Offline Migration techniques, where the period of eight minutes is omitted.


    Note

    Ensure your Cisco Catalyst 9800 Controller has IOS-XE version 17.15.2 for CW9178I, CW9176I, and D1 APs. The controller network must also be reachable from the AP subnet.

    The migration methods are prioritized in this order
    • Fast Offline Migration
      • DHCPv4
      • DNSv4
      • DHCPv6
      • DNSv6
    • Local Status Page
      • You can manually migrate the APs through the Local Status Page of the AP when Fast Offline Migration options are not available.
    • Offline Migration
      • DHCPv4
      • DHCPv6
      • DNSv4
      • DNSv6
      • Broadcast/Multicast Discovery

Result

APs successfully transition from initial setup in the Meraki Dashboard to established operational management under the Cisco Catalyst 9800 Wireless LAN Controller, ready for enhanced performance and control.

Fast offline migration

This task guides you through the process of executing a fast offline migration using DHCPv4, DHCPv6, DNSv4, and DNSv6 configurations to ensure network stability and performance.

This procedure is essential for network environments requiring quick migration of Access Points (APs) to a new controller mode, leveraging DHCP and DNS configurations.

Perform these steps for a fast offline migration.

Procedure

Step 1

DHCPv4: The fast offline migration for DHCPv4 is Option 43.

The syntax for the option 43 string is F3 <size> <IP array> Mode=<1|2>, where Mode 1 is Meraki and Mode 2 is Catalyst.

  1. To change the existing option 43 string f104.ac10.0118 to f305.ac10.0118.02, do the following:

    • Change type from f1 to f3,

    • Change length from 04 to 05,

    • Add the sub-option 01 for Meraki or 02 for Catalyst.

  2. For controller discovery using DHCPv4, enter the following IOS/IOS XE configuration example:

    ip dhcp pool vlan192
                                    network 192.168.200.0 255.255.255.0
                                    default-router 192.168.200.1
                                    option 43 hex hex f305.ac10.0118.02

  3. In the Windows server configuration, choose DHCP > IPv4 > Scope Options.

  4. From the list of option names, select 043 Vendor Specific Info and click Configure Options.

    The Scope Options window is displayed.

  5. Choose the General tab and select the 043 Vendor Specific Info checkbox from the Available Options.

  6. Click OK.

Note

 

Ensure that at least one IP from the IP array is reachable via Internet Control Message Protocol (ICMP) or CAPWAP. The AP tries to contact the controller through pings. If the controller responds, the AP migrates to the controller management mode, otherwise the AP tries a CAPWAP discovery.

Step 2

DHCPv6: The fast offline migration for DHCPv6 involves configuring Option 52 and Option 17.

Note

 

Configure Option 17, where the Enterprise ID is 29671, Subcode is 1, Mode is either 1 (Meraki), or 2 (Catalyst vendor-specific 29671). Option 52 (standard) is IPv6 array.

  1. In the Windows server configuration, choose DHCP > IPv6 > Scope Options.

  2. From the list of option names, select 00052 capwap ac-address and click Configure Options.

    The Scope Options window is displayed.

  3. Choose the General tab and select the 00052 capwap ac-address checkbox from the Available Options.

  4. Click OK.

  5. To configure Option 17, choose DHCP > right-click IPv6, and select Define Vendor Classes.

    The DHCP Vendor Classes window is displayed.

  6. In the DHCP Vendor Classes window, create a new class.

  7. In the New Class window, enter the Display Name, enter the Vendor ID as 29671, and enter the ASCII value as Cisco Wireless AP CW9178I, for the CW9178I platform.

    Note

     

    For CW9176I and CW9176D1, use the following ASCII strings, respectively, Cisco Wireless AP CW9176I and Cisco Wireless AP CW9176D1.

  8. Click OK.

  9. Choose DHCP > right-click IPv6, and select Set Predefined Options.

    The Predefined Options and Values for v6 window is displayed.

  10. In the Predefined Options and Values for v6 window, click Option Type.

    The Option Type window is displayed.

  11. In the Option Type window, in the Code field, enter 1 and then click OK.

  12. Click OK.

  13. Choose DHCP > IPv6 > Scope Options > Configure Options.

    The Scope Options window is displayed.

  14. In the Scope Options window, click the Advanced tab.

  15. From the Vendor class list, select the vendor class.

  16. From the Available Options, check the 00001 fast-conversion checkbox.

  17. In the Data entry section, in the Byte field, enter 0X2.

  18. Click OK.

    Note

     

    Ensure at least one IP from the IP array is reachable via Internet Control Message Protocol (ICMP) or CAPWAP. The AP tries to reach the controller through pings. If the controller responds, the AP migrates to the controller management mode, otherwise the AP tries a CAPWAP discovery.

    The 00001 fast-conversion option is added to the list of Scope Options.

Step 3

DNSv4 and DNSv6: Fast offline migration using the migration string.

  1. Add a DNS record cisco-automigrate.<domain> in the DNS server.

    The AP checks for the cisco-automigrate.<domain> DNS entry.

    If the IP pings from DNS are successful, then the APs migrate immediately to the controller mode. If the pings fail, the AP tries the CAPWAP discovery method.

    Note

     

    For this method to work correctly, the DHCP server must return the domain-name option (option 15) to the AP.

Successfully configuring fast offline migration ensures that APs migrate quickly to the new controller mode, maintaining network stability and performance.

Offline migration

The AP uses the traditional discovery mechanisms of DHCP, DNS and broadcast/multicast, if it is not able to reach the Meraki Cloud, perform a Fast Offline Migration, or migrate using the Local Status page.

Prevent false or accidental migration

The purpose of this task is to guide users on preventing accidental or unauthorized migration of APs to a controller, ensuring network stability and security.

To prevent accidental or false migration, do the following:

Procedure

Step 1

Ensure that at least one IP in the IP address array returned by the DHCP option or the IP address of the resolved DNS entry is CAPWAP reachable. This CAPWAP response must include the controller version image for the CW917x AP to validate it and join the controller.

Step 2

Enter cisco-do-not-automigrate when setting the DNS entry to resolve the controller's IP address. When it is resolved, the AP does not migrate to the controller mode.

Step 3

You can configure commands to prevent the controller from responding to Day 0 CAPWAP discovery requests by CW917x APs. You can fine-tune its configuration based on its own deployment specification. Configuration is done in the AP Join Profile.

To prevent accidental or false migration, you must perform these configurations.

Device(config)# ap profile onboarding-prof
Device(config-ap-profile)# no capwap-discovery onboarding
Device(config-ap-profile)# exit

To respond to the CAPWAP discovery, use the following configuration:

Device(config)# ap profile onboarding-prof
Device(config-ap-profile)# capwap-discovery ?
onboarding  Configure CAPWAP onboarding related parameters
private     Include private IP in CAPWAP Discovery Response
public      Include public IP in CAPWAP Discovery Response

Device(config-ap-profile)# capwap-discovery onboarding ?
all      Configure automatic CAPWAP onboarding from Meraki based on both
unicast and broadcast discovery request
unicast  Configure automatic CAPWAP onboarding from Meraki based on unicast
discovery request only

By default the controller accepts only unicast requests for onboarding.

Note

 

If the CW917x APs have to be in the same subnet as the controller and use Broadcast (IPv4), or Multicast (IPv6) for discovery, then CAPWAP discovery onboarding should be set to all . Otherwise, the controller will not respond to Broadcast/Multicast discovery requests.

Completion of this task ensures that the APs are properly configured and do not unintentionally migrate to controller mode, preventing unauthorized network changes and maintaining system integrity.

Cisco regulatory domain

Determining the regulatory domain is very important for wireless AP deployments. Unlike the mode of operation, which is a choice that can be made by the customers, provisioning the regulatory domain follows some strict rules and guidelines. With single PID, regulatory domain is automatically determined from where the APs are deployed.

Country code and regulatory domain

A country code is an identifier that enables Wi-Fi 7 APs to operate in compliance with the regulations of the country where they are deployed. Regulatory domains ensure that APs adhere to local compliance requirements through methods such as

  • Compliance through geo-location: For APs operating in Meraki mode, regulatory standards are enforced using geo-location and network-wide settings.

  • Hardware-independent enforcement: With certain AP models, such as the CW917x series, compliance is achieved via software rather than hardware-specific SKUs allowing worldwide deployment.

Regulatory domain information is determined based on the location and country where APs are deployed.

Determining AP Location

Various methods exist for determining the location of APs, which affect regulatory domain information.

  • Meraki determined location: APs use IP addresses, shipping destinations, or dashboard configurations to reveal their location, essential for regulatory enforcement.

  • GPS/GNSS-based location: If an AP is unable to identify the country-of-presence through Cisco cloud, the AP makes use of GPS or GNSS-based location. When the AP is located close to the open sky and there are enough satellites to get a location fix, the AP tries to use the satellites to locate country of operation.

  • Proximity-based AP location: The proximity-based AP location method is useful for determining AP location based on proximity to other Cisco APs, especially when the APs are unable to find their location using the standard location techniques.

    For example, Anchored APs are APs that are closer to the periphery of a building and may be able to receive GPS signals, whereas the Non-Anchored APs are APs located in the middle of building, which may not be able to receive signals. The controller learns about the neighboring APs using radio resource management (RRM). Using RRM, you can propagate the location from the Anchored APs to the Non-Anchored APs.

    This method is effective when the Wi-Fi 7 APs hear the Neighbor Discovery Protocols (NDPs) over 2.4 GHz from any other AP (Wi-Fi 7 or other APs) joined to the same controller.

    Proximity-based location determination is faster compared to the other approaches, such as GPS or GNSS-based location.

  • AP Regulatory Activation File: When automated methods are unsuccessful, a manual configuration via the appropriate activation file is implemented.

Examples of country code resolution

This document aims to provide detailed examples and explanations of the methods used by Wi-Fi 7 Access Points to determine and resolve their country codes, including GPS/GNSS-based location, proximity-based location, migration, and regulatory activation file methods.

These examples show how Wi-Fi 7 APs determine their country code

  • GPS/GNSS-based location: APs obtain geolocation via the integrated GPS/GNSS antenna. The CW917x series AP have a built-in GPS/GNSS. They can obtain the geolocation co-ordinates, as long as they can get a clear sky view, typically placed near a window, to obtain the satellite signal. The controller maps geolocation coordinates to the country. Until the AP obtains the country code, it will have -UN as the regulatory domain.

    For APs joining without domain the output displays -UN as the regulatory domain.

    For example, this show command displays the details of a Wi-Fi 7 AP which has the regulatory domain as -UN: 

    Device# show ap summary
Number of APs: 1
CC = Country Code
RD = Regulatory Domain

AP Name Slots AP Model  Ethernet MAC   Radio MAC      CC   RD   IP Address    State         Location
-------------------------------------------------------------------------------------------------------
AP-B2E0   4   CW9178I   c414.a26f.b2e0 c414.a26f.b2f0 --   -UN  20.20.20.52  Registered default location

    This show commands display the results after the controller determines the country code and the AP reloads and joins back with a country code: 

    Device# show ap name Wi-Fi7-AP-B2E0 config general | inc Country
Country Code                                    : US
Regulatory Domain Allowed by Country            : 802.11bg:-A 802.11a:-AB 802.11 6GHz:-B
AP Country Code                                 : US  - United States
Country Code Resolution Method                  : GPS


Device# show ap summary
Number of APs: 1
CC = Country Code
RD = Regulatory Domain
AP Name Slots AP Model  Ethernet MAC   Radio MAC      CC   RD   IP Address    State         Location
-------------------------------------------------------------------------------------------------------
AP-B2E0   4   CW9178I   c414.a26f.b2e0 c414.a26f.b2f0 US   -B  20.20.20.52  Registered default location

    Note

    In some deployment scenarios, without a clear sky view or with thick windows and neighboring buildings, the AP may take a long time or fail to obtain a GPS/GNSS signal. In such cases, other methods like Proximity, Migration, or Regulatory Activation File can be used to obtain the country code and regulatory information for the controller management mode.

    For greenfield deployments, we recommend that you use GPS/GNSS. Use Migration through Meraki Dashboard if you encounter issues obtaining the GPS/GNSS signal.

  • Proximity-based AP location: For brownfield deployments, if your APs cannot obtain the GPS/GNSS signal due to existing legacy APs, use proximity-based discovery. 

    Device# show ap summary
Number of APs: 2
CC = Country Code
RD = Regulatory Domain
AP Name  Slots AP Model  Ethernet MAC  Radio MAC       CC   RD   IP Address     State        Location
-----------------------------------------------------------------------------------------------------------
AP-B2E0    4     CW9178I c414.a26f.b2e0 c414.a26f.b2f0 --   -UN  20.20.20.52  Registered   default location
AP-E040    3     CW9176I 8c88.814f.e040 ecf4.0caf.6a60 US   -B   20.20.20.51  Registered   default location

    In the example above, the AP named AP-E040 has a country code and regulatory domain and the AP named AP-B2E0 that does not have a country code and regulatory domain, are in close proximity. AP-B2E0 learns its country code from AP-E040. The APs reload, after they learn their country code from the neighboring APs.

    This example displays the state of the AP after obtaining the country code:

    Device# show ap summary
Number of APs: 2
CC = Country Code
RD = Regulatory Domain
AP Name  Slots AP Model  Ethernet MAC  Radio MAC       CC   RD   IP Address     State        Location
-----------------------------------------------------------------------------------------------------------
AP-B2E0    4     CW9178I c414.a26f.b2e0 c414.a26f.b2f0 US  -B  20.20.20.52  Registered   default location
AP-E040    3     CW9176I 8c88.814f.e040 ecf4.0caf.6a60 US  -B  20.20.20.51  Registered   default location

    C9800-L# show ap name Wi-Fi7-AP-B2E0 config general | inc Country
Country Code                                    : US
Regulatory Domain Allowed by Country            : 802.11bg:-A 802.11a:-AB   802.11 6GHz:-B
AP Country Code                                 : US  - United States
Country Code Resolution Method                  : Proximity

  • Migration: When you migrate APs from Meraki Dashboard, the APs keep their existing country code.

    For greenfield users, where

    • there are no legacy deployments,

    • the deployment restrictions make it difficult to obtain the GPS or GNSS signal, and

    • there is easy workflow of migrating the APs to the controller mode for Day 0, and obtaining country information,

    we recommend the migration method.

    This example displays the country code resolution method as Installed via Meraki Dashboard

    Device# show ap name Wi-Fi7-AP-B2E0 config general | inc Country
Country Code                                    : US
Regulatory Domain Allowed by Country            : 802.11bg:-A  802.11a:-AB 802.11 6GHz:-B
AP Country Code                                 : US  - United States
Country Code Resolution Method                  : Installed via Meraki Dashboard

  • Regulatory Activation File: Download a Regulatory Activation File (RAF) from the Meraki Dashboard, that can be installed on the controller. See the section on Regulatory Activation File method for more details.

Regulatory activation file

The Cisco Meraki dashboard creates a regulatory activation file that has AP details such as the AP location, serial numbers, MAC addresses, country code, and site tags that can be imported to the controller via the Cisco Meraki Dashboard or saved to an external server or device.

To download the file from the Meraki Dashboard, choose Meraki Dashboard > Network-wide > General > Regulatory info > Download regulatory file.

Configure AP regulatory activation (GUI)

This task guides you through the process of activating the regulatory domain on APs that have not been factory-programmed with a specific regulatory domain, using the GUI.

Complete this task to activate the country code and regulatory domain of APs, which are in the worldwide mode.

Before you begin

To provision a specific regulatory domain on APs that are not factory-programmed with a regulatory domain, download the regulatory activation file from the Meraki dashboard.

Procedure

Step 1

Choose Administration > Regulatory Activation.

Step 2

Click the upload area to select the regulatory activation file from your local folder, or, drag and drop the file into the upload area.

Note

 

Ensure that you add a new file every time regulatory activation has to be performed.

Step 3

Click Upload to upload and validate the regulatory activation file.

A message indicates the activation file has been validated. The records display the AP MAC details, Country Code, Serial Number, and the following validation results:

  • Invalid Domain: In this mode, APs do not have a country code, resulting in an undefined (UN) regulatory domain. The country code from the activation file is applied to APs that match this condition.

  • Regulatory Mismatch: In this mode, APs have a country code, but the country code is not configured on the controller.

    Note

     

    To resolve a regulatory mismatch issue, enable the country code on the controller.

  • Not World Wide Mode: The APs in this mode are currently not affected by the regulatory activation process.

Step 4

Click Apply to start the activation process.

The activation process resolves the country code and regulatory domain of APs in Invalid Domain.

A warning message is displayed that the regulatory activation process will cause the joined APs to be non-operational and hence get disconnected.

Step 5

Click OK to start the process.

The process runs in the background. A message is displayed if none of the records is impacted by the uploaded regulatory activation file.

The result of this task is that the APs are configured with the appropriate country code and regulatory domain, ensuring compliance and operational readiness.

What to do next

Go to the Access Point Configuration page to monitor the results.

Configure AP regulatory domain (CLI)

The purpose of this task is to guide users through the CLI commands necessary to configure AP regulatory activation, ensuring compliance with regional regulations.

Procedure

Step 1

Enable privileged EXEC mode

Example:
Device# enable

Enables privileged EXEC mode. Enter your password if prompted.

Step 2

Apply the regulatory domain configuration

Example:
Device# ap regulatory activation apply

Applies the regulatory domain configuration.

Step 3

Clear all the AP MAC to country mapping records

Example:
Device# ap regulatory activation clear all

Clears all the AP MAC to country mapping records or a specific AP MAC to country mapping record.

Step 4

Configure the regulatory domain activation file

Example:
Device# ap regulatory activation file reg-ap-act.json

Configures the regulatory domain activation file.

This configures the activation file necessary for domain settings.

What to do next

Verify that the AP regulatory domain configurations are operational and comply with regional requirements.

Verifying regulatory activation

Describes the verification details of the regulatory activation feature.

Verifying Regulatory Activation Details for All APs

To verify regulatory activation details for all APs, run the following command:

Device# show ap regulatory activation all
Regulatory Activation file Meta-data
------------------------------------
Date Created     : 2024-06-28T08:55:13Z
Created By       : ciscoap.user@meraki.net/SSO
Device count     : 10
Organization Id  : 1130091
AP MAC              Serial Number      Country code
----------------------------------------------------
00XX.0a0X.5dXX       Q2XX-LUXX-DDXX       US   
00XX.0a0X.5fXX       Q2XX-MUXX-4RXX       US   
00XX.0a0X.01XX       Q2XX-ALXX-4UXX       US   
00XX.0a0X.63XX       Q2XX-G8XX-7WXX       US   
00XX.0a1X.0dXX       Q2XX-BBXX-ELXX       US   
00XX.0a1X.19XX       Q2XX-E8XX-ZZXX       US   
00XX.0a1X.1dXX       Q2XX-2LXX-FSXX       US   
00XX.0a1X.04XX       Q2XX-5RXX-AFXX            
00XX.0a3X.08XX       Q2XX-3YXX-D3XX       US   
00XX.0a1X.0aXX       Q2XX-5QXX-ERXX       US   
.
.
.
Verifying Regulatory Activation Details for Specific APs
To verify the regulatory activation details for specific APs, run the following command:
Device# show ap regulatory activation 38XX.79XX.9fXX
AP MAC          Serial Number         Country Code     
-----------------------------------------------------
38XX.79XX.9fXX  Q3XX-XKXX-F3XX

E-Label display

E-LABEL compliance status

A regulatory requirement for wireless APs is a set of standards that:

  • mandates compliance with evolving legal or formal regulations,

  • covers aspects such as operational frequencies and power levels, and

  • include the implementation of technologies like the "E-label" for compliance.

Starting with the Cisco IOS XE 17.18.1 version, the E-Label digital labeling feature became accessible via the controller's GUI. This feature enables seamless integration of new regulatory approvals concerning the E-Label compliance without necessitating physical modifications to the devices.

Feature history for access point upgrade management enhancements

Table 1. Feature history

Release

Feature Information

Cisco IOS XE 17.18.1

The E-Label digital labeling feature is accessible via the controller's GUI and enables seamless integration of new regulatory approvals for wireless APs.

Starting with the Cisco IOS XE 17.18.1 release, this digital labelling feature is available via the controller’s GUI, enabling seamless integration of new regulatory approvals without requiring physical modifications to the device.

E-Label compliance status of AP models

These are the AP models that support E-Label compliance status

  • Cisco Catalyst Wi-Fi 6 APs

  • Cisco Catalyst Wi-Fi 6E APs

  • Cisco Catalyst Wi-Fi 7 APs

Wi-Fi Technology

AP Model

Cisco Catalyst Wi-Fi 6 APs

Cisco Catalyst 9105 AXI/AXW APs

Cisco Catalyst 9115 AXI/AXE APs

Cisco Catalyst 9117 AXI APs

Cisco Catalyst 9120 AXI/AXE/AXP APs

Cisco Catalyst 9130 AXI/AXE/AXE-STA APs

Cisco Catalyst 9124 AXI/AXE/AXD APs

Cisco Catalyst Wi-Fi 6E APs

Cisco Catalyst 9136I APs

Cisco Catalyst Wireless 9166I/D1 APs

Cisco Catalyst Wireless 9164I APs

Cisco Catalyst Wireless 9162I APs

Cisco Catalyst Wireless 9163E APs

Cisco Catalyst Wi-Fi 7 APs

Cisco Catalyst Wireless 9178I APs

Cisco Catalyst Wireless 9176I/D1 APs

Cisco Catalyst Wireless 9172I/H APs

Configure AP E-Label compliance status (GUI)

Ensure regulatory compliance of the AP E-Label by configuring its status through the GUI.

This task involves verifying the compliance status of an AP E-Label via the GUI.

To configure the AP E-Label compliance status, perform these steps

Procedure

Step 1

Choose Monitoring > Wireless > AP Statistics.

Note

 

All the APs connected to the controller are automatically displayed.

Step 2

Click the AP to view the regulatory compliance status.

Step 3

Go to 360 View.

Step 4

Click the Click here for Legal and Regulatory information.

Note

 

This option will be under the AP Country Code detail.

A pop-up is displayed with the regulatory information for the selected AP, showing compliance details across various countries.