Technical Tip: Change FortiAP-U431F Boot image ID for FortiLAN Cloud deployment (GUI and CLI)

[laltuzar]

Description	This article describes how to change the FortiAP-U431F boot image to be  deployed automatically on FortiLAN Cloud.
Scope	FortiLAN Cloud. FortiAP-U431F v6.2, build 0220.
Solution	Note that the Image ID can be changed through 2 methods: GUI and CLI. This post will explain both methods. Changing Image ID using the CLI: 1) Connect to the FortiAP-U431F using a console cable. Make sure to use a speed rate of 115200, otherwise,  a distorted output will be visible. 2) Restart the FortiAP. 3) During the startup, press Ctrl+C combination to abort the u-boot on the specified output as in the example below. 4) Use the default password 'fap22b1!$' when prompted. 5) Execute the command 'print boot' to show the boot configurations. See that the Image ID is set to 'meru default image'. 6) Change the Boot image by entering the command 'set_image_id' 7) Execute the command 'set_image_id fap_primary'. Note that there are four options available for this command. 'fap_primary', 'fap_default' or 'fap_secondary' will be the options to deploy with FortiLAN Cloud. 8) Execute 'print boot' again to make sure the changes were performed successfully. 9) Restart the FortiAP by executing the command 'reset'. 9.1) If the FortiAP comes back again as 'meru default image', repeat the process but change to 'fap_default' or 'fap_secondary' as 7) suggests. ------------------------------- FortiAP-PU431F (DATE - TIME) Ver:XXXXXXX Serial Number:PU431FTHXXXXXX Region Code:N ------------------------------- Hit CTRL+c to abort u-boot in 3 seconds Please enter password: MG link 1G 0 u-boot> print_boot meru default image status: len 0x2640014, crc 0x0 AP version is 0.0.0 image status: New image image try count is 0 meru primary image status: len 0x0, crc 0x0 AP version is 0.0.0 unknow image status image try count is 0 fap default image status: len 0x2e00014, crc 0xb37aef52 AP version is 6.2.dc image status: New image image try count is 0 Image ID : meru default image Previous Image ID : meru default image Auto-learning : Turn ON u-boot> u-boot> set_image_id fap_primary Erasing at 0xc0000 -- 100% complete. u-boot> print_boot meru default image status: len 0x2640014, crc 0x0 AP version is 0.0.0 image status: New image image try count is 0 fap default image status: len 0x2e00014, crc 0xb37aef52 AP version is 6.2.dc image status: New image image try count is 0 fap primary image status: len 0x0, crc 0x0 AP version is 0.0.0 unknow image status image try count is 0 Image ID : fortinet primary image Previous Image ID : meru default image Auto-learning : Turn ON u-boot> reset Change Image ID using the GUI: 1) Enter FortiAP's GUI (default IP is 192.168.1.2) by connecting the FortiAP to a free port on a Switch. 2) By default, the AP will show the interface below with Image ID as 'MERU SECONDARY'. In order to change it so it can be deployed with FortiLAN Cloud (FORTINET PRIMARY or FORTINET SECONDARY), select Configure. 3) After loading the configure interface, change the Image ID to 'Fortinet Primary',select Apply. The FortiAP will reboot and come back with the correct image. 3.1) In case this does not work and the FortiAP comes back as 'MERU SECONDARY' again, try to use 'Fortinet Secondary' as Image ID instead. 4) After the FortiAP restarts, it should come back to the following default GUI. Use 'admin' as user and no password. Then log in and change the default password to a strong one. 5_ Once the default password is changed, log in again and see that now the FortiAP will start the registering process on FortiLAN Cloud. If the FortiAP has been added to FortiLAN Cloud, the registration process will start and complete automatically. 6) After a couple of minutes, the FortiAP correctly deployed on FortiLAN Cloud will be visible. FortiAP U431F online on FortiLAN Cloud FortiAP U431F online on FortiLAN Cloud Related documents: Troubleshooting Tip: Change out of box FAP-U boot image Undeploying a FortiAP device Adding a FortiAP device to FortiLAN Cloud with a key Managing FortiAP Configuring FortiAP settings Activating/Deactivating a FortiAP device If there are still problems, create a Customer Service ticket through the Support Portal.

[lwildgoose]

It's useful to note that the U-431F/433F wont accept an upgrade directly from 6.2.0 to either 6.2.4 or 7.0.0 whether you're upgrading from a Fortigate, FortiLAN cloud or directly on the AP via HTTP/TFTP.

This is due to the file structure changed introduced in build 4001, without installing this firmware first, the AP wont upgrade past build 0237 successfully.

I recommend following this upgrade path:

v6.2.0 build 0220 --> v6.2.1 build 0237 -->FAP_U433F-v6-build4001-FORTINET.out --> v6.2.2 build 0267 -->
v6.2.3 build 0281 --> v6.2.4 build 0307

6.2.4 Release Notes: https://docs.fortinet.com/document/fortiap-u/6.2.4/fortiap-u-release-notes/689796/special-notice

Or for 7.0.0

v6.2.0 build 0220 --> v6.2.1 build 0237 -->FAP_U433F-v6-build4001-FORTINET.out --> v6.2.2 build 0267 -->
v6.2.3 build 0281 --> v7.0.0 build 0031

7.0.0 Release Notes: https://docs.fortinet.com/document/fortiap-u/7.0.0/fortiap-u-release-notes/588560/upgrade-and-downgr...