|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical RE: Labeling and naming
I'll use your reply as a template: Device naming convention: <2 letters of the state/province abbreviation> <3 letters of city code> <3 letters of POP location> <unless there is only one POP in the city, then this field is blank> <1 letter describing device type> a = RAS Server/Access device (including remote console devices) s = Switch r = Router <2 letter device abbreviation> 12 = Cisco 12000 Series 75 = Cisco 7500 Series 50 = Cisco Catalyst 5000 Series 65 = Cisco Catalyst 6500 Series p3 = Lucent PM3 58 = Cisco AS5800 etc.. <2 digit device sequence identifier> <x letter/digit interface ID/number> Examples: ON-TOR-FRN-R12-01-POS11-2 Ontario, Toronto, Front St. Cisco 12000, #1, POS, slot 11, port 2 BC-VAN-HBR-R75-04-A9-0-1 British Columbia, Vancouver, Harbour Center, Cisco 7500 Series, #4, ATM, linecard 9, slot 0, interface 1 AB-CAL-A53-01-32 Alberta, Calgary, Cisco AS5300, #1, dialup port 32 NOTE: DNS for the devices themselves (for telnet, ssh, snmp, etc) are identicle to the above, except the interface information is not included. ie: ON-TOR-FRN-R12-09.LOOK.CA > -----Original Message----- > From: Przemyslaw Karwasiecki [mailto:[email protected]] > Sent: Wednesday, January 24, 2001 10:36 AM > To: Kurt Erik Lindqvist; [email protected] > Subject: RE: Labeling and naming > > > > Hello, > > We are currently trying to resolve the very same issue. > So far we plan to use following scheme: > > 1) Device name should be concatenation of following parts: > > <2 letters of ISO country code> > http://www.bcpl.net/~jspath/isocodes.html > <3 letters of airport city code> > http://www.ufreight.com/faq/airport_code/airport_code_by_ac.html > <3 letters of location> > to be created > <4 letters of device name abbreviations> > to be created -- in case of cisco: model number > <1 letter separator> > arbitrary decided to be capital letter X (no DNS nor > arithmetic exp problems) > <1 letter device ordinal> > can be hex if needed > > Examples: > USMIANOC3662X1 - Miami Lakes NOC cisco 3662 > USMIATPL7206X1 - Miami Teleplace cisco 7206 > USMIANAPJM20X1 - Miami NAP Juniper M20 > VEBRMPOP2501X1 - Venezuela, Barquisimento POP, VE cisco 2501 > VACCSCTV1010X1 - Venezuela, Caracas CANTV collocation, > cisco Lightstream 1010 > > 2) We will also create DNS zone ???core.net which will be > used in two main ways: > > a) reverse DNS lookup, to map IP addresses into > hierarchical names, like: > > serial1-0-0-128-<customer_name>.USMIATPL3662X1.TelePlace.mia.u > s.ifxcore.net > This will be mainly used for tools like traceroute, etc. > > b) straight DNS lookups of devices itself, like: > USMIATPL3662X1.ifxcore.net > This will be used to get easy access to a device itself > (through Loopback), > and due to mnemonic nature of device name should be > easy to memorize. > > So far the only problem we run into with this scheme is 12 > character limit > on hostnames on some boxes. > > Przemek > > -----Original Message----- > From: [email protected] [mailto:[email protected]]On Behalf Of > Kurt Erik Lindqvist > Sent: Wednesday, January 24, 2001 9:21 AM > To: [email protected] > Subject: Labeling and naming > > > > > > For a project I am currently working on I stumbled upon the following. > What is the best way to lable and name equipment? Although > this applies to > all equipment such as SDH ADMs, IP, ATM etc I realised that > it seems to be > hardest to find a sensible convention for IP equipment. > Preferably I would > like to find a convention that fits all, but I guess that is utopia. > > So, since list contains, PTTs, Telcos, ISPs and wannabees is there any > good common scheme or pointers to something useful? > > - kurtis - > > > > > -------------------------------------------------------------- > ----------- > This email server is running an evaluation copy of the > MailShield anti- > spam software. Please contact your email administrator if you have any > questions about this message. MailShield product info: www.mailshield.com . |