Wireless Access

 View Only
last person joined: 10 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

5Ghz ARM Channel Churn due to Bad Channel Quality

This thread has been viewed 12 times

  • 1.  5Ghz ARM Channel Churn due to Bad Channel Quality

    Posted 21 days ago

    We run a fleet of IAP-335's on 8.10.0.10, Airwave managed. Lately we have had a lot of disruption due to ARM frequently changing channels due to Bad Channel Quality. Many sites are CBD or shopping mall's so interference in 5Ghz is the norm. Each channel change dropped clients for 1-2 minutes but Client Aware has always been enabled. Clients need a full re-auth, role is delivered by CPPM. Not wanting to statically set channel/power we stabilized sites with below CLI. The main CLI that resolved was  'channel-quality-aware-arm-disable'. Initially we tried moving interference-immunity from 2->7. It helped a little. What's worse than a poor quality channel? One that keeps disappearing!

    1) Client Aware. Does not seem to work as advertised?

    2) Airwave IGC. It does not give access to these CLI options. We had to move to Template mode and loose per site (VC) overrides. Sometimes it is useful.

    3) TAC recommendation: "We recommend conducting a site survey and strategically deploying the APs (Access Points) for an improved experience."?

    Deployed CLI changes:

    arm
     backoff-time 1800
     channel-quality-aware-arm-disable
     free-channel-index 30
     client-match restriction-timeout 3

    rf dot11g-radio-profile
     interference-immunity 7
     free-channel-index 40

    rf dot11a-radio-profile
     interference-immunity 7
     free-channel-index 30

    What it stopped:

    Phy-Type  :5GHz
    ARM History
    -----------
    Time of Change       Old Channel  New Channel  Old Power  New Power  Reason  Result
    --------------       -----------  -----------  ---------  ---------  ------  ------
    2024-05-08 16:52:09  108          132          15         15         Q       Configured
    2024-05-08 16:46:48  140          108          15         15         Q       Configured
    2024-05-08 16:42:33  116          140          15         15         Q       Configured
    2024-05-08 16:28:47  56           116          15         15         Q       Configured
    2024-05-08 14:22:01  116          56           15         15         Q       Configured
    2024-05-08 14:17:01  140          116          15         15         Q       Configured
    2024-05-08 14:02:07  116          140          15         15         Q       Configured
    2024-05-08 13:14:29  56           116          15         15         Q       Configured
    2024-05-08 12:22:07  116          56           15         15         Q       Configured
    2024-05-08 12:16:14  140          116          15         15         Q       Configured
    2024-05-08 12:11:13  116          140          15         15         Q       Configured
    2024-05-08 11:47:49  108          116          15         15         Q       Configured
    2024-05-08 11:06:11  116          108          15         15         Q       Configured
    2024-05-08 10:54:17  140          116          15         15         Q       Configured
    2024-05-08 10:32:00  116          140          15         15         Q       Configured
    2024-05-08 10:08:57  108          116          15         15         Q       Configured
    2024-05-08 09:41:19  116          108          15         15         Q       Configured
    2024-05-08 09:35:20  140          116          15         15         Q       Configured
    2024-05-08 09:11:25  116          140          15         15         Q       Configured
    2024-05-08 09:07:21  36           116          15         15         Q       Configured
    Q: Bad Channel Quality



  • 2.  RE: 5Ghz ARM Channel Churn due to Bad Channel Quality

    Posted 12 days ago

    Wondering if this 8.10.0.10 fix has any bearing. "AOS-245621 Instant APs did not switch channels nor avoided interference". After implementing cli 'channel-quality-aware-arm-disable' we still see channel changes due to interference and empty channel, but the times appear now to be outside of busy 9-5 as in these channel changes obeyed the rules for client-aware and but changes for bad channel quality did not?


    Original Message