Join the RUCKUS Technical Family

Case (215679)

Hello Team,We hope this email finds you well.Could you kindly provide us with the Country of Origin for ICX7550-24F, including the specific address if available?If this request is not within your scope, we kindly ask you to forward it to the appropriate contact.Please feel free to reach out if you have any questions or require further clarification.We sincerely appreciate your support.Thanks in advance!Case (215679)

ICX 7150-C12P: bootloader command "update_primary" does not work due to FIPS

Hello,I received a used ICX 7150-C12P. I've been trying to use theupdate_primary command but it returnsFIPS:update_primary command is disabled in FIPS/CC modeeven after disabling FIPS.I've fully booted into FastIron, cleared the keys, disabled FIPS, wrote to memory, and reloaded (after rebooting, fips show says that everything is turned off). I still get the same message when trying to update_primary. Does anyone have any experience with FIPS? I would appreciate any guidance. Thanks.REPLICATION1) Here is everything that I have done in FastIron to disable FIPS:enableconfigure terminalfips zeroizecrypto key zeroize allno fips enablewrite memoryreload2) Here is everything I did in the bootloader after that:setenv ipaddr 192.168.0.34setenv netmask 255.255.255.0setenv serverip 192.168.0.24setenv image_name ICX7xxx/SPR08090mc.binsetenv uboot ICX7xxx/mnz10118.binsetenv fipsresetupdate_ubootsaveenvreset3) More bootloader commands after thereset:factory set-defaultsetenv fipsresetupdate_primaryAt this point,update_primary returnsFIPS:update_primary command is disabled in FIPS/CC mode.Here is the show version output if it is pertinent:ICX7150-C12 Switch>show version Copyright (c) Ruckus Networks, Inc. All rights reserved. UNIT 1: compiled on Oct 3 2023 at 04:49:31 labeled as SPS09010h_cd2 (29360128 bytes) from Primary SPS09010h_cd2.bin (UFI) SW: Version 09.0.10h_cd2T211 Compressed Primary Boot Code size = 786944, Version:10.1.26T225 (mnz10126) Compiled on Tue Nov 29 12:43:26 2022 HW: Stackable ICX7150-C12-POE ========================================================================== UNIT 1: SL 1: ICX7150-C12-2X10GR POE 12-port Management Module Serial #:XXXXXXXXXXX [REDACTED] Software Package: BASE_SOFT_PACKAGE Current License: 2X10GR P-ASIC 0: type B160, rev 11 Chip BCM56160_B0 ========================================================================== UNIT 1: SL 2: ICX7150-2X1GC 2-port 2G Module ========================================================================== UNIT 1: SL 3: ICX7150-2X10GF 2-port 20G Module ========================================================================== 1000 MHz ARM processor ARMv7 88 MHz bus 8 MB boot flash memory 2 GB code flash memory 1 GB DRAM STACKID 1 system uptime is 1 day(s) 41 minute(s) 44 second(s) The system started at 06:05:40 GMT+00 Tue Oct 03 2023 The system : started=cold start

ICX 7150 Left the stack

Good DayWe had a pentest conducted on our environment and a few vulnerabilities were found with our Ruckus switch stack. We attempted to flash the stack during our maintenance weekend but it kept timing out. We then issued a reload command to reboot the stack. After the stack came back up it flashed fine. Fast forward to Monday morning and the branch complained that wifi in section of the building was down. To make a long story short the switch left the stack. The switch was removed and shipped to me to look at as we have another branch where the same issue has occurred. The power light is green and the syst light is orange. When a console cable is plugged the prompt just says "OS>". We attempted a software recovery and flashed the switch with SPR09010kufi.bin which is what we used for all other SPR stacks using the instructions here . The only part I skipped was the setenv uboot and update_uboot as I dont have the boot.bin and I noted this:Copying U-Boot image (mnz10127.bin) to Primary flashsf erase 0x0 0xc0000sf write 0x720c0f34 0x0 0xc0000device 0 offset 0x0, size 0xc0000U-Boot update Done.After issuing the reset command, the switch reboots and just goes back to the OS prompt. Green Power Light, Orange System light. I am not sure what more to do. Firstly for some reason it boots from the secondary partition and at the end of the boot process it shows an error related to "Incompatible version of booted application (SPR09010k.bin) and packages (SPR09010e.bin) stored in UFI image" so I flashed to SPR09010eufi.binOS> rebootOS> Stopping File Manager daemon...Stopping health monitor daemon...dhclientv4 executable file is not present.dhcpdv4 executable file is not present.Stopping poe daemon...Stopping system statistics daemon...Cannot open network namespace "fi": No such file or directoryAfter flashing back to the e firmware the switch booted fine.Extract UFI FI version success, version = SPR09010e.binNew packages found, uninstalling old packages if any..Installing packages, this may take some timePackages has been installed successfully.[MEMBER]local-6@ICX7150-C12 Router>show flashStack unit 6:NAND Type: Micron NAND 2GiB (x 1)Compressed Pri Code size = 33554432, Version:09.0.10eT213 (SPR09010e.bin)Compressed Sec Code size = 33554432, Version:09.0.10eT213 (SPR09010e.bin)Compressed Pri Boot Code size = 786944, Version:10.1.25T225 (mnz10125)Compressed Sec Boot Code size = 786944, Version:10.1.25T225 (mnz10125)Code Flash Free Space = 714231808After rebooting the switch again, it booted from primary flash: Crashkernel Disableddevice 0 offset 0xbfe00, size 0x200Enter 'b' to stop at boot monitor: 0device 0 offset 0x0, size 0xc0000Uboot Checksum Verification: PASSbootdelay: ===Booting image from PrimaryProcessing packages from primary partitionExtract UFI FI version success, version = SPR09010k.binIncompatible version of booted application (SPR09010e.bin) and packages (SPR09010k.bin) stored in UFI imageError, cannot install packagesUninstalling old packages if any.Error in processing packagesPackage installation is incomplete, related functionalities may not be availableAny assistance would be appreciated.

R850如何改为瘦AP

R850现在是胖AP，接入网络后控制器无法识别到，请问如何改为瘦AP让控制器能自动连接控制。

Ruckus IoT API Tokens

Hello,I am trying to clarify the token usage for the REST API. I am using controller version 2.2.1The/v1/oauth/login endpoint returns a access_token and a refresh_token. The doc's say that the validity of the access_tokenis 1 week, and that the refresh_token should be used to generate a new access_token upon it's expiry.The/v1/oauth/refresh endpoint is said to return a refresh_token, though it looks like it returns anaccess_token. Valid for 60 days.If the refresh endpoint does indeed return a access_token, then that would follow the logic presented in the login documentation. But then, what about the refresh_token? After the 60 days, should you use Basic Auth again to retrieve tokens?

How to Configure Ruckus R750 as a Wireless Mesh (Repeater) on vSZ 6.1 Without Ethernet Backhaul

Hello everyone,At our organization, all our Ruckus APs are managed by Virtual SmartZone (vSZ) version 6.1.0.0.935. We want to deploy a Ruckus R750 outside the building, but we cannot run an Ethernet cable to that location. Instead, we want the R750 to act as a wireless repeater (mesh AP):It should get its uplink wirelessly from a nearby wired/root AP that’s already managed by vSZ.It should provide normal Wi-Fi access to clients.We’ve already got other APs managed by vSZ; this will be the first one to run on mesh.Could someone please provide a step-by-step guide for enabling and configuring mesh on vSZ 6.1,Thanks in advance!