MR56 Not Allowing 5Ghz clients tro connect

AxL1971
A model citizen

MR56 Not Allowing 5Ghz clients tro connect

MR56 running firmware MR 31.1.6

 

For information we only allow corporate laptops to connect to 5 Ghz other non coperate laptops (phones as an example) only connect on 2.4 Ghz

 

Noticed this twice last week, one AP had a large number of devices connected to the 5Ghz radio but another AP close by did not have any 5Ghz connected, devices connected ok to both AP's on the 2.4Ghz

 

Once I restarted the AP with no 5Ghz devices, 5Ghz clients were able to connect.

 

Did not see this behaviour before. 

 

Just curious if others have noticed similair behaviour.

6 Replies 6
alemabrahao
Kind of a big deal

I think that this may be a version bug, but just out of curiosity, do you have Client Balancing enabled? If so, have you tried disabling it?

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
AxL1971
A model citizen

client balancing disabled

alemabrahao
Kind of a big deal

So I suggest you downgrade the firmware to test and also open a support case so they can investigate.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
AxL1971
A model citizen

be be honest not going to downgrade as it has only occured twice and a reboot of the AP's resolves this. Also we are replacing the MR56 with the CW9166I ina few weeks

PhilipDAth
Kind of a big deal
Kind of a big deal

31.1.7 is the current stable firmware release.  I would consider upgrading to that.  Release notes:

 

Wireless firmware versions MR 31.1.7 changelog

Important note

Bug fixes

  • General stability and performance improvements
  • False positive DFS alerts in Japan on MR56 APs
  • APs stop transmitting on wired interfaces due to exception (Wi-Fi 6 APs)
  • Clients disconnect with error code 17 (Wi-Fi 6, Wi-Fi 6E, Wi-Fi 7 APs)
  • Clients disconnect with reason code 0 (reserved) (Wi-Fi 6, Wi-Fi 6E, Wi-Fi 7 APs)
  • Association ID mismatch (Wi-Fi 6, Wi-Fi 6E, Wi-Fi 7 APs)
  • 2.4GHz 802.11n clients unable to connect (Wi-Fi 7 APs)
IvanJukic
Meraki Employee All-Star Meraki Employee All-Star
Meraki Employee All-Star

Hi @AxL1971 ,

 

The two most common causes are, people are moving about in one area. Say a Presentation. The other situation is when the Minimum bit rate & SNR need adjusting for the local environment. The Wireless client makes the decision which AP it associates to. To ensure you have a good balance between coverage and overlap. Have a look at the below guide, I find it provides a good explanation with visuals. 


"Various factors influence the client's decision of which AP it should connect to. The main factors that can be manipulated to affect this are:


- Signal to Noise ratio (SNR)
- Minimum bit rate

"

 

 

https://documentation.meraki.com/MR/Wireless_Troubleshooting/Wireless_Issue_Resolution_Guide#Clients...

 

 


Cheers,

Ivan Jukić,
Meraki APJC

If you found this post helpful, please give it kudos. If it solved your problem, click "accept as solution" so that others can benefit from it.
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco ID. If you don't yet have a Cisco ID, you can sign up.