Noticed this repeatedly, but inconsistently: while browsing and connected to channel 149---
Sporadically page loading stops... not browser specific that I notice.
Turning off/back on WIFI fixes it, temporarily.
Did some searching, and found this thread, which though written from home use perspective, made me curious.
avoid 80mhz channel width
Is this not an issue, in a controller-enviroment?
When using 80mhz channels you have:
- Fewer non-overlapping channels so interference is more likely.
- Some clients that have packet aggregation issues that could affect performance
- WLAN infrastructures that rarely run 80mhz wide channels so bugs with 80mhz wide implementations are less likely to be seen or fixed.
- Throughput that can be affected by impairment on any of 4 channels.
- If you use DFS, the more likely the chance of false radar events to occur..
Long story short, there are quite a few things that could go wrong with 80mhz channels.
Sounds like something to be avoided, unless throughput is overly important.
So how/where does the Aruba controller address this?
The Aruba controller is limited to the number of channels in use and the overlap created by having access points within earshot. You must design your network properly because an Aruba controller cannot overcome a poor design.
OK, but it does sound like you are not crazy about 80 width... is mimimizing 80 mhz width something that can be handled within an AP configuration file, or is that part of how the Controller integrates APs within an area?
Sorry if I'm oversimplifying, still feeling my way with a lot of this.
You would specify the 80Mhz settings within the controller which in turn would be pushed out to AP. These settings are configured under the ARM profile.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2020 Hewlett Packard Enterprise Development LPAll Rights Reserved.