April 2011 - Test - lists.nanog.org

RPKI in the real world: using MaxLength
by Alex Band 20 Apr '11

20 Apr '11

The RIPE NCC is running their Resource Certification system for a couple of months now, and we've got quite a number of prefixes covered by ROAs in the repository by now. So I decided to have a look at how people are creating their ROAs and in particular how the 'Maximum Length' feature is used, which authorises the AS to deaggregate the prefix to the specified point. We compared the repository to the prefixes seen by our RIS route collectors. It gives a good indication how people are using this option, and what the effects are when people base routing decisions on validation results. You can read the article here: https://labs.ripe.net/Members/AlexBand/using-the-maximum-length-option-in-r… I'm interested to hear if you think we should change our implementation, and what choice you think is the best. -Alex

1 0

IPv4 address exchange
by Peter Thimmesch 19 Apr '11

19 Apr '11

John, Please note that we have filed our proposal for accreditation of IP address registrars with ICANN over a month ago. (Please see ICANN's Correspondence Page, Letters from David Holtzman to David Olive and John Jeffrey, filed 2 March 2011, Proposed Statement of IP Policy) <http://www.icann.org/en/correspondence/statement-ip-address-registrar-accre ditation-policy-31mar11-en.pdf > In addition we pointed out, in our opinion, that the current process for reviewing and approving a Global Policy is somewhat skewed towards the Regional Internet Registries. Hence we requested that due to this obvious and readily apparent Conflict-of-Interest (yes, I expect you will disagree with even this, which is so clear that to debate this would be simply too much even by the new standards that you have set recently in your online arguments with Prof. Mueller) we explore other forums to have the merits of the proposal aired. Regards, Peter Thimmesch Chairman

3 2

IPv4 address exchange
by Scott Weeks 19 Apr '11

19 Apr '11

Has this been discussed here? I did a quickie search and saw nothing. Other than spam to a technical mailing list, do you guys care, or is it a non-issue? scott --- Begin forwarded message: From: "Martin v. Löwis" <martin(a)v.loewis.de> To: apnic-talk(a)lists.apnic.net Subject: [apnic-talk] IPv4 address exchange Date: Mon, 18 Apr 2011 22:07:59 +0200 With the address pool exhausted in APNIC for regular allocations, service providers will need a way to acquire additional address blocks for deployment; by discovering resources that are currently unused (or can be released by the current user with sufficient effort). In order to promote such address transfers, we are offering the Asia-Pacific region a platform, at http://tradeipv4.com/ While this platform is designed to ultimately allow transfer of addresses within and across all regions of the world, we expect that interest within the APNIC community will be largest, hence this announcement. Kind regards, Martin v. Löwis _______________________________________________ apnic-talk mailing list apnic-talk(a)lists.apnic.net http://mailman.apnic.net/mailman/listinfo/apnic-talk

11 34

Implementations/suggestions for Multihoming IPv6 for DSL sites
by Daniel STICKNEY 19 Apr '11

19 Apr '11

Hello all, I'm investigating how to setup multihoming for IPv6 over two DSL lines (different ISPs), and I wanted to see if this wheel has already been invented. Has anyone already set this up or tested it ? In my research into the proposed solutions I came across this document "IEEE Communications Surveys - 2nd Quarter 2006, Volume 8, No. 2" (http://www.shim6.org/path-to-mh.pdf) which seems quite thorough. It compares routing methods, middle-box methods, and host-centric methods. It mentions "During the last years, the IETF has made several explicit or implicit architectural decisions regarding IPv6 multihoming. The main decision is to go down the path of developing the host-centric approaches" as well as "Host-centric multihoming, the approach promoted by the IETF for IPv6 multihoming, [...]". After the comparison of all host-centric methods it adds " [...], the IETF has decided by the end of 2004 to foster the SHIM approach." This approach looks interesting to me after all the comparisons, though I'm less familiar with it. I'm interested to hear your real-world experiences on this topic. Thanks, Daniel

20 52

Re: Easily confused...
by Scott Weeks 19 Apr '11

19 Apr '11

--- nanog(a)jima.tk wrote: From: Jima <nanog(a)jima.tk> On 2011-04-16 20:06, Michael Painter wrote: > Brielle Bruns wrote: >> I'm assuming your provider's network engineers (stupidly) assumed >> 123.x.x.x was a good idea for use in a private setup because it hadn't >> been assigned from the global pool (yet). >> >> Wouldn't be the first provider or service to not use proper RFC assigned >> private IP space for their internal networking setup. > > Apologies...missed operative word 'internal'.<s> I was about to reply pointing that out. FWIW, they're not announcing that space, so I definitely agree with the poorly-thought-out private infrastructure theory. http://bgp.he.net/AS36149#_prefixes FWIW. ----------------------------------------------------------------------- When I was last there there was a definite lack of folks with hands-on experience managing that size of address space: a /15 and two /16s plus some swamp. Further there're a lot of companies that contract to them that suggest these things and the contractor's advice is always faithfully followed, so any blame will go to the vendor if trouble happens due to design flaws. Making waves by saying this or that is wrong definitely gets one into hot water... ;-) ----------------------------------------------------------- > They are testing IPTV on Oahu in preperation for roll-out, so maybe they > renumbered in order to more easily identify the segments.(?) Really, I'd have hoped they'd use their two-year-old 2607:f9a0::/32 for anything that ambitious...but I might be wishing for too much. (Also, that 123 block seems to have been allocated in 2006, so it'd be even more unprofessional to start projects with that space since then.) -------------------------------------------------------- I'm the one that got this space for them, but allocation of folks to IPv6 roll out was minimal due the the upcoming IPTV roll out. I was the lone IPv6 voice in the company for a long time, but when I left there was gaining interest in IPv6 strategies. Not enough netgeeks and too many projects rolling out. scott

