Rect

#CLUS
Cisco Webex Teams

Questions?
Use Cisco Webex Teams (formerly Cisco Spark)
to chat with the speaker after the session
How
1 Find this session in the Cisco Live Mobile App
2 Click “Join the Discussion”
3 Install Webex Teams or go directly to the team space
4 Enter messages/questions in the team space
Webex Teams will be moderated

by the speaker until June 18, 2018. cs.co/ciscolivebot#BRKUCC-2011
#CLUS BRKUCC-2011 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 2
Best Practices for Migrating From
Previous Versions of Cisco Unified
Communications Manager (CUCM)
to Version 12.X (12.0 & 12.5)
Brandon Ta, Consulting Systems Engineer and
Business Architect
bta@cisco.com
BRKUCC-2011
#CLUS
Required GAAP Reconciliation
and Forward-Looking Statements
The Cisco products, service or features identified in this document may
not yet be available or may not be available in all areas and may be
subject to change without notice. Consult your local Cisco business
contact for information on the products or services available in your
area. You can find additional information via Cisco’s World Wide Web
server at http://www.cisco.com. Actual performance and environmental
costs of Cisco products will vary depending on individual customer
configurations and conditions.
Session Highlights
• Smart Licensing:
• SLR (Specific License Reservation) Smart License with CUCM 12.5
• Business Edition 6000 Starter License
• Upgrade Enhancements with CUCM and IM&P 12.5

• Updated Platform Support with BE6KM5 and BE7KM5
Details Might Change!
Reference
Previous Sessions for various CUCM Versions
• To CUCM 10.5
Best Practices for Migrating Previous Versions of CUCM to version 10.5. - BRKUCC-2011 ( 2014
San Francisco and 2014 Cancun)
• To CUCM 11.X
Best Practices for Migrating Previous Versions of CUCM to version 11.0 - BRKUCC-2011 (2015
San Diego, 2016 Las Vegas, 2016 Cancun and 2016 Berlin )
• To CUCM 12.0
Best Practices for Migrating Previous Versions of CUCM to version 12 - BRKUCC-2011 ( 2017
Las Vegas and 2017 Berlin)
Cisco Live Access Sessions On-demand

http://www.ciscolive.com/global/
Reference
Smart Licensing and CUCM
• Lab: dCloud.cisco.com
Collab VT Migration & Smart Licensing Lab – CUCM, Unity Connection and CER
• Tech Talk: Smart Licensing for Collaboration Applications (CUCM and Unity Connection)
Recording: https://communities.cisco.com/docs/DOC-58520
Lab Document and Presentation: https://communities.cisco.com/docs/DOC-77054
• Cisco Live: Foundational Smart Account and Smart Licensing
Smart Accounts and Smart Software Licensing - CISSOL-1116 (2016 Las Vegas)
Agenda
• Session Objectives and Scope
• Overview of System Level Planning
• Smart Licensing Planning, Design and Migration for CUCM 12.X
• CUCM Upgrade/Migration Methods and Tools
• Platform Support and Migration
• System Preparation and Optimizing Upgrade Speed for CUCM Upgrade
• Upgrade Execution and CUCM Registration and SLR with Smart Licensing
Session Objectives
and Scope
Session Objectives
• To provide foundational knowledge for a successful upgrade or migration to CUCM 12.X

• Planning
• Considerations
• Approach
• Tools
• To provide an overview of Smart Account and Smart Licensing including new Smart License
support in CUCM 12.5
• To provide an overview and best practices to optimize upgrade and migration from a holistic
system level
Session Scope
Virtualized CUCM
Virtualized CUCM 12.X
Bare Metal CUCM
• Upgrade or migrate to CUCM 12.X

• System level approach
• License conversion from traditional node and ELM/PLM license to Smart Licensing
Overview of Systems
Level Planning for
CUCM Upgrade and/or
Migration
2
System Level Planning
Upgrade/Migration Optimizing Upgrade
License Management Platform System Preparation Execution
Methods and Tools Speed
Smart Licensing DSU Servers Deprecated TFTP server Phone firmware

Smart Account DRU Virtualization phones DB replication Application
License Conversion PCDU Virtualized CUCM Disk Space Purge CDR dependencies
License Optimization
PCDM VMware changes COP file(s) Upgrade windows
Smart Registration
SLR Registration
Pre-Upgrade list Post-Upgrade list

link (end of slide link (end of slide
deck) deck)
Smart Licensing
Planning, Design and
Migration for CUCM
12.X
3
CUCM Licensing
Overview
License Manager for CUCM by Versions
CUCM Version 5.0-8.6 9.0-11.5 12.0 and later
License Manager Publisher ELM/PLM Cisco Smart Software Manager (CSSM)
CUCM STATUS
SMART AGENT
STATUS
CUCM 12.X Licenses
CUCM License Licensing CUCM Description

Mode Version
CUWL Enterprise 12.X Migrated CUCM and BE6K licenses
Enhanced Plus Enterprise 12.X Migrated CUCM and BE6K licenses
Enhanced Enterprise 12.X Migrated CUCM and BE6K licenses
Basic Enterprise 12.X Migrated CUCM and BE6K licenses
Essential Enterprise 12.X Migrated CUCM and BE6K licenses
TelePresence Room Enterprise 12.X Migrated CUCM and BE6K licenses

BE6K Software License Starter New BE6K purchase with version 12.5
BE6000 12.5+
Bundle (R-CBE6K-K9) (per cluster)
Example: CUCM 12.5 License Consumption
CSSM CUCM License

Essential, Basic, Enhanced, Enhanced Plus,
CUWL and TelePresence Room
CUCM
(Enterprise Mode)
CSSM CUCM License

Essential, Basic, Enhanced, Enhanced Plus,
CUWL and TelePresence Room
CUCM on BE6K
(Enterprise Mode)
CSSM CUCM License
1
BE6K Starter Bundle (1 per cluster if available)
(35 Enhanced/35VM or 35 CUWL BE or 35
CUWL Meetings)
2
CUCM on BE6K Essential, Basic, Enhanced, Enhanced Plus,
(BE6K Mode) CUWL and TelePresence Room
Smart Licensing
Overview
Planning for Smart Licensing
1 2 3
CER
Smart Account Smart License

Structure Deployment
Enabled
Model
(Account/Roles) Products
1.Smart Account Structure: Smart Account Structure
ACCOUNT STRUCTURE
Create or get access
to Smart Account Create Virtual
Design Smart
Accounts and Top Level:
(e.g. abc.com, Accounts Structure
Define/Assign Roles
xyz.com, etc.) Smart Account = abc.com
Account Description and Usage Examples Sub Level:

Virtual Account =
Account that represent a company (domain abc.com, xyz.com, etc. Collaboration
Smart Account based)
Sub Level:
• Sub-Account to Smart Account Geographical locations,
Virtual Account =
• Represent different departments of the departments, product Infrastructure
main Smart Account or organization types, etc.
• Where product registers to
Virtual Account
• Where license are assigned to
• Equal to an instance of ELM/PLM
E.G. Virtual Account “collaboration” have X,Y, Z, etc. quantity of collaboration licenses and where
all Smart Licensing enabled collaboration products will register to
1. Smart Account Structure: Roles
Create or get access
to Smart Account Create Virtual
Design Smart
Accounts and
(e.g. abc.com, Accounts Structure
Define/Assign Roles
xyz.com, etc.)
Visibility/Typical ROLES
Roles Privileges
Assignment
Highest level account that can create High Level Managers and admin Top Level:
Smart Account accounts and roles at the Smart Account of the Smart Account
level and Virtual Account level Smart Account Admin = Manager1
Administrator
Smart Account User = TeamLead2 (view)
View level access at the Smart Account Manager or trusted partners

Smart Account User level and Virtual Account level
• Manage properties of the assigned Lead engineers Sub Level for Collaboration Virtual
Account:
Virtual Account
Virtual Account • User can register and view licenses Virtual Account Admin = TechLead3
Administrator specific to the assigned Virtual
Virtual Account User = Engineer4
Account
• View properties of the assigned Virtual Deployment engineers

Account
Virtual Account User • User can register and view licenses
specific to the Virtual Account
Reference
Customer Smart Account Roles (Detailed)
User Roles Capabilities in CSC Capabilities in SSM Capabilities in ELA Capabilities in LRP
Smart Account • Edit/View Account Properties • No access • No access • No access

