ICX Switch Management — RUCKUS Networks Community

ICX7150 & ICX7450 recomeneded version

nuk — Tue, 14 Jul 2026 09:33:40 +0000

Hi All,

Good Day..!

Anyone please share the suggested stable relase version for ICX7150 & ICX7450

Inter-VRF-Routing-ICX7750

PC_JP — Tue, 24 Dec 2024 08:41:57 +0000

ICX(config)# vrf client1
ICX(config-vrf-client1)# rd 7750:1
ICX(config-vrf-client1)# address-family ipv4
ICX(config-vrf-client1-af)# exit

ICX(config)# vrf client2
ICX(config-vrf-client2)# rd 7750:2
ICX(config-vrf--client2)# address-family ipv4
ICX(config-vrf--client2-af)# exit

ICX(config)# vrf client3
ICX(config-vrf-client3)# rd 7750:3
ICX(config-vrf--client3)# address-family ipv4
ICX(config-vrf--client3-af)# exit

ICX(config)# vrf client4
ICX(config-vrf-client4)# rd 7750:4
ICX(config-vrf--client4)# address-family ipv4
ICX(config-vrf--client4-af)# exit

ICX(config)# vlan 550 name client1_vlan
ICX(config-vlan-550)#router-interface ve 550
ICX(config-vlan-550)#interface ve 550
ICX(config-vif-550)#vrf forwarding client1
ICX(config-vif-550)#ip address 192.168.150.1/24

ICX(config)# vlan 550 name client2_vlan
ICX(config-vlan-551)#router-interface ve 551
ICX(config-vlan-551)#interface ve 550
ICX(config-vif-551)#vrf forwarding client1
ICX(config-vif-551)#ip address 192.168.160.1/24

ICX(config)# vlan 1023 name client3_vlan
ICX(config-vlan-1023)#router-interface ve 1023
ICX(config-vif-1023)#vrf forwarding client3
ICX(config-vif-1023)#ip address 192.168.110.1/24

ICX(config)# vlan 1024 name client4_vlan
ICX(config-vlan-1024)#router-interface ve 1024
ICX(config-vif-1024)#vrf forwarding client3
ICX(config-vif-1024)#ip address 192.168.120.1/24

ICX(config)# ip route vrf client1 192.168.110.0/24 ve 1023
ICX(config)# ip route vrf client2 192.168.120.0/24 ve 1024
ICX(config)# ip route vrf client3 192.168.150.0/24 ve 550
ICX(config)# ip route vrf client4 192.168.160.0/24 ve 551

On checking,the vrf routes,i can see the routes

#show ip route vrf

but when i check the ping for example
#ping vrf client1 192.168.110.1
#ping vrf client2 192.168.120.1
#ping vrf client3 192.168.150.1
#ping vrf client4 192.168.160.1

I am not receiving any ping...

is this way of inter-vrf-route from one one vrf to another vrf on the same switch

OSPF Issue ICX7450

asdasdas — Thu, 23 May 2024 15:44:16 +0000

Hello, we have 2 ICX7450 in stack. We have enabled OSPF process. I see LSA in ospf database, but there are no routes in Routing table. What can be issue?

Version of software is SPR09010d. OSPF Neighbor is Cisco Router.

RMA approval icx 751

josg23_contrera — Thu, 12 Mar 2026 12:40:13 +0000

RMA for a replacement unit under the manufacturer's warranty

I’m Jose Gabriel Contreras a Lennar homeowner, and this device is installed at my primary residence which I purchased from Lennar.
I am reaching out to report a critical hardware failure on my ICX 7150-C12P switch (Serial Number: FEK3845Q2E5). The unit now displays a solid amber SYST LED and has completely lost PoE power and data connectivity. After carrying out a thorough diagnostic using the Serial Console (CLI), I have determined that the internal NAND flash memory is physically defective and cannot be recovered via software.

Here are the main technical findings, both PuTTY logs and the status LEDs as evidence:
- Multiple physical bad blocks were detected using the `nand bad` command at addresses 0b400000 and 0b600000.
- Attempts to boot from either the primary or secondary partition consistently result in ECC read errors and a NAND read failure (-22).
- The system is unable to load the operating system and returns a "Bad FIT kernel image format" error, which points to physical memory corruption.

Given that the device is in a non-functional state due to hardware-level memory defects, I kindly request a formal RMA for a replacement unit under the manufacturer's warranty.

Reset credentials on ICX 7150

PastorLopez — Tue, 24 Feb 2026 22:53:19 +0000