3 2

Re: Barracuda Networks is at it again: Any Suggestions as to an Alternative?
by AP NANOG 17 Apr '11

17 Apr '11

I would look into Asatro, they have a solid product and good support. If you want a contact person let me know and I will email you directly. On 4/9/11 11:55 AM, proth(a)cnsny.net wrote: > Andrew, > We use and offer Postini - a front end service. Postini is a anti virus and spam filter, and can spool mail if your circuits are down. Postini is a Google company and works like a charm. If you need more information please contact me offline proth(a)cnsny.net > > Paul > > Sent from my Verizon Wireless Phone > > ----- Reply message ----- > From: "Andrew Kirch"<trelane(a)trelane.net> > Date: Sat, Apr 9, 2011 10:39 am > Subject: Barracuda Networks is at it again: Any Suggestions as to an Alternative? > To: "John Palmer (NANOG Acct)"<nanog2(a)adns.net>,<nanog(a)nanog.org> > > John, > > My suggestion isn't _QUITE_ an appliance, but it works very well and > I've been exceptionally happy with it. It's a distribution of linux > controlled via a web interface that does far more than just mail > filtering (at which it is both flexible and adept). Take a look at > http://www.clearfoundation.com/Software/overview.html. The hardware > requirements shouldn't be too insane, and the rules > updates/subscriptions for the various services are all month to month, > and not a bucket of insane. > > Andrew > > > On 4/8/2011 11:51 PM, John Palmer (NANOG Acct) wrote: >> OK, its been a year since my Barracuda subscription expired. The unit >> still stops some spam. I figured that I would go and see what they >> would do if I tried to renew my subscription EXACTLY one year after it >> expired. Would their renewal website say "Oh, you are at your >> anniversary date", and renew me for a year? >> >> No such luck: They want me to PAY FOR AN ENTIRE YEAR for which I did >> NOT receive service and then for the current (upcoming year). Sorry - >> I don't allow myself to be ripped off like that. Sorry Barracuda - you >> get no money from me and I'll tell everyone I know about this policy >> of yours. >> >> I posted an article about this unscrupulous practice on my blog last >> year at http://www.john-palmer.net/wordpress/?p=46 >> >> My question is - does anyone have any suggestions for another e-mail >> appliance like the Barracuda Spam Firewall that doesn't try to charge >> their customers for time not used. I should be able to shut off the >> unit for a year or whatever and simply renew from the point that I >> re-activate the unit instead of having to pay for back-years that I >> didn't use. >> >> Thanks >> >> >> >> >> >

