Post-upgrade Task Flow
Procedure
Command or Action | Purpose | |||||
---|---|---|---|---|---|---|
Step 1 |
If the cluster is in mixed mode, manually update the CTL file. Reset the phones to reflect the latest updates.
|
|||||
Step 2 |
Remove the serial port that you added during the pre-upgrade tasks so that it does not impact VM performance. Perform this procedure for all nodes. |
|||||
Step 3 |
If you deactivated Cisco extension mobility as part of the pre-upgrade tasks, you can now restart it. |
|||||
Step 4 |
Run the post upgrade COP. |
The post-upgrade COP runs a series of tests to verify system stability. These tests compare pre and post upgrade settings in order identify differences. After you complete all the steps in this table, run the post-upgrade COP file again and verify the COP report.
|
||||
Step 5 |
Reset TFTP parameters that are changed during the upgrade process. |
|||||
Step 6 |
Restore any Enterprise Parameter settings on IM and Presence Service nodes that may have been overwritten during the upgrade process. |
|||||
Step 7 |
Use this procedure to restore the high and low watermarks to their original values in order to avoid premature purging of traces. You can skip this task for PCD migrations. |
|||||
Step 8 |
You must update the VMWare Tools after you complete the upgrade. Perform this procedure for all nodes. |
|||||
Step 9 |
After an upgrade, you must reinstall any locales that you are using, with the exception of US-English, which is installed by default. Perform this procedure for all nodes. |
|||||
Step 10 |
Use this procedure if you increased the database replication timeout value before you began the upgrade process. Perform this procedure on Unified Communications Manager nodes only. |
|||||
Step 11 |
Use this procedure to verify your endpoints and resources on Unified CM nodes after the upgrade is complete. |
|||||
Step 12 |
Use this procedure to verify the number of assigned users on IM and Presence Service nodes after the upgrade is complete. |
|||||
Step 13 |
Verify phone functions and features are working correctly after the upgrade. |
|||||
Step 14 |
If you use Cisco Unified Real Time Monitoring Tool (RTMT), upgrade to the new software version. |
|||||
Step 15 |
Optional. Use this procedure to upload phone rings, callback tones, and backgrounds to a TFTP server so that they are available to Unfiied CM nodes. |
|||||
Step 16 |
Optional. For Unified CM nodes only, upload a text file that contains a customized log-on message. |
|||||
Step 17 |
If you are completing a PCD migration from Release 6.1(5), you must recreate your IPSec policies as they are not migrated to the new release. |
|||||
Step 18 |
If you had Manager Assistant deployed before the upgrade and users were assigned to the InterCluster Peer-User or Admin-CUMA roles, you must reassign users to roles, as these roles do not exist in the current release. |
|||||
Step 19 |
Use this procedure only if you performed an upgrade or migration from Cisco Unified Presence Release 8.x to an IM and Presence Service release. |
|||||
Step 20 |
If you disabled High Availability for the IM and Presence Service Service before the upgrade process, use this procedure to turn it back on. |
|||||
Step 21 |
If you stopped the IM and Presence Service Sync Agent service before you began the upgrade process, restart it now. |
|||||
Step 22 |
For the AXL Connection to be established after Unified Communications Manager upgrades, restart the CER service. You also need to restart the AXL Change notification toggle on the Unified CM publisher node. |
Switch the Software Version
When you perform a standard upgrade, the new software is installed as an inactive version. You can reboot to the new software during the upgrade process or you can switch to the new version later.
If you did not switch versions immediately after completing the upgrade, do so now. You must switch versions so that the upgrade is complete and all nodes in the cluster are updated. Do not perform a backup until you have switched to the new software version.
When you switch versions, the system restarts, and the inactive software becomes active. The system restart may take up to 15 minutes. When you perform this procedure both the active and inactive software versions are indicated.
Caution |
This procedure causes the system to restart and become temporarily out of service. |
Before you begin
The software versions on Unified Communications Manager and IM and Presence Service nodes must match according to the manual switching rules. Therefore, you must switch Unified Communications Manager before you switch IM and Presence Service.
Review the information in Understanding Version Switching
Procedure
Step 1 |
If you switch versions in a multinode deployment, you must switch the publisher node first. |
Step 2 |
Log in to the management software for the node that you are upgrading:
|
Step 3 |
Select . |
Step 4 |
Verify the version of the active software and the inactive software. |
Step 5 |
Select Switch Versions to switch versions and restart the system. |
After you perform a switch version when you upgrade Unified Communications Manager, IP phones request a new configuration file. This request results in an automatic upgrade to the device firmware.
Update CTL file
Note |
From Release 12.5(1)SU3 Update CTL is no longer required. |
Procedure
Step 1 |
Verify Unified Communications Manager Security Mode in .Locate the Cluster Security Mode field. If the value in the field displays as 1, Unified Communications Manager is configured for mixed mode. |
Step 2 |
Manually update CTL file. For more information on how to update CTL file, see Security Guide for Cisco Unified Communications Manager. |
Step 3 |
Reset the phones to reflect the updates. |
Remove the Serial Port
During the pre-upgrade tasks, you added a serial port to the virtual machine to capture the upgrade logs. After you have successfully upgraded the system, you must remove the serial port so that it does not impact the performance of the virtual machine.
Procedure
Step 1 |
Power off the virtual machine. |
Step 2 |
Edit the settings to remove the serial port. For information about how to edit the settings, see the VMWare documentation. |
Step 3 |
Power on the virtual machine and proceed with the post-upgrade tasks. |
Restart Extension Mobility
Upgrades from Release 9.x or earlier require you to stop Cisco extension mobility before you begin the upgrade process. If you deactivated Cisco extension mobility as part of your pre-upgrade tasks, use this procedure to restart the service on Unified Communications Manager nodes.
Procedure
Step 1 |
From Cisco Unified Serviceability, choose . |
Step 2 |
From the Server list, choose the node on which you want to deactivate services and click Go. |
Step 3 |
Select the Cisco Extension Mobility services. |
Step 4 |
Click Restart. |
Run Upgrade Readiness COP File (Post-upgrade)
After upgrading, run the post-upgrade COP file, which checks the following:
-
Installed COP Files
-
Network services and connectivity (DNS, NTP, intra-cluster)
-
FIPS mode password length restrictions
-
Licensing sync
-
VMware tools compatibility
-
Disk space
-
SIP and H.323 trunk registrations
-
Database authentication and replication status
-
Database sanity
-
Status of last DRS backup
-
Services status
-
Installed COPs and Locales
-
Device Registration Status Count
-
Enterprise Parameter and Service Parameter settings
-
TFTP Maximum Service Counts
-
Active and Inactive versions
Note |
It's strongly recommended that you run the Upgrade Readiness COP file for post-upgrade checks after you upgrade in order to verify the health of your system. |
Procedure
Step 1 |
Download the Upgrade Readiness COP file to run post upgrade tests.
|
Step 2 |
Check your post-upgrade system health:
|
Step 3 |
To view the reports from CLI for post-upgrade run file get install/PostUpgradeReport.txt command. |
Step 4 |
To view the report from RTMT
|
What to do next
Reset TFTP Parameters
During the upgrade process, the TFTP service parameter Maximum Serving Count is changed to allow for an increased number of device registration requests. Use this procedure to reset the parameter after the upgrade is complete.
Procedure
Step 1 |
From the Cisco Unified CM Administration interface, choose . |
Step 2 |
From the Server drop-down list, select the node that is running the TFTP service. |
Step 3 |
From the Service drop-down list, select Cisco TFTP service. |
Step 4 |
Click Advanced. |
Step 5 |
Click Save. |
Step 6 |
Set the Maximum Serving Count to the same value that you used prior to the upgrade, or to the value that is recommended for your configuration. The default value is 500. We recommend that you use the default value if you run the TFTP service with other Cisco CallManager services on the same server. For a dedicated TFTP server, use the following values:
|
Restore Enterprise Parameters
Some Enterprise Parameters exist on both Unified Communications Manager nodes and IM and Presence Service nodes. Where the same parameter exists, the settings that are configured on Unified Communications Manager nodes overwrite the settings configured on IM and Presence Service nodes during an upgrade. Enterprise Parameters that are unique to IM and Presence Service nodes are retained during an upgrade.
Use this procedure to reconfigure the settings on IM and Presence Service nodes that have been overwritten during the upgrade process.
Before you begin
Make sure you have access to the settings that you recorded as part of the pre-upgrade tasks.
Procedure
Step 1 |
From the Cisco Unified CM IM and Presence Administration interface, choose . |
Step 2 |
Compare the current settings to the settings that existed prior to the upgrade and update the Enterprise Parameters as needed. |
Step 3 |
Click Save. |
Step 4 |
Click Reset, and then click OK to reset all devices. |
Reset High and Low Watermarks
Use this procedure to restore the high and low watermarks to their original values in order to avoid premature purging of traces.
Procedure
Step 1 |
In the Real Time Monitoring Tool (RTMT) interface, double-click Alert Central in the left navigation pane. |
Step 2 |
On the System tab, right-click LogPartitionLowWaterMarkExceeded and select Set Alert/Properties. |
Step 3 |
Select Next. |
Step 4 |
Adjust the slider value to 80. |
Step 5 |
On the System tab, right-click LogPartitionHighWaterMarkExceeded and select Set Alert/Properties. |
Step 6 |
Select Next. |
Step 7 |
Adjust the slider value to 85. |
Updating VMware Tools
VMware Tools are a set of utilities for management and performance optimization. Your system uses one of the following VMware Tools:
-
Native VMware Tools (provided by VMware)
-
Open VMware Tools (provided by Cisco)
-
To upgrade Unified Communications Manager from a version earlier than Release 11.5(x), you must use the native VMware tools option. You can change to open VMware Tools after the upgrade.
-
For upgrades from Unified Communications Manager Release 11.5(1) onwards (for example, to a higher SU), you can choose whether your system use Native VMware or Open VMware Tools.
-
For fresh installation and PCD migrations from Unified Communications Manager Release 11.5(1) onwards, open VMware tools installed by default.
Procedure
Step 1 |
Execute a command utils vmtools status to ensure that VMware tools are currently running. |
||
Step 2 |
If necessary, run one of the following commands to switch to the desired VMware tools platform: utils vmtools switch native or utils vmtools switch open. |
||
Step 3 |
Follow one of the methods below if you are using Native VMware Tools:
For information about how to configure these options, refer to VMware documentation. You can also find more information by searching the topic "VMware Tools" at https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/virtualization-software-requirements.html#vmtools. |
Install Locales
Use this procedure to install locales. After an upgrade, you must reinstall any locales that you are using, with the exception of US-English, which is installed by default. Install the latest version of the locales that match the major.minor version number of your Unified Communications Manager node orIM and Presence Service node.
You can install locales on Unified Communications Manager or on IM and Presence Service nodes. If you are installing a locale for both products, install the locale on all cluster nodes in the following order:
-
Unified Communications Manager publisher node
-
Unified Communications Manager subscriber nodes
-
IM and Presence database publisher node
-
IM and Presence subscriber nodes
If you want to install specific locales on IM and Presence Service nodes, you must first install the Unified Communications Manager locale file for the same country on the Unified Communications Manager cluster.
Procedure
Step 1 |
Find the locale installer for your release on cisco.com:
|
Step 2 |
Download your release's locale installer to a server that supports SFTP. You need the following files:
|
Step 3 |
Log in to Cisco Unified OS Administration using the administrator account. |
Step 4 |
Choose . |
Step 5 |
Complete the following fields in the Software Installation/Upgrade window:
|
Step 6 |
Click Next. |
Step 7 |
Download and install the locale on the server. |
Step 8 |
Restart the server. The updates take effect after the server restarts |
Step 9 |
Repeat this procedure on all Unified Communications Manager and IM and Presence Service cluster nodes in the prescribed order. |
Note |
Do not reset user locales for your end users until the new locale is installed on all cluster nodes. If you are installing the locale for both Unified Communications Manager and IM and Presence Service Service, you must install the locale for both products before you reset user locales. If you run into any issues, such as could occur if an end user resets a phone language before the locale installation is complete for IM and Presence Service Service, have your users reset their phone language in the Self-Care Portal to English. After the locale installation is complete, users can reset their phone language, or you use Bulk Administration to synchronize locales to the appropriate language by bulk. |
Restore the Database Replication Timeout
This procedure applies to Unified Communications Manager nodes only.
Use this procedure if you increased the database replication timeout value before you began the upgrade process.
The default database replication timeout value is 300 (5 minutes). Restore the timeout to the default value after the entire cluster upgrades and the Unified Communications Manager subscriber nodes have successfully set up replication.
Procedure
Step 1 |
Start a CLI session using one of the following methods:
|
Step 2 |
Execute the utils dbreplication setrepltimeout timeout command, where timeout is database replication timeout, in seconds. Set the value to 300 (5 minutes). |
Verify the Registered Device Count
Use the Cisco Real -Time Monitoring Tool (RTMT) to view the device count and verify your endpoints and resources after the upgrade is complete.
Procedure
Step 1 |
From the Unified RTMT interface, select . |
||||||||||
Step 2 |
Record the number of registered devices:
|
||||||||||
Step 3 |
Compare this information to the device counts that you recorded before the upgrade and ensure that there are no errors. |
Verify Assigned Users
Use this procedure to verify the number of assigned users on nodes after the upgrade is complete.
Procedure
Step 1 |
From the Cisco Unified CM IM and Presence Administration interface, select . |
Step 2 |
Compare this information to the number of assigned users that you recorded before the upgrade and ensure that there are no errors. |
Test Functionality
After the upgrade, perform the following tasks:
-
Run the post-upgrade COP.
It runs a series of tests to verify that the system is stable. It also compares various parameters before the upgrade with the current version to identify any differences. After you complete all the steps in this list, run the post-upgrade COP file again and verify the COP report.
-
Verify phone functions by making the following types of calls:
-
Voice mail
-
Interoffice
-
Mobile phone
-
Local
-
National
-
International
-
Shared line
-
-
Test the following phone features:
-
Conference
-
Barge
-
Transfer
-
C-Barge
-
Ring on shared lines
-
Do Not Disturb
-
Privacy
-
Presence
-
CTI call control
-
Busy Lamp Field
-
-
Test IM and Presence Service functions:
-
Basic presence states, such as available, unavailable, and busy
-
Send and receive files
-
Advanced features, such as persistent chat, federated users, and message archiving
-
Upgrade RTMT
Tip |
To ensure compatibility, Cisco recommends that you upgrade RTMT after you complete the Unified Communications Manager upgrade on all servers in the cluster. |
Note |
When an IM and Presence Service node is configured as the primary collector for the Cisco AMC service and an upgrade is performed,
we see the following error in Unified RTMT:
|
RTMT saves user preferences and downloaded module jar files locally on the client machine. The system saves user-created profiles in the database, so you can access these items in Unified RTMT after you upgrade the tool.
Before you begin
Before you upgrade to a newer version of RTMT, we recommend that you uninstall the previous version.
Procedure
Step 1 |
From Unified Communications Manager Administration, choose . |
Step 2 |
Click Find. |
Step 3 |
Perform one of the following actions:
|
Step 4 |
Download the installation file to your preferred location. |
Step 5 |
Locate and run the installation file. |
Step 6 |
In the RTMT welcome window, click Next. |
Step 7 |
Because you cannot change the installation location for upgrades, click Next. |
Step 8 |
In the Maintenance Complete window, click Finish. |
Manage TFTP Server Files
You can upload files for use by the phones to the TFTP server. Files that you can upload include custom phone rings, callback tones, and backgrounds. This option uploads files only to the specific server to which you connected, and other nodes in the cluster do not get upgraded.
Files upload into the tftp directory by default. You can also upload files to a subdirectory of the tftp directory.
If you have two Cisco TFTP servers that are configured in the cluster, you must perform the following procedure on both servers. This process does not distribute files to all nodes, nor to both Cisco TFTP servers in a cluster.
To upload and delete TFTP server files, follow this procedure:
Procedure
Step 1 |
From the Cisco Unified Communications Operating System Administration window, navigate to . The TFTP File Management window displays and shows a listing of the current uploaded files. You can filter the file list by using the Find controls. |
Step 2 |
To upload a file, follow this procedure: |
Step 3 |
To delete files, follow this procedure: |
Set Up a Custom Log-On Message
You can upload a text file that contains a customized log-on message that appears in Cisco Unified Communications Operating System Administration, Cisco Unified CM Administration, Cisco Unified Serviceability, Disaster Recovery System Administration, Cisco Prime License Manager, and the command line interface.
To upload a customized log-on message, follow this procedure:
Procedure
Step 1 |
From the Cisco Unified Communications Operating System Administration window, navigate to . The Customized Logon Message window displays. |
||
Step 2 |
To choose the text file that you want to upload, click Browse. |
||
Step 3 |
Click Upload File.
The system displays the customized log-on message. |
||
Step 4 |
To revert to the default log-on message, click Delete. Your customized log-on message gets deleted, and the system displays the default log-on message.
|
Configure IPSec Policies
Use this procedure only if you are performing a PCD migration from Release 10.5. You must reconfigure your IPSec policies after the PCD migration is complete. Before migration, you must disable the IPSec policy in both the nodes of the cluster. And after successful migration, ensure that you enable the IPSec policy.
-
IPSec requires bidirectional provisioning, or one peer for each host (or gateway).
-
When you provision the IPSec policy on two Unified Communications Manager nodes with one IPSec policy protocol set to "ANY" and the other IPSec policy protocol set to "UDP" or "TCP", the validation can result in a false negative if run from the node that uses the "ANY" protocol.
-
IPSec, especially with encryption, affects the performance of your system.
Procedure
Step 1 |
From Cisco Unified OS Administration, choose . |
Step 2 |
Click Add New. |
Step 3 |
Configure the fields on the IPSEC Policy Configuration window. See the online help for more information about the fields and their configuration options. |
Step 4 |
Click Save. |
Step 5 |
(Optional) To validate IPsec, choose Validate IPsec check box, and then click Ping. , check the |
Assign New Manager Assistant Roles
Perform this procedure only if your previous release was configured to use the Cisco Unified Communications Manager Assistant feature, and you assigned application users to use either the InterCluster Peer-User or the Admin-CUMA roles. The InterCluster Peer-User and Admin-CUMA roles are deprecated from release 10.0(1) onward and are removed during the upgrade process. You must assign new roles for those users.
Procedure
Step 1 |
To configure roles and users, see the chapter Manage Users in Administration Guide for Cisco Unified Communications Manager. |
Step 2 |
Ensure that the AXL user defined on the IM and Presence Service service user interface ( ) has a Standard AXL API Access role associated with it on the Unified Communications Manager application user page. |
Verify IM and Presence Service Data Migration
When you upgrade from Cisco Unified Presence Release 8.x to an IM and Presence Service Service release, user profiles are migrated to Unified Communications Manager. The user profile information is stored as new service profiles on Unified Communications Manager with the following name and description format:
Name: UCServiceProfile_Migration_x (where x is a number starting at 1)
Description: Migrated Service Profile Number x
To ensure that users can successfully log into Cisco Jabber after an upgrade from Cisco Unified Presence Release 8.x, you must verify that the user profile data migration was successful.
Profiles that are created but that are not assigned to users are not migrated to Unified Communications Manager.
Procedure
Step 1 |
From Cisco Unified CM Administration, select . |
||
Step 2 |
Select Find to list all service profiles. |
||
Step 3 |
Verify that there are migrated service profiles with the following name format: UCServiceProfile_Migration_x |
||
Step 4 |
If there are no migrated service profiles, check the installdb log file for any errors. |
||
Step 5 |
If the data migration fails, an import error alarm is raised on Unified Communications Manager and the Cisco Sync Agent sends a failure notification to the Cisco Unified CM IM and Presence Administration GUI.
|
What to do next
You can edit these service profiles to give them more meaningful names. See Administration Guide for Cisco Unified Communications Manager for more information about configuring service profiles.
Run the post-upgrade COP file. It runs a series of tests to verify that the system is stable. It also compares various parameters before the upgrade with the current version to identify any differences.Enable High Availability on Presence Redundancy Groups
This procedure applies to IM and Presence Service nodes only. If you disabled high availability on presence redundancy groups before beginning the upgrade process, use this procedure to enable it now.
Before you begin
If it has been less than 30 minutes since your services restarted, confirm that your Cisco Jabber sessions have been recreated before you enable High Availability. Otherwise, Presence will not work for Jabber clients whose sessions aren't created.
To obtain the number of Jabber sessions, run the show perf query counter "Cisco Presence Engine" ActiveJsmSessions
CLI command on all cluster nodes. The number of active sessions should match the number of users that you recorded when you
disabled high availability prior to the upgrade.
Procedure
Step 1 |
From the Cisco Unified CM Administration user interface, choose . |
Step 2 |
Click Find and select the Presence Redundancy Group. |
Step 3 |
Check the Enable High Availability check box. |
Step 4 |
Click Save. |
Step 5 |
Repeat this procedure in each Presence Redundancy Group. |
Restart the IM and Presence Sync Agent
If you stopped the IM and Presence Service Sync Agent service before you began the upgrade process, restart it now.
Procedure
Step 1 |
From the Cisco Unified Serviceability interface, select . |
Step 2 |
Select an IM and Presence Service node from the Server drop-down list and click Go. |
Step 3 |
In the IM and Presence Services section, select the Cisco Sync Agent and click Restart. |
Example
Note |
After the Cisco Intercluster Sync Agent has finished the initial synchronisation, manually load the new Tomcat certificate onto Unified Communications Manager. This ensures that the synchronisation does not fail. |
Note |
Run the post-upgrade COP. It runs a series of tests to verify that the system is stable. It also compares various parameters before the upgrade with the current version to identify any differences. |
Restart Cisco Emergency Responder Service
Procedure
If you stopped the Cisco Emergency Responder service before you began the upgrade process, restart it now.
Step 1 |
From the Cisco Emergency Responder serviceability interface, select Tools > Control Center. |
Step 2 |
Select Cisco Emergency Responder and click Restart. |