I think that's one of the subjects that Priscilla covers in her Top-down
Network Design book

some of the better "rules" are
 avoid using special characters (hypens, underscores) (I break that rule all
the time because I love using hyphens!)
 if you can, identify the type of equipment in the name (PDX001RTR or
PDXRTR001 or PDXGW001)
 if you can, use the same nomenclature for a site (PDXRTR001, PDXESW001 for
an ethernet switch, PDXATM001 for an ATM switch)
 for sites within a metropolitan area, find some short acronym that will
make sense to everyone involved (if you're the Lone Ranger, that makes the
task much easier, because we know that Tonto doesn't configure network
equipment  ;-), so in the Portland area, BVRRTR001 for Beaverton, SEARTR001
for Seaside, etc.)
 some folks like to use a nomenclature that represents the function of the
site rather than the name - if you have clear diversity like that, then go
for it
 finally, there are a few shops that use a very precise naming convention
based on Bellcore's conventions - those are mainly telco/telecom shops,
though, and unless you're familiar with that standard, you're better off
finding familiar names.

for buildings within campus networks, we've been fortunate enough to have
alphabetic buildings, and networking, for example, got assigned trees (the
Unix guys got mountains and bridges... LOL)

----- Original Message -----
From: "LeBrun, Tim" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 06, 2001 2:00 PM
Subject: Router/Switch naming standards


> Group,
> I am curious to know the opinions on what are some of the better
> naming standards used to name routers/switches?  I have heard of several
> (using local airport codes being the most common, i.e. PDX001(Portland) or
> ATL001(Atlanta)).  And then of course incrementing the number each time
you
> add a router/switch.  Any suggestions?
>
> [EMAIL PROTECTED]
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to