Drag to reposition cover

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

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

BackupProphet

Well-Known Member
Jul 2, 2014
1,083
640
113
Stavanger, Norway
olavgg.com
I have the 6450-24p and for me, the switch is very quiet; and uses about 30-35watts. A friend was asking about the 6610-48p. Hard question to answer, but "now many times louder is the 6610-48p vs the 6450 "?
I am testing my units tonight, received 4 units of the 6450. The 6610 is a lot louder, but the 6450 makes a vibrating sound. I think I need to replace the fan, then it should be super quiet.
 

tommybackeast

Active Member
Jun 10, 2018
286
105
43
Damn, tried a Delta fan, with similar specs, but the fan wouldn't start. The wires are green and yellow, which is unusal. I guess the middle pin is what should be supplying power?
I cannot comment to that at all, merely as FYI, my own 6450-24p which frankly was in mint shape inside and out when i got it (not even rack rash); running 2 10GB ports, 14 1GB, and no PoE is silly quiet. When I opened it up expecting to need to clean out some dust bunnies; it was spotless.
 

BackupProphet

Well-Known Member
Jul 2, 2014
1,083
640
113
Stavanger, Norway
olavgg.com
It's not standard, I compared with my other "standard" fans, I had to reverse the order. The Delta belonged to another switch I had that died, which had another non standard order. No big deal deal, but it is annoying.
 

Myth

Member
Feb 27, 2018
148
7
18
Los Angeles
stack of two ICX6610's, then you can connect important hosts to both switches via LACP, so you can lose a switch and not notice
Oh wow of course LACP across multiple switches, amazing! That's going to take some research on how to set that up.

We have three servers, each with 2x ports 40GigE. So how would it work to connect each server via 2x 40GigE ports. I guess one 40GigE line per switch. Would I then connect the two switches together using a 1GigE line?
 

kapone

Well-Known Member
May 23, 2015
1,095
642
113
Oh wow of course LACP across multiple switches, amazing! That's going to take some research on how to set that up.

We have three servers, each with 2x ports 40GigE. So how would it work to connect each server via 2x 40GigE ports. I guess one 40GigE line per switch. Would I then connect the two switches together using a 1GigE line?
No.

You connect each switch to your router on a different interface. That way each switch is its own LAN segment (with potential VLANs downstream). Your servers now have two paths to get to the router, if one of them fails, there's still one path available (The LACP link will still be up).

Edit: Actually, there's many ways to do this. This may or may not be the right/optimal way to do it, depending on what you're trying to achieve.
 

fohdeesha

Kaini Industries
Nov 20, 2016
2,727
3,075
113
33
fohdeesha.com
No I mean literally stack the switches (use the stacking commands/code to make them become one logical switch), then each server/host would have a LACP connection of two links, one landing on each switch chassis. Then you can rip the power cord out of a switch, and thanks to the hitless stacking failover, the remaining switch will take over, that LACP link will become the one left active, and servers will not notice even a temporary traffic drop, it's hitless.

This is what I do at home and in colo, every important link (transit uplink, virt hosts, storage etc) lands on 2 switches in a stack, so I'm not tied to one switch. Keep in mind @Myth that the ICX6610 only has 2x 40gbE ports, and if you stack them, you should use at least one of the 40gbE ports per switch to do it, so you'll be left with 2x free 40gbE ports in a stack. That's enough to LACP to a storage host or something, but the rest of the hosts etc will have to use 10gbE ports as you've ran out of 40gbE. If you need high density 40gbE Arista 7050qx is the way to go
 
  • Like
Reactions: D4M4EVER and Matt G

jmacsob

New Member
Mar 18, 2017
8
1
3
42
So I was poking around inside my switch and I accidentally shorted something out and now my 6450-24 appears to be dead, it's unable to see the ethernet ports or any of the hardware it seems.
Code:
 I2C Dev 0x24, Register 03 Initial Fail
FAIL!
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
Unable to select to bank 0 of HWM
mvEgigaEnvMacGet: Wrong MAC (<NULL>).
mvEgigaLoad: mvEgigaEnvMacGet failed.
mv_eth_init: mvEgigaLoad() failed.
No ethernet found.
Enter 'b' to stop at boot monitor:  1

Bootloader Version: 10.1.05T310 (Mar 19 2015 - 16:39:59)

Bootloader Version: 10.1.05T310 (Mar 19 2015 - 16:39:59)TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Unable to read IO Expander 27 Register 1
ioexp_read fail
Error while reading Base MAC from EEPROM



TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Unable to read CPLD revision
Model ID: 1.0.0.0.0.1
assembly error, wrong PoE card installed

 I2C Dev 0x20, Register 06 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x20, Register 07 Initial Fail
 I2C Dev 0x24, Register 06 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x24, Register 07 Initial Fail
 I2C Dev 0x20, Register 02 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x20, Register 03 Initial Fail
 I2C Dev 0x24, Register 02 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x24, Register 03 Initial Fail
