<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 20/Feb/15 10:34, Saul wrote:<br>
</div>
<blockquote
cite="mid:a4499a14.00000ca0.00000019@SAUL-PC.eNetworks.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hi<o:p></o:p></p>
<p class="MsoNormal">I was wondering: are there any best
practise documents out there for naming conventions for
routers, switches, cabinets etc?<o:p></o:p></p>
<p class="MsoNormal">I know every organisations requirements are
different, it’s a tricky subject, but when growing to with
equipment an multiple DCs in multiple geographic locations,
things become rather interesting. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Would be happy to hear other peoples
experiences that have gone through this.</p>
</div>
</blockquote>
<br>
In my experience, your choice of naming convention will depend on
what type of network you are.<br>
<br>
If you are a global carrier (typically wholesale), it is a little
easy. But if you are regional or local network that mainly deploys
network in several places within a city, and between cities in the
same country, this can get a lot trickier.<br>
<br>
For global-centric networks that typically live in well-known data
centres in each city, you can rely on using airport city codes to
define the location, even though you may spread across multiple data
centres within the same city.<br>
<br>
For local-centric networks, you're better off developing your own
method of tagging buildings you deploy kit into, as not all of them
will be data centres. Many of them will end up being high-rise
building where your kit is deployed in a dusty old basement with
barely enough cooling. In such a case, you can develop your own
naming convention that can be used within your CRM tool so that
Engineering and non-Engineering staff know how to quickly locate
PoP's, e.g., a network I used to work for a couple of years ago has
vehicle license plates broken down by state, where the first letter
in the license plate signifies the state in which the car was
registered. Then, the name of the building (not necessarily a data
centre) into which kit was deployed was given a meaningful
abbreviation (which would also include numbers if necessary) down to
a fixed number of characters. The final construct would be:<br>
<br>
building_abbrevation_license_plate_state_first_letter<br>
<br>
So let's say your car was registered in Acme state, and the license
plates from Acme state start with the letter "A" (AJN 1234S being
the license plate, for example), and that you're deploying kit in a
building called Boistrous which is codified as "bois", the final PoP
name would become:<br>
<br>
boista<br>
<br>
So your device name for that location would become:<br>
<br>
cr-01-boista.domain.name ==> as an example<br>
<br>
I could get into a lot of detail for either scenario, but as a first
stab, this is the general idea. In essence, for networks that deploy
densely in a single country, codifying your own names for buildings
(even for well-known data centres) scales better, since the majority
of your network won't be in data centres.<br>
<br>
Mark.<br>
</body>
</html>