partnerpro-get-started-col4
RTF-team-overview

What is the RUCKUS Technical Family?

RUCKUS Technical Family (RTF) is a vibrant community of networking professionals and technology enthusiasts using RUCKUS solutions.

More than just another tech group, RTF thrives on the connections and expertise of its members.
 

Why You Should Join RTF

We are passionate about creating simple, powerful networking solutions. Join us to share knowledge, gain early access to new technologies, and connect with top engineers. As a partner, you'll enjoy exclusive webinars, direct collaboration with experts, and access to a global network in over 20 languages.

Join the RUCKUS Technical Family today and be part of a community built on knowledge and relationships.

Why choose the RUCKUS Technical Family?

RUCKUS-Web-Icons_Stay-Updated

Stay updated with the latest technology

RTF provides regular webinars and newsletters with all of the latest industry insights to keep you ahead of the curve.

RUCKUS-Web-Icons_RUCKUS-Expert

Reliable support from RUCKUS Experts

Engage directly with RUCKUS experts for quick, reliable solutions to your technical challenges.

RUCKUS-Web-Icons_Curated-Content

Curated, high-quality technical content

Receive only the most relevant and actionable content through our curated resources

RUCKUS-Web-Icons_Collab

Collaborative community

Connect with peers, share experiences, and collaborate to solve even the toughest technical issues. 

Webinars

smart-campus-ebook-hero400b

Monthly Webinar

January – 2025 Networking Technology Trends 

Stay ahead with our monthly webinars that cover the latest trends, updates, and best practices in networking technology. Designed for continuous learning and keeping your skills sharp, these sessions are perfect for all RUCKUS professionals. Our webinars qualify eligible Partners to receive Continuing Education (CE) points, an easy and convenient way of extending their RUCKUS certifications! More information can be found here.

Register now 

 

RTF Hospitality & MDU webinar

IPTV & Streaming media; MDU Best Practices

Dive into specialized content focused on Multi-Dwelling Units (MDU) and the hospitality sector. Learn how to design and deploy customized RUCKUS solutions to meet the unique challenges of these environments.

Sign up for this webinar

hospitality-main-hero-400b

RTF-webinar-archive-hero_500x281

Webinar archive

Check out older webinar recordings available in a variety of local languages.

View the webinar archive


RTF-events-calendar

Community events

Stay connected in person and online. Find events in your industry and connect with professionals just like you. 

View upcoming events

 

 

 

Stay informed with the RUCKUS Technical Family Newsletter

 

Subscribe to our newsletter for the latest RUCKUS news, technical insights, and updates. Whether you're a seasoned pro or just starting out, our newsletter delivers valuable content straight to your inbox

 

Read past RUCKUS Technical Family Newsletters

 

Forums

Discuss your local projects and ask any technical questions using our dedicated RTF forums channel. Our global team of System Engineers take an active part in these discussions, offering help and advice. For the list of all forum topics visit community.ruckuswireless.com.

RUCKUS Community

