DCS on NWA50AX is selecting the channel with highest interference probability and ignores empty ones
However, the behavior is quite strange:
At current location, there are 3 other APs in range:
- Ubiquiti: 40MHz@channel 38 (far away)
- Ubiquiti: 40MHz@channel 46 (5m from NWA50AX)
- ASUS: 80MHz@channel 58 (12m from NWA50AX, not being used)
The two ubiquitis have the same SSIDs and their current activity is very similar. However, every time the NWA50AX will go for the channel used by the nearest AP.
My question is... How?
- I would understand if at the time of scan there was no activity at that particular frequency, however the long-term probability of it being used is very high. And it will definitely cause much interference. This should be taken into account.
- What is much worse, channels 100-144 are absolutely free. I do understand that using 120-128 would be dumb, however the other ones are free and there is no activity at all there - confirmed with spectral analysis on Cisco AP which shows the activity of meteoradars well.
All Replies
-
Hi @santomet
Welcome to Zyxel Community!
The DCS decision mechanism always a topic that user is curious about.
We are constantly working to strengthen the functions of DCS in every firmware version upgrade.
Not only the BSSID running in the same band will be considered but also other factors will be evaluated such as total RSSI, Noise floor, Channel utilization…
There are two situations where DCS may not change the channel as a result.
One is the environment is less with interference, although there are other BSSIDs in the same band but they’re not reach the calculated threshold and won’t impact wireless service much.
The other is the environment is too noisy to let AP perform scanning under a reliable condition.
From your description, the first scenario is more likely in your case.
If you still have any questions, we’d like to investigate from the DCS logs for getting more information. Please don’t hesitate to collect the diagnostics file of AP and send us via private message.
Thank you
Regards,
Bella
0 -
Thanks for the reply.
I would like to push it further and maybe even here as users are, naturally, curious. I think that it would be nice if you could share more detailed information so we can get it somewhere together.
This is the important part from the diagnostics in my case; note that there are a few other APs around today. Also note that I am using 20MHz bandwidth because it is enough for my use case and at the same time it lowers the probability of interference.====================================================== current radio2 info wlan-2-1 44 5G 11ax 20MHz 19 channels in total CHAN 40MHZ 80MHZ DFS MAXRSSI BLKRSSI NF CH_LOAD TalmW Radar Rrate BSSs TalSNR LastStime Ptime 36 Y Y N -95 0 -95 43 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 40 Y Y N -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 44 Y Y N -95 0 -95 0 0.000000 0 0 0 0 2022/1/6 07:55:04 1970/1/1 00:00:00 48 Y Y N -36 0 -95 4 0.000650 0 0 3 175 2022/1/6 07:47:43 2022/1/6 07:55:04 52 Y Y Y -95 0 -95 1 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 56 Y Y Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 60 Y Y Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 64 Y Y Y -70 0 -95 0 0.000000 0 0 1 25 1970/1/1 00:00:00 1970/1/1 00:00:00 100 Y Y Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 104 Y Y Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 108 Y Y Y -95 0 -95 2 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 112 Y Y Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 116 Y Y Y -95 0 -95 5 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 120 Y Y Y -86 0 -95 7 0.000000 0 0 1 9 1970/1/1 00:00:00 1970/1/1 00:00:00 124 Y Y Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 128 Y Y Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 132 Y N Y -95 0 -95 1 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 136 Y N Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 140 N N Y -95 0 -95 38 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 vaps: wlan-2-1 ====================================================== dfs nol:( ). The number of channels in NOL:0. chan 36 totalRssi 0 blockrssi 0 chan 36, rssi_weighted 0, rssi_raw_weighted 0, chanload_weighted 43 chan 40 totalRssi 0 blockrssi 0 chan 40, rssi_weighted 0, rssi_raw_weighted 0, chanload_weighted 0 chan 44 totalRssi 0 blockrssi 0 chan 44, rssi_weighted 0, rssi_raw_weighted 0, chanload_weighted 0 chan 48 totalRssi 175 blockrssi 0 chan 48, rssi_weighted 175, rssi_raw_weighted 175, chanload_weighted 4 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1209] totalSNR is 175, avg_SNR is 43 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1238] SNR_variance 43 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1265] chanload chandidate channel list 36 weight 43 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1265] chanload chandidate channel list 40 weight 0 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1265] chanload chandidate channel list 44 weight 0 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1313] txpwr chandidate channel list 40 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1313] txpwr chandidate channel list 44 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1347] zeroRSSI_nondfs_list 40 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1347] zeroRSSI_nondfs_list 44 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1520] new ALG Radio2 5G best channel 44
With the comparison of other logs it is quite apparent how the algorithm works:- Scan for 48 seconds (quite interesting selection)
- Take Non-DFS channels (even if DFS channels are also selected explicitly in the list):
- Sum the SNRs and compute an average
- Select channels with the SNR lower than the average (in this case 40 and 44)
- Prefer channels with zero RSSI
- from the rest [MAGICALLY] select one channel. I have not been able to find the meaning nor the way CH_LOAD parameter is being used in the algorithm.
- The bandwidth of operating BSSIDs is not taken into account! From the list it is apparent that the BSSID operating with the control channel 48 is not only the strongest, but also quite active. However this is not projected into the measurement for channel 44 which in in reality being used to the same extend (confirmed by spectral analysis on Cisco AP). Even if that would not be the case, it is of high probability that the interference is going to be high throughout the day. It is also visible from the table that channels 40 and 44 are treated as there would be no BSSs at all, which is simply not true. The difference of performance between this automatically selected channel and truly free one is significant.
- The explicitly selected channels are simply filtered out, just because they are DFS. This does not work as expected until I deselect channels 36-48 completely. I would like for the explicitly selected channels to have the same initial priority and that this criteria would be taken into account only at the very end of the algorithm. This makes more sense even thought it would need to comply with the DFS and SRD regulations in the end.
0 -
Thanks for the reply.
I would like to push it further and maybe even here as users are, naturally, curious. I think that it would be nice if you could share more detailed information so we can get it somewhere together.
This is the important part from the diagnostics in my case; note that there are a few other APs around today. Also note that I am using 20MHz bandwidth because it is enough for my use case and at the same time it lowers the probability of interference.====================================================== current radio2 info wlan-2-1 44 5G 11ax 20MHz 19 channels in total CHAN 40MHZ 80MHZ DFS MAXRSSI BLKRSSI NF CH_LOAD TalmW Radar Rrate BSSs TalSNR LastStime Ptime 36 Y Y N -95 0 -95 43 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 40 Y Y N -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 44 Y Y N -95 0 -95 0 0.000000 0 0 0 0 2022/1/6 07:55:04 1970/1/1 00:00:00 48 Y Y N -36 0 -95 4 0.000650 0 0 3 175 2022/1/6 07:47:43 2022/1/6 07:55:04 52 Y Y Y -95 0 -95 1 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 56 Y Y Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 60 Y Y Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 64 Y Y Y -70 0 -95 0 0.000000 0 0 1 25 1970/1/1 00:00:00 1970/1/1 00:00:00 100 Y Y Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 104 Y Y Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 108 Y Y Y -95 0 -95 2 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 112 Y Y Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 116 Y Y Y -95 0 -95 5 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 120 Y Y Y -86 0 -95 7 0.000000 0 0 1 9 1970/1/1 00:00:00 1970/1/1 00:00:00 124 Y Y Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 128 Y Y Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 132 Y N Y -95 0 -95 1 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 136 Y N Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 140 N N Y -95 0 -95 38 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00 vaps: wlan-2-1 ====================================================== dfs nol:( ). The number of channels in NOL:0. chan 36 totalRssi 0 blockrssi 0 chan 36, rssi_weighted 0, rssi_raw_weighted 0, chanload_weighted 43 chan 40 totalRssi 0 blockrssi 0 chan 40, rssi_weighted 0, rssi_raw_weighted 0, chanload_weighted 0 chan 44 totalRssi 0 blockrssi 0 chan 44, rssi_weighted 0, rssi_raw_weighted 0, chanload_weighted 0 chan 48 totalRssi 175 blockrssi 0 chan 48, rssi_weighted 175, rssi_raw_weighted 175, chanload_weighted 4 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1209] totalSNR is 175, avg_SNR is 43 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1238] SNR_variance 43 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1265] chanload chandidate channel list 36 weight 43 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1265] chanload chandidate channel list 40 weight 0 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1265] chanload chandidate channel list 44 weight 0 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1313] txpwr chandidate channel list 40 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1313] txpwr chandidate channel list 44 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1347] zeroRSSI_nondfs_list 40 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1347] zeroRSSI_nondfs_list 44 [2022/1/6 08:04:39][dcs_find_best_5G_channel:1520] new ALG Radio2 5G best channel 44
With the comparison of other logs it is quite apparent how the algorithm works:- Scan for 48 seconds (quite interesting selection)
- Take Non-DFS channels (even if DFS channels are also selected explicitly in the list):
- Sum the SNRs and compute an average
- Select channels with the SNR lower than the average (in this case 40 and 44)
- Prefer channels with zero RSSI
- from the rest [MAGICALLY] select one channel. I have not been able to find the meaning nor the way CH_LOAD parameter is being used in the algorithm.
- The bandwidth of operating BSSIDs is not taken into account! From the list it is apparent that the BSSID operating with the control channel 48 is not only the strongest, but also quite active. However this is not projected into the measurement for channel 44 which in in reality being used to the same extend (confirmed by spectral analysis on Cisco AP). Even if that would not be the case, it is of high probability that the interference is going to be high throughout the day. It is also visible from the table that both channels 40 and 44 are treated as there would be no BSSs at all, which is simply not true. You might say that there is no impact to the performance but in reality the difference of performance between this automatically selected channel and truly free one is significant.
- The explicitly selected channels are simply filtered out, just because they are DFS. This does not work as expected until I deselect channels 36-48 completely. I would like for the explicitly selected channels to have the same initial priority and that this criteria would be taken into account only at the very end of the algorithm. This makes more sense even thought it would need to comply with both the SRD and DFS regulations in the end.
1 -
Hi @santomet
Although we can’t reveal much detail algorithm here but one criteria is to choose non-DFS channel and previous better channel as the prior candidate.
In our internal test, band 1 is quite noisy so the procedure of DCS will scan all channels we’ve selected in the pool. Your environment is quite clean by comparing to ours.
[2022/1/11 05:00:48][ dcs_scan_handler:1371] Random backoff_time 120
[2022/1/11 05:02:48][ in_dfs_cac: 153] slotnum 1, incac 0
[2022/1/11 05:02:48][ dcs_scan_handler:1397] DCS invoke scanning
[2022/1/11 05:02:48][ invoke_scan_agent: 182] Start invoke dcs scan (5G)
[2022/1/11 05:03:36][ dcs_signal_action: 267] Recv signal(16)
[2022/1/11 05:03:36][dcs_signal_event_handler:1447] current state WAIT_SCAN_COMPLETE, signal event 1 , requestor 0
[2022/1/11 05:03:36][dcs_signal_event_handler:1525] Received scanning done
======================================================
current radio2 info wlan-2-1 128 5G 11ax 20MHz
19 channels in total
CHAN 40MHZ 80MHZ DFS MAXRSSI BLKRSSI NF CH_LOAD TalmW Radar Rrate BSSs TalSNR LastStime Ptime
36 Y Y N -23 0 -95 40 0.005072 0 0 22 555 1970/1/1 00:00:00 1970/1/1 00:00:00
40 Y Y N -42 0 -95 24 0.000238 0 0 17 632 1970/1/1 00:00:00 1970/1/1 00:00:00
44 Y Y N -40 0 -95 29 0.000235 0 0 16 453 2022/1/11 02:21:37 2022/1/11 03:06:59
48 Y Y N -48 0 -95 23 0.000033 0 0 17 416 1970/1/1 00:00:00 1970/1/1 00:00:00
52 Y Y Y -95 0 -95 1 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00
56 Y Y Y -66 0 -95 9 0.000000 0 0 15 177 1970/1/1 00:00:00 1970/1/1 00:00:00
60 Y Y Y -48 0 -95 5 0.000037 0 0 9 318 1970/1/1 00:00:00 1970/1/1 00:00:00
64 Y Y Y -91 0 -95 5 0.000000 0 0 4 14 1970/1/1 00:00:00 1970/1/1 00:00:00
100 Y Y Y -36 0 -95 4 0.000508 0 0 12 355 1970/1/1 00:00:00 1970/1/1 00:00:00
104 Y Y Y -43 0 -95 6 0.000115 0 0 5 222 1970/1/1 00:00:00 1970/1/1 00:00:00
108 Y Y Y -70 0 -95 3 0.000000 0 0 5 86 1970/1/1 00:00:00 1970/1/1 00:00:00
112 Y Y Y -41 0 -95 6 0.000099 0 0 7 269 1970/1/1 00:00:00 1970/1/1 00:00:00
116 Y Y Y -50 0 -95 7 0.000010 0 0 1 45 2022/1/11 03:06:59 2022/1/11 04:00:49
120 Y Y Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00
124 Y Y Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00
128 Y Y Y -95 0 -95 1 0.000000 0 0 0 0 2022/1/11 04:00:49 1970/1/1 00:00:00
132 Y N Y -95 0 -95 3 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00
136 Y N Y -38 0 -95 6 0.000536 0 0 4 225 1970/1/1 00:00:00 1970/1/1 00:00:00
140 N N Y -95 0 -95 0 0.000000 0 0 0 0 1970/1/1 00:00:00 1970/1/1 00:00:00
vaps: wlan-2-1
======================================================
dfs nol:(
).
The number of channels in NOL:0.
chan 36 totalRssi 555 blockrssi 0
chan 36, rssi_weighted 555, rssi_raw_weighted 555, chanload_weighted 40
chan 40 totalRssi 632 blockrssi 0
chan 40, rssi_weighted 632, rssi_raw_weighted 632, chanload_weighted 24
chan 44 totalRssi 453 blockrssi 0
chan 44, rssi_weighted 453, rssi_raw_weighted 453, chanload_weighted 29
chan 48 totalRssi 416 blockrssi 0
chan 48, rssi_weighted 416, rssi_raw_weighted 416, chanload_weighted 23
chan 52 totalRssi 0 blockrssi 0
chan 52, rssi_weighted 0, rssi_raw_weighted 0, chanload_weighted 1
chan 56 totalRssi 177 blockrssi 0
chan 56, rssi_weighted 177, rssi_raw_weighted 177, chanload_weighted 9
chan 60 totalRssi 318 blockrssi 0
chan 60, rssi_weighted 318, rssi_raw_weighted 318, chanload_weighted 5
chan 64 totalRssi 14 blockrssi 0
chan 64, rssi_weighted 14, rssi_raw_weighted 14, chanload_weighted 5
chan 100 totalRssi 355 blockrssi 0
chan 100, rssi_weighted 355, rssi_raw_weighted 355, chanload_weighted 4
chan 104 totalRssi 222 blockrssi 0
chan 104, rssi_weighted 222, rssi_raw_weighted 222, chanload_weighted 6
chan 108 totalRssi 86 blockrssi 0
chan 108, rssi_weighted 86, rssi_raw_weighted 86, chanload_weighted 3
chan 112 totalRssi 269 blockrssi 0
chan 112, rssi_weighted 269, rssi_raw_weighted 269, chanload_weighted 6
chan 116 totalRssi 45 blockrssi 0
chan 116, rssi_weighted 45, rssi_raw_weighted 45, chanload_weighted 7
chan 120 totalRssi 0 blockrssi 0
chan 120, rssi_weighted 0, rssi_raw_weighted 0, chanload_weighted 0
chan 124 totalRssi 0 blockrssi 0
chan 124, rssi_weighted 0, rssi_raw_weighted 0, chanload_weighted 0
chan 128 totalRssi 0 blockrssi 0
chan 128, rssi_weighted 0, rssi_raw_weighted 0, chanload_weighted 1
chan 132 totalRssi 0 blockrssi 0
chan 132, rssi_weighted 0, rssi_raw_weighted 0, chanload_weighted 3
chan 136 totalRssi 225 blockrssi 0
chan 136, rssi_weighted 225, rssi_raw_weighted 225, chanload_weighted 6
chan 140 totalRssi 0 blockrssi 0
chan 140, rssi_weighted 0, rssi_raw_weighted 0, chanload_weighted 0
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1209] totalSNR is 3767, avg_SNR is 198
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1238] SNR_variance 198
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1265] chanload chandidate channel list 52 weight 1
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1265] chanload chandidate channel list 56 weight 9
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1265] chanload chandidate channel list 64 weight 5
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1265] chanload chandidate channel list 108 weight 3
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1265] chanload chandidate channel list 116 weight 7
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1265] chanload chandidate channel list 120 weight 0
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1265] chanload chandidate channel list 124 weight 0
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1265] chanload chandidate channel list 128 weight 1
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1265] chanload chandidate channel list 132 weight 3
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1265] chanload chandidate channel list 140 weight 0
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1313] txpwr chandidate channel list 52
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1313] txpwr chandidate channel list 56
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1313] txpwr chandidate channel list 64
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1313] txpwr chandidate channel list 108
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1313] txpwr chandidate channel list 116
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1313] txpwr chandidate channel list 120
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1313] txpwr chandidate channel list 124
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1313] txpwr chandidate channel list 128
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1313] txpwr chandidate channel list 132
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1313] txpwr chandidate channel list 140
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1338] zeroRSSI_dfs_list 52
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1356] final_dfs_list 56
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1356] final_dfs_list 64
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1356] final_dfs_list 108
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1356] final_dfs_list 116
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1338] zeroRSSI_dfs_list 120
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1338] zeroRSSI_dfs_list 124
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1338] zeroRSSI_dfs_list 128
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1338] zeroRSSI_dfs_list 132
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1338] zeroRSSI_dfs_list 140
[2022/1/11 05:03:36][dcs_find_best_5G_channel:1520] new ALG Radio2 5G best channel 128
dfs nol:(
).
The number of channels in NOL:0.
[2022/1/11 05:03:36][process_set_channel_state:1604] Radio2 cannot find channel better than current channel 128For your first point about the main channel selection consider with bandwidth, we’ll discuss and keep enhance DCS functions.
If you still have questions, we can help to check your DCS logs in the Diagnostic file for getting more information.
Thank you.
Regards,
Bella
0
Categories
- All Categories
- 414 Beta Program
- 2.2K Nebula
- 130 Nebula Ideas
- 90 Nebula Status and Incidents
- 5.4K Security
- 171 USG FLEX H Series
- 255 Security Ideas
- 1.4K Switch
- 71 Switch Ideas
- 1K Wireless
- 36 Wireless Ideas
- 6.2K Consumer Product
- 235 Service & License
- 370 News and Release
- 77 Security Advisories
- 24 Education Center
- 5 [Campaign] Zyxel Network Detective
- 2.9K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 80 About Community
- 69 Security Highlight