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

[Vesalius]

how do sth members get the licensing to upgrade from sfp to sfp+ as mentioned in post#6?

By reading post#1 more carefully.

 

[Rain]

how do sth members get the licensing to upgrade from sfp to sfp+ as mentioned in post#6?

See @fohdeesha's documentation site, specifically the "Brocade Fun > ... Licensing" section relevant to your switch. Fohdeesha Docs

 

[brb78]

See @fohdeesha's documentation site, specifically the "Brocade Fun > ... Licensing" section relevant to your switch. Fohdeesha Docs

missed that hyperlink, thanks!

 

[Drewy]

Currently, 08.0.95f.

I have not. I figured since this is likely far from a supported mode of operation (stacking with BASE-T adapters) they wouldn't provide much help. There's also this thread (link) where they indicate stacking on their own 10G RJ45 transceivers isn't even supported. I may give it a shot though, I suppose.

i’d forget it and save being laughed at. If they don’t support their own transceivers they are not going to support someone else’s. They actually say in that post fibre or dacs.

 

[Wolfcastle]

Update: received a scavenged PoE board for my ICX 6610 from the eBay seller. PoE is now up and running though RJ45 ports 1-4 are still dead (as expected).

 

[linuxsrc]

have just picked up a couple of icx6610s and I am trying to get the console serial port set to 115200, and what I did for the 6650 does not work.

Setting this in the u-boot on the 6650 I used

setenv baudrate 115200

On the 6610s there is nothing. I read that others just used buadrate, as they are not u-boot

Where does one change the baud rate for the serial console on these?

Thanks in advance.

 

[Phlesh]

Having some trouble now that I've introduced a VLAN into my 6610 switch and hoping somebody can help me figure out what I've done wrong.

I have a VLAN 8 and a VLAN 1 (default). The VLAN 1 I've given an IP of 10.200.1.5/30 (so, just two IP's usable, intentionally so). The VLAN 8 I've given an IP of 10.111.8.1/24.

I have two devices on untagged ports, one on each VLAN:

• Device 1 on VLAN 1: 10.200.1.6 (gateway 10.200.1.5)
• Device 2 on VLAN 8: 10.111.8.10 (gateway 10.111.8.1)

Each device can ping the switch at any of its IP's (10.111.8.1, 10.200.1.5, etc.). But neither device can ping the other.

My understanding is that routes were default "on" for all VLAN's on the switch, unless ACL's are created to prevent cross-talk. I have no ACL's or really any other configuration in place that I know about that would be preventing this from working. What should I check?

 

[kapone]

Having some trouble now that I've introduced a VLAN into my 6610 switch and hoping somebody can help me figure out what I've done wrong.

I have a VLAN 8 and a VLAN 1 (default). The VLAN 1 I've given an IP of 10.200.1.5/30 (so, just two IP's usable, intentionally so). The VLAN 8 I've given an IP of 10.111.8.1/24.

I have two devices on untagged ports, one on each VLAN:

• Device 1 on VLAN 1: 10.200.1.6 (gateway 10.200.1.5)
• Device 2 on VLAN 8: 10.111.8.10 (gateway 10.111.8.1)

Each device can ping the switch at any of its IP's (10.111.8.1, 10.200.1.5, etc.). But neither device can ping the other.

My understanding is that routes were default "on" for all VLAN's on the switch, unless ACL's are created to prevent cross-talk. I have no ACL's or really any other configuration in place that I know about that would be preventing this from working. What should I check?

