[105312] in North American Network Operators' Group
RE: Cable Colors
daemon@ATHENA.MIT.EDU (Blake Pfankuch)
Tue Jun 17 10:18:28 2008
From: Blake Pfankuch <bpfankuch@cpgreeley.com>
To: "matthew@eeph.com" <matthew@eeph.com>, Peter Wohlers <pedro@whack.org>
Date: Tue, 17 Jun 2008 08:18:06 -0600
In-Reply-To: <48572023.1010205@eeph.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Course it can still get a little rough. In our noc we have a well working =
standard.
Blue =3D=3D IPKVM
Black =3D=3D Internal Data VLAN
Red =3D=3D WAN VLAN
Green =3D=3D Client managed device
Yellow =3D=3D Client device (we manage)
White =3D=3D to Desktop (or phone)
Pink =3D=3D iSCSI
Orange =3D=3D SAN fiber
Sadly we don't have any white and red (as someone else pointed out. Poor n=
ew tech with no fingers)
-----Original Message-----
From: Matthew Kaufman [mailto:matthew@eeph.com]
Sent: Monday, June 16, 2008 8:24 PM
To: Peter Wohlers
Cc: nanog@nanog.org
Subject: Re: Cable Colors
Peter Wohlers wrote:
> As you can see, by and large, people assign colors to functions. What
> color to what function varies like the wind. Unlike a previous employer
> whose colo-manager person insisted on using colors to represent cable
> lengths (Doh!), color -> function mapping seems pretty universal.
I used to do that too... Until I stood behind a rack trying to figure
out which of the 70 or so gray wires from the switch was the one going
to the box I was having the problem with. Then I bought as many
different colors as I could find, and mixed things up a bit.
Matthew Kaufman
