Reset Search
 

 

Article

Identifi access-points moving from their custom DFS channel to a non-DFS channel

« Go Back

Information

 
TitleIdentifi access-points moving from their custom DFS channel to a non-DFS channel
Symptoms
  • Current channel is showing a non-DFS channel that is different than the last requested channel which is a DFS channel
  • Channel plan is set to "Custom"
  • logs similar to the following
Sep 27 10:18:39 EWC events: Access Point AP Serial Number 1234Y-1234567890: 09/27/16 15:18:38: Radar found on channel 5660Mhz 2
Sep 27 10:46:14 EWC events: Access Point AP Serial Number 1234Y-1234567890: 09/27/16 15:46:13: RADAR Interference Previously Detected on wlan 0, channel: 5700 AP selecting new channel 1

 
Environment
  • Identifi access-points
  • Only channel 140 in channel plan
Cause
  • Channels 50 to 144 are DFS channels which are also used by meteorological RADAR
  • If they see any meteorological RADAR events, they will automatically move to a different, non-DFS channel  (channels 36 to 48)
  • In the logs listed in this article, Frequency 5700Mhz equals channel 140 (the custom channel that was configured on the AP's radio 1), so the AP had to move away from that channel per legal regulation to avoid the RADAR using the same channel.
Resolution
 
  • This is FAD (Functioning as Designed)
  • Use non-DFS channels in areas where radar is known to be encountered frequenty
  • Use DFS channels with the knowledge that if the AP detects the presence of this frequency being used, it will move the channel to a non-DFS channel
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255