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

¿Qué es la familia técnica RUCKUS?

La familia técnica RUCKUS (RTF) es una comunidad dinámica de profesionales de redes y entusiastas de la tecnología que utilizan soluciones RUCKUS.

Más que otro grupo tecnológico, RTF se basa en las conexiones y la experiencia de sus miembros.
 

¿Por qué debería unirse a RTF?

Nos apasiona crear soluciones de red sencillas y potentes. Acompáñenos para compartir conocimientos, obtener acceso temprano a nuevas tecnologías y conectar con los mejores ingenieros. Como socio, disfrutará de seminarios web exclusivos, colaboración directa con expertos y acceso a una red global en más de 20 idiomas.

Únase a la familia técnica RUCKUS hoy mismo y forme parte de una comunidad basada en el conocimiento y las relaciones.

¿Por qué elegir la familia técnica RUCKUS?

RUCKUS-Web-Icons_Stay-Updated

Manténgase actualizado con la tecnología más reciente

RTF proporciona seminarios web y boletines periódicos con las últimas perspectivas del sector para mantenerle a la vanguardia.

RUCKUS-Web-Icons_RUCKUS-Expert

Asistencia fiable de expertos RUCKUS

Interactúe directamente con expertos RUCKUS para obtener soluciones rápidas y fiables a sus desafíos técnicos.

RUCKUS-Web-Icons_Curated-Content

Contenido técnico seleccionado y de alta calidad

Reciba solo el contenido más relevante y práctico a través de nuestros recursos seleccionados

RUCKUS-Web-Icons_Collab

Comunidad colaborativa

Conéctese con sus compañeros, comparta experiencias y colabore para resolver incluso los problemas técnicos más difíciles. 

Webinars

smart-campus-ebook-hero400b

Seminario web mensual

March – Managing Property Identities and Workflows with RUCKUS One 

April – Introducing RUCKUS ICX 8100 series switches

Manténgase a la vanguardia con nuestros seminarios web mensuales que abarcan las últimas tendencias, actualizaciones y mejores prácticas en tecnología de redes. Estas sesiones están diseñadas para el aprendizaje continuo y para mantener sus habilidades definidas, y son perfectas para todos los profesionales 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.

Regístrese ahora 

 

Seminario web de MDU y RTF de hotelería

IPTV y medios de transmisión; prácticas recomendadas de MDU

Conozca contenido especializado centrado en unidades multifamiliares (MDU) y el sector de la hotelería. Aprenda a diseñar e implementar soluciones RUCKUS personalizadas para satisfacer los desafíos únicos de estos entornos.

Inscribirse en este seminario web

hospitality-main-hero-400b

RTF-webinar-archive-hero_500x281

Archivo del seminario web

Consulte las grabaciones de los seminarios web en varios idiomas locales.

Ver el archivo del seminario web

Días de incorporación de 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? Regístrese para obtener más información.


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.


AD-117885-EN-RTF Onboarding banner for the site (500x281)


RTF-events-calendar

Eventos comunitarios

Manténgase conectado en persona y en línea. Encuentre eventos en su sector y conéctese con profesionales como usted. 

Ver próximos eventos

 

 

 

Manténgase informado con el boletín de la familia técnica RUCKUS

 

Suscríbase a nuestro boletín para recibir las últimas noticias de RUCKUS, información técnica y actualizaciones. Tanto si es un profesional experimentado como si acaba de empezar, nuestro boletín le ofrece contenido valioso directamente en su bandeja de entrada

 

Read past RUCKUS Technical Family Newsletters

 

Foros

Comente sus proyectos locales y haga preguntas técnicas con nuestro canal de foros de RTF dedicados. Nuestro equipo global de ingenieros de sistemas participa activamente en estos debates, al ofrecer ayuda y asesoramiento. Para ver la lista de todos los temas del foro, visite community.ruckuswireless.com.

Comunidad de 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?
(35) (0) (0) (0)
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
(170) (4) (0) (0)
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
(47) (0) (0) (0)
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
(136) (3) (0) (0)
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/N‪141402003114‬MAC:6CAAB3314D00
(64) (0) (0) (0)
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?Gracias
(73) (0) (0) (0)
Recursos destacados
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
Videos educativos RUCKUS

El canal de educación RUCKUS se centra en explicar conceptos y protocolos fundamentales en el ámbito de las redes cableadas e inalámbricas. También proporcionamos demostraciones de diferentes tareas en relación con la marca de productos RUCKUS.

Technical_Documentation 5760 x 3243
Documentos técnicos

Consulte nuestra biblioteca de documentos técnicos: notas de la versión, configuración, mejores prácticas, guías de implementación y mucho más.