Re: Network Naming Conventions

Sorry for the delay; I've been traveling and neglecting my lists. on Sat, Mar 13, 2010 at 10:47:28AM -0500, Paul Stewart wrote: > 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. I study PTR naming conventio

Re: Network Naming Conventions

On Sat, 13 Mar 2010 10:47:28 -0500 "Paul Stewart" wrote: > 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? Bottom line is there is proba

RE: Network Naming Conventions

c). Thanks, Erik -Original Message- From: Pierre-Yves Maunier [mailto:na...@maunier.org] Sent: Tuesday, March 16, 2010 9:16 AM To: Paul Stewart Cc: NANOG list Subject: Re: Network Naming Conventions 2010/3/13 Paul Stewart > Hi Folks... > > > > With many changes going on t

Re: Network Naming Conventions

On Tue, 2010-03-16 at 14:15 +0100, Pierre-Yves Maunier wrote: > par = city (Paris, using the 3 letters IATA City code, not the Airport code > such as CDG for Paris) definitely +1 for IATA city codes. Less problems than the airport ones. ^

Re: Network Naming Conventions

2010/3/13 Paul Stewart > 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, rt

Re: Network Naming Conventions

Access network primarily CLLI codes of the building where the POP is located or closest serving CO, backbone three letter airport codes and in some cases CLLI codes. During the transition form JvNCNet to VERIO/NTT we had some CNAMES to the old network names where things at for example Philadelphia

Re: Network Naming Conventions

Bill Stewart writes: > - Tolkien characters (one of the reasons for DNS was that too many > people wanted to name their machine "frodo" or "mozart".) Diskworld characters are also quite common. For my own systems I use names of single malts. cheers Je 'typing on Bowmore' ns -- --

Re: Network Naming Conventions

On Mon, 2010-03-15 at 18:51 -0400, Patrick W. Gilmore wrote: > but they just don't realize how many there are. wow, deja-vu ! A few years ago I went into a large SSI infrastructure undergoing reconfiguration where the cluster nodes were named along the lines of biscuits, pizzas, vegetables, sw

Re: Network Naming Conventions

Sub-atomic particles. Some people say there are not enough, but they just don't realize how many there are. Plus you can expand into elements, then compounds. -- TTFN, patrick

Re: Network Naming Conventions

- Beers (the main server got to be "anchor", which made our ex-Navy boss happy and seemed more professional than some others - Mountains, mostly volcanic - Psychoactive chemicals ("the database is on speed, the development project's on prozac...) - Friends at Princeton used quarks ("Up is down toda

RE: Network Naming Conventions

A Helpful resource. http://www.namingschemes.com/ I used Element names from the periodic table for physical servers in a VMware Cluster once. I used robot names from Futurama for Continuous Integration build agents (Atlassian Bamboo) I have seen stars, greek gods, Lord of the rings characters an

RE: Network Naming Conventions

Can always call a router "packetloss". I used to use the names of transformers ;) -Original Message- From: Antonio Querubin [mailto:t...@lava.net] Sent: Monday, March 15, 2010 12:14 PM To: Greg Whynott Cc: 'nanog@nanog.org' Subject: Re: Network Naming Conventions

Re: Network Naming Conventions

On Mon, 15 Mar 2010, Greg Whynott wrote: We use confidence inspiring names here for our devices, shakey, broken, jitter, crusty Ah, try endangered plants/animals :) Antonio Querubin 808-545-5282 x3003 e-mail/xmpp: t...@lava.net

Re: Network Naming Conventions

