Dell Wireless 1820A & AP230, only connect at 400Mbps

Using 80MHz configured on AP230 radio profile, I cannot connect at all to the 5Ghz network (get connected to 2.4Ghz only)

Dropping to 40MHz I get the 400Mbps

SSID:    *************
Protocol:    802.11ac
Security type:    WPA2-Personal
Network band:    5 GHz
Network channel:    44
Link-local IPv6 address:    fe80::ac24:f0af:755a:a0b9%11
IPv4 address:    192.168.88.98
Manufacturer:    Broadcom
Description:    Dell Wireless 1820A 802.11ac
Driver version:    1.555.0.0
Physical address (MAC):    30-52-CB-**-**-**
 

Name:    Wi-Fi
Description:    Dell Wireless 1820A 802.11ac
Physical address (MAC):    30:52:cb:**:**:**
Status:    Operational
Maximum transmission unit:    1500
Link speed (Receive/Transmit):    144/400 (Mbps)
DHCP enabled:    Yes
 

The latest Broadcom driver for this card 1.555.0.0 (from 26/11/2015) does not have any configurable settings for 2x2 MIMO (and not even a setting for Prefer 5Ghz, hence I needed to do it in CLI of the AP)

Yet with Zyxel it was working oob at full expected speed

It is not client decision if the driver has no such option!

Client will go for 2.4 because that is easier.

Only way to get it using 5Ghz is to have in config:

radio profile uknh_radio_ng_ng0 band-steering enable
radio profile uknh_radio_ng_ng0 band-steering mode force-5g

which works well and makes the client connect to 5Ghz (as show above - Network band:    5 GHz)

So there is no issue where client connects!

I have ofcourse tested also with differently named SSID for 5Ghz (getting exactly the same results = 400Mbps)

But the whole point of this exercise was to NOT have separate SSIDs, but a single blanket one that covers everywhere. Which is fine, apart from the speed of connection

AP230 can do 1.3 Gbps in the 5 GHz 802.11ac mode

Anybody has any idea to what CLI command this translates (on AC radio profile)?

Enable Aggregate MAC Protocol Data Units: Select the check box to enable AMPDU (Aggregate MAC Protocol Data Unit) transmissions to reduce overhead when the transmission channel is busy. When you enable AMPDU, the HiveAP combines data frames into fewer, larger frames before transmitting them and is able to recognize the format of larger frames when it receives them. Generally, enabling AMPDU increases performance. Clear the check box to disable AMPDU. By default, it is enabled.

My full radio profile for 802.11ac:

radio profile uknh_AP230_radio_ng_ac0
radio profile uknh_AP230_radio_ng_ac0 phymode 11ac
radio profile uknh_AP230_radio_ng_ac0 dfs
radio profile uknh_AP230_radio_ng_ac0 channel-width 40
radio profile uknh_AP230_radio_ng_ac0 acsp max-tx-power 15
radio profile uknh_AP230_radio_ng_ac0 acsp access channel-auto-select time-range 01:00 04:00
radio profile uknh_AP230_radio_ng_ac0 acsp interference-switch enable
radio profile uknh_AP230_radio_ng_ac0 scan access client power-save
radio profile uknh_AP230_radio_ng_ac0 max-client 50
radio profile uknh_AP230_radio_ng_ac0 interference-map enable
radio profile uknh_AP230_radio_ng_ac0 interference-map cu-threshold 35
radio profile uknh_AP230_radio_ng_ac0 interference-map crc-err-threshold 35
radio profile uknh_AP230_radio_ng_ac0 deny-client 11b
radio profile uknh_AP230_radio_ng_ac0 short-guard-interval
radio profile uknh_AP230_radio_ng_ac0 benchmark phymode 11b rate 11 success 60 usage 50
radio profile uknh_AP230_radio_ng_ac0 benchmark phymode 11b rate 5.5 success 70 usage 50
radio profile uknh_AP230_radio_ng_ac0 benchmark phymode 11g rate 36 success 70 usage 50
radio profile uknh_AP230_radio_ng_ac0 benchmark phymode 11g rate 24 success 80 usage 50
radio profile uknh_AP230_radio_ng_ac0 benchmark phymode 11a rate 36 success 70 usage 50
radio profile uknh_AP230_radio_ng_ac0 benchmark phymode 11a rate 24 success 80 usage 50
radio profile uknh_AP230_radio_ng_ac0 benchmark phymode 11n rate mcs4/2 success 80 usage 50
radio profile uknh_AP230_radio_ng_ac0 benchmark phymode 11n rate 54 success 70 usage 50
radio profile uknh_AP230_radio_ng_ac0 benchmark phymode 11ac rate mcs2/2 success 80 usage 50
radio profile uknh_AP230_radio_ng_ac0 benchmark phymode 11ac rate 54 success 70 usage 50
radio profile uknh_AP230_radio_ng_ac0 frameburst
radio profile uknh_AP230_radio_ng_ac0 acsp power-maxdrop 9

 

