Description
Scope
Solution
This article explains how to find the root cause of the region code mismatch error on APs and to proceed to the right next action steps.
Region code mismatch on a FortiAP can cause FortiAP health showing up as poor or no channel assigned through FortiGate i.e the FortiAPs will not be serviceable.
If this error appears , the first action to do is to compare which region code FortiAP was ordered and the region code of FortiAP received.
The region code on an actual AP can be found in two different methods:
Silver Label: The region code will be mentioned on the silver label on the actual physical FortiAPs as shown below.
See the region code mentioned right after the model.
If the FortiAP is online on FortiGate the same can be checked using the command:# diagnose wireless-controller wlac -c wtpIf the access to the FortiAP using console/ssh/telnet, run the below command to confirm the same and find also the same o/p from https access to AP: # fap-get-status 
Scope
FortiAP W2/U
Solution
Every AP has a hard coded region information with Fortinet database and there are multiple other factors involved on the region code including the support and registration process, therefore it is not supported to change the region code of an AP.
- If your FAP order is requested with a proper region code but you received a wrong one, please contact the reseller to get the proper model through the CRA process.
- If your FAP order is requested with a wrong region code and you want to get the proper one, please contact the reseller to get the proper model through the CRA process.
- If FAP order is requested with a proper region and you received the proper one on the box, but the BIOS or Silver Label have mismatched SKU’s – Fortinet will replace to FortiAP via the RMA process.
A useful link to find supported countries and corresponding region code information is the 'Setting your geographic location' section in the 'FortiWiFi and FortiAP Configuration Guide' in the Fortinet Document Library.
