|Description||This article describes how to change the FortiAP-U431F boot image to be deployed automatically on FortiLAN Cloud.|
FortiAP-U431F v6.2, build 0220.
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 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.
7) Execute 'print boot' again to make sure the changes were performed successfully.
8) Restart the FortiAP by executing the command 'reset'.
8.1) If the FortiAP comes back again as 'meru default image', repeat the process but change to 'fap_default' or 'fap_secondary' as 6) suggests.
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 the 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', and 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 an Image ID instead.
4) After the FortiAP restarts, it should come back to the following default GUI. Use 'admin' as a 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.
This procedure must fix the issue with the following similar output:
If there are still problems, create a Customer Service ticket through the Support Portal.