Wireless Access

Hi,

I just noticed something on the connection modes of the wireless clients in our environment.

The band steering was enabled on the SSID-Internet and set to prefer 5Ghz with allowed band set to all however, the wireless clients are still trying and connecting to 802.11b. Would you be able to advise and enlighten me on this?

Like for this mac address 00:66:4B:7D:0C:F1, the mac address was initially associated to CN-PVG-PVG03-FLOOR05-002 using 802.11n (2.4 GHz) but when it moves and asssociate to another AP CN-PVG-PVG03-FLOOR05-001 near to i, the connection mode was already 802.11b. Both APs are using the same AP group with 80 Mhz enabled. The auth type as well was EAP (EAP-PEAP) when connecting using 802.11n (2.4 GHz) and Authenticated by AP (EAP-PEAP) using 802.11b.

If you are running ArubaOS 6.3 or 6.4, by default ClientMatch is on, which means that the Band Steering parameter is ignored.

Hi,

I am running in 6.4.2.4, using AP 225. With that client session output, What kind of behavior is that?

Jaded

Hi,

Aruba introduced a new feature called ClientMatch, this feature always choose a best AP for a client based on client location, current SNR and AP load etc.. this feature enables good throughput all the time.

The out put reflecting Client Match . until and unless you have any performance issues do not play with CM. for testing purpose you can disable it from the ARM profile.

for your ref :

Hi,

Thanks for the reply. I understood that portion on the client match but why the client will try to use 802.11b if the client match will get the best AP around to connect the client using 802.11a/n with a better thoughput? in this output, 802.11b is present.

Jaded

Jaded,

Clientmatch will try to move the client to the a band AFTER association, but only if the a-band signal strength is significantly better than the 2.4ghz band on the same access point.  If the power on the 5ghz band on the access point is not stronger than the 2.4ghz band, it will not attempt to move the client.

You should type

show ap arm client-match history client-mac <mac address of client>

on the commandline of the controller to see if any attempts have been made to steer your client.

Jaded,

Clientmatch will try to move the client to the a band AFTER association, but only if the a-band signal strength is significantly better than the 2.4ghz band on the same access point.  If the power on the 5ghz band on the access point is not stronger than the 2.4ghz band, it will not attempt to move the client.

You should type

show ap arm client-match history client-mac <mac address of client>

on the commandline of the controller to see if any attempts have been made to steer your client.

Hi,

This is one of the client that I noticed.

Please refer to the attached file. With that output, how do I check if the steering was on place? Could it be on the time of change if they move from one AP to another as long as the a band signal is higher than 2.4Ghz.

Jaded

Attachment(s)

client-match history.txt   1 KB 1 version

The controller is only moving this device from a 2.4ghz radio to another 2.4ghz radio.  Are you certain this device is 5ghz capable?  Either the strength of the signal that the AP sees your client on 5ghz is weak or your client does not support 5ghz.

What is the output of:

show ap virtual-beacon-report client-mac <mac address of your client>

Hi,

I've changed the client mac address to this one. This is a 2.4 Ghz device, does the output is telling that the AP is steering the clients to move to another optimal radio?

Jaded

Attachment(s)

client-match history.txt   7 KB 1 version

Your access points only see that client on channel 1, 6 and 11.  It does not see it on any 5ghz channels, at all.  You need to tell us why that is..

EDIT:  What are you trying to accomplish?  If the client is 2.4ghz only, what do you want to be done?