|
Home > Archive > CCDA/CCDP > March 2003 > Network Labeling Techniques
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Network Labeling Techniques
|
|
|
| Network Labeling Techniques
------------------------
Hi All,
I’m really confused as I start reading about the Network labeling techniques for large and scalable network that serve both Data and Voice, I went through the ANSI/TIA/EIA 606-A standard but it seems for me that it’s too complicated. So as I know most of the people here in the forum are working in large networks and they might help me through this or can send me links for whitepapers regarding this issue..
Thanks..
--
Tamer Bayomy | |
| anchor40 2003-03-12, 9:50 am |
| Number one rule - make it logical, so that a new-hire can walk in and understand the scheme.
Number two rule - a lot of upfront investment is planning will result in MUCH shorter spending of time while maintaining
When we built our facility, we laid an alpha-numeric grid on the floor North-South is A-Z, and West-East is 1-24. Each cubicle, no matter of its size, has at least one wall-jack and when coupled with the floor number, each jack is labeled FFANN (I'm in 23G24, 23rd floor, cube G24).
We did the same in the office where our 35000 sq ft data center is located, and due to its size, the alpha characters require 2 letters, but it's only one floor so we dropped the floor number from the name. Every row has its own patch panel, so we would reference a server by it's patch panel location, like BN19-24, even though the server itself could be located in cabinet BN22.
Also, the datacenter walls are labeled with the appropriate row or rack id. You don't need to know exactly where anything is, as long as you know it's location id. Anyone with access can walk along the N-S walls and find the row, then look at the E-W walls to find the appropriate rack.
Hope this helps!
 | |
| xtam1 2003-03-12, 10:12 am |
| Anchor40, Thanks for replying.. |
|
|
|
|