Damn this ICX7650 is LOUD. My Apple watch shows 63dB ~ 70 dB when near the switch. It was new in box but came with two Rev A PSUs ! On the other hand, I have like 3 Rev C and one Rev B RPS-16 PSU so it's not a problem.I will make sure to report.
Weird... I assumed that Rev B and Rev C superseded Rev A and no Rev A are produced anymore. Can't imagine that they're shipping new ICX7650 with years old Rev A PSUsIt was new in box but came with two Rev A PSUs !
weird mine doesn't sound any louder than my icx6610-48p. I should check what psu's are in mine.Damn this ICX7650 is LOUD. My Apple watch shows 63dB ~ 70 dB when near the switch. It was new in box but came with two Rev A PSUs ! On the other hand, I have like 3 Rev C and one Rev B RPS-16 PSU so it's not a problem.
Yeah I'd love to hear back. I am pondering buying one, but I don't want something that's louder than my 6610, that's already on the edge of being too loud for my liking.weird mine doesn't sound any louder than my icx6610-48p. I should check what psu's are in mine.
Would it be possible to take readings for both switches with an iPhone and a SPL app like Decibel X for example? I'll try doing the same ...weird mine doesn't sound any louder than my icx6610-48p. I should check what psu's are in mine.
It's odd that your AP ports are showing "N/A" for PVID.I'll check that out now. The default VLAN is 1, however, I'd prefer it to be 50, since that's my physical hardware management subnet. Since the AP's management is on VLAN 1, I keep reading that its native on all ports automatically, and I can't set VLAN 1 as untagged to any interfaces. I suppose if I re-IP my APs to be on VLAN 50, it should work... That said, as shown below, the link for ve 1 is showing as Down, and I can't figure out how to get that to change it's link state to Up.
Code:VII-SW48P01(config)#show vlan Total PORT-VLAN entries: 7 Maximum PORT-VLAN entries: 64 [CODE]VII-SW48P01(config)#sh int brief wide Port Link State Dupl Speed Trunk Tag Pvid Pri MAC Name 1/1/1 Down None None None None Yes N/A 0 748e.f8d3.c340 Wireless AP First Floor 1/1/2 Up Forward Full 1G None Yes N/A 0 748e.f8d3.c341 Wireless AP Second Floor 1/1/3 Down None None None None No 1 0 748e.f8d3.c340 ve50 Up N/A N/A N/A None N/A N/A N/A 748e.f8d3.c340
Well TIL... I had no idea there was a difference in that firmware I don't recall seeing anything in the Fohdeesha docs about that. I have pfsense handling routing, nothing doing that/ACLs on the Brocade. I'll offload some layer 3 to the Aristas once I get those up.It's odd that your AP ports are showing "N/A" for PVID.
But I think these issues may be because the Brocade is running the router firmware. What is supposed to be doing the routing? Do you have any ACLs in this topology? If so, what switch is doing that? If it's the Ubiquiti (you said they were cores earlier), then I would run the switch firmware on the Brocade. You don't want "ve" interfaces on both as that will cause issues with routing, oddly enough even if you have "ve 50" on the Ubiquiti and "ve 50" on the Brocade. Ultimately, if VLAN 50 is to be the management VLAN, you'd be looking at implementing something like:
Ubiquiti:
Brocade:
- Management IP on VLAN 50 ve
- Trunk ports carry all needed VLANs tagged to Brocade (including VLAN 50)
Now you can worry about APs being on a VLAN 50 untagged port with dual mode running and carrying the tagged traffic of the other VLANs.
- Trunk ports carry all VLANs tagged (including VLAN 50)
- The interesting nuance here is that, when you run the switch firmware, you can only run "ip address x.x.x.x/x" on the default VLAN to manage it. You won't be able to do something like "int ve 50" followed by "ip address x.x.x.x/x" on the ve anymore. It will disappear from the menu, which will simplify things. However, make the Brocade management IP be in the VLAN 50 range despite the trunk port showing a PVID of 1.
- Add an "ip default route <Ubiquiti switch>" statement on the Brocade and now all VLAN traffic will be delegated to Ubiquiti for routing.
- You shouldn't have to create ACLs on the Brocade either since routing belongs with Ubiquiti.
Maybe others that are more seasoned at this can chime in and double check/correct my logic.
Yes, the router firmware has an R in it-> SPR08030x where R = Router. The switch one has an S in the same place. SPS08030xWell TIL... I had no idea there was a difference in that firmware I don't recall seeing anything in the Fohdeesha docs about that. I have pfsense handling routing, nothing doing that/ACLs on the Brocade. I'll offload some layer 3 to the Aristas once I get those up.
> show flash
Compressed Pri Code ..<stuff here>.. (SPS08030e.bin)
Compressed Sec Code ..<stuff here.. (SPS08030e.bin)
> boot flash secondary
Once you get the switch firmware on it, just run:Edit: Maybe I'm an idiot, but how can I get a management IP set to the switch to be accessible via any of the connected interfaces and not limit it to the MGMT port?
> conf t
> ip address x.x.x.x/24
It‘s not worth mentioning because approx. no one uses switch only firmware. The router firmware contains all the same functionality, plus L3 features if/when they’re necessary later.I don't recall seeing anything in the Fohdeesha docs about that.
Any update on this? Sorry I would love to buy one, but if I do and it's crazy loud I think my wife will be less than pleased...weird mine doesn't sound any louder than my icx6610-48p. I should check what psu's are in mine.
Please don't do that. Thanks.If it's the Ubiquiti (you said they were cores earlier), then I would run the switch firmware on the Brocade.
sorry work has been really busy - hoping to shut it down, pull the psus on Friday, and maybe get some comparable sound readings of the 7650 and 6610. re-iterating. audibly I cannot tell the difference between the 7650 and 6610 - but everyone's ear's are different.Any update on this? Sorry I would love to buy one, but if I do and it's crazy loud I think my wife will be less than pleased...
*on edit* - it looks like these use the same power supplies as the 6610. I have two revision C power supplies already.
FWIW, I use the switch firmware on my 6450 since my 6610 does router duty. The switch-only firmware works with IPv6 better when the prefixes may change (i,e, home network). The switch-only firmware will auto configure IPv6 advertised prefixes with SLAAC like any other end devices. The router firmware can take a prefix and add the eiu-64 address or be configured manually but not SLAAC is not an option.It‘s not worth mentioning because approx. no one uses switch only firmware. The router firmware contains all the same functionality, plus L3 features if/when they’re necessary later.
I'll check that out now. The default VLAN is 1, however, I'd prefer it to be 50, since that's my physical hardware management subnet. Since the AP's management is on VLAN 1, I keep reading that its native on all ports automatically, and I can't set VLAN 1 as untagged to any interfaces. I suppose if I re-IP my APs to be on VLAN 50, it should work... That said, as shown below, the link for ve 1 is showing as Down, and I can't figure out how to get that to change it's link state to Up.
Code:VII-SW48P01(config)#show vlan Total PORT-VLAN entries: 7 Maximum PORT-VLAN entries: 64 Legend: [Stk=Stack-Id, S=Slot] PORT-VLAN 1, Name DEFAULT-VLAN, Priority level0, Spanning tree Off Untagged Ports: (U1/M1) 3 4 5 6 11 12 17 18 19 20 37 38 Untagged Ports: (U1/M1) 39 40 41 42 43 44 45 46 47 48 Untagged Ports: (U1/M2) 3 4 Tagged Ports: None Uplink Ports: None DualMode Ports: None Mac-Vlan Ports: None Monitoring: Disabled PORT-VLAN 50, Name v50_MGMTPhysical, Priority level0, Spanning tree Off Untagged Ports: (U1/M1) 7 8 9 10 13 14 15 16 Tagged Ports: (U1/M2) 1 2 Uplink Ports: (U1/M2) 1 2 DualMode Ports: None Mac-Vlan Ports: None Monitoring: Disabled PORT-VLAN 60, Name v60_MGMTUser, Priority level0, Spanning tree Off Untagged Ports: (U1/M1) 31 32 33 34 35 36 Tagged Ports: (U1/M1) 1 2 Tagged Ports: (U1/M2) 1 2 Uplink Ports: (U1/M2) 1 2 DualMode Ports: None Mac-Vlan Ports: None Monitoring: Disabled PORT-VLAN 100, Name v100_Guest, Priority level0, Spanning tree Off Untagged Ports: None Tagged Ports: (U1/M1) 1 2 Tagged Ports: (U1/M2) 1 2 Uplink Ports: (U1/M2) 1 2 DualMode Ports: None Mac-Vlan Ports: None Monitoring: Disabled PORT-VLAN 110, Name v110_Wiferino, Priority level0, Spanning tree Off Untagged Ports: None Tagged Ports: (U1/M1) 1 2 Tagged Ports: (U1/M2) 1 2 Uplink Ports: (U1/M2) 1 2 DualMode Ports: None Mac-Vlan Ports: None Monitoring: Disabled PORT-VLAN 120, Name v120_IOT, Priority level0, Spanning tree Off Untagged Ports: None Tagged Ports: (U1/M1) 1 2 Tagged Ports: (U1/M2) 1 2 Uplink Ports: (U1/M2) 1 2 DualMode Ports: None Mac-Vlan Ports: None Monitoring: Disabled PORT-VLAN 130, Name v130_Cams, Priority level0, Spanning tree Off Untagged Ports: (U1/M1) 21 22 23 24 25 26 27 28 29 30 Tagged Ports: (U1/M1) 1 2 Tagged Ports: (U1/M2) 1 2 Uplink Ports: (U1/M2) 1 2 DualMode Ports: None Mac-Vlan Ports: None Monitoring: Disabled
Code:VII-SW48P01(config)#sh int brief wide Port Link State Dupl Speed Trunk Tag Pvid Pri MAC Name 1/1/1 Down None None None None Yes N/A 0 748e.f8d3.c340 Wireless AP First Floor 1/1/2 Up Forward Full 1G None Yes N/A 0 748e.f8d3.c341 Wireless AP Second Floor 1/1/3 Down None None None None No 1 0 748e.f8d3.c340 1/1/4 Down None None None None No 1 0 748e.f8d3.c340 1/1/5 Down None None None None No 1 0 748e.f8d3.c340 1/1/6 Down None None None None No 1 0 748e.f8d3.c340 1/1/7 Down None None None None No 50 0 748e.f8d3.c340 MX7000 MGMT 1/1/8 Down None None None None No 50 0 748e.f8d3.c340 MX7000 MGMT 1/1/9 Up Forward Full 1G None No 50 0 748e.f8d3.c340 NAS01 IPMI 1/1/10 Up Forward Full 1G None No 50 0 748e.f8d3.c340 NAS02 IPMI 1/1/11 Down None None None None No 1 0 748e.f8d3.c340 1/1/12 Down None None None None No 1 0 748e.f8d3.c340 1/1/13 Down None None None None No 50 0 748e.f8d3.c340 APC UPS MGMT 1/1/14 Down None None None None No 50 0 748e.f8d3.c340 1/1/15 Down None None None None No 50 0 748e.f8d3.c340 APC PDU 1 1/1/16 Down None None None None No 50 0 748e.f8d3.c340 APC PDU 2 1/1/17 Down None None None None No 1 0 748e.f8d3.c340 1/1/18 Down None None None None No 1 0 748e.f8d3.c340 1/1/19 Down None None None None No 1 0 748e.f8d3.c340 1/1/20 Down None None None None No 1 0 748e.f8d3.c340 1/1/21 Up Forward Full 100M None No 130 0 748e.f8d3.c354 Surveillance Camera 1/1/22 Up Forward Full 100M None No 130 0 748e.f8d3.c355 Surveillance Camera 1/1/23 Up Forward Full 100M None No 130 0 748e.f8d3.c356 Surveillance Camera 1/1/24 Up Forward Full 100M None No 130 0 748e.f8d3.c357 Surveillance Camera 1/1/25 Up Forward Full 100M None No 130 0 748e.f8d3.c358 Surveillance Camera 1/1/26 Up Forward Full 100M None No 130 0 748e.f8d3.c359 Surveillance Camera 1/1/27 Down None None None None No 130 0 748e.f8d3.c35a Surveillance Camera 1/1/28 Down None None None None No 130 0 748e.f8d3.c35b Surveillance Camera 1/1/29 Down None None None None No 130 0 748e.f8d3.c35c Surveillance Camera 1/1/30 Down None None None None No 130 0 748e.f8d3.c35d Surveillance Camera 1/1/31 Down None None None None No 60 0 748e.f8d3.c35e Mike's Office 1/1/32 Down None None None None No 60 0 748e.f8d3.c35f Mike's Office 1/1/33 Down None None None None No 60 0 748e.f8d3.c360 Mike's Office 1/1/34 Down None None None None No 60 0 748e.f8d3.c361 Mike's Office 1/1/35 Down None None None None No 60 0 748e.f8d3.c362 Mike's Office 1/1/36 Down None None None None No 60 0 748e.f8d3.c363 Mike's Office 1/1/37 Down None None None None No 1 0 748e.f8d3.c340 1/1/38 Down None None None None No 1 0 748e.f8d3.c340 1/1/39 Down None None None None No 1 0 748e.f8d3.c340 1/1/40 Down None None None None No 1 0 748e.f8d3.c340 1/1/41 Down None None None None No 1 0 748e.f8d3.c340 1/1/42 Down None None None None No 1 0 748e.f8d3.c340 1/1/43 Down None None None None No 1 0 748e.f8d3.c340 1/1/44 Down None None None None No 1 0 748e.f8d3.c340 1/1/45 Down None None None None No 1 0 748e.f8d3.c340 1/1/46 Down None None None None No 1 0 748e.f8d3.c340 1/1/47 Down None None None None No 1 0 748e.f8d3.c340 1/1/48 Down None None None None No 1 0 748e.f8d3.c340 1/2/1 Up Forward Full 10G None Yes N/A 0 748e.f8d3.c340 Uplink to Core 1/2/2 Disable None None None None Yes N/A 0 748e.f8d3.c340 Uplink to Core 1/2/3 Down None None None None No 1 0 748e.f8d3.c340 1/2/4 Down None None None None No 1 0 748e.f8d3.c340 mgmt1 Down None None None None No None 0 748e.f8d3.c340 Port Link State Dupl Speed Trunk Tag Pvid Pri MAC Name ve1 Down N/A N/A N/A None N/A N/A N/A 748e.f8d3.c340 ve50 Up N/A N/A N/A None N/A N/A N/A 748e.f8d3.c340
It's odd that your AP ports are showing "N/A" for PVID.
But I think these issues may be because the Brocade is running the router firmware. What is supposed to be doing the routing? Do you have any ACLs in this topology? If so, what switch is doing that? If it's the Ubiquiti (you said they were cores earlier), then I would run the switch firmware on the Brocade. You don't want "ve" interfaces on both as that will cause issues with routing, oddly enough even if you have "ve 50" on the Ubiquiti and "ve 50" on the Brocade. Ultimately, if VLAN 50 is to be the management VLAN, you'd be looking at implementing something like:
Ubiquiti:
Brocade:
- Management IP on VLAN 50 ve
- Trunk ports carry all needed VLANs tagged to Brocade (including VLAN 50)
Now you can worry about APs being on a VLAN 50 untagged port with dual mode running and carrying the tagged traffic of the other VLANs.
- Trunk ports carry all VLANs tagged (including VLAN 50)
- The interesting nuance here is that, when you run the switch firmware, you can only run "ip address x.x.x.x/x" on the default VLAN to manage it. You won't be able to do something like "int ve 50" followed by "ip address x.x.x.x/x" on the ve anymore. It will disappear from the menu, which will simplify things. However, make the Brocade management IP be in the VLAN 50 range despite the trunk port showing a PVID of 1.
- Add an "ip default route <Ubiquiti switch>" statement on the Brocade and now all VLAN traffic will be delegated to Ubiquiti for routing.
- You shouldn't have to create ACLs on the Brocade either since routing belongs with Ubiquiti.
Maybe others that are more seasoned at this can chime in and double check/correct my logic.
that is not true, I have 8x of the 6610 and only use the switch firmware, I prefer this versionIt‘s not worth mentioning because approx. no one uses switch only firmware. The router firmware contains all the same functionality, plus L3 features if/when they’re necessary later.
I did say “approx.”, however there is good reason for Ruckus merging the two into a single (router!) image in 10.x.that is not true, I have 8x of the 6610 and only use the switch firmware, I prefer this version
Yeah, I don't get the hate for L2 firmware. I've got 2 fortigate firewalls that do all the routing I need in my home lab.FWIW, I use the switch firmware on my 6450 since my 6610 does router duty. The switch-only firmware works with IPv6 better when the prefixes may change (i,e, home network). The switch-only firmware will auto configure IPv6 advertised prefixes with SLAAC like any other end devices. The router firmware can take a prefix and add the eiu-64 address or be configured manually but not SLAAC is not an option.
Honestly for anyone using the ICX switches for just L2 switches and not using their L3 abilities, go with the switch firmware and prevent further odd routing issues that you may cause without intention.
Any update on this? Sorry I would love to buy one, but if I do and it's crazy loud I think my wife will be less than pleased...
*on edit* - it looks like these use the same power supplies as the 6610. I have two revision C power supplies already.