Country/Region Mismatch under managed APs since upgrading to 6.2.2.

[James_G]

Since upgrading to FortiOS 6.2.2 on 80D I get "Country/Region Mismatch" warning under managed FortiAP. I am trying to set everything to GB, to that end I have changed config wireless-controller setting to "set country GB", and I have changed the FortiAP profile to "set ap-country GB" - this is on the FAP321C UK profile, but I still get the mismatch warning. Am I missing anything else, do I need to set GB elsewhere in config? Extract from my config below:

config wireless-controller setting set country GB set darrp-optimize-schedules "default-darrp-optimize" end

config wireless-controller wtp-profile edit "FAP321C UK" config platform set type 321C end set handoff-sta-thresh 30 set ap-country GB config radio-1 set band 802.11n set frequency-handoff enable set ap-handoff enable set vap-all disable set vaps "dsfeswfre" "wfewfew" "wfewfewg" set channel "1" "6" "11" end config radio-2 set band 802.11ac set vap-all disable set vaps "dsfeswfre" "wfewfew" "wfewfewg" set channel "36" "40" "44" "48" end next end

[rms2018]

Hi Ede,

I am having the same issue with a FAP-423E, it's showing Vietnam as a RegCode.  I've spoken to support and they are not able to help me reset it. Your prior response stated that support used a password protected CLI command to do this.  Can you elaborate a bit more on that?  Any info that you can provide would be really appreciated.  I have 3 APs that are all having this issue and I really don't want to trash them.  They were purchased over a year ago and I didn't realize that they were running on the wrong country code until recently.  Thanks!!

[ede_pfau]

As I've posted then, I opened a support call (via web chat to keep it simple) for this. The friendly guy at the other end first changed the region setting to "US" and then back to "International". That did the trick. I was able to set the correct region setting afterwards.

I could not flip this setting myself as it requires a password, input on the CLI. (So somehow support needs to get access to the AP's CLI).

You may refer the supporter to this post as proof that this procedure exists.

[rms2018]

Hi, I've tried that and referenced the ticket and support wasn't able to help out.  I am not sure what the command is that allows for this via the CLI and I was hoping support would be able to investigate this forum and look into the case to figure it out but they didn't do so.  I've ended up with 3 FortiAP 423-E that I can't use, they're now sitting in their boxes.  It's too bad support can't help me with this.  I will try again but I am doubtful that they will help.  Thanks again!

[Admin_FTNT]

There is a recent Knowledge Base article "Technical Note: Region code mismatch on FortiAP" which describes the steps to take if you have a mismatched country and region.

[James_G]

Admin_FTNT wrote:

There is a recent Knowledge Base article "Technical Note: Region code mismatch on FortiAP" which describes the steps to take if you have a mismatched country and region.

The units I had issues with are 5 years old, but still under support, should I go back to the original reseller, as I didn't notice issue until 6.2 was released and made the issue visible?

[James_G]

I have spoken to re-seller, who will take up with distributor, who will take up with Fortinet

Possibly I will get some replacements for 4 year old AP's for free??!?!