Educause Security Discussion mailing list archives

Re: Server naming conventions


From: "Jones, Dan" <Dan.Jones () UMASSMED EDU>
Date: Wed, 10 Feb 2010 16:25:12 -0500

Claven was our mx host some time back too. I still love that name. 

We too have a star trek clique... but there are so many servers we've
run out of names (including original star trek, next generation, etc.,
etc.).

We use a naming convention that indicates server ownership, location,
function, and ##; e.g. EdUnivApps01 is owned by the school (ED), on the
University (Univ) campus, and is the first application server in the
group (Apps01). This standard convention helps since it's easy to
instantly know many aspects about the server... especially location and
function. 

If you extend this naming convention to the cable labeling scheme in
your data center, and add the switch port each device connects to (and
any intermediary DC cabling hops) it can pay even greater benefits. Full
labeling at all cable transitions identifies the entire path, server,
and switch port wherever you are. (very slick)

Network gear has a standard naming convention that similarly captures
location, closet, function, chassis & slot. 

Dan Jones
UMass Medical School

-----Original Message-----
From: The EDUCAUSE Security Constituent Group Listserv
[mailto:SECURITY () LISTSERV EDUCAUSE EDU] On Behalf Of Pete Hickey
Sent: Wednesday, February 10, 2010 3:17 PM
To: SECURITY () LISTSERV EDUCAUSE EDU
Subject: Re: [SECURITY] Server naming conventions

On Wed, Feb 10, 2010 at 02:17:08PM -0500, Woodruff, Daniel wrote:
What kinds of naming conventions do everyone follow when building new
servers?

TV shows.  Our email infrastructure is characters from Cheers, with
Cliff as the main mailer.  Star trek forms another group, etc...

-- 
Pete Hickey                      
The University of Ottawa         "Beware of geeks bearing GIFs."
Ottawa, Ontario                  
Canada                           

Current thread: