That’s not out of line. Mine idles at 32-33w after boot with nothing but the console cable plugged in.My ICX 6450-24P draws 36w at idle, nothing plugged in. Datasheet says it should only pull 21w idle (first post from fohdeesha mentions 25w). That is almost 50% higher! Is this considered defective or are there that much variance between same models?
The main reason I got the 6450 is for the low power consumption because I have to sit next to this thing so I wanted to reduce heat and noise as much as possible. At this rate, I might as well add another 14w and get a 7250-48P to double all the ethernet and fiber ports.
View attachment 16506
Bummer.That’s not out of line. Mine idles at 32-33w after boot with nothing but the console cable plugged in.
Yes that would be helpful to get another data point.Kill-A-Watts have been showing in the past to not always be very accurate with lower power draw devices on them. I can dig mine out and test my ICX 6450-24p i just got the other day and see.
don't need the license for static routing but theyre free anyway just send me a PM. you will need aa license for half of the 10gb portsKill-A-Watts have been showing in the past to not always be very accurate with lower power draw devices on them. I can dig mine out and test my ICX 6450-24p i just got the other day and see.
Question for the ICX6450-24p. I am wanting to use the Layer 3 features to offload VLAN routing and such from my PFSense to the switch. Do I need the " ICX6450-PREM-LIC" license to do this, or can it do it already?
I got the 10Gbps active (thank you very much) and fully patched as well, and have the R installeddon't need the license for static routing but theyre free anyway just send me a PM. you will need aa license for half of the 10gb ports
Anyone able to help me out with finding the part number?Does anyone have a part number for the PSU blanking panels for the 6650? I want to pull the redundant ones and put them on the shelf. I can't seem to find the part number anywhere - just seems to be mentioned as part of the base device. Anyone have any they don't need and want to get rid of?
*cough* foam block cut to size...Anyone able to help me out with finding the part number?
Or can get thin aluminum sheet and cut to size. Cuts with sturdy scissors, and easy to punch holes in it too.*cough* foam block cut to size...
Tomato...TomaaahtoOr can get thin aluminum sheet and cut to size. Cuts with sturdy scissors, and easy to punch holes in it too.
I can confirm mine does it too. And I've tested with a BW-SHP6 and with a Eastron SDM120. Yea, ok, not lab grade by any means, but I think it's a little bit better than a random kill-a-watt. Oh, and it does so with a very poor power factor (0.55-0.6ish, can't remember at the moment, but I've written about it in the past).My ICX 6450-24P draws 36w at idle, nothing plugged in. Datasheet says it should only pull 21w idle (first post from fohdeesha mentions 25w). That is almost 50% higher! Is this considered defective or are there that much variance between same models?
Gently asking: might you have a URL handy ? (of your prior detailed post you mentioned here), thank youFrom experience, do not use pfSense as your router and DHCP server. Keep pfSense unaware of your VLANs. Use a point-to-point VLAN if pfSense is virtualized -OR- dedicate a port/lag to pfSense if it's a physical device.
Use your L3 switch as your internal router and pfSense as your edge router/firewall/NAT only so it will only receive internet-bound traffic.
With the ICX64R (L3) firmware, you will want to add a router-interface (ve) to each of the VLANs that need to be routed at all. Give each VE an IP address and appropriate subnet, and use that IP address as any connected device's Default Gateway (aka next-hop) address on each VLAN respectively.
Look up my post history and you'll find a good detailed post on how I have a similar setup with some good helpful info in this very thread.
Using the ICX as the L3 router to handle all vlans and ACLs is the *proper* way, aka the way it's intended to be used. That being said, there are quite a few folks here that are simply using it as a L2 switch, and doing inter-VLAN routing on pfsense or whatever.Thank you @ArmedAviator for that info, never thought to do things that way at all! I presume I then also manage all of the ACL's with in the ICX also to limit access to systems between VLANS. I guess I was thinking as PFSense to manage all of this as it is very familiar and easy to do (spoiled by GUIs). On the other hand, i also do not want to be spending the next 2 weeks figuring our CLI syntax to create everything switch side. I also do a lot of IP reservations as well my home lab which is a lot of windows boxes and stuff. Managing it all from PfSense would be easier for me in the end with out needing to become a networking expert.
Approach | Pro | Con |
L3 Routing |
|
|
L2 Switch with pfsense (etc) |
|
|