[123809] in North American Network Operators' Group
Re: Network Naming Conventions
daemon@ATHENA.MIT.EDU (Pierre-Yves Maunier)
Tue Mar 16 09:16:35 2010
In-Reply-To: <C0A98BB6DAFAAB46A78BBA2C51B98F3E01079C91@nexus.nexicomgroup.net>
Date: Tue, 16 Mar 2010 14:15:59 +0100
From: Pierre-Yves Maunier <nanog@maunier.org>
To: Paul Stewart <pstewart@nexicomgroup.net>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
2010/3/13 Paul Stewart <pstewart@nexicomgroup.net>
> 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....
>
>
>
Hello,
On our side we're using things like :
xe3-3-0-154.tcr1.th2.par.as8218.eu
xe3-3-0 : interface (Juniper behaviour)
154 : vlan (if we use vlans on the interface)
tcr1 = first transport core router
th2 = datacenter (Telehouse 2, generally 2 to 4 letters at our appreciation)
par = city (Paris, using the 3 letters IATA City code, not the Airport code
such as CDG for Paris)
--
Pierre-Yves Maunier
