Upgrade Sequence · Command or Action Purpose Performallpre-upgradetasksthatapply toyoursite.SeePre-upgradeTasks. Step 1 Upgrade Guide for Cisco Unified Communications Manager and

Upgrade Sequence

• Standard Upgrade of Unified Communications Manager and IM and Presence Nodes, page 1

• Refresh Upgrade of Unified Communications Manager and IM and Presence Nodes, page 4

• Standard Upgrade of Unified Communications Manager Nodes Only, page 6

• Refresh Upgrade Of Unified Communications Manager Nodes Only, page 8

• Standard Upgrade of IM and Presence Nodes Only, page 10

• Refresh Upgrade of IM and Presence Nodes Only, page 13

• Parallel Upgrades, page 15

Standard Upgrade of Unified Communications Manager and IMand Presence Nodes

The table below lists the sequence that you must follow when you perform a standard upgrade of both theUnified Communications Manager and the IM and Presence applications.

Procedure

PurposeCommand or Action

Perform all pre-upgrade tasks that applyto your site. See Pre-upgrade Tasks.

Step 1

Upgrade Guide for Cisco Unified Communications Manager and IM and Presence Service, Release 11.5(1) 1

cucm_b_upgrade-guide-cucm-115_chapter_0100.pdf#unique_14


Do not make any configuration changes duringan upgrade. For example, do not changepasswords, perform LDAP synchronizations,or run any automated jobs until you havecompleted the upgrade on all nodes andperformed the post-upgrade tasks. Anyconfiguration changes that you make duringan upgrademay be lost, and some configurationchanges can cause the upgrade to fail.

Caution

We recommend that you suspend user synchronizationwith LDAP and do not resume synchronization until you

Stop all configuration tasks.Step 2

have completed the upgrade on all Cisco UnifiedCommunicationsManager nodes and all IM and PresenceService nodes.

Do not modify any of the IM and Presence Service serverentries on the Application Server or Server configurationpages of the Cisco Unified CM Administration interface.The IM and Presence Service upgrade processautomatically updates these entries on the Cisco UnifiedCommunications Manager cluster during the final stages(switch version) of the upgrade process.

Any manual modification of these entries during theupgrade process will result in data migration failuresbetween IM and Presence Service and Cisco UnifiedCommunications Manager. If such failures occur, youmust restart the entire upgrade process for both CiscoUnified Communications Manager and IM and PresenceService clusters.

The Unified Communications Manager publisher node isthe first node in the cluster.

Upgrade the Unified CommunicationsManager publisher node using one ofthe following methods:

Step 3

• Upgrade From a Local Source

• Upgrade From a Remote Source

Upgrade the Unified CommunicationsManager subscriber nodes using one ofthe following methods:

Step 4



Switch the first node (publisher node) to the upgradedpartition.

Switch the Software Version on the firstnode (publisher node).

Step 5

Upgrade Guide for Cisco Unified Communications Manager and IM and Presence Service, Release 11.5(1)2

Upgrade SequenceStandard Upgrade of Unified Communications Manager and IM and Presence Nodes







Switch the subscriber nodes to the upgraded partition.You can switch the subscriber nodes to the upgraded

Switch the Software Version on thesubscriber nodes.

Step 6

partition either all at once or one at a time, depending onyour site requirements.

Ensure that database replication is functioning betweenthe first node (the Unified Communications Managerpublisher node) and the subscriber nodes.

Verify that Database Replication isFunctioning

Step 7

Perform post-upgrade tasks for UnifiedCommunications Manager nodes. SeePost-Upgrade Tasks.

Step 8

The IM and Presence database publisher node is the firstnode in the IM and Presence cluster.

Upgrade the IM and Presence databasepublisher node using one of thefollowing methods:

Step 9



Upgrade the IM and Presencesubscriber nodes using one of thefollowing methods:

Step 10



Switch the software to the new software release on theIM and Presence database publisher node (the first IM

Switch the Software Version on the IMand Presence database publisher node.

Step 11

and Presence node). Wait until the first node hassuccessfully restarted and is at the sign in prompt beforeyou proceed to the next step.

On the IM and Presence subscriber node, switch thesoftware to the new software release. After the IM and

Switch the Software Version on the IMand Presence subscriber node.

Step 12

