James makes a good point...
Pick a scheme which: 1. Uses simple memorable names. 2. Makes business sense to you. 3. You know how to manage (database, publication, updates, etc. If I had to weight these criteria, I would weight 3 most heavily.
The other key thing to bear in mind is consistency and scalability... (i.e. design a scope that can grow with your network and needs {interface/server}.{router/vmhost}.{city}.{country}.example.net The other thing that doesn't really have any defined list is {city}, Some people prefer 2 letter, some 3 letter, some people use airport codes etc.. Hope that helps! G --- Gary Steers Sharedband NOC/3rd Line Support Sharedband UK: +44 (0)1473 287207 US: +1 206 420 0240 E: gary.steers@sharedband.com We have a new support system - http://support.sharedband.com -----Original Message----- From: Cutler James R [mailto:james.cutler@consultant.com] Sent: 25 January 2011 22:41 To: nanog group Subject: Re: Network Naming On Jan 25, 2011, at 3:50 PM, Nick Olsen wrote:
Whats the rule of thumb for naming gear these days (routers,switches...etc). Or is there one?
Pick a scheme which: 1. Uses simple memorable names. 2. Makes business sense to you. 3. You know how to manage (database, publication, updates, etc. If I had to weight these criteria, I would weight 3 most heavily. James R. Cutler james.cutler@consultant.com