User deleted post
User deleted comment
9mo
In that case, you're fine with any non-TOR switch I'd think. I personally have Unifi aggregate switches (redundant) at the top of my racks with about 5 PowerEdge hosts and a few NAS boxes.
What are the other ToR switches were you quoted? I’m assuming S-Series? What model?
User deleted comment
9mo
4112 is cute
Honestly, I’d go with S4112 if it were my environment. They run OS10 and support VLT which will support in-service software upgrade (ISSU) for dual-homed servers. N3224PX will run OS6 by default which, IMO, is not as stable as OS10. They also will not support ISSU as they leverage standard stacking protocols
Will N32xx switches work? Most likely. But S-Series switches are built specifically for this use-case. I disagree with others who have said S-Series is overkill. I think they’re just right.
EDIT - have you actually received a quote for the N3224PX switches? I wouldn’t be surprised if they’re similarly priced to S4112.
What are your requirements? Max number of RJ45/SFP+ ports, Layer 3 functionality? Any sort of support agreement?
The Dell S Series are great switches, we use them for top of rack/core deployments but they are generally aimed at the datacentre market and might be more than what you need.
If you are needing 10GbE RJ45 then options will be slightly more limiting compared to SFP+ Personally, Ubiquiti wouldn’t be my first choice in environments where things are mission critical and need to work.
That does seem like overkill. I believe a switch like that is only needed for a super low latency or QOS environments, like when you're using storage spaces direct in a cluster I need to keep storage pools in sync.
Depending on the network capabilities of your storage, one thing to consider is a switch that has a few 25Gb or 40Gb ports for the storage, and then the rest being 10 gig ports for the hosts, that way one host doesn't completely saturate the network link for the storage. This also depends on the storage; All of my storage would suffer IO bottlenecks well before network bottlenecks.