Amount of Time to patch CMS for DST?

[Stinney]

Has anyone had the patch for CMS DST done?

What system do you have and how long did it take?

We're being told that it will be 4hrs of hard down time for the patch to be done. This seems a little excessive for a patch install.

We have:

CMS r13
Sun V880

Any information would be appreciated.

- Stinney

Favorite all too common vendor response: "We've never seen this issue before.

 

[FicBen]

I was told 6 hours. Avaya suggested manually changing the time.

 

[4merAvaya]

We've done 4 so far. About 6 hours (including backups).

Kevin

 

[CBB]

About 3 hours not including backups on both a R12 and R13

 

[dfalken]

I did mine with two full maintenance backups in 4 hours.

 

[telm59]

I must be doing something wrong took me 5 minutes.
rel 2.2.0

 

[lisalisa173]

For CMS
Our Solar patch upgrade took almost 3 hours just to load. We did the complete the upgrade but ran into operational hours. We stopped after the first Solar upgrade and started the next night for the remainder of the upgrade.
You are basically installing the back bone Unix Part of CMS again.
Be sure you have back up before you start.. total time was about 6 hours. Don't give yourself less if you need to load the whole thing not just the last piece. You'll get burnt.
lisa

 

[rgtrgt]

isnt it easier to just change the time 4 times a year?

 

[Stinney]

Not when you hav3 15+ systems to change.

At my old job, with just 1 CMS, 2 - 8700's, 2 Prologix, 3 - VM, maybe.

I appreciate all of your imput. Our lab CMS (SUN 150) will be patched today and our production CMS (V880) tomorrow. I'll let you know how well/bad things go and for how long.

- Stinney

Favorite all too common vendor response: "We've never seen this issue before.

 

[lisalisa173]

My old company has 200 systems they need to change..
Mostly magix, a few 8700 & cms but still -- I am happy i am not there anymore lol ..
Lisa

 

[rgtrgt]

without patching the solaris portion, am i still ok just changing the time manually?

 

[lopes1211]

I just dialed into a customer CMS to verify root access anticipating a manual DST adjustment and I see the unix time is currently 3 hours off. When looking at real time and historical data in CMS, everything is set to the correct (PBX) time and all appears fine. Is this whole patch nonsense just more Avaya smoke and mirrors?

I understand updating 15+ systems can be a pain but is the manual change 30 seconds x 15 sites x 4 times a year really more of a pain than a 6 hour upgrade / outage x 15 sites?

I'm recommending to all of my customers to manually change it and throw the time and money at an R14 release next year. After seeing what I saw on the system I dialed into today however, I'm wondering if anything at all needs to be done. This particular CMS was R3V6.

-CL

 

[wildcard100001]

6 8700's 2 8300's - 2 hours... though you could prep and have the patch already on the server ready to go. Which I did not.

Don't forget... you need shell access enabled on your pbx login...

As mikeydidit mentioned... you must do both A and B servers. Thanks again for the faq.

Thanks,

Wildcard

 

[Stinney]

4 1/2 hours for SUN 150 and V880, both r13.

Ran into some isues restarting visual vectors again on the SUN 150, but it did not effect anything while VV was trying to restart.

No issues with the V880 at all.

Thanks again to all of you who contributed.

- Stinney

Favorite all too common vendor response: "We've never seen this issue before.

 

[PhoneDataDude]

How do you manually change the time? I just checked our cms at the unix prompt, and it's off by over 20 minutes. CMS appears to get it's time from the switch. Am I wrong?

 

[phoneguy55]

PhoneDataDude

Look here.

http://support.avaya.com/japple/css/japple?PAGE=OpenPage&temp.template.name=DLT2007

 

[4merAvaya]

Login as root and enter 'date ddmmhhmm', where dd=day, mm=month, hh=hour (military time), and mm=minute.

Kevin

 

[rgtrgt]

They changed the CMS DST a little bit:

http://support.avaya.com/japple/css...tID=201940&temp.bucketID=162024&PAGE=Document

 

[rjblanch]

Can i ask a simple question regarding the DST change - if your CMS synch's time off the PABX and you change the time on PABX, then why do it on the CMS?

I have been doing DST changes now for the past 9 years in Australia and not once have I had to do anything with the CMS. Is this something special or have I missed the whole point?

 

[telcomwork]

Took me about 4.