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

FOS 7.0.13 compatibility with old FortiAP 220B

Hello

We have FOS 6.2.x and want to upgrade to 7.0.13.

In the meantime we have some old FAP 220B that we want to keep but without breaking the compatibility.

The following command on another FOS 7.0.13 shows that FAP 220B is compatible with FOS 7.0.13.

config wireless-controller wtp-profile

Now I need to check which FAP firmware version is required/recommended on my FAP 220B so it can be compatible with my FOS 7.0.13.

Tried to check on document "FortiAP and FortiOS Compatibility Matrix" but couldn't find anything on FAP 220B, I guess because it is EoL/EoSL.

Any idea where I can find this info?

AEK
AEK
1 Solution
mpftnt
Staff
Staff

Hi AEK.

 

FortiAP 220B is supported until FAP OS version 5.2.7 only. EOS date: 2018-10-06 (Please refer to: https://support.fortinet.com/Information/ProductLifeCycle.aspx)

 

If FortiGates running FortiOS 7.0.1 and later need to manage FortiAP models that cannot be upgraded or legacy FortiAP models whose names end with the letters B, C, CR, or D, administrators can allow those FortiAPs' connections with weak cipher encryption by using compatibility mode:

 

config wireless-controller global
set tunnel-mode compatible
end

 

https://docs.fortinet.com/document/fortigate/7.0.13/fortios-release-notes/453836/strong-cryptographi...

View solution in original post

3 REPLIES 3
pmudgal
Staff
Staff

Hi Sir,

 

Thank you for contacting Fortinet support.

 

For comparability you can check the below link:

https://docs.fortinet.com/document/fortiap/7.4.0/fortiap-and-fortios-compatibility-matrix/495193/for...

 

Also can you please share the command output where it shows that it is compatible  with FOS 7.0.13.

For confirmation of EOL/EOS you can open a case with FAP TAC for more information.

 

Best Regards,

Piyush

AEK
Honored Contributor II

Hi Piyush

(Sorry I pressed SOLUTION button by mistake)

Actually the document you shared is the one I checked before, but unfortunately it doesn't talk about FAP-220B.

 

Here is the requested output:

FW01 # get system status 
Version: FortiGate-200F v7.0.13,build0566,231024 (GA.M)
Security Level: 1
Firmware Signature: certified
Virus-DB: 92.00731(2024-01-17 10:26)
Extended DB: 92.00731(2024-01-17 10:25)
AV AI/ML Model: 2.14306(2024-01-17 07:45)
IPS-DB: 6.00741(2015-12-01 02:30)
IPS-ETDB: 26.00716(2024-01-17 00:44)
APP-DB: 26.00715(2024-01-16 01:56)
INDUSTRIAL-DB: 6.00741(2015-12-01 02:30)
IPS Malicious URL Database: 4.00942(2024-01-17 06:38)
Serial-Number: FG200FT*********
BIOS version: 05000011
System Part-Number: P25129-01
Log hard disk: Not available
Hostname: FW01
Private Encryption: Disable
Operation Mode: NAT
Current virtual domain: root
Max number of virtual domains: 10
Virtual domains status: 1 in NAT mode, 0 in TP mode
Virtual domain configuration: disable
FIPS-CC mode: disable
Current HA mode: a-p, primary
Cluster uptime: 387 days, 6 hours, 53 minutes, 53 seconds
Cluster state change time: 2023-11-06 09:13:48
Branch point: 0566
Release Version Information: GA
FortiOS x86-64: Yes
System time: Wed Jan 17 20:27:21 2024
Last reboot reason: warm reboot


FW01 # config wireless-controller wtp-profile

FW01 (wtp-profile) # edit 1

FW01 (1) # config platform

FW01 (platform) # set type ?
AP-11N Default 11n AP.
220B FAP220B/221B.
210B FAP210B.
222B FAP222B.
112B FAP112B.
320B FAP320B.
11C FAP11C.
14C FAP14C.
223B FAP223B.
28C FAP28C.
320C FAP320C.
221C FAP221C.

... <output truncated>

U24JEV FAPU24JEV.
U321EV FAPU321EV.
U323EV FAPU323EV.
U431F FAPU431F.
U433F FAPU433F.
U231F FAPU231F.
U234F FAPU234F.
U432F FAPU432F.
U231G FAPU231G.
U441G FAPU441G.

 

 
AEK
AEK
mpftnt
Staff
Staff

Hi AEK.

 

FortiAP 220B is supported until FAP OS version 5.2.7 only. EOS date: 2018-10-06 (Please refer to: https://support.fortinet.com/Information/ProductLifeCycle.aspx)

 

If FortiGates running FortiOS 7.0.1 and later need to manage FortiAP models that cannot be upgraded or legacy FortiAP models whose names end with the letters B, C, CR, or D, administrators can allow those FortiAPs' connections with weak cipher encryption by using compatibility mode:

 

config wireless-controller global
set tunnel-mode compatible
end

 

https://docs.fortinet.com/document/fortigate/7.0.13/fortios-release-notes/453836/strong-cryptographi...

Labels
Top Kudoed Authors