[c-nsp] Maintenance - Change Management Policies

[christopher.a.kane at jpmchase.com]

>Standing window ranges always tend to be the middle ground between COB 
and 
>SOB (that's start of business, smartasses.) This is generally because 
it's 
>lowest impact on the periods where it costs the least. You don't want to 
>do it during normal business hours, as it impacts incoming revenue 
streams 
>when paid staff will be unable to function. 

Totally agree with the at-the-best-time-for-the-business point. 
Unfortunately, what may be a good time for one division/business unit/line 
of business is not a good time for another. 

Then there are those situations in which 'impact' or 'potential impact' 
(you know, a simple act such as walking by the router) may cause complete 
routing failure for 20 minutes while convergence takes place. 

How careful should one be? Hey, I'm only adding a name to this existing 
VLAN...but, yes the switch may choke at anytime. Therefore, assume 
complete outage time during the implementation of my seemingly benign 
change.

-chris


>- billn


On Fri, 13 Oct 2006, christopher.a.kane at jpmchase.com wrote:

>> Our collective NSP/ISP experiences show that emphatically advertising 
>> standing maintenance windows provided for great flexibility when it 
came 
>> to configuration changes and cleanups. Does 0300-0600 Local sound 
>> familiar?
>> 
>> For those of us within the Enterprise space and dealing with 
>> infrastructures between 5,000 to upwards of 20,000 nodes - I'm curious 
to 
>> know the various flavors of maintenance schedules. I'd like to hear 
about 
>> your current processes, what works and what the challenges are. Do you 
>> have standing windows globally, per Business Unit, per portion of the 
>> infrastructure?
> 
>> If you care to respond off-list, I can compile and post. 
>> 
>> Thanks,
> -chris
> 



-----------------------------------------
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law.  If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED.  Although this transmission and
any attachments are believed to be free of any virus or other
defect that might affect any computer system into which it is
received and opened, it is the responsibility of the recipient to
ensure that it is virus free and no responsibility is accepted by
JPMorgan Chase & Co., its subsidiaries and affiliates, as
applicable, for any loss or damage arising in any way from its use.
If you received this transmission in error, please immediately
contact the sender and destroy the material in its entirety,
whether in electronic or hard copy format. Thank you.