| Solution |
- On the 5 GHz spectrum (UNII-2, UNII-2 Extended) most of the channels are used by Wireless systems such as Weather Radar, Military, Airport, Habour, and Satellite communications systems, and the same spectrum is also shared by 802.11 Wireless Networks as well and this can cause interference to both the systems.
-
DFS (Dynamic Frequency Selection) allows FortiAP units to utilize all DFS channels on the 5 GHz spectrum (UNII-2, UNII-2 Extended), and also the FortiAP should comply with permitted transmit power on that channel in that regulatory domain. If a radar event is detected, the FortiAP will automatically change the operating channel on the 5 GHz radio to overcome interference.
-
When a radar event is detected on the DFS channels (Channel 52 to 144), the FortiAP would put the detected channel(s) into NOL (Non-Occupancy List) - the FortiAP maintains a list of channels where the radar has been detected. Thereafter, the FortiAP avoids using these channels (NOL) for at least 30 minutes after detecting radar on the channels.
-
Radar events can be viewed on the FortiGate WiFi Event logs and also on the FortiAP as shown below:
FortiGate:
date=2024-11-29 time=13:02:32 id=744268591027XXX itime="2024-11-29 13:02:31" euid=3 epid=104 dsteuid=3 dstepid=3 logver=702071577 logid=0104043XXX type="event" subtype="wireless" level="notice" bandwidth="20MHz" action="radar-detected" msg="Demo-AP radio 2 found radar pulse, change channel 104 ==> 104." logdesc="Physical AP radio radar detected" sn="FP431GTY23XXXXX" ip=172.16.X.X ssid="N/A" ap="Demo-AP" channel=104 radioid=2 radioband="802.11ax-5G" configcountry="GB " opercountry="GB " cfgtxpower=1 opertxpower=7 eventtime=1732885351815975289 tz="+0000" slctdrmamode="ap" operdrmamode="ap" devid="FG200FT923XXXXX" vd="root" dtime="2024-11-29 13:02:32" itime_t=1732885351 devname="FG200F"
Technical Tip: How to collect logs and config to assist TAC in debugging issues on FortiAP WiFi
FortiAP:
klog | grep Radar
[174785.270285] wlan: [0:D:dfs] WLAN_DEBUG_DFS_ALWAYS : dfs_process_radar_ind_on_home_chan: Radar found on channel=120, freq=5600 MHz. Primary beaconning chan:120, freq=5600 MHz.
rcfg | grep nol
nol list : 60, 64, 124, 128,
-
Verify whether there is any External Radar system (Airport/Weather/Harbour/Military) set up near the site. If yes, to minimize radar detections, it is possible to incorporate the following changes:
-
Ensure FortiGate is on the newer 7.4.x and above versions because it has new features or enhancement - Wi-Fi 5G Hz UNII-3 channels (149, 153, 157, 161, and 165) are allowed in European countries and region code E countries starting FortiAP 7.4 and FortiGate 7.4 and higher versions and this step will provide more channels for the FortiAP units to operate on the 5 GHz spectrum: New features or enhancements.
FortiAP Mantis 876673: Wi-Fi UNII-3 channels allowed in certain European countries.
FortiGate Mantis 852998: Wi-Fi UNII-3 channels should be allowed in certain European countries.
-
Deselect all DFS channels from the FortiAP profile on the 5 GHz radio (this step can be suitable for low-density FortiAP deployment).
-
Deselect only the frequently detected radar i.e. nol channels from the FortiAP profile from 5 GHz radio (this step can be suitable for both low and high-density FortiAP deployment).
-
Use 20 MHz channel width on the FortiAP 5 GHz radio.
-
Ensure the Distributed Automatic Radio Resource Provisioning (DARRP) feature is enabled on all the radios in the FortiAP profile:
Understanding Distributed Radio Resource Provisioning
-
Ensure the FortiAP unit is operating on the latest 7.4 or 7.6 firmware version.
-
Useful commands on the FortiAP:
cfg
radartool
radartool -i wifi1 bangradar
klog | grep Radar
iwconfig
date
fap-tech
|
