nanog mailing list archives
Re: Network Naming Conventions
From: Larry Sheldon <LarrySheldon () cox net>
Date: Sat, 13 Mar 2010 12:26:08 -0600
For end-point hosts ("servers") I prefer terse topical names for single-function machines ("Finance", "Purchasing") and some predictable pattern that ties somehow to the organization for multipurpose machines ("Bluejay", "Parrot"). For network equipment at end points I prefer a string that starts with the machine's function, ends it an interface identifier, with location info in the middle. ("rtr-oma-hosp-3rd-peds", "rtr-oma-hosp-3rd-surg"). For network out in the middle I would do the same except expand the location data a bit and change the I/F infor to a hardware descriptive. -- Democracy: Three wolves and a sheep voting on the dinner menu. (A republic, using parliamentary law, protects the minority.) Requiescas in pace o email Ex turpi causa non oritur actio Eppure si rinfresca ICBM Targeting Information: http://tinyurl.com/4sqczs http://tinyurl.com/7tp8ml
Current thread:
- Re: Network Naming Conventions, (continued)
- Re: Network Naming Conventions Ravi Pina (Mar 13)
- RE: Network Naming Conventions Adcock, Matt [HISNA] (Mar 15)
- Re: Network Naming Conventions Nathan Ward (Mar 15)
- Re: Network Naming Conventions Joe Greco (Mar 15)
- Re: Network Naming Conventions Greg Whynott (Mar 15)
- Re: Network Naming Conventions James Jones (Mar 15)
- Re: Network Naming Conventions James Bensley (Mar 13)
- RE: Network Naming Conventions Tim Sanderson (Mar 13)
- Re: Network Naming Conventions Roy (Mar 13)
- Re: Network Naming Conventions Barry Shein (Mar 13)
- RE: Network Naming Conventions Paul Stewart (Mar 13)
- RE: Network Naming Conventions Paul Stewart (Mar 13)
- Re: Network Naming Conventions Rubens Kuhl (Mar 14)
- Re: Network Naming Conventions Joe Greco (Mar 14)