" AP Profile" missing in web interface

I had the same problem when I installed one too. The problem is that you are running the wrong firmware. There is a special build of the firmware for the Fortigate if you want it to be a Wireless Controller. It is really hard to find on the fortinet web site. Log into the Fortinet support site, go to Firmware Images, then click on the link for FortiAP (make sure you click on the link in the area under " please select from the products listed below for Firmware Downloads" , not the area with the handly little tabs). then clikc on v4.00 then 4.0MR2 then MR2_Patch_2 then Wireless_controller download and install the firmware for your firewall and you will get the option for the AP Profile. I am not sure why Fortinet has a half hobbled version of Wireless Controller software built into the regular release firmware, but it makes it really confusing. Good Luck.

MR 3 (4.3.0) will supposedly bring the wireless controller functionality into the " normal" firmware branch, and you wont need the special branch currently required. You may also be happy to note that 4.3.0 is supposed to come out this week, on March 18. But obviously, things could get pushed back, and 4.3.0 is probably going to have alot of bugs to start out. I am thinking of picking up a FortiAP very soon myself.

Well it was hard to come by this info as many of you know how hard it is to get into support the same week you call.... You need to be on V4 MR3 on the FG and FAP. Quoted " FortiOS v4.0 MR3 officially supports upgrade from the FortiOS v4.0 MR2 Patch Release 4 or later." 3-19 was the release date as far as when it came out but 3-23 was the mainstream avail. I upgraded last night. 2x 110c' s and a WiFi80CM. I would just love to know 2 things. -How thru any means CLI of the FAP or thru your FG110C to tell what Firm FAP really has. -How you flash it to the newer firmware it requires. I have tried the TFTP but keep having timeout erros or checksum errors. I have been reading up on a Forti-DOC that states you can upgrade from within the support FG unit. AHAHAAAH what a joke cause thats all it says i cant find anywhere how or even it stating can only get info thru cli it just doesnt say period. So far on support.fortinet.com I Can only find 6 articles that relate to the FAP period. 4 on the KB, 2 being Japan only, 1 being interoprability, and last being about your disclaimer messages lol.... all that assumes you had no issues getting the right firmware or getting it working correctly to need to make a disclamer. The 6th article and last under techinical documents is the quicksetup guide thats it. Anybody seen the cli commands for this thing. I noticed its now linux and not forti code on the FAP.

Message

1. fap-get-status 2. Two ways to upgrade FAP a. upgrade FAP from FAP cli: restore ? Usage: restore restore <image filename on tftp sever> <tftp sever ip address> b. upgrade FAP from controller You must have your FAP connected to the controller, and in the managed AP page, click to edit a FAP, and you can see something like: FortiAP OS Version FAP22B-v4.0-build309 [Upgrade] If the FAP is not connected to the AC, you will not be able to see the above line.

Fortigate doesn' t seem to like Solarwinds. I could never get it to work reliably with the Fortigates, even tho it was brilliant with all my HP and Cisco gear. Try the 3CDaemon instead. I had better luck with it. http://support.3com.com/software/3cdv2r10.zip

Just got a FortiAP. I knew beforehand I would need 4.3.0 or a special branch of 4.2.X to get wireless controller to work with my fortigate 200B. Seems odd, since with 4.2.4 under the wireless controller tab, everything seems to point that it should work, everthing is enabled, Fortigate " sees" the fortiAP, and vice versa, but the FortiAp has a yellow Status light, which means " FortiGate wireless controller had been found but FortiAp is not managed" . If anyone here knows how to get it managed without needing to upgrade to 4.3.0 in a production environment, I would love to know. The reason being, 4.3.0 is so unstable if you see the recent posts here. Now, I personally had a lot of issues with 4.2.2 regular branch with my 200B. I see that the special version needed to get the wireless controller is 4.2.2. HMMM, not good. Why is there not the " special" version for 4.2.3 or 4.2.4? Am I really stuck between choosing the special 4.2.2 or the 4.3.0? Both are confimed buggy, and I am in a production environment. The FortiAP has been out since about June 2010, how the heck did anyone get this AP unit working back then, since it still seems a confusing mess to do it now.

have you tried to upgrade the FortiAP ? i used to have 4.2.2 ( the wireless controller firmware ) and it worked very well

I personally had a lot of issues with 4.2.2 regular branch with my 200B

You have two options only... 4.2.2 special build or 4.3. If you go with 4.2.2 special build then be sure to install the fortiap 112 firmware. What issue are you having? I have a 200b with the special build and it works good. The only issue that I have is with wan opt/web cache and the issue were not fixed in 4.2.3 or 4.2.4.

Check the " type" it is most likely a " VAP" which is a wireless SSID. It doesn’t have an IP address assigned to it so it is not active. If you don’t need it delete it? Go to the wireless controller tab and check your profiles. You should see the wireless and you can delete it from there.