[123703] in North American Network Operators' Group
RE: Network Naming Conventions
daemon@ATHENA.MIT.EDU (Erik L)
Sat Mar 13 13:30:18 2010
From: Erik L <erik_list@caneris.com>
To: Paul Stewart <pstewart@nexicomgroup.net>, NANOG list <nanog@nanog.org>
Date: Sat, 13 Mar 2010 13:27:02 -0500
In-Reply-To: <C0A98BB6DAFAAB46A78BBA2C51B98F3E01079C91@nexus.nexicomgroup.net>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Hey Paul,
> Core1-rtr-to-ge1-1-1-vl20.nexicom.net
>=20
> Core box #1, rtr=3Drouter, to=3Dlocation, ge1-1-1=3Dinterface, vl20=3Dvla=
n etc
> etc....
>=20
That's disturbingly similar to ours :)
tflns2-ge0-1-vl1.caneris.com
TF =3D Toronto/Front
LNS #2 =3D LNS #2=20
ge0-1 =3D interface
vl1 =3D VLAN 1
>=20
> Going forward, I'd like to examine a better method to identify the
> devices.... does anyone have published standards on what they use or
> that of other networks and maybe even why they chose those=20
> methods? =20
>
One of my colleagues has written an overview and pros/cons of the most comm=
on naming conventions (purpose, geographic, purpose+geographic, and "themes=
") at http://www.watson-wilson.ca/blog/name-conv.html. He's a systems guy, =
so it's not written in the context of net ops, but some of the ideas are co=
mmon.=20
> But what do folks do for "aggregation devices" such as=20
> dial-up shelves,
> BAS devices etc?
>=20
See my example at the top.
>=20
> Finally, we have a fair amount of gear (that we own) at customer
> premises that act as either a managed device or a demarcation=20
> point ....
> how to you name those today?
>=20
Currently similarly to this:
MANAGED-DSL-1xxxx, where the 1xxxx is the account number. At the time it wa=
s decided to use this for no other reason than when a box/link goes down, i=
t's trivial to find the customer/contacts in the OSS since the device name =
in the monitoring alert already has an account number embedded in it. Silly=
reason perhaps, but it's simple and it works.
=20
>=20
> Open ended questions obviously - looking for many ideas.=20
>=20
There are many ways of doing it and many factors to consider, I'll just thr=
ow some food for thought:
-Purpose / device type
-Geography=20
-Hierarchical naming
-Scalability of the naming system
-DNS
-Humans - who's using the names and how? Reading/writing - how/frequency? W=
hat information do you want to convey (for obvious reason, this may vary gr=
eatly depending both on the target and the device)?
-Systems - what else is using your names or may be using your names in futu=
re? OSS/provisioning/monitoring/graphs for interfaces - automated? Limitati=
ons on character set and length of name, e.g. DNS, stupid switches with abs=
urdly short max lengths of port description fields, etc. A regexp can come =
in handy to define this (and perhaps your entire naming scheme) precisely. =
In a heterogeneous environment, you have all sorts of stuff where you may h=
ave two or more names to refer to the same thing.
-Prefixes/suffixes
-Mergers and acquisitions - what happens when you have to merge your networ=
k with someone else's? Though I can see the value of prefixing, I don't lik=
e naming conventions which prefix everything with an abbreviation of the co=
mpany for two reasons:
-Typing extra keystrokes repeatedly every day for no reason isn't fun
-Sorting/lists don't work nicely, especially when you would otherwise use =
a key to go down to the first letter of a name
-Traceroutes: I recall reading the slides from a NANOG presentation (unfort=
unately I don't recall the author's name and don't have a link now) which d=
iscussed naming devices in a traceroute-friendly way (friendly as in meanin=
gful to those outside the org as well); you might want to find this.
-Finally, look at how others do it - there are plenty of examples
Erik
________________________________________
From: Paul Stewart [pstewart@nexicomgroup.net]
Sent: Saturday, March 13, 2010 10:47 AM
To: NANOG list
Subject: Network Naming Conventions
Hi Folks...
With many changes going on this year in our network, I figured it's a
good time to revisit our naming conventions used in our networks.
Today, we use the following example:
Core1-rtr-to-ge1-1-1-vl20.nexicom.net
Core box #1, rtr=3Drouter, to=3Dlocation, ge1-1-1=3Dinterface, vl20=3Dvlan =
etc
etc....
Going forward, I'd like to examine a better method to identify the
devices.... does anyone have published standards on what they use or
that of other networks and maybe even why they chose those methods? The
core of the network is fairly easy for us to look at different changes
where you have interfaces, subinterfaces, locations etc. to deal with.
But what do folks do for "aggregation devices" such as dial-up shelves,
BAS devices etc?
Finally, we have a fair amount of gear (that we own) at customer
premises that act as either a managed device or a demarcation point ....
how to you name those today?
Open ended questions obviously - looking for many ideas.
;)
Paul
---------------------------------------------------------------------------=
-
"The information transmitted is intended only for the person or entity to w=
hich it is addressed and contains confidential and/or privileged material. =
If you received this in error, please contact the sender immediately and th=
en destroy this transmission, including all attachments, without copying, d=
istributing or disclosing same. Thank you."
