Bienvenue chez RUCKUS Networks, qui fait partie du portefeuille mondial de solutions réseau de CommScope. En savoir plus.
Qu’est-ce que la famille technique RUCKUS ?
La famille technique RUCKUS (RTF) est une communauté dynamique de professionnels du réseau et de passionnés de technologie qui utilisent des solutions RUCKUS.
Plus qu’un simple groupe technologique, RTF s’appuie sur les relations et l’expertise de ses membres.
Pourquoi rejoindre la RTF ?
Nous sommes passionnés par la création de solutions réseau simples et puissantes. Rejoignez-nous pour partager vos connaissances, accéder rapidement aux nouvelles technologies et entrer en contact avec les meilleurs ingénieurs. En tant que partenaire, vous profiterez de webinaires exclusifs, d’une collaboration directe avec des experts et d’un accès à un réseau mondial dans plus de 20 langues.
Rejoignez la famille technique RUCKUS dès aujourd’hui et faites partie d’une communauté fondée sur les connaissances et les relations.
Pourquoi choisir la famille technique RUCKUS ?
Restez informé des dernières technologies
RTF propose régulièrement des webinaires et des bulletins d’informations avec toutes les dernières informations du secteur pour vous permettre de garder une longueur d’avance.
Assistance fiable d’experts RUCKUS
Contactez directement des experts RUCKUS pour trouver des solutions rapides et fiables à vos défis techniques.
Contenu technique de grande qualité et organisé
Recevez uniquement le contenu le plus pertinent et le plus exploitable grâce à la sélection de nos ressources
Communauté collaborative
Connectez-vous avec vos pairs, partagez vos expériences et collaborez pour résoudre les problèmes techniques les plus difficiles.
Webinaires
Webinaire mensuel
March – Managing Property Identities and Workflows with RUCKUS One
April – Introducing RUCKUS ICX 8100 series switches
Gardez une longueur d’avance grâce à nos webinaires mensuels qui couvrent les dernières tendances, mises à jour et meilleures pratiques en matière de technologie de réseau. Conçues pour un apprentissage continu et pour garder vos compétences à jour, ces sessions sont parfaites pour tous les professionnels RUCKUS. 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.
Webinaire RTF sur l’hôtellerie et les MDU
IPTV et médias en streaming ; meilleures pratiques MDU
Plongez dans un contenu spécialisé et axé sur les unités pour logements multiples (MDU) et le secteur de l’hôtellerie. Découvrez comment concevoir et déployer des solutions RUCKUS personnalisées pour répondre aux défis uniques de ces environnements.
Archive de webinaires
Consultez les enregistrements de webinaires plus anciens disponibles dans une variété de langues locales.
Jours d’intégration RTF
Are you a new RUCKUS channel partner or a new member of an existing Channel Partner? If that’s you, then you may have questions, like Who is RUCKUS? and What sets us apart? Inscrivez-vous pour en savoir plus !
If you're already a partner, log in to register for the webinar.
Not a partner yet? Learn more about the benefits of the RUCKUS BIG DOGS Partner Program and how you can apply to join our pack and register for the webinar.
Événements communautaires
Restez connecté en personne et en ligne. Trouvez des événements dans votre secteur et faites connaissance de professionnels comme vous.
Afficher les prochains événements
Restez informé grâce au bulletin d’informations de la famille technique RUCKUS
Abonnez-vous à notre bulletin d’informations pour recevoir les dernières actualités RUCKUS, des informations techniques et des mises à jour. Que vous soyez un professionnel chevronné ou que vous débutiez tout juste, notre bulletin d’informations vous livre un contenu précieux directement dans votre boîte de réception
Forums
Discutez de vos projets locaux et posez des questions techniques en utilisant notre canal dédié aux forums RTF. Notre équipe mondiale d’ingénieurs système participe activement à ces discussions, en offrant de l’aide et des conseils. Pour obtenir la liste de tous les sujets du forum, rendez-vous sur community.ruckuswireless.com.
Communauté RUCKUS
Hello,Does Ruckus 1 not support the SPR code for a 7150-C12P?I noticed out of the "cloud ready" box, both partitions areSPS08095k.binOnboarding the switch, I selected "Router" code as that's my standard.However, Switch is sitting in "Firmware Updating" in the portal for about an hour now.The switch havingSPS08095k.bin in both partitions and it sitting at this for an hour makes me think this is an undocumented requirement?
Good Morning Community,i have a problem with dropping pakets in the UC Egress queues.Traffic comes in with 25GB and goes out with 10GB.I think that could be the reason for queuse overun (traffic comes only burst (iscsi)) not fully load.Is there any recommended tununig option to increase the buffer for that queues or is there a other solution available?Thanks for helping
Dear team,We have an issue with my AP,s in the controller they are offline, we have them in Miami and controller is located in MxThe connectivity is OK, they are reachable, we have done some tests link reboot, factory reset but the status is the same.The certificate is ok:rkscli: get rpki-cert issuerIssuer: RuckusPKI-DeviceSubCA-2OKrkscli:We have configured the IP of the controller sometimes:rkscli: get scg------ SCG Information ------SCG Service is enabled.AP is managed by SCG.State: CONN_GET_ADDR_STATEServer List: (OMITTED)The status is:CONN_GET_ADDR_STATEin the controller page is: new configuration.I have AP R750 has the version: 5.2.2.0.2122 (we have another APs than have the same version and they works well.My controller has:Controller versión: 5.2.2.0.317Cnotrol plane software versión: 5.2.2.0.126AP firmware versión: 5.2.2.0.301The logs in the ap are the following:Mar 20 17:24:39 RuckusAP local0.info remoteclid[8742]: Retrying connect to SCGMar 20 17:24:40 RuckusAP user.err MsgDist[1124]: MD try connection towards SCG-MDMar 20 17:24:40 RuckusAP user.err MsgDist[1124]: RCSL_Connect to 127.0.0.1 failedMar 20 17:24:40 RuckusAP daemon.info cubic[1448]: util_cmd_proc:1569 Execute CMD type: [1][GEMar 20 17:24:40 RuckusAP daemon.warn cubic[1448]: apcfg_general_get_base_info:513 ret:[6]/[baMar 20 17:24:40 RuckusAP daemon.info cubic[1448]: apcfg_general_get_sz_list:319 Server list[1Mar 20 17:24:40 RuckusAP daemon.warn cubic[1448]: apcfg_general_get_base_info:556 ret:[34]/[fMar 20 17:24:40 RuckusAP daemon.debug cubic[1448]: apcfg_general_get_radio_info:153 backgrounMar 20 17:24:40 RuckusAP daemon.debug cubic[1448]: apcfg_general_get_radio_info:153 backgrounMar 20 17:24:40 RuckusAP daemon.info cubic[1448]: cub_conn_get_addr_state_action:597 It's RegMar 20 17:24:40 RuckusAP daemon.debug cubic[1448]: cub_conn_get_addr_state_action:601 CurrentMar 20 17:24:40 RuckusAP daemon.info cubic[1448]: cub_state_action:2298 Start [IMG_REQ_STATE]Mar 20 17:24:40 RuckusAP daemon.info cubic[1448]: cub_state_action:2302 [CONN_GET_ADDR_STATE]Mar 20 17:24:40 RuckusAP daemon.info cubic[1448]: json_cmd_proc:558 Data type : [3][GENERATE_Mar 20 17:24:40 RuckusAP daemon.debug cubic[1448]: apcfg_get_config_id:577 File : [/writable/Mar 20 17:24:40 RuckusAP daemon.debug cubic[1448]: curl_https_request:1332 curl_https_request", "timeStamp": "20250320T172440", "seqNumber": 72, "zoneUUID": "0000", "configUUID": "", "purpose": "FW_CONF" }].Mar 20 17:24:40 RuckusAP daemon.info cubic[1448]: util_cmd_proc:1569 Execute CMD type: [5][GEMar 20 17:24:40 RuckusAP daemon.debug cubic[1448]: wrap_getaddrinfo:1188 getaddrinfo with addMar 20 17:24:40 RuckusAP daemon.debug cubic[1448]: resolve_addrinfo:1237 wrap_getaddrinfo witMar2017:24:40RuckusAPdaemon.infocubic[1448]:do_curl:1069SendHTTPrequesttoURL:[httpMar 20 17:24:40 RuckusAP daemon.err cubic[1448]: do_curl:1131 curl_easy_perform failed:[7][CoMar 20 17:24:40 RuckusAP daemon.debug cubic[1448]: cub_sm_check_retry_timeout:183 Lost secondMar 20 17:24:40 RuckusAP daemon.info cubic[1448]: cub_state_action:2298 Start [CONN_GET_ADDR_Mar 20 17:24:40 RuckusAP daemon.info cubic[1448]: cub_state_action:2302 [IMG_REQ_STATE] -> [CMar 20 17:24:42 RuckusAP user.err MsgDist[1124]: MD try connection towards SCG-MDMar 20 17:24:42 RuckusAP user.err MsgDist[1124]: RCSL_Connect to 127.0.0.1 failedMar 20 17:24:42 RuckusAP local1.info sessionMgr[1131]: build_and_send_scg_init_req:207 EnterMar 20 17:24:42 RuckusAP user.err MsgDist[1124]: Failed to route the messageMar 20 17:24:42 RuckusAP user.err MsgDist[1124]: RCSL_MSG_HDR : [Total Len = 57][MsgType=RCS90000000048, dstMac=0x0, srcMac=0x0, topic=0x0]Mar 20 17:24:42 RuckusAP user.err MsgDist[1124]: Route_Msg FailedMar 20 17:24:42 RuckusAP local1.err sessionMgr[1131]: sm_init_notify_cb:193 Error: MD failedMar 20 17:24:43 RuckusAP daemon.err gapd: Fail to get pool statsMar 20 17:24:43 RuckusAP daemon.info gapd: selecting.....Mar 20 17:24:44 RuckusAP user.err MsgDist[1124]: MD try connection towards SCG-MDMar 20 17:24:44 RuckusAP user.err MsgDist[1124]: RCSL_Connect to 127.0.0.1 failedMar 20 17:24:45 RuckusAP daemon.info cubic[1448]: util_cmd_proc:1569 Execute CMD type: [1][GEMar 20 17:24:45 RuckusAP daemon.warn cubic[1448]: apcfg_general_get_base_info:513 ret:[6]/[baMar 20 17:24:45 RuckusAP daemon.info cubic[1448]: apcfg_general_get_sz_list:319 Server list[1Mar 20 17:24:45 RuckusAP daemon.warn cubic[1448]: apcfg_general_get_base_info:556 ret:[34]/[fMar 20 17:24:45 RuckusAP daemon.debug cubic[1448]: apcfg_general_get_radio_info:153 backgrounMar 20 17:24:45 RuckusAP daemon.debug cubic[1448]: apcfg_general_get_radio_info:153 backgrounMar 20 17:24:45 RuckusAP daemon.info cubic[1448]: cub_conn_get_addr_state_action:597 It's RegMar 20 17:24:45 RuckusAP daemon.debug cubic[1448]: cub_conn_get_addr_state_action:601 CurrentMar 20 17:24:45 RuckusAP daemon.info cubic[1448]: cub_state_action:2298 Start [IMG_REQ_STATE]Mar 20 17:24:45 RuckusAP daemon.info cubic[1448]: cub_state_action:2302 [CONN_GET_ADDR_STATE]Mar 20 17:24:45 RuckusAP daemon.info cubic[1448]: json_cmd_proc:558 Data type : [3][GENERATE_Mar 20 17:24:45 RuckusAP daemon.debug cubic[1448]: apcfg_get_config_id:577 File : [/writable/Mar 20 17:24:45 RuckusAP daemon.debug cubic[1448]: curl_https_request:1332 curl_https_request", "timeStamp": "20250320T172445", "seqNumber": 73, "zoneUUID": "0000", "configUUID": "", "purpose": "FW_CONF" }].Mar 20 17:24:45 RuckusAP daemon.info cubic[1448]: util_cmd_proc:1569 Execute CMD type: [5][GEMar 20 17:24:45 RuckusAP daemon.debug cubic[1448]: wrap_getaddrinfo:1188 getaddrinfo with addMar 20 17:24:45 RuckusAP daemon.debug cubic[1448]: resolve_addrinfo:1237 wrap_getaddrinfo witMar2017:24:45RuckusAPdaemon.infocubic[1448]:do_curl:1069SendHTTPrequesttoURL:[httpMar 20 17:24:45 RuckusAP daemon.err cubic[1448]: do_curl:1131 curl_easy_perform failed:[7][CoMar 20 17:24:45 RuckusAP daemon.debug cubic[1448]: cub_sm_check_retry_timeout:183 Lost secondMar 20 17:24:45 RuckusAP daemon.info cubic[1448]: cub_state_action:2298 Start [CONN_GET_ADDR_Mar 20 17:24:45 RuckusAP daemon.info cubic[1448]: cub_state_action:2302 [IMG_REQ_STATE] -> [CMar 20 17:24:46 RuckusAP user.err MsgDist[1124]: MD try connection towards SCG-MDMar 20 17:24:46 RuckusAP user.err MsgDist[1124]: RCSL_Connect to 127.0.0.1 failedMar 20 17:24:48 RuckusAP user.err MsgDist[1124]: MD try connection towards SCG-MDMar 20 17:24:48 RuckusAP user.err MsgDist[1124]: RCSL_Connect to 127.0.0.1 failedMar 20 17:24:49 RuckusAP local0.err remoteclid[8742]: connect failed, reason: Connection refuMar 20 17:24:49 RuckusAP local0.info remoteclid[8742]: fail to connect to SCG...Mar 20 17:24:49 RuckusAP local0.info remoteclid[8742]: Retrying connect to SCGMar 20 17:24:50 RuckusAP user.err MsgDist[1124]: MD try connection towards SCG-MDMar 20 17:24:50 RuckusAP user.err MsgDist[1124]: RCSL_Connect to 127.0.0.1 failedMar 20 17:24:50 RuckusAP daemon.info cubic[1448]: util_cmd_proc:1569 Execute CMD type: [1][GEMar 20 17:24:50 RuckusAP daemon.warn cubic[1448]: apcfg_general_get_base_info:513 ret:[6]/[baMar 20 17:24:50 RuckusAP daemon.info cubic[1448]: apcfg_general_get_sz_list:319 Server list[1Mar 20 17:24:50 RuckusAP daemon.warn cubic[1448]: apcfg_general_get_base_info:556 ret:[34]/[fMar 20 17:24:50 RuckusAP daemon.debug cubic[1448]: apcfg_general_get_radio_info:153 backgrounMar 20 17:24:50 RuckusAP daemon.debug cubic[1448]: apcfg_general_get_radio_info:153 backgrounMar 20 17:24:50 RuckusAP daemon.info cubic[1448]: cub_conn_get_addr_state_action:597 It's RegMar 20 17:24:50 RuckusAP daemon.debug cubic[1448]: cub_conn_get_addr_state_action:601 CurrentMar 20 17:24:50 RuckusAP daemon.info cubic[1448]: cub_state_action:2298 Start [IMG_REQ_STATE]Mar 20 17:24:50 RuckusAP daemon.info cubic[1448]: cub_state_action:2302 [CONN_GET_ADDR_STATE]Mar 20 17:24:50 RuckusAP daemon.info cubic[1448]: json_cmd_proc:558 Data type : [3][GENERATE_Mar 20 17:24:50 RuckusAP daemon.debug cubic[1448]: apcfg_get_config_id:577 File : [/writable/Mar 20 17:24:50 RuckusAP daemon.debug cubic[1448]: curl_https_request:1332 curl_https_request", "timeStamp": "20250320T172450", "seqNumber": 74, "zoneUUID": "0000", "configUUID": "", "purpose": "FW_CONF" }].Mar 20 17:24:50 RuckusAP daemon.info cubic[1448]: util_cmd_proc:1569 Execute CMD type: [5][GEMar 20 17:24:50 RuckusAP daemon.debug cubic[1448]: wrap_getaddrinfo:1188 getaddrinfo with addMar 20 17:24:50 RuckusAP daemon.debug cubic[1448]: resolve_addrinfo:1237 wrap_getaddrinfo witMar2017:24:50RuckusAPdaemon.infocubic[1448]:do_curl:1069SendHTTPrequesttoURL:[httpMar 20 17:24:50 RuckusAP daemon.err cubic[1448]: do_curl:1131 curl_easy_perform failed:[7][CoMar 20 17:24:50 RuckusAP daemon.debug cubic[1448]: cub_sm_check_retry_timeout:183 Lost secondMar 20 17:24:50 RuckusAP daemon.info cubic[1448]: cub_state_action:2298 Start [CONN_GET_ADDR_Mar 20 17:24:50 RuckusAP daemon.info cubic[1448]: cub_state_action:2302 [IMG_REQ_STATE] -> [CMar 20 17:24:52 RuckusAP user.err MsgDist[1124]: MD try connection towards SCG-MDMar 20 17:24:52 RuckusAP user.err MsgDist[1124]: RCSL_Connect to 127.0.0.1 failedMar 20 17:24:52 RuckusAP local1.info sessionMgr[1131]: build_and_send_scg_init_req:207 EnterMar 20 17:24:52 RuckusAP user.err MsgDist[1124]: Failed to route the messageMar 20 17:24:52 RuckusAP user.err MsgDist[1124]: RCSL_MSG_HDR : [Total Len = 57][MsgType=RCS90000000049, dstMac=0x0, srcMac=0x0, topic=0x0]Mar 20 17:24:52 RuckusAP user.err MsgDist[1124]: Route_Msg FailedMar 20 17:24:52 RuckusAP local1.err sessionMgr[1131]: sm_init_notify_cb:193 Error: MD failedMar 20 17:24:53 RuckusAP daemon.err gapd: Fail to get pool statsMar 20 17:24:53 RuckusAP daemon.info gapd: selecting.....Mar 20 17:24:54 RuckusAP user.err MsgDist[1124]: MD try connection towards SCG-MDMar 20 17:24:54 RuckusAP user.err MsgDist[1124]: RCSL_Connect to 127.0.0.1 failedOKRegards
I am planning to enable simple RSTP on our 7550 switch which is also connected by trunk to 3rd party switch already running RSTP.I see the way to enable it is to run command "spanning-tree single 802-1w" however I see on the list after tabbing single there is also RSTP on the bottom of options.So what would be the difference of running "spanning-tree single 802-1w" vs "spanning-tree single RSTP"?Thanks
Hi,One of the my R300 got associated with a controller and now is in controller mode. I need to set it back to standalone mode. how do i do that ??I want firmware standalone for device R300 S/N141402003114MAC:6CAAB3314D00
Hi,I'm running into an issue with client devices which are roaming & disconnecting erratically in the interval of a single minute. On the user's end they see their streaming being interrupted. This happens throughout the day and night so it doesn't pinpoint down to a specific time.We run vSZ-E controller - Version7.0.0.0.726AP - H510 - Firmware6.1.2.0.850AP - H550 -6.1.2.0.850We have 2 campus, old and new. The old campus runs on mostly H510 and the new campus have all H550. The issue tends to be reported mostly from the new campus, and I have seen the events logs on a user's device roaming.What's different from the old and new campus is also the deployment of the APs. The old campus has 1 AP deployed in a block of 4 rooms. While the new campus has 2 APs in a block of 4 rooms.After encountering the issue I've made the below changes to the APs in the new block but the issue still persists:- Reduce Tx power to -3dB(1/2) on both 2.4Ghz and 5Ghz- Changed inactivity timer from 120 to 2400- Changed the BSS Min Rate on the WLAN to 12Mbps- RSS based rejection threshold is at -77dBmAre there any other suggestions? Should I look into decreasing the Tx power even more?Merci
Ressources à la une
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.
Vidéos de formation RUCKUS
La chaîne de formation RUCKUS se concentre sur l’explication des concepts et protocoles fondamentaux dans le domaine des réseaux câblés et wireless. Nous proposons également des démonstrations de différentes tâches liées à la marque des produits RUCKUS.
Documents techniques
Consultez notre bibliothèque de documents techniques : notes de version, configuration, meilleures pratiques, guides de déploiement, et plus encore !