When I was helping build a little datacenter, we labeled all racks in
x-y-z arrangement.
X is row, Y is rack, and Z is U from the 'bottom up' of the server
where it connected.
The other end always went to a spot on the SAME row where a gig switch
was that was
connected via fiber to the core switch.

It worked, and we did a quick web site for internal use that was done
with BASH scripts
writing to a 'flat file database'.  It was character graphics
(remember those?) and very
fast.

><> ... Jack
Whatever you do, work at it with all your heart... Colossians 3:23
"If you are not part of the solution, you are part of the precipitate"
- Henry J. Tillman
"Anyone who has never made a mistake, has never tried anything new." -
Albert Einstein
"You don't manage people; you manage things. You lead people." -
Admiral Grace Hopper, USN
Life is complex: it has a real part and an imaginary part. - Martin Terma


On Thu, Feb 7, 2013 at 9:46 AM, Matt Simmons
<standalone.sysad...@gmail.com> wrote:
> Hi,
>
> So, my current situation is that I'm working in a datacenter with 21 racks
> arranged in three rows, 7 racks long. We have one centralized distribution
> switch and no patch panels, so everything is run to the switch which lives
> in the middle, roughly. It's ugly and non-ideal and I hate it a bunch, but
> it is what it is. And it looks a lot like this:
> http://www.flickr.com/photos/bandman614/7835443304/in/set-72157604826850180
>
> Anyway, so given this really suboptimal arrangement, I want to be able to
> more easily identify a particular patch cable because, as you can imagine,
> tracing a wire is no fun right now.
>
> While everyone that I've talked to agrees that both ends need labeled. The
> question is what do you put on them. The schools of thought as far as I am
> aware are:
>
> 1) Every cable end's label says exactly what the other end is connected to,
> including hostname and port number
>
> 2) Every cable end's label is uniquely identified to that cable, because
> things move and relabeling sucks.
>
> 3) <insert your other viewpoint here>
>
> Is there actually some best practice that I'm unaware of? How would you do
> it in this case?
>
> --Matt
>
>
> --
> LITTLE GIRL: But which cookie will you eat FIRST?
> COOKIE MONSTER: Me think you have misconception of cookie-eating process.
>
> _______________________________________________
> Tech mailing list
> Tech@lists.lopsa.org
> https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
> This list provided by the League of Professional System Administrators
>  http://lopsa.org/
>
_______________________________________________
Tech mailing list
Tech@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to