[135477] in North American Network Operators' Group
RE: Network Naming
daemon@ATHENA.MIT.EDU (Gary Steers)
Tue Jan 25 20:15:37 2011
Date: Wed, 26 Jan 2011 01:15:18 -0000
In-Reply-To: <A584FE4D-62CF-4218-8D21-CF51628BDA76@consultant.com>
From: "Gary Steers" <gary.steers@sharedband.com>
To: "nanog group" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
James makes a good point...
> Pick a scheme which:
> 1. Uses simple memorable names.
> 2. Makes business sense to you.
> 3. You know how to manage (database, publication, updates, etc.
> If I had to weight these criteria, I would weight 3 most heavily.
The other key thing to bear in mind is consistency and scalability... =
(i.e. design a scope that can grow with your network and needs
{interface/server}.{router/vmhost}.{city}.{country}.example.net
The other thing that doesn't really have any defined list is {city}, =
Some people prefer 2 letter, some 3 letter, some people use airport =
codes etc..
Hope that helps!
G
---
Gary Steers
Sharedband NOC/3rd Line Support
Sharedband
UK: +44 (0)1473 287207
US: +1 206 420 0240
E: gary.steers@sharedband.com
We have a=A0new support system - http://support.sharedband.com
-----Original Message-----
From: Cutler James R [mailto:james.cutler@consultant.com]=20
Sent: 25 January 2011 22:41
To: nanog group
Subject: Re: Network Naming
On Jan 25, 2011, at 3:50 PM, Nick Olsen wrote:
> Whats the rule of thumb for naming gear these days=20
> (routers,switches...etc). Or is there one?
Pick a scheme which:
1. Uses simple memorable names.
2. Makes business sense to you.
3. You know how to manage (database, publication, updates, etc.
If I had to weight these criteria, I would weight 3 most heavily.
James R. Cutler
james.cutler@consultant.com
