[123696] in North American Network Operators' Group
Re: Network Naming Conventions
daemon@ATHENA.MIT.EDU (James Jones)
Sat Mar 13 11:07:11 2010
Date: Sat, 13 Mar 2010 11:06:42 -0500
From: James Jones <james@freedomnet.co.nz>
To: nanog@nanog.org
In-Reply-To: <C0A98BB6DAFAAB46A78BBA2C51B98F3E01079C91@nexus.nexicomgroup.net>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On my last network I named all the routers after simpsons characters.
On 3/13/10 10:47 AM, Paul Stewart wrote:
> 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=router, to=location, ge1-1-1=interface, vl20=vlan 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 which it is addressed and contains confidential and/or privileged material. If you received this in error, please contact the sender immediately and then destroy this transmission, including all attachments, without copying, distributing or disclosing same. Thank you."
>
