cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
671
Views
0
Helpful
4
Replies

PCD uograde pre-req steps ( disable EM, disable HA IM&P, chnages as per OVA

shaftstri
Level 1
Level 1

IF using PCD 10.5 to upgrade CUCM and IM&P from 9.1 to 10.5

 

Do you still need to do the following or will PCD do it all

  1. Disable Extension Mobility in CUCM (  will PCD do it?)
  2. Disble HA in IM&P  ( Will PCD do it)
  3. Change vNICs from flexible to vmxnet3  ( I noticed on one upgrade PCD didn't change vNIC)
  4. Change OS to 64 bit

Thanks

1 Accepted Solution

Accepted Solutions

Manish Gogna
Cisco Employee
Cisco Employee

The manual steps which are not a part of installation or upgrade through iso image will need to be done by the administrator. I also want to add that for upgrades to CUCM 10.x version there is no need to disable extension mobility.

https://tools.cisco.com/bugsearch/bug/CSCus10292/?reffering_site=dumpcr

Symptom:
This is a Documentation Defect :
========================

##############################
In pre-10.x versions of CUCM, the upgrade guide specifies that EM services need to be disabled prior to upgrade. This was specified for DB reasons. The DB team has informed us that this requirement is no longer necessary after 10.x.
##############################


From: 10.0.1 upgrade guide:

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/10_0_1/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100.pdf
On page 44, under step 8, item c):

"Disable the Cisco Extension Mobility service by navigating to Cisco Unified Serviceability > Tools > Service Activation. For more information, see the Cisco Unified Serviceability Administration Guide.
Note that when you deactivate the Cisco Extension Mobility service, Cisco Extension Mobility users cannot log in and log out of phones that supp

Conditions:
no need to disable EM service during upgrades after 10.x

 

HTH

Manish
 

View solution in original post

4 Replies 4

Manish Gogna
Cisco Employee
Cisco Employee

The manual steps which are not a part of installation or upgrade through iso image will need to be done by the administrator. I also want to add that for upgrades to CUCM 10.x version there is no need to disable extension mobility.

https://tools.cisco.com/bugsearch/bug/CSCus10292/?reffering_site=dumpcr

Symptom:
This is a Documentation Defect :
========================

##############################
In pre-10.x versions of CUCM, the upgrade guide specifies that EM services need to be disabled prior to upgrade. This was specified for DB reasons. The DB team has informed us that this requirement is no longer necessary after 10.x.
##############################


From: 10.0.1 upgrade guide:

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/10_0_1/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100.pdf
On page 44, under step 8, item c):

"Disable the Cisco Extension Mobility service by navigating to Cisco Unified Serviceability > Tools > Service Activation. For more information, see the Cisco Unified Serviceability Administration Guide.
Note that when you deactivate the Cisco Extension Mobility service, Cisco Extension Mobility users cannot log in and log out of phones that supp

Conditions:
no need to disable EM service during upgrades after 10.x

 

HTH

Manish
 

Hi

PCD is will only perform Upgrade will not disable or change listed items, those are manual process.

HTH,

Regards,

Mohammed Noor

Jaime Valencia
Cisco Employee
Cisco Employee

Just to clarify what you're asking, upgrade, as an in-place upgrade, same VM, PCD will not do anything besides loading the ISO and performing the upgrade, any pre-reqs like COP files, making sure enough space is available, etc, are manually done, and after the upgrade, any VM changes, are manually done.

If you're actually asking about a migration, then you forget about the pre-reqs and changes to the VM as PCD will install a fresh image to then just import your info.

HTH

java

if this helps, please rate

I have just had a failed upgrade from 8.6.2 to 10.5.2. The process hung at the end of the Install Software phase and although the new Publisher appeared in good shape the process never went to the Import User-Facing Features Data. Was there a pre req we missed that could have caused this?

ps hate the 5 hour timeout period.