Approver • View Users at Smart Account & Virtual Account Level
• View / Accept Agreements
• View Event Logs
Smart Account • Edit / View Account Properties • Can perform all activities in • Can perform all activities in • Can perform all activities in
Administrator • Add / Edit / Delete Virtual Accounts Smart Software Manager at ELA linked to the Smart LRP linked to the Smart
• Add / Edit / Delete Users (at SA and VA level) Smart Account Level and Account they have access to Account they have access
• View / Accept Agreements Virtual Account Level to
• View Event Logs
Smart Account • View Account Properties • Can perform all activities in • Can perform all activities in • Can perform all activities in
User • View Virtual Accounts Smart Software Manager at ELA linked to the Smart LRP linked to the Smart
• View Users (at SA and VA level) Smart Account Level and Account they have access to Account they have access
• View Agreements Virtual Account Level to
• View Event Logs
Virtual Account • View Account Properties • Can perform all activities in • Can perform all activities in • Can perform all activities in
Administrator • View Assigned Virtual Accounts SSM for the Virtual Accounts ELA linked to the Virtual LRP linked to the Virtual
• Add / Edit / Delete Users (capability to add Virtual they have access to Account they have access to Account they have access
Account Admins or Virtual Account Users) to
• View Agreements
• View Event logs (restricted to assigned VAs)
Virtual Account • View Account Properties • Can perform all activities in • Can perform all activities in • Can perform all activities in
User • View Assigned Virtual Accounts SSM for Virtual Accounts they ELA linked to the Virtual LRP linked to the Virtual
• View Users (only those linked to assigned VAs) have access to Account they have access to Account they have access
• View Agreements to
• View Event Logs (restricted to assigned VAs)
Reference
Smart Licensing Reference Links
• Smart Account Information

• http://cisco.com/go/smartaccounts
• Smart Licensing Information
• http://cisco.com/go/smartlicensing
• Smart Accounts and Smart Licensing On-Demand Training Materials
• https://communities.cisco.com/docs/DOC-68582
• Request a new Sales Software Training Session at the time of your
choosing
• https://www.ciscofeedback.vovici.com/se/7FAD612023A8BF7E
• Operational Exchange Community (search)
• https://ucrm-cisco.force.com/OperationsExchange/s/
Smart Licensing and Smart Account Recommendation
• Create a new Smart Account (SA) or get access to current Smart Account
• Agree and establish a Smart Account structure, roles and standard naming convention
for the various virtual accounts
• Take a holistic view when creating the account structure (legal requirements, liabilities,
asset management, budget alignment, policy, overhead, tax, etc.)
• Recommend separation for production and lab virtual accounts for entitlement
• Socialize the structure, roles and purchase process to assign licenses to the proper
Smart Account and Virtual Account(s)
• Communicate with partner on organization SA structure and license assignment
for typical orders
• Consider assigning “Smart Account User” role to trusted partner to move
licenses to the correct SA and virtual account for orders that are not assigned
properly
• For orders without SA and virtual account assignment, the license(s) will go into
the “Default” virtual account. Keep monitoring this virtual account and track
licenses back to “Order Number” by using “Transaction History”
2.Smart Licensing Deployment Models
Options
1 Direct cloud access Your
Cisco
Cisco product sends usage information directly over the internet. No additional components
Software
Usage
HTTPs
Cisco
are needed. Product Cisco.com
2 Direct cloud access through an HTTPs proxy

Ease of use
Your
Cisco
Cisco Products send usage information over the internet via a Proxy Server – Smart Call Home
Software
Usage
Transport Gateway
Transport Gateway (Free VM Download) or off-the-shelf Proxy (such as Apache). Cisco
or HTTPs Proxy
Security Policy
Product Cisco.com
3 Mediated access through an on-premises collector – connected Your

Cisco
Cisco Products send usage information to a local connected collector, which acts as a local
Software
Usage
license authority. Periodically, an exchange of information will be performed to keep the

Cisco.com
databases in sync. Cisco HTTPs Smart Software
Product Manager satellite
4 Mediated access through an on-premises collector – disconnected File

Transfer
Cisco Products send usage information to a local disconnected collector, which acts as a local Your
license authority. Once a month, an exchange of human readable information will be

Cisco
Software
Usage
performed to keep the databases in sync.

Cisco HTTPs Smart Software Cisco.com
Product Manager satellite
5 Full Offline Access – License Reservation File

Transfer
Your
Cisco
CUCM 12.5 uses Specific License Reservation (SLR). License are specified (Essential, Basic, Software
Usage
Enhanced, etc.) and reserved on CSSM for perpetual or term based for CUCM consumption. Cisco
* CUCM does not use Product License Reservation (PLR). Reserve for the full product Product
Cisco.com
Previous License and Smart Licensing Models
CUCM CUCM
(9-11.5) (12.X)
CUC
(9-11.5)
CUC cisco.com
(12.X)
ELM/PLM
CER CER CER

(10-11.5)
CER Cisco Smart Software Cisco Smart
(12.X)
Manager satellite Software
(Optional) Manager
(CSSM)
Publisher
CUCM Publisher CUCM Authorization Code
(5-8.6) (12.5)
Specific License Reservation (SLR)
27
Collaboration License Substitution within CSSM
CUWL
Enhanced Plus
CUWL
Enhanced
Enhanced Plus Enhanced Cisco
Basic Basic Basic Smart

Enhanced Software
Manager
Basic Essential Essential Essential

(CSSM)
Essential
3.Smart License Enabled Collaboration Products
Collaboration Products Version Licensing Mode
Cisco Unified Communications Manager 12.0 Smart ONLY
Session Management Edition 12.0 Smart ONLY
Unity Connection 12.0 Smart ONLY
Cisco Emergency Responder 12.0 Smart ONLY
Cisco Unified Communications Manager Express 11.0 Hybrid
SRST 12.1 Hybrid
Cisco Unity Express Virtual 9.0.5 Smart ONLY
Prime Collaboration Provisioning 12.4 Hybrid
vCUSP 9.0 Smart ONLY
vCUBE Current Hybrid
CUCM License
Migration
Collaboration License Migration to Smart License
CUCM 9.0-11.5 License Conversion
CSSM
License
Service Device Based Licenses Selected Account
• Smart Account
• Virtual Account
Cisco System
LRP PAK Based
Types of Migration Approach
PAK Based Fulfilled, partial or unfulfilled PAK to Smart