2 1

mail admin contacts within gc.ca ?
by Jim Mercer 17 Apr '11

17 Apr '11

anyone have a method of determining who to contact about DNS/email issues within gc.ca? i tried emailing postmaster(a)pco.gc.ca, but got a bounce back saying i was not on the 'approved list'. (pco.gc.ca being the group i need to contact) -- Jim Mercer jim(a)reptiles.org +1 416 410-5633 You are more likely to be arrested as a terrorist than you are to be blown up by one. -- Dianora

2 1

RE: 365x24x7 (sleep patterns)
by Mark Green 17 Apr '11

17 Apr '11

Suggestion; once on the 'night shift' stay put for at least three months... Sleep patterns take time to adjust. Jumping between day and night shifts will burn out even the most motivated employee. Mark Green > From: nanog-request(a)nanog.org > Subject: NANOG Digest, Vol 39, Issue 46 > To: nanog(a)nanog.org > Date: Fri, 15 Apr 2011 15:52:19 +0000 > > Send NANOG mailing list submissions to > nanog(a)nanog.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.nanog.org/mailman/listinfo/nanog > or, via email, send a message with subject or body 'help' to > nanog-request(a)nanog.org > > You can reach the person managing the list at > nanog-owner(a)nanog.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of NANOG digest..." > > > Today's Topics: > > 1. 365x24x7 (harbor235) > 2. Re: New hijacks, and lots of them (Ronald F. Guilmette) > 3. Re: 365x24x7 (Peter Hicks) > 4. Re: 365x24x7 (Charles Mills) > 5. RE: 365x24x7 (Greg Moore) > 6. Re: 365x24x7 (Steve Clark) > 7. Re: 365x24x7 (Marshall Eubanks) > 8. Re: 365x24x7 (Alex Brooks) > 9. RE: 365x24x7 (Sanders, Randall K) > 10. Re: 365x24x7 (Tony Finch) > 11. Re: 365x24x7 (harbor235) > 12. Re: 365x24x7 (Paul Graydon) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 15 Apr 2011 09:14:05 -0400 > From: harbor235 <harbor235(a)gmail.com> > Subject: 365x24x7 > To: NANOG list <nanog(a)nanog.org> > Message-ID: <BANLkTimD9jYVzM_hv21y9LHzObR3RVG0YA(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > If I were going to provide a 365x24x7 NOC, how many teams of personnel do I > need > to fully cover operations? I assume minimally you need 3 teams to cover the > required > 24 hr coverage, but there is off time and schedule rotation? > > thoughts, experience? > > Mike > > > ------------------------------ > > Message: 2 > Date: Fri, 15 Apr 2011 06:17:06 -0700 > From: "Ronald F. Guilmette" <rfg(a)tristatelogic.com> > Subject: Re: New hijacks, and lots of them > To: nanog(a)nanog.org > Message-ID: <2971.1302873426(a)tristatelogic.com> > > > In message <5824.1302780126(a)tristatelogic.com>, I wrote: > > > http://www.47-usc-230c2.org/20110414-snowshoe-1.txt > > http://www.47-usc-230c2.org/20110414-snowshoe-2.txt > > My apologies to anyone and everyone who tried to get at these files. > It seems that my provider may perhaps have recently developed some > rather odd ideas about packet filtering for static broadband lines. > Until I can get the problem worked out, the following alternative URLs > ought to do instead: > > ftp://ftp.47-usc-230c2.org/pub/20110414-snowshoe-1.txt > ftp://ftp.47-usc-230c2.org/pub/20110414-snowshoe-2.txt > > > > > ------------------------------ > > Message: 3 > Date: Fri, 15 Apr 2011 14:17:48 +0100 > From: Peter Hicks <peter.hicks(a)poggs.co.uk> > Subject: Re: 365x24x7 > To: harbor235 <harbor235(a)gmail.com> > Cc: NANOG list <nanog(a)nanog.org> > Message-ID: <066F653E-C0F8-4026-9FE0-3A8899378D0C(a)poggs.co.uk> > Content-Type: text/plain; charset=us-ascii > > > On 15 Apr 2011, at 14:14, harbor235 wrote: > > > If I were going to provide a 365x24x7 NOC, how many teams of personnel do I > > need to fully cover operations? I assume minimally you need 3 teams to cover the > > required 24 hr coverage, but there is off time and schedule rotation? > > > Although more geared up for on-call, http://blog.hinterlands.org/2010/07/running-an-oncall-rota/ is a very useful resource. > > > Peter > > > > ------------------------------ > > Message: 4 > Date: Fri, 15 Apr 2011 09:25:02 -0400 > From: Charles Mills <w3yni1(a)gmail.com> > Subject: Re: 365x24x7 > To: harbor235 <harbor235(a)gmail.com>, NANOG list <nanog(a)nanog.org> > Message-ID: <BANLkTint8hnfenSQZBHoS3x4hAS_P78JNA(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > I've had it done in places where I work where you'll have 3 rotations > working 12 hour shifts. > > In a 2 week pay period they get their 80 hours in a blend 36 one week > and 44 the next. It gives some nice consecutive days off time which > also doubles as a retention tool for some employees. You might have > to get creative to have all the days work out but it can be done. > > On Fri, Apr 15, 2011 at 9:14 AM, harbor235 <harbor235(a)gmail.com> wrote: > > If I were going to provide a 365x24x7 NOC, how many teams of personnel do I > > need > > to fully cover operations? I assume minimally you need 3 teams to cover the > > required > > 24 hr coverage, but there is off time and schedule rotation? > > > > thoughts, experience? > > > > Mike > > > > > > -- > ===================================== > Charles L. Mills > Email: w3yni1(a)gmail.com > ===================================== > Need server hosting, DR or colocation services?? See me! > > > > ------------------------------ > > Message: 5 > Date: Fri, 15 Apr 2011 09:37:54 -0400 > From: Greg Moore <mooregr(a)greenms.com> > Subject: RE: 365x24x7 > To: harbor235 <harbor235(a)gmail.com>, NANOG list <nanog(a)nanog.org> > Message-ID: <mailman.2806.1302882739.16627.nanog(a)nanog.org> > Content-Type: text/plain; charset="iso-8859-1" > > When I did this years ago I found 5 was really a minimum so that I could cover weekends and then had extra coverage as needed during the week. > > I did find it was good to swap out the graveyard shift every 6 months or so. > > -----Original Message----- > From: harbor235 > Sent: Friday, April 15, 2011 9:14 AM > To: NANOG list > Subject: 365x24x7 > > If I were going to provide a 365x24x7 NOC, how many teams of personnel do I > need > to fully cover operations? I assume minimally you need 3 teams to cover the > required > 24 hr coverage, but there is off time and schedule rotation? > > thoughts, experience? > > Mike > > > > > ------------------------------ > > Message: 6 > Date: Fri, 15 Apr 2011 09:48:42 -0400 > From: Steve Clark <sclark(a)netwolves.com> > Subject: Re: 365x24x7 > To: Charles Mills <w3yni1(a)gmail.com> > Cc: NANOG list <nanog(a)nanog.org> > Message-ID: <4DA84CBA.5030409(a)netwolves.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 04/15/2011 09:25 AM, Charles Mills wrote: > > I've had it done in places where I work where you'll have 3 rotations > > working 12 hour shifts. > > > > In a 2 week pay period they get their 80 hours in a blend 36 one week > > and 44 the next. It gives some nice consecutive days off time which > > also doubles as a retention tool for some employees. You might have > > to get creative to have all the days work out but it can be done. > > > > On Fri, Apr 15, 2011 at 9:14 AM, harbor235<harbor235(a)gmail.com> wrote: > >> If I were going to provide a 365x24x7 NOC, how many teams of personnel do I > >> need > >> to fully cover operations? I assume minimally you need 3 teams to cover the > >> required > >> 24 hr coverage, but there is off time and schedule rotation? > >> > >> thoughts, experience? > >> > >> Mike > >> > > > > > I worked once in a production plant. They had 4 crews a,b,c,d and worked 6 days on 2 off. It was rotating shifts. As an example crew A worked 6 > days 8-4 was off 2 days then started the next shift on 4-midnight, then midnight to 8. So at any one day 3 of the 4 crews were working and the other > crew was off. > > -- > Stephen Clark > *NetWolves* > Sr. Software Engineer III > Phone: 813-579-3200 > Fax: 813-882-0209 > Email: steve.clark(a)netwolves.com > http://www.netwolves.com > > > ------------------------------ > > Message: 7 > Date: Fri, 15 Apr 2011 09:52:11 -0400 > From: Marshall Eubanks <tme(a)americafree.tv> > Subject: Re: 365x24x7 > To: Greg Moore <mooregr(a)greenms.com> > Cc: NANOG list <nanog(a)nanog.org> > Message-ID: <CAC57439-9CCC-42E3-8CB4-FA4141D8F3DA(a)americafree.tv> > Content-Type: text/plain; charset=us-ascii > > > > On Apr 15, 2011, at 9:37 AM, Greg Moore wrote: > > > When I did this years ago I found 5 was really a minimum so that I could cover weekends and then had extra coverage as needed during the week. > > > > I did find it was good to swap out the graveyard shift every 6 months or so. > > > > When I worked with NASA and the Navy on remote locations that needed full time staffing, the rule of thumb was > 5 people and 4 shifts was the absolute minimum, and the people had to be motivated enough to pull 12 hour shifts on a regular basis (i.e., this > was very bare bones). The 4th shift was needed during the weekends. > > Anything less, and you would have uncovered periods if, say, 2 people got sick simultaneously. > > Regards > Marshall > > > > -----Original Message----- > > From: harbor235 > > Sent: Friday, April 15, 2011 9:14 AM > > To: NANOG list > > Subject: 365x24x7 > > > > If I were going to provide a 365x24x7 NOC, how many teams of personnel do I > > need > > to fully cover operations? I assume minimally you need 3 teams to cover the > > required > > 24 hr coverage, but there is off time and schedule rotation? > > > > thoughts, experience? > > > > Mike > > > > > > > > > > > ------------------------------ > > Message: 8 > Date: Fri, 15 Apr 2011 15:27:32 +0100 > From: Alex Brooks <askoorb+nanog(a)gmail.com> > Subject: Re: 365x24x7 > To: nanog <nanog(a)nanog.org> > Message-ID: <BANLkTikkVH_yk=97oWgq_A0YLxZ9dxNVXg(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Fri, Apr 15, 2011 at 2:14 PM, harbor235 <harbor235(a)gmail.com> wrote: > > If I were going to provide a 365x24x7 NOC, how many teams of personnel do I > > need > > to fully cover operations? I assume minimally you need 3 teams to cover the > > required > > 24 hr coverage, but there is off time and schedule rotation? > > Well, if you feel like being "nice" to your employees, or want to stop > them from making mistakes a few months/years in to shift work, (or if > you're having to set something up abroad), the Working Time Directive > can be a useful guideline. > > (Full details at http://en.wikipedia.org/wiki/Working_Time_Directive > and http://www.businesslink.gov.uk/bdotg/action/layer?topicId=1073858926 > if you're board, ignore the silly bits) > > But basically, in general, workers aged 18 and over are entitled to: > > - work no more than six days out of every seven, or 12 out of every 14 > - take a 20-minute break if their shift lasts for more than six hours > - work a maximum 48-hour average week > > And in general, night workers: > > - should not work more than an average of eight hours in a 24-hour > period, averaged over a reference period of 17 weeks > > If you're an employer, be glad you're in North America :-) > > HTH, > > Alex > > > > ------------------------------ > > Message: 9 > Date: Fri, 15 Apr 2011 09:31:48 -0500 > From: "Sanders, Randall K" <Randall.K.Sanders(a)xo.com> > Subject: RE: 365x24x7 > To: nanog <nanog(a)nanog.org> > Message-ID: > <B0E45381691B4E4188ECEE2507142CFC5C7B3660(a)txplanexch01.corp.inthosts.net> > > Content-Type: text/plain; charset="us-ascii" > > Have you taken into account number of alarms per hour, inbound call volume for repairs, and how much repair is done at the first tier level? Bare minimum staffing in a busy environment? > > Randy Sanders > > -----Original Message----- > From: Alex Brooks [mailto:askoorb+nanog@gmail.com] > Sent: Friday, April 15, 2011 9:28 AM > To: nanog > Subject: Re: 365x24x7 > > On Fri, Apr 15, 2011 at 2:14 PM, harbor235 <harbor235(a)gmail.com> wrote: > > If I were going to provide a 365x24x7 NOC, how many teams of personnel do I > > need > > to fully cover operations? I assume minimally you need 3 teams to cover the > > required > > 24 hr coverage, but there is off time and schedule rotation? > > Well, if you feel like being "nice" to your employees, or want to stop > them from making mistakes a few months/years in to shift work, (or if > you're having to set something up abroad), the Working Time Directive > can be a useful guideline. > > (Full details at http://en.wikipedia.org/wiki/Working_Time_Directive > and http://www.businesslink.gov.uk/bdotg/action/layer?topicId=1073858926 > if you're board, ignore the silly bits) > > But basically, in general, workers aged 18 and over are entitled to: > > - work no more than six days out of every seven, or 12 out of every 14 > - take a 20-minute break if their shift lasts for more than six hours > - work a maximum 48-hour average week > > And in general, night workers: > > - should not work more than an average of eight hours in a 24-hour > period, averaged over a reference period of 17 weeks > > If you're an employer, be glad you're in North America :-) > > HTH, > > Alex > > > > > > > ------------------------------ > > Message: 10 > Date: Fri, 15 Apr 2011 15:36:35 +0100 > From: Tony Finch <dot(a)dotat.at> > Subject: Re: 365x24x7 > To: harbor235 <harbor235(a)gmail.com> > Cc: NANOG list <nanog(a)nanog.org> > Message-ID: > <alpine.LSU.2.00.1104151530010.19442(a)hermes-2.csi.cam.ac.uk> > Content-Type: TEXT/PLAIN; charset=US-ASCII > > harbor235 <harbor235(a)gmail.com> wrote: > > > If I were going to provide a 365x24x7 NOC, how many teams of personnel > > do I need to fully cover operations? > > Hours in the working year = 8 * 5 * 48 = 1920 > Hours in the calendar year = 24 * 7 * 52 = 8736 > Ratio = 4.55 > > Tony. > -- > f.anthony.n.finch <dot(a)dotat.at> http://dotat.at/ > Rockall, Malin, Hebrides: South 5 to 7, occasionally gale 8 at first in > Rockall and Malin, veering west or northwest 4 or 5, then backing southwest 5 > or 6 later. Rough or very rough. Occasional rain. Moderate or good, > occasionally poor. > > > > ------------------------------ > > Message: 11 > Date: Fri, 15 Apr 2011 10:52:02 -0400 > From: harbor235 <harbor235(a)gmail.com> > Subject: Re: 365x24x7 > To: NANOG list <nanog(a)nanog.org> > Message-ID: <BANLkTinLSBedu3hq8hg4ihjEMcOHHbRjGg(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Guys, > > Thanx alot, there is some great stuff here, also some stuff I had not > thought of. > > thanx again, > > Mike > > On Fri, Apr 15, 2011 at 10:36 AM, Tony Finch <dot(a)dotat.at> wrote: > > > harbor235 <harbor235(a)gmail.com> wrote: > > > > > If I were going to provide a 365x24x7 NOC, how many teams of personnel > > > do I need to fully cover operations? > > > > Hours in the working year = 8 * 5 * 48 = 1920 > > Hours in the calendar year = 24 * 7 * 52 = 8736 > > Ratio = 4.55 > > > > Tony. > > -- > > f.anthony.n.finch <dot(a)dotat.at> http://dotat.at/ > > Rockall, Malin, Hebrides: South 5 to 7, occasionally gale 8 at first in > > Rockall and Malin, veering west or northwest 4 or 5, then backing southwest > > 5 > > or 6 later. Rough or very rough. Occasional rain. Moderate or good, > > occasionally poor. > > > > > ------------------------------ > > Message: 12 > Date: Fri, 15 Apr 2011 05:52:13 -1000 > From: Paul Graydon <paul(a)paulgraydon.co.uk> > Subject: Re: 365x24x7 > To: nanog(a)nanog.org > Message-ID: <4DA869AD.9070202(a)paulgraydon.co.uk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 4/15/2011 3:14 AM, harbor235 wrote: > > If I were going to provide a 365x24x7 NOC, how many teams of personnel do I > > need > > to fully cover operations? I assume minimally you need 3 teams to cover the > > required > > 24 hr coverage, but there is off time and schedule rotation? > > > > thoughts, experience? > > > > Mike > > > For what it's worth, was part of a datacenter operations department that > had a 24x7 team. 4 shifts, 4 staff on each shift (1 was supervisor who > did same work as the rest, 1 'point of contact' who stayed in the office). > 4 days on, 4 days off, 12 hour shifts, 8-8. Shift teams would alternate > between day and night (so 4 day, 4 off, 4 night, 4 off, repeat ad > infinitum). During the day that was bolstered by 6 day-staff, Monday to > Friday, who would have a staggered start through the day (IIRC 2 start > at 8, 2 at 9, 2 at 11) > > > > ------------------------------ > > _______________________________________________ > NANOG mailing list > NANOG(a)nanog.org > https://mailman.nanog.org/mailman/listinfo/nanog > > End of NANOG Digest, Vol 39, Issue 46 > *************************************

