Brocade ICX Series (cheap & powerful 10gbE/40gbE switching)

[infoMatt]

Thank you! adding a 330µF cap removed the whining noise.

Well, it's kind of a beefy one for sure I'm glad it worked for you... I'll have to source some random caps that I have lying around. Mine is even worse (excluding the rattling noise at boot, maybe it will go away when the fan is tighten to the case), because being it a PoE model it has two fans.

BTW, is that an 122K? Nice find!

 

[noise850]

I'm also having the same problem as noise850 with the switch stuck in high speed fan mode...There is also some kind of whining noise running in low. It may be present at high too just non audible when the fans are a bit louder.

This is it! This is exactly the problem I'm having with my 6450-48 non PoE. The sound is amplified much more once the case lid is on and that noise is maddening.

I wish I had thought about the cap mod, but I already ordered a Noctua A4x20 PWM (they were out of FLX and I didn't care I've spent more on fans than on the switch). So far the Noctua sounds perfect at high speed mode and is keeping the switch at 49 deg on Sensor A, 60 deg on Sensor B at the hottest part of the day. I'll have to keep watch on it but if these temps stay this way I'm fine with this setup. If not, I'll try putting a cap and the Sunon back in.

And if anyone else needs the info, on the Noctua PWM fan you swap the Black and Green wires. Yellow and Blue stay the same.

 

[hmw]

My ICX-6610-24PE arrived - one of the corners where the right hand PSU is - was dented. Does anyone know where to get replacement screws?

 

[hmw]

Following the Fohdeesha guide on post #1, the s/w version for the ICX-6610 is 08030t. I noticed on Ruckus the latest firmware is 08030u. Tried to look at release notes and it says

Enhancements in FastIron 08.0.30u
FastIron 08.0.30u release contains defect fixes. There are no enhancements in this release.

Anyone upgraded to 08.0.30u? Does it have any known bug fixes other than the HDHomeRun issue?

 

[hmw]

Upgraded both the ICX-6610-24PE and ICX-6610-48PE to 08.0.30u. Now waiting to grab some licenses from Da Man.

The switches came with two PSU Rev B for one switch and a Rev B and Rev C for the other switch. Was worried about getting Rev A, even the noise on the Rev B after they spin down - is quite loud

I get the following message after boot on one of the switches (tried swapping the PSUs and fan trays around - but only tried with one PSU at a time):

Power supply 1  detected in standby mode.

Power supply 2  detected.

Power supply 2  detected.
Power supply 2  is up.
PoE: Stack unit 1 Power supply 2  with 748000 mwatts capacity is up
PoE Info: Adding new 55V capacity of 748000 mW, total capacity is 748000, total free capacity is 748000
PoE Info: PoE module 1 of Unit 1 on ports 1/1/1 to 1/1/48 detected. Initializing....
PoE Event Trace Log Buffer for 2000 log entries allocated
PoE Event Trace Logging enabled...
lost arbitration, dev=50
i2c controller reset, dev=50
lost arbitration, dev=50
i2c controller reset, dev=50
lost arbitration, dev=50
i2c controller reset, dev=50
lost arbitration, dev=50
i2c controller reset, dev=50
lost arbitration, dev=50
i2c controller reset, dev=50
M:9 L:0 - PS EEPROM Offset Read: i2c cmd failed, i2c addr 0x50 error 4, ps 1
------------------------------------------------------------------
lost arbitration, dev=50
i2c controller reset, dev=50
PoE Info: PoE module 1 of Unit 1 initialization is done.

Is the "i2c cmd failed message" normal?

 

[infoMatt]

Is the "i2c cmd failed message" normal?

I'm not sure but I'd say no, that's not the expected behaviour. It seems it struggles to read the PoE module EEPROM; can you enable power and confirm it is powering up some PD?

 

[nthu9280]

Next step - it's finally time to pull the trigger on a rack cabinet...!

Below are some tips when you are in the market for a rack in US.
- if you live near a large metro area, setup alerts on craigslist. Full height 42u are more common than 24u and shorter.
- Also make sure it is full depth (1070mm) or close to it. (Speaking from experience )
- Square holes.

 

[Rand__]

- Also make sure it is full depth (1070mm) or close to it. (Speaking from experience )

Totally off topic, but recently got a full depth rack and actually couldn't fit any of my SM Rails in it
I have short and regular ones, but none have the required length

 

[ljvb]

Totally off topic, but recently got a full depth rack and actually couldn't fit any of my SM Rails in it
I have short and regular ones, but none have the required length

