Our environment illustrated: what network cable colours mean what

May 14, 2011

Yesterday I mentioned in passing that we had a colour scheme for network cables, at least in our machine room and some wiring closets. To illustrate our environment, here's the cable colours we currently use:

red Our 'red' network for general user-managed machines.
pink The wireless network.
white Serial console cables; rather than have real serial cables, we run serial over standard Cat-5 cables using adapters.
green The management subnet(s).
yellow One of our iSCSI networks.
black The other iSCSI network.
blue Everything else; public subnets and sandboxes.

(I should note that this is for the cables themselves, not for the cable shrouds at the end of the cable. Our usual habit is to make the cable shrouds the same colour as the cable, but we don't worry about it too much.)

A couple of research groups also use some of these colours to keep their own network setups straight; I believe that black and yellow are 'shared' colours, and there is also someone using purple cables for something. The shared colours don't cause confusion because they're in completely separate places; our black and yellow wires only get used in one small area of our machine room.

(But where they get used they are very handy at keeping straight which iSCSI network is which and making sure that no one ever mistakes an iSCSI network or switch for anything ordinary.)

We're not very big on labeling our cables unless they're really important or unusual. Our experience with things like cable labels is that they are like comments in source code; they're fine until things start changing and then they never get updated and become actively misleading. If we're not going to be able to trust cable labels, it's better not to have them at all.


Comments on this page:

From 208.71.232.130 at 2011-05-17 13:10:57:

about labeling cables:

I label both ends with the same number, no matter what happens to either end of a cable (configuration wise) end1 will always lead to end2

-- Goozbach

Written on 14 May 2011.
« Our network layout (as of May 2011)
The most interesting reason for an unrouted sandbox network »

Page tools: View Source, View Normal, Add Comment.
Search:
Login: Password:
Atom Syndication: Recent Comments.

Last modified: Sat May 14 01:09:57 2011
This dinky wiki is brought to you by the Insane Hackers Guild, Python sub-branch.