My current setup is approaching the 'need a database' scale... (we're at around 60 physical servers I've gotta deal with, if you count co-lo customer boxes, and maybe another 20 virtuals we manage. We've got around 1300 customer virtuals that I don't name or manage. so dealing with that database, either by massaging freeside until it can do what we need to do, or writing something else is one of our next projects.)
- 6-letter department abbreviation
- 3-letter group abbreviation
- 1-letter role/type identifier (e.g. w for workstation, s for server, m for mobile)
- 3-number sequence number, with the highest order digit often grouping related systems together.
It worked out pretty well and it made the systems easy to figure out from the hostname alone.
I like the idea of geographical names, but I would get a little annoyed when I moved a system from one building to another.
The thing is, vendors of expensive MPLS gear like to sell this idea of 'location independent subnets' to upper management as a way to 'simplify' the network.
Now maybe it's just 'cause I don't know layer two well, but god damn it is so much easier to troubleshoot layer three problems than to troubleshoot layer two problems, so I strongly favor making the subnets location and/or rack dependent.
Currently we are using a "code" to ID servers.
- 2 letter geographical location code
- 2 letter building code
- 4 number computer ID
(e.g. LIMB0001)
This was after someone had to spend nearly a whole day working out where computer CU2043 was located :)