Hi there, we brainstormed alot about this topic some time ago, following some conclusions: - anything trademarked might be a problem (so Zoidberg might be cool for a router, but I couldn't take a router named Zapp for serious, and "Farnsworth is going mad" would be considered as normal operat

Re: Network Naming Conventions

For Shipwright.com, it's Donald McKay's ships and famous clippers (shortened) (Flying) cloud, (Neptune's) car, &cet, then Jack Aubrey's commands (sophie, surprise...), and, finally, the names of various senti

Re: Network Naming Conventions

On Mar 15, 2010, at 11:37 AM, Sachs, Marcus Hans (Marc) wrote: I used to use dead presidents to name devices. Lincoln, Washington, Jefferson, etc. Humorous yet patriotic. We used to use deceased musicians. Popular (i.e., rock) for Linux servers. Classical musicians for everything else.

RE: Network Naming Conventions

I used to use dead presidents to name devices. Lincoln, Washington, Jefferson, etc. Humorous yet patriotic. Marc

RE: Network Naming Conventions

10,000 sheets of paper = 1.2 trees, per year By not printing this email, you’ve saved paper, ink and millions of trees   From: Ravi Pina [mailto:r...@cow.org] Sent: Sat 3/13/2010 3:33 PM To: Randy Bush Cc: nanog@nanog.org Subject: Re: Network Naming Conventions On Sun, Mar 14, 2010 at 04:58:11AM

Re: Network Naming Conventions

ours is a small network, so is ok to have fun. 8) we do use CNAMES to provide useful information(and make managers happy).. and name servers after the service the provide, eg ldap1.auth.mgt here is an example: gwhyn...@ops:~$ host rma.mgt rma.mgt.oicr.on.ca is an alias for RiserRoom5a.hp821

Re: Network Naming Conventions

> So, for production network and server gear, I like domain names > built with city and site codes: > site.city.domain I don't think anyone's saying you can't also do that. Using CLLI or IATA or whatever alongside router names works fine, and using CNAME's allows you to provide both a functional

Re: Network Naming Conventions

On 16/03/2010, at 2:10 AM, Adcock, Matt [HISNA] wrote: > I've used a Jimmy Buffett theme in test labs before. Naming themes are fine in test labs, because devices have a different function/role several times per day, a name acts like an asset tag in that it sticks with it through its lifetime.

Re: Network Naming Conventions

Being in the IDS business mostly involved with Snort, I've given my sensors "pig names" in the past. Wilbur, Arnold, Lechoncito On Mar 15, 2010, at 9:57 AM, Andrew D Kirch wrote: > Nice, I've used mountains (Denali, Everest, Olympus, etc) in the past to > name systems. Used profanity for

Re: Network Naming Conventions

Nice, I've used mountains (Denali, Everest, Olympus, etc) in the past to name systems. Used profanity for awhile to name machines, there's really quite a bit of it, and every language has it's own set, giving a large pool to choose from. Sadly, when outages occurred, it was somewhat difficult to

Re: Network Naming Conventions

We use confidence inspiring names here for our devices, shakey, broken, jitter, crusty G - Original Message - From: Adcock, Matt [HISNA] To: Ravi Pina ; Randy Bush Cc: nanog@nanog.org Sent: Mon Mar 15 09:10:40 2010 Subject: RE: Network Naming Conventions I've u

RE: Network Naming Conventions

saved paper, ink and millions of trees   From: Ravi Pina [mailto:r...@cow.org] Sent: Sat 3/13/2010 3:33 PM To: Randy Bush Cc: nanog@nanog.org Subject: Re: Network Naming Conventions On Sun, Mar 14, 2010 at 04:58:11AM +0900, Randy Bush wrote: > > On my last network I named all the ro

Re: Network Naming Conventions

It was a small network. On 3/13/10 2:58 PM, Randy Bush wrote: On my last network I named all the routers after simpsons characters. scaled well?

RE: Network Naming Conventions

I have yet to see a core router named "Luke" or "Bart"... ;) -Original Message- From: Joe Greco [mailto:jgr...@ns.sol.net] Sent: March-14-10 11:11 PM To: Rubens Kuhl Cc: Paul Stewart; NANOG list Subject: Re: Network Naming Conventions > On Sat, Mar 13, 2010 a

Re: Network Naming Conventions

> On Sat, Mar 13, 2010 at 6:01 PM, Paul Stewart > wrote: > > Yeah, just learning that... got a *tonne* of offline replies. > > > > Planets won't work well, simpson characters we'll run out very > > quickly umm.. forgot the rest.  We were looking for something that > > makes sense to the funct

Re: Network Naming Conventions

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 bel

Re: Network Naming Conventions

On Sat, Mar 13, 2010 at 6:01 PM, Paul Stewart wrote: > Yeah, just learning that... got a *tonne* of offline replies. > > Planets won't work well, simpson characters we'll run out very > quickly umm.. forgot the rest.  We were looking for something that > makes sense to the function of the box

Re: Network Naming Conventions

On Sat, Mar 13, 2010 at 10:47:28AM -0500, Paul Stewart wrote: > 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? Looked through the thread

Re: Network Naming Conventions

In a message written on Sat, Mar 13, 2010 at 10:47:28AM -0500, Paul Stewart wrote: > Open ended questions obviously - looking for many ideas. I think a key question to ask yourself is who needs to be able to interpret your names? Depending on your business, customers, engineers, etc you may have

Re: Network Naming Conventions

On Sun, Mar 14, 2010 at 04:58:11AM +0900, Randy Bush wrote: > > On my last network I named all the routers after simpsons characters. > > scaled well? Don't forget there were 5 Snowballs...

