Problem Connection AP to FGT

[TopJimmy]

Hello, I' m having an issue connection an AP220B our FGT620b. The 620B is running 4.3.12 and I' m not sure what version the AP is running but I know it' s in the 4.3 branch. Anyway, this should be straight forward but I just can' t get it. I can' t make the interface on the FGT a dedicated AP interface but it still should work, right? FortiGate Interface: (port2) = 172.16.253.2 FortiAP = 172.16.1.45 With no DHCP server available in 172.16.1.1/0, I' ve set the AP statically with the following commands: cfg -a AC_DISCOVERY_TYPE=" 1" cfg -a ADDR_MODE=STATIC cfg –a AP_IPADDR=”172.16.1.45” cfg –a AP_NETMASK=”255.255.255.0” cfg –a IPGW=”172.16.1.1” cfg –a AC_IPADDR_1=”172.16.253.2” cfg -c Then I pull the plug and plug it back in. It never does light up with the flashing green LED and I don' t see it listed under the " Managed FortiAP" section on the FGT. I can ping from both devices so I know it has some network connectivity. (From FGT) execute ping 172.16.1.45 PING 172.16.1.45 (172.16.1.45): 56 data bytes 64 bytes from 172.16.1.45: icmp_seq=0 ttl=63 time=0.2 ms 64 bytes from 172.16.1.45: icmp_seq=1 ttl=63 time=0.1 ms 64 bytes from 172.16.1.45: icmp_seq=2 ttl=63 time=0.1 ms --- 172.16.1.45 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.1/0.1/0.2 ms (From FortiAP) FAP22B3U1xxxxxxx # ping 172.16.253.2 PING 172.16.253.2 (172.16.253.2): 56 data bytes 64 bytes from 172.16.253.2: icmp_seq=0 ttl=254 time=0.2 ms 64 bytes from 172.16.253.2: icmp_seq=1 ttl=254 time=0.1 ms 64 bytes from 172.16.253.2: icmp_seq=2 ttl=254 time=0.1 ms --- 172.16.253.2 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.1/0.1/0.2 ms I' ve " factoryreset" it a few times and still no go so I' m not sure what to do next. Any help would be much appreciated.

[Carl_Wallmark]

Your IP addresses looks wrong on the AP AC = 172.16.253.2 When you have 172.16.1.45 and netmask 255.255.255.0 ?

[TopJimmy]

ORIGINAL: Selective Your IP addresses looks wrong on the AP AC = 172.16.253.2 When you have 172.16.1.45 and netmask 255.255.255.0 ?

No...the FGT address is correct. It' s 172.16.253.2/255.255.255.252 and the AP' s address is 172.16.1.45/24. The AP hangs off the same interface that (port2) that the 172.16.253.2 IP is assigned to. I' ll try to upgrade the AP to the latest firmware although I' ve never done it before without it being connected to a FGT.

[Dave_Hall]

I don' t have a 220B in front of me so not sure what the full options for " cfg -a AC_DISCOVERY_TYPE=?" does. (Documentation on the FortiAP are sparse.) Even with a proper routable IP on the AP it needs to be able to " discover" the AC via either Broadcast, multicast, or DHCP option 138. So I am curious to know what " AC_DISCOVERY_TYPE" command does. If this is a new FortiAP then chances are the firmware is still on 4.0 MR2 patch 2 (or there abouts). I suggest upgrading to the latest firmware on the same MR path as the main unit. (Actually it' s a good idea to upgrade the firmware anyway.) Edit: Found some useful info in kb#FD33978 about that cmd. Noticed in another KB about setting the AC port connector. (Sample give is AC_CTL_PORT:=5246.)