What does this controller log message mean: “RESTARTING ALL TX”?
Product and Software: This article applies to all Aruba controllers and all ArubaOS versions.
“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.
If DFS is in the regulatory domain and ARM selects one DFS channel for an AP to go to, does the AP go to that channel without any prior silence or checking?
Any time an AP changes to a DFS channel (ARM or no-ARM), it must wait for the nonoccupancy time (of 1 minute or 10 minutes [channels 124-132 in Europe] before it transmits any packet (including beacon frames).
What does the AP do when it detects radar while on a DFS channel?
If an AP detects radar on a DFS channel, it must move away from that channel and not come back to it for 30 minutes. If ARM is enabled, the AP goes to next best channel (DFS or non DFS) and remains there unless it has to change.
If ARM is disabled, the AP moves away from the DFS channel after detecting radar and comes back to it after 30 minutes have expired.
What does the AP do while on a DFS channel and ARM decides to make a channel change to either another DFS channel or a non-DFS channel?
The AP changes channel and if it happens to be a DFS channel, it again must wait 60 seconds before sending beacons or any transmissions.
For non-DFS channel, there is no such requirement.
Note: Consult actual regional 802.11a/DFS documentation for DFS channel information.