[33864] in North American Network Operators' Group
Re: Maintenance Windows for Networks Spanning Multiple Time Zones
daemon@ATHENA.MIT.EDU (bmanning@vacation.karoshi.com)
Wed Jan 24 20:51:17 2001
From: bmanning@vacation.karoshi.com
Message-Id: <200101250037.AAA15090@vacation.karoshi.com>
To: kurtis@kurtis.pp.se (Kurt Erik Lindqvist)
Date: Thu, 25 Jan 2001 00:37:06 +0000 (UCT)
Cc: Valdis.Kletnieks@vt.edu, brett.hawn@rcn.com (Brett L. Hawn),
nanog@merit.edu
In-Reply-To: <Pine.LNX.4.05.10101240917470.25571-100000@tankgirl.kurtis.pp.se> from "Kurt Erik Lindqvist" at Jan 24, 2001 09:20:18 AM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu
> > On Mon, 22 Jan 2001 17:20:03 EST, "Brett L. Hawn" said:
> > > Pardon my intrusion, but common sense tells me: at a time where you will
> > > have the least amount of impact on the least amount of people.
> >
> > I'll play devil's advocate here. Do you want to minimize the impact on
> > the end users, or the number of phone calls generated to the NOC? ;)
> >
>
> One of doing this is to split into several zones. We have one for US work,
> one for transatlantic and one for Europe. This increases the complexity
> but tends to lower the impact per maintenace session.
>
> - kurtis -
Too complex. Back in the Day... :)
We scheduled our maintaince windows between 09:00 and 10:00 local time.
Our techs were awake, we could get vendors on the phone and parts shipped
if needed.
--bill
