“RESTARTING-ALL-TX” is printed when the mandatory 60 seconds or 600 seconds nonoccupancy expires and the AP is ready to send beacon frames. This message does not indicate that Radar was detected, it only means that the AP changed to a channel that requires DFS radar detection.
So possibly client devices are affected because the AP moved from its original channel to a DFS channel that required the 60 second wait before starting transmission. If Client-aware is enabled (it is by default), and AP would not change channels on its own unless an error threshold is reached indicating that the previous channel was unusable.
@shaun23 wrote:
All,
I am seeing the following message within the "show log system x" within our controllers:
Mar 8 09:58:29 KERNEL(EGLT_AP14@10.3.65.38): RESTARTING ALL TX
Mar 8 10:39:27 KERNEL(BRAD_AP14@192.168.82.171): RESTARTING ALL TX
Mar 8 10:54:01 KERNEL(BRAD_AP14@192.168.82.171): RESTARTING ALL TX
After some Googling I've come across the following article written by Aruba.
https://community.arubanetworks.com/t5/Controller-Based-WLANs/What-does-this-controller-log-message-mean-RESTARTING-ALL-TX/ta-p/178270
Is this something I should be worried about? Will my clients be disconnected while this process happens?
Cheers
Shaun