Faça parte da RUCKUS Technical Family

ICX 7250 9.0.10 config parsing error at boot

We have a small number of remaining ICX 7250s which are running 8.0.95. They are mostly in environments that require a quiet switch (albeit not fanless) with more than 12 POE ports, and I don't really have budget to replace them.I upgraded one of our spares to 9.0.10j_cd7T213 to play around. There are the usual oddities I've also seen with version 10 (prompting for a username on "enable" seems like a behavior change specifically designed to enrage experienced network engineers...) but only one thing I really found concerning. By policy we disable all management except SSH and serial console on all network devices - it's non-negotiable.Booting our standard configuration on the 7250 with 9.0.10 yields this, just before the console first prompts for login:Config parsing complete: 0,43 percent time: 00:10 parsed: [ver 09.0.10j_cd7T213]Error - Config send failedError [1 ui_common_send: Not able to apply - itc error please try again] parsing line: [no web-management https]show run from a privileged exec does show the "no web-management https" statement, and it does not appear the switch is actually listening on port 443, but, more disturbingly, if I then interactively reconfigure the switch with "web-management https" and then "no web-management https" it throws the same "Config send failed" error and rejects all subsequent configuration statements.Is this the kind of thing to expect from 9.0.10? I haven't tried downgrading a switch from 9 or 10 to 8, but maybe this is the time...

the concept of "session" in "/Clients/Wireless/Clients List/Overview"

My Ruckus R560 is managed by Ruckus ONE. My mobile phone is connected to the R560's SSID. Some apps may generate traffic.I find that my mobile phone has three sessions in the "/Clients/Wireless/Clients List/Overview".I also find one completed session in the "/Clients/Wireless/Clients List/Report".Could you help me to confirm what the other two sessions are?

Zone director 1200

How do reset a zone director 1200

Purchased a new ICX7150-C12P from Amazon, unable to set up from MacOS BigSur 11.7.10

Purchased a new ICX7150-C12P from Amazon, unable to set up from MacOS BigSur 11.7.10

Temperature sensors (AIR OUTLET NEAR PSU) on Icx7250-48p,

Hello,Can someone just explain where is the position of this temperature sensor exactly.I understand the one that is call "MGMT THERMAL PLANE", but this is not clear for me about the air outlet.Is it wherechassis pierced with a small hole above the PSU ? because there is no fan at this place, so it's just natural convection outtake ?At summer time, my icx7250 switch frequently to the high cpu fan speed because the temperature is two high.The temperature low threshold seems quite low : 41°c to toggle two high speed, but only 34° to come back to low speed.Thanks, Laurent.

Title: Bootloader Stuck on ICX7150-C12P, Firmware Update Fails with CRC Mismatch Errors

I’m currently trying to recover a Ruckus ICX7150-C12P switch that is stuck in bootloader mode after a power outage. The switch’s system LED is solid amber and no access points connected have power.What I’m Seeing:When connected via serial console (USB-to-serial) at 9600 baud, I reach the bootloader prompt.The bootloader attempts to load the firmware file named SPR08090d.bin via TFTP.I have set up a TFTP server on macOS, serving files from /private/tftpboot.I placed the firmware files (SPR08090f.bin, SPS08090f.bin, SPR08095gufi.bin, SPS08095gufi.bin) in /private/tftpboot.I renamed SPR08090f.bin to SPR08090d.bin to match what the bootloader requests.What I’ve Tried:Verified TFTP server is running and transferring files successfully with zero packet loss.Ensured IP addresses and network settings are correct between switch and TFTP server.Attempted update commands from the bootloader:update_primary SPR08090d.binupdate_primary (default to the renamed file)Each time, the switch reports CRC mismatch errors or invalid firmware image headers.Tried multiple firmware versions from Ruckus website (08.0.90f, 08.0.95g), but none work without mismatch errors.Renaming files to match bootloader expected names doesn’t fix the problem.Asked Ruckus support to provide the original SPR08090d.bin firmware as it seems the bootloader requires this exact version.What I Need Help With:Confirming the exact firmware version and file required to recover this switch from bootloader mode.Instructions or tools to recover from this state without risking bricking the device.Any alternative recovery methods (e.g., USB flash recovery, serial recovery).Advice on upgrading bootloader or firmware in this stuck state.Thank you in advance for any guidance or assistance!