I see no reason why not. As far as I can tell, the fans are the same, but the jumper layout is slightly different to tell the switch which direction the fans are installed (you don't want intake and exhaust fans on the same face). As long as you do all the fans the same way, the switch won't tell the difference. JUST MAKE SURE you have all intake/exhaust the same way.
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.
If I remember correctly, this has been attempted an concluded that the cables are too short and you'd have to solder.
But yes, very annoying that the PoE versions only seem to exist as -E versions. Probably because PoE access switches are usually located in separate network cabinets where everything is on the front, whereas the ones with -I airflow for datacenter are always non-PoE
But yes, very annoying that the PoE versions only seem to exist as -E versions. Probably because PoE access switches are usually located in separate network cabinets where everything is on the front, whereas the ones with -I airflow for datacenter are always non-PoE
Offtopic, but kinda still relevant for many users: nvidia released the v12.28.2302 firmware for cx-4 cards 
It's not showing up via mlxup, but it's avaialble via direct & manual updates.
Ethernet: Firmware for ConnectX®-4 EN
Infiniband/VPI: Firmware for ConnectX®-4 IB/VPI
It's not showing up via mlxup, but it's avaialble via direct & manual updates.
Ethernet: Firmware for ConnectX®-4 EN
Infiniband/VPI: Firmware for ConnectX®-4 IB/VPI
I don’t need PoE version, but -I version is (at least in EU) hard to find cheap. I read that intake switches are louder because fans have more rpm’s. Can I manually adjust that in config? And what I’d like to know the most, is there any physical difference between inlet and exhaust version in parts positioning? I believe in PSU that can have significant impact on airflow. Is there anyone willing to make photos of -I version of PSU and fan?
Most likely. In -E mode, air is being pulled from the entire width of the switch, albeit small holes that span across. In -I mode, air is entering only via fans...and if you don't use both fans/fan trays and both PSUs, you're limiting it. That'll lead to a warmer switch, i.e. higher RPMs.
No. None. Zilch. Nada.
Part numbers are different but the hardware bits are identical.
Yes and No. Like I said, pull vs push...has different flow dynamics.
It would be interesting to compare temperature of exhaust installed on the back side of the rack compared to inlet installed same way. I wonder if it's even worth it, I believe inlet switch will have still higher temperature than exhaust one.
Maybe I buy both just for fun
Ya and maybe they might talk me through a bit of it. I like the subject matter however it is different from my profession which is technical but completely unrelated. It's just sourcing such a person.
Hi everyone! I've had a 6610-48p for about 1.5 years and it's been great. However, after unplugging it yesterday to move it (at that point it was running continuously for 2-3 months I would guess), it's become stuck in a boot loop. It won't even go into the boot monitor when pressing 'b', however it does register the key press. The serial output is in the attachments. From what I've seen around this thread, it seems that the cksum '71f1' is correct, but it errors out on the next part. Googling didn't get me very far. Only other similar trace I've seen is here:
https://forums.servethehome.com/ind...powerful-10gbe-40gbe-switching.21107/page-354
I would assume something is wrong with the flash, but I also attached a memory test that errors out. I don't know if that is normal. Could someone confirm? Any other ideas would be appreciated. Thanks a lot!
https://forums.servethehome.com/ind...powerful-10gbe-40gbe-switching.21107/page-354
I would assume something is wrong with the flash, but I also attached a memory test that errors out. I don't know if that is normal. Could someone confirm? Any other ideas would be appreciated. Thanks a lot!
Last edited:
doesn't look normal, if you want u can buy ram and swap it in: Centon Lot of 2 RD703G01 2GB PC2-5300 Reg ECC CL5 DDR2 667Mhz 1 Rank SODIMM 6-2 | eBay
Thanks for the feedback. I just think it's a little weird for the ram to have gone bad since the switch has been running fine until it was restarted. But who knows...I guess I'll replace the ram. In the meantime, I'll try to see if I can dump the contents of the flash. How hard could it be to turn an RPi into a JTAG debugger.....or maybe desolder the flash and talk to it directly (I have an STM32 board around, maybe it has enough pins). I'll be back with updates.
Okay, so I found a replacement ram module locally for like $8 and I actually can't believe it fixed it. I'm somewhat astonished it ran fine for so long with crapped out ram, but I guess it never rebooted because of the UPS and the switching ASICs chugged along. Well, I guess that's that. Thanks a lot and see you all again when something else breaks.
Got some ICX-6450's and trying to wrap my head around setup.
VLANs are 10, 20, 30. Do I create a router-interface (interface ve 10, ve 20, ve 30) for each VLAN with an ip address within that subnet?
I plan on using fiber 1/2/2 port to tag each of the VLANs. This is what I would consider the trunk or uplink port that the DHCP server is going to plug into.
I plan on having all services such as printers, wireless access points, etc on VLAN 10. Within vlan 10 I plan on untagging the appropriate ethernet ports (1/1/5, 1/1/6, 1/1/7, etc). This works fine and I get a vlan 10 IP address when plugged into one of these ports. However, I am going to use Ruckus Unleashed APs and I can setup SSID's to use particular VLANs. How would I go about doing this on the ICX 6450? For example, let's say that I have a R710 plugged into 1/1/5. Right now within vlan 10 I have untagged ethe 1/1/5 and the R710 gets a vlan 10 IP address. However, I cannot go into vlan 20 and vlan 30 and untag ethe 1/1/5 so how do I go about doing this? When a user connects into SSID "test-vlan10" they should be within the vlan 10 subnet, if they connect into SSID "test-vlan20" they should be contained within the vlan 20 subject, etc. I'm curious CLI-wise but more so conceptually what needs to happen so I can understand L3 better.
VLANs are 10, 20, 30. Do I create a router-interface (interface ve 10, ve 20, ve 30) for each VLAN with an ip address within that subnet?
I plan on using fiber 1/2/2 port to tag each of the VLANs. This is what I would consider the trunk or uplink port that the DHCP server is going to plug into.
I plan on having all services such as printers, wireless access points, etc on VLAN 10. Within vlan 10 I plan on untagging the appropriate ethernet ports (1/1/5, 1/1/6, 1/1/7, etc). This works fine and I get a vlan 10 IP address when plugged into one of these ports. However, I am going to use Ruckus Unleashed APs and I can setup SSID's to use particular VLANs. How would I go about doing this on the ICX 6450? For example, let's say that I have a R710 plugged into 1/1/5. Right now within vlan 10 I have untagged ethe 1/1/5 and the R710 gets a vlan 10 IP address. However, I cannot go into vlan 20 and vlan 30 and untag ethe 1/1/5 so how do I go about doing this? When a user connects into SSID "test-vlan10" they should be within the vlan 10 subnet, if they connect into SSID "test-vlan20" they should be contained within the vlan 20 subject, etc. I'm curious CLI-wise but more so conceptually what needs to happen so I can understand L3 better.
I'm much more surprised you were able to find such niche ram locally that fast lmaoOkay, so I found a replacement ram module locally for like $8 and I actually can't believe it fixed it. I'm somewhat astonished it ran fine for so long with crapped out ram, but I guess it never rebooted because of the UPS and the switching ASICs chugged along. Well, I guess that's that. Thanks a lot and see you all again when something else breaks.
(and for future readers, it doesn't need to be 2GB - stock is 512MB, which is even harder to find, but it can be bigger than this. so any DDR2 ECC PC2-5300 512MB and up will work - the OS will ignore anything above 512mb)
Wouldn’t you need atleast one to be able to access fastiron without using console cable?
Any downside to having a router interface on each vlan setup on the ICX?
yes sorry i use the management interface you would need a ve for the network vlan that you want the switch to answer or all of them. Since your gatteway is your router interface i am guessing you should be fine.
I seem to be running the 'show running' command frequently as I make changes and try to understand the changes I've made and compare to previous running config along with what the switch does differently now. I copy and paste this into a notepad.
I was thinking, it seems that I could setup a switch much more efficiently in notepad and then copying and pasting the new config over to the ICX.
I realize that there is some TFTP type methods of backing up and importing in a config file but is there a way to do it without TFTP? Such as editing a single file, pasting all of the config items, saving file and then loading the file all on the switch?
It seems very inefficient in many repetitious with small differences such as naming interface ports. Going into the interface port, then naming it, then going to a different interface port, naming it, etc. Seems easier to do it all in a spreadsheet and then copy and paste into notepad and then just copy and paste them all at once into the config.
I was thinking, it seems that I could setup a switch much more efficiently in notepad and then copying and pasting the new config over to the ICX.
I realize that there is some TFTP type methods of backing up and importing in a config file but is there a way to do it without TFTP? Such as editing a single file, pasting all of the config items, saving file and then loading the file all on the switch?
It seems very inefficient in many repetitious with small differences such as naming interface ports. Going into the interface port, then naming it, then going to a different interface port, naming it, etc. Seems easier to do it all in a spreadsheet and then copy and paste into notepad and then just copy and paste them all at once into the config.
There is no built-in method to do anything except upload an entire configuration file, with all of the commands necessary to build the desired configuration. If you want to organize and edit the configuration data using a different format, you'll have to consider other tools like netconf.
That would not be the optimal way to do it. Most commands "cascade". For e.g.
Code:
interface eth 1/1/10 name XXX
interface eth 1/1/11 name XXXOn my Mellanox switches (the Brocade CLI is similar), I can issue almost all config commands just from the prompt. Just a snippet.
Code:
vlan 3
vlan 20
vlan 100
vlan 200
vlan 300
vlan 400
vlan 665
interface ethernet 1/2 switchport access vlan 3
interface ethernet 1/3 switchport access vlan 3
interface ethernet 1/4/3 switchport access vlan 665
interface ethernet 1/9 switchport hybrid allowed-vlan all
interface ethernet 1/10 switchport hybrid allowed-vlan all
interface ethernet 1/19 switchport hybrid allowed-vlan all
interface ethernet 1/20 switchport hybrid allowed-vlan all
interface ethernet 1/21 switchport access vlan 200
interface ethernet 1/22 switchport access vlan 100
interface ethernet 1/23 switchport access vlan 200
interface ethernet 1/24 switchport access vlan 100
interface ethernet 1/25 switchport access vlan 200
interface ethernet 1/26 switchport access vlan 100
interface ethernet 1/27 switchport access vlan 200
interface ethernet 1/28 switchport access vlan 100
interface ethernet 1/29 switchport access vlan 200
interface ethernet 1/30 switchport access vlan 100
interface ethernet 1/31 switchport access vlan 200
interface ethernet 1/32 switchport access vlan 100
interface ethernet 1/33 switchport access vlan 200
interface ethernet 1/34 switchport access vlan 100
interface ethernet 1/35 switchport access vlan 200
interface ethernet 1/36 switchport access vlan 100
interface port-channel 1 switchport hybrid allowed-vlan all
vlan 3 name "INFRA"
vlan 20 name "HOMELAN"
vlan 100 name "PROD_ETH"
vlan 200 name "PROD_ISCSI"
vlan 300 name "DEV_ETH"
vlan 400 name "DEV_ISCSI"
vlan 665 name "TRANSIT"