|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical RE: Labeling and naming
Correction: in my previous message I incorrectly cited Syncordia, when I meant to say "Telcordia," which is the new name for Bellcore. ------Original Message------ From: "Frank Coluccio" <[email protected]> To: Przemyslaw Karwasiecki <[email protected]>, Kurt Erik Lindqvist <[email protected]>, [email protected] Sent: January 24, 2001 4:33:53 PM GMT Subject: RE: Labeling and naming A similar Bellcore/Syncordia convention that is used by the telcos and their affiliates closely resembles what you have described. It's called CLLI, for Common Language Location Identification, pronounced (some would argue, appropriately,) "Silly." I'm not necessarily recommending this convention, but it does provide some food for thought, and a basis for comparison to other methods that may be discussed here. See: http://www.ntca.org/bus_tech/tech_eng/clli.html An excerpt: ----begin: Code Format A CLLI code is an 11 character alphanumeric code that assigns a unique identification code to each location and to each coded telephone plant item. The code structure is: AAAABBCCDDD AAAA is the geographical or place code BB is the geopolitical or state/country code CC is the network site code DDD is the network entity code The combination of these codes comprises a unique place, a unique building and a specific entity. For example: CITYSTBDDS0 represents the first digital switch (DS0), in the town of CITY, in the state of ST, in the building BD. CLLI codes are used to: - identify buildings - identify specific equipment sites or interface points - identify entities such as switches <continued at above url > -----end One common pitfall in labeling physical assets occurs when logical IDs become confused with physical attributes that describe geography and order. As in floor, rack, shelf, slot, jack and I/O numbers, etc. A relational database is usually used to solve this, by maintaining the logical attributes in the background, or vice versa. Frank Coluccio DTI Consulting Inc. New York, NY [email protected] ------Original Message------ From: "Przemyslaw Karwasiecki" <[email protected]> To: Kurt Erik Lindqvist <[email protected]>, [email protected] Sent: January 24, 2001 3:36:29 PM GMT 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.us.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 -
|