Presence subscriber node has restarted and has come backonline with the new software release, switch the softwarerelease on the next node. Wait until each of the nodes hassuccessfully restarted (is at the sign in prompt) before youproceed with the software switch on the next node. Repeatuntil the new software release is running on all nodes.

Replication takes 20-30 minutes on average, but it maytake longer depending on the size of the database.

Verify that Database Replication isComplete on IM and Presence nodes.

Step 13

Perform post-upgrade tasks for the IMand Presence Service. See Post-UpgradeTasks.

Step 14


Upgrade SequenceStandard Upgrade of Unified Communications Manager and IM and Presence Nodes















Refresh Upgrade of Unified Communications Manager and IMand Presence Nodes

The table below lists the sequence that you must follow when you perform a refresh upgrade of both theUnified Communications Manager and the IM and Presence applications.

Procedure



Step 1

Do not make any configuration changesduring an upgrade. For example, do notchange passwords, perform LDAPsynchronizations, or run any automated jobsuntil you have completed the upgrade on allnodes and performed the post-upgrade tasks.Any configuration changes that you makeduring an upgrade may be lost, and someconfiguration changes can cause the upgradeto fail.

Caution




Do not modify any of the IM and Presence Service serverentries on the Application Server or Server configurationpages of the Cisco Unified CMAdministration interface.The IM and Presence Service upgrade processautomatically updates these entries on the Cisco UnifiedCommunicationsManager cluster during the final stages(switch version) of the upgrade process.

Any manual modification of these entries during theupgrade process will result in data migration failuresbetween IM and Presence Service and Cisco UnifiedCommunications Manager. If such failures occur, youmust restart the entire upgrade process for both CiscoUnified CommunicationsManager and IM and PresenceService clusters.


Upgrade SequenceRefresh Upgrade of Unified Communications Manager and IM and Presence Nodes



For a list of the upgrade COP files that are required, seeObtain Upgrade Files

Install the required COP files on everyCiscoUnified CommunicationsManagernode in the cluster and then restart eachnode.

Step 3

The Unified Communications Manager publisher nodeis the first node in the cluster.

Upgrade the Unified CommunicationsManager publisher node using one of thefollowing methods:

Step 4



Upgrade the Unified CommunicationsManager subscriber nodes using one ofthe following methods:

Step 5




Switch the Software Version on the firstnode (publisher node). Wait until the firstnode has successfully restarted and is at

Step 6

the sign in prompt before you proceed tothe next step.



Step 7

partition either all at once or one at a time, dependingon your site requirements.

You can switch the subscriber nodes to theupgraded partition either all at once, or one ata time, depending on your site requirements.

Note



Step 8


Step 9


Install the required COP files on everyIM and Presence node in the cluster andrestart the nodes.

Step 10


Upgrade the IM and Presence databasepublisher node using one of the followingmethods:

Step 11



Upgrade SequenceRefresh Upgrade of Unified Communications Manager and IM and Presence Nodes















Switch the software to the new software release on theIM and Presence database publisher node (the first IM


Step 12

and Presence node). Wait until the first node hassuccessfully restarted and is at the sign in prompt beforeyou proceed to the next step.

Upgrade the IM and Presence subscribernodes using one of the followingmethods:

Step 13





Step 14

Presence subscriber node has restarted and has comeback online with the new software release, switch thesoftware release on the next node. Wait until each of thenodes has successfully restarted (is at the sign in prompt)before you proceed with the software switch on the nextnode. Repeat until the new software release is runningon all nodes.



Step 15


Step 16

Standard Upgrade of Unified Communications Manager NodesOnly

The table below lists the sequence that you must follow when you perform a standard upgrade of the UnifiedCommunications Manager nodes in your network. When you upgrade Unified Communications Managernodes without upgrading IM and Presence nodes, ensure that the installed version of the IM and PresenceService is compatible with the new version of the Unified Communications Manager software.


Upgrade SequenceStandard Upgrade of Unified Communications Manager Nodes Only










When Cisco Unified Communications Manager 10.0(x) is upgraded as part of a service update or amaintenance release, Cisco Sync Agent sends a notification to Cisco Unified CM IM and PresenceAdministration that the IM and Presence Service database publisher node and subscriber nodes must berebooted. You must manually clear this notification after the reboots are complete. A warning messageabout the upgrade is also raised in the Cisco Unified Communications Manager OS Administration GUI.

