I have used Client Load Balancing with good results for a high density deployment. If my understanding is correct the way it works is this: All APs over which you want to load balance the clients must be on the same controller If AP1 has "n" more clients on it than AP2 then further association requests are refused by AP1 encouraging clients to try AP2 This refusal can be limited to "x" number of attempts before access is granted anyway as the assumption is that ultimately you want to provide service to the client Both "n" and "x" are configurable numbers but there is a default which I don't have time to look up right now. Doing the above, turning on band select and turning off lower data rates on the radios spread a huge number of clients (350+) over a relatively small number of APs/radios (8 x 3502I) fairly evenly and feedback from delegates was good.
... View more
I upgraded a customer 5508 to 184.108.40.206 the other day and now can't access the GUI using Google Chrome. I get a page saying "SSL connection error". It works fine with Internet Explorer and Firefox. The final Wireshark packet in the Chrome trace says "Handshake Failure". Have upgraded Chrome and tried with different laptops with the same result. I have also upgraded our lab controller (also a 5508) and that's the same. Anyone else seeing this?
... View more