[c-nsp] OT: Enterprise (Not ISP) Maintenance Windows

Mohamed A. Monsef Abbas m.abdelmonsef at gmail.com
Fri Sep 26 18:19:32 EDT 2014

Dear friend,
Yes we track every change for example Iwas working for national railways
company we schedule any a time for any change same case was in the bank and
same case in the partner I am working now never go with risk in your
network network down will effect the e-mail where the CEO monitor the
activities from it so he will start shouting. And net engineer got in
troubles after that.
Best timing
Trasportation weekend at night after 1 Am till 8 AM
Banking after business hours for changes which will take maximum 4 hours in
case huge change will take 7 or 8 hours in weekend late time so you gain
the 2 days off

This best practise is my personal decisions while serving in these
companies so think before giving a decision claculate your risk which risk
can be accepted by managment the finance guys (they are the stupids and
they don't understand what we do, they think the can buy anything)

CCIE #37569
On Sep 26, 2014 11:51 PM, "Scott Voll" <svoll.voip at gmail.com> wrote:

> For those of you working in an enterprise, company, agency, etc.  Do you
> have a standard (network) maintenance windows?
> If so, when?  How often?  Can you schedule anything in it, or if it will
> cause an outage does it need to go through 3+ layers of meetings and buy
> off to get it approved before you can schedule it?
> I'm just trying to understand what the norm is, "in the real world".
> Thanks
> Scott
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

More information about the cisco-nsp mailing list