do you have the LAG tagged in both those vlans on the brocade side? aside from that, you need to figure out why one of the links is only coming up at 100mbps
Yes.. Vlan 30 and Vlan 2000 is tagged in both vlan on interface 1/1/1 and 2/1/1do you have the LAG tagged in both those vlans on the brocade side? aside from that, you need to figure out why one of the links is only coming up at 100mbps
Port Link State Dupl Speed Trunk Tag Pvid Pri MAC Name
1/1/1 Down None None None 1 Yes N/A 0 cc4e.24b8.5c4c To pfSense Mast
2/1/1 Down None None None 1 Yes N/A 0 cc4e.24b8.5c4c
1/1/2 Up Blocked Full 100M 2 Yes N/A 0 cc4e.24b8.5c4c To pfSense Back
2/1/2 Up Blocked Full 1G 2 Yes N/A 0 cc4e.24b8.5c4c
I 'm troubleshooting the pfSense Backup box first. The interfaces are 1/1/2 and 2/1/2. In pfSense the speed and duplex is set to autoselect. On the ICX6610 each interface is set to auto. They should match...I just realized you have two different LACP bonds, to two different pfsense boxes, and it looks like you have issues with both.
In the config you sent me, the LACP bond to pfsense master is port 1/1/1 and 1/2/1
From your show interface output, none of the ports in the first LACP group are up at all:
Code:Port Link State Dupl Speed Trunk Tag Pvid Pri MAC Name 1/1/1 Down None None None 1 Yes N/A 0 cc4e.24b8.5c4c To pfSense Mast 2/1/1 Down None None None 1 Yes N/A 0 cc4e.24b8.5c4c
Then the LACP bond for the second pfsense box, which is ports 1/1/2 and 2/1/2, one is up at 1G but the other is stuck at 100mbps:
I would triple check you actually have the proper port pairs going from the switch to the correct pfsense boxes, because something here is screwed upCode:1/1/2 Up Blocked Full 100M 2 Yes N/A 0 cc4e.24b8.5c4c To pfSense Back 2/1/2 Up Blocked Full 1G 2 Yes N/A 0 cc4e.24b8.5c4c
There is something going on with the LAG setup on the pfSense_Backup lag.. For some reason, 1 port is registering as 1gbps and the other is registering as 100mbps in the auto speed-duplex setting... This is weird... Maybe I need to recreate the pfSense_Backup lag...I just realized you have two different LACP bonds, to two different pfsense boxes, and it looks like you have issues with both.
In the config you sent me, the LACP bond to pfsense master is port 1/1/1 and 1/2/1
From your show interface output, none of the ports in the first LACP group are up at all:
Code:Port Link State Dupl Speed Trunk Tag Pvid Pri MAC Name 1/1/1 Down None None None 1 Yes N/A 0 cc4e.24b8.5c4c To pfSense Mast 2/1/1 Down None None None 1 Yes N/A 0 cc4e.24b8.5c4c
Then the LACP bond for the second pfsense box, which is ports 1/1/2 and 2/1/2, one is up at 1G but the other is stuck at 100mbps:
I would triple check you actually have the proper port pairs going from the switch to the correct pfsense boxes, because something here is screwed upCode:1/1/2 Up Blocked Full 100M 2 Yes N/A 0 cc4e.24b8.5c4c To pfSense Back 2/1/2 Up Blocked Full 1G 2 Yes N/A 0 cc4e.24b8.5c4c
Considering I recommended checking the cable 2 different times before doing anything else, I can definitely believe itYou would not believe this, but I had a bad CAT6 cable.
Thanks a lot for this, it gives me somewhere to start thinking about how to attack the problem. I'm not shooting for anything unreasonable like a silent icx 6100 -- just a bit of a noise reduction on a 6450 so I could use it near where I sleep without irritating my SO too much (my home office is in the bedroom thanks to SF bay area rents.)It's even worse. The fans in the power supplies are controlled by the switch over i2c as well. If you take apart one of the power supplies (and I did), the fan/power led of the PSU connects to a header inside the PSU. If you remove this wire, the PSU won't turn on...
If you replace the fan IN the PSU with a slower one, the PSU will turn on, but the switch won't boot...'cause..well Brocade said FU when it came to silencing this switch.
That said, in all fairness, the 6610 is 1U switch with almost o.5tbps of switching bandwidth. That's a lot. The 6610 does get seriously hot, and probably needs these screamers, unless they change the chassis design. After letting the switch run for a few hours, open it up, and you can barely touch the heatsinks for more than a few seconds. They are that hot and that's WITH the screamers. If you even manage to replace the fans with something slower, there's a better than even chance, you'll cook the switch.
Yeah, it sounds like we're thinking about this in similar ways. I haven't done any controls programming in a while but I think an arduino should work for this, no? The last time I did anything like this was two jobs ago using labview. It's a good excuse to play around with programming controls again anyway.I've been learning Fusion360 just for designing shrouds/ducts. PM me, I'm interested on discussing some designs.
Like others said, the PSUs have data lines to monitor/check for these things. It's a PITA. Without putting together a PCB with a MCU that spoofs those signals, you won't get anywhere sadly. Like others said too, the thermal of the 6610 is already tight enough with the stock fans. I can't imagine making it work well with slower/less CFM fans.
I just got a bunch of Sunon and Delta units to test if anyone is interested.
Fan ok, speed (auto): [[1]]<->2
Fan speed switching temperature thresholds:
1 -> 2 @ 71 deg-C
1 <- 2 @ 66 deg-C
Sensor B Temperature Readings:
Current temperature : 39.0 deg-C
Sensor A Temperature Readings:
Current temperature : 43.5 deg-C
Warning level.......: 73.0 deg-C
Shutdown level......: 83.0 deg-C
Fan failed
Sensor B Temperature Readings:
Current temperature : 47.5 deg-C
Sensor A Temperature Readings:
Current temperature : 51.0 deg-C
Warning level.......: 73.0 deg-C
Shutdown level......: 83.0 deg-C
That's certainly easier than attacking the hardware watchdog, thanks for checking!Yup, just double checked - unplugged the fan completely in one of my lab 6450's - it boots up perfectly fine, doesn't even give an error in console or the log. The only indication anything is changed, is if you run "show chassis" it says "fan failed" in one of the lines, but it doesn't care and continues running fine. This means you can stick pretty much any fan in here you want (or none at all) and it won't care
It just needs to be a 40mm 12v 3pin (power + tach) fan. The included model is W40S12BMA5 - some info here - [W40S12BMA5-5*]| Nidec Corporation
The non poe models have 1 of them, the PoE models have 2 of the fans. I've had it running with the fan disconnected for a while now and the temp has only slowly crept up, still not even half of warning level - so I'd imagine you could grab a fan with half the CFM of the stock unit and be totally fine
Thank you for your note re VOIP for home usage; and that today, QOS is not needed for one VOIP line.no special switch commands, it'll work fine
QoS for voice is important when you're on a limited WAN connection and have a lot of other competing traffic, eg business environments where you need to guarantee bandwidth for the phone system. In a home environment with 50mbps of WAN available (or even more these days) QoS'ing 0.001mbps worth of VOIP traffic isn't going to get you a whole lot, even when pegging the connection with netflix instances etc most home routers these days have smart enough buffers/management to not squash a tiny 8kbps voip connection. This becomes more important when you start to have a larger overall phone system (like a PBX) where you need guaranteed bandwidth to support several simultaneous calls
If you do want to implement QoS, you would need to do it where the WAN connection is (eg your router). Since the switch will do full line rate on every port (tens of thousands of times more bandwidth than a VOIP call) there's not much to be gained by assigning different QoS flows/etc on the switch to voip traffic in a home situation