FortiAP devices are thin wireless access points (AP) supporting the latest Wi-Fi technologies (multi-user MIMO 802.11ac Wave 1 and Wave 2, 4x4), as well as 802.11n, 802.11AX , and the demand for plug and play deployment.
Article Id 240632
Description This article describes why FortiAP - UF series devices cannot be recognized by FortiGate.
Scope Any supported version of FortiGate.

Change-out-of-box-FAP-U-boot-image FAP-UXXXF (2022):


Some FortiAP-UF devices cannot be recognized by FortiGate devices because running from the factory to FortiWLC compatibility mode.


It is noticeable when the due device is rebooting by itself constantly every 2-3 min, even if it can get an IP address from a local DHCP server.


To confirm this behavior, connect on to the FortiAP-F device by CLI using the serial port (set port speed to 115200) and observe device outputs carefully in search of the following messages:


01/01 00:01:54.373] Current boot flags: auto learning OFF image id Meru Sec

[01/01 00:01:54.373] Probably Primary Meru image is corrupted, please upgrade!!


Now this kind of device have been locked from the factory so, it is not possible to change it using the CLI interface.


CwDiscoveryTask.745 CwDiscoveryTask:: Interface does not have the IP

Login Failed

Enter Login Password:



[01/01 00:03:13.437] INIT: Discovery: Changed infrastructure mode to Wired (from Mesh-PnP)

CwDiscoveryTask.745 CwDiscoveryTask:: Interface does not have the IP

Login Failed

Enter Login Password:


If attempting to use SSH, it should be asked to provide the same credentials before seeing any message.


Just take note of the device IP address reported on CLI messages or the DCHP server and use it to access the GUI interface as instructed in this previous article:


Try Fortinet Secondary image if the primary image fails to load on the first attempt.


After successfully changing the boot mode, it is suggested to proceed to the upgrade of the latest version available. Note that it is necessary to go in sequence 6.2.1, 6.2.2, etc. 


Note that between 6.2.1 and 6.2.2, it is mandatory to upgrade to an intermediate service version 4001. It is possible to download it from the support portal using the related support credentials:


This is important because if the correct sequence is not followed between versions 6.2.1 and 6.2.2, the device will fail to load the update or the memory may become corrupted. In this case, the device may need to be physically replaced.