My take
For smallish sites and companies, use of colloquial names is common and fun. In past lives, for example, just about every company has a Testerosa server. Tolkein and Marvel comic heros are common too.
For large corporation sites, not possible. Server names have to be reasonable short (for scripting), and informative. Site name + server type + server function + server number is fairly typical...
NYCNTPX01 - New York (US), NT, Proxy, number 01
HOU2KNT01 - Houston (US), Windows 2000, Lotus Notes, number 01
TORNVFS01 - Toronto (CA), Novell, file server, 01
LLANVFS02 - Llanelli (UK), Novell, file server, 02
There are several reasons for this...
- Group servers by site for monitoring
- Quickly determine server OS and purpose
- Scripts can be used to make use of fixed field length to copy files / document specs / prevenative maintenance. For example reboot all Notes servers on Sunday at 1AM.
Sorry for being so dull with the names but where some business have 100's and perhaps 1,000's of servers, FRODO and HULK just dont work.
Another use of a formal naming convention is for servers in public use. Imagine a server responsible for traffic tickets or airplane bookings being called KENNY or RAMBO. Lacks in originality but also lacks in professionalism.
Small shops are more fun. But the trend seems to be that they are gobbled up by the bigger companies. Case in point, TheVampire comment before it was sucked up by earthlink.
Pet peeves in naming...
- When those "powers that be" change the name of a device without notification, and then do it again, and again.
- When those "powers that be" decide to re-name all workstations with a numeric serial number. (Note: You can not ping a number -- has to be an alphanumeric name or an IP address. Management said - "So what if you loose one tool, this is what I have decided" -- non technical people making technical decisions -- with 1,000's of desktops, not a cool move.)