It is still not working. I tried reduce the power level and disable 2.4GHz SSID. The device is still not able to connect to 5G SSID with 160Mhz enabled.
Original Message:
Sent: Jul 12, 2023 05:08 AM
From: Herman Robers
Subject: Can't achieve 160MHz bandwidth on AP-345 (RW)
According to the screenshot, the AP is broadcasting 160MHz channels.
If clients don't connect, but connect to 2.4GHz, that probably has to do with that you have both radios on the same power level, so the 2.4GHz radio is much stronger, and more attractive to clients. On 5GHz the AP power should be at least 6dB higher than 2.4GHz, with wider channels (160MHz = 8x 20MHz) the power should be 9 dB higher for the same SNR. Either disable the 2.4GHz radio, or put it on 3 or 6 dBm max to see if clients will connect then...
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
Original Message:
Sent: Jul 12, 2023 01:07 AM
From: catro
Subject: Can't achieve 160MHz bandwidth on AP-345 (RW)
Yes the AP is broadcasting on channel 36S. I just want to use 160MHz only when I need high bandwidth. So it is nice to have it.
Original Message:
Sent: Jul 11, 2023 08:29 AM
From: Herman Robers
Subject: Can't achieve 160MHz bandwidth on AP-345 (RW)
Does 'show ap bss-table' show that the AP is broadcasting on channel 36S?
As mentioned 160GHz is not used so much, maybe not all clients support it?
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
Original Message:
Sent: Jul 11, 2023 05:56 AM
From: catro
Subject: Can't achieve 160MHz bandwidth on AP-345 (RW)
Thanks for the quick reply, Herman! Here is the output.
# show ap allowed-channelsAllowed Channels for AP Type 345 Country Code CN------------------------------------------------PHY Type Allowed Channels-------- ----------------2.4GHz (indoor) 1 2 3 4 5 6 7 8 9 10 11 12 135GHz (indoor) 36 40 44 48 52 56 60 64 149 153 157 161 1652.4GHz (outdoor) 1 2 3 4 5 6 7 8 9 10 11 12 135GHz (outdoor) 149 153 157 161 1652.4GHz 40MHz (indoor) 1-5 2-6 3-7 4-8 5-9 6-10 7-11 8-12 9-135GHz 40MHz (indoor) 36-40 44-48 52-56 60-64 149-153 157-1612.4GHz 40MHz (outdoor) 1-5 2-6 3-7 4-8 5-9 6-10 7-11 8-12 9-135GHz 40MHz (outdoor) 149-153 157-1615GHz 80MHz (indoor) 36-48 52-64 149-1615GHz 80MHz (outdoor) 149-1615GHz 160MHz (indoor) 36-645GHz 160MHz (outdoor) None5GHz (DFS) 52 56 60 645GHz (ZWDFS) disable
I tried to force channel to 36S, then all my devices are not able to connect to the AP.
Original Message:
Sent: Jul 11, 2023 05:41 AM
From: Herman Robers
Subject: Can't achieve 160MHz bandwidth on AP-345 (RW)
First check if for your regulatory domain the 160 MHz channels are allowed (run command via Support menu or SSH/console: show ap allowed-channels).
Then, I could not get 160MHz assigned either through ARM, possibly because there is too much interference and it's a bad idea to run 160MHz channels in most situations), but if you go in the AP, Edit, then assign the channel 'by administrator', it works for me:
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
Original Message:
Sent: Jul 10, 2023 03:46 AM
From: catro
Subject: Can't achieve 160MHz bandwidth on AP-345 (RW)
Hello, I have the same issue to enable 160MHz as mentioned in this post. Can anyone help? Thanks in advance! More than that, I attempted to set 160mhz-support to auto in the CLI. But the result is the same.
Country code: CN
Instant verions: 8.10.0.7 LSR
I have AP-345 (RW) with latest firmware and Regulatory Setting, using it without controller. The documentation states that AP supports 160MHz mode, but I can't make it work. The maximum I get is the 80MHz band.
When ARM is enabled, AP automatically selects channel 36E, which means 80MHz.
If I turn off ARM (Configuration > Access Points > edit current AP > Radio > switch 5 GHz band from "Adaptive radio management assigned" to "Administrator assigned"), channel selection becomes available. And, among others, there are channels 36S and 100S, which means 160Mhz bands.
Also, in Configuration > RF, in advanced options, in "Valid 5 GHz channels" all available channels selected, including 36S and 100S.
If I choose 36S or 100S, AP pretends that it works, but no any client can connect to it. As clients I have Macbook Pro 2021, IPhone 12, ASUS laptop, TV-box, and others. They just can't see Wi-Fi-network on AP-345.
If I switching channel on AP-345 to any 20/40/80 MHz bands (36, 36+, 36E, etc.), all clients can successfully connect and work with it.
I have some router with OpenWRT, and it have Channel Analysis tool. And it sees Wi-Fi-network on AP-345, but shows it 80 MHz-width band when it switched to 36S or 100S mode.
Also this third-party router can work with 160MHz-bands itself, and if I creating access point on it, my clients, such as laptop, works with it in 160MHz mode without any issues. So I believe there is no problem with clients.
What am I doing wrong with Aruba AP?