Before You Begin
Caution |
Stop all configuration tasks. Do not make any configuration changes during an upgrade. For example, do not change passwords, perform LDAP synchronizations, or run any automated jobs. Do not remove, re-add, or reinstall any nodes in the cluster during the upgrade process. You can make configuration changes only when you have completed the upgrade on all nodes and performed the post-upgrade tasks. Any configuration changes that you make during an upgrade will be lost, and some configuration changes can cause the upgrade to fail. We recommend that you suspend user synchronization with LDAP and do not resume synchronization until you have completed the upgrade on all Unified Communications Manager nodes and all IM and Presence Service Service nodes. |
Caution |
During a Refresh Upgrade, traffic is no longer processed and several reboots are required, therefore, you must perform a refresh upgrade during a maintenance window. |
Note |
If you use RTMT as a monitoring tool and have a mega cluster deployment, Cisco recommends high-availability setup for RTMT to avoid any connectivity loss during Simple Upgrade. Following are the steps to setup high availability for RTMT Monitoring:
|
Note |
During the switch version, only User Facing features (UFF) in dynamic tables (numplandynamic, devicedynamic, and more) gets updated. Other tables are migrated during upgrade. Any configuration changes after the upgrade or before the switch versions are lost. |
Note |
The system checks for any existing phone service URLs during upgrade and automatically appends “&EMCC=#EMCC#” if it does not find any phone service URLs. As a result, any phones that do not support EMCC may encounter issues trying to login to Extension Mobility. The appended “&EMCC=#EMCC#” can be removed after upgrade if Unified Communications Manager contains any legacy or third-party devices which does not support EMCC |