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

January – 2025 Networking Technology Trends 

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


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

I have an ICX 7650-48F unit that is constantly rebooting.I have attempted a soft reset which resulted in an indefinite initializing state (sys LED blinking green).I have also attempted recovery procedure which resulted in no success.Below I have pasted the boot monitoring list as it shows a failure in HW init. Is this unit in need of an RMA? or was there a step I missed in attempting to recover this unit?61580116 bytes read in 505 ms (116,3 MiB/s) ## Loading kernel from FIT Image at 90000200 ... Using 'conf@1' configuration Trying 'kernel@1' kernel subimage Description: Linux for ICX7650/ICX7850 Created: 2020-03-16 3:23:46 UTC Type: Kernel Image Compression: lzma compressed Data Start: 0x900002d8 Data Size: 3459243 Bytes = 3,3 MiB Architecture: AArch64 OS: Linux Load Address: 0x80080000 Entry Point: 0x80080000 Hash algo: crc32 Hash value: 1a473a0f Verifying Hash Integrity ... crc32+ OK ## Loading ramdisk from FIT Image at 90000200 ... Using 'conf@1' configuration Trying 'ramdisk@1' ramdisk subimage Description: Ramdisk -rootfs Created: 2020-03-16 3:23:46 UTC Type: RAMDisk Image Compression: lzma compressed Data Start: 0x90359b34 Data Size: 58045929 Bytes = 55,4 MiB Architecture: AArch64 OS: Linux Load Address: 0x00000000 Entry Point: 0x00000000 Hash algo: crc32 Hash value: f76d6abf Verifying Hash Integrity ... crc32+ OK ## Loading fdt from FIT Image at 90000200 ... Using 'conf@1' configuration Trying 'fdt@1' fdt subimage Description: ICX7650.dtb Created: 2020-03-16 3:23:46 UTC Type: Flat Device Tree Compression: uncompressed Data Start: 0x9034cc5c Data Size: 27517 Bytes = 26,9 KiB Architecture: AArch64 Hash algo: crc32 Hash value: fd8efcc8 Verifying Hash Integrity ... crc32+ OK Loading fdt from 0x9034cc5c to 0x81200000 Booting using the fdt blob at 0x81200000 Uncompressing Kernel Image ... OK reserving fdt memory region: addr=81000000 size=200000 reserving fdt memory region: addr=e0000000 size=1000000 Loading Ramdisk to fb38c000, end feae75e9 ... OK Using Device Tree in place at 0000000081200000, end 0000000081209b7c Starting kernel ... ssp-pl022 66180000.ssp: probe: no chip select defined ssp-pl022 66190000.ssp: probe: no chip select defined phy-bcm-ns2-sata 67004000.sata_phy: Will limit CDR integral to +-149 (about 4544ppm) iproc-pcie 20020000.pcie: HOT-PLUG on bus:(null):1:313 iproc-pcie 50020000.pcie: HOT-PLUG on bus:(null):1:337 ahci 663f2000.ahci: can't get clock iproc_nand 66460000.nand: timeout waiting for command 255 (9) iproc_nand 66460000.nand: irq status 00000000, intfc status 00000000 iproc_nand 66460000.nand: timeout waiting for command 144 (7) iproc_nand 66460000.nand: irq status 00000000, intfc status 00000000 iproc_nand 66460000.nand: timeout waiting for command 144 (7) iproc_nand 66460000.nand: irq status 00000000, intfc status 00000000 iproc_nand 66460000.nand: timeout waiting for command 144 (7) iproc_nand 66460000.nand: irq status 00000000, intfc status 00000000 hub 1-0:1,0: config failed, hub doesn't have any ports! (err -19) hub 3-0:1,0: config failed, hub doesn't have any ports! (err -19) /hs_noc/usb@66480000: arguments longer than property /hs_noc/usb@66480000: arguments longer than property /hs_noc/usb@664a0000: arguments longer than property /hs_noc/usb@664a0000: arguments longer than property /hs_noc/usb@0x664c0000: arguments longer than property /hs_noc/usb@0x664c0000: arguments longer than property /hs_noc/usb@66480800: arguments longer than property hub 5-0:1,0: over-current condition on port 1 /hs_noc/usb@664a0800: arguments longer than property /hs_noc/usb@0x664c0800: arguments longer than property iproc-udc 664e0000.usbd_udc_dwc: couldn't get extcon device sdhci-iproc 66420000.sdhci: vqmmc not available, disable HS200 cap. sdhci-iproc 66430000.sdhci: invalid resource sdhci-iproc 66430000.sdhci: vqmmc not available, disable HS200 cap. hub 8-0:1,0: over-current condition sd 2:0:0:0: [sdb] No Caching mode page found sd 2:0:0:0: [sdb] Assuming drive cache: write through sd 2:0:0:0: [sdb] No Caching mode page found sd 2:0:0:0: [sdb] Assuming drive cache: write through sd 2:0:0:0: [sdb] No Caching mode page found sd 2:0:0:0: [sdb] Assuming drive cache: write through iproc-udc 664e0000.usbd_udc_dwc: couldn't get extcon device of_dma_request_slave_channel: dma-names property of node '/apb/serial@66130000' missing or empty INIT: version 2,88 booting INIT: Entering runlevel: 3 Starting mdev... Starting irqbalance: OK Starting SP805 watchdog... System time was Thu Jan 1 00:32:16 UTC 1970. Setting the System Clock using the Hardware Clock as reference... System Clock set. System local time is now Thu Jan 1 00:32:16 UTC 1970. Initializing random number generator... done. Starting system message bus: done Starting network: OK Starting HPA's tftpd: done Starting fw_downloader: OK fw_downloader started Mounting file system... ### FS Management... ### Creating /dev/sda devices Done Partition Present BitMap: 7 Running FS Check, followed by Partition Mount ... e2fsck 1.43.4 (31-Jan-2017) /dev/sda1: clean, 13/131072 files, 147258/523264 blocks fsck for boot partition complete, result (Code: 0): No FS Error e2fsck 1.43.4 (31-Jan-2017) /dev/sda2: recovering journal /dev/sda2: clean, 18/32768 files, 6263/131072 blocks fsck for opt partition complete, result (Code: 0): No FS Error e2fsck 1.43.4 (31-Jan-2017) /dev/sda3: clean, 108/196608 files, 66498/786176 blocks fsck for config partition complete, result (Code: 0): No FS Error Partition Mount xBitMap: 0 Partitions successfully mounted ### FS Management Complete ### Checking Boot partition... Done 1 external USB Drive(s)/Partition(s) Mounted Processing packages from primary partition Incompatible version of booted application and packages stored iSoftlockup time is given as 15 x 2 secs gzip fixup getting applied/ PCIe Fixup is getting applied. setpci: Warning: No devices selected for "4.w=0x4001". iproc-udc 664e0000.usbd_udc_dwc: couldn't get extcon device Stopping Fw_downloader:OK Starting fw_downloader: OK fw_downloader started SKU TYPE 48F BCM82756 is programmed to download the firmware over MDIO already.!! Starting TPM Infra addgroup: group 'tss' in use Group tss and User tss created kernel.hostname = localhost hostname set to localhost Starting TCSD Daemon TCSD Up and Running Creating TUN device ethaddr: c0:c5:20:83:b4:d9 applying netdev fixups. net.core.netdev_budget = 50 net.core.netdev_max_backlog = 2000 Enabling time stamp. Installing crashkernel infra primary image found. copying dts and os image from it. /tmp/rootfs Done!! Starting the FastIron. softlockup enabled on bootup. INTR: Interrupt thread created ... I2C_CLIENT: PSU Write failed @offset 28 Softlockup Module Init PCI_CORE: rv 0 dev->mapped_address[0]= f6294000 , &p=0xcaed258 CLIENT_BINDER: No host found for client spi-mtd: host_name CLIENT_BINDER: No host found for client spi-mtd: host_name CLIENT_CORE: I2C device database init I2C_CORE: --> SG <-- no driver found for bus0 devtpm CPLD_CORE: Platform_ID 66, sku-name 48F Non-POE CPLD_CORE: HW Revision Type : 'PVT' CPLD_CORE: PCB REV : 'V1' WARNING: TSC frequency estimated Based on Monotonic Clock TSC frequency is ~25001KHz MEMORY: MEMORY Initialized PCI_CORE: Probing all PCI Devices... PCI_CORE: PCI device 0002:01:00,0 PCI_CORE: probe driver: 1657:20 es4651bfx_fpga PCI_CORE: Cannot create /dev/uio0 PCI_CORE: uio number 0 PCI_CORE: UIO RESOURCE allocation Successfull PCI_CORE: Physical 8000000 , Virtual 0xf6294000, size=200000 PCI_CORE: rv 0 dev->mapped_address[1]= f5094000 , &p=0xcaed25c PCI_CORE: Physical 8200000 , Virtual 0xf5094000, size=200000 ============================================================== Library ==> Load Address ============================================================== libc-2.24.so ==> 0xf6c94000 libgcc_s.so.1 ==> 0xf6d83000 libsilpi.so ==> 0xf6dad000 libplatform.so ==> 0xf6e2d000 libm-2.24.so ==> 0xf707b000 libpthread-2.24.so ==> 0xf7111000 libdl-2.24.so ==> 0xf7135000 librt-2.24.so ==> 0xf7148000 ld-linux.so.3 ==> 0xf715e000 ============================================================== FIPS Disabled:PORT NOT DISABLED GENERIC: platform type 102 GENERIC: warm_mem 0xf5294000, size 86a, sil_get_warm_mem_pointer=0xf5294000, GENERIC: warm_mem 0xf5294000, size 86c, sil_get_warm_mem_pointer=0xf529486c, !!!!All CPLDS and FPGAs are up-to-date. No Update required !! DDR_ECC: DDR ECC Check is enabled. GENERIC: Signature: ca95 Base MAC: c0:c5:20:83:b4:9c GENERIC: ***************************************************************** ***************************************************************** Platform ID 102 [48F Non-POE] [fes_type= 130 ] HW Revision 'PVT' MAINBOARD FW: Installed Version : 04.0A CPLD0: Installed Version : 02,08 CPLD1: Installed Version : 03,01 GENERIC: ***************************************************************** ***************************************************************** Loaded Image TNR08092b from Pri Built on (UTC): Mon Mar 16 03:23:52 2020 GENERIC: Enabling Console Logging Applying factory defaults.. INFO: startup config data is not available, try to read from backup INFO: startup config data in the backup area is not available GENERIC: warm_mem 0xf529486c, size 39801c, sil_get_warm_mem_pointer=0xf529486c, GENERIC: warm_mem 0xf529486c, size 39801c, sil_get_warm_mem_pointer=0xf562c888, Hotplugger Daemon Initialized .. set_board_level: gi_board_type = 130DMA pool size: 134217728 PHY Reset De-asserted SOC unit 0 attached to PCI device BCM56568_B0 0:bcmi_xgs5_bfd_init: uKernel BFD application not available Reseting PHY 0x0... Retrying FW download on MIURA BCM82756 0x0 Reseting PHY 0x0... Failed to release semaphore miura (handle 0xe0d00540), count 1, itr 0, error 1 stack: 0008370c 00083808 f6db6d2c 02dc21d0 001682a0 041789d8 f3bfeb04 Downloading firmware using MDIO. Will write to EEPROM if present Reseting PHY 0x0... Failed to release semaphore miura (handle 0xe0d00540), count 1, itr 0, error 1 stack: 0008370c 00083808 f6db6d2c 02dc21d0 001682a0 041789d8 f3bfeb04 MDIO download or writing firmware to EEPROM failed for 0x0 Failed to initialize Module 1 BCM82756 ports Failed to initialize standalone PHYs. Aborting... *********************************************** FATAL ERROR: Failed in HW init hence rebooting *********************************************** 8,5: Halt and reboot Copying Hmon log files to flash.. Done Copying SZ log files to flash.. Done Copy RAMFS console log file to flash before we shutdown Copy RAMFS fitrace error log file to flash before we shutdown PCI-FPGA EP found, disabling FPGA interrupts Unmounting external USB Unmounting Boot partition Unmounting Opt partition Unmounting Config partition Unbinding Drivers.. unbind done. The system is going down NOW! [ 70,229069] SysRq : Resetting [ 70,286492] Requesting WARM Boot. [ 70,327317] send DDR self-refresh command to M0 NOTICE: IHOST: Broadcom BCM58712 B0 NOTICE: IHOST: Setting Core Frequency to 2000 NOTICE: Booting Trusted Firmware NOTICE: BL1: Built : 01:08:50, Oct 9 2019 NOTICE: BL1: Booting BL2 NOTICE: BL2: Built : 01:08:51, Oct 9 2019 NOTICE: IHOST: Broadcom BCM58712 B0 NOTICE: Starting DDR bring-up for part "mt40a1g8" at 2132MHz and datawidth of 72bits ... NOTICE: Warm Boot --> Skip DRAM Initialization WARNING: DRAM, ECC errors detected on initialization. NOTICE: DRAM tuning and initialization done! WARNING: Failed to access image 'bl32.bin' (-1) WARNING: Failed to load BL3-2 (-1) NOTICE: BL1: Booting BL3-1 NOTICE: BL3-1: Built : 01:08:51, Oct 9 2019 ERROR: Error initializing runtime service tspd_fast Ruckus Networks Bootloader: 10.1.17T235 (Oct 09 2019 - 01:08:48 -0700) DRAM: 4 GiB I2C: ready Booting from Primay Flash Check the firmware upgrade ... done. In: serial Out: serial Err: serial Enabling onboard SATA host set up port 0 set up port 1 ahci_host_init: SATA link 0 ok. AHCI 0001,0300 32 slots 2 ports 6 Gbps 0x3 impl SATA mode flags: 64bit ncq stag clo pmp fbss slum part scanning bus for devices... S/N: A46207170D8901807006 Firmware version: SBFM01.0 Product model number: SATA SSD Capablity: 31277232 sectors Device 0: (0:0) Vendor: SATA Prod.: SSD Rev: SBFM Type: Hard Disk Capacity: 15272,0 MiB = 14,9 GiB (31277232 x 512) Found 1 device(s). Net: e1000: c0:c5:20:83:b4:d9 1 e1000 interfaces found ................................ done e1000#0 Applying IDM Fixups... SF: 512 bytes @ 0x17fe00 Read: OK +++++++++++++++++++++++++++++++++ SKU Type : ICX7650-48F CPU CPLD Revision: 02,07 Boot Loader Flash: Primary FI Image to Boot : Primary +++++++++++++++++++++++++++++++++ Enter 'b' to stop at boot monitor: 0Thank you,Joe J
(7) (2) (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?
(4) (0) (0) (0)
We have multiple remote office locations where we are looking at installing ruckus APs and want to know what are the possibilities for integrating wireless user logon with sso usingOIDC/Oauth or SAML with an IAM/IdP we are already using. We are not using ldap, not using active directory, not using azure.We are not using the 'social media' logins and we saw that unleashed may support some OAuth with google, facebook, linkedin, Microsoft, none of which we are using. Does unleashed support or plan to offer connecting to otherOIDC/Oauth or SAML?Are there any other methods for connecting ruckus APs tootherOIDC/Oauth or SAML? The locations may have ruckus icx switches and we would prefer to use the embedded Unleashed as the locations will have a low AP count and do not require more sophisticated features. The remote office locations will have compute available to run vms or containers for any required additional ruckus or other applications to support a solution.
(16) (0) (0) (0)
Where can I getRuckus 902-1170-US00 Power Adapter in India?
(177) (1) (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
(89) (1) (0) (0)
I followed all of the steps for the first AP in the education video and cant see my AP in the staging area inside of virtual smartzone like in video, is there a setting inside of VSZ that I'm missing. also is there an easier way to deploy, detect and configure as I have 50+ to do and this seems not very efficient
(223) (7) (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.