[123812] in North American Network Operators' Group
RE: Network Naming Conventions
daemon@ATHENA.MIT.EDU (Erik Soosalu)
Tue Mar 16 10:37:16 2010
Date: Tue, 16 Mar 2010 10:36:22 -0400
In-Reply-To: <54718ee81003160615k5e882b5fnd64d31c20ed88ec6@mail.gmail.com>
From: "Erik Soosalu" <eriks@nationalfastfreight.com>
To: "Pierre-Yves Maunier" <nanog@maunier.org>,
"Paul Stewart" <pstewart@nexicomgroup.net>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
For pretty much all hardware we use
<city><site><devicetype><devicequalifier><devicenumber>
And for routers/switches I add the interface info.
e.g:
Tracing route to cal1sw-01.nff.local [10.1.9.4]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms con1sw-01-v103.nff.local [10.1.3.2]
2 1 ms <1 ms <1 ms con1rt-01-fe0-0.nff.local [10.1.250.99]
3 4 ms 3 ms 3 ms tor1rt-01-fe0-0s550.nff.local
[10.1.254.1]
4 48 ms 48 ms 50 ms cal1rt-01-fe0-1.nff.local [10.1.254.22]
5 56 ms 50 ms 48 ms cal1sw-01.nff.local [10.1.9.4]
But this also covers a lot of other stuff. We've got a list of 20
different device types
edm1ppc01 - Edmonton 1, page printer, color, unit 1
mtl2rt-02 - Montreal 2, router, unit 2
cal1lp-04 - Calgary 1, line printer 4
con1lt-12 - Concord 1, laptop #12
Everything gets asset tagged and labelled with the ID.
Servers are labelled by function (monitor, sql, etc).
Thanks,
Erik
-----Original Message-----
From: Pierre-Yves Maunier [mailto:nanog@maunier.org]=20
Sent: Tuesday, March 16, 2010 9:16 AM
To: Paul Stewart
Cc: NANOG list
Subject: Re: Network Naming Conventions
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=3Drouter, to=3Dlocation, ge1-1-1=3Dinterface, =
vl20=3Dvlan 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 =3D first transport core router
th2 =3D datacenter (Telehouse 2, generally 2 to 4 letters at our
appreciation)
par =3D city (Paris, using the 3 letters IATA City code, not the Airport
code
such as CDG for Paris)
--=20
Pierre-Yves Maunier