Licensing
Device Based PLM based to Smart Licensing
CSSM - Cisco Smart Software Manager (https://software.cisco.com/#SmartLicensing-LicenseConversion)
LRP – License Registration Portal (https://slexui.cloudapps.cisco.com/SWIFT/LicensingUI/Home)
* Steps with Screen captures are in the appendix

CUCM License Usage
and Optimization
CUCM License Usage
1
• Extension mobility users: No license
User • Extension mobility user with Unified Mobility (SNR): UCL Basic license
Device without Owner User ID association: UCL
2
•
Device • Based on the device
• E.g. Public space phones, shared workspace phones, etc.
3
User • Device with Owner User ID association: UCL or CUWL
/ Device • Based on the model of device and the number of devices assigned to the
user
• I.e. 1- 2 devices: UCL, 3 -10 devices: CUWL
4
• TelePresence (TP) device
TelePresence • E.g. CTS, MX, SX, TX, etc.
CUCM Licensing
http ://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/10_0_1/ccmfeat/CUCM_BK_F3AC1C0F_00_cucm -features-services-guide-100/CUCM_BK_F3AC1C0F_00_cucm-features-services-guide-100_chapter_0100101.html#CUCM_RF_UCAE0263_00
Device and Owner User ID Association
Device > Phone > Device Name
• Device with Owner User ID field configured
potentially uses less licenses
- I.E. Extension mobility user with Unified Mobility
feature and a phone uses one license
- I.E. Multiple phones with the same Owner ID
field
• Owner User ID Field:
- CUCM 9.1(1a) or earlier: User or None
- CUCM 9.1(2) or later: User or Anonymous
Cisco Device Assignment Tool (DAT)
• Pre-upgrade or post-upgrade of CUCM
Device Assignment Tool 9.0 and later releases
Match Users to
CUCM Search for
Unassigned Assign Owners • Align OwnerUserID to IP Phones for User
Unassigned
6.X-9.1
Phones via AXL
Phones based on 3 (OwnerUserID) to Based Licensing (CUCM 9.0 and later
defaults and 4 Phones
per CUCM cluster
optional rules releases).
• Windows PC (7 and later) or Apple Mac
(OSX 10.8 and later) Java application
CUCM
10.X-11.X
Device Name OwnerUserID CUCM Version Device Name OwnerUserID
SEP123456789012 None 9.1(1a) or earlier SEP123456789012 UserX
SEP098765432109 Anonymous 9.1(2) or later SEP098765432109 UserY
Device Assignment Tool 11.5

https://software.cisco.com/download/release.html?mdfid=286284802&softwareid=282204704&release=COP-Files&relind=AVAILABLE&rellifecycle=&reltype=latest
35
Reference
Cisco Device Assignment Tool (DAT)
DAT
(UdatApplication.jar)
• Based on sequence of 7 rules
or manually edited xls file
CUCM
Upgrade/Migration
Methods and Tools
4
CUCM Versions, Builds
and Requirements
Reference
Sample CUCM Versions and Builds
CUCM Version CUCM Build Numbering Convention
(A.B.C.XYzzz-x)
12.5(1) 12.5.1.10000-X
(A) Major version (License)
12.0(1)SU1 12.0.1.21900-7 11.5.1.10000-6
(B) Minor version (Long Life Release)
12.0(1) 12.0.1.10000-10
11.5.1.10000-6
11.5(1)SU4 11.5.1.14900-11 (C) Maintenance release (Patch and/or Features)
11.5(1)SU3b 11.5.1.13902-2 11.5.1.10000-6

(X) Build (Patch)
11.5(1)SU3a 11.5.1.13901-3
11.5.1.10000-6
11.5(1)SU3 11.5.1.13900-52 11.5.1.20000-5 (example)
11.5(1)SU2 11.5.1.12900-21 (Y) FCS:0, ES or SU: 1-9
11.5.1.10000-6 (FCS)
11.5(1)SU1 11.5.1.11900-26
11.5.1.12900-21 (ES or SU look at last three digits)
11.5(1) 11.5.1.10000-6 (zzz) FCS:000, ES: 001-899, SU: 900-999
11.5.1.10000-6 (FCS)
11.0(1a)SU3 11.0.1.23900-5
11.5.1.11001-5 (ES) (example)
11.0(1a)SU2 11.0.1.22900-14
11.5.1.12900-21 (SU)
Reference
Build Requirements
Build Matching
Use Case Matching Example
Servers in CUCM Cluster AA.B.C.Xyzzz-x 11.5.1.10000-6
Upgrade During An Installation AA.B 11.5. to 11.5 newer
CUCM and IM&P Servers AA.B 11.5 and 11.5
Servers in IM&P Cluster AA.B.C.Xyzzz-x 11.5.1.10000-4
CUCM and Device Packs AA.B.C 10.5.2 and 10.5.2
* Specific compatibility are in corresponding release notes (e.g. Cisco Unified Communications Manager
11.5.1.14900-11 is ONLY compatible with IM and Presence Service 11.5.1.14900-32
Separate CUCM & Unity Connection 12.X
CUCM 12.X ISO
CUCM & Unity Connection

7.X-11.5 ISO
Unity Connection 12.X

ISO
Upgrade Method
Methods and Tools for Upgrade
CUCM 6.1(5)
Appliance
CUCM 7.1(3/5)
CUCM 8.X
CUCM 9.X What

Upgrade
Method?
What CUCM 12.X

CUCM 8.X Upgrade
Tool?
CUCM 9.X
Virtualized
CUCM 10.X
CUCM 11.X
CUCM 12.0
Upgrade Methods and
Tools
Upgrade Methods and Tools – Unified CM OS
Direct
DSU Standard
Upgrade Unified CM OS Admin Upgrades
Direct Native and embedded tool
DRU Refresh
Upgrade * Upgrade Enhancement in CUCM 12.5
Upgrades
Method
PCDU PCD
Upgrade Prime Collaboration Deployment
(PCD) Upgrades and Migrations
PCDM
PCD External tool (virtual machine)
Migrate
Unified CM OS Admin Types of Upgrades
Standard Upgrade (formerly called L2 Upgrade):

SU • Active partition is running while upgrade software is
being installed on inactive partition
Unified •
•
Low complexity with shortest possible downtime
Between CUCM versions with the same major Linux
CM OS •
versions
(e.g. CUCM 10.0 to 11.0 or CUCM 10.0 to 11.5)
Admin
RU RU (Refresh Upgrade):
• Server is down while upgrade software including OS is
being installed on inactive partition
• Medium complexity with longer downtime
• Between CUCM versions with the different major Linux
versions (starting with RHEL 5 and later)
• (e.g. CUCM 8.6 to 11.5 or CUCM 9.1 to 11.5)
CUCM Upgrade and Reboot Options (SU & RU)
Active Partition (CUCM 11) Inactive Partition (CUCM 11)
Inactive Partition (CUCM 10) Active Partition (CUCM 12)
1
CUCM CUCM
Publisher Publisher
CUCM 12 Active Partition (CUCM 11) Inactive Partition (CUCM 11)

Upgrade 2 Inactive Partition (CUCM 10) Active Partition (CUCM 12)
ISO
CUCM CUCM
Subscriber Subscriber
• Upgrade Publisher first
SU and RU Upgrade Table
CUCM Version Linux Release
5.1(x) & 6.X RHEL 3 Update 8
7.0(1) RHEL 4 Update 4
SU
L2
7.1(3) & 8.0(x) RHEL 4 Update 7
CUCM / RHEL CUCM / RHEL
Version X Version Y
8.5 RHEL 4 Update 8
8.6* RHEL 5 Update 5
SU
9.X RHEL 5 Update 7
RU
SU
New 11.5(1) RHEL 6 Update 7
12.X
CUCM / RHEL CUCM / CentOS 12.0(1) CentOS 6

Version X Version Z
12.5(1) CentOS 7
Reference
Reboot Options (preferred)
CUCM
Upgrade Type Switching Type Reboot Options
Standard Upgrade Automatic Switch to new version after upgrade (system reboots)
Manual Do not switch to new version after upgrade (no system
reboots)
Refresh Upgrade Automatic Switch to new version after upgrade (system reboots)
Manual Do not switch to new version after upgrade (no system
reboots)
Unity Connection
Upgrade Type Switching Type Reboot Options
Standard Upgrade Manual Do not switch to new version after upgrade (no system
reboots)
Refresh Upgrade Manual Do not switch to new version after upgrade (no system
reboots)
Reference
SU Cluster Upgrade Sequence for Least
Service Impact
Sequence 1 2 3 4 5 6 7 8
SU
CUCM
Manual Switch DB Sync DB Sync
Pub
CUCM
Manual * Switch DB Sync
Primary Subs
CUCM
Secondary Manual Switch DB Sync * DB Sync
Subs
IM&P
Manual Switch DB Sync
Pub
IM&P
Subs
Reboot Option
*Phone registration using CM Groups and/or disable CM Service on the other CUCM Subs
RU Cluster Upgrade Sequence for Least Reference
Service Impact
Sequence 1 2 3 4 5 6 7 8 9 10 11
RU
CUCM
Manual Switch DB Sync DB Sync
Pub
CUCM Manual
* Switch DB Sync
Primary Subs **
CUCM
Manual * Switch DB Sync * DB Sync
Secondary Subs
IM&P DB Sync
Manual Switch
Pub
IM&P DB Sync
Manual Switch
Subs
Reboot Option
*Phone registration using CM Groups and/or disable CM Service on the other CUCM Subs
** Phone registration after upgrade
Cluster Upgrade Sequence for Shortest Upgrade Time
Sequence 1 2 3 4 5 6 7
SU
CUCM
Pub
CUCM
Subs
Reference
IM&P DB Sync
Manual Switch
Pub
IM&P
Subs
Sequence 1 2 3 4 5 6 7 8 9
RU
CUCM
Pub
CUCM
Subs Reference
IM&P Switch
Manual DB Sync
Pub
IM&P
Subs
Reference
Minimal Upgrade Duration
Products SU RU Switch DB
(hours) (hours) (hours) Replication *
(hours)
CUCM ½ - 2 or
2-4 3-5 1/2
Pub more
CUCM ½ - 2 or
1-2 1-2 1/2
Subs more
IM&P ½ - 2 or
2-4 3-5 1/2
Pub more
IM&P ½ - 2 or
1-2 1-2 1/2
Subs more
Sample Cluster Upgrade
12-15 16-20 8*
(least impact)
• There are many characteristics and specific details that will negatively and excessively impact these optimal
durations especially DB replications. In some cases, it can take many hours especially over slow WAN link.
• Use your specific past upgrade baseline
* Some DB replication takes over 14 hours
SU Cluster Upgrade for Least Service Impact
CUCM 12.5 Upgrade Enhancement
Sequence SU 1 2 3 4 5 6 7 8
CUCM Pub Manual Switch DB Sync DB Sync
CUCM Primary Subs Manual * Switch DB Sync
CUCM Secondary Subs Manual Switch DB Sync * DB Sync
IM&P Pub Manual Switch DB Sync
IM&P Subs Manual Switch DB Sync
Upgrade Inactive Partition and Database

Replication Setup Enhancement
Sequence SU 1 2 3 4 5 6
CUCM Pub Manual DB Sync Switch
CUCM Primary Subs Manual/DB Sync * Switch
CUCM Secondary Subs Manual/DB Sync Switch * Example

IM&P Pub Manual DB Sync Switch
IM&P Subs Manual/DB Sync Switch
Available after upgrading to CUCM 12.5 and for future upgrades
Sample Upgrade Schedule in CUCM 12.0 and
Earlier
Sequence SU 1 2 3 4 5 6 7 8
CUCM Pub Manual Switch DB Sync DB Sync
CUCM Primary Subs Manual * Switch DB Sync
CUCM Secondary Subs Manual Switch DB Sync * DB Sync
IM&P Pub Manual Switch DB Sync
IM&P Subs Manual Switch DB Sync
CUCM ≤12.0 Scheduled Onsite/Downtime for Upgrade
Month
Weekend
Potential Upgrade Schedule Benefits
CUCM 12.5 Enhancement (Upgrade and Replication Setup)
Sequence SU 1 2 3 4 5 6
CUCM Pub Manual DB Sync Switch
CUCM Primary Subs
CUCM Secondary Subs

Manual/DB Sync
Manual/DB Sync
*
Switch
Switch
*
Example
IM&P Pub Manual DB Sync Switch
IM&P Subs Manual/DB Sync Switch
Upgrade During Month Less Scheduled Month

CUCM ≥12.5
Work Days Off Hours Weekdays
Onsite/Downtime Weekend
• Available after upgrading to CUCM 12.5 and for future upgrades

• Freeze changes (MACD) or track changes to incorporate after the upgrade
CUCM 12.5 Cluster Software Location with OS
Admin (Publisher sFTP Credential)
PUBLISHER
SUBSCRIBER
sFTP
• Publisher secure ftp server and sftp credential can

be use for all subscribers for upgrade
• Minimize going to all the other subscribers
CUCM 12.5 Cluster Upgrade with OS Admin
(Publisher only)
PUBLISHER
SUBSCRIBER CUCM 12.5

Cluster Upgrade
• Use OS Admin on Publisher to initiate cluster upgrade

• Minimize going to all the other subscribers as previous approach
CUCM 12.5 Cluster Reboot/Switch Version with
OS Admin (Publisher only)
PUBLISHER
SUBSCRIBER
• Use OS Admin on Publisher to initiate cluster Reboot or Switch Version

• Minimize going to all the other subscribers as previous approach
Example: CUCM 12.5 Cluster Upgrade Schedule
Upgrade During Month Less Scheduled Month
CUCM ≥12.5
Work Days Off Hours Weekdays
Onsite/Downtime Weekend
Database Replicate Set Up after

Upgrade
• Available after upgrading to CUCM 12.5 and for
future upgrades
• Freeze changes (MACD) or track changes to
incorporate after the upgrade
Upgrade Methods and Tools – Unified CM OS
Direct
DSU Standard
Upgrade Unified CM OS Admin Upgrades
Direct Native and embedded tool
DRU Refresh
Upgrade * Simple Upgrade in CUCM 12.5
Upgrades
Method
PCDU PCD
Upgrade Prime Collaboration Deployment
(PCD) Upgrades and Migrations
PCDM
PCD External tool (virtual machine)
Migrate
PCD Upgrades and
Migrations
PCD Upgrades and Migrations
U Direct Upgrade (SU and RU)
Prime
Collaboration
Deployment
Migrate existing clusters
M • Simple – same network settings (IP addresses and/or
hostnames)
• Network – new network settings (IP addresses and/or
hostnames)
Prime Collaboration Deployment CUCM Capabilities
CUCM 12
Upgrade ISO CUCM Cluster CUCM Cluster CUCM Cluster
Upgrade Cluster Migrate Cluster
CUCM 12
CUCM Cluster Upgrade ISO CUCM Cluster
PCD Cluster Discovery Fresh Install
Host1/IP1
CUCM Cluster Host2/IP2 CUCM Cluster CUCM Cluster
Switch Version Readdress Restart

Reference
PCD Capabilities for other Collaboration Applications
IM&P Presence
Unity CUCCX
Connection
PCD 12.0 Environment Requirements
OVA
PCD
PCD ESXi Host
PCD 12.1.1 ESXI ESXI ESXI Edition
Version Version
2
vCPU
(2000Mhz) 4.1 5.5 • Cisco UC Virtualization Foundation (appears as
“Foundation Edition” in vSphere Client)
vRAM 4GB 5.0
6.0 • Cisco UC Virtualization Hypervisor Plus 6.0 or higher
5.1 • VMware vSphere Standard Edition, Enterprise Edition,
vDisk 80GB
6.5 or Enterprise Plus Edition
5.5
CentOS 6 • Evaluation mode license (for example, for lab
Guest OS 6.0 deployments and not production use)
(64 bit)
vNIC Adapter VMXNet3 6.5

* End of General Support for ESXi 5.5 is September 19, 2018
PCD Upgrade
sftp to /upgrade directory
CUCM 12 Direct Upgrade

Upgrade ISO,
COP files
PCD
Standard Upgrade
CUCM & IM/P
Cluster
Refresh Upgrade
PCD Migrate
Add Source CUCM Clusters to PCD
Discover Cluster 3 Add ESXi hosts to PCD
4 Inventory ESXi Hosts
Define Migration Destination Cluster
Migration Task 5
or
CUCM & IM/P
Migration Task 5 Cluster
CUCM & IM/P
Cluster
2 OVA
1 Deploy OVAs
sftp to /fresh_install directory
CUCM 12
PCD Bootable ISO
PCD Assisted Upgrades and Migrations
PCD Upgrade (Virtual to Virtual)
From CUCM Version Target CUCM
U 8.0(3), 8.6(1),8.6(2),9.0.(1),9.1(1),9.1(2),10.0(1),
Version
10.X, 11.X or 12.X
10.5(1),10.5(2),11.0(1),11.5(1), 12.0(1)
Prime
Collaboration PCD Migration (Physical to Virtual)
Deployment From CUCM Version Target CUCM
Version
M 6.1(5),7.1(3),7.1(5),8.0(1),8.0(2),8.0(3),
8.5(1),8.6(1),8.6(2),9.0.(1),9.1(1),9.1(2)
10.X, 11.X or 12.X
Simple Migration: Source network settings (IP addresses

and/or hostnames)
Network Migration: New network settings (IP addresses
and/or hostnames)
PCD Considerations and Planning
• Consider appropriate version and edition of hypervisor to run PCD
• Lab testing with or without NAT feature
• Allow network traffic to and from PCD
• SU/RU upgrade does not automate COP file installation. PCD 12.5 can batch COP files
installation and upgrade with Task Chaining
- ciscocm.version3-keys.cop.sgn
- ciscocm.refresh_upgrade_v1.3.cop.sgn
• Inspect PCD logs via activelog tomcat/logs/ucmap/log4j/ucmap*.log
PCD Administration Guide:

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/pcdadmin/12_0_1/cucm_b_pcd-admin-guide-121a.html
Upgrade and Migration Tools
Upgrade and Migration Tools
Tools OS Admin (12.5+ with Cluster Wide
PCD
Upgrade)
Collaboration CUCM and IM&P ONLY CUCM, IM&P, CUC*, CUCCX*
Applications
Size of Small to Medium Medium to Large
Deployment
Cluster Level Upgrade, Restart and Switch Version Upgrade, Migrate, Restart, Switch
Task Version, Fresh Installation, and
Readdress
Tool Resource Native and Built-In External Virtual Machine
* No Migrate option
CUCM Upgrade COP
Files
Reference
CUCM Upgrade COP Files
CUCM X CUCM Y
Current Version Target Version COP File Required
<8.5.1.17123-1 10.5(1) or higher ciscocm.version3-keys.cop.sgn

<8.6(2)su5
<9.1(2)su1
8.5(x) or lower 8.6 or higher ciscocm.refresh_upgrade_v1.5.cop.sgn
Upgrade Path
Virtualized CUCM to Virtualized CUCM 12.0
CUCM 8.6
CUCM 9.X
CUCM 12.0
CUCM 10.X PCD Upgrade or
Unified CM OS Admin
CUCM 11.X
CUCM
CUCM Version Upgrade Type COP File(s)
8.6 RU ciscocm.version3-keys.cop.sgn (<8.6(2)su5)
9.X RU ciscocm.version3-keys.cop.sgn (<9.1(2)su1)
10.X SU
11.X SU
Virtualized CUCM to Virtualized CUCM 12.5
CUCM 8.6
CUCM 9.X
CUCM 12.5
CUCM 10.X PCD Upgrade or
Unified CM OS Admin
CUCM 11.X
CUCM 11.X
CUCM
CUCM Version Upgrade Type COP File(s)
8.6 RU ciscocm.version3-keys.cop.sgn (<8.6(2)su5)
9.X RU ciscocm.version3-keys.cop.sgn (<9.1(2)su1)
10.X RU
11.X RU
12.0 RU
Appliance (MCS) to Virtualized CUCM 12.X
CUCM 6.1(5)
CUCM 7.1(3/5)
CUCM 12.X
CUCM 8.X PCD Migration
CUCM 9.X
• PCD Migration is recommended
Reference
CUCM Upgrade Type and Upgrade Method
MCS to CUCM 12.0
CUCM Version Upgrade Type Upgrade Method
6.1(5) NA PCD
7.1(3/5) NA PCD
8.X NA PCD
8.6 RU PCD
9.X RU PCD
Virtualized to CUCM 12.0

8.6 RU PCD or Unified CM OS Admin Upgrade
9.X RU PCD or Unified CM OS Admin Upgrade
10.X SU PCD or Unified CM OS Admin Upgrade
11.X SU PCD or Unified CM OS Admin Upgrade
12.0 SU PCD or Unified CM OS Admin Upgrade
Reference
CUCM Upgrade Type and Upgrade Method
MCS to CUCM 12.5
6.1(5) NA PCD
7.1(3/5) NA PCD
8.X NA PCD
8.6 RU PCD
9.X RU PCD
Virtualized to CUCM 12.5

Platform Support
and Migration
5
Reference
Previous Sessions for UC on UCS Migration
• BRKUCC-1903 - Migration and Co-Existence Strategy for Collaboration Applications in a
Virtualized Environment (2014 San Francisco)
• BRKUCC-1903 - Migration and Co-Existence Strategy for Unified Communications (UC) or
Collaboration Applications on Unified Computing Systems (UCS) (2013 Orlando)
Platform Selection
and Migration
Appliance to Virtualization Conversion
UC App UC App UC App UC App
3 VOS VOS VOS VOS
2
Platform ESXi 5/6 Hypervisor
Conversion
Server Hardware
1 Physical Server (BE7000)

CPU Memory NIC Storage
1. Server platform selection

2. VMware ESXi requirements
3. Conversion of appliance to virtual machine or OVA
* Leverage “Cisco Collaboration Virtualization” website (frequent changes)
Cisco Collaboration Virtualization

http://www.cisco.com/go/virtualized-collaboration
1. Server Platform Selection
Business Edition appliances Tested Reference Specs-Based- Specs-Based-
(“Packaged Collaboration Solutions”) Configurations (TRCs) UCS 3rd-party
BE6000M BE7000M “UC on UCS” “UC on UCS” with 3rd-Party with
BE6000H BE7000H with fixed-configuration “min specs” “min specs”
etc. etc.
Turnkey IT More Simpler, but Prescriptive
Flexible, but more Complex More Traditional IT
“Do it for me…” “Tell me what to do…” “I know what I’m doing…”
Current Packaged Collaboration Solutions
BE7000M (M5) BE7000H (M5)
BE6000M (M5) BE6000H (M5)
C220 M5SX TRC#1 C220 M5SX TRC#2 C240 M5SX TRC1 C240 M5SX TRC#1
Small Small Plus Medium Large
End of Sales and Support Considerations
• C210M2 End of HW Support is Jan. 31, 2018
• C210M2 is Only supports up to ESXi 5.5
C210M2 UC on UCS
ESXi 5.5 • ESXi 5.5 End of General Support is September 19, 2018
• Start upgrading ESXi to 6.X. Current latest supported version is ESXi 6.5.
Soon EOS Packaged Collaboration Solutions (June 30, 2018)

BE7000M (M4) BE7000H (M4)
BE6000M (M4) BE6000H (M4)
C220 M4S TRC#1 C220 M4S TRC#2 C240 M4S2 TRC1 C240 M4SX TRC#1 B200 M4 TRC#1
Small Small Plus Medium Large
• Supported older releases of collaboration applications

• Short term support for large number of collaboration applications
2. VMware Requirements (Sample for CUCM)
vCenter Mandatory
for Spec-based
CUCM Version ESXi Version ESXi Edition
12.X 5.0 U1, 5.1, 5.5, 6.0 and 6.5 Cisco:

Cisco UC Virtualization Hypervisor
11.5 5.0 U1, 5.1, 5.5, 6.0 and 6.5 Cisco UC Virtualization Hypervisor Plus
Cisco UC Virtualization Foundation
11.0 5.0 U1, 5.1, 5.5, and 6.0
Cisco or VMware:
10.5 4.0 U4, 4.1 U2, 5.0 U1, 5.1, 5.5, 6.0 and Standard, Enterprise or Enterprise Plus
6.5
10.0 4.0 U4, 4.1 U2, 5.0 U1, 5.1, 5.5, and 6.0
9.1 4.0 U3, 4.1 U1, 5.0, 5.1, 5.5, and 6.0
Cisco Virtual Machine Template (OVA) File
OVA
2
CCO
1
vSphere
Client Business Edition 7000
• Open Virtual Archive (OVA): Portable virtual appliance that defines configuration
(memory, storage space, etc.) for a virtual machine and is a compressed version of OVF
• Cisco will provide OVA files with Virtual Machine Hardware Version (VMV) 7 and VMV8
on CCO for collaboration applications deployment
• Deploy the latest OVA version and the highest available VMV version that matches to
ESXi version
Example of ESXI and Collaboration OVA Version
ESXi Version VMware Virtual Recommended Cisco Collaboration Collaboration Application VMV Version Cisco
Machine Hardware OVA VMV Version Application Version OVA Version
Version (VMV)
5.0U1 8 8 cucm_12.0_vmv8_v1.0.ova
5.1 9 8
CUCM 12.0 8 1.1
5.5 10 8
6.0 11 8
6.5 13 8
• Use matching collaboration application to OVA file especially with the new separated
ISO files for CUCM and IM&P
– E.g. cucm_12.0_vmv8_v1.0.ova and Bootable_UCSInstall_UCOS_12.0.1.21900-
7.sgn.iso
• VMV can be upgraded, but cannot be downgraded. Keep as high as VMV 8
Virtual Machine Compatibility

http://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.vm_admin.doc%2FGUID-64D4B1C9-CD5D-4C68-8B50-585F6A87EBA0.html
3. Conversion of Appliance to Virtual Machine or OVA
OVA
MCS
Server
Maximum
Number of
OVA
Deployment
vCPU • Smaller MCS server converts to a standard
Model Phone Size 2500 device OVA or restricted performance
7845-I3 or 10000 10000 4 CPU OVA on CUCMBE 6K
earlier
7845-I3 or 7500 7500 2
• MCS and C series both has similar direct
earlier attached storage (DAS)
7845- 7500 7500 2
I2/H2 or • Storage option for redundancy: FC SAN
earlier
7825-I5 or 1000 2500 2
earlier
7825-I5 or 1000 1000 2
earlier
7816-I5 or 500 1000 2
earlier
7828-I5 or 500 1000 2 Restricted performance CPU (CUCMBE 6K)
earlier
Reference
Appliance versus Virtualization Support
Feature Appliance Virtual
Music on Hold (live source) USB audio (unicast and IOS or Barix (multicast only) *
multicast)
Install and upgrade error logs USB Virtual serial port
Answer file (platformConfig.xml) USB Virtual floppy
UPS via USB APC UPS via USB UPS on UCS/ESXi
Back up Tape Secure ftp
eToken encryption key USB on client and not server USB on client and not server
SMDI Serial port NA
• Take these support considerations into account when virtualizing CUCM
• * Multicast to Unicast conversion with CUCM 11.5. for specific phones, SIP trunk, SBC,
etc.
UCS, VMWare and
Collaboration Operational
Support
Dependencies and Support: Applications, OVA,
ESXi Version and UCS Firmware/Hardware
CUCM Version ESXi Version
Collaboration application to 12.0 5.0 U1, 5.1, 5.5, 6.0 and 6.5
supported version of ESXi
https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_
system/virtualization/cisco-collaboration-virtualization.html
UCS hardware and

supported version of ESXi ESXi Version UCS hardware supported/not supported
6.5 C210M2, C210M1

6.5 C240M4S2: firmware 3.2(3)
https://ucshcltool.cloudapps.cisco.com/public/
• Upgrade of collaboration application might requires ESXi version upgrade
• New version of ESXi might requires new OVA files (e.g. ESXi 6.5). Use the latest OVA files
• Upgrade of ESXi version (application or ESXi standardization) might requires

• UCS firmware update (e.g. firmware 3.2(3) on C240M4S2)
• UCS hardware replacement (e.g. C210M2 and ESXi 6.5 or later)
VMware OVA Support
and Virtual Machine
Migration
Reference
CUCM 7,500 Devices OVA Changes
CUCM 7500 8.5 8.6 9 9.1 10.X 11.X 12.0 12.5
vCPU 2 2 2 2 2 2 2 2
(1300Mhz) (3600Mhz) (3600Mhz) (3600Mhz) (3600Mhz) (3600Mhz) (3600Mhz) (3600Mhz)
vRAM 6GB 6GB 6GB 6GB 6GB 8GB 8GB 8GB

vDisk 2 x 80GB 2 x 80GB 2 x 80GB optional 110GB 110GB 110GB 110GB 110GB
Guest OS RHEL 4 (32) RHEL 4 (32) RHEL 5 (32) RHEL 5 (32) RHEL 6 (64) RHEL 6 (64) CentOS 6 (64) CentOS 7 (64)
vNIC Adapter Flexible Flexible Flexible Flexible VMXNet3 VMXNet3 VMXNet3 VMXNet3
VMware Check and Check and Check and Check and

Tool/Advance No No No No
upgrade Tools upgrade Tools upgrade Tools upgrade Tools
• Shutdown virtual machine (vm) and apply changes BEFORE upgrade

• vCPU: Change “Reservation” values (Resources)
• vRAM: Change “Reservation” values (Resources)
• vDisk: Change “Provisioned Size” (Resources)
• vNIC: Change vNIC type. Instruction in the appendix and in README files
• Guest Operating System (OS): Change Guest OS and Version (Option)
Reference
CUCM 10,000 Devices OVA Changes
CUCM 8.6 9 9.1 10.X 11.X 12.0 12.5
10000
vCPU 4 4 4 4 4 4 4
(7200Mhz) (7200Mhz) (7200Mhz) (7200Mhz) (7200Mhz) (7200Mhz) (7200Mhz)
vRAM 6GB 6GB 6GB 6GB 8GB 8GB 8GB
vDisk 2 x 80GB 2 x 80GB optional 110GB 110GB 110GB 110GB 110GB
Guest OS RHEL 4 (32) RHEL 5 (32) RHEL 5 (32) RHEL 6 (64) RHEL 6 (64) CentOS 6 (64) CentOS 7 (64)
vNIC Adapter Flexible Flexible Flexible VMXNet3 VMXNet3 VMXNet3 VMXNet3

VMware Check and Check and Check and Check and
Tool/Advance No No No
upgrade Tools upgrade Tools upgrade Tools upgrade Tools
• Shutdown virtual machine (vm) and apply changes BEFORE upgrade

• vCPU: Change “Reservation” values (Resources)
• vRAM: Change “Reservation” values (Resources)
• vDisk: Change “Provisioned Size” (Resources)
• vNIC: Change vNIC type. Instruction in the appendix and in README files
• Guest Operating System (OS): Change Guest OS and Version (Option)
Clarifications
• OVA with dual 80GB vDisk is supported with CUCM 9.X, 10.X, 11.X
and 12.0
• Secondary vDisk on OVA with dual 80GB vDisk has the /common partition and
can be extended at release CUCM 10.0 and later for upgrade space
• Primary vDisk on OVA with dual 80GB vDisk are partitioned with various disk
partitions with respective sizes and cannot be resized to 110GB to match with
the newer OVA
• Resize Virtual Machine
http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtual
ization/virtualization-software-requirements.html#resize_vm
• To change OVA that from dual 80GB vDisk to single 110GB vDisk
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/install/11_5_1/r
eplace/cucm_b_replacing-single-server-or-cluster-1151.html
CUCM 11 to CUCM 12.X Guest OS Change
Features CUCM 11.X CUCM 12.0 CUCM 12.5
Guest OS RHEL 6 CentOS 6 CentOS 7

(64 bit) (64 bit) (64 bit)
• Shutdown CUCM
• Change the Guest OS from RHEL 6 (64 bit) to CentOS 4/5/6/7 (64 bit)
– ESXi 5.5 only has CentOS 4/5/6 (ESXi 5.5 End of Technical Guidance 9/19/2018)
https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/support/product-
lifecycle-matrix.pdf
– Should be done before CUCM upgrade
• Upgrade to CUCM 12.X
Reference
CUCM 9 to CUCM 10/11/12 Adapter Change
Features CUCM 9.X CUCM 10.X/11.X/12.X
Guest OS 5 (32bit) RHEL 6 (64 bit)/CentOS

6/7 (64 bit)
Adapter Type Flexible VMXNet3
• Update to the latest VMtools if not auto upgrade
• Shutdown CUCM
• Change Network adapter type from Flexible to VMXNET3

– Automatic MAC: Edit VMX file in the VM machine directory. Instruction in link below
– VMware vSphere PowerCLI for both automatic and manual MAC. Instruction in link below
• Upgrade CUCM
CUCM 12.0 OVA:

https://www.cisco.com/web/software/283088407/139512/cucm.ova.README_12.0.pdf
System Preparation and
Optimizing Upgrade
Speed for CUCM
Upgrade
6
CUCM 12.0 Phone
Deprecation
CUCM Phone Deprecation
CUCM 12.0 CUCM 11.5
12 S, 12 SP, 12 SP+, 30 SP+, 30

VIP, 7902G, 7905G, 7910,
Phone Models 7921, 7970 and 7971
7910G, 7910+SW, 7910G+SW, 7912G,
7920 and 7935
* Phones will NOT register to CUCM
Starting Upgrade to 11.5 or Login After Upgrade Add Deprecated Phone After
12.X Upgrade
Warning banner in CCM Admin
Warning in “Upgrade Status” when these phones are in the
Notification Add action fails
field database
Delete these phones out of the Only add supported models of

Remediation Upgrade phone models
database phones
CUCM 12.0 AND 11.5 Deprecation Phone Models
• Field Notice
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/12_0_1/deprecated_ph
ones/cucm_b_deprecated-phone-models-for-1201.html?emailclick=CNSemail
• Phones (17 models) will not be able to register to CUCM 12.0
• Check phone models for support and migrate IP phones using Endpoint Refresh Tool -
Migration FX before upgrading to CUCM 11.5
• Free Migration FX software for 1 years with a Cisco TMP of 100 78XX/88XX IP phones
(L-CP-MGFX-PROMO=)
• Free Trial Version of MigrationFX (up to 50 phones) from UnifiedFX
Endpoint Refresh Tool - Migration FX
http://refreshcollab.cisco.com/webportal/66/Endpoint%20Refresh%20Tool 3
Disk Space Required in
/common Partition for
Upgrade
Disk Space for Upgrade
Extending vDisk Space
25GB Required
10.X or later Resize vDisk (2nd vDisk if 2 X 80GB)
/common
partition
8.5(1), 8.6(2), 9.1(1), ciscocm.vmware-disk-size-reallocation-
CUCM 12 9.1(2) 1.0.cop.sgn
Upgrade ISO
Deleting files
All CUCM Versions Reduce log files
9.1 and earlier ciscocm.free_common_space_v1.3.k3.cop.sgn
• Reduce log files:

• LogPartitionLowWaterMarkExceeded 30% (default 80%)
• LogPartitionHighWaterMarkExceeded 40% (default 85%)
• Delete old ATS & RIS Database Aborted Transaction logs
• file delete activelog cm/log/informix/ats/* noconfirm
• file delete inactivelog cm/log/informix/ats/* noconfirm
Improve Performance
Improve Upgrade Performance
• Change TFTP service parameter for dedicated TFTP server on CUCM 5.1(1c) or later:
• System > Service Parameter > Cisco TFTP (Advance)
• Maximum Serving Count (default is 500)
• 1,500 for single processor dedicated TFTP server and 3,000 for dual processors dedicated TFTP
server
• Increase database replication parallel processing count (Publisher)

• utils dbreplication setprocess 40 (default is 1)
• Increase database replication timeout for large cluster (Publisher)

• utils dbreplication setrepltimeout <3600> (default is 300)
• Range is 300 to 3600
Upgrade Optimization: Replication Time Improvement –
Previously Best Practices
Blocked Error and Warning Messages
Replication configuration
changes
DB changes that
impacts AXL 503 error response: “Write Operations
replication time denied because Cisco UCM or IM and
Presence upgrade is in progress.”
Replication time BAT Error message "Upgrade in Progress.
as a function of Job cannot be started"
bandwidth
LDAP Sync. "Upgrade in progress. Cannot be
synced"
• Disabling provisioning during upgrade. Previously Self Care Portal WARNING: Add/Update/Delete not
allow as a system upgrade is in
are best practices for upgrade in previous version progress
• Disable EM service in CUCM 9 and earlier not included UDS 503 error response
• IBM IDS new feature implementation for transmitting CM Admin

MACD
Banner and Status
files in bulk CCM Service Update failed

Activation/Trace Add/Update/Delete not allow as a
• Sync Agent sync time optimization system upgrade is in progress
Phone auto- Auto-registration disabled/IVR return

registration and error
Self Provisioning
Upgrade Execution
and CUCM Registration
with Smart Licensing
7
Execution in Phases: Minimizing Upgrade Window
1Phase I:
2
Phase II:
3
Phase III:
4Phase IV:
5 Phase V:
6
Phase VI:
Owner User ID / phone IP Phone Proactive UC Applications Pre- Prepare CUCM for CUCM and UC
association and Replacement Upgrade Migration Upgrade Applications Post
Firmware Upgrade Upgrade Migration
license request
IP Phone UC Applications CUCM

Replacement Apply COP files
Firmware Upgrade Upgrade
• Phase II, IV or V might have to be repeated for each of

the step in a multi-step upgrade
• Check with Compatibility Matrix on Collaboration UC Applications
applications and firmware compatibility Upgrade
Smart Licensing for
CUCM
CUCM Smart Licensing Overview
• Smart Licensing is enabled by default on CUCM 12.0 and later

• Evaluation mode 90 days with full capacity
• 90 days evaluation timer counts down when CUCM starts to consume licenses
regardless if register or unregister to Cisco Smart Software Manager (CSSM) or Smart
Software Manager satellite server
CUCM Smart License Management - Status
(System > Licensing > License Management)
Smart Software Licensing (Smart Agent)
Registration • Unidentified/Unregistered
Status • Registered
• Unregistered-Registration
Expired
License Authorization • No licenses in use
Status • Evaluation Mode
• Evaluation expired
• Authorized
• Out of compliance
• Authorization Expired
• Smart Software Licensing of CUCM is the status of the Smart Agent communication
to Cisco Smart Software Manager (CSSM)
• Status of CUCM license can be seen in the Status section or CUCM banner
Reference
Smart Licensing States in CUCM
Registration Status Authorization Status Evaluation Period Overage Period (90 Enforcement (No MACD)
(90 days) days)
Unregistered or Evaluation Mode Start with 90 and NA No
Registration Expired will decrement if
UCM is consuming
licenses
Unregistered or Evaluation Expired 0 days NA Yes
Registration Expired
Registered or No Licenses in Use NA NA No

Unregistered or
Registration Expired
Registered Authorized NA NA No
Registered OOC NA Overage period No till overage period is applicable

remaining Yes after overage days(90 days) are
over
Registered Authorization Expired NA Overage period No till overage period is applicable
remaining Yes after overage days(90 days) are
over
* CUCM Smart License banner status in the slide notes
CUCM Registration with
Smart Licensing
Reference
Direct CUCM Smart Licensing Registration
• software.cisco.com > Smart Software

Licensing > Inventory > General
Log into • Select the appropriate Smart Account and
CSSM Virtual Account
cisco.com
• Copy existing Product Instance Registration

Token or Cisco
Registration • Create New Token Smart
Token from • Copy or download token Software
CSSM Manager
(CSSM)
• System > License Management > Register

• Direct or HTTP/HTTPS Proxy transport setting
Register • Paste token and register
CUCM
Transport Settings for CUCM for Smart Licensing
• Set communication between CUCM Publisher and CSSM or Smart Software Manager
satellite server
• Smart License Deployment Model
• Direct: Direct cloud access
• Transport Gateway: Mediated access through an on premise collector (Smart Software Manager satellite)
• HTTP/HTTPS Proxy: Direct cloud access through an HTTPs proxy
Registering CUCM with Smart Licensing
Smart Software Central > Smart Software Licensing > Inventory > General System > Licensing > License Management
• Create or copy existing registration token from CSSM or Smart Software

Manager satellite server to CUCM
CUCM SLR (Specific
License Reservation)
Process with Smart
Licensing
Specific License Reservation with CUCM 12.5
CUCM 12.5 SLR - Reservation
CSSM
License Service
Browse to obtain Reservation Request Code (UDI)

Select Smart Account and Virtual Account to reserve licenses
Supported Role Select License Reservation and enter in Reservation Request Code
Smart Account Admin Choose type of licenses, Perpetual or Term based licenses and quantity Cisco System
Smart Account User
Virtual Account Admin Select Generate Authorization Code
Publisher Enter Authorization Code Virtual Account User
for license
management Reserved Licenses
• Specify and reserve Perpetual or Term based licenses on CSSM for CUCM 12.5 or
later
• For highly secure network which does not requires regular sync to CSSM
• Reserved Licenses remained effectively reserved in CSSM until CUCM generate a
Reservation Return Code (return the SLR authorization for the product)
• Reserved Licenses in CSSM can be transferred across Virtual Account as needed
Specific License Reservation with CUCM 12.5
CUCM 12.5 SLR - Update
CSSM
License Service
Select the CUCM instance to update licenses on
Select Update Reserved Licenses

Supported Role Make changes to license reservation
Smart Account Admin Obtain Authorization Code Cisco System
Enter new Authorization Code Smart Account User
Virtual Account Admin
Publisher Obtain Confirmation Code Virtual Account User Enter Confirmation Code
for license
management Reserved Licenses
• Change in reserved licenses (increase or decrease) can be done on previous

reserved licenses in CSSM
• The new updated license reservation is effectively reserved in CSSM as soon as
Authorization Code is generated
• If new updated license reservation is a decrease in quantity, then a Confirmation Code
is required to reduce
System Level Planning
Upgrade/Migration Optimizing Upgrade
License Management Platform System Preparation Execution
Methods and Tools Speed
Smart Licensing DSU Servers Deprecated TFTP server Phone firmware

Smart Account DRU Virtualization phones DB replication Application
License Conversion PCDU Virtualized CUCM Disk Space Purge CDR dependencies
License Optimization
PCDM VMware changes COP file(s) Upgrade windows
Smart Registration
SLR Registration
Pre-Upgrade list Post-Upgrade list

link (end of slide link (end of slide
deck) deck)
Reference
Upgrade Tasks
• Pre-Upgrade Task
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/11_5_1/cucm_b_upgrad
e-guide-cucm-115/cucm_b_upgrade-guide-cucm-115_chapter_010001.html
• Post-Upgrade Task List
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/11_5_1/cucm_b_upgrad
e-guide-cucm-115/cucm_b_upgrade-guide-cucm-115_chapter_01000.html
Questions ?
Thank you
#CLUS
Reference Links
Reference
Reference links
• Product License Registration
www.cisco.com/go/license
• Product Upgrade Tool (PUT)
www.cisco.com/upgrade
• Unified Communications in a Virtualized Environment
http://www.cisco.com/go/uc-virtualized
• UC Virtualization Supported Hardware:
http://docwiki.cisco.com/wiki/UC_Virtualization_Supported_Hardware#Table_1_-
_UC_on_UCS_TRCs
Reference
Reference links
• Unified Communications Licensing Availability by Release
https://communities.cisco.com/docs/DOC-57172
Complete your online session evaluation
Give us your feedback to be entered

into a Daily Survey Drawing.
Complete your session surveys through
the Cisco Live mobile app or on
www.CiscoLive.com/us.
Don’t forget: Cisco Live sessions will be available for viewing
on demand after the event at www.CiscoLive.com/Online.
Continue
your Demos in the
Cisco
Walk-in
self-paced labs
Meet the
engineer 1:1
Related
sessions
education campus meetings
Thank you
#CLUS
#CLUS
Appendix
CUCM License
Conversion:
1. PAK
2. Device
PAK based Migration – Assign to a Smart Account
• Consolidate unassigned PAKs to a Smart Account and Virtual Account for visibility
• Login to the Traditional Licensing Portal at http://tools.cisco.com/SWIFT/LicensingUI/Home
• Locate the PAKs to be migrated. Right click and select Assign to Smart Account and Virtual Account
© 2017 Cisco and/or its affiliates. All rights reserved. Cisco Confidential
1
PAK based Migration : Assign SA and VA
• Select the Smart Account and Virtual Account to which the PAK will be assigned
1
PAK based Migration : Classic PAK assigned
• Classic PAKs will show assigned Smart Account for full visibility
1
PAK Migration to Smart License on - LRP
• Select the PAK which needs to converted to smart entitlement.
• From the PAK context option, select “Convert to Smart Licensing”
1
PAK based Migration to Smart License on LRP -
Review and Submit
• Select SKUs under PAK and quantity of Licenses to be converted and click on Submit
• PLM Licenses which are partially converted will need new PLM License file for managing the remaining
Classic Licenses :
• PLM under e-fulfillment mode will receive new License file automatically
• PLM under manual fulfillment will need to download and manually upload new License file in PLM
1
PAK based Migration to Smart License on LRP-
Confirmation message
• Once the licenses are converted to smart entitlements, Success message is shown.
• The entitlements will now be available on CSSM under selected Smart and Virtual Account.
1
PAK based Migration to Smart License on CSSM
• Convert PAKs to equivalent Smart Licenses when they are available
• Go to Convert PAKs tab .
• Assigned PAKs will show up on the CSSM portal. Click Convert to Smart License
1
PAK based Migration to Smart Licenses on CSSM
(Select License)
• Select SKUs under PAK and quantity of Licenses to be converted
• PLM Licenses which are partially converted will need new PLM License file for managing the remaining
Classic Licenses :
• PLM under manual fulfillment will need to download and manually upload new License file in PLM
1
(Review and Confirm)
• Review and confirm.
• Once converted to Smart Entitlement, the old classic licenses will be invalidated
1
(Smart Licenses converted)
• Converted Smart Licenses added into the Smart Account and Virtual Account
1
Device based migration to Smart Licenses on LRP
• Login to the Traditional Licensing Portal at http://tools.cisco.com/SWIFT/LicensingUI/Home
• Go to Device tab. Locate the PLM Device to be migrated(please filter using PLM UUID)
• If not available : Obtain the License request from PLM and add the PLM Device.
1
Device based migration to Smart Licenses on LRP :
PLM device added
• PLM device added shows up under Device tab
1
Assign PLM Device
• Assign PLM device to Smart Account and Virtual Account
1
Select SA and VA
• Select Smart Account and Virtual Account to which PLM will be assigned
1
PLM device assigned
• Shows Smart Account assigned for the PLM device
1
• Select the device where the classical licenses needs to be converted to Smart entitlements.
• From the context option select “Convert licenses to Smart Licensing” option.
1
(Select Licenses)
• Select SKU and quantity of Licenses to be converted
• PLM Licenses which are partially converted will need new License file for managing the remaining Classic
Licenses :
• PLM under manual fulfillment will need to download and manually upload new License file
1
(Review and Submit)
• Review , Confirm and click Submit
• Once the licenses are fully converted, the PLM UUID will be removed from LRP
• Confirmation message will be shown once the licenses are converted.
• The entitlements will now be available on CSSM under selected Smart and Virtual Account.
1
Device based migration to Smart Licenses on CSSM
• Assigned Device will show up on the Cisco Smart Software Manager Portal. The CSSM portal will be
refreshed every 1 hour. If the assigned device is not visible in CSSM, please recheck after an hour.
• Go to Convert Licenses tab and click Use License Conversion wizard
1
Device based migration to Smart Licenses on
CSSM
• Select the Product family as “Cisco Unified Communications” and provide the PLM Device UUID
1
CSSM (Select License)
• Select SKU and quantity of Licenses to be converted
• PLM Licenses which are partially converted will need new License file for managing the remaining Classic
Licenses :
• PLM under manual fulfillment will need to download and manually upload new License file
1
CSSM (License converted)
• Review , Confirm and click Convert Licenses
• When old Licenses are converted, they will be invalidated
1
#CLUS

Rect

Uploaded by

Copyright:

Available Formats

Rect

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Rect

Uploaded by

Copyright:

Available Formats

#CLUS

Cisco Webex Teams

Webex Teams will be moderated

• Upgrade Enhancements with CUCM and IM&P 12.5

Details Might Change!

Cisco Live Access Sessions On-demand

• To provide foundational knowledge for a successful upgrade or migration to CUCM 12.X

• Upgrade or migrate to CUCM 12.X

Smart Licensing DSU Servers Deprecated TFTP server Phone firmware

Pre-Upgrade list Post-Upgrade list

License Manager Publisher ELM/PLM Cisco Smart Software Manager (CSSM)

CUCM License Licensing CUCM Description

Enhanced Plus Enterprise 12.X Migrated CUCM and BE6K licenses

Enhanced Enterprise 12.X Migrated CUCM and BE6K licenses

Basic Enterprise 12.X Migrated CUCM and BE6K licenses

Essential Enterprise 12.X Migrated CUCM and BE6K licenses

TelePresence Room Enterprise 12.X Migrated CUCM and BE6K licenses

CSSM CUCM License

CSSM CUCM License

Smart Account Smart License

Account Description and Usage Examples Sub Level:

View level access at the Smart Account Manager or trusted partners

• View properties of the assigned Virtual Deployment engineers

Smart Account • Edit/View Account Properties • No access • No access • No access

• Smart Account Information

2 Direct cloud access through an HTTPs proxy

3 Mediated access through an on-premises collector – connected Your

license authority. Periodically, an exchange of information will be performed to keep the

4 Mediated access through an on-premises collector – disconnected File

license authority. Once a month, an exchange of human readable information will be

performed to keep the databases in sync.

5 Full Offline Access – License Reservation File

CER CER CER

Specific License Reservation (SLR)

Basic Basic Basic Smart

Basic Essential Essential Essential

Session Management Edition 12.0 Smart ONLY

Unity Connection 12.0 Smart ONLY

Cisco Emergency Responder 12.0 Smart ONLY

Cisco Unified Communications Manager Express 11.0 Hybrid

SRST 12.1 Hybrid

Cisco Unity Express Virtual 9.0.5 Smart ONLY

Prime Collaboration Provisioning 12.4 Hybrid

vCUSP 9.0 Smart ONLY

vCUBE Current Hybrid

Types of Migration Approach

PAK Based Fulfilled, partial or unfulfilled PAK to Smart

* Steps with Screen captures are in the appendix

Device without Owner User ID association: UCL

Device Name OwnerUserID CUCM Version Device Name OwnerUserID

SEP123456789012 None 9.1(1a) or earlier SEP123456789012 UserX

SEP098765432109 Anonymous 9.1(2) or later SEP098765432109 UserY

Device Assignment Tool 11.5

11.5(1)SU3b 11.5.1.13902-2 11.5.1.10000-6

11.5(1)SU2 11.5.1.12900-21 (Y) FCS:0, ES or SU: 1-9

CUCM 12.X ISO

CUCM & Unity Connection

Unity Connection 12.X

CUCM 9.X What