RE: Network Naming Conventions

Some of the suggestions around kinda what we have today but with some changes are what'll we'll debate internally. Take care, Paul -Original Message- From: Ravi Pina [mailto:r...@cow.org] Sent: March-13-10 2:01 PM To: Paul Stewart Cc: NANOG list Subject: Re: Network Nam

RE: Network Naming Conventions

Just wanted to say thanks to everyone who responded - game me more to think about than I thought was possible ;) Paul "The information transmitted is intended only for the person or entity to which it is addressed

Re: Network Naming Conventions

On March 13, 2010 at 10:53 c...@sandcastl.es (ck) wrote: > i believe in keeping host names as short as possible, so to start, i At BU we brought down about 1/3 of the internet (no joke!) around 1985 when our very first host table entries to SRI-NIC contained single letter hosts (like a.bu.edu) a

Re: Network Naming Conventions

On March 13, 2010 at 18:24 aa...@wholesaleinternet.net (aa...@wholesaleinternet.net) wrote: > STD's hmm, since we actually are STD.COM that could be a useful idea... -b

Re: Network Naming Conventions

On 3/13/2010 10:12 AM, Tim Sanderson wrote: ...Types of coffee and donuts Tim -Original Message- From: James Bensley [mailto:jwbens...@gmail.com] Sent: Saturday, March 13, 2010 12:27 PM To: NANOG list Subject: Re: Network Naming Conventions On 13 March 2010 16:06, James Jones wrote

RE: Network Naming Conventions

> > On my last network I named all the routers after simpsons > characters. > > scaled well? > He wrote "last" instead of "current"...make your own conclusions ;)

Re: Network Naming Conventions

> On my last network I named all the routers after simpsons characters. scaled well?

Re: Network Naming Conventions

On 3/13/2010 10:47, 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. I favor using CLLI code (well fake ones) TAMQFLTART1 is in the city of tampa (TAMQ) in FLorid

Re: Network Naming Conventions

On Sat, 13 Mar 2010, Paul Stewart wrote: 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

Re: Network Naming Conventions

Heh. Host naming discussions is like religion and politics at parties. It only leads to someone going home crying, red wine spilled all over their new dress, and a black eye. Not in that order. -r On Sat, Mar 13, 2010 at 10:47:28AM -0500, Paul Stewart wrote: > Hi Folks... > > > > With many c

Re: Network Naming Conventions

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

Re: Network Naming Conventions

islands rivers/creeks types of swords fruit minerals fermented things 3char strings punctuation marks twins ... --bill On Sat, Mar 13, 2010 at 10:47:28AM -0500, Paul Stewart wrote: > Hi Folks... > > > > With many changes going on this year in our network, I figured it's a > good time to r

Re: Network Naming Conventions

Singers: tenchi% ping elvis elvis is alive tenchi% On Sat, 13 Mar 2010, aa...@wholesaleinternet.net wrote: STD's --Original Message-- From: Tim Sanderson To: NANOG list Subject: RE: Network Naming Conventions Sent: Mar 13, 2010 12:12 PM ...Types of coffee and donuts

RE: Network Naming Conventions

in a traceroute-friendly way (friendly as in meaningful to those outside the org as well); you might want to find this. -Finally, look at how others do it - there are plenty of examples Erik ____ From: Paul Stewart [pstew...@nexicomgroup.net] Sent: Saturday, Mar

Re: Network Naming Conventions

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

Re: Network Naming Conventions

STD's --Original Message-- From: Tim Sanderson To: NANOG list Subject: RE: Network Naming Conventions Sent: Mar 13, 2010 12:12 PM ...Types of coffee and donuts Tim -Original Message- From: James Bensley [mailto:jwbens...@gmail.com] Sent: Saturday, March 13, 2010 12:27

RE: Network Naming Conventions

...Types of coffee and donuts Tim -Original Message- From: James Bensley [mailto:jwbens...@gmail.com] Sent: Saturday, March 13, 2010 12:27 PM To: NANOG list Subject: Re: Network Naming Conventions On 13 March 2010 16:06, James Jones wrote: > On my last network I named all the rout

Re: Network Naming Conventions

On 13 March 2010 16:06, James Jones wrote: > On my last network I named all the routers after simpsons characters. We use ancient Greek gods. -- Regards, James ;)

Re: Network Naming Conventions

-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 f

Re: Network Naming Conventions

On my last network I named all the routers after simpsons characters. On 3/13/10 10:47 AM, 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 ex

Network Naming Conventions

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=vl