T

Just because the client does not offer an option to select a frequency does not mean that the client does not make the decision. The AP can offer the client the SSID and connection options, but it cannot decide which of the options the client has to uses, nor which frequency band it uses. 

This also applies when band steering is switched on. 

Well, what can I say to convince you?

With no option in driver, withOUT “band-steering mode force-5g” in AP config client will connect only to 2.4Ghz, WITH “band-steering mode force-5g” in AP config, same client will connect to 5Ghz

While I know the commands for A-MPDU & A-MSDU because the lot is available ie here

I have checked my enterprise config & while Enable aggregate... is checked in ac radio profile, it does not reflect in the actual config, it only shows in the ng radio profile (hence the question, because it makes no sense to me)

Hello,

You don't have to convince me. I understand that you cannot set the channel selection on your client and that therefore only bandsteering on the AP helps (since you want to use one SSID in both frequency bands).

I just wanted to point out, that by wifi standard, it is a decision of your client and therefore bandsteering is only a workaround. But it's nice if it works.

Regarding frame aggregation: According to standard 802.11ac, frame aggregation is ALWAYS used here and therefore it does not have to be explicitly turned on. For example see here:

https://www.oreilly.com/library/view/80211ac-a-survival/9781449357702/ch03.html

Specifically: "802.11ac, however, adds an interesting new take on aggregation: all frames transmitted use the aggregate MPDU (A-MPDU) format. Even a single frame transmitted in one shot is transmitted as an aggregate frame."

Hi Sebus,

MCS data rate is chosen by a transmitting device algorithm (client or AP - it’s independent in each direction) based on several criteria, in particular RF-related indicators such as SNR. Are both APs in the same distance to the client device, ie. is the RSSI on the client equal? Are both APs on the same channel or not? If not, what other traffic (nearby APs, client devices) appears on the channels?

Just FYI, you won’t get 1.3 Gbps datarate unless you have 3x3 MIMO WLAN on a device, here you can find some examples: clients.mikealbano.com

BTW forcing 5 GHz might produce other issues when a dual-band device keeps trying to connect to the SSID on 2.4 GHz band because of its internal algorithm decision flow. Without that, clients are going to jump between bands occasionally though. So if separate SSIDs are not an option, I’d recommend to consider ‘Encourage’ instead of ‘Force’.

Hope that helps,

Tomasz

Hi Sebus,

That sounds totally reasonable that you’d like to see the highest achievable data rate for your client device on both, and that is in fact possible for 1820A chipset to reach 866.7 Mbps. We can definitely aim for this in lab environment. I have never had a problem to get it so far on any Extreme APs (IdentiFi/WiNG/XIQ). There is less WLAN chipset manufacturers than WLAN infrastructure/client vendors. Datarate-related components are pretty basic in that terms, so if there are no sw bugs (on either side) or misconfig or bad environment it should work rather similar on any AP/STA equipment pair (assuming same characteristics: MIMO, channel width, RSSI and so on). To be clear, 80 MHz is a must for 866.7 Mbps datarate to be achievable with 2x2 MIMO 11ac device, see here: https://mcsindex.net/

Please let me make perfectly sure about this: is RSSI on the client the same for the signals from both XIQ/Zyxel during testing? Like -50 dBm vs -50 dBm? I’m asking for this as I see some glimpses of ACSP on the XIQ side. Moreover (maybe it’s because of late hour) I don’t see TxP setting on Zyxel. As a good practice, TxP should not be set to maximum and it should not be too low if we aim for both high datarate and effective throughput.

If that potential testing environment issue mentioned above was checked, I would only recommend contacting GTAC so they can assist in narrowing down possible causes with XIQ AP (AP software bug, client device driver issue, RF thing, configuration thing). Or, if it’s nothing urgent, maybe few others will have some food for thoughts as well. @Sam Pirok@Christoph S.@Ovais Qayyum

Hope that helps,

Tomasz

Hi Sebus,

I’d say we should focus on troubleshooting 80 MHz issue with AP230 then. I’ll try to reproduce the issue to look around the AP logs myself but hopefully someone already fell into that problem before.

Could you please tell us the firmware version currently running on that AP?

Take care,
Tomasz

Anybody? Or am I the only one with this issue?

sebus