Upgrade Sequence and Time Requirements
The sequence in which you perform upgrade procedures depends on your deployment, and on how you want to balance the level of user impact with the amount of time required to complete the upgrade. You must identify the sequence that you will follow before you are ready to perform the upgrade process.
The information in this section applies only if you are performing a direct upgrade using either the Unified CM OS Administration interface or the PCD Upgrade task. PCD Migrations do not require this step.
Understanding Version Switching
When you upgrade a node, the new software is installed as an inactive version. To activate the new software, you must switch the node to the new software version. There are two ways to switch to the new software version:
-
Automatic switching—the system switches the version automatically as part of the upgrade process
-
Manual switching—physically switch the version using the OS Administration interface after the upgrade process is complete
The method that you choose depends on the type of upgrade that you are doing. During the upgrade process, the wizard prompts you to choose whether to switch the software version automatically by rebooting to the upgraded partition, or whether to switch the version manually at a later time. The table below lists the switching method to use for each type of upgrade.
Upgrade type |
Switching type |
When prompted, choose . . . |
Result |
---|---|---|---|
Standard upgrade |
Automatic |
GUI: Reboot to upgraded partition CLI: Switch to new version after upgrade |
When you choose this option, the system reboots to the new software version. |
Manual |
GUI: Do not reboot after upgrade CLI: Do not switch to new version after upgrade |
When you choose this option, the system continues to run the old software version when the upgrade is complete. You can manually switch to the new software later. |
|
Refresh upgrade |
Automatic |
GUI: Reboot to upgraded partition CLI: Switch to new version after upgrade |
Choose this option to use the new software version immediately following the upgrade. |
Manual |
GUI: Do not reboot after upgrade CLI: Do not switch to new version after upgrade |
Use this option only if you are performing a refresh upgrade in stages. When you choose this option the system reboots to the old software version when the upgrade is complete, and you can manually switch to the new software later. |
When you switch versions, your configuration information migrates automatically to the upgraded version on the active partition.
If for any reason you decide to back out of the upgrade, you can restart the system to the inactive partition that contains the older version of the software. However, any configuration changes that you made since you upgraded the software will be lost.
For a short period of time after you install Unified Communications Manager or switch over after upgrading to a different product version, any changes made by phone users may be lost. Examples of phone user settings include call forwarding and message waiting indication light settings. This can occur because Unified Communications Manager synchronizes the database after an installation or upgrade, which can overwrite phone user settings changes.
Recommended Sequence (Refresh Upgrades)
The following table shows the recommended sequence for performing a refresh upgrade. This method provides the least time and impact for the upgrade.
Sequence |
Unified Communications Manager Nodes |
IM and Presence Service Nodes |
---|---|---|
1 |
Upgrade the publisher node to the new software version. The new software is inactive. |
— |
2 |
Upgrade the secondary subcriber nodes in parallel. The new software is inactive. |
Upgrade the IM and Presence database publisher node in parallel with the Unified Communications Manager subscriber nodes. |
3 |
Upgrade the primary subscriber nodes |
Upgrade the subscriber nodes. The new software is inactive. |
4 |
Switch the software version on the publisher node and reboot it. The new software is active. |
— |
5 |
Switch the software version on the secondary subscriber nodes in parallel and reboot them. |
Switch the software version on the database publisher node and reboot it. The new software is active. |
6 |
Switch the software version on the primary subscriber nodes in parallel and reboot them. |
Switch the software version on the subscriber nodes in parallel and reboot them. The new software is active. |
7 |
Ensure that database replication is complete and functioning between the publisher node and all subscriber nodes before proceeding. |
Ensure that database replication is complete and functioning between the publisher node and all subscriber nodes. |
Sequence Rules
When you are planning to perform an upgrade using either the Unified CM OS Admin interface or the PCD upgrade task, you must ensure that your plan takes the following sequencing rules into account.
-
The Unified Communications Manager publisher node must be the first node that you upgrade. The new software is installed as an inactive version.
-
You can begin upgrading Unified Communications Manager subscriber nodes as soon as the publisher node has been upgraded with an inactive version of the new software.
-
You must switch the Unified Communications Manager publisher node to the new software version and reboot it before you switch the version on any subscriber nodes. The publisher node must be the first node to switch to the new software version and reboot.
-
If you upgrade a group of subscriber nodes, after you switch the software version and reboot, you must wait for database replication to complete on all subscriber nodes before proceeding with any COP file installs or configuration changes.
-
If you are upgrading Unified Communications Manager nodes to a Maintenance Release (MR) or an Engineering Special (ES) Release and you are not upgrading IM and Presence Service nodes, you must reboot all IM and Presence nodes after the Unified Communications Manager upgrade is complete.
-
If you are upgrading IM and Presence Service nodes in addition to Unified Communications Manager nodes:
-
The IM and Presence Service database publisher node must be the first IM and Presence Service node that you upgrade. The new software is installed as an inactive version.
-
You can begin upgrading IM and Presence Service subscriber nodes as soon as the publisher node has been upgraded with an inactive version of the new software.
-
You can wait until all of the Unified Communications Manager nodes are upgraded to an inactive version before you upgrade the IM and Presence Service database publisher node, or you can choose to upgrade in parallel. If you upgrade in parallel, start upgrading the IM and Presence Service database publisher node at the same time that you upgrade the Unified Communications Manager subscriber nodes.
-
You must switch to the new software version and reboot all Unified Communications Manager nodes, starting with the publisher node, before you can switch versions on the IM and Presence Service nodes.
-
You must switch the IM and Presence Service database publisher node to the new software version and reboot it before you switch the software version on any IM and Presence Service subscriber nodes.
-
If you upgrade a group of IM and Presence Service subscriber nodes, after you switch the software version and reboot, you must wait for database replication to complete on all subscriber nodes before proceeding.
-
-
If you are upgrading IM and Presence Service nodes to a Maintenance Release (MR) or an Engineering Special (ES) Release and you are not upgrading Unified Communications Manager nodes, the following additional sequencing rules apply:
-
For upgrades using the Unified CM OS Admin interface, you must upgrade the Unified Communications Manager publisher node and then upgrade the IM and Presence Service nodes to the Maintenance Release (MR) or an Engineering Special (ES) Release.
-
If you are using the Prime Collaboration Deployment migration task, you must select the Unified Communications Manager publisher node in addition to the IM and Presence Service nodes.
-
If you are using the Prime Collaboration Deployment upgrade task, you do not need to select the Unified Communications Manager publisher node as long as the first 3 digits of new version of IM and Presence Service match the first 3 digits of the currently installed version of Unified Communications Manager.
-