RUCKUS Technical Family

Slow performance on Ruckus ICX 8200 switches

Hi All,Last year we installed new switches. Previously we worked with HP 1950 switches. During the network project we installed new Ruckus 8200 switches. Since then we have performance issues with our ERP program called CSB. To clarify CSB is a client server connection using SQL server and ODBC driver on the client side.The problem we are having is that CSB is running very slow on the 8200 switches when being connected to a docking station. We have tested with several docking stations. Here are some setups we have tested:HP probook 450 G8 with a HP USB-C dock G4 > slow performanceHP probook 450 G8 with a Lenovo USB-C dock > slow performanceHP probook 450 G8 with a HP Thunderbolt USB-C dock > slow performanceHP elitebook 650 G9 with a HP USB-C dock G4 > slow performanceHP elitebook 650 G9 with a Lenovo USB-C dock > slow performanceHP elitebook 650 G9 with a HP Thunderbolt USB-C dock > good performanceHP probook 650 G4 with a HP ultraslim dock > good performanceHP elitebooks are only used by IT, the majority has a probook 450 G8 or a probook 650 G4. We recently bought new laptops. HP probook 450 G10 and they also have the slow performance. What we noticed is that all laptops are using a Realtek driver for the network and the elitebook are using a Intel driver with the HP thunderbolt driver. So we were thinking that there was a problem with the Realtek drivers.Countless updates did not resolve the issue. I also did several whireshark sessions just to explore what was going on and what we did notice is that the TDS protocol is taking a very long time.One more thing is once we connect a unmanaged switch, a usb to ethernet adapter, a physical telephone between docking and switch everything is running fast again. So we started investigating and the flow control feature has effect it seems. If we disable flow control on the HP switches, everything is slow again. What I read is that on Ruckus 8200 switches flow control is on by default. We have tested with several flow control settings but none of them make a difference. Also enabling the symmetrical flow control setting does not resolve the issue.Here are some outputs of whiresharks. I sorted the whole whireshark so you can see what takes the longest to process. Just to give you an image. We start CSB and then open the GPM editor (to edit labels) and that takes normally around 6 seconds to open.This output is done on our old HP switches:You can see that the TDS protocol is taking around 4.5 seconds to processThis is the output done on our new Ruckus 8200 switches:You can clearly see that the same process is taking 5-6 times longer than usual. This has effect on all things done in CSB.As a test we received a Ruckus 7150 switch. We connected the switch the same way as the 8200 switches in our network. When connected to a 7150 switch all problems are resolved. All setups as mentioned above have good performance. The GPM editor opens in around 6 seconds. The configuration of the 7150 and the 8200 are the same which is pretty basic.So from all testing we think the issue sits with our 8200 switches. We have already done updates to the RDR10010b firmware. But that does not resolve the issue.We hope by this way we can finally find a solution for this very annoying problem.Thanks in Advance!

LBO

I am new to ruckus. I have SZ 144 controller with R850 APs and third parties, Huawei and Cisco, cascaded switches connecting them.I need to configure LBO (local internet breakout) for my all SSIDs (WLANs) and APs. How can I do that?Any help please. Thank you

future of clustering & mct

tl:dr: does mct have a future or is it getting phased out.heya,we recently got 4 7850's to replace some aging cisco nexus's, they won our public tender easily & specs are impressive. we are a heavy user of vpc on the nexus side, but replacing this with mct has proven to be a challenge. our tender specified as minimal feature l3 redundancy for ipv6, so we're bound to 10.0.10 or higher.we also required link bundeling over 2 devices running independant operating systems while presenting themselves as a single device to the other end: which mct (multi chassis trunking) provides.finally, pvrst needed to be supported on all links.which is when the fun started as any vlan that becomes an mct vlan disables stp. both our partner & their ruckus liasons always came with examples from the 8.0.95 docs ( https://docs.commscope.com/bundle/fastiron-08095-l2guide/page/GUID-F20E9DED-FCDA-4C3C-BBC7-19127E9E18FC.html ), in specific the last 2 mct chapters. those are notably abcent (with good reason i guess) from 10.0 docs.in the end i got a config working with mct + pvrst when using stp in "single" mode. while not what we intended it can be argued that this meets the minimum reqs detailed in our tender.my current view of mct is not really possive after all this. documentation for the 10.0.x train as it stands is quite inconsistent, troubleshooting pretty barebones, created quite a few inconsistent (different stp protocols, differing vlans, etc) mct's which still got accepted, snmp support for mct also seems to have gotten lost somewhere along the way, issu for clusters seems to talk about stacks instead. our partner also let slip they only had 1 client which used mct & tried to push us to going for a stack instead.however, i'm running out of time & need to get these in production. since our partner has been excellent in other projects they won i don't want to return these switches due to being non complaint (since i already sent back the 8200's due to no redundant&hot swap fans & psu's - at least the model they proposed) and as noted above mct in 10.0 seems like it can use some love: i'll be going for stacking instead of clusters.long intro , now to the question: what's the plan for mct? from what the rumormill told me 10.0.x was a major rework of the code make it less complex going forward. is mct low in the todo queue (for whatever reason), is a replacement in the works, is it being phased out? i started this project on 10.0.10a, used each release including cd versions up until the 10.0.20 i'm on now, but the release notes are silent on mct items.all that said: kudos to the ruckus support staff. this might be the second time in 20 years that support was lightning fast to respond, actually knew the products they support, had frequent & to the point feedback. and actually got the bugs resolved.(this was fun: "ping vrf tstix 10.40.69.252 source 10.40.69.2532" - and 2532 is not a typo - case 01631172)

SmartZone 144 in redundancy with ZoneDirector

Hello,We currently have 67 Ruckus access points managed by two ZoneDirector 1200 in high availability. Would it be possible to add a single SmartZone 144, as the primary controller, in redundancy somehow with the two ZoneDirector?I know we would have to re-purchase licenses for all 60 APs, but is this kind of mixed redundancy possible?Thanks in advance.

Loop on access sw is Affecting distribution switch uplink

Hiwe have a branch office ( 2 Avaya ERS4826GTS-pwr+ in stack) connected to our HQ .here the ToplogyHQ -----Avaya ERS4826GTS-pwr+ in stack1/25---------VLAN238-------1/2/8 ICX7250-24P in stack Avaya ERS4826GTS-pwr+in stack2/25--------VLAN238----------2/2/8 ICX7250-24P in stackthenICX7250-24P in stack1/2/26---------VLAN238-----1/2/1ICX7250-24P -------VLAN 237 ------VLAN 80 ------VLAN 238we have multiple loop issue on VLAN 237 but the problem is that UPLINK onAvaya ERS4826GTS-pwr to HQ goes down due to this loop !can you PLease help preventing the loop to affect the AvayaERS4826GTS as it put down all the site

Ruckus r350 slow unstable bandwidth

Hello allI want to ask why my access point is monitored slowly, is it because there is a wrong configuration, for wifi 6 I turned off now I use wifi 5, if I activate it, it is monitored slowly on my wifi network, please help me to optimize the configuration of the r350 device, I have looked for ways but the access point is monitored slowly, I'm using 500 mbps bandwidth, 7 access points have been installed.big thanks