FAP-221C - offline/disconnected

[sanderl]

On a Fortigate 60E with v6.2.3 - build1066 I have 3 FAP-221C FortiAP's successfully "connected". Thus 3 AP's have a fortiprofile connected to them and are working and having clients etc.

Now when I want to connect a 4th FAP-221C I have issues. Whatever I tried I can't get this AP "connected". The AP has the latest FW 6.0 Build 0044. I upgraded it via CLI (via 192.168.1.2 etc). If connected that way I can login via SSH and via browser. I have done "factoryreset" and cfg -x the AP and it boots up via POE and via 12V (if I go to it via 192.168.1.2) etc.

But when connected to the same interface as the other 3 AP's, having an IP address, can ping from Fortigate, etc. It just does not get "connected"...

What can be wrong? the only thing different is that the 3 working APs are model "FAP-221C-E" and the problematic one is "FAP-221C-I"...

Please help me out :)

EDIT: Now after 1 hour... I see to great astonishment that the AP is sending out a "test123" SSID... just out of the blue despite the FAP has been factory defaulted multiple times via CLI and via the "paperclip... I can successfully connect to that test123 SSID and access my local network instantly without any password... and in the Fortigate everything is the same Ehm... What the heck?

[Dave_Hall]

 The country code can be globally set via the wireless-controller, but you can always set the country code via individual FortiAP profile.

 

sanderl wrote:

Dave, that are settings for the controller, not the AP.

[sanderl]

Dave, it is not the WLC controller country code thats wrong, it is th country code in the AP that is currentl set to "I" whih is internnational and as such is set correctly because the AP is "stickered" with FAP-221C-I. My ask is if this country code, thus the code of the AP can b changed to an "E" for Europe. such as it becomes a FAP-221C-E.