What do you prefer To use as a naming scheme for your network?

Figured my 1st post should be a valid one. Im Kind of an ameteur in the networking area, but im studying at sait for my ccna and security certs, and i hope to rapidly progress.

Now, ive been reading a few security books, and one inpaticular brought up an interesting point about naming network resources. on one hand, making the names of computers Easy (such as server1, email1 etc...) helps with troubleshooting and network traffic analasys, but it also helps potential threats find their way easier.

On the other hand making the network resources anonymous can be difficult for the network admin, and thus you're told to find a balance.

To me, one of the best ways to do it is by room numbers. This way, you know which room the erros could be comming from, while at the same time have some anonymity on your network. internal sources could mess you over, but it seems like a good overall idea to me.

Your Thoughts?

Personally, I pick themes for networks based on authors. (Males are workstations females are servers... why? Because most engineers are sexless males and have an eaiser time remembering women's names. As such they remember their own desktop and several servers easily.)

For examples, one segement is Shakespeare and the systems are named:

Juliet, Ophelia, Desdemona, Cleopatra, Kate, etc for servers and Romeo, Hamlet, Othello, Antony, Petruchio, etc.

Within a cluster (which may have a single network name) the different systems go on a more singular theme like money (dollar, pound, euro, yen, rupee, etc), communist leaders (Lenin, Stalin, Mao, Castro, etc), or even 60's beat poets like the UGCS department of CalTech uses. ;)

This way you have a naming system that is easy for people to build memory tricks around, while being clearer to document than "mail_server1, ..., mail_server9, etc" and doesn't automatically reveal the architecture to an outsider... all while maintaining some logical flow. (once you know the rules)

cheers,

catch

Greek, Roman gods, ancient mapmakers, etc. We even did Seinfeld characters once.

LOTR and Harry potter characters seem to be popular atm..

The use of numbers (server1, server2, etc) is not the way to go IMHO !
It doesn't make it easier..

Also naming stuff something you can easilly link in your mind is good.. Cow, Pig, Chicken.. (for example) or Apple, Orange, Plum..

I did one with Disney characters - One segment (the largest client) had 7 servers named for the 7 dwarves, another had 2 named Bambi and Thumper...

We have workstations with OS first then a random numerical string.
Servers are named with an abbreviation of the location, an abbreviated function and then a number if needed. i.e. London exchange server2 would be LonEx02.
Firewalls are named after greek gods.

Whatever sticks in your head I suppose.

Yeah...Themes seem to be popular in networking names...

I've had a firm that uses names of trees ... it was very challenging at first to find the correct server... asking the local admin ... where can I find the "Maple" or "Conifer" ...how about the mighty "Oak" used for a cluster ... the routers and firewalls were named with animal names like Cheeta and Chipmunk ... the guy that designed this network sure had fun :) .

I to think that just naming servers and other apparel Server1 etc.. isn't the right way to go.

C.

Or if it's a very small network, use the names of chesspieces. My dad used the names pawn, rook, knight, bishop and queen for the systems that he has in his network. The name also was related to the power of these systems too. The webserver is queen, his main computer is rook. Two other systems for testing were called knight and bishop and a small laptop was called pawn. The scheme thus also indicated the importance of his system.
And I've asked him when he would have a computer called king but he replied there already was a king. He was the king because without him, game over. It is an interesting way to give names according to their importance.

One disadvantage to using a thematic naming schemes is it doesn't scale very well. It might work in the early stages of your network, but as time goes on you may run out of names. Also if you have multiple sites in your network it can be hard to determine where the server is located.

The scheme I have a preference for is one that allows you to determine the location, room and type of server (bearing in mind, this would depend upon the security requirements of your network - it may be inappropriate to contain that much detail). This allows you to come up with a scheme like:

DEN101PS

Which can break down into:

DEN = Denver
101 = Room 101
PS = Print Server

Whichever way you go, you need to ensure you document your naming scheme and ensure all the techs follow it. Confusion will reign if you have a mixture of systems with no documentation.

Hope this helps

T

Although I mentioned that using named systems will not automatically reveal the architecture of the network to an outsider. I do not think this is a relevant security point. Clearly the system will be examined before an attack is launched and by that point the attacker will know what the system does regardless of its name.

Pick thematic names for simplicity ("dick" and "jane" vs "ERP Server 6" and "ERP Server 9" or worse names like "Primary ERP Server 6/Back-up Email Server 2/Back-up Webserver 2") and not for security.

cheers,

catch

Whatever you do, UAnimosity, don't try to be funny. I set up a simple domain for a doctors office and his remote office. I named the domain Human. The servers were named after viruses/diseases, the workstations after organs.

After all was said and done, a network tech was running through the exchange logs for something and noticed that userx had logged into hiv and was not the primary user. (or something to that effect)

Anyway, the Doctor was not happy about the server name. I had to rename all the servers and workstations. At least I got to keep the domain name.

You can use the last two octets of the IP address. Makes it easy and since you have to remember them anyway.....what the heck.

interesting naming schemes, especailly that shakespeare one, i thought that was quite well done.

MOst organizations i know dont really a sense of humour when it comes to their network. they're a buisness enviroment and dont really want humour clouding your tasks.

Still, it was a nice try.

I like famous guitar players, and pink floyd songs. Keeps me chucklin.

I usually use elements for the workstations (oxygen,nitrogen) and scientists for the servers ( einstein, newton)

what we used at my old gov't job was pretty much like what TechGrunt said.

First two-four are city, second two are state, next three describe the machines function, last three are digits because of how many of each machine we had.

Example:

sfcasnf001

sf = san francisco
ca = california
snf = server, novell, file
001 = the first of these machines in the SF location

this scaled to huge proportions... the network had over 2 million machines (servers, workstations and "others") on it :)

I've seen many places do exactly what TechGrunt and Lv4 described.

Star Trek names (Laforge, picard, enterprise, voyager)...then they get into clustered systems...Riker01 Riker02, etc. It get's ugly. Then, you can see the corporate mentailty shift as they start a uniform standard that helps categorize devices and locales.
UNYCOS001 < Unix, New York, Corporate site, Server #001
WNYCOW015 < Windows, New York, Corporate site,Workstation #015
WNYCON095 < Windows, New York, Corporate site, Notebook #095

While it works, if you know the code, it's ugly. I personally like theme's, such as catch and others have mentioned. Great thinkers, artists, musicians...I have a friend who has the horsemen of the apocalypse on his home network...what ever you like.

I would prefer not to see smtpmail1, exchange04, oradb, etc. in server names...but using a letter or two to help a group of employees quickly recognize the function is probably fine. It leaves less to the imagination though.