sysadmin/RackNetworking written at 23:17:46; Add Comment
Getting your networks to your racks
I'm in the process of getting a new test server installed in a rack in our machine room. This means we needed to set up some network connections for it, which involved someone dragging yet more cable around our machine room and finding switch ports to plug into to get the necessary networks (which turned out not to be an entirely trivial thing).
As a result, the whole thing got me thinking about the issue of the best way to get all of your networks to where they need to be in your racks. The good approaches that I can think of right now are:
The first approach can deliver the most efficient network bandwidth, because you can clump machines that all need to talk to each other together on one switch, regardless of where they are physically located. You can't count on clumping such machines together in a single rack for at least two reasons; first, you may have more than a rack's worth of such machines, and second, machines may need bandwidth to more than one such clump.
Our current approach in practice is mostly the first option, partly because almost all of our new racks are only one row over from our network core. We have one new rack that is all the way on the other side of the room; fortunately it doesn't currently need more than a gigabit in total and its machines are all on one network. (And the rack is nearly full of modern machines, so the latter is unlikely to change for several years.)
* * *
Atom feeds are available; see the bottom of most pages.