The Ruckus folks are very busy. The most recent is 8.0.95c. On one of the Ruckus Twitch Live Streams, the host mentioned that 8.0.92d (and I would presume 92d or newer) will automatically try to connect to Ruckus Cloud.
Brocade ICX Series (cheap & powerful 10gbE/40gbE switching)
- Thread starter fohdeesha
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
No, 8.0.30u is the latest and final firmware for ICX6xxx line.
EDIT: fixed version typo
Last edited:
Probably a typo, but that should be 8.0.30u
Ruckus ICX 6430 and 6450 Campus Switches | Products | Ruckus Wireless Support
support.ruckuswireless.com
Using super silent fans and let it run at 12 V is one possibility. Another possibility is to use fans that already spin-up at the voltage of fan control level 1, provide sufficient air flow at this voltage and run silent. Beside the fact that an installation is much easier without soldering, the advantage is to have a second level of more cooling power in case of overheat. In your case the only fallback level is power down of the complete switch in case of overheat.
In my case it is the PoE version of the 7250 and there also are positive examples of fan mods existing. But please have a look below what could happen in case of wrong fan tuning.
ICX 7250-24P exploded.
The joy with my ICX 7250-24P suddenly came to an end when the PSU exploded yesterday. Smoke, flames and electrical "bzzzz sound" included.
To go back in time. I modified my device by replacing the fans to for noise reasons. There is no heavy load on my device and I used only one PoE device. Temperature of both sensors are fine. See record of last 24 h till crash below. The device is running like this for 3 weeks or so. The up and down is because of changing ambient temperature during day and night. But suddenly an "explosion" and it was over.
I cannot say for sure if it is because of the modification I did or by chance. Theoretically the temperature at the sensor could be fine but not in other areas. In every case I would not recommend to anybody to do this type of modification.
Anybody who wants to exchange my broken ICX 7250-24P to a running ICX 7150-24 or ICX 7150-24P?
View attachment 17835
View attachment 17836
Good points. My 7250 is a non-PoE model, but I'm sure adequate cooling is even more critical with PoE models and their larger PSUs. Do you have any examples of quieter 40mm fans that fit that criteria? Before I went with the Noctuas, I couldn't find any suitable replacements.
Thank you for the detailed write up. I think I am doing something wrong (clearly!).
It is 24port unifi port 6 (all vlans) to unifi 8port 8 (all vlans), I am using port 48 of the 6450 as the 'feed'.
If I plug port 8 from the 8 port into a PC, I can change all Vlan's on the Unifi & the PC follows suit.
If i set that same unifi port 8 to the testvlan group (Vlan 75, 85, 95, and the 'native' vlan is 105) - the same PC when plugged into Unifi port 8, can access all vlans by switching the vlan tag in windows.
When I take port 8 and plug it into port 48 on the ICX 6450 - I have it as port 48 being tagged to vlans 75, 85, 95, and 105. I do not have port 48 as dual mode or untagged - i am expecting that as nothing is untagged, it will not default to any vlan or get an IP?
Next:
Port 47 untagged as vlan 75
Port 46 untagged as vlan 85
Port 45 untagged as vlan 95
Port 44 untagged as vlan 105
If i plug the PC into ports 44-47 I am not getting any IP when I would expect each port to be on a different Vlan with an IP.
Since port 8 from the unifi works fine, I think I am making a mistake somewhere. I think I am close but not quite there. I do NOT have the management vlan on the ICX6450 as would like to deny internet access to the switch (I guess it could be done via firewall).
The ciscos dont have the Manangement vlans - just the vlans it needs.
Thanks,
Rich
It is 24port unifi port 6 (all vlans) to unifi 8port 8 (all vlans), I am using port 48 of the 6450 as the 'feed'.
If I plug port 8 from the 8 port into a PC, I can change all Vlan's on the Unifi & the PC follows suit.
If i set that same unifi port 8 to the testvlan group (Vlan 75, 85, 95, and the 'native' vlan is 105) - the same PC when plugged into Unifi port 8, can access all vlans by switching the vlan tag in windows.
When I take port 8 and plug it into port 48 on the ICX 6450 - I have it as port 48 being tagged to vlans 75, 85, 95, and 105. I do not have port 48 as dual mode or untagged - i am expecting that as nothing is untagged, it will not default to any vlan or get an IP?
Next:
Port 47 untagged as vlan 75
Port 46 untagged as vlan 85
Port 45 untagged as vlan 95
Port 44 untagged as vlan 105
If i plug the PC into ports 44-47 I am not getting any IP when I would expect each port to be on a different Vlan with an IP.
Since port 8 from the unifi works fine, I think I am making a mistake somewhere. I think I am close but not quite there. I do NOT have the management vlan on the ICX6450 as would like to deny internet access to the switch (I guess it could be done via firewall).
The ciscos dont have the Manangement vlans - just the vlans it needs.
Thanks,
Rich
Hi, is there an list of fans that will work on the ICX 6450? i have a 48p model so that's 3 fans. The fan I've seen recommended is the Sunon
KDE1204PKVX but it seems to be out of stock everywhere except an amazon listing (https://www.amazon.com/Sunon-40x40x20mm-pin-fan-KDE1204PKVX/dp/B006ODM76C) which has it for $10 which is double the regular price. So that would be $30 in fans which is not imposible but I wanted to see if there are other options. I know a lot of fans wont work wih the voltage speed contorll, so that's why I'm asking about known good options. Thanks.
KDE1204PKVX but it seems to be out of stock everywhere except an amazon listing (https://www.amazon.com/Sunon-40x40x20mm-pin-fan-KDE1204PKVX/dp/B006ODM76C) which has it for $10 which is double the regular price. So that would be $30 in fans which is not imposible but I wanted to see if there are other options. I know a lot of fans wont work wih the voltage speed contorll, so that's why I'm asking about known good options. Thanks.
Thanks @fohdeesha and @klui !
Humm. We currently have 08.0.90BT211 on the switches at the school. I'm guessing this is "90b", not the "90d" he mentions in the video (and some of the chats show).
I'll look into an upgrade to 90d, and to stay put. Will also check my personal 7250 as well.
I wonder if there were some EULA changes to disclose the cloud talking.
Anyone have access to the Brocade Network Advisor downloads? I have a license which requires me to install a 12.x.x version (which I have) but when I try to update to 14.x.x on Server 2019 it errors out with issues. Unfortunately at least 14.3.0 and 14.4.0/.1 are SAN only from Brocade. I don't have a Ruckus account to try and get a newer version. I can stay running on 12 but would like a more up to date version if it still supports the ICX/VDX lines.
Is it possible to configure interface management 1 with its own routing table on a ICX 6610, playing with VRF but looks like that int management 1 wont work, no VRF Forwarding options?
I'm looking at possibly of having a backdoor in case of emergency, workaround is using a jumpbox in that mgmt subnet... but not clean.
ICX 6610
Primary FCXR08030u.bin
SW: Version 08.0.30uT7f3
I'm looking at possibly of having a backdoor in case of emergency, workaround is using a jumpbox in that mgmt subnet... but not clean.
ICX 6610
Primary FCXR08030u.bin
SW: Version 08.0.30uT7f3
The plot thickens... According to this page, ICX switches 7150, 7550, 7650, 7850 requires firmware 8090d to connect to RUCKUS Cloud.
> * Requires ICX release 8.0.90d and above
I wonder if it's 8092 that does some type of auto-call out - or if it's 8090d and above. I wish I was setup to do network traffic snooping to see; but right now, I need to get this network up for the school. So no time at this moment to play with firmware versions.
I'll stick to 8090b that we already have. We just need some basic VLANs. I'm not even doing InterVLAN routing on these switches, to K.I.S.S. since they don't have a network person there - it's just me, part time, and I may not be around.
EDIT: Well, dammit...
> FastIron Software 08.0.91 delivers Ansible support to all ICX 7000 Series switches.
EDIT2: But on the Ansible download page, it says recommended firmware that Ansible is "applicable" for is 8090j.
Last edited:
For some reason I can't even get a local loop working using the SFP+ ports on my ICX7250-24P (PoE). I connected two 10G-SFPP-SR transcievers from fs.com (Brocade-compatible) using an 1m LC UPC to LC UPC cable. The switch is running
I connected the modules to 1/2/5 and 1/2/7 using this configuration:
Any ideas why the link doesn't come up?
08.0.80eT213.I connected the modules to 1/2/5 and 1/2/7 using this configuration:
Code:
interface ethernet 1/2/5
optical-monitor
no spanning-tree
no flow-control both
!
interface ethernet 1/2/7
optical-monitor
no spanning-tree
no flow-control bothshow optic says this:
Code:
SSH@switch(config)#show optic 1/2/5
Port Temperature Voltage Tx Power Rx Power Tx Bias Current
+-----+-------------+-------------+-------------+-------------+---------------+
1/2/5 40.8125 C 3.4091 volts -1.6392 dBm -3.9794 dBm 5.922 mA
Normal Normal Normal Low-Alarm Normal
SSH@switch(config)#show optic 1/2/7
Port Temperature Voltage Tx Power Rx Power Tx Bias Current
+-----+-------------+-------------+-------------+-------------+---------------+
1/2/7 36.7226 C 3.3953 volts -1.4375 dBm -3.2287 dBm 6.636 mA
Normal Normal Normal Low-Alarm Normalshow media validation says this:
Code:
SSH@switch(config)#show media validation
Port Supported Vendor Type
----------------------------------------------------------------------
1/2/5 Yes RUCKUS Type : 10GE SR 300m (SFP+)
1/2/7 Yes RUCKUS Type : 10GE SR 300m (SFP+)show interfaces brief says this:
Code:
1/2/5 Down None None None None No 1 0 cc4e.24dd.bf6a
1/2/7 Down None None None None No 1 0 cc4e.24dd.bf6aSo, having not ever seen someone physically loop ports on a switch like this, what is the purpose of this setup? Off-hand, I'd expect this to not work on any switch because it's the same MAC on each end.
I just wanted to verify that the transceivers are working before anything else I'd connect it to arrives. You're right about the same MAC, but should it just be... silent?
Hey guys,
I need a bit of help. Since this afternoon my ICX6610 is acting in a weird way. The symptom is packet drop/delay.
See below a sample ping
My ICX config is here -> m4r1k/nfvi_lab
A reload as well as poweroff (for more than 40 min) did not make any change.
Do you have any idea? Thanks a lot!
Follows a couple of dumps from the ICX.
I need a bit of help. Since this afternoon my ICX6610 is acting in a weird way. The symptom is packet drop/delay.
See below a sample ping
Code:
$ ping diablo -i 0.1
PING diablo (192.168.178.10): 56 data bytes
64 bytes from 192.168.178.10: icmp_seq=0 ttl=64 time=0.678 ms
64 bytes from 192.168.178.10: icmp_seq=1 ttl=64 time=0.607 ms
64 bytes from 192.168.178.10: icmp_seq=2 ttl=64 time=0.853 ms
64 bytes from 192.168.178.10: icmp_seq=3 ttl=64 time=0.780 ms
64 bytes from 192.168.178.10: icmp_seq=4 ttl=64 time=0.847 ms
64 bytes from 192.168.178.10: icmp_seq=5 ttl=64 time=0.600 ms
64 bytes from 192.168.178.10: icmp_seq=6 ttl=64 time=0.704 ms
64 bytes from 192.168.178.10: icmp_seq=7 ttl=64 time=0.701 ms
64 bytes from 192.168.178.10: icmp_seq=8 ttl=64 time=1.020 ms
64 bytes from 192.168.178.10: icmp_seq=9 ttl=64 time=0.879 ms
64 bytes from 192.168.178.10: icmp_seq=10 ttl=64 time=0.804 ms
64 bytes from 192.168.178.10: icmp_seq=11 ttl=64 time=0.786 ms
64 bytes from 192.168.178.10: icmp_seq=12 ttl=64 time=0.749 ms
64 bytes from 192.168.178.10: icmp_seq=13 ttl=64 time=0.841 ms
64 bytes from 192.168.178.10: icmp_seq=14 ttl=64 time=0.847 ms
64 bytes from 192.168.178.10: icmp_seq=15 ttl=64 time=0.958 ms
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
Request timeout for icmp_seq 22
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26
Request timeout for icmp_seq 27
Request timeout for icmp_seq 28
Request timeout for icmp_seq 29
Request timeout for icmp_seq 30
Request timeout for icmp_seq 31
64 bytes from 192.168.178.10: icmp_seq=16 ttl=64 time=1672.865 ms
64 bytes from 192.168.178.10: icmp_seq=17 ttl=64 time=1569.951 ms
64 bytes from 192.168.178.10: icmp_seq=18 ttl=64 time=1465.662 ms
64 bytes from 192.168.178.10: icmp_seq=19 ttl=64 time=1362.174 ms
64 bytes from 192.168.178.10: icmp_seq=20 ttl=64 time=1261.169 ms
64 bytes from 192.168.178.10: icmp_seq=21 ttl=64 time=1156.913 ms
64 bytes from 192.168.178.10: icmp_seq=22 ttl=64 time=1052.125 ms
64 bytes from 192.168.178.10: icmp_seq=23 ttl=64 time=949.553 ms
64 bytes from 192.168.178.10: icmp_seq=24 ttl=64 time=848.981 ms
64 bytes from 192.168.178.10: icmp_seq=25 ttl=64 time=748.313 ms
64 bytes from 192.168.178.10: icmp_seq=26 ttl=64 time=646.812 ms
64 bytes from 192.168.178.10: icmp_seq=27 ttl=64 time=546.815 ms
64 bytes from 192.168.178.10: icmp_seq=28 ttl=64 time=443.034 ms
64 bytes from 192.168.178.10: icmp_seq=29 ttl=64 time=342.879 ms
64 bytes from 192.168.178.10: icmp_seq=30 ttl=64 time=241.997 ms
64 bytes from 192.168.178.10: icmp_seq=31 ttl=64 time=141.787 ms
64 bytes from 192.168.178.10: icmp_seq=32 ttl=64 time=39.833 ms
64 bytes from 192.168.178.10: icmp_seq=33 ttl=64 time=1.124 ms
64 bytes from 192.168.178.10: icmp_seq=34 ttl=64 time=0.850 ms
64 bytes from 192.168.178.10: icmp_seq=35 ttl=64 time=0.588 ms
64 bytes from 192.168.178.10: icmp_seq=36 ttl=64 time=0.828 ms
64 bytes from 192.168.178.10: icmp_seq=37 ttl=64 time=0.934 ms
^C
--- diablo ping statistics ---
38 packets transmitted, 38 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.588/381.785/1672.865/539.441 msA reload as well as poweroff (for more than 40 min) did not make any change.
Do you have any idea? Thanks a lot!
Follows a couple of dumps from the ICX.
Code:
#show version
Copyright (c) 1996-2016 Brocade Communications Systems, Inc. All rights reserved.
UNIT 1: compiled on Feb 13 2019 at 18:30:50 labeled as FCXR08030t
(10545807 bytes) from Primary FCXR08030t.bin
SW: Version 08.0.30tT7f3
Boot-Monitor Image size = 370695, Version:10.1.00T7f5 (grz10100)
HW: Stackable ICX6610-24
==========================================================================
UNIT 1: SL 1: ICX6610-24 24-port Management Module
Serial #: SNIP
License: ICX6610_ADV_ROUTER_SOFT_PACKAGE (LID: SNIP)
P-ENGINE 0: type E02B, rev 01
==========================================================================
UNIT 1: SL 2: ICX6610-QSFP 10-port 160G Module
==========================================================================
UNIT 1: SL 3: ICX6610-8-port Dual Mode(SFP/SFP+) Module
==========================================================================
800 MHz Power PC processor 8544E (version 0021/0023) 400 MHz bus
65536 KB flash memory
512 MB DRAM
STACKID 1 system uptime is 22 minute(s) 26 second(s)
The system started at 07:28:06 GMT+01 Thu Feb 07 2036
The system : started=cold start
#show loop-detection status
loop detection packets interval: 10 (unit 0.1 sec)
index port/vlan status # errdis sent-pkts recv-pkts
1 vlan1 0 errdis port 0 993 0
2 vlan120 0 errdis port 0 993 0
3 vlan130 0 errdis port 0 993 0
4 vlan178 0 errdis port 0 388 0
5 vlan2000 0 errdis port 0 993 0
6 vlan2001 0 errdis port 0 993 0
7 vlan2002 0 errdis port 0 993 0
8 vlan2003 0 errdis port 0 993 0
9 vlan2004 0 errdis port 0 993 0
10 vlan2005 0 errdis port 0 993 0
11 vlan2006 0 errdis port 0 993 0
12 vlan2007 0 errdis port 0 993 0
13 vlan2008 0 errdis port 0 993 0
14 vlan2009 0 errdis port 0 993 0
15 vlan2010 0 errdis port 0 993 0
16 vlan2011 0 errdis port 0 993 0
17 vlan2012 0 errdis port 0 993 0
18 vlan2013 0 errdis port 0 993 0
19 vlan2014 0 errdis port 0 993 0
20 vlan2015 0 errdis port 0 993 0
21 vlan2016 0 errdis port 0 993 0
22 vlan2017 0 errdis port 0 993 0
23 vlan2018 0 errdis port 0 993 0
24 vlan2019 0 errdis port 0 993 0
25 vlan2020 0 errdis port 0 993 0
26 vlan2021 0 errdis port 0 993 0
27 vlan2022 0 errdis port 0 993 0
28 vlan2023 0 errdis port 0 993 0
29 vlan2024 0 errdis port 0 993 0
30 vlan2025 0 errdis port 0 993 0
31 vlan2026 0 errdis port 0 993 0
32 vlan2027 0 errdis port 0 993 0
33 vlan2028 0 errdis port 0 993 0
34 vlan2029 0 errdis port 0 993 0
35 vlan2030 0 errdis port 0 993 0
36 vlan2031 0 errdis port 0 993 0
37 vlan2032 0 errdis port 0 992 0
38 vlan2033 0 errdis port 0 992 0
39 vlan2034 0 errdis port 0 992 0
40 vlan2035 0 errdis port 0 992 0
41 vlan2036 0 errdis port 0 992 0
42 vlan2037 0 errdis port 0 992 0
43 vlan2038 0 errdis port 0 993 0
44 vlan2039 0 errdis port 0 993 0
45 vlan2040 0 errdis port 0 993 0
46 vlan2041 0 errdis port 0 993 0
47 vlan2042 0 errdis port 0 993 0
48 vlan2043 0 errdis port 0 993 0
49 vlan2044 0 errdis port 0 993 0
50 vlan2045 0 errdis port 0 993 0
51 vlan2046 0 errdis port 0 993 0
52 vlan2047 0 errdis port 0 993 0
53 vlan2048 0 errdis port 0 993 0
54 vlan2049 0 errdis port 0 993 0
55 vlan2050 0 errdis port 0 993 0
#show statistics
Port In Packets Out Packets In Errors Out Errors
1/1/1 9052 6555 0 0
1/1/2 0 0 0 0
1/1/3 231 224 0 0
1/1/4 0 0 0 0
1/1/5 0 0 0 0
1/1/6 0 0 0 0
1/1/7 0 0 0 0
1/1/8 0 0 0 0
1/1/9 0 0 0 0
1/1/10 0 0 0 0
1/1/11 0 0 0 0
1/1/12 0 0 0 0
1/1/13 0 0 0 0
1/1/14 0 0 0 0
1/1/15 0 0 0 0
1/1/16 0 0 0 0
1/1/17 0 0 0 0
1/1/18 0 0 0 0
1/1/19 0 0 0 0
1/1/20 0 0 0 0
1/1/21 0 0 0 0
1/1/22 0 0 0 0
1/1/23 0 0 0 0
1/1/24 0 0 0 0
1/2/1 0 0 0 0
1/2/2 0 0 0 0
1/2/3 0 0 0 0
1/2/4 0 0 0 0
1/2/5 0 0 0 0
1/2/6 0 0 0 0
1/2/7 0 0 0 0
1/2/8 0 0 0 0
1/2/9 0 0 0 0
1/2/10 0 0 0 0
1/3/1 0 0 0 0
1/3/2 0 0 0 0
1/3/3 0 0 0 0
1/3/4 0 0 0 0
1/3/5 0 0 0 0
1/3/6 0 0 0 0
1/3/7 0 0 0 0
1/3/8 0 0 0 0
mgmt1 0 0 0 0
TOTAL 9283 6779 0 0