Meru Contention and Chromebooks
We are running about 30 Chromebooks per AP at our installation, with about 18 AP's total. Our controller an MC 1500, AP's are 832i's. Avg distance between AP = 75'. About 70% of clients network wide are 802.11ac/5.2Ghz. All Chromebooks are AC 5.2Ghz.
We have recurring problems, the most significant being station association. When a classroom of Chromebooks log in simultaneously, it takes about 20 minutes for all station/AP associations to take place. Chromebook logs show the station associates, then it disconnects, most likely because of a change in RSS. Meru controller logs show disassociation. Seems to me this could work much better. A Meru engineer has tweaked and adjusted quite a bit, the solution seems to center around spreading out connections to more AP's (e.g. reducing TX to balance AP's better). Does this make sense to others? Wasn't virtual cell supposed to solve this kind of problem?
Do others of you have problems with high density installations? Chromebooks?
