Upgrade and Migration Guide for Cisco Unified Communications Manager and the IM and Presence Service, Release 15 and SUs - Upgrade Tasks

Publisher

Cisco Systems

URL

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/15/cucm_b_upgrade-and-migration-guide_15/cucm_m_upgrade-tasks.html

Published

2026-08-14

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

Cisco copyright; all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• During an upgrade the administrator can choose to switch to the new version automatically when the upgrade completes; the default is not to switch automatically. in context
• The Clusterwide Upgrade option is available only for direct standard upgrades where the pre-upgrade version is at least 12.5(1). in context
• After the pre-upgrade check COP file is installed, its report can be viewed from the CLI with file view install PreUpgradeReport.txt. in context
• After reverting to the previous version, database replication must be reset manually with the CLI command utils dbreplication reset all. in context
• When reverting a cluster, switch back the publisher first, then all backup subscriber nodes, then all primary subscriber nodes. in context
• Upgrade software can be loaded from DVD/CD, from the local filesystem, or from an SFTP server whose directory, address and login credentials the administrator supplies. in context
• Cluster-wide version switching is available only for Direct Standard Upgrades from 12.5(x) or later. Otherwise each node is switched individually, for example with utils system switch-version. in context
• To upgrade a node in FIPS mode, the cluster security password must be at least 14 characters long. in context
• Make no configuration changes during the upgrade. Cisco says changes made then are overwritten, and that includes password changes, LDAP synchronisation and automated jobs. in context
• Configuration changes made after the upgrade and before a revert are lost when you revert. in context
• To revert a cluster, switch the publisher back first, then all backup subscribers, then all primary subscribers, and then reset database replication with utils dbreplication reset all. in context
• Suspend LDAP user synchronisation for the upgrade and resume it only after the whole upgrade is complete. in context

Cite this source record

APA

WarmTransfer. (2026, August 14). Upgrade and Migration Guide for Cisco Unified Communications Manager and the IM and Presence Service, Release 15 and SUs - Upgrade Tasks. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cucm-upgrade-15-upgrade-tasks

BibTeX

@misc{warmtransfer-cisco-cucm-upgrade-15-upgrade-tasks,
  title  = {Upgrade and Migration Guide for Cisco Unified Communications Manager and the IM and Presence Service, Release 15 and SUs - Upgrade Tasks},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-cucm-upgrade-15-upgrade-tasks},
  note   = {Cisco Systems, accessed 2026-09-24}
}