topic Re: Hard to come back to DFS channel in ExtremeCloud IQ

Hard to come back to DFS channel

sergi_dupe — Mon, 01 Jun 2020 20:49:32 GMT

I have an AP122 allowed to work on DFS channels.

Usually AP selects channel 136 because it is the only one transmitting on that channel (0 interferences from other APs nearby).

However, after detecting radar signals AP does not come back to that DFS channel after several days or even weeks. Logs keep saying this: “ah_dcd: wifi: [DFS-dcost] wifi1: Invalid channel 136” after radar signal disappears.

I thought that once radar signals are not detected anymore, AP would come back in a matter of minuter/hours.

Any hint?

Regards

Re: Hard to come back to DFS channel

Paul_Wang — Mon, 01 Jun 2020 21:46:54 GMT

Until the next scheduled ACSP scan happens, it's the expected design that the AP will not switch back to the original DFS channel after the radar signal is detected. But if you enable "Dynamic Frequency Selection > Enable manual channel selection return" in the radio profile (CLI: radio profile <string> dfs static-channel) and configure a static DFS channel, the AP will try to switch back to the original DFS channel after waiting for 30 minutes following the last channel change caused by the radar signal detection.

Re: Hard to come back to DFS channel

w1f1n00b — Thu, 04 Jun 2020 02:13:58 GMT

@Paul Wang, but unless they’ve changed the default, background scans (acsp) are set for every 10 minutes.

@sergi.dupeyou can confirm background scans via cli with “sh int wifi0” or “sh int wifi1” and look for backround scans details (or use “sh int wifi0 | inc bgscan” to filter just the relevant info

Following as I’m just starting to use DFS channels and am curious what to look out for.

Re: Hard to come back to DFS channel

Paul_Wang — Thu, 04 Jun 2020 08:04:42 GMT

@john_kern - 30 minutes is the NOP (Non occupancy period). If a radar signal is detected on a channel, that channel will not be used for at least 30 minutes.

Re: Hard to come back to DFS channel

w1f1n00b — Thu, 04 Jun 2020 21:39:34 GMT

I guess the question would be, is the channel the AP is changing to and staying on acceptable? It won’t specifically go back to the DFS channel it was on unless it was set manually and you check the box for “Enable manual channel selection return”. Otherwise my understanding is after the DFS event (and the 30 minute NOP) the AP will then resume normal ACSP (based on background scans).

Re: Hard to come back to DFS channel

gacpac — Sat, 06 Jun 2020 05:39:30 GMT

I remember using DFS channels in a big area. tons of issues with IoT devices, a lot of manufactures don't support it. eg. roku and fire tv

Re: Hard to come back to DFS channel

w1f1n00b — Thu, 05 Nov 2020 00:06:25 GMT

Coming back to this thread, I’ve since stopped using DFS channels, as I’ve been told by GTAC that APs do not perform background scans while on a DFS channel. This means no radio auto power adjustments, or rrm channel changes.