Troubleshooting Tip: Unable to create WTP-Profile when channel 40 used bond=40MHZ

[Nur]

Description	This article describes the error when creating a FortiAP profile from the FortiManager ADOM level and being unable to save.
Scope	FortiAP, FortiManager.
Solution	The below error will appear as below: channel 48 is not supported. dfs=yes,region=,plat=431F,cnty=XX,band=802.11ac,n-only,bond=40MHz When the 40Mhz is set as channel width, 2 of the 20 MHz channels are bonded together to form 1 channel.  If using the channel is not supported with 40HMz, it is not possible to select save as the FortiManager will pop up an error. Ideally, in 40 Mhz the below are the channels that would be available for use. List of 40Mhz Channels: 38, 46, 54, 62, 102, 110, 118, 126, 134, 142, 151, 151, 167, 175.  Below are channels that could not be used with bond 40HMz: radio-2/channel : channel 40 is not supported. radio-2/channel : channel 48 is not supported. radio-2/channel : channel 56 is not supported. radio-2/channel : channel 64 is not supported. radio-2/channel : channel 104 is not supported. radio-2/channel : channel 112 is not supported. radio-2/channel : channel 120 is not supported. radio-2/channel : channel 128 is not supported. radio-2/channel : channel 136 is not supported. radio-2/channel : channel 144 is not supported. radio-2/channel : channel 153 is not supported. radio-2/channel : channel 161 is not supported.