Note

Procedure


Perform all pre-upgrade tasks that apply toyour site. See Pre-upgrade Tasks.

Step 1


Caution

We recommend that you suspend user synchronizationwith LDAP and do not resume synchronization until


you have completed the upgrade on all Cisco UnifiedCommunications Manager nodes and all IM andPresence Service nodes.

Do not modify any of the IM and Presence Serviceserver entries on the Application Server or Serverconfiguration pages of the Cisco Unified CMAdministration interface. The IM and Presence Serviceupgrade process automatically updates these entries onthe Cisco Unified Communications Manager clusterduring the final stages (switch version) of the upgradeprocess.

Any manual modification of these entries during theupgrade process will result in data migration failuresbetween IM and Presence Service and Cisco UnifiedCommunications Manager. If such failures occur, youmust restart the entire upgrade process for both CiscoUnifiedCommunicationsManager and IM and PresenceService clusters.

The Unified CommunicationsManager publisher nodeis the first node in the cluster.


Step 3



Upgrade SequenceStandard Upgrade of Unified Communications Manager Nodes Only





Upgrade the Unified CommunicationsManager subscriber nodes using one of thefollowing methods:

Step 4




When you have completed the upgrade ofall the subscriber nodes,Switch theSoftware Version on the first node(publisher node).

Step 5

You can switch the subscriber nodes to the upgradedpartition either all at once or one at a time, dependingon your site requirements.

When the publisher node is switched to thenew version,Switch the Software Versionon the subscriber nodes.

Step 6



Step 7


Step 8

If you upgraded Cisco UnifiedCommunications Manager to a

Step 9

Maintenance Release (MR) or anEngineering Special (ES) Release and youdo not upgrade the IM and PresenceService, you must reboot all IM andPresence nodes after the UnifiedCommunications Manager upgrade iscomplete.

Refresh Upgrade Of Unified Communications Manager NodesOnly

The table below lists the sequence that you must follow when you perform a refresh upgrade of UnifiedCommunications Manager nodes only. When you upgrade Unified Communications Manager nodes withoutupgrading IM and Presence nodes, ensure that the installed version of the IM and Presence Service is compatiblewith the new version of the Unified Communications Manager software.


Upgrade SequenceRefresh Upgrade Of Unified Communications Manager Nodes Only










Procedure



Step 1


Caution

We recommend that you suspend user synchronizationwith LDAP and do not resume synchronization until


you have completed the upgrade on all Cisco UnifiedCommunications Manager nodes and all IM andPresence Service nodes.

Do not modify any of the IM and Presence Serviceserver entries on the Application Server or Serverconfiguration pages of the Cisco Unified CMAdministration interface. The IM and Presence Serviceupgrade process automatically updates these entries onthe Cisco Unified Communications Manager clusterduring the final stages (switch version) of the upgradeprocess.



Install the required COP files on everyCisco Unified Communications Managernode in the cluster and then restart eachnode.

Step 3



Step 4




Upgrade SequenceRefresh Upgrade Of Unified Communications Manager Nodes Only






Upgrade the Unified CommunicationsManager subscriber nodes using one of thefollowing methods:

Step 5




Switch the Software Version on the firstnode (publisher node). Wait until the firstnode has successfully restarted and is at

Step 6

the sign in prompt before you proceed tothe next step.



Step 7

partition either all at once or one at a time, dependingon your site requirements.

You can switch the subscriber nodes to theupgraded partition either all at once, or one ata time, depending on your site requirements.

Note



Step 8


Step 9

If you upgraded Unified CommunicationsManager to a Maintenance Release (MR)

Step 10

or an Engineering Special (ES) Releaseand you do not upgrade IM and PresenceService, you must reboot all IM andPresence nodes after the UnifiedCommunications Manager upgrade iscomplete.

Standard Upgrade of IM and Presence Nodes OnlyThe table below lists the sequence that you must follow when you perform a standard upgrade of the IM andPresence nodes in your network without upgrading Unified Communication Manager subscriber nodes.

When you upgrade IM and Presence nodes without upgrading Unified Communication Manager subscribernodes, ensure that the installed version of Unified CommunicationManager is compatible with the new versionof the Unified Communication Manager software. The software version of the first IM and Presence node(the IM and Presence database publisher node) must match the first two numbers of the software version