Check if your devices (I'm looking at you....Windows....) have firewall/policy/rules preventing a ping response?

 

[Phlesh]

@kapone Fairly certain that is not the case. One of these devices is my OSX laptop that I've used for a ton of debugging and pinging from, and the other is a OPNsense machine that is definitely responsive to pings because I've gotten it to respond to pings in the past. Also, the switch itself can ping all of these devices using the built-in ping tool.

 

[kapone]

@kapone Fairly certain that is not the case. One of these devices is my OSX laptop that I've used for a ton of debugging and pinging from, and the other is a OPNsense machine that is definitely responsive to pings because I've gotten it to respond to pings in the past. Also, the switch itself can ping all of these devices using the built-in ping tool.

That's...weird.

Routes ARE default ON for VLANs in the 6610, I've never seen it not be on by default. A few suggestions/things to try, possibly?

- Instead of VLAN1, move that device to a different VLAN, eliminating any "default VLAN" issues. Test
- Factory reset the 6610 and try again?
- Instead of a /30 on that VLAN, try /24 just for shits and giggles.

 

[Phlesh]

@kapone I'll try anything at this point!

I've got a VLAN 16 and a VLAN 32 now. Same setup -- x.x.[32/16].10 IP's for two different devices, one on each subnet. Neither can ping the other at this moment.

Anything else I can check? Is there a way I could have inadvertently disabled inter-VLAN routing?

 

[Phlesh]

Another question, might help me debug: is there any way from the serial port to watch some of the packets going to/from a given IP, and provide some info on what switching decisions are being made for each packet?

 

[kapone]

Do a "sh run" and paste the output.

 

[fohdeesha]

have just picked up a couple of icx6610s and I am trying to get the console serial port set to 115200, and what I did for the 6650 does not work.

Setting this in the u-boot on the 6650 I used

On the 6610s there is nothing. I read that others just used buadrate, as they are not u-boot

Where does one change the baud rate for the serial console on these?

Thanks in advance.

setenv is for the u-boot based switches, the 6610 runs brocades custom bootloader not based on u-boot. I can't remember if I ever found it on those. I thought I remember it being something under the "set" command in the bootloader but not seeing it there right off the bat, could be hidden

 

[fohdeesha]

updating some stuff for a colo customer I set up ages ago and think I found a record for their setup, ICX6610 with zero issues:

STACKID 1  system uptime is 1102 day(s) 18 hour(s) 55 minute(s) 33 second(s)
The system started at 02:03:04 GMT-05 Sat Jan 26 2019

 

[tinfoil3d]

There's no ECC onboard right? I mean, a lot of things can happen in 3 years but since it only has something like 64 or 128mb chances of bitflip in a critical area isnt that high either i guess

 

[fohdeesha]

There's no ECC onboard right? I mean, a lot of things can happen in 3 years but since it only has something like 64 or 128mb chances of bitflip in a critical area isnt that high either i guess

the memory in these switches is ECC, 512MB PC2-5300 Reg ECC specifically in the case of the 6610 - with 64 or 128mb they wouldn't even be able to uncompress the OS image into RAM during boot

 

[tinfoil3d]

that explains a lot. but to tell you the truth i have raspi and even desktop computers running for way longer than that and still doing fine. no ecc whatsoever

 

[linuxsrc]

setenv is for the u-boot based switches, the 6610 runs brocades custom bootloader not based on u-boot. I can't remember if I ever found it on those. I thought I remember it being something under the "set" command in the bootloader but not seeing it there right off the bat, could be hidden

Monitor>set ?
debug-task Debug task
sample-rate Sample task
sample-task Sample task
ether-address Configure Ethernet address

Nothing here that seems to make you think you can change the rate
This is why I am confused, I tried this with expecting it to be similar to what the 7xxx versions did.

Monitor>set baudrate 115200
Syntax error, 'baudrate'

Thinking like you, I tried it just in case it was hidden.

Strange how, nothing points to baud rate being able to be changed, even in the official docs. Brocade seems to never mention it, and I have spent a bit of time combing through them to find any mention of baud rate outside, use 9600 blah blah blah, to connect to the console.

 

[fohdeesha]

Nothing here that seems to make you think you can change the rate
This is why I am confused, I tried this with expecting it to be similar to what the 7xxx versions did.



Thinking like you, I tried it just in case it was hidden.

Strange how, nothing points to baud rate being able to be changed, even in the official docs. Brocade seems to never mention it, and I have spent a bit of time combing through them to find any mention of baud rate outside, use 9600 blah blah blah, to connect to the console.

it's entirely possible it's hardcoded to 9600 baud on the old powerPC custom bootloaders, they're pretty basic. Is there a specific reason you need to increase it?