I have that problem with the rack I am trying to give away.. fits my SM crap (before I got rid of the SM stuff, but all the DL 360 and 380s are too long.

 

[deified]

Anyone have any "best practices" for the Brocade ICX6610 48p?
Here is a little about my setup;
Windows 10 machine with a MCX354A-FCBT --> Cisco QSFP-40G-SR-BD Compatible [fs.com brand] --> 15m om5 LC to LC --> Cisco QSFP-40G-SR-BD Compatible --> ICX6610 port 1/2/1.
Server 2019 with a MCX354A-FCBT --> Mellanox MC2207130-002 56gb/s DAC --> ICX6610 port 1/2/6
I get about 30-35 Gbps running 3 iperf3 tests at once.
I wasnt sure about enabling all ports poe, does this increase overall power consumption?
thanks for any helpful tips or tricks

 

[Schut]

I'm all set up with a 48 port POE ICX-6610, and I'm extremely pleased for the $150 shipped I paid to Ebay. I've thanked Fohdeesha privately, but I'll do so again here publicly. Many, many thanks.

Here's my question:

I have maybe 10 POE phones, 7 POE cameras (some external with IR), and 3 Unify POE wifi APs. Since this is my first layer 3 switch, I have yet to get VLANs working for all these devices, although I intend to, and when I do I expect I will segregate each class of port into its own bank on the switch.

In the meantime, is there any reason NOT to enable POE on all ports? Is this harder on the power section of the switch, even if I don't have all the ports loaded with POE devices? I notice the default from Brocade is to disable them, so I wonder if that is suggestive of anything.

 

[klui]

@hmw
Honestly the dented screw looks fine. Couldn't pliers be used to bend it back? Just put a piece of cloth between to keep it from getting scratched. Download the offical release notes to see closed defects and known issues. My 6610-48P spews out the same I2C errors when only one PSU is powered up and both are plugged in--the error would refer to the PSU that's not powered up. Power up both PSUs and they should go away--if not you have a problem.

@deified
The best practices depend on what you want your network to do. @fohdeesha gave you a good start with the guide for login credentials. Other things to think about would be enabling spanning tree, and DHCP snooping. If you want to go hardcore, consider port security, DoS protection, MAC authentication, TACACS, RADIUS, and disable all ports unless they're used.

@Schut
My recommendation is turn off PoE unless you know the port is connected to a device that uses it. I've found some devices can fool PoE negotiation on the 6610, but that was on old firmware. This practice falls in line with "only turn on services if you use them and disable by default." Power wise it shouldn't make any difference.

 

[hmw]

@hmw
Download the offical release notes to see closed defects and known issues.

Enhancements in FastIron 08.0.30u
FastIron 08.0.30u release contains defect fixes. There are no enhancements in this release.

Yeah downloaded them and that’s all that the official release notes say

updated anyways

 

[klui]

Yeah downloaded them and that’s all that the official release notes say updated anyways

Look again. I made the same mistake in the past. For a lot of enterprise release notes enhancements, fixes, and known issues are in separate sections. That entry you quoted is on page 6 (of 226). Scroll up 2 pages before that and you will see "Closed defects with code changes in Release 08.0.30u" on page 29 and "Known Issues in Release 08.0.30u" on page 34.

 

[hmw]

Look again. I made the same mistake in the past. For a lot of enterprise release notes enhancements, fixes, and known issues are in separate sections. That entry you quoted is on page 6 (of 226). Scroll up 2 pages before that and you will see "Closed defects with code changes in Release 08.0.30u" on page 29 and "Known Issues in Release 08.0.30u" on page 34.

Awesome - thanks, looked again and found the known issues and defects closed !

 

[Reece5646]

Good day all, new here, so my apologies if I’m posting in the wrong location ...

Question, after following these instructions, all went well, however the switch is now in router mode, and I can’t figure out for the life of me how to get it back to switch mode

Any help would be great !

 

[infoMatt]

I have that problem with the rack I am trying to give away.. fits my SM crap (before I got rid of the SM stuff, but all the DL 360 and 380s are too long.

Most of the times you can adjust the posts, moving them forward or backward untill you find a spot where all the rails align and can snap into the mounting holes. It's fine if the tail of the server is behind the rear post, if you need it.

Good day all, new here, so my apologies if I’m posting in the wrong location ...

Question, after following these instructions, all went well, however the switch is now in router mode, and I can’t figure out for the life of me how to get it back to switch mode

Any help would be great !

What do you mean? If you don't define any VE on a VLAN it will just act as a "pure" L2 device.

 

[Spearfoot]

Good day all, new here, so my apologies if I’m posting in the wrong location ...

Question, after following these instructions, all went well, however the switch is now in router mode, and I can’t figure out for the life of me how to get it back to switch mode

Any help would be great !

The CLI wizards here will probably scoff at my simple approach of using the Web administrative interface for doing this. But I'm pretty sure you can fix this by loading the Web GUI and insuring 'L2 Switching' is enabled on the General System Configuration page, and 'Route Only' is disabled on its 'Advanced Settings' page.

 

[Reece5646]

The CLI wizards here will probably scoff at my simple approach of using the Web administrative interface for doing this. But I'm pretty sure you can fix this by loading the Web GUI and insuring 'L2 Switching' is enabled on the General System Configuration page, and 'Route Only' is disabled on its 'Advanced Settings' page.View attachment 14544
View attachment 14545

THANK YOU !
That’s exactly what I was looking for and that was right in front of my face this entire time this is why I should not be doing this stuff at 4 o’clock in the morning lol

thank you a million !

I will definitely be testing this in a few hours when I get some motivation LOL

 

[Reece5646]

The CLI wizards here will probably scoff at my simple approach of using the Web administrative interface for doing this. But I'm pretty sure you can fix this by loading the Web GUI and insuring 'L2 Switching' is enabled on the General System Configuration page, and 'Route Only' is disabled on its 'Advanced Settings' page.View attachment 14544
View attachment 14545