I agree - this convention is easy to type/understand/automate. Makes it easy to AXFR and see which devices are in a pop. We throw a bit of Perl at our device configs to create RR's for each device (imagine doing it manually... blergh). KISS :) -- Tom On 14/03/2010, at 5:23 AM, ck wrote: i believe in keeping host names as short as possible, so to start, i wouldn't put the location in the hostname, but putting the loc/pop code in dns (eg: sjc1.nexicom, tor1.nexicom, iad1.nexicom, etc), same goes for rtr, you really dont need that, imo personally, i prefer the shortest possible name cr - core router csw - core switch br/tr/pr - border/transit/peer router and prepending the interface id eg: cr1.tor1.nexciom.net<http://cr1.tor1.nexciom.net> ge-1-1-1.cr1.tor1.nexicom.net of if your want to have full role name ge-1-1-1.core1.tor1.nexicom.net te-1-0-0.border1.tor1.nexciom.net -ck On Sat, Mar 13, 2010 at 8:21 AM, virendra rode <virendra.rode@gmail.com>wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul, If my memory serves me correct, Richard presented traceroute presto at nanog47 that covered location identifiers. HTH, regards, /virendra Paul Stewart wrote: Hi Folks... With many changes going on this year in our network, I figured it's a good time to revisit our naming conventions used in our networks. Today, we use the following example: Core1-rtr-to-ge1-1-1-vl20.nexicom.net Core box #1, rtr=router, to=location, ge1-1-1=interface, vl20=vlan etc etc.... Going forward, I'd like to examine a better method to identify the devices.... does anyone have published standards on what they use or that of other networks and maybe even why they chose those methods? The core of the network is fairly easy for us to look at different changes where you have interfaces, subinterfaces, locations etc. to deal with. But what do folks do for "aggregation devices" such as dial-up shelves, BAS devices etc? Finally, we have a fair amount of gear (that we own) at customer premises that act as either a managed device or a demarcation point .... how to you name those today? Open ended questions obviously - looking for many ideas. ;) Paul ---------------------------------------------------------------------------- "The information transmitted is intended only for the person or entity to which it is addressed and contains confidential and/or privileged material. If you received this in error, please contact the sender immediately and then destroy this transmission, including all attachments, without copying, distributing or disclosing same. Thank you." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFLm7t7pbZvCIJx1bcRAin3AJ4r69FiLr+qC6KpVn3pfPnuEWRQCgCeMeRU BbhE1ExSlGBTGU/rWk+3pj4= =TeNX -----END PGP SIGNATURE----- -- Kind Regards, Tom Wright Internode Network Operations P: +61 8 8228 2999 W: http://www.internode.on.net<http://www.internode.on.net/>