FAIL!
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
Unable to select to bank 0 of HWM
mvEgigaEnvMacGet: Wrong MAC (<NULL>).
mvEgigaLoad: mvEgigaEnvMacGet failed.
mv_eth_init: mvEgigaLoad() failed.
No ethernet found.
Enter 'b' to stop at boot monitor:  0
bootdelay: ===
Booting image from Primary
## Booting image at 00007fc0 ...
   Created:      2015-04-22  22:31:19 UTC
   Data Size:    8393876 Bytes =  8 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel in BE mode ...
Uncompressing Image................................................................................................................................................................................................................................................................................................................................................................. done, booting the kernel.


Bootloader Version: 10.1.05T310 (Mar 19 2015 - 16:39:59)TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Unable to read IO Expander 27 Register 1
ioexp_read fail
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Error while reading Base MAC from EEPROM



TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Unable to read CPLD revision
Model ID: 1.0.0.0.0.1
assembly error, wrong PoE card installed
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x20, Register 06 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x20, Register 07 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x24, Register 06 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x24, Register 07 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x20, Register 02 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x20, Register 03 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x24, Register 02 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x24, Register 03 Initial Fail
FAIL!
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
Unable to select to bank 0 of HWM
mvEgigaEnvMacGet: Wrong MAC (<NULL>).
mvEgigaLoad: mvEgigaEnvMacGet failed.
mv_eth_init: mvEgigaLoad() failed.
No ethernet found.
Enter 'b' to stop at boot monitor:  0
bootdelay: ===
Booting image from Primary
## Booting image at 00007fc0 ...
   Created:      2015-04-22  22:31:19 UTC
   Data Size:    8393876 Bytes =  8 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel in BE mode ...
Uncompressing Image................................................................................................................................................................................................................................................................................................................................................................. done, booting the kernel.
Config partition mounted.
Creating TUN device
Starting the FastIron.
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 1
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 2
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 3
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 4
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 5
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 6
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Failed to read ext id from CPLD!

I2C Bus Error !!
Please remove ALL faulty SFPs and power cycle if the switch doesn't recover.

Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system reboot
Restarting system.


Bootloader Version: 10.1.05T310 (Mar 19 2015 - 16:39:59)TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Unable to read IO Expander 27 Register 1
ioexp_read fail
Error while reading Base MAC from EEPROM



TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Unable to read CPLD revision
Model ID: 1.0.0.0.0.1
assembly error, wrong PoE card installed

 I2C Dev 0x20, Register 06 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x20, Register 07 Initial Fail
 I2C Dev 0x24, Register 06 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x24, Register 07 Initial Fail
 I2C Dev 0x20, Register 02 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x20, Register 03 Initial Fail
 I2C Dev 0x24, Register 02 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x24, Register 03 Initial Fail
FAIL!
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
Unable to select to bank 0 of HWM
mvEgigaEnvMacGet: Wrong MAC (<NULL>).
mvEgigaLoad: mvEgigaEnvMacGet failed.
mv_eth_init: mvEgigaLoad() failed.
No ethernet found.
Enter 'b' to stop at boot monitor:  0
bootdelay: ===
Booting image from Primary
## Booting image at 00007fc0 ...
   Created:      2015-04-22  22:31:19 UTC
   Data Size:    8393876 Bytes =  8 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel in BE mode ...
Uncompressing Image................................................................................................................................................................................................................................................................................................................................................................. done, booting the kernel.
Config partition mounted.
Creating TUN device
Starting the FastIron.
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 1
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 2
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 3
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 4
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 5
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 6
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Failed to read ext id from CPLD!

I2C Bus Error !!
Please remove ALL faulty SFPs and power cycle if the switch doesn't recover.

Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system reboot
Restarting system.


Bootloader Version: 10.1.05T310 (Mar 19 2015 - 16:39:59)TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Unable to read IO Expander 27 Register 1
ioexp_read fail
Error while reading Base MAC from EEPROM



TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Unable to read CPLD revision
Model ID: 1.0.0.0.1.1

 I2C Dev 0x20, Register 06 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x20, Register 07 Initial Fail
 I2C Dev 0x24, Register 06 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x24, Register 07 Initial Fail
 I2C Dev 0x20, Register 02 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x20, Register 03 Initial Fail
 I2C Dev 0x24, Register 02 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x24, Register 03 Initial Fail
FAIL!
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
Unable to select to bank 0 of HWM
mvEgigaEnvMacGet: Wrong MAC (<NULL>).
mvEgigaLoad: mvEgigaEnvMacGet failed.
mv_eth_init: mvEgigaLoad() failed.
No ethernet found.
Enter 'b' to stop at boot monitor:  0
bootdelay: ===
Booting image from Primary
## Booting image at 00007fc0 ...
   Created:      2015-04-22  22:31:19 UTC
   Data Size:    8393876 Bytes =  8 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel in BE mode ...
Uncompressing Image................................................................................................................................................................................................................................................................................................................................................................. done, booting the kernel.
Config partition mounted.
Creating TUN device
Starting the FastIron.
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 1
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 2
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 3
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 4
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 5
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 6
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Failed to read ext id from CPLD!

I2C Bus Error !!
Please remove ALL faulty SFPs and power cycle if the switch doesn't recover.

Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system reboot
Restarting system.