Upgrade SequenceStandard Upgrade of IM and Presence Nodes Only








installed on the Unified Communications Manager publisher node. For example, IM and Presence Servicesoftware version 10.0.1.10000-1 is compatible with Cisco Unified CommunicationsManager software version10.0.1.30000-2.

Procedure



Step 1


Caution




Do not modify any of the IM and Presence Service serverentries on the Application Server or Server configurationpages of the Cisco Unified CMAdministration interface.The IM and Presence Service upgrade processautomatically updates these entries on the Cisco UnifiedCommunicationsManager cluster during the final stages(switch version) of the upgrade process.




Step 3










Upgrade the IM and Presence databasepublisher node using one of the followingmethods:

Step 4



Upgrade the IM and Presence subscribernodes using one of the followingmethods:

Step 5



Wait until each of the nodes has successfully restartedand is at the sign in prompt before you proceed with the

Switch the Software Version You mustswitch the software to the upgradedversion in the following order:

Step 6

software switch on the next node. Repeat until the newsoftware release is running on all nodes.

• Switch the software on the UnifiedCommunicationsManager publishernode.

• Switch the software on the IM andPresence database publisher node.

• Switch the software on the IM andPresence subscriber nodes.



Step 7

Perform post-upgrade tasks for the IM andPresence Service. See Post-Upgrade Tasks.

Step 8

In the event of an IM and Presence upgrade failure

If the upgrade of the Cisco Unified Communications Manager node is successful but the upgrade of IM andPresence nodes fails, you must either:

• perform another upgrade of both the Cisco Unified Communications Manager nodes and the IM andPresence nodes after you address the issues that caused the failure

• perform a DRS restore on the Cisco Unified Communications Manager node where the backup wastaken from to restore it to the configuration it had before the attempted upgrade of the IM and Presencenodes











Refresh Upgrade of IM and Presence Nodes OnlyThe table below lists the sequence that you must follow when you perform a refresh upgrade of the IM andPresence nodes in your network without upgrading Cisco Unified CommunicationManager subscriber nodes.When you upgrade IM and Presence nodes without upgrading Cisco Unified Communications Managersubscriber nodes, ensure that the installed version of Cisco Unified Communications Manager is compatiblewith the new version of the IM and Presence Service software.

Procedure



Step 1

Do not make any configuration changes duringan upgrade. For example, do not changepasswords, perform LDAP synchronizations,or run any automated jobs until you havecompleted the upgrade on all nodes andperformed the post-upgrade tasks. Anyconfiguration changes that you make during anupgrade may be lost, and some configurationchanges can cause the upgrade to fail.

Caution



have completed the upgrade on all Cisco UnifiedCommunications Manager nodes and all IM and PresenceService nodes.

Do not modify any of the IM and Presence Service serverentries on the Application Server or Server configurationpages of the Cisco Unified CM Administration interface.The IM and Presence Service upgrade processautomatically updates these entries on the Cisco UnifiedCommunications Manager cluster during the final stages(switch version) of the upgrade process.

Any manual modification of these entries during theupgrade process will result in data migration failuresbetween IM and Presence Service and Cisco UnifiedCommunicationsManager. If such failures occur, youmustrestart the entire upgrade process for both Cisco UnifiedCommunications Manager and IM and Presence Serviceclusters.


Install the required COP files on everyCisco Unified CommunicationsManager node in the cluster and thenrestart each node.

Step 3


Upgrade SequenceRefresh Upgrade of IM and Presence Nodes Only




The Unified Communications Manager publisher node isthe first node in the cluster.

Upgrade the Unified CommunicationsManager publisher node using one ofthe following methods:

Step 4



The Cisco Unified Communications Manager publishernodemust be running the new software before you upgradeeach IM and Presence subscriber node.

Switch the Software Version on the firstnode (publisher node). Wait until thefirst node has successfully restarted andis at the sign in prompt before youproceed to the next step.

Step 5


Upgrade the IM and Presence databasepublisher node using one of thefollowing methods:

Step 6



Switch the software to the new software release on the IMand Presence database publisher node (the first IM and


Step 7

Presence node). Wait until the first node has successfullyrestarted and is at the sign in prompt before you proceedto the next step.

Upgrade the IM and Presencesubscriber nodes using one of thefollowing methods:

