Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
hanstran
New Contributor

FGT100D and FAP221C

Bumping this to a new thread. Has anyone managed to get the FGT100D to work with the FAP221C? I am running the FGT_100D-v500-build4457-FORTINET.out in the FGT and the FAP_221C-v5.0.0-b0060-fortinet.out in the FAP. But the FAP is stuck on " AC Discovery Status Discovering AC ..." and it never appear in the FGT. Have also tried to setup the FAP with a static controller IP address. Some system info: S-FW1-0 # get system status Version: FortiGate-100D v5.0,build4457,140410 (GA Patch 7) Virus-DB: 22.00161(2014-05-08 13:57) Extended DB: 22.00161(2014-05-08 13:59) IPS-DB: 4.00492(2014-05-08 00:55) IPS-ETDB: 0.00000(2001-01-01 00:00) Serial-Number: FG100D3G13829424 Botnet DB: 1.00515(2014-05-04 20:31) BIOS version: 04000030 System Part-Number: P11510-03 Log hard disk: Available Internal Switch mode: interface Hostname: S-FW1-0 Operation Mode: NAT Current virtual domain: root Max number of virtual domains: 10 Virtual domains status: 3 in NAT mode, 0 in TP mode Virtual domain configuration: enable FIPS-CC mode: disable Current HA mode: a-p, master Branch point: 271 Release Version Information: GA Patch 7 FortiOS x86-64: Yes System time: Mon May 12 10:37:47 2014 S-FW1-0 # edit " port10" set vdom " root" set type physical set snmp-index 23 next edit " mgmt-ap" set vdom " root" set ip 10.28.46.1 255.255.255.0 set allowaccess ping capwap set snmp-index 47 set interface " port10" set vlanid 46 next config wireless-controller setting set country NO end FP221C3X14000344 # fap-get-status Version: FortiAP-221C v5.0,build449,140130 (GA) Serial-Number: FP221C3X14000344 BIOS version: 04000002 Regcode: E Hostname: FP221C3X14000344 Branch point: 060 Release Version Information:GA FP221C3X14000344 #
5 REPLIES 5
hanstran
New Contributor

An update. After disabling HA and only using one FGT100D, the FAP suddenly did appear. Is not HA and Wireless supported? Regards, Hans Jørgen
mlotz
New Contributor

FYI I also encountered this issue with FortiAP 223B' s and our FortiGate 100D HA cluster. After upgrading from 5.0.6 to 5.0.7 the FAPs were no longer showing connected. Downgrading back to 5.0.6 resolved the issue. I couldn' t test trying without HA, as it is a production cluster. Thanks. Michael
harald21
Contributor

Hello, we too have some HA cluster with FortiAP' s running: FGT-40C-HA (A-P) - FortiOS 5.0.7 (build4457) with FAP-221C running fine FGT-310B-HA (A-P) - FortiOS 5.0.7 (build3608) with FAP-210B and FAP-220B running fine So in general it seems not to be an issue with FAP and HA. Maybe something special with FGT-100D? Sincerely Harald
Layard
New Contributor III

Hello, The same thing happened to me. Does anyone have an update? Layard
Layard Terrero
Layard Terrero
Sean_Toomey_FTNT

I have a FGT-100D running 5.2.0 GA and FAP-221C running 5.2 as well. All is fine here, AP' s are nice and stable and have worked well consistently over the course of several weeks. I believe there were some significant optimizations done to both FortiOS 5.2 as well as the firmware for the AP itself in 5.2 that may make a big difference in your experience. Can you try upgrading to 5.2 and let us know how it works for you then? Cheers!
-- Sean Toomey, CISSP FCNSP Consulting Security Engineer (CSE) FORTINET— High Performance Network Security
Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors