CUCM 11.5 TO 12.
5(1)SU1 UPGRADE GUIDE
CONTENTS
Version History................................................................................................................................................................1
Considerations................................................................................................................................................................1
Requirements and Limitations........................................................................................................................................2
Deprecated Phone Models for this Release...............................................................................................................2
Upgrades from 11.5(1)SU2 with Push Notifications Enabled....................................................................................2
Disable Push Notifications..........................................................................................................................................2
Add a Unified Communications Manager product instance into the Smart Licensing system..................................2
Enable Push Notifications for this release..................................................................................................................2
System Requirements.....................................................................................................................................................3
Upgrade Sequence..........................................................................................................................................................3
Before You Begin.............................................................................................................................................................3
run pre-upgrade check....................................................................................................................................................3
Upgrade Procedure.........................................................................................................................................................5
Dbreplication issues........................................................................................................................................................7
Change the CUCM IP Addresses.....................................................................................................................................7
Update IP Address on TFTP Proxy...................................................................................................................................8
Reference:.....................................................................................................................................................................10
VERSION HISTORY
Created 9/25/2019 - Tim Waters
Updated 12/19/2019 – Tim Waters
o Updated Considerations section to include ESXi requirement.
o Added chapter: Change the CUCM IP Addresses
o Added chapter: Proxy TFTP IP Address Change
CONSIDERATIONS
Servers will need to move to the new DTCR to meet vSphere ESXi requirement.
This introduces additional steps:
Engage Server Engineering to migrate/clone the servers to DTCR
Engage Network Engineering to provide new IP addresses and set up firewall rules
You must update the IP address on each node (See: Update IP Address on CUCM Server)
You must update the IP addresses on the Proxy TFTP Cluster (See Update IP Address on TFTP Proxy)
Other than that, this is a standard upgrade; no COP file required
The upgrade file is not available as a direct download. You must use Cisco Product Upgrade Tool (PUT) or My Cisco
Entitlements (MCE). (Contract number: 95468956)
Utilize Cisco Smart Software Manager(CSSM) or Cisco Smart Software Manager Satellite for licensing
** This is a refresh upgrade so it will go fully down while upgrading.
REQUIREMENTS AND LIMITATIONS
DEPRECATED PHONE MODELS FOR THIS RELEASE
Cisco Unified IP Phone 7970G
Cisco Unified IP Phone 7971G-GE
Cisco Unified Wireless IP Phone 7921G
UPGRADES FROM 11.5(1)SU2 WITH PUSH NOTIFICATIONS ENABLED
If you are upgrading from the 11.5(1)SU2 release and you had Push Notifications enabled in the old release, you
must disable Push Notifications in the current release and then follow the onboarding process to enable Push
Notifications once again. This is required due to API changes in this release that were not a part of the 11.5(1)SU2
release. Your upgraded system will not be able to send troubleshooting logs to the Cisco Cloud unless you disable
Push Notifications and then follow the onboarding process for this release.
After you upgrade your system, do the following:
DISABLE PUSH NOTIFICATIONS
1. From Cisco Unified CM Administration, choose Advanced Features > Cisco Cloud Onboarding
2. Uncheck the following check boxes:
a. Enable Push Notifications
b. Send Troubleshooting information to the Cisco Cloud
c. Send encrypted PII to the Cisco Cloud for troubleshooting
3. Click Save.
ADD A UNIFIED COMMUNICATIONS MANAGER PRODUCT INSTANCE INTO THE SMART LICENSING
SYSTEM
See the "Smart Software Licensing" chapter of the System Configuration Guide for Cisco Unified Communications
Manager at http://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-
callmanager/products-installation-and-configuration-guides-list.html
ENABLE PUSH NOTIFICATIONS FOR THIS RELEASE
For the full onboarding process, See the "Configure Push Notifications for Cisco Jabber on iPhone and iPad"
chapter of the System Configuration Guide for Cisco Unified Communications Manager at
http://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/
products-installation-and-configuration-guides-list.html
SYSTEM REQUIREMENTS
The following requirements are for 7,500 users (per VM):
CUCM Servers vCPU vRAM vDisk vNIC vSphere ESXi
REQUIRED 2 8 GB 1 x 110 GB VMXNET 3 6.5, 6.7
✔ UC-CMFLEX1-VP01 2 8 GB 1 x 110 GB VMXNET 3 6.5
✔ UC-CMFLEX1-VP02 2 8 GB 1 x 110 GB VMXNET 3 6.5
✔ UC-CMFLEX1-VP03 2 8 GB 1 x 110 GB VMXNET 3 6.5
** Had to move servers to new DTCR to meet vSphere ESXi requirement.
UPGRADE SEQUENCE
Recommended sequence for upgrading in the least amount of time:
1. Upgrade the publisher node to the new software version. The new software is inactive.
2. Upgrade the subscriber node(s) in parallel. The new software is inactive.
3. Switch the software version on the publisher node and reboot it. The new software is active.
4. Switch the software version on the subscriber nodes in parallel and reboot them.
5. Ensure that database replication is complete and functioning between the pub and sub nodes.
This sequence assumes no IM&P nodes.
BEFORE YOU BEGIN
1. Obtain the proper files from the Cisco website or TAC.
* NOTE: The upgrade file is not available as a direct download. You must use Cisco Product Upgrade Tool (PUT) or
My Cisco Entitlements (MCE). (Contract number: 95468956)
2. Upload files to LNX-UCBKUP-VP02 using an SFTP client such as WinSCP:
/home/osumc_voice/UC_Server_Install_and_Upgrade_Files/CUCM/12_5_1_SU1
The 12.5 upgrade files have already been obtained and uploaded.
RUN PRE-UPGRADE CHECK
1. Open the web GUI of the CUCM publisher (e.g. uc-cmflex1-vp01)
2. Navigate to Cisco Unified OS Administration and log in
3. From the top menu choose Software Upgrades > Install/Upgrade
4. Enter the file location and hit Next
Source: Remote Filesystem
Directory: /home/osumc_voice/UC_Server_Install_and_Upgrade_Files/CUCM/12_5_1_SU1
Username: osumc_voice
Password: ********
Transfer Protocol: SFTP
SMTP Server / Email Destination: Leave blank
5. Choose the upgrade file ciscocm.preUpgradeCheck-00019.cop.sgn and hit Next
6. After CUCM downloads the file, click Next to continue
7. Allow a few minutes for the installation to run
8. Check the log file to be sure nothing was flagged “FAIL”
When ready, proceed to the CUCM upgrade.
UPGRADE PROCEDURE
Starting with the primary CUCM peer, upgrade the CUCM cluster peers in sequence as follows:
1. Open the web GUI of the CUCM server (e.g. uc-cmflex1-vp01)
2. Navigate to Cisco Unified OS Administration and log in
3. From the top menu choose Software Upgrades > Install/Upgrade
4. Enter the file location and hit Next
5. Choose the upgrade file UCSInstall_UCOS_12.5.1.11900-146.sgn.iso and hit Next
6. After CUCM downloads the file, click Next to continue
7. Select Do not reboot after upgrade and hit Next
**WARNING** The system WILL reboot and be offline during the upgrade process.
8. Log into vSphere: https://vmw-vc1-vp01.osumc.edu/vsphere-client/?csp#extensionId
%3Dvsphere.core.vm.gettingStarted%3Bcontext%3Dcom.vmware.core.model%253A
%253AServerObjectRef~3f63e861-99d5-49dd-bcc1-349af2373930%253AVirtualMachine%253Avm-
578452~core and launch the console to continue to monitoring the installation
9. Wait 1-2 hours for the upgrade to complete.
** The console may turn blue and appear to be unresponsive. Just let it be. Flex upgrade on pub took around 2
hours.
Once finished you will get a login prompt. Note that the version is still 11.5 because it is not yet active until we
reboot later.
10. Repeat steps 1 – 7 to upgrade the subscribers in parallel
11. Once all upgrades have completed, switch versions on publisher to activate 12.5
utils system switch-version
12. Once it has rebooted, verify you are on the new version by running:
show version
13. Wait for all services to show STARTED. This can take some time.
utils service list
14. Once all services are back up, repeat steps 10-13 for each subscriber
15. Once all nodes are on the new version, wait for database replication to show status “(2) Setup
Completed” on all nodes. This should not take too long.
To monitor the process, run the dbreplication runtimestate command.
The software upgrade on the CUCM cluster is now complete.
DBREPLICATION ISSUES
For the Flex upgrade, dbreplication failed. Here is how to troubleshoot and fix the issue.
Reset the database replication from the scratch
1. utils dbreplication stop all (Only on the publisher)
2. utils dbreplication dropadmindb (First on all the subscribers one by one then the publisher)
3. utils dbreplication reset all ( Only on the publisher )
To monitor the process, run the dbreplication runtimestate command.
Sync progress states are Defining > Defined > Syncing > Setup Complete
If status shows “db-diff” it means that nodes are on different versions of CUCM.
To resolve this:
1. Run the show version command on each node to determine which is still on the old version.
2. Run the utils system switch-version command on affected node(s) to fix.
Engage TAC if this does not fix the issue.
CHANGE THE CUCM IP ADDRESSES
Be very careful when performing these steps and take note of the following caveats:
Changing the IP address or hostname triggers an automatic self-signed certificate regeneration. This
causes all devices in the cluster to reset so that they can download an updated ITL file. If your cluster is
using CA-signed certificates, you will need to have them re-signed.
Expect to run into dbreplication issues. See Dbreplication Issues for troubleshooting steps.
Always take a backup of the Cluster before you begin.
** Change the IP address for the database publisher node before you change any subscriber nodes.
1. Log into the CLI of the Publisher node of the cluster you want to change
2. Run the following command, replacing the placeholders with the new values as shown in the example:
set network ip eth0 [new_ip_address] [new_subnet_mask] [new_gateway]
Example: set network ip eth0 10.53.57.101 255.255.255.224 10.53.56.1
3. The following output displays:
WARNING: Changing this setting will invalidate software license on this
server. The license will have to be re-hosted.
Continue (y/n)?
4. Verify the output of the CLI command. Enter yes, and then press Enter to start the process
5. Enter the following command and ensure you see the new IP address in the CLI output:
Show network eth0
If you don’t see the changes reflected yet, wait for some time and verify it again. On successful
verification only, go to the next step.
6. Once the Publisher IP has been updated, repeat these steps to update all subscriber nodes.
**As long as the Publisher IP has been updated, you can update the Subscribers in any order, one at a time or
simultaneously.
7. Check and make any required configuration changes to other associated Cisco Unified Communications
components, such as Unity, and TFT Proxy (See: Update IP Address on TFTP Proxy)
8. Review and complete any applicable post-change tasks listed here:
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/install/11_5_1/ipchange/
cucm_b_change-ip-address-and-hostname_1151/cucm_b_change-ip-address-and-
hostname_1151_chapter_0101.html
UPDATE IP ADDRESS ON TFTP PROXY
Log into the TFTP Cluster CM Administration page: https://uc-cmtftp1-vp01.osumc.edu/ccmadmin
Navigate to Advanced Features > Cluster View
Click Find then click on the Cluster ID you wish to update
Click on the TFTP link.
Enter the new IP addresses and click Save
Restart TFTP services on all nodes within the TFTP cluster: https://uc-cmtftp1-vp01.osumc.edu/ccmservice/
REFERENCE:
CUCM 12.5 Documentation (All)
https://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-version-12-
5/model.html
OVA templates and sizing for CUCM 12.5
https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/virtualization-cisco-
unified-communications-manager.html#v12.5
CUCM 12.5(1)SU1 Release Notes
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/12_5_1/SU1/cucm_b_release-notes-
for-cucm-imp-1251su1/cucm_b_release-notes-for-cucm-imp-1251su1_chapter_00.html
Cisco Unity Connection 12.x Compatibility Matrix
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/compat/12_x/cucm_b_compatibility-matrix-cucm-
imp-125x.html#reference_5AE1A27CAA0ECE997E49B50A5B4C57F3
Steps to troubleshoot database replication issues
https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-
callmanager/200396-Steps-to-Troubleshoot-Database-Replicati.html
