Skip to main content
Cisco Meraki

MR Regulatory Domains


Cisco traditionally sells a unique product SKU per country/territory. These devices have features enabled or disabled as necessary. Cisco Meraki’s philosophy is making IT simple and a software implementation is used to automatically set the right features based on the identified regulatory domain for an MR. This simplified software implementation allows Meraki to ship a single SKU worldwide and is applicable to MR access points (APs) and MX security appliances with Wi-Fi (MX-W) capabilities.

MX Products will not support a manual override of the regulatory domain, please contact support in case of alerts. For more information follow this link.

The regulatory behavior defined in this document does not apply for LTE and users may need to buy region-specific products for LTE support with MX devices.


Regulatory Domain Setting for a Device 

A device's regulatory domain is determined based on the ship-to location when a device is sold and the IP geo-location (Geo-IP) when the device checks into the dashboard. If the ship-to country or subsequent Geo-IP lookup for a specific node does not match the network country, an error will be shown in the dashboard and users must take corrective action. Devices and dashboard networks can only function in one country at a time.

From a device management perspective, it is recommended to create separate dashboard networks per geographical area or country per building, floor, etc., and assign devices to those networks accordingly. A more in-depth conversation about the dashboard organization and network is discussed in the Cisco Meraki Best Practice Design document.

If new APs are added to a network and this causes a regulatory mismatch, the new APs will alert about the regulatory mismatched and the AP will be placed in the network’s configured country.


Regulatory Domain Setting for a Network

The regulatory domain of a network is determined by the network country. It can be set manually after a network is created or can be automatically determined when devices are deployed into the network. The regulatory domain can be set manually by navigating to Network-wide > General > Country/Region and selecting the appropriate country.

The first device added to the network is used to determine the country if it is not manually set. This will also automatically set the regulatory domain for the network.

Regulatory domain enforcement

There are two different ways to enforce the regulatory domain to the Access Points:

  • Automatic (done by the dashboard, recommended).

  • Manual enforcement.


As explained before, regulatory enforcement is done per Geo-IP Location and network-wide setting automatically. The user only defines the country when creating the network and that will be the source of truth when compared to the GeoIP location, any mismatches will generate alerts. If all the nodes in the network are detected (via geolocation) to be in the same country, the network country is updated automatically to this detection.

Usually, this configuration will be correct except special cases where the IP of the gateway is located in a different country, (due to VPN, MPLS, etc).


A user can agree to use the manual regulatory enforcement in order to bypass the Geo-IP location and enforce the desired regulatory domain of a specific country manually.


In order to do this, a legal agreement must be accepted specifying the user is responsible to enforce the right regulatory domain to be used on the network acknowledging the physical location of the Access Points will match the specified.


Go to Network-Wide > General, a new option is presented to change to “Manual country setting”


Screen Shot 2021-11-15 at 5.15.17 PM.png


After clicking on it, the legal agreement will be presented, please, make sure to read it and understand it fully before accepting.

Screen Shot 2021-11-15 at 5.17.09 PM.png

Once accepted, two new options will be presented in the “Manual enforcement options” section:


  • Override APs to match network

    • This setting will enforce the country selected to all access points disregarding the GeoIP location of the Access Point.

  • Revert network to auto-detection

    • This option will enforce the automatic regulatory domain of the network as before.


Screen Shot 2021-11-15 at 5.19.37 PM.png

The country defined in the network can also be changed at this point.


To verify the country of the access point go to Wireless > Access Points, select the desired one and Regulatory Info can be seen with the country enforcement. For example:

Screen Shot 2021-11-15 at 5.20.19 PM.png



Manual Country Mismatch Alert

Screenshot at Jan 31 11-02-00.png

In order to clear this type of alert, please follow these steps:

Step 1. Check the AP physical location's country with the network administrator

Step 2. Confirm that all the APs within the network are installed in the same country. If not, separate the APs within different networks per country location.

Step 3. Navigate to Network-wide > CONFIGURE > General > Network Location and ensure that the Country/Region setting is using the actual AP physical location's country. 

In this case, the AP’s network is physically located in Mexico, but the AP-name device at some point was manually configured in US, triggering the alert.

Screenshot at Jan 31 11-04-20.png

Step 4. Once we confirm that the AP-name is in fact located in Mexico, or whichever country is configured under Country/Region, click Override APs to match network. 

Screenshot at Jan 31 11-05-33.png

That pushes the correct country configuration and will clear the Manual country mismatch alert.


Be aware the country configured must always match the country where the Access Points are physically located.

Country Detection Mismatch Alert

Screenshot at Jan 31 14-40-13.png 

Follow these steps to clear the country detection mismatch alert:

Step 1. Check the APs physical location's country with the network administrator.

Step 2. Confirm that all APs within the network are installed in the same country. If not, separate the APs within different networks per country location.

Step 3. Navigate to Network-wide > CONFIGURE > General > Network Location and ensure that the Country/Region setting is using the APs physical location's country. 

If the Country/Region is not correct, you have two options to fix it:

Option A.

If all the APs are detecting the same country and it’s correct, you can use the auto-detection feature. To do so, select Revert network-to auto-detection. 

Auto-detection uses the geoIP location of the public AP’s IP address to configure the country/region of the network and all the APs within. You can use neustar geolocation lookup tool to confirm the public IP detected location. If you suspect there's an error in neustar, please reach out to Meraki Support.

Screenshot at Jan 31 14-42-42.png


Option B. 

Manually select the Country/Region to the right option and override the APs to match network and click Override AP’s to match network.

Screenshot at Jan 31 14-45-31.png


If the country is already correct:

Click Override APs to match the network. That’ll clear the alert and push the right config to the APs.

This option is generally used when the AP’s use a VPN tunnel and reach the internet through a country different from where they are located.

In this example, the APs are physically located in the US, but they use a VPN tunnel to reach the internet through Mexico. We override the APs to the US, since that’s their physical location’s country.

Screenshot at Jan 31 14-52-40.png

Be aware the country configured must always match the country where the Access Points are physically located.

  • Was this article helpful?