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

Lelio Fulgenzi lelio at uoguelph.ca
Tue May 28 14:02:47 EDT 2019


Personally, I hate the fact that IM&P can’t be restarted without first disabling HA. So basically, if you have an unattended restart, you have to go in and make configuration changes.

Yuck.

---
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 12:46 PM
To: Lelio Fulgenzi <lelio at uoguelph.ca>; 'Bill Talley' <btalley at gmail.com>
Cc: 'voyp list, cisco-voip' <cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] IM&P Upgrade Steps during CUCM upgrade

Yeah, I HATE this bug.  Why in the world can’t the docwiki or what ever it’s called be updated quicker than a bug be filed/made universally known, and who came up with these recommendations TAC or the BU.

But I have seem IMP just not start services, and adding resources magic fix it.

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 9:46 AM
To: Bill Talley <btalley at gmail.com<mailto:btalley at gmail.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


In the words of the immortal Chris Farley….

holy schnikes

If possible, it is recommended to have 4vCPU and 8 GB RAM as we are seeing more cases with high CPU due to resources related.

They want 4 vCPU if possible? They think these things grow on trees? 😊

Right now, our two IMP servers are at 2 vCPU and 4GB of RAM. (5000 user OVA).

I’ll have to see about coordinating this change as well. We don’t have a lot of capacity/activity on these servers, so I think we should be OK for now.

Funny thing – Bug updated May 20, 2019, but virtualization docs still show old OVA information.

---
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: Bill Talley <btalley at gmail.com<mailto:btalley at gmail.com>>
Sent: Tuesday, May 28, 2019 11:08 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

That’s the process I typically follow without issues.

Also, I can’t recall if this was posted here, but wanted to make sure you’ve seen the recent changes to resource requirements for IM&P.   This may not apply to you if you have more than 5000 users.

IM&P VM resource requirements needs to be updated
CSCvk65006
Description
Symptom:
IM&P version 11.5.1.x or 12.0.1.x installed using one of the following configuration:
150 users (Full UC) 1vCPU 2 GB RAM
1,000 users (Full UC) 1vCPU 4 GB RAM
5,000 users (Full UC) 2vCPU 4 GB RAM

Customers with any of the above configuration might notice an increase use of CPU and Memory resources.

This can be fixed by manually increasing the resources according to the table below:
150 users (Full UC) 2vCPU 8 GB RAM
1,000 users (Full UC) 2vCPU 8 GB RAM
5,000 users (Full UC) 2vCPU 8 GB RAM

Conditions:
Performance Issues

Workaround:
Manually increase resources according to the table below:
150 users (Full UC) 2vCPU 8 GB RAM
1,000 users (Full UC) 2vCPU 8 GB RAM
5,000 users (Full UC) 2vCPU 8 GB RAM

If possible, it is recommended to have 4vCPU and 8 GB RAM as we are seeing more cases with high CPU due to resources related.




Sent from an iOS device with very tiny touchscreen input keys.  Please excude my typtos.

On May 28, 2019, at 8:47 AM, 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

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><mailto:lelio at uoguelph.ca>

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

[University of Guelph Cornerstone with Improve Life tagline]
<winmail.dat>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190528/ceecaab2/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/ceecaab2/attachment.png>


More information about the cisco-voip mailing list