Familia técnica RUCKUS

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

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)

Assign Policy Based on Device Name

Is there a way to assign a policy based on the device name? I am trying to do something clever with the workflow to pick up the device name, and pass it to the USERNAME variable, and then using a RADIUS attribute group assign the policy based on a regex of the device name, but I can't seem to get it to work.Any guidance would be great!ThanksJames

Wierd DHCP Issue

ICX7150 switch having issues with DHCP helper service. We have couple virtual interfaces with DHCP Helpers attached and we reboot the switch and the DHCP helper seems to do its job then about 5 min after the client stops getting DHCP requests from the server. Its almost like the DHCP helper service is clashing on the device. Any ideas?

What OS version will Ruckus one be able to support openroaming?

What OS version will Ruckus one be able to support openroaming?

AP R760 not discovered by vSZ

I've a vSZ and an AP, on the same vlan (management).First curious problem, the AP has not been able to get a DHCP ip address.Then I manually configured an IP on the AP and, my AP and my vSZ are able tto ping each other, as ther are able to ping the internet or local dns addresses.I did manually enter the "Primary Controller Addr" in the AP Administration/management configuration, with no success. Also, I did create a DNS entry for ruckuscontroller.something.com and zonedirector.something.com. I also tyring with the DHCP option 43.I did a pfsense firewall, but there is no specific rules for this vlan, all traffic allowed. My AP is on a trunk, management vlan is untag and the others are taged.The fact that the DHCP is not working in the first time is still bugging me, but I can't see the reason for all this.Please advise. Thank you.