By Manny Fernandez

January 4, 2020

FAP U431 Not Registering

I had a customer call me about some FortiAPs that where not registering with the FortiGate.  When I logged into the AP, I noticed it was booting with the Meru code.  This is the code the AP uses to connect to the Fortinet Wireless Controller as opposed to the Fortigate’s AP controller.

When I looked at the User & Device then Device Inventory I was seeing the following:

2020-01-04_20-28-10.png

Take note of the Software OS section.  You can see the ones that ARE operational show the FortiAP OS while the other show Other Identified Devices.  Check you DHCP leases for the IPs being used by the un-registered devices.

2020-01-04_20-27-27.png

As you can see above, this is the screen you will see when logged into the un-registered AP.  You will need to  click the Configure button.

2020-01-04_20-56-25.png

As you can see in the Before screen, it is configured for Meru .  We need to change that.

2020-01-04_20-56-38.png

Now you can see we set the Image ID to Fortinet Primary

2020-01-04_20-56-46.png

Once you apply, you will see the process bar increase and subsequently it will disconnect as it reboots.

If you telnet to the IP of the AP and login into it, you can issue the print_boot

 

2020-01-04_21-56-11.png

Now that the devices are rebooted, you should be able to Authorize them.

2020-01-04_22-01-26.png

Hope this helps

 

 

 

Recent posts

  • In FortiOS 7.4, Fortinet enhanced the ability to do... Full Story

  • Apple shortcuts have been an amazing addition to IOS. ... Full Story

  • Years ago, when I started using FortiGates, I had... Full Story