I recently upgraded my ICX7150-C12P to 10.0.10f SPR firmware from the 09.0.10j.cd4 SPS and since re-adding the switch to unleashed i have the problem that the switch keeps wanting to join on 5.137.250.224.(see screenshot below) Even tho the switch is already connected to unleashed and otherwise working fine.When approving this "switch" it isn't able to communicate to this specific interface, it also can't be removed. Removing the existing switch doesn't resolve it either. I can get it working again by specifing the correct IP in unleashed for the discovery, but then i get the annoying 5.137.*.* IP back in the approval list. This isn't a valid IP in my subnet, and also never set in the switch. The switch has also been factory reset since the firmware upgrade and the troubleshooting.Unleashed logs report: Failed to add ICX [c0:c5:20:99:4f:f1]. The ICX already exists. Please enter a different one. The MAC address from the one i specified (my managemt ip) and the one unleashed tries to connect (5.137.*.*) are the same (?)I'm running unleashed version 200.16.7.0.402, i have tried to upgrade 200.17 but this gave me alot of issues with my R350 AP's.I would like to keep on the 10.0 track now, but if there isn't any fix or update expected soon i think it's the best to go back to the 9.0 track.This is what the unleashed logs tell me:Dec 28 17:39:03 RuckusAP Beneden sys_wrapper: icx_test_default():ICXD: ICX[id=2]: 5.137.250.224: start to access ICX as user "super".Dec 28 17:39:03 RuckusAP Beneden syslog: M8d2023S0D0 pid=2769[14546], icxd_state_loop():ICXD: ICX[id=2]: 5.137.250.224: OLD_STATE=[discovery], have_approve=1, icx_username=[]Dec 28 17:39:02 RuckusAP Beneden ZD-APMgr: Ma33b02S0D0 IPC_thread rcv ping from TACMONDec 28 17:38:53 RuckusAP Beneden syslog: M8d2022S0D0 pid=2769[14546], icxd_state_loop():ICXD: ICX[id=2]: 5.137.250.224: NEW_STATE=[discovery], delay 10 seconds.Dec 28 17:38:53 RuckusAP Beneden syslog: M8d2022S0D0 pid=2769[14546], icxd_discovery():ICXD: ICX[id=2]: 5.137.250.224: icx-test-default done, result is [NO_RESULT]Dec 28 17:38:53 RuckusAP Beneden sys_wrapper: icx_test_default():ICXD: ICX[id=2]: 5.137.250.224: lastline "==================== LOGIN(test-default): (Sat Dec 28 17:38:43 CET 2024) ====================", expect "assword:".Dec 28 17:38:51 RuckusAP Beneden syslog: Mad1fd6S0D0 pid=2769[2769], doJobEx():worker: action:[cleanup-response], Done.Dec 28 17:38:43 RuckusAP Beneden empty: forked dbclient -y -l super 5.137.250.224Dec 28 17:38:43 RuckusAP Beneden empty: version 0.6.20b startedDec 28 17:38:43 RuckusAP Beneden sys_wrapper: icx_test_default():ICXD: ICX[id=2]: 5.137.250.224: ping 5.137.250.224 success.Dec 28 17:38:43 RuckusAP Beneden mping[21230]: status=succ result=34 to_pid=1243 ports=1 ports_signaled=1Dec 28 17:38:43 RuckusAP Beneden mping[21230]: mping 512: cmd=arping -u -z 195 -q -f -c1 -w1 -S 34 -P 21230 -l/tmp/mping_hm_latency.log -I br0 192.168.168.1 &Dec 28 17:38:43 RuckusAP Beneden mping[21230]: Target default gateway 192.168.168.1 via br0Dec 28 17:38:41 RuckusAP Beneden sys_wrapper: icx_test_default():ICXD: ICX[id=2]: 5.137.250.224: start to access ICX as user "super".Dec 28 17:38:41 RuckusAP Beneden syslog: M8d2022S0D0 pid=2769[14546], icxd_state_loop():ICXD: ICX[id=2]: 5.137.250.224: OLD_STATE=[discovery], have_approve=1, icx_username=[]Dec 28 17:38:32 RuckusAP Beneden ZD-APMgr: Ma33b01S0D0 IPC_thread rcv ping from TACMONDec 28 17:38:31 RuckusAP Beneden syslog: M8d2021S0D0 pid=2769[14546], icxd_state_loop():ICXD: ICX[id=2]: 5.137.250.224: NEW_STATE=[discovery], delay 10 seconds.Dec 28 17:38:31 RuckusAP Beneden syslog: M8d2021S0D0 pid=2769[14546], icxd_discovery():ICXD: ICX[id=2]: 5.137.250.224: icx-test-default done, result is [NO_RESULT]Dec 28 17:38:31 RuckusAP Beneden sys_wrapper: icx_test_default():ICXD: ICX[id=2]: 5.137.250.224: lastline "==================== LOGIN(test-default): (Sat Dec 28 17:38:21 CET 2024) ====================", expect "assword:".Dec 28 17:38:21 RuckusAP Beneden empty: forked dbclient -y -l super 5.137.250.224Dec 28 17:38:21 RuckusAP Beneden empty: version 0.6.20b startedDec 28 17:38:21 RuckusAP Beneden sys_wrapper: icx_test_default():ICXD: ICX[id=2]: 5.137.250.224: ping 5.137.250.224 success.Dec 28 17:38:21 RuckusAP Beneden syslog: Mad1fceS0D0 pid=2769[2769], doJobEx():worker: action:[cleanup-response], Done.Dec 28 17:38:19 RuckusAP Beneden sys_wrapper: icx_test_default():ICXD: ICX[id=2]: 5.137.250.224: start to access ICX as user "super".Dec 28 17:38:19 RuckusAP Beneden syslog: M8d2021S0D0 pid=2769[14546], icxd_state_loop():ICXD: ICX[id=2]: 5.137.250.224: OLD_STATE=[discovery], have_approve=1, icx_username=[]Dec 28 17:38:13 RuckusAP Beneden mping[20980]: status=succ result=34 to_pid=1243 ports=1 ports_signaled=1Dec 28 17:38:13 RuckusAP Beneden mping[20980]: mping 512: cmd=arping -u -z 195 -q -f -c1 -w1 -S 34 -P 20980 -l/tmp/mping_hm_latency.log -I br0 192.168.168.1 &Dec 28 17:38:13 RuckusAP Beneden mping[20980]: Target default gateway 192.168.168.1 via br0Dec 28 17:38:12 RuckusAP Beneden syslog: Mad1fc9S0D0 pid=2769[2769], icxd_av_is_supported():ICXD: AV_Profile[icx-id:2,unit-id=1] The model don't support AV profileDec 28 17:38:12 RuckusAP Beneden syslog: upgrade_debug: pid=20976, insert_field_to_upgrade_ap_list(): firmware_file open failureDec 28 17:38:12 RuckusAP Beneden syslog: upgrade_debug: pid=20976, get_ap_list(): see [/tmp/unleashed_upgrade/upgrade_ap_list_from_election.xml.ready], ap-list ready!Dec 28 17:38:12 RuckusAP Beneden syslog: upgrade_debug: pid=20976, get_ap_list(): ap-list loop 0.Dec 28 17:38:09 RuckusAP Beneden syslog: M8d2020S0D0 pid=2769[14546], icxd_state_loop():ICXD: ICX[id=2]: 5.137.250.224: NEW_STATE=[discovery], delay 10 seconds.Dec 28 17:38:09 RuckusAP Beneden syslog: M8d2020S0D0 pid=2769[14546], icxd_discovery():ICXD: ICX[id=2]: 5.137.250.224: icx-test-default done, result is [NO_RESULT]Dec 28 17:38:09 RuckusAP Beneden sys_wrapper: icx_test_default():ICXD: ICX[id=2]: 5.137.250.224: lastline "==================== LOGIN(test-default): (Sat Dec 28 17:37:59 CET 2024) ====================", expect "assword:".Dec 28 17:38:02 RuckusAP Beneden ZD-APMgr: Ma33b00S0D0 IPC_thread rcv ping from TACMONDec 28 17:37:59 RuckusAP Beneden empty: forked dbclient -y -l super 5.137.250.224Dec 28 17:37:59 RuckusAP Beneden empty: version 0.6.20b startedDec 28 17:37:59 RuckusAP Beneden sys_wrapper: icx_test_default():ICXD: ICX[id=2]: 5.137.250.224: ping 5.137.250.224 success.Dec 28 17:37:57 RuckusAP Beneden sys_wrapper: icx_test_default():ICXD: ICX[id=2]: 5.137.250.224: start to access ICX as user "super".Dec 28 17:37:57 RuckusAP Beneden syslog: M8d2020S0D0 pid=2769[14546], icxd_state_loop():ICXD: ICX[id=2]: 5.137.250.224: OLD_STATE=[discovery], have_approve=1, icx_username=[]Dec 28 17:37:51 RuckusAP Beneden syslog: Mad1fb7S0D0 pid=2769[2769], doJobEx():worker: action:[cleanup-response], Done.
(753) (10) (0) (0)
Hello,Will a stack of ICX-7150's run if the firmware is mismatched? I intend to perform a network firmware upgrade and may not have access to all the switches in the stack and on the network in the same day. Will the switches still communicate if they are not all on the same firmware?
(91) (4) (0) (0)
I am new homeowner to existing system... password was left to us by previous owner so we have been using for a year with original setup.I cannot access dashboard from PC or mobile. I cannot update any firmware because I cannot access dashboard.R510... lights are working fineDefault IP address: 192.168.0.1 however, I had to do an arp -a CMD to find out connected IP addresses and find correct one. I get to the admin/login.jsp screen to enter my login and password and this is the error I get, using admin and sp-admin as stated on the unit, also with the username and password I have been using for the past year...and the admin Lennar username and password that is on a printed sticker on the back of the device.Thank you for assistance
(28) (0) (0) (0)
Hi everyone,Iam having trouble accessing the web interface on my Ruckus ZoneDirector 1200. Whenever I log in, the interface partially loads, but then the screen goes black, and I cannot navigate or access any settings.The network itself seems to be working fine, as all the access points and connected clients are functioning normally, but I can’t manage the system through the web interface.I have tried clearing my browser cache, using different browsers like Chrome and Firefox, and even rebooted the ZoneDirector, but the issue persists.The device is running the latest firmware, so I’m unsure if this is a compatibility problem or something else in the configuration.Has anyone faced this issue before or have any suggestions for fixing it? thank you in advance .
(38) (0) (0) (0)
(Sorry if this is a duplicate post, but I tried 2 days ago and it still hasn't appeared.)I have an R650 running Unleashed (200.17.7.0.139) that periodically renegotiates the uplink speed down to 100Mbps, where it sticks. My network is:Router (1g port) -> generic unmanaged switch (2.5g) -> POE injector (Ruckus NPE5818) -> R650PoE adapter has a 48v power supply, AP Operating Mode is set to 802.3at in the Ruckus dashboardWhen the uplink negotiates down, the Dashboard/Ethernet Port Status for eth1 changes from 2500Mbps to 100MbpsCycling the switch power supply (the easiest way for me to force renegotiation) immediately returns speed to expected, and it stays there for anywhere from a few hours to a few days before dropping again.Based on other answers here, I have replaced all the cables (all CAT 6e or CAT 7), and replaced the switch, with no change.I've examined the logs, and while I don't understand evert\ything there I do see that at the time of the speed dropping, I have a handful of lines over a short period like the following:Jan 19 20:17:30 RuckusAP kernel: [182922.157158] nss-dp 3a007000.dp3 eth1: PHY Link is downfollowed a few lines later byJan 19 20:17:45 RuckusAP kernel: [182937.189082] nss-dp 3a007000.dp3 eth1: PHY Link up speed: 1000but the *last* "Link is down" message was followed byJan 19 20:23:10 RuckusAP kernel: [183261.941081] nss-dp 3a007000.dp3 eth1: PHY Link up speed: 100This sequence does not appear anywhere else in the logs, just when the speed drops, and is usually over a 5-10 minute period; after the drop to 100Mbps it remains stable until I get around to power cycling the switch again.What is a reasonable next step in my diagnosis? I was thinking of trying powering the AP directly instead of by POE, but that requires me hauling my 70-year-old ass up a tall ladder so would prefer to try less physical things first.What could be triggering the link down state? Can I ssh into the AP and turn off whatever is doing this?Thanks in advance for your help.
(60) (2) (0) (0)
Continuing this issue I am reposting the issue posted by someone as i dont get proper reply in comments.https://community.ruckuswireless.com/t5/ICX-Switches/DHCP-server-icx-7750/m-p/101495#M7109SW version is 08.0.95pT203I have created 2 VLANS. For example vlan 100 and vlan 101For vlan 100 I have used the dhcp pool created on ICX7750 and For Vlan 101 I used the TP-link router to provide DHCP. Both PC+ Mobile working fine with VLAN101 in SSID101 but VLAN 100 has SSID 100 in AP on which only PC get connects.On checking VSZ6.1.2 it shows in AP clients i can see the DHCP ip received by the PC but the DHCP from the mobile phone reaches to VSZ but it shows 0.0.0.0:: and it donot request the dhcp to switch but incase of PC it does with the same SSID.On checking via Wireshark:--On Laptop (Wi-Fi)--Receives DHCP Pool AddressDHCP Request:*Option:(50) Requested IP address (192.168.92.4)DHCP ACK:*Option:(54) DHCP Server Identifier(192.168.92.1)--On Mobile (Same Wi-Fi)--Do not lease IP address, no Request and ACK, Only Discover is seen in Wireshark*Option:(53) DHCP Message Type (Discover)DHCP: Discover (1)*Option:(61) Client IdentifierClient Mac Address:<------>*OPtion:(12) HostnameHostname: <Redmi-12-5G>*option:(55) Parameter Request listLength:12Parameter Request List Item: (1) Subnet maskParameter Request List Item: (3) RouterParameter Request List Item: (6) Domain name ServerParameter Request List Item: (15) Domain nameParameter Request List Item: (26) Interface MTUParameter Request List Item: (28) Broadcast AddressParameter Request List Item: (51) IP Address lease timeParameter Request List Item: (58) Renewal time valueParameter Request List Item: (43) vendor-specific InformationParameter Request List Item:(114) DHCP Captive-PortalParameter Request List Item: (108) IPv6-Only Preferredswitch configuration:ip dhcp-server pool vlan100excluded-address 192.168.92.1!excluded-address 192.168.92.100 192.168.92.254lease 1 0 0network 192.168.92.0 255.255.255.0option 3 ip 192.168.92.1deployip helper-use-responder-ipinterface ve 100vrf forwarding abcip address 192.168.92.1 255.255.255.0ip helper-address 1 192.168.92.1also globally i have enabledip dhcp-server enableip dhcp-server relay-agent-echo enable
(146) (3) (0) (0)
Featured resources
Zero-Trust-Architecture-Meta-2-500x281
Network Security with Zero Trust

Traditional security models aren't enough to combat today's cyber threats. Learn how RUCKUS Networks empowers organizations to implement Zero Trust principles—for continuous verification, strict access controls, and enhanced network protection.

ruckus-education-channel-hero500
RUCKUS Education Videos

The RUCKUS Education channel focuses on explaining fundamental concepts and protocols in the Wired and Wireless networking arena. We also provide demonstrations of different tasks in relation to the RUCKUS brand of products.

Technical_Documentation 5760 x 3243
Technical documents

Check out our library of technical documents: release notes, configuration, best practice, deployment guides and more!