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

Troubleshoot FAP 221B not visible in controller

I' ve installed FAP 221B with FortiWifi 60D and used it as Controller at some 3+ sites. Just added the APs to the network and let DHCP assign a IP and it was found and I could authorize it. I' m on a new site and the AP gets IP and its possible to communicate with it but its not visible in the Controller for the authorization process. What is the more common issues on Controller/AP and how to best troubleshoot this? Any ideas are appreciated.
12 REPLIES 12
Bromont_FTNT
Staff
Staff

What' s the network topology at this new site? Firmware on both AP and FGT? New AP?
gojj

Hi, almost immediate after posting this message I found one thing thats different between the FortiWifi 60D. On the previous ones there is FortiOS 5.0.4 - but on this one, with the issue, we only run FortiOS 5.0.3 We use an ip plan of e.g 172.16.0.0/22 Where FortiWifi is 172.16.0.1 and all APs starts with 172.16.0.24x and clients connection to them are located in e.g 172.16.3.0/26 (tunnel mode) AP:s are initially FAP OS 5.0 build 032. They are all new AP:s. I will upgrade the FortiWifi and see if that helps. Should have done my homework more throughly....
Dave_Hall
Honored Contributor

Configure option 138 on the DHCP server to provide the IP address of the controller. This info is listed in the wireless deployment guides. For 4.0 MR3 see page 45. For 5.0 see page 40. If using Windows server, see this KB#FD33978.

NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C

NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C
Bromont_FTNT
Staff
Staff

5.0.3 vs 5.0.4 should not matter... Telnet to the AP to see what the output of " cfg -s" is.
gojj

FP221Bxxxxx # cfg -s BAUD_RATE:=9600 ADMIN_TIMEOUT:=5 ADDR_MODE:=DHCP AP_IPADDR:=192.168.1.2 AP_NETMASK:=255.255.255.0 IPGW:=192.168.1.1 AP_MODE:=0 DNS_SERVER:=208.91.112.53 STP_MODE:=0 AP_MGMT_VLAN_ID:=0 TELNET_ALLOW:=0 HTTP_ALLOW:=1 AC_DISCOVERY_TYPE:=0 AC_IPADDR_1:=192.168.1.1 AC_HOSTNAME_1:=_capwap-control._udp.example.com AC_DISCOVERY_MC_ADDR:=224.0.1.140 AC_DISCOVERY_DHCP_OPTION_CODE:=138 AC_CTL_PORT:=5246 AC_DATA_CHAN_SEC:=2 MESH_AP_TYPE:=0 MESH_MAX_HOPS:=4 MESH_SCORE_HOP_WEIGHT:=50 MESH_SCORE_CHAN_WEIGHT:=1 MESH_SCORE_RATE_WEIGHT:=1 MESH_SCORE_BAND_WEIGHT:=100 MESH_SCORE_RSSI_WEIGHT:=100 even if those settings regarding IP exists it does answer on it' s IP 172.23.36.241 for example. They seem to be more of the default values.
Bromont_FTNT
Staff
Staff

Yes, those are the default values on the AP... the IP addresses you see there are only used if it doesn' t get an IP via DHCP, the AC_IPADDR is only used if it can' t discover the controller via other means. The Fortiwifi is on 172.16.0.1/22 but the AP is on 172.23.36.241?
gojj

AP is 172.16.0.241 in this example - the other IP was a misspelling in this case with example IP:s
gojj
New Contributor

Upgraded FortiWifi 60D to Forti OS 5.0.4 and no luck with that either.
gojj
New Contributor

I updated the FAP to the newest firmware build 048, but no luck. Found the webpage and that states: AC Discovery Status Discovering AC ... Seems it cant find the Controller for some reason. But it possible to ping 172.16.0.1 from the FAP itself so it should be able to discover the Controller which should be 172.16.0.1 I presume.
Labels
Top Kudoed Authors