S8720, CM5 Update to SP3. Standby Refresh?

[TechJimF]

Stumped. I downloaded SP3 to both the active and standby servers. Unpacked it on the standby, deactivated SP1, activated SP3. Went to interchange the servers, got error stating that the standby server is not refreshed.

I rolled back to SP1 and saved translations. Status summary displayed standby refresh? yes. I thought i was in the clear so i went through the same process and got the standby server on SP3 again. Status summary now displayed standby refresh? no. So I saved translations again but this time got an error 'can not save to standby server' or something like that.

I guess my question is, how do I refresh the standby server other than saving translations and/or why am I getting the error in the first place? Is my process for updating the standby server wrong?

Any help is appreciated. Want to try again Thursday night.

Thanks,

Jim

 

[Mitch672]

The answer is simple: once you have a different patch on the standby and active servers, they will NEVER refresh. You must do a "forced interchange", and, your phone system will do a cold start. Sorry, but that's just how it is.

mitch


AVAYA Certified Specialist

 

[TechJimF]

Mitch,

So if the standby is at SP3 and the active is at SP1 and I force an interchange, both servers are going to reboot?

I thought that by having duplicated servers that the standby can be patched, interchange, then the original active then gets patched without the whole process being service affecting.

Jim

 

[mikeydidit]

Jim I am upgrading tonight going from 3.0.1 to 3.1.4 and its going to be service affecting. You are going to have to let it reboot for the new load to take effect. I am looking around 2 minuted downtime for it to come back up and start processing calls.

I understand that their is a patch that can make it not service effecting, but to load the patch takes a reset system 4, so it's going to happen either way.

"A people that values its privileges above its principles soon loses both."
- Dwight D. Eisenhower (1890-1969), Inaugural Address, January 20, 1953

For the best response to a question, read faq690-6594

 

[TechJimF]

Mikeydidit,

Your going to a different load, I'm only trying to put a service pack on CM 5.0, not trying to go to CM 5.1.1 for example.

If I force the interchange, then I'll be down for 2 minutes or so, all calls drop?

Do you know anything else about the patch? If I have to go down I rather put the patch in place so the next time I don't cause an outage.

Thanks,

Jim

 

[mikeydidit]

Product Correction Notice (PCN)
Issue Date: February 11, 2008
Archive Date: N/A
Supplement 2 Date: June 2, 2008
PCN Number: 1605P

Does applying this PCN
disrupt my service?
This service pack will disrupt service in that it requires a reset 4 to
take effect.

Sorry Jim I do not have the number for the patch. I learn this yesterday talking with a friend in Denver.

"A people that values its privileges above its principles soon loses both."
- Dwight D. Eisenhower (1890-1969), Inaugural Address, January 20, 1953

For the best response to a question, read faq690-6594

 

[Mitch672]

almost every single CM4, and now CM5 patch is a "cold patch" now, meaning, when the patch is applied, it reboots the system.

Once you force the interchange, your now patched standby server will become active, and once you now patch the former active server, they will sync up again...

You only end up reseting the system once, after the standby server is first patched, on the "forced interchange"

In the past, mos tof the patches where "hot patches", and didn't need a reboot, now tghey do, that's just the way the cookie crumbles.

mitch


AVAYA Certified Specialist

 

[TechJimF]

So all service is lost on the 'forced interchange' but that's it, correct? The outage is about 3 - 5 minutes?

Thanks,

Jim

 

[mikeydidit]

Jim I am not going to say how long your outage will last, but ours was around 45 seconds last night. The handshake and shadowing was not back up between the servers but it did start processing calls. Total time for both severs to come back up an happy, around two minutes.

"A people that values its privileges above its principles soon loses both."
- Dwight D. Eisenhower (1890-1969), Inaugural Address, January 20, 1953

For the best response to a question, read faq690-6594

 

[Tolson]

The outage will depend on how large of a system you have, how many media gateways you are running. In our Lab system the outage was long enough for the gateways to go into LSP mode although the switch was only out about 2 minutes. On our production system with 40 port networks the outage was much longer, close to 15 minutes before everything was back up and running with no errors. The trunk groups take the longest to come back and get themselves sorted out.