R600,SZ100 is taking overload latency with 30 clients

[harvi_yesid_cal]

R600 aps are working fine(answers about 1-5ms to gateway LAN), until 30+ clients connect to the SSID on same AP(300-600ms to gateway LAN).

Controller version: 3.5.1.0.862
Control Plane Software Version: 3.5.1.0.820
Data Plane Software Version: 3.5.1.0.807
AP Firmware Version: 3.5.1.0.1010

[jamie_walmsley]

Just re-read your comment and see your referring to latency on the AP's wired interface. for me that appears to be fine, its just wireless clients that are seeing latency.

[michael_murphy_]

My latency is wireless clients, not the ap's themselves.   I can have 15 (of 125) overload with high latency up to 600 ms or use up to 95% of airtime.



The could be interference from other ap's (power / channel) but I see these come and go.  Which would imply channels changing often.  They are telling me even though you set AUTO for power they stay on full.  That they can't manage power on the ap from the controller, which is disappointing.

[harvi_yesid_cal]

Hi Michael.

Mi problem, is your problem, hahahaha, when 30+ clients are concurrents to the same AP, answer times to the gateway(from clients), raise to 130-200ms.

About manage power on the AP from controller, i manage it on AP from controller selecting the AP and clicking on configuration at top of the page where you take screenshot.

Regards.

[michael_murphy_]

To me, if you have an AUTO setting for power, that implies that you can manage the power.  Which an enterprise controller should be able to do and that is what Ruckus says they are.  The fact that you have to manually change power means that your AP's really aren't self healing as described. 

If AP's were running at 50% power and one drops out, the controller should realize this, and then step up power on the adjacent APs to help cover the hole created by the failed unit.  Setting power manually prevents this from happening.  Also if you add another AP in the environment you would now need to manually change power levels on everything else.  That change would cause a cascade of changes throughout the building.  It's not good to manage these manually.  I have 4 building and 125 aps.  That's going to be a lot of management.  That's not enterprise stuff to me which Ruckus claims to be.   

What I don't understand is why this is an issue for me now.  I've had my system 2.5 years.  The first 2 years were all good.  Not much change in the environment.  Now things have gone to heck.  The latency and high utilization issues will roam the ap's on my network, changing locale all the time.  I suspect controller software is to blame.  I was fine at 3.2.  Somewhere in the 3.4 software my sz100's became real unhappy.  Moving to 3.5 didn't resolve the issue.  Makes using the wireless network difficult or frustrating.  You never know when things are going to fall apart or reassemble for you.

I hope to find resolutions with them soon.  Ruckus was good for 2 years for me.  Better than my previous Cisco stuff.  Now I almost long for my Cisco equipment again.

[harvi_yesid_cal]

Michael.

I think so we are not so different on issues and topology.

I'm validating update to 3.6 version or to a patch and test again January, when students come back and let you know how is going.

Thanks for your help.

Merry Christmas.