[cisco-voip] IM&P Upgrade Steps during CUCM upgrade

Tue May 28 10:59:09 EDT 2019

I hear ya. I thought about that. But since we don’t do this very often, and we do have a window of opportunity, I wanted to take the safe approach.

I would hate to hit an undocumented feature that caused a service outage as part of upgrading the inactive partition.

---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

From: NateCCIE <nateccie at gmail.com>
Sent: Tuesday, May 28, 2019 10:37 AM
To: Lelio Fulgenzi <lelio at uoguelph.ca>; 'Ryan Huff' <ryanhuff at outlook.com>
Cc: 'voyp list, cisco-voip' <cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] IM&P Upgrade Steps during CUCM upgrade

Lelio,

Are you apposed to upgrading the inactive partition during working hours?  For my planning, the upgrade window starts when the bumps in service occur, which is usually the switch version.

There are some cases where the upgrade is not “online” there is a R1/R2 upgrade designation for this, where it is also upgrading the OS, but those are fairly rare.

Thanks,
-Nate

From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Lelio Fulgenzi
Sent: Tuesday, May 28, 2019 8:23 AM
To: Ryan Huff <ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>>
Cc: voyp list, cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>) <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] IM&P Upgrade Steps during CUCM upgrade

Sweet. Thanks. I need to map out the window I have and see how this all fits in.

I really hate how the version compatibility is _so_ tight with the IMP cluster now.  One more thing to have to worry about.

Oh well.

TAC just gave me some advice to see how long the DB replication would take after the switch version. Ahead of time, I do a “utils dbreplication status” and then “utils dbreplication runtimestate” until all tables show synced and take that time.

Does that sound about right?

---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

From: Ryan Huff <ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>>
Sent: Tuesday, May 28, 2019 10:04 AM
To: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
Cc: voyp list, cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>) <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] IM&P Upgrade Steps during CUCM upgrade

This is what I do for an in-place upgrade with no other changes (hostname, IP address.. etc).

I do the cucm pub first (obviously), then imp pub (which is more like a cucm sub for upgrade purposes), then all the cucm and imp subs; everything into the inactive pt.

I do the pubs individually, then I’ll do a couple subs at a time .. etc.

Next I Switch version on the pubs; cucm, imp then the subs.

On the switch version, I wait till one node is fully up (tomcat started) before switching another.

May not be as efficient as it could be, but has kept me out of trouble thus far; plan your dive, dive your plan.

On May 28, 2019, at 09:48, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:

I’m reading the upgrade guide, specifically, the time sequencing:

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/11_5_1/cucm_b_upgrade-guide-cucm-115/cucm_b_upgrade-guide-cucm-115_chapter_010010.html<https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cisco.com%2Fc%2Fen%2Fus%2Ftd%2Fdocs%2Fvoice_ip_comm%2Fcucm%2Fupgrade%2F11_5_1%2Fcucm_b_upgrade-guide-cucm-115%2Fcucm_b_upgrade-guide-cucm-115_chapter_010010.html&data=02%7C01%7C%7Cedf6cceff56c4271c0ea08d6e3732081%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636946480931843697&sdata=uVpiEsv2xfx%2BzhCSZXFn79Vxy0EjdGOv8xIE6YmbGYs%3D&reserved=0>

and it mentions upgrading the IM&P publisher (to inactive partition) at the same time as upgrading the subscribers. Then doing a switch version on the IMP pub at the same time as the CUCM subs.

Anyone do this parallel type upgrade before?

Sure would save a lot of time.

Lelio

---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<https://eur04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.uoguelph.ca%2Fccs&data=02%7C01%7C%7Cedf6cceff56c4271c0ea08d6e3732081%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636946480931843697&sdata=%2FFvRhe37xnrPEID%2FvmbygmM70chD2bcyHNPfQW4ZoLo%3D&reserved=0> | @UofGCCS on Instagram, Twitter and Facebook

<image001.png>

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7Cedf6cceff56c4271c0ea08d6e3732081%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636946480931803660&sdata=n96J0GwP3OzvowH3GaT0ql4dru%2FfLKIh4lIdTugoT8Y%3D&reserved=0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190528/1803e674/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1297 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190528/1803e674/attachment.png>