10 10

Re: NANOG Digest, Vol 39, Issue 52
by Coy Hile 17 Apr '11

17 Apr '11

> >> Rotating shifts between daytime and nighttime is a horrible thing to >> do to your workers, both for their health and their attention span. > I wonder how well something like the following would work (seen in paid fire/EMS circles): 24 on, 48 off. But staff those 24 shifts with maybe 20% more than actually needed to provide minimum coverage. Of course, that all assumes that you can trust your guys to work out the dynamics of "hey, you watch for the next 30 while I take a break". -c

3 2

Easily confused...
by Michael Painter 16 Apr '11

16 Apr '11

Was trying to determine where this 'honolulu' speedtest was hosted: Tracing route to honolulu.speedtest.net [74.209.160.12] over a maximum of 30 hops: 1 22 ms * * 123.87.93.224 2 27 ms 29 ms 25 ms hawaiian-telcom-inc.gigabitethernet2-17.core1.lax2.he.net [184.105.134.170] 3 84 ms 90 ms 84 ms gige-g2-17.core1.lax2.he.net [184.105.134.169] 4 92 ms 98 ms 99 ms 10gigabitethernet7-3.core1.sjc2.he.net [184.105.213.5] 5 112 ms 114 ms 112 ms 10gigabitethernet4-3.core1.sea1.he.net [72.52.92.158] 6 113 ms 113 ms 114 ms six.netriver.net [206.81.80.160] 7 113 ms 113 ms 113 ms static-74-209-160-12.lynnwood.netriver.net [74.209.160.12] Trace complete. 123.87.93.224? inetnum: 123.64.0.0 - 123.95.255.255 netname: CTTNET country: CN descr: China TieTong Telecommunications Corporation

6 8