Step 8





Step 9

Presence subscriber node has restarted and has come backonline with the new software release, switch the softwarerelease on the next node. Wait until each of the nodes hassuccessfully restarted (is at the sign in prompt) before youproceed with the software switch on the next node. Repeatuntil the new software release is running on all nodes.



Step 10


Step 11


Upgrade SequenceRefresh Upgrade of IM and Presence Nodes Only














In the event of an IM and Presence upgrade failure

If the upgrade of Cisco Unified Communications Manager nodes is successful but the upgrade of IM andPresence nodes fails, you must either:

• perform another upgrade of both the Cisco Unified Communications Manager nodes and the IM andPresence nodes after you address the issues that caused the failure

• perform a DRS restore on the Cisco Unified Communications Manager node where the backup wastaken from to restore it to the configuration it had before the attempted upgrade of the IM and Presencenodes

Parallel UpgradesThe table below lists the sequence that you must followwhen you want to upgrade nodes in a cluster in parallel.

You can begin upgrading subscriber nodes after the publisher node has finished upgrading. If you are performinga refresh upgrade, there will be a temporary server outage until all subscriber nodes get upgraded to the newsoftware version.

Procedure


Perform all pre-upgrade tasks that apply to your site. See Pre-upgrade Tasks.Step 1


Upgrade SequenceParallel Upgrades



Do not makeanyconfigurationchangesduring anupgrade. Forexample, donot changepasswords,performLDAPsynchronizations,or run anyautomatedjobs until youhavecompleted theupgrade on allnodes andperformed thepost-upgradetasks. Anyconfigurationchanges thatyou makeduring anupgrade maybe lost, andsomeconfigurationchanges cancause theupgrade tofail.

Caution

We recommend that yoususpend user


synchronization withLDAP and do notresume synchronizationuntil you havecompleted the upgradeon all Cisco UnifiedCommunicationsManager nodes and allIM and PresenceService nodes.

Do not modify any ofthe IM and Presence




Service server entries onthe Application Serveror Server configurationpages of the CiscoUnified CMAdministration interface.The IM and PresenceService upgrade processautomatically updatesthese entries on theCisco UnifiedCommunicationsManager cluster duringthe final stages (switchversion) of the upgradeprocess.

Any manualmodification of theseentries during theupgrade process willresult in data migrationfailures between IM andPresence Service andCisco UnifiedCommunicationsManager. If such failuresoccur, you must restartthe entire upgradeprocess for both CiscoUnifiedCommunicationsManager and IM andPresence Serviceclusters.

The UnifiedCommunications

Upgrade the Unified Communications Manager publisher node using one ofthe following methods:

Step 3

Manager publisher node• Upgrade From a Local Source is the first node in the

cluster.• Upgrade From a Remote Source

View the installation log to monitor the status of the upgrade by using theSoftware Installation/Upgrade window in Cisco Unified Communications

Step 4

Operating System Administration or by using the command line interface(CLI).

• List the install log:






file list install install_* dateinstall_log_2008-10-01.09.41.57.loginstall_log_2008-10-08.12.59.29.loginstall_log_2008-10-14.09.31.06.logdir count = 0, file count = 3

• Search the most recent install log for the string PRODUCT_VERSION;for example:

admin:file search installinstall_log_2013-01-07.09.39.11.logPRODUCT_VERSION

Searching path:/var/log/install/install_log_2013-01-07.09.39.11.logSearching file:/var/log/install/install_log_2013-01-07.09.39.11.log01/07/2013 09:53:54 post_upgrade|PRODUCT_VERSIONis 9.1.1.10000-11|<LVL::Info>01/07/2013 09:53:54post_upgrade|PRODUCT_VERSION_DISPLAY is9.1.1.10000-11|<LVL::Info>Search completed

When the upgrade on the publisher node is complete, begin the upgrade onthe subscriber nodes using one of the following methods:

Step 5



Activate the newsoftware on thepublisher node.

Switch the Software Version on the publisher node:Step 6

Activate the newsoftware on thesubscriber nodes.

Switch the Software Version on the subscriber nodes.Step 7







Documents

Upgrade Sequence · Command or Action Purpose Performallpre-upgradetasksthatapply toyoursite.SeePre-upgradeTasks. Step 1 Upgrade Guide for Cisco Unified Communications Manager and