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]
Re: Router/Switch naming standards
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]
LONG! RE: Router/Switch naming standards
/begin babble Well, It depends. ;-) We are currently going through a similar (design) issue. One of the major issues of naming is scalability, because much like the network design itself it can be a real pain later --if not planned for. Businesses buy other businesses, sites relocate, become dual homed, etc. We are _mostly_ a hub and spoke network for our regions & branches. So for quite a while we used a geographical area (self created) to identify the major node, then a name, then an increment number. EX: 17rtr01 (Area 17, router # 01) (Atlanta) Then branch offices hanging off this regional router were as such: EX: 1701rt1 (Area 17, Sub area 1 router # 01) (Columbia SC) Then their respective switches (we have a lot of token ring & a growing number of Ether) were as such: EX: 17mdf-s001 (Area 17 Main Distro Frame Switch 1) with no idea if it was TR/ET EX: 17idf6a-s001 (Area 17 6th floor Int. Distro Frame Switch 1) with no idea if it was TR/ET Now: one of the bigger problems with this is--> what happens when you start to go to a meshed network. Doesn't follow as neatly. 1701rt1 is now hanging off of both 17rt01 and 14rt01. And like I said, b. buy other b. Overlapping networks (NATing private IPs), etc start making things kinda crazy until you get it sorted out. Then later on because sites come & go (networks seem to always be in flux) you end up with 17rtr01, 1701rt1,1704rt1, & 1707rt1 and the new folks are wondering where is 1702, 1703, 1705 & 1706. So what we are now extremely close to finalizing is something along these lines: ATL-RT1 (we'll _never_ have more than 9 routers in Atlanta) ATL-MDF-ES01 Atlanta MDF Ethernet Switch 1 (these are stackable Nortel 450s & we'll never have more than 99--and five nines chance never more than 9) ATL-MDF-TS01 Atlanta MDF T/R Switch 1 ATL-MDF-SP01 Atlanta MDF StackProbe 1 ATL-I6A-ES01 Atlanta IDF floor 6A, Ether Sw 1 etc.etc. Now, that takes care of both the regions & branches hanging off them (along with a Big E5 size drawing of the network). So: what about a pretty large Data Center. 250 Racks. One 6509 for every for racks. So here is what we did there: RDC-CS-S001 Redmond Data Center Core Switch 1 RDC-CS-S002 RDC Core Switch 2 RDC-CS-RT1 RDC Core Switch Router 1 MSFC slot 15 RDC-CS-RT2 RDC Core Switch Router 2 RDC-CS-RTV1 RDC Core Switch HSRP IP address of RT1/RT2 External interface (V for virtual) RDC-CS-RTV2 RDC CS HSRP IP address of RT1/RT2 Internal interface RDC-GA-S132 RDC General Access (ie: servers plugged in here @ gig & 100) Switch located in Rack 132 RDC-GA-S145 RDC Gen. Access Sw located in Rack 145 RDC-DNS1RDC DNS 1 RDC-HA-BIG1 RDC High Available BigIP (F5 Gear) #1 RDC-HA-BIG2 RDC HA BigIP (F5 Gear) #2 RDC-HA-BIGV1RDC HA BigIP (F5 Gear) Vitual Interface External RDC-HA-DNS1 RDC HA DNS 1 Then there is stuff like DMZs (or is that DMZzz), Partner connections, etc. Basically it takes a bit of planning. ;-) HTH & good luck, /end babble TroyC -Original Message- From: LeBrun, Tim [mailto:[EMAIL PROTECTED]] Sent: Friday, April 06, 2001 2:01 PM To: '[EMAIL PROTECTED]' 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]