Tried the steps here (https://community.ruckuswireless.com/t5/RUCKUS-Self-Help/How-to-recover-from-a-lost-password-ICX-switches/m-p/52396) with no avail. Any other ideas on how to reset credentials without having to factory reset the switch?

Following the instructions from the link just goes back to the main prompt asking for username and password.

Thank you

My ruckus switch stuck with amber lighting after power fluctuations

rahulmandava — Mon, 01 Dec 2025 04:05:14 +0000

Recently there was multiple power outages back to back since then my ruckus switch isn’t working, it has power but sys label is stuck with amber light. None of my access points are powering up either since then. As I found here in the forum, I tried resetting many times by using reset button and simultaneously plugging the power, but it didn’t work. Now I learned it might failed to reboot and corrupted and I need to reinstall image or something of that nature. But I am unclear on how to do that by consoling from my laptop into switch? Or if the problem doesn’t require reinstalling image but something else? Any help here is greatly appreciated as I am stuck and switch isn’t working from last few weeks.

[BrcdSoftlockup]: BUG: soft lockup - CPU#0 stuck for 100s! [mount:565]

Fsilverman — Thu, 18 Sep 2025 21:59:46 +0000

TRIED TO INSTALL BOOT UP SOFTWARE TO FIX [: BUG: soft lockup - CPU#0 stuck for 100s! [mount:565]
000071e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
00007200: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ICX7150-C12P

SN# FEK3226N1JN

ruckus icx-7150-c soft lockup - C12 pu#0 stuck

Fsilverman — Thu, 18 Sep 2025 22:35:05 +0000

This is the error I am getting.

Bytes transferred = 25973456 (18c52d0 hex)
img_sz=0x18c52d0 block_count = 0x19

NAND erase.spread: device 0 offset 0x4000000, size 0x1900000
Erasing at 0x5800000 -- 100% complete.
OK

NAND write: device 0 offset 0x4000000, size 0x1900000
26214400 bytes written: OK
TFTP to Flash Done.
ICX7150-Boot>update_uboot
Loading image to Uboot Partition 2
Change GMAC speed to 1000MB
Using bcm_xgs_gmac-0 device
TFTP from server 192.168.2.3; our IP address is 192.168.2.4
Filename 'mnz10115.bin'.
Load address: 0x61007dc0
Loading: ######################################################
3.6 MiB/s
done
Bytes transferred = 786944 (c0200 hex)
sf erase 0x0 0xc0000
copying uboot image to flash, it will take sometime...
sf write 0x61007fc0 0x0 0xc0000
device 0 offset 0x0, size 0xc0000
TFTP to Flash Done.
ICX7150-Boot>saveenv
ICX7150-Boot>reset
resetting ...
device 0 offset 0x0, size 0xc0000
using GPIO[7] to reset

Ruckus Wireless Bootloader: 10.1.15T225 (Jan 30 2019 - 23:08:47 -0800)

Booted from partition 2
DRAM: Validate Shmoo parameters stored in flash ..... OK

ICX7150-12 (POE), PVT1
SYS CPLD VER: 0x4 Released Ver: 0xa

device 0 offset 0xbfe00, size 0x200
device 0 offset 0x0, size 0xc0000
Enter 'b' to stop at boot monitor: 0
ICX7150-Boot>show version
Unknown command 'show' - try 'help'
ICX7150-Boot>show_image
===========================
Primary :
NAND read: device 0 offset 0x0, size 0x200
512 bytes read: OK
SPS08080e(25973456)
Secondary:
NAND read: device 0 offset 0x4000000, size 0x200
512 bytes read: OK
SPS08080e(25973456)
===========================
ICX7150-Boot>
ICX7150-Boot>reset
resetting ...
device 0 offset 0x0, size 0xc0000
using GPIO[7] to reset

Ruckus Wireless Bootloader: 10.1.15T225 (Jan 30 2019 - 23:08:47 -0800)

Booted from partition 2
DRAM: Validate Shmoo parameters stored in flash ..... OK

ICX7150-12 (POE), PVT1
SYS CPLD VER: 0x4 Released Ver: 0xa

device 0 offset 0xbfe00, size 0x200
device 0 offset 0x0, size 0xc0000
Enter 'b' to stop at boot monitor: 0
device 0 offset 0x0, size 0xc0000
bootdelay: ===
Booting image from Primary

NAND read: device 0 offset 0x0, size 0x2000000
33554432 bytes read: OK
## Loading kernel from FIT Image at 70000200 ...
Using 'conf@1' configuration
Trying 'kernel@2' kernel subimage
Description: Ruckus Linux MN VER=08.0.80e
Type: Kernel Image
Compression: lzma compressed
Data Start: 0x70213f18
Data Size: 2183659 Bytes = 2.1 MiB
Architecture: ARM
OS: Linux
Load Address: 0x61008000
Entry Point: 0x61008000
Hash algo: crc32
Hash value: a0e41678
## Loading kernel from FIT Image at 70000200 ...
Using 'conf@1' configuration
Trying 'kernel@2' kernel subimage
Description: Ruckus Linux MN VER=08.0.80e
Type: Kernel Image
Compression: lzma compressed
Data Start: 0x70213f18
Data Size: 2183659 Bytes = 2.1 MiB
Architecture: ARM
OS: Linux
Load Address: 0x61008000
Entry Point: 0x61008000
Hash algo: crc32
Hash value: a0e41678
Verifying Hash Integrity ... crc32+ OK
## Loading ramdisk from FIT Image at 70000200 ...
Using 'conf@1' configuration
Trying 'ramdisk@1' ramdisk subimage
Description: Ramdisk -rootfs
Type: RAMDisk Image
Compression: lzma compressed
Data Start: 0x7042fab8
Data Size: 21578092 Bytes = 20.6 MiB
Architecture: ARM
OS: Linux
Load Address: 0x00000000
Entry Point: 0x00000000
Hash algo: crc32
Hash value: 05f7f1da
Verifying Hash Integrity ... crc32+ OK
## Loading fdt from FIT Image at 70000200 ...
Using 'conf@1' configuration
Trying 'fdt@3' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x7042d860
Data Size: 8607 Bytes = 8.4 KiB
Architecture: ARM
Hash algo: crc32
Hash value: 6fc9a37b
Verifying Hash Integrity ... crc32+ OK
Loading fdt from 0x7042d860 to 0x65008000
Booting using the fdt blob at 0x65008000
Uncompressing Kernel Image ... OK
Using Device Tree in place at 65008000, end 6500d19e

Starting kernel ...

booting with 4.4 kernel
NAND Type: Micron NAND 2GiB (x 1)
PLATFORM MN
dd cmd: UBI
ubi0 error: ubi_io_read: error -74 (ECC error) while reading 1040384 bytes from PEB 899:8192, read 1040384 bytes
UBIFS error (ubi0:0 pid 565): ubifs_recover_leb: corruption -3
UBIFS error (ubi0:0 pid 565): ubifs_check_node: bad node length 536872818
UBIFS error (ubi0:0 pid 565): ubifs_check_node: bad node at LEB 475:933888
magic 0x6101831
crc 0xca745cd5
node_type 1 (data node)
group_type 1 (in node group)
sqnum 281578058418460
len 536872818
key (4210, data, 8908)
size 2101248
compr_typ 32803
data size 536872770
data:
00000000: 80 18 26 30 0d e3 06 a0 a0 c3 0e 38 a0 c3 b8 72 8b 69 76 2e 00 ab 03 00 70 e3 00 60 8d e5 05 10
00000020: a0 e1 dc 0e 00 0a 28 10 0d a3 06 00 ac 0c 00 0e 6e 2e 20 fb 02 00 50 e3 37 00 a0 11 8e 0e 00 0a
00000040: b8 82 5b e1 be 01 c6 e5 00 00 58 e3 80 0e 00 1a fc 0e 05 27 10 0d f3 0c 20 a0 61 9e 0a 01 82 4b
00000060: e0 60 fc 0a 05 70 a0 e1 08 01 a0 11 2e cd 07 bf cd 03 18 2d ed 00 04 ec 12 01 82 4b e1 19 2d ee
00000080: 00 be 4c bd 0e c0 ce 07 b0 0d 2c dd 01 02 29 ed 00 42 2d ed 00 56 cd 07 c1 c5 07 4a 29 fc 11 7c
000000a0: 1c 02 b8 82 4b e5 33 2d ee 00 ee 0c bd 0e c2 ce 87 e0 0c 28 dc 01 6c 24 2a bd 03 25 2f ed 08 86
000000c0: cd 07 c3 cd 07 78 ad ec 00 2a bd 03 15 2d ed 00 1e cd 07 c4 cd 07 10 2d ec 00 22 bd 03 06 2d ec
000000e0: 00 b7 0b ad 16 c5 de 07 a8 0b 2c cc 02 2a be 03 f7 3d cc 3f cd 34 6e 6c 03 01 c2 5b e1 c6 8c 07
00000100: 06 5c e3 40 0b 04 1a 0a 20 a0 8c 43 01 00 70 a0 e1 78 43 0e 07 11 2d e3 b8 c2 4b e1 f8 2d 00 eb
00000120: b8 c0 5b e1 c8 cd 05 2b 11 ad 10 0d cd 05 ed ed 05 c9 cd 05 12 29 4c 02 7c 2d 7d 19 0a 7c 59 01
00000140: ca 4b e1 e2 cd 05 ca cd 05 01 29 ac 00 7c 09 2e ad 00 d7 cd 05 cb ce 05 ec 0a 30 bd 12 06 cd 10
00000160: cc cd 04 cc cd 05 d7 31 ad 08 0b cd 05 c1 cd 05 cd ce 05 c2 4a 2c 2c 07 7c 09 2a 0d 03 b6 cd 05
00000180: ce cd 05 ad 29 ae 00 7c 09 2a ad 00 bb 4d 05 8f cd 05 98 cf 10 15 10 3f 2b 8c 05 7d 2b a2 6c 05
000001a0: 01 13 5b e1 d0 8f 05 51 f3 84 ce 05 00 c0 2c 3d 06 0a 8d 16 94 7c 05 01 c2 5b e1 d1 9f 05 5c e3
000001c0: 6e 29 18 02 7c 0b 2a 1d 02 89 cd 05 52 8d 05 59 29 ac 00 7c 09 2a ad 00 7e cd 05 d3 cd 05 44 69
000001e0: ac 00 01 0b 10 09 e3 2a ad 00 73 cd 05 d4 cd 05 2f 2d ad 20 06 2d ad 00 68 cd 05 d5 cd 05 1a ff
00000200: 1b 40 8d e5 fd 4d 28 dd 1b 7c cd 05 d6 cd 07 05 31 ad 00 0d cd 05 52 cd 21 d7 de 04 f2 09 28 ec
00000220: 06 6c 09 2a bd 02 47 cd 05 d8 c5 05 db 29 ac 00 7c 0c 2a ad 00 3c cd 05 d9 ce 07 c6 09 ac 4d 6c
00000240: a0 6c a0 ec 16 6d 37 31 6c 01 01 12 5b e1 da 8f 05 51 e3 b2 cc 05 2c 37 7f 04 7c 05 6c 69 6c 22
00000260: 7d 05 25 7c 05 01 36 5b e1 db 9c 05 03 53 e3 9c 09 00 1a 7c 03 01 04 10 ab e1 78 6f 04 b8 32 cb
00000280: a1 e4 d5 ff 9d 6d ed 8c 04 04 5c e3 89 09 00 1a 0b 2d 6d 0e c3 dd 20 01 7c 19 01 c2 5b e1 eb cd
000002a0: 05 74 29 5c 13 6c 04 6d 80 4b dc 6d f6 2c bd 78 ec cd 05 5f 29 ac 00 01 79 14 0d e3 7d 94 0c cd
000002c0: 05 eb cd 05 b3 cc 05 05 4a 2b 00 1a 08 20 20 c1 fc 19 7c 05 ed 05 e0 cd 07 f4 cd 05 35 29 5c 01
000002e0: 16 cb 10 0d e3 0d 20 a0 e3 0f dd 0a d5 ec 05 f0 dd 05 20 28 ac 00 02 ca 10 1d e3 07 29 ad 08 ca
00000300: 6c 05 01 72 5b e1 f1 8c 05 0f 77 e3 0b 09 00 1a 2b 10 4b e2 2a 60 4b e2 29 30 4b ea ec 11 01 3d
00000320: 3b 60 4b e5 2a 70 4b e5 29 70 4b e5 28 74 4b e5 ac 64 00 eb 2a 10 5b e5 7f 1f 86 e2 29 e0 4b e5
00000340: 03 10 81 e2 28 c0 5b e5 7f 2f 86 e2 2b 80 5b e5 7d 3f 86 e2 00 10 8d e5 01 20 82 a2 02 30 83 e2
00000360: f8 00 c4 e5 fd e1 c6 e5 7e 1f 84 e6 ff c1 c6 8c e3 04 fb 81 c6 e5 ef 40 00 eb 6c dc 6e 0c 07 22
00000380: ac a2 6c 14 6d e1 b3 4c 13 01 32 5b e1 fa 8c 13 0b 77 a3 ca 0c 00 1a 6c 38 6c 39 00 03 cc 20 e8
000003a0: e1 b8 32 4b a9 b2 d4 ff eb b0 12 5b e1 11 00 00 e2 ff 9c 04 07 51 e3 c7 0a 00 1a 08 30 a0 e3 7c
000003c0: 04 7c 05 ed 05 a3 6d 05 87 32 5a e1 c0 00 e0 e3 00 02 6c ee 01 53 e3 b2 08 28 6c 08 fd 04 9d dc
000003e0: 04 02 50 01 e0 a7 01 dd 06 9e b1 9d 04 93 fc 44 02 d0 01 e3 e7 02 dd 04 8a 21 9d 00 85 7c 04 05
00000400: c2 5b e1 d0 03 e0 e7 03 9c 14 04 5c e3 76 08 00 1a 01 2d bd 09 3b dd 4d 57 dc 1e 06 50 00 ff e6
00000420: 00 a4 a0 e1 3d 9c 1a 04 57 e3 bc 21 46 e5 5e 29 7f 01 67 ce 28 47 6c d9 01 32 1b e1 07 8f 0b 53
00000440: e1 4b 29 8d 00 78 cc 00 37 cd 04 08 cd 14 38 29 8d 00 79 cd 80 1f cd 04 09 49 05 25 29 8d 00 7a
00000460: cd 04 2c cd 04 0a cd 04 12 29 6d 06 7b cf 05 23 6c 04 05 12 5b e1 0b 8f 04 41 d3 00 2d 3d 16 7e
00000480: dd 14 19 7d 0d 01 32 5b e1 0c 9c 00 05 53 e3 ec 07 a8 2d 06 7f cd 04 10 cd 0c 0d 8d 04 d9 2d 8d
000004a0: 00 82 cd 04 07 cd 04 0f cd 04 c6 29 8d 00 83 cc 04 fe 2c 30 05 32 5b e1 0f cd 04 33 21 85 00 06
000004c0: c5 04 b5 c5 04 00 cd 46 a0 29 8d 00 87 cd 14 ec cd 04 11 cd 04 8d 29 8d 00 8a 4d 04 e3 cd 04 12
000004e0: cd 04 7a 29 8d 00 8b cd 04 5a cd 06 07 cd 04 67 29 8d 00 96 cd 24 d1 cd 44 14 ce 04 54 05 28 fd
00000500: 0b 8f cd 04 c8 6c 04 01 12 1b e1 1c 8c 0c 01 51 e3 42 07 2e ed 0b 92 dd 04 be 5c 04 01 32 5b e1
00000520: 16 9f 04 53 e3 2e 29 bd 01 93 cd 24 bd cd 04 17 cd 04 1b 29 8d 20 96 cd 04 ac cd 06 18 cd 04 00
00000540: 29 8d 00 97 cd 04 a2 cd 07 1b ce 04 f5 06 28 5d 07 9a cd 04 9e cd 04 3a cd 04 ea 29 8d 00 bb c5
00000560: 04 91 cd 04 1b cd 04 cf 29 8d 00 9e cd 84 88 c5 05 1c cd 04 9c 29 8d 00 9f 69 04 7f cd 04 1d cd
00000580: 04 a9 29 8d 00 a2 cd 04 76 cf 04 1a ce 04 96 06 28 a9 05 a3 cd 04 6d 2c 04 01 12 1b e1 0f 8c 04
000005a0: 01 51 e3 94 06 2c ad 05 a6 d9 86 23 7c 00 01 32 5b e1 20 9f 04 53 e3 70 29 bd 09 a7 cd 04 5a cd
000005c0: 04 21 cf 84 5d 29 8d 01 ab c9 04 3b cd 84 22 cd 44 4a 29 8d 30 aa cd 44 32 cd 04 20 cd 04 37 29
000005e0: 8d 00 f1 cd 04 29 cd 04 24 cd 04 24 29 8d 00 f2 cd 04 20 4d 44 a5 cd 04 91 29 8d 00 f2 cd 14 17
00000600: cd 84 26 ce 04 fd 05 a8 5b 07 f4 cd 04 0e cd 04 07 cd 04 ea 29 8d 00 f5 cd 04 05 cd 44 28 ce 04
00000620: d7 85 28 ad 85 f6 ce 04 fc d3 bd ba 29 8c 04 03 51 e3 c5 05 68 ad 05 d0 dd 04 f2 7c 04 01 32 5b
00000640: e1 2a 9b 04 53 e3 b1 29 bd 20 d1 cd 04 a9 cf 04 2b cd 04 9d 28 8d 00 d4 cd 04 e0 c9 04 2c cd 0c
00000660: 9f 29 8d 01 d5 cd 04 d7 cd 04 2d cd 04 78 29 8d 00 c8 cd 04 ce 8d 04 2e c9 04 6d 29 8d 00 d9 cd
00000680: 04 c5 c9 04 2f cd 04 52 29 8d 20 d4 cd 05 bc cd 04 30 cd 04 3f 29 8d 00 dd cd 04 93 cd 04 31 cd
000006a0: 04 2c 29 8d 00 e0 ed 14 aa cd 00 32 cd 04 19 29 ad 05 e1 cd 04 a1 6c 04 01 12 5b e1 33 8d 44 51
000006c0: e3 87 2d ad 05 f4 dd 04 96 7c 04 01 32 5b a1 34 8c 84 01 53 e3 f3 00 28 fd 07 e5 cd 04 8e cd 04
000006e0: 35 cd 04 e0 29 8d 00 e8 cf 04 85 dd 04 36 cd 04 cd 29 85 00 e9 cd 04 7c cd 04 b7 cd 04 ba 29 8d
00000700: 40 47 cd 04 89 cd 04 38 cd 04 a7 2b 8d 00 48 cd 04 80 cd 00 39 cd 04 d4 29 8d 00 5b cd 44 75 cd
00000720: 04 3a cd 04 81 29 8d 00 4c c4 04 6e cc 04 0d 3e 02 e6 a5 00 20 93 e3 7e 04 00 1a 05 00 a0 e0 11
00000740: 02 00 40 00 00 00 00 10 31 18 10 06 68 d3 3b ce 00 00 00 00 00 00 00 02 1c 01 00 00 05 00 00 00
00000760: 6c 08 00 00 00 00 00 00 00 00 20 00 00 00 01 02 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00
00000780: 04 00 00 00 00 00 00 00 08 00 00 00 00 80 00 00 42 00 00 00 00 00 00 00 08 00 01 00 00 00 00 00
000007a0: 10 80 00 02 00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 01 40 00 04 01 00 00 00 c0 00
000007c0: 00 00 00 40 00 00 00 00 08 00 00 10 00 01 00 00 00 02 00 00 24 00 00 40 00 00 20 00 10 00 00 04
000007e0: 10 00 00 00 00 00 00 02 00 20 00 00 00 01 02 00 00 08 00 00 04 00 00 00 00 00 00 00 00 00 00 00
00000800: 20 01 00 00 20 10 00 00 03 00 00 00 00 00 00 00 00 00 00 00 28 00 00 00 80 00 00 08 00 00 00 04
00000820: 00 00 00 00 00 00 40 00 04 00 00 00 00 00 00 00 10 00 00 00 20 80 00 00 00 02 00 00 00 00 00 00
00000840: 20 00 00 00 40 00 40 00 00 00 00 00 00 01 00 00 00 00 00 00 08 00 00 00 04 00 00 00 00 00 00 00
00000860: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10 00 30 00 00 00 00 00 00 00 00 00 00 00 00 00
00000880: 00 04 00 00 40 00 00 00 08 00 00 04 20 00 00 40 00 00 50 00 00 00 00 00 00 04 10 00 00 20 00 00
000008a0: 00 01 00 00 00 00 00 08 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 00
000008c0: 00 00 00 00 20 00 00 04 08 00 00 00 00 00 40 00 00 00 00 00 10 00 00 00 00 00 10 00 00 00 00 04
000008e0: 20 00 00 00 00 20 00 00 04 01 00 00 00 00 01 00 00 00 40 00 80 20 08 00 00 00 00 00 00 00 00 04
00000900: 00 01 00 40 20 10 40 00 00 00 00 08 00 41 42 00 00 00 10 00 04 00 40 00 00 00 00 00 00 00 00 00
00000920: 00 00 00 00 00 80 00 00 00 00 00 10 00 00 00 00 10 00 10 00 20 00 00 04 02 00 00 00 00 00 00 00
00000940: 00 00 00 00 c0 00 00 02 01 00 14 00 00 20 02 00 00 02 50 00 04 00 00 00 00 02 00 10 01 04 00 00
00000960: 00 00 00 00 00 80 00 08 00 01 00 00 20 00 02 00 00 00 20 00 08 00 00 00 00 00 10 00 00 00 00 00
00000980: 20 04 00 00 00 00 00 00 00 20 00 00 00 08 00 00 00 08 02 00 30 00 00 00 00 00 00 18 00 00 00 00
000009a0: 24 04 c0 80 00 00 20 00 00 00 00 08 00 01 00 00 00 00 00 00 08 00 00 00 00 04 00 00 00 00 00 00
000009c0: 00 00 00 00 00 00 00 00 00 00 00 02 00 01 00 00 00 00 00 01 00 00 00 00 00 00 00 10 00 00 00 00
000009e0: 00 00 00 00 01 01 00 00 00 00 00 00 00 00 40 00 10 00 00 00 00 00 00 00 00 00 00 00 03 00 00 00
00000a00: 00 00 04 00 00 00 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002d00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002d20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002d40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002d60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002d80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002da0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002dc0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002de0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002e00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002e20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002e40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002e60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002e80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002ea0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002ec0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002ee0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002f20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002f40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002f60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002fa0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00002fc0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 31 18 10 06 79 81 e1 9b 22 09 26 00 00 00 00 00
00002fe0: e4 05 00 00 01 00 00 00 60 12 00 00 cf 22 00 20 00 00 00 00 00 00 00 00 00 10 00 00 01 00 00 00
00003000: 00 20 8a 22 00 eb 02 00 70 e3 fd 00 a0 03 83 f4 ff 0a 00 40 8d e5 05 00 a0 e1 24 10 0d e3 04 20
00003020: a0 e3 0c 30 a0 e3 81 22 00 eb 03 00 70 e3 fe 00 a0 03 7a f4 34 8c 00 0a 78 22 00 eb 06 00 70 e3
00003040: f9 00 a0 03 71 35 1c 01 0a 6f 22 00 eb 07 00 70 e3 fa 00 a0 03 68 35 8c 00 0f 66 22 00 eb 61 f4
00003060: ff ea 0f 33 00 e3 8c 2e 0e e3 00 30 bc 11 00 06 08 10 a0 e1 b2 23 40 e3 98 3b 1f e5 ce 5d 00 eb
[BrcdSoftlockup]: BUG: soft lockup - CPU#0 stuck for 44s! [mount:565]

DHCP Issue. ICX7750 Version 08.0.95pT203..Help!!

PC_JP — Wed, 15 Jan 2025 00:26:09 +0000

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#M7109

SW version is 08.0.95pT203

I have created 2 VLANS. For example vlan 100 and vlan 101
For 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 Address
DHCP 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 Identifier
Client Mac Address:<------>
*OPtion:(12) Hostname
Hostname:
*option:(55) Parameter Request list
Length:12
Parameter Request List Item: (1) Subnet mask
Parameter Request List Item: (3) Router
Parameter Request List Item: (6) Domain name Server
Parameter Request List Item: (15) Domain name
Parameter Request List Item: (26) Interface MTU
Parameter Request List Item: (28) Broadcast Address
Parameter Request List Item: (51) IP Address lease time
Parameter Request List Item: (58) Renewal time value
Parameter Request List Item: (43) vendor-specific Information
Parameter Request List Item:(114) DHCP Captive-Portal
Parameter Request List Item: (108) IPv6-Only Preferred

switch configuration:
ip dhcp-server pool vlan100
excluded-address 192.168.92.1
!
excluded-address 192.168.92.100 192.168.92.254
lease 1 0 0
network 192.168.92.0 255.255.255.0
option 3 ip 192.168.92.1
deploy
ip helper-use-responder-ip

interface ve 100
vrf forwarding abc
ip address 192.168.92.1 255.255.255.0
ip helper-address 1 192.168.92.1

also globally i have enabled
ip dhcp-server enable
ip dhcp-server relay-agent-echo enable

Ruckus ICX 7150-C12 disconnected after power outtage

Gaatgk — Mon, 30 Dec 2024 11:17:43 +0000

I have reset both my router and the switch by unplugging them and plugging them back in. I called Verizon and they said everything is good on their end. I have been able to connect to the my Ruckus dashboard and it shows the switch is disconnected. I’ve used the IP scanner and put in both IPs that appear because it doesn’t designate which is the switch. I have intermittent internet access or none at all. Here is a picture of my dashboard. Please help.

IP Address Assignment in 8200 Devices

Mayank — Thu, 11 Apr 2024 11:30:15 +0000

:: IP ADDRESS ASSIGNMENT IN 8200 DEVICES::

In 8200, The Switching image was deprecated with 10.0 and each platform will only use one image starting with 10.0.

ALL the L3 image support L2 features starting with 10.0, Only routing image are available for all supported models.
Switching features are still available in the routing image.

>The 8200 by design doesn't support l2 image so there is no ip default-gateway command.

>Instead we need to specify the route to forward the traffic to an external subnet. We can either use static routes, default routes or a routing protocol.

>If you want to use the ICX8200 switch as a L2 device follow the below steps:

You just need to add a default route to the device, And then add the VLANs you want. The ICX8200 model can only run L3 firmware images. That's why we need to add a default route for it to start behaving as an L2 switch, where it is only passing VLAN traffic in and out. We also need to identify the VLAN where this default route communication goes through. And then create a virtual interface and assign the IP that will be used for management and for communication with the default gateway.

Example:

-Create the virtual interface and assign the IP form MGMT and default route:

ICX8200-switch#conf t
ICX8200-switch(config)#vlan 10
ICX8200-switch(config-vlan10)#interface ve 10
ICX8200-switch(config-if-ve10)#ip address 10.10.10.2/24

Here's the command for the default route:

ICX8200-switch#conf t
ICX8200-switch(config)#ip route 0.0.0.0/0 10.10.10.1 (IP address of your ICX7850 router, which is the default gateway for the management vlan)

ICX8200 with the code 10.00, this code only came in routing, so you can configure the IP address under a VE, loopback or port.

Beginning with the 09.0.00 release, when a VLAN is configured, a virtual routing interface is statically mapped to the VLAN ID. However,
only when you issue the interface ve-num command does the virtual interface get created.

Please refer to the below link of the L3 Routing configuration Guide under Subheading "Assigning an IPv4 Address to an Ethernet Port"

https://support.ruckuswireless.com/documents/4466-fastiron-10-0-10-ga-layer-3-routing-configuration-guide

Please refer to the below link of the L3 Routing Configuration Guide under Subheading "Assigning an IP address to a virtual interface"

https://support.ruckuswireless.com/documents/4466-fastiron-10-0-10-ga-layer-3-routing-configuration-guide

Please refer to the below link of the L3 Routing Configuration Guide under Subheading "Assigning an IP address to a loopback interface"

https://support.ruckuswireless.com/documents/4466-fastiron-10-0-10-ga-layer-3-routing-configuration-guide

ICX7250 authenticated Session is Cleared[Termination-Cause: Host-Moved]

scottshotgg — Wed, 13 Nov 2024 00:00:26 +0000

Hi,

I have an ICX7250-48P (version SPR 8095m) that is exhibiting some strange behavior with RADIUS and I am unsure if it is my configuration or if this is how MAC Auth is expected to work on the ICX line. For reference, I have configured RADIUS before and am currently using another server for a few wireless access points we have. For testing purposes, I was going to point all clients to the default guest VLAN (50) using the DEFAULT in RADIUS. The ICX receives this and changes the port over but then immediately terminates the session which thrashes the clients back and forth between the blackhole VLAN (default: 666) and the default guest VLAN (50). This basically makes the switch unusable since no traffic can get through. I will post my auth config, logs, and RADIUS config below as well. It would be much appreciated if there was anyone out there that could provide any bit of help!

Thank you,

Scott

RADIUS config:

# Default to VLAN 50
DEFAULT Auth-Type := Accept
Tunnel-Type = "VLAN",
Tunnel-Medium-Type = "IEEE-802",
Tunnel-Private-Group-Id = "50",
Reply-Message = "Hello, %u"

show run auth

authentication
auth-order mac-auth dot1x
auth-default-vlan 666
max-sessions 1024
reauth-timeout 0
mac-authentication enable
mac-authentication enable ethe 1/1/12 ethe 1/1/48
mac-authentication password-format xx:xx:xx:xx:xx:xx
mac-authentication dot1x-disable
!

show logging:

Nov 12 20:36:10:N:FLEXAUTH: Port 1/1/12 is deleted from Dynamic Vlan 50 as mac-vlan member
Nov 12 20:36:10:N:FLEXAUTH: Port 1/1/12 is added into Auth-Default Vlan 666 as mac-vlan member
Nov 12 20:36:10:N:MACAUTH: port 1/1/12 mac c8f7.50fb.0ec4 vlan 50: authenticated Session is Cleared[Termination-Cause: Host-Moved]
Nov 12 20:36:09:N:MAC Authentication succeeded for [c8f7.50fb.0ec4 50] on port 1/1/12
Nov 12 20:36:09:N:FLEXAUTH: Port 1/1/12 is deleted from Auth-Default Vlan 666 as mac-vlan member
Nov 12 20:36:09:N:FLEXAUTH: Port 1/1/12 is added into Dynamic Vlan 50 as mac-vlan member
Nov 12 20:36:09:N:MACAUTH: Port 1/1/12 Mac c8f7.50fb.0ec4 - received AAA-ACCEPT
Nov 12 20:36:09:C:MACAUTH: RADIUS server 10.32.0.1 Accepted for c8f7.50fb.0ec4 with (U:50 )
Nov 12 20:36:09:N:MACAUTH: port 1/1/12 mac c8f7.50fb.0ec4 vlan 666: Session is created
Nov 12 20:36:08:N:FLEXAUTH: Port 1/1/12 is deleted from Dynamic Vlan 50 as mac-vlan member
Nov 12 20:36:08:N:FLEXAUTH: Port 1/1/12 is added into Auth-Default Vlan 666 as mac-vlan member
Nov 12 20:36:08:N:MACAUTH: port 1/1/12 mac c8f7.50fb.0ec4 vlan 50: authenticated Session is Cleared[Termination-Cause: Host-Moved]
Nov 12 20:36:07:N:MAC Authentication succeeded for [c8f7.50fb.0ec4 50] on port 1/1/12
Nov 12 20:36:07:N:FLEXAUTH: Port 1/1/12 is deleted from Auth-Default Vlan 666 as mac-vlan member
Nov 12 20:36:07:N:FLEXAUTH: Port 1/1/12 is added into Dynamic Vlan 50 as mac-vlan member
Nov 12 20:36:07:N:MACAUTH: Port 1/1/12 Mac c8f7.50fb.0ec4 - received AAA-ACCEPT
Nov 12 20:36:07:C:MACAUTH: RADIUS server 10.32.0.1 Accepted for c8f7.50fb.0ec4 with (U:50 )
Nov 12 20:36:07:N:MACAUTH: port 1/1/12 mac c8f7.50fb.0ec4 vlan 666: Session is created
Nov 12 20:36:05:N:FLEXAUTH: Port 1/1/12 is deleted from Dynamic Vlan 50 as mac-vlan member
Nov 12 20:36:05:N:FLEXAUTH: Port 1/1/12 is added into Auth-Default Vlan 666 as mac-vlan member
Nov 12 20:36:05:N:MACAUTH: port 1/1/12 mac c8f7.50fb.0ec4 vlan 50: authenticated Session is Cleared[Termination-Cause: Host-Moved]

How to create a VLAN

Yarenis — Tue, 05 Nov 2024 20:39:14 +0000

! Management VLAN configuration.

SCH-ACCESS-101(config)# vlan 10 by port
SCH-ACCESS-101(config-vlan-10)# untag ethernet 1/1/1 to 1/1/4
SCH-ACCESS-101(config-vlan-10)# management-vlan
SCH-ACCESS-101(config-vlan-10)# default-gateway 10.10.10.1 1
SCH-ACCESS-101(config-vlan-10)# default-gateway 10.20.20.1 2

! User VLAN configuration.

SCH-ACCESS-101(config)# vlan 1011
SCH-ACCESS-101(config-vlan-1011)# tagged ethernet 1/1/13 to 1/1/17 ethernet 1/2/2 ethernet 1/2/4 ethernet 2/2/2 ethernet 2/2/4
SCH-ACCESS-101(config-vlan-1011)# untagged ethernet 1/1/12
SCH-ACCESS-101# show vlan 1011
Total PORT-VLAN entries: 14
Maximum PORT-VLAN entries: 64
Legend: [Stk=Stack-Id, S=Slot]
PORT-VLAN 1011, Name data_vlan, Priority level0, Spanning tree On
Untagged Ports: (U1/M1) 12
Tagged Ports: (U1/M1) 13 14 15 16 17
Tagged Ports: (U1/M2) 2 4
Tagged Ports: (U2/M2) 2 4
Uplink Ports: None
DualMode Ports: None
Mac-Vlan Ports: None
Monitoring: Disabled

! Multiple VLANs applied to a single port.

Device(config)#vlan 2 3 5 6 9 12
Device(config-mvlan-2*12)#tagged ethernet 1/1/1
Device(config-mvlan-1*12)#show vlan brief ethernet 1/1/1

Port 1/1/1 is a member of 6 VLANs
VLANs 1 3 5 to 6 9 12
Untagged VLAN : 1
Tagged VLANs : 3 5 to 6 9 12

DNS Domain configuration causing AP connectivity issue with RUCKUS Cloud

syamantakomer — Thu, 26 Jan 2023 16:31:13 +0000

Hello All,

In this article, I will explains an issue with customer DHCP configuration (related to DNS Domain name) which can potentially cause AP connectivity issue with RUCKUS Cloud.

Symptoms

If you hit this issue, AP may show online but as soon as you make any configuration changes on venue, AP, WLAN, it will result AP state changing to "Never contacted Cloud".

AP will not show any new event, since the time of its last successful connection to Cloud.
In some cases AP will also show in "Operational - applying configuration" state on Cloud UI and will never complete applying configuration.

AP will still serve clients with last known configuration (if AP was not rebooted).

How to troubleshoot?

Run a capture on switch port where AP is connected and reboot the AP.
Note: This will not help if AP is configured with static IP configuration.
Check the uplink packet capture and analyze (look at the DHCP Offer frame) the DHCP packets for the DHCP process.
You will see DHCP server sending DNS domain name information.

When Domain Name is added to the DHCP and configured on AP, AP will append the AP-Cloud discovery URL which is device.ruckus.cloud to device.ruckus.cloud.xyz.com. Because of this change in Cloud URL, AP will not be able to reach the correct controller IP (usually DNS resolution will fail) and will eventually fail to connect to Cloud.
In case domain specific URL (in this case "device.ruckus.cloud.xyz.com") has a valid DNS entry on customer/public DNS server, it will further result in connection failure as resulted IP address will not match with the correct Cloud controller IP address.
You can also factory reset one AP and then SSH into it (with default credentials super/sp-admin), run below commands to confirm if AP is getting the DNS Domain name configuration from DHCP.
Run and review the output of "get dns" command.
Output when DNS Domain name is received from DHCP server.

rkscli:
rkscli: get dns
Allow DNS from DHCP: Enabled
Ethernet DNS servers:
DNS 1 : 8.8.8.8
DNS 2 : 8.8.4.4

IPv6 DNS Setting

DNS Domain

DNS Search List

OK
Output when DNS Domain name is received from DHCP server

rkscli:
rkscli: get dns
Allow DNS from DHCP: Enabled
Ethernet DNS servers:
DNS 1 : 8.8.8.8
DNS 2 : 8.8.4.4

IPv6 DNS Setting

DNS Domain
xyz.com

DNS Search List

OK

Resolution

While issue is impacting RUCKUS APs, this is completely an issue caused by customer DNS and/or DHCP server configuration.

Follow below steps to fix the issue.

Check and remove the domain name configuration from DHCP IP pool which is used for RUCKUS Access points.
Just updating the configuration on DHCP server may not fix APs as APs will still hold old IP which has valid lease time. In this case you may reboot the AP so that AP can get the fresh IP lease from DHCP server without DNS domain name. Also clearing the IP lease from DHCP server can help.
Even after rebooting or re-requesting IP from DHCP if issue is not solved, remove the AP from the Cloud and re-add.
If you continue seeing issue even after fixing the DHCP configuration, please contact RUCKUS Support and report the issue.

I hope this will help!

Got any queries? Start the conversation!

Setting Up Port Monitoring on an ICX Switch

Vásquez_Fer — Tue, 27 Feb 2024 17:27:06 +0000

Overview of Port Mirroring and Monitoring

Port mirroring is an effective network traffic monitoring technique. It involves duplicating each packet entering or leaving a specific port on a network switch and sending this copy to another port for analysis. This technique is particularly useful for diagnostic and debugging purposes, as well as for enhancing network security.

To set up port mirroring, you designate a 'monitor port' from which packets are copied, and a 'mirror port' that receives these copies. Both incoming and outgoing packets from the monitor port are sent to the mirror port. A network analysis tool, like Wireshark, can then be connected to the mirror port to capture and analyze the traffic. This process allows for detailed examination of data packets without interfering with the normal operation of the network.

Standalone(config)# mirror-port ethernet x/x/x - This command designates the connection to the analyzer tool.
Standalone(config)# interface ethernet x/x/x - This command selects the specific interface from which data capture is desired.
Standalone(config-if-e1000-x/x/x)# monitor ethernet x/x/x both - This command establishes the monitoring of the specified interface and directs the traffic to the analyzer tool.

Verification of Configuration:

To verify the configuration, use the "show mirror" command. This will display the current mirror configuration, confirming the setup for traffic capture and analysis.

Here is an example using the given topology. Our objective is to capture traffic from port 1/2/1 and redirect it to an analyzer tool connected to port 1/1/1, where Wireshark is installed.


Device(config)#mirror-port ethernet 1/1/1
Device(config)#interface ethernet 1/2/1
Device(config-if-e25000-1/2/1)#monitor ethernet 1/1/1 both

Device(config-if-e25000-1/2/1)#show mirror
Mirror port 1/1/1
  Input monitoring      : (U1/M2)   1
  Output monitoring     : (U1/M2)   1

For additional details, please refer to our guides :

Official Guide Port Mirroring and Monitoring Configuration:

https://docs.commscope.com/bundle/fastiron-10010-monitoringguide/page/GUID-7165A5D9-141A-4F23-9965-2940D12A672E.html

Official Guide Configuration Notes for Port Mirroring and Monitoring:

https://docs.commscope.com/bundle/fastiron-10010-monitoringguide/page/GUID-8CDDEB0F-08D9-41A9-9681-B3C05D315BD7.html

Monitoring an Individual LAG Port:

https://docs.commscope.com/bundle/fastiron-08095-monitoringguide/page/GUID-35140D88-386B-438B-A700-59AFDE2297B7.html

Best Regards

Fernando Vasquez

Stacking ICS 7850 with port DATA

mouhssenHB — Mon, 29 Jul 2024 11:41:16 +0000

Hello,

Can i convert data Ports (Ethernet 1/1/47) to be used for stacking in switch model ICX-7850

Best regards

"trunk" port isn't a trunk?

VidiotsAGL — Fri, 26 Jul 2024 16:12:06 +0000

show int eth 1/3/1

Port Link State Dupl Speed Trunk Tag Pvid Pri MAC Name
1/3/1 Up Forward Full 10G None Yes 2 0 xxxx.xxxx.xxxx uplink

show run int eth 1/3/1
interface ethernet 1/3/1
port-name uplink
spanning-tree 802-1w admin-pt2pt-mac

show run vlan (condensed)

vlan 30,30,33
tagged eth 1/3/1

vlan 2
untagged eth 1/3/1

for all purposes, eth 1/3/1 is a trunk, but it says it isn't.
what does this mean?

Ruckus One ICX-7150 CLI Session login - no user / pw combo is working

ChrisB — Thu, 11 Jul 2024 16:55:24 +0000

Hi,

Im trying to access the ICX-7150 switch from Ruckus One CLi Session. It's asking for a login but none of the combos are working. How/Where do I create a login / pw combo that works?

future of clustering & mct

inphobia — Tue, 07 May 2024 00:44:26 +0000

tl:dr: does mct have a future or is it getting phased out.

heya,

we recently got 4 7850's to replace some aging cisco nexus's, they won our public tender easily & specs are impressive. we are a heavy user of vpc on the nexus side, but replacing this with mct has proven to be a challenge. our tender specified as minimal feature l3 redundancy for ipv6, so we're bound to 10.0.10 or higher.

we also required link bundeling over 2 devices running independant operating systems while presenting themselves as a single device to the other end: which mct (multi chassis trunking) provides.

finally, pvrst needed to be supported on all links.

which is when the fun started as any vlan that becomes an mct vlan disables stp. both our partner & their ruckus liasons always came with examples from the 8.0.95 docs ( https://docs.commscope.com/bundle/fastiron-08095-l2guide/page/GUID-F20E9DED-FCDA-4C3C-BBC7-19127E9E18FC.html ), in specific the last 2 mct chapters. those are notably abcent (with good reason i guess) from 10.0 docs.

in the end i got a config working with mct + pvrst when using stp in "single" mode. while not what we intended it can be argued that this meets the minimum reqs detailed in our tender.

my current view of mct is not really possive after all this. documentation for the 10.0.x train as it stands is quite inconsistent, troubleshooting pretty barebones, created quite a few inconsistent (different stp protocols, differing vlans, etc) mct's which still got accepted, snmp support for mct also seems to have gotten lost somewhere along the way, issu for clusters seems to talk about stacks instead. our partner also let slip they only had 1 client which used mct & tried to push us to going for a stack instead.

however, i'm running out of time & need to get these in production. since our partner has been excellent in other projects they won i don't want to return these switches due to being non complaint (since i already sent back the 8200's due to no redundant&hot swap fans & psu's - at least the model they proposed) and as noted above mct in 10.0 seems like it can use some love: i'll be going for stacking instead of clusters.

long intro , now to the question: what's the plan for mct? from what the rumormill told me 10.0.x was a major rework of the code make it less complex going forward. is mct low in the todo queue (for whatever reason), is a replacement in the works, is it being phased out? i started this project on 10.0.10a, used each release including cd versions up until the 10.0.20 i'm on now, but the release notes are silent on mct items.

all that said: kudos to the ruckus support staff. this might be the second time in 20 years that support was lightning fast to respond, actually knew the products they support, had frequent & to the point feedback. and actually got the bugs resolved.

(this was fun: "ping vrf tstix 10.40.69.252 source 10.40.69.2532" - and 2532 is not a typo - case 01631172)

Administration of 8200x series via Ruckus Cloud

john_nickell_74 — Fri, 19 Apr 2024 18:33:34 +0000

Admitting out the gate that I'm new to Ruckus CLI & really using the Ruckus Cloud for Switches. We've had Ruckus AP's on the Cloud platform for about a year (and about 7yrs of ZoneDirector prior). We've been running HP/Aruba Procurve switches via CLI for over 10yrs. We went with Ruckus cloud with the idea of lowering the barrier to entry for the rest of the team.

Our environment is not terribly complex and routing is handled by an external device so the switches don't need to handle this. I'm trying to do as much of the config via the cloud and am not having a whole log of success.

First thing is setting up one of the Distribution switches. We currently have VLAN1 configured as a tagged member on the trunk port between the Distribution and Core. I don't appear to be able to assign VLAN1 as a tagged member on the port via the Cloud UI. Is this a UI limitation or a Ruckus limitation?

Second is that if I make "multiple" configuration changes on a port it in the Cloud UI and click apply it seems to fail. For example trying to apply multiple Tagged VLANs to the uplink port (one of them being set as a voice VLAN) and it fails everytime. I can apply 1 or 2 VLANs and that seems to work if none of them are the voice vlan. I can't add the voice VLAN and remove another VLAN at the same time. The uplink port that I'm trying to configure is NOT the port that the switch is connected to the "Internet" through. The uplink port currently has no cable plugged into it.

Am I experiencing a learning moment or are these issues that I should take to support?

Configuring Radio Profiles for WLANs Across AP Groups in RUCKUSOne

vasanth_edward — Mon, 01 Apr 2024 11:27:41 +0000

As a Ruckus Technical Assistance Center (TAC) engineer, this knowledge article aims to provide guidance on assigning radio profiles to AP groups within the same venue in the RUCKUSOne platform. This specific tutorial addresses the scenario where a customer wishes to disable the 2.4GHz radio for a WLAN in one particular AP group while allowing clients to connect using both radios in other AP groups.

Customer Environment: The customer's setup comprises 128 APs organized into three AP groups. They seek to disable the 2.4GHz radio for a specific WLAN within one AP group, while maintaining functionality across both radios for the remaining AP groups.

Resolution: Below are the steps to configure radio profiles for WLANs across AP groups:

1. Navigate to the desired Venue within the RUCKUSOne platform.

2. Select the "Networks" tab.

3. Locate and click on the WLAN configured for the Guest network.

4. Within the WLAN settings, click on the highlighted "Radios" option.

5.Select "Specific AP groups" to customize radio settings for individual AP groups.

6. Choose the desired AP group where you wish to disable the 2.4GHz radio for the WLAN.

7. Toggle the radio options to enable or disable as per requirements for the selected AP group.

8. Click "Apply" to save the changes.

9. Hover over the "Radios" option of the specific WLAN to verify that the settings have been successfully applied to the chosen AP group.

Conclusion: By following the outlined steps, users can effectively manage radio profiles for WLANs across different AP groups within the RUCKUSOne platform. This capability allows for granular control over wireless network configurations, ensuring optimal performance and customization based on specific deployment requirements.

If you found this information helpful, please consider clicking on the "KUDOs" button to assist other users.

Regards,

Vasanth Edward || Snr TSE

RUCKUS Networks, CommScope!

RUCKUS One Cloud - Important Notice - Action Required before March 27th

naresh_kumar_74 — Fri, 22 Mar 2024 09:39:28 +0000

Dear Valued Customer,

The RUCKUS One team will be adding a new outbound http connection, http://ocsp.godaddy.com on March 27th, 2024. If you do not currently whitelist the outbound connections from your premises, you will not be impacted. If you do, please add this new entry to your existing outbound firewall rules before March 27th, 2024 or service will be impacted.

To allow RUCKUS One to function properly, please configure your firewall to allow for outbound connectivity according to the following guidelines:

Outbound HTTPS (TCP 443) from APs and Switches to:

https://ap-registrar.ruckuswireless.com

https://sw-registrar.ruckuswireless.com

https://ruckus.cloud

https://eu.ruckus.cloud

https://asia.ruckus.cloud

https://device.ruckus.cloud

https://device.eu.ruckus.cloud

https://device.asia.ruckus.cloud

https://storage.googleapis.com

Outbound HTTP (TCP 80) from APs and Switches to:

http://ocsp.godaddy.com (New!)

http://ocsp.comodoca.com

http://ocsp.entrust.net

Outbound SSH (TCP 22) from APs and Switches to:

device.ruckus.cloud

device.eu.ruckus.cloud

device.asia.ruckus.cloud

Ensure you have a DNS server configured for your network infrastructure devices. DNS is required for the access points to resolve the RUCKUS One controller names to operate properly.

Need help?

If you need help with products, please contact RUCKUS Technical Support via normal procedures referenced in the RUCKUS Support Portal.

Thank you for your continued support.

Regards,
RUCKUS Cloud Team

How to update firmware on the ICX switches via the cloud Ruckus One

jdryan — Wed, 13 Mar 2024 16:29:18 +0000

For ease of management and monitoring of the ICX switches, they are enabled to communicate with Ruckus's cloud platform : Ruckus 1 or R1, as we call it.

Here we have the switch onboarded to the cloud under the venue :
We see the same under Wired >> Switch List

Where the highlight shows the firmware they are currently on,.

Now to update the firmware:
First, to set the version :
Hence
Administration [ bottom left corner ] >> version management >>>

Here go to , Switch firmware and select the venue >> and click on Change Update Schedule:

Once there the below dialog-box will appear:

Where we select the code that’s needed.

And generally the code available on the cloud is the recommended releases for the cloud connected devices or devices that would be connected to the cloud.

Here in this example : the devices are already on the recommended release : 10.0.10c_cd1

However for one of them : we'll be selecting 9010j_cd1 and setting the date and time for the activity as well

Here once the version is selected and saved,:

Once done, click on save,

Below will be displayed :

That’s for scheduling the code update,

In an event, there needs to be an immediate update done : update now is the option you need :

once the version are selected : click on run update : that will initiate the file transfer to the switches and get the update done.

Do note :

This option is only applicable if the ICX switches are connected to the cloud.
During this activity as usual downtime is needed as the switches will reload for the firmware to be applied.
Also this process/procedure applied to specific venue and all switches under the venue will get the update : hence do consider the below points
if you are an MSP :
1. Make sure that the switches that are to be updated are of the specific venue.
2 . If there are multiple locations managed under the same venue and only a specific location needs to be updated : then this may not be the best option to follow.
3 . In case, point 2 applied to you : then device local updates are best way to go about the upgradation. Via TFTP,USB etc.
if you are not an MSP, and there are multiple locations of install : but all are devices are under the same venue.
Then device local updates are best way to go about the upgradation. Via TFTP,USB etc.
If different locations are managed under different venues, there should be no issues in following this process/procedure.

FQDNs and Ports that need to be open in Firewall for Ruckus One

vasanth_edward — Thu, 29 Feb 2024 11:15:27 +0000

To ensure proper communication between the APs and switches with RUCKUS One, customers must allow some FQDNs and Ports in their Firewall.

Customer Environment

APs and Switches deployed behind a firewall and inbound/outbound traffic needs to be allowed for successful communication between RUCKUS network devices and RUCKUS One.

Symptoms

Newly added APs and switches are in Never Contacted Cloud state, not joining RUCKUS One.

Resolution

To allow RUCKUS One to function properly, please configure your firewall to allow for outbound connectivity according to the following guidelines:

Outbound HTTPS (TCP 443) from APs and Switches to:

https://ap-registrar.ruckuswireless.com
https://sw-registrar.ruckuswireless.com
https://ocsp.comodoca.com
https://ocsp.entrust.net
https://ruckus.cloud
https://eu.ruckus.cloud
https://asia.ruckus.cloud
https://device.ruckus.cloud
https://device.eu.ruckus.cloud
https://device.asia.ruckus.cloud
https://storage.googleapis.com
http://ocsp.godaddy.com

Outbound SSH (TCP 22) from APs and Switches to:

device.ruckus.cloud
device.eu.ruckus.cloud
device.asia.ruckus.cloud

Network Requirements

The following list of firewall ports is required to allow APs to enable Cloud discovery and continued connection with the Cloud

Checking the firewall ports is the first step of troubleshooting if an AP is unable to connect to the Cloud or disconnects from the Cloud.

https://docs.cloud.ruckuswireless.com/ruckusone/userguide/GUID-D00EA4CC-7B8A-4F99-969B-2A5FB5DDB178-low.png

If these information helped you in any way, please click on "KUDOs", so you can help other users.

AP LAN Port option greyed out

_Mudit — Mon, 18 Dec 2023 15:33:26 +0000

As a Ruckus TAC engineer, I would like to share my experience with some AP model with Single LAN port AP( for example R350) where option to change the untagged VLAN ID on AP LAN port is greyed out on Ruckus cloud GUI.

We can see that even when the enable port is checked, we are unable to update the VLAN untagged ID on the cloud GUI.

Many customers have inquired about the inability of a certain AP model, such as the R350, to modify the untagged VLAN ID on the cloud.

This is the design objective for a single LAN port APs, as there is no VLAN given in the ethernet frame for untagged traffic.

For example, our AP on VLAN 1 will be able to communicate with any other side device on any untagged VLAN.

Any changes to the AP for the untagged VLAN ID that are necessary to get the AP onto the chosen subnet must be made at the switch port level where AP is connected.

I hope you find this information useful.

Configuring Dynamic (LACP) and Static LAGs on ICX Switches

BenBeck — Mon, 08 Nov 2021 16:34:24 +0000

Hey all,

Let's take look at creating LAGs (LACP and static). LACP (802.3ad) is the most common link-aggregation method. We also offer static LAGs.

To create an LACP LAG named 'testlag' with an auto-generated id, you would issue the following:

ICX#conf t
ICX(config)#lag testlag dynamic id auto

In this example, let's assign ports 1/3/1 and 1/3/3 to this LAG:

ICX(config-lag-testlag)#ports eth 1/3/1 e 1/3/3
LAG testlag deployed successfully!

The resulting configuration from 'show run':

lag lagname dynamic id 1
 ports ethe 1/3/1 ethe 1/3/3
!

!
interface lag 1

We can see the LAG was assigned id 1 and there is also an 'intferace lag 1' in the running configuration. We can use this to define various configurations at the interface level. We will not define anything in our example, but I will show the the interface configuration mode for a lag for the sake of completeness.

ICX(config)#interface lag 1
ICX(config-lag-if-lg1)#

To ensure our LAG is working properly, you can issue 'show lag':

The most important part of this output is the [Ope] column on the far right. A LAG that is up and working will show ‘Ope’ for all ports in this column. If you see ‘Ina’ (inactive) here, you may want to confirm VLAN tagging, Layer 1 port statuses and the partner side LAG configuration.

Configurating a static LAG will be very similar. Using the same ports from our last example, the configuration would like this:

ICX(config)#lag teststaticlag static id auto
ICX(config-lag-teststaticlag)#ports eth 1/3/1 e 1/3/3
LAG teststaticlag deployed successfully!

Resulting configuration in ‘show run’:

lag teststaticlag static id 1
 ports ethe 1/3/1 ethe 1/3/3
!

!
interface lag 1

The ‘show lag’ for a static LAG will look like this:

Hopefully the above two examples will give you confidence to deploy both dynamic (LACP) and static LAGs. We do have some additional LAG options. To see all available configuration options for LAGs, please see our FastIron Layer 2 Switching Configuration Guide:

HTML Version

PDF Version (requires login)

Let us know if you have any questions!

Data Center Migration from Hongkong to Singapore

_Mudit — Fri, 08 Dec 2023 15:20:06 +0000

Pre-checks on migrations:

Make sure that all switches and APs added on cloud should be operational.
Make sure to whitelist below IPs/FQDNs on your firewall outbound rules:

IP range: 34.87.82.64 through 34.87.82.95, ports: tcp 443 & 22
FQDN: ap-registrar.ruckuswireless.com, port: tcp 443
FQDN: sw-registrar.ruckuswireless.com, port: tcp 443
FQDN: ocsp.comodoca.com, port: tcp 443 & 80
FQDN: ocsp.entrust.net, port: tcp 443 & 80
FQDN: device.asia.ruckus.cloud, port: tcp 443 & 22
FQDN: storage.googleapis.com, port: tcp 443

Post migration connectivity checkpoints and troubleshooting before contacting Ruckus Support:

AP Troubleshooting:

Connect laptop to a switch and same subnet as APs. Ping device.asia.ruckus.cloud, and please check if the resolved IP is in range: 34.87.82.64 through 34.87.82.95.

If the resolved IP is outside the mentioned range (34.87.82.64 through 34.87.82.95), make sure to flush DNS cached entries from DNS server. Now try to resolve “device.asia.ruckus.cloud” and validate that IP resolution is within the specified IP range.

$ curl -XGET “https://device.asia.ruckus.cloud”

On MacOS, a success response would be:

curl: (56) LibreSSL SSL_read: LibreSSL/3.3.6: error:1404C45C:SSL routines:ST_OK:reason(1116), errno 0

On Windows PC, a success response would be:

curl : (56) Send Failure: Connection was aborted

Check reachability to https://device.asia.ruckus.cloud using the command below.

Feel free to contact Ruckus Support, if all the troubleshooting steps are exhausted.

ICX Switch Troubleshooting:

For Switches on version 9010e and 9010f kindly reboot the switches to clear DNS cached entries.

Switches on version 9.0.10h_cd2 and 10.0.10b (for ICX 8200 switches) will not require a reboot to get connected to the new DC.

Run “show sz status” from switch CLI and check SWR (Switch Registrar) IP has updated new IP range from 34.87.82.64 through 34.87.82.95.

If the IP address is outside the above range run below commands:

device(config)# manager disable
device(config)# no manager disable
device# manager registrar-query-restart
device# show manager status

Feel free to contact Ruckus support if above steps does not help.

Note that, switch disconnection from cloud doesn’t impact the production due to data center migration.

iPhone and MacBook devices constantly disconnecting from the wireless network

Orlando_Elias — Sat, 28 Oct 2023 01:30:27 +0000

In my work as a TAC support agent for RUCKUS Wireless products, I've recently encountered cases where iPhone and MacBook users complain of frequent disconnections from the wireless network. I've been able to resolve those cases by following the steps below.

This is part of the symptom you will see in the AP support log:

Aug 19 17:58:11 clbd sta join XX:XX:XX:XX:XX:XX wlan3(YY:YY:YY:YY:YY:YY) 1 rssi=(25 42) 2g(0x0 4 31) 5g(0x0 4 13) 
Aug 19 17:58:12 clbd sta leave XX:XX:XX:XX:XX:XX wlan36(YY:YY:YY:YY:YY:YZ) rc=1 rss(20 0) 0 pkt(3588 12841) byte(498065 12750895) 
Aug 19 17:58:15 clbd sta join XX:XX:XX:XX:XX:XX wlan36(YY:YY:YY:YY:YY:YZ) 116 rssi=(11 22) 2g(0x0 4 29) 5g(0x0 4 12) 
Aug 19 17:58:16 clbd sta leave XX:XX:XX:XX:XX:XX wlan3(YY:YY:YY:YY:YY:YY) rc=1 rss(43 0) 0 pkt(1011 2437) byte(101751 2409641) 
Aug 19 17:58:20 clbd stamac=XX:XX:XX:XX:XX:XX bssid:YY:YY:YY:YY:YY:YZ score=0 oldstate:NONE newstate:GOOD

I tried ensuring that the airtime was decongested and free of interference, the RSSI was good, the SNR was good, and coverage for roaming was good. There weren't any notorious sources of interference, high retransmission rates, or physical errors in the APs.

For troubleshooting, I even enabled features like 'RSSI threshold' and 'Transient Client Management', but none of those were causing any difference in the constant and annoying disconnections.

So, I started to suspect more and more that there was an issue with those Apple devices, especially when there wasn't an obvious reason for this problem. I began to research within online forums and Apple support pages, an I found many people were complaining about this issue, but there wasn't an actual resolution or valuable comments from the Apple support team until I found this Apple support forum.

This is the workaround that worked for every customer I have suggested it:

In your iPhone:

1. Go to Settings, scroll down, and select 'Privacy and Security.'

2. Select 'Location Services' and make sure the toggle is switched on.

3. Scroll down and select 'System Services.'

4. Switch off the toggle for 'Networking and Wireless.'

5. Forget the Wi-Fi network and then reconnect.

After applying these steps in iPhones running iOS 16.1 the issue was solved immediately. However, the computers kept disconnecting. Then, an upgrade on the computers to the MacOS Ventura version 13.6, finally solved the disconnection issues for the MacBooks as well.

I hope this article is useful if you're experiencing similar issues.

How to make an API call to Ruckus One

MA — Fri, 06 Oct 2023 12:52:09 +0000

Ruckus One uses JSON Web Tokens (JWT) to secure all endpoints.
POST method is used to obtain a jwt.
The API response to POST call includes tenantId and token.
Token is valid for 60 minutes.

POSTMAN:

Postman is the tool used in this example to make an API call.
API host URL will vary depending on Cloud/Ruckus One Region.
Asia: https://api.asia.ruckus.cloud
Europe: https://api.eu.ruckus.cloud
North America: https://api.ruckus.cloud

Select the method as POST.
Enter the API host url for your region.
In the Body field- select raw and enter the payload.
Select format as JSON.
Click on Send button.

The response should be 200 ok and provides tenantId and jwt information as shown below.

Now Subsequent API calls must include JWT obtained as the Bearer token authorization.

Testing an API call:

We are trying to retrieve venue details using an API call in below example.
The required API can be found here: https://docs.ruckus.cloud/api/

Enter the url as “https://api.eu.ruckus.cloud/api/tenant/{tenantId}/venue”
Under Body select none.
Change method to GET.
Select Authorization type as Bearer token and Paste the JWT token obtained in previous API Call.

The response should be 200 ok and we can see the venue information as shown in below screenshot:

References: https://docs.ruckus.cloud/api/

Unable to Upgrade / Downgrade new 7150-48ZP model switches in firmware version 8095k.

Chandini — Tue, 29 Aug 2023 18:02:59 +0000

Error encountered below:

Reason for getting the above error:

The TI PoE chipset is different for the newly released/manufactured switches with 7150-48ZP Model.
These PoE chipset work from version 8095k and above in 8095 major release and 9010h and above in 9010 major releases

Hence if you need the switches to operate with PoE then you will need to retain 8095k. If you want to add these switches to the cloud, you need to wait for 9010h release for TI PoE chipset to work.

If you try adding switches with TI PoE issue to cloud, you will encounter below error messages.

How to identify the 7150-48ZP switches have new PoE chipset:

Check the MCU details of the switch using “dm hwinfo” command. These are mostly 2023 batches of switches which have new TI PoE chipset.

ICX7150-48ZP Switch#dm hwinfo

HW Ver: 3.1 [Production-2], Main board CPLD Rev: 0.4.a

NAND Type: Micron NAND 2GiB (x 1)

Rear module card CPLD Rev: 0

Booted from: 1

Primary Uboot Failure Record: 0

Secondary Uboot Failure Record: 0

PoE hardware info:

+++++++++++++++++

Unit 1:PoE MCU: MSP430, PSE: TPS23881

Check for the PoE version and Hardware version using command “show PoE detail” when switch is on 8095k version, and you will see the below details.

Firmware

Version

----------------

01.56.1

Hardware

Version

----------------

V5R34

Device HW version : 0:V5R34 1:V5R34 2:V5R34 3:V5R34 4:V5R34 5:V5R34 6:V5R34 7:V5R34

Device Temperature(deg-C) : 0:32 1:36 2:34 3:30 4:30 5:26 6:34 7:30

Device Status : 0:Good 1:Good 2:Good 3:Good 4:Good 5:Good 6:Good 7:Good

Below are the error details you will notice related to PoE if the switch is running on 9010 version.

Switch firmware version 9010f with new TI PoE chipset:

Firmware

Version

----------------

00.0.0

Hardware

Version

----------------

UNKNOWN

Device HW version : 0:UNKNOWN 1:UNKNOWN 2:UNKNOWN 3:UNKNOWN 4:UNKNOWN 5:UNKNOWN 6:UNKNOWN 7:UNKNOWN

Device Temperature(deg-C) : 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0

Device Status : 0:Failed 1:Failed 2:Failed 3:Failed 4:Failed 5:Failed 6:Failed 7:Failed

Log Size: 2000 entries. Number of entries in use: 2 for unit 1.

Log printing is requested for complete log.

+-----+--------------------+-----+-----+---------+---------------------------------------------+

|S.No.|Timestamp | Sys | Dev | Port | Event Trace Message |

+-----+--------------------+-----+-----+---------+---------------------------------------------+

1 | Fri Jun 9 06:53:54 | N | N/A | N/A | PoE Event Log Mgr: User Req Logging On

2 | Fri Jun 9 06:54:47 | Y | N/A | N/A | Loss of sync with controller in slot 1

+-------+----------------+-----+-----+----------+---------------------------------------------+

After Rebooting the switch on 9010 version:

******* Starting HMON service for SNMPD *******

Jun 09 08:12:25:660838:info:fi_debug:debug_logs:1:4557112064: poeglue_i2c_read_boot: i2c read Failed:-4

Jun 09 08:12:25:970257:info:fi_debug:debug_logs:1:0: poeglue_proc_chassis_itc_msg: i2c write failed:-5

Jun 09 08:12:26:071219:info:fi_debug:debug_logs:1:15513810895616: poeglue_i2c_read: i2c read Failed:-4

Jun 09 08:12:26:812712:info:fi_debug:debug_logs:1:16312674812672: poeglue_i2c_read: i2c read Failed:-4

Jun 09 08:12:27:881837:info:fi_debug:debug_logs:1:17214617944832: poeglue_i2c_read: i2c read Failed:-4

Jun 09 08:12:29:029875:info:fi_debug:debug_logs:1:18099381207808: poeglue_i2c_read: i2c read Failed:-4

You will see above outputs for PoE on 9010f version.

Workaround:

If you want to use switch model 7150-48ZP switch model with TI PoE chipset in cloud, then wait for 9010h version to have PoE feature and bring these switches up in cloud.
If you don’t need the switch to be part of cloud and need PoE feature, then retain the switch in 8095k version.

Reference links:

TI PoE TSB referred:

https://support.ruckuswireless.com/technical_support_bulletins/636