Bootloader Version: 10.1.05T310 (Mar 19 2015 - 16:39:59)TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Unable to read IO Expander 27 Register 1
ioexp_read fail
Error while reading Base MAC from EEPROM



TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Unable to read CPLD revision
Model ID: 1.0.0.1.1.1

 I2C Dev 0x20, Register 06 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x20, Register 07 Initial Fail
 I2C Dev 0x24, Register 06 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x24, Register 07 Initial Fail
 I2C Dev 0x20, Register 02 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x20, Register 03 Initial Fail
 I2C Dev 0x24, Register 02 Initial FailTWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail

 I2C Dev 0x24, Register 03 Initial Fail
FAIL!
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
TWSI: mvTwsiRead: 940: mvTwsiStopBitSet fail
Read hw monitor register value fail
Unable to configure hw monitor
Unable to select to bank 0 of HWM
mvEgigaEnvMacGet: Wrong MAC (<NULL>).
mvEgigaLoad: mvEgigaEnvMacGet failed.
mv_eth_init: mvEgigaLoad() failed.
No ethernet found.
Enter 'b' to stop at boot monitor:  0
bootdelay: ===
Booting image from Primary
## Booting image at 00007fc0 ...
   Created:      2015-04-22  22:31:19 UTC
   Data Size:    8393876 Bytes =  8 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel in BE mode ...
Uncompressing Image................................................................................................................................................................................................................................................................................................................................................................. done, booting the kernel.
Config partition mounted.
Creating TUN device
Starting the FastIron.
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 1
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 2
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 3
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 4
Error: I2C access failed for device 0x27, command -1071879421, I2C code = 0x1, SIM Code = 14, TWSI Sts = 0xf8
Retrying read of extended board-id, retry count: 5
I'm unable to interrupt the boot process and not sure if there is anything else I can try before writing this one off. Anyone seen this before?
 

fohdeesha

Kaini Industries
Nov 20, 2016
2,727
3,075
113
33
fohdeesha.com
looks like you fried something on the i2c bus and it took the whole bus out, pretty much a write off

There's a 1% chance it's a short or damage on the LED/reset daughterboard (it has a couple i2c multiplexers), you can try unplugging it from the mainboard and booting again. this board: https://i.imgur.com/W31ceGX.jpg

I really doubt that's where the damage is (unless that's where you were poking around), but worth a try before throwing it away
 

jmacsob

New Member
Mar 18, 2017
8
1
3
42
Thanks, yeah I wasn't anywhere near the daughterboard. I thought I had shorted the fan pins on the empty fan header but, it's possible I may have accidentally touched something else.
 

arglebargle

H̸̖̅ȩ̸̐l̷̦͋l̴̰̈ỏ̶̱ ̸̢͋W̵͖̌ò̴͚r̴͇̀l̵̼͗d̷͕̈
Jul 15, 2018
657
244
43
Kind of an off the wall question here: Can the icx6xxx series handle per-vlan MTU without any major disruption? I don't actually need it but I'd like the option to chuck storage packets around at 9k MTU and traditional traffic at 1500. I think I googled this last week and the answer wasn't completely clear.

I'm going to play around with my switches today and I'll probably have a chance to test this out but if anyone can confirm for me that'd be great too.
 

arglebargle

H̸̖̅ȩ̸̐l̷̦͋l̴̰̈ỏ̶̱ ̸̢͋W̵͖̌ò̴͚r̴͇̀l̵̼͗d̷͕̈
Jul 15, 2018
657
244
43
I would just keep MTU at 1500, you get lower latency which is much more important than throughput.
Yeah, I've actually run tests with MTU set at 9000 vs 1500 and iperf/smb throughput was about 3x faster at the non-Jumbo size. I'm more curious if it's possible than anything else.
 

fohdeesha

Kaini Industries
Nov 20, 2016
2,727
3,075
113
33
fohdeesha.com
Kind of an off the wall question here: Can the icx6xxx series handle per-vlan MTU without any major disruption? I don't actually need it but I'd like the option to chuck storage packets around at 9k MTU and traditional traffic at 1500. I think I googled this last week and the answer wasn't completely clear.

I'm going to play around with my switches today and I'll probably have a chance to test this out but if anyone can confirm for me that'd be great too.

yup no problem, however obviously if something from the storage network needs to get routed to another vlan with default MTU, and the devices don't properly support PMTU discovery (which is surprisingly a lot of stuff) it's going to have to be fragmented, which is bad news

look on page 46 of fastiron-08030mb-l3guide.pdf for details. You would just run the MTU command on the VE interface for each vlan instead of the physical port. If the storage vlan doesn't have a VE (eg no routing) just run it on the ports for storage stuff

fragmentation is disabled by default (it will drop packets that would otherwise require fragmentation, because it's so slow). If you want it to fragment packets between VLAN's when the host doesn't support PMTUD and is trying to send 9k packets to a 1.5k vlan, you need to run "mtu-exceed forward global"
 
Last edited:
  • Like
Reactions: arglebargle

miked1

New Member
Mar 15, 2017
8
0
1
55
Do the ears of a 6450-48P (or a -24P) allow for vertically wall mounting the switch?