Brkucc 2011

Best Practices for Migrating
Previous Versions of Cisco Unified

Communications Manager (CUCM)
to Version 11.5
Baha Akman, Technical Leader Services
baha@cisco.com
BRKUCC-2011
Agenda
1. Session Objectives and Scope

2. CUCM 11.5 Upgrade Methods & Definitions
3. CUCM Upgrades & Migrations with Prime Collaboration
Deployment (PCD)
4. CUCM Licensing Overview & Prime License Manager
5. CUCM 11.5 Upgrade Paths
6. System Level Planning and Considerations
• Q&A * Cisco Unified Communications Manager = CUCM = Unified CM = CallManager
* Cisco Prime License Manager = PLM = Cisco Enterprise License Manager = ELM
Session Objectives and Scope
1
Session Highlights
• Direct Standard Upgrade (SU aka L2)
CUCM Upgrades • Direct Refresh Upgrade (RU)
• Automated process with PCD

CUCM Migration • CUCM 10+ Virtualized ONLY (MCS  UCS)
Prime Collaboration • CUCM Orchestration tool for operational tasks

• Migrations, Upgrade, COP file installation, fresh
Deployment (PCD) installation or hostname/IP Address change
BRKUCC-2011 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 5
Reference
Solution Names and Versions
CUCM / Unified CM /
License Manager
CallManager / UC Manager
Enterprise License Manager

Cisco CallManager
(ELM)
3.0-3.3
9.0 – 9.1
Prime License Manager

Cisco Unified CallManager
(PLM)
4.0-4.2
10.0-11.X
Cisco Unified
Communications Manager
(CUCM)
4.3-11.X
Platform Terminology
Bare Virtual
Metal Machine
VMware
Supported
Servers
Cisco UCS, Business Edition

MCS, HP or IBM Servers 6K, Business Edition 7K, TRC,
Specs-based
Session Scope
• Platform
1
conversion from
Bare Metal CUCM Migration Virtualized CUCM 11.5 bare metal
CUCM to
virtualized CUCM
2 Virtualized CUCM SU / RU Virtualized CUCM 11.5

11.5
• Upgrade or
migrate to CUCM
11.5
• System level
approach
Compatibility Information for Cisco Unified Communications Manager Release 11.x
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/compat/11_x/cucm_b_cucm-imp-compatibility-matrix-11x.html
CUCM 11.5 Upgrade Methods &
Definitions
2
CUCM Version, Build and Upgrade
Schedule
CUCM Major/Minor Versions
• Major and minor version upgrades requires active
CUCM Major CUCM Minor Cisco Software Support Service (SWSS)
•
Version Version End of Sales support service contracts
- Minor version upgrade requires active Essential
11.0 11.5 Operate Service (ESW) contract
- Major version upgrade requires active Unified
10.0 10.5 Communication Software Subscription (UCSS)
contract
9.0 9.1 • End of Sales (EOS) notice EOS
8.0 8.5 and 8.6 - http://www.cisco.com/c/en/us/products/collateral

/unified-communications/unified-
communications-software-subscription/eos-eol-
7.0 7.1 notice-c51-732026.html
6.0 6.1
5.0 5.1
End of Life/Support Notices and Release Selection
Milestone Potential Activity Summary
Before End-of-Sales Date Ability to deploying new cluster
After End-of-Sales Date Start planning for upgrades
End of SW Maintenance Desire to complete the upgrade 1 year
Deployment Models:
- Extended period on a single release with “Long-Life Release” (i.e. 10.5, 11.5, etc.)
- New features with “Short-Life Releases” (i.e. 11.0, 12.0, etc.)
Upgrade Planning:
- Consistent release cycles New
- Predictable End of Sales/Support milestone durations
End-of-Life and End-of-Sale Notices

http://www.cisco.com/c/en/us/products/unified-communications/unified-communications-manager-callmanager/eos-eol-notice-listing.html
Sample Upgrade Schedule for Long-Life Release New
End of SW
Maintenance
Cisco CUCM Version N
Email/RSS Feed End-of-Sale Releases Date:
App. SW
Notification of End-of-Sales Date
Service and End-of-Life End-of-Life

Announcement
Date
6 months 12 months
Active
CUCM Version Upgrade Window (UW)
(N+1)
UW
Active
CUCM Version
(N+2)
Long-life release customers can upgrade to every Long-Life release or every other Long-life
releases
Cisco Notification Service

http://www.cisco.com/cisco/support/notifications.html
Reference
Sample CUCM Versions and Builds
CUCM Version CUCM Build Numbering Convention
(A.B.C.XYzzz-x)
11.5(1)SU2 NEW
11.5.1.12900-25 (A) Major version (License)
11.5(1) 11.5.1.10000-6 10.5.2.10000-5

(B) Minor version (Long Life Release)
11.0(1a)SU2 11.0.1.22900-14
10.5.2.10000-5
11.0(1a) 11.0.1.20000-2 (C) Maintenance release (Patch and/or Features)
11.0(1) 11.0.1.10000-10 10.5.2.10000-5

(X) Build (Patch)
10.5(2)SU3a 10.5.2.13901-2 10.5.2.10000-5
10.5(2)SU3 10.5.2.13900-12 10.5.2.20000-5 (example)

(Y) FCS:0, ES or SU: 1-9
10.5(2)SU2a 10.5.2.12901-1
10.5.2.10000-5 (FCS)
10.5(2)SU2 10.5.2.12900-14
10.5.2.11900-1 (ES or SU look at last three digits)
10.5(2)SU1 10.5.2.11900-3 (zzz) FCS:000, ES: 001-899, SU: 900-999
10.5.2.10000-5 (FCS)
10.5(2) 10.5.2.10000-5
10.5.2.11001-5 (ES) (example)
10.0(1)SU2 10.0.1.12900-2
10.5.2.11900-3 (SU)
Upgrade Methods & Definitions
Upgrade Methods
Direct
DSU Standard
Upgrade (L2)
Unified CM OS Admin Upgrades
and Migrations
Direct
DRU
Refresh
Upgrade (RU)
Upgrade
Methods
PCDU
PCD
Upgrade
Prime Collaboration Deployment
(PCD) Upgrades and Migrations
PCD Migrate
PCDM
(M1)
Unified CM OS Admin Types of Upgrades
Standard Upgrade (formerly called L2 Upgrade):

Appliance/Virtual to Appliance/Virtual model
SU • Low complexity with possible shortest downtime
• Between CUCM versions with the same major RHEL
versions
Types of
• (e.g. CUCM 10.0 to 11.0 or CUCM 10.0 to 11.5)
Upgrades
RU (Refresh Upgrade): Appliance/Virtual to
Appliance/Virtual model with major RHEL version
RU change (starting with RHEL 5)
• Medium complexity with possible longer downtime
• (e.g. CUCM 8.6 to 11.5 or CUCM 9.1 to 11.5)
SU versus RU Upgrade
SU • Active partition is running while software upgraded on

inactive partition
• Low downtime since upgrade can be done while system
Upgrade is functioning
RU • Server is down while software is upgraded

• Higher downtime since upgrade cannot be done while
system is functioning
Upgrade • Upgrade Time is equal to Fresh installation of CUCM
Detailed SU and RU upgrade process

are in the appendix
CUCM Upgrade and Reboot Options (SU & RU)
Active Partition (CUCM 10) Inactive Partition (CUCM 10)
Inactive Partition (CUCM 9) Active Partition (CUCM 11)
1
CUCM CUCM
Publisher Publisher
CUCM 11 Active Partition (CUCM 10) Inactive Partition (CUCM 10)

Upgrade 2 Inactive Partition (CUCM 9) Active Partition (CUCM 11)
ISO
CUCM CUCM
Subscriber Subscriber
• Always Upgrade Publisher node first

• Switchover options depends on the collaboration product
• CUCM Publisher can be switched over before Subscriber(s) Upgrade Startup
• CUC Publisher must NOT be switched over before Subscriber Upgrade Completes
Unified Communications Manager Version 11.5
BRKUCC-2011 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
https://software.cisco.com/portal/pub/download/portal/select.html?&mdfid=286306100&flowid=79971&softwareid=282074295 19
Switchover Reboot Methods
CUCM
Upgrade Type Switchover
Reboot Options
Method
Automatically reboot and Switch to the new version after
Automatic
upgrade completes successfully.
Standard Upgrade
Do not reboot and Switch to new version after upgrade
Manual
completes successfully
Refresh Upgrade reboots at the start of Upgrade.
Automatic
Remain in the Upgraded version after upgrade completes
Refresh Upgrade successfully.
CUCM + IM&P Automatically reboot and Switch back to the previous version
Recommended Manual
after Refresh upgrade completes successfully.
* PCD always Initiates Upgrades in “Manual” mode. PCD creates a separate Manual Switchover task if the Automatic
Switchover option is selected within the Upgrade Wizard.
Reference
SU and RU Upgrade: Appliance/Virtual to
Appliance/Virtual Decision Tree
Existing CUCM CUCM VOS
cluster being Version RHEL Release
upgraded
5.1(x) & 6.X RHEL 3 Update 8
7.0(1) RHEL 4 Update 4
L2
SU
Upgrade to same YES Perform a 7.1(3) & 8.0(x) RHEL 4 Update 7
major RHEL SU Upgrade 8.5 RHEL 4 Update 8
RU
version
SU
8.6* RHEL 5 Update 5
SU
RU
NO
9.X RHEL 5 Update 7
Upgraded
RU
Perform a CUCM 10.0(1) RHEL 6 Update 2
RU Upgrade cluster
SU
* RU starts with CUCM 8.6 or RHEL 5 for CUCM.
CUCM 11.5 Deprecated Phone Models
Upgrade
to 11.5
After
Upgrade
Endpoint Refresh Tool - Migration FX

http://refreshcollab.cisco.com/webportal/66/Endpoint%20Refresh%20Tool
BRKUCC-2011 3
© 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 22
Add
device
in11.5
• Field Notice
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/11_5_1/fieldNotice/cu
cm_b_fn-deprecated-phone-models-1151.html?emailclick=CNSemail
• CUCM 11.5 Release Notes
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/11_5_1/cucm_b_relea
se-notes-cucm-imp-1151/cucm_b_release-notes-cucm-imp-1151_chapter_010.html
• Phones (14 models) will not be able to register to CUCM 11.5
• 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
BRKUCC-2011 3
© 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 24
Unified CM OS Admin Upgrade Process
• Add version 11.X of

license for the
appropriate ELM or
Existing Existing Existing New CUCM New CUCM ELM/PLM PLM
CUCM CUCM CUCM 11.X Cluster 11.X Cluster
Cluster Cluster Cluster • Or Upgrade
Standalone PLM to
Upgrade Switch Switch Add
Upgrade
License to
11.0 First
Publisher Subscribers Partition Partition
ELM/PLM
Back Up Inactive Inactive on on and add • For 9.X to 11.X,
With DRS Partition Partition Publisher Subscriber CUCM to upgrade IM&P after
PLM if CUCM cluster is
new
cluster upgraded
CUCM CUCM • This scenario applies

sFTP to virtualized CUCM
11.X 11.X CLI or CLI or
Server
ISO file ISO File OS Admin OS Admin only
1 2 3 4 5 6
COP Files for Upgrades
CUCM Image Digital Signature Validation
RSA (Rivest Shamir Adleman) Keys Version
RSA Key version of ISO or COP file(s) must match what CUCM supports COP
(sgn)
file
ISO
CUCM acceptable RSA Signed
RSA Key Version Files
CUCM Build RSA Key Versions CUCM Build Signed RSA Version
Accepted
5.0(4) – 10.0(X) RSA v2
< 8.5.1.17123-1 RSA v2
10.5(1) or higher RSA v3
< 8.6.2.24122-1 RSA v2
ciscocm.free_common_space_v1.3.k3.cop.sgn
< 9.1.2.11018-1 RSA v2
Third party COP files need RSA v3 signature
10.X RSA v2 and v3
11.X RSA v3 Only COP files / Images Signed with RSA v3 Keys can be used
with CUCM 11.X and later
CUCM and ISO/COP Files
CUCM accepts RSA v2
COP
(sgn)
CUCM accepts RSA v3
✔ CUCM 11.5 ISO RSA v3 Signed
CUCM 9.1(2) COP file adds RSA v3 file

ISO
ciscocm.version3-keys.cop CUCM 11.5
CUCM 11.5 ISO RSA v3 Signed

CUCM accepts RSA v2 CUCM accepts RSA v2 /v3
✔
✔
ISO
ISO
CUCM 9.1(2) CUCM 10.0 ISO is RSA v2 CUCM 10.0 CUCM 11.5
CUCM 10.0
ciscocm.free_common_space_v1.0.cop.sgn
COP
(sgn)
CUCM accepts RSA v3 COP file is RSA v2 Signed file
X
COP file is RSA v3 Signed COP
✔ (sgn)
file
CUCM accepts RSA v3
CUCM 11.0 ciscocm.free_common_space_v1.3.k3.cop.sgn
Verify that Third-party COP files have been signed with RSA v3 if installed onto CUCM 11.X or later:
2N, Ascom, Avara, BT, DoCoMo, Fujitsu, Intelbras, IP Blue, IP Trade, Mindshare, Mobile Heartbeat, Nokia, RIM, Sony, Speakerbus,
Spectralink, Syn-Apps, Tandberg, Telecore, Telematrix, Verizon BRKUCC-2011 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Reference
CUCM COP Files for Upgrades
Current Version Target Version
<8.5.1.17123-1 10.5(1) or higher ciscocm.version3-keys.cop.sgn
<8.6.2.24122-1 / 8.6(2)su5 * 8.6(2)su5+ and 9.1(2)su1+ has v3 Keys
<9.1.2.11018-1 / 9.1(2)su1 pre-installed
8.5(x) or lower 8.6 or higher ciscocm.refresh_upgrade_v1.5.cop.sgn
8.5(1), 8.6(2), 9.1(1), ciscocm.vmware-disk-size-reallocation-1.0.cop.sgn
9.1(2) or lower
Any CUCM with <25GB 9.1(x) or higher ciscocm.free_common_space_v1.3.k3.cop.sgn
available in Common
6.1(4), 6.1(5), 7.1(3) 8.5(x) ciscocm.allow_upgrade_to_unrestricted.cop.sgn
• Always Backup system before apply COP file
• Match RSA version of COP file to CUCM supported RSA version
• To check for COP file installed, use “show version active” in CLI or “Show > Software”
in OS Admin
CUCM Platform Conversion (PC) with Examples
Optional Upgrade
• Bare Metal or Appliance to Virtual Platform Conversion
PC
• E.g. CUCM 10.X and later can only run virtualized
MCS 7845-I3 C240M4 • E.g. MCS to UCS
Optional Upgrade
PC • Virtual to Virtual Platform Conversion

• E.g. Change from C-Series Rack Severs to B-Series
C240M4 B200M4 Blade Servers
Optional Upgrade
PC • Virtual to Virtual Platform Conversion
C240M4
• E.g. Change older C-Series Rack Severs to current
C210M1
older C-Series Rack Severs
CUCM Platform Conversion (PC) Approaches
Cisco DRS (Disaster Recovery System):

PC
1 Traditional method leveraging DRS backup and DRS restore to

change platform only
NEW
PC Cisco PCD (Prime Collaboration Deployment)
NEW
2 New method leveraging PCD to change platform and/or upgrade
Unified CM OS Admin Migration for 8.0(2) - 9.1(2)
RU
Upgrade
New New CUCM New New Virtualized

CUCM on virtualized virtualized Publisher virtualized virtualized CUCM 11.X
MCS CUCM CUCM or ELM CUCM CUCM
DRS • Upgrade ELM to PLM
Install on Restore Install on DRS before RU upgrade
First node on First Secondary Restore CUCM to 11.X
DRS or node or Upload node or Full
Backup Publisher Publisher License(s) Subscriber Cluster • License upload:
- 8.X: Node, DLU and
SW Feature with
license MAC on
CUCM CUCM Publisher
sFTP ISO sFTP ISO sFTP
Server Image Server Image Server - 9.X: License to ELM
1 2 3 4 5 6 - 10.X/11.X: License to
PLM
Replacing a Single Server or Cluster for Cisco Unified Communications Manager:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/install/11_0_1/replace/CUCM_BK_R13B8C48_00_replacing-a-single-server-cluster_1101.html 32
32 BRKUCC-2011 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 32
Upgrade Methods
Direct
DSU Standard
Upgrade (L2)
Unified CM OS Admin Upgrades
and Migrations
Direct
DRU
Refresh
Upgrade (RU)
Upgrades
Method
PCDU
PCD
Upgrade
(PCD) Upgrades and Migrations
PCD Migrate
PCDM
(M1)
CUCM Upgrades & Migrations with
3
PCD Upgrades and Migrations
U Upgrade existing clusters
Types of
Upgrades/
Migrations 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 (PCD)
MCS Migrate
Example
• PCD is a VMware vApp used for management of Cisco
collaboration applications:
- CUCM
- CUC
CUCM 6.X
- CUP / IM&P
- CUCCX
• Management tasks (Upgrade, Switch Versions, Server
Restart, Readdress, Install and Migrate) are based on
CUCM 7.X collaboration application and version of the application
PCD • VMware vApp is pre-configured virtual machine with OS

and PCD application (1.5GB)
• pcd_vApp_UCOS_11.5.3.10000-14_vmv7_v1.2.ova
CUCM 8.X
• PCD OVA containing preinstalled app ships as part of
UCM media kit
• Bootable ISO Available via PUT or TAC (NOT posted on
ESXi Host
CCO)
CUCM 9.X ⚠️ ESXi 6.0 API
Support with PCD • Update ISOs are Posted on CCO
11.5(1)SU1+
Reference
CUCM Supported Tasks by PCD 11.5(3)
Feature CUCM CUCM CUCM CUCM CUCM CUCM CUCM CUCM
6.1(5) 7.1(3), 7.1(5) 8.0(1-3) 8.5(1) 8.6(1-2) 9.x 10.X 11.X
Migration to 10.X/11.X X X X X X X X X
New
Fresh Install X X
Upgrade X X X X
Switch Version X X X X
Restart X X X X
Readdress X X
(Hostname/IP
Address Change)
PCD 11.5(3) Administration Guide:

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/pcdadmin/11_5_3/cucm_b_pcd-admin-guide-1153/cucm_b_pcd-admin-guide-1153_chapter_011.html
Reference
CUP/IM&P Supported Tasks by PCD 11.5(3)
Feature 8.5(4) 8.6(3-5) 9.x 10.x 11.X
Migration to 10.X/11.X X X X X X
New
Fresh Install X X
Upgrade + COP X X X X
Install
Switch Version X X X X
Restart X X X X
Readdress
(Hostname/IP
Address Change)

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/pcdadmin/11_5_3/cucm_b_pcd-admin-guide-1153/cucm_b_pcd-admin-guide-1153_chapter_011.html
PCD Requirements
PCD CUCM CUC CUCCX
VOS VOS VOS VOS

• Virtual machine virtual requirements
- 2 vCPU
ESXi 6 Hypervisor
- 4 GB vRAM Server Hardware
- 80 GB vDisk (Consider Increasing)

CPU Memory NIC Storage
• VMware requirements
- To run PCD On
- ESXi 4.1, 5.0, 5.1, 5.5 and 6.0
- To perform Fresh Install or Migration Tasks
New - VMware API Support for ESXi 6.0 with PCD 11.5(1)SU1+
- CUCM-BE 6K / CUCM-BE 7K (ESXi 4.1 – 5.5) shipped with Cisco UC Virtualization Hypervisor. 👎 NO PCD Support
- Update to Cisco UC Virtualization Foundation 5.5 / 6.0 or to Cisco UC Virtualization Hypervisor Plus
- New CUCM-BE 6/7K (ESXi 6.0) comes with Cisco UC Virtualization Hypervisor Plus 6.0 👍 with PCD Support
Virtualization Software Requirements

http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/virtualization-software-requirements.html#license_comparison
Reference
PCD 11.5(3) Supported Versions of ESXi
PCD Version ESXi Version of Host for UC Applications
11.5(1) 5.5
11.5(1)SU1, 11.5(2), 11.5(3) 5.5 / 6.0
PCD Version Migrate or Fresh install Task

Supported CUCM Releases
11.5(1), 11.5(1)SU1 10.5(2) / 11.0(1)
11.5(2), 11.5(3) 10.5(2) / 11.0(1) / 11.5(1)
👍 Upgrade PCD to latest version 11.5(3) First 👍

Ordering and Deploying PCD Initially
PUT OVA PCD_VAPP.OVA for vSphere Client
pcd_vApp_UCOS….OVA
PCD
PCD Version PCD Build

11.5(3) 11.5.3.10000-14 NEW
11.5(2) 11.5.2.10000-4
11.5(1)SU1 11.5.1.11900-1
10.5(3)SU1 10.5.1.11900-3
• Product Upgrade Tool (PUT) - www.cisco.com/upgrade
• PCD part of “CUCM Software Version 10.X/11.X for PUT Only”
• Download as pcd_vApp_UCOS_11.5.3.10000-14_vmv7_v1.2.ova
Downloads Home → Products → Unified Communications → Call Control → Unified Communications Manager (CallManager) → Unified
Communications Manager Version 11.5 → Prime Collaboration Deployment Updates-11.5(3)
Prime Collaboration Deployment Updates – 11.5(3)
https://software.cisco.com/portal/pub/download/portal/select.html?&mdfid=286306100&flowid=79971&softwareid=286287305 41
PCD Interactions with External Components
• PCD and VMware ESXi communication
- ESXi host root credential no longer required
- w/ PCD 11.5(2) Host and Virtual Machine
privileges are sufficient
- NFS mounts PCD /fresh_install directory PCD
- ESXi Support Limitations 5.x vs 6.0
ftp/sftp
- ESXi License Requirements
- Data center or server team coordination Virtualized
sftp CUCM 11.X
ucsinstall*.iso,*cop.sgn /upgrade
bootable*.iso /fresh_install
VMware vSphere ESXi

Host
PCD Interactions with External Components Cont.
PCD
Ssh/sftp
• PCD and CUCM communication
HTTPs
- CUCM OS admin credential Platform
SOAP
API CUCM
- Install ciscocm.ucmap_platformconfig.cop
during Discovery and certain PCD Tasks such
as Migration / Data Export If Discovery or Migration Task is
- Platform SOAP API for certain PCD Tasks such stuck its possible this COP Install
as Restart, Upgrade, Switch Version has stalled/failed.
- Requires Platform SOAP Services to be Workaround: From Platform CLI or
activated on CUCM 8.6 on all Nodes GUI “Assume control”, then cancel
the install then try again on PCD
NEW
PCD
10.5(2)
outside inside

PCD
- Static NAT support with PCD 10.5(2)+
CUCM
10.1.1.10 192.168.1.2
- PCD Behind NAT
outside inside
- CUCM Behind NAT
- PAT not enough need 1 to 1 Static NAT PCD
Source CUCM
192.168.1.2 10.1.1.10
Dest. CUCM
10.1.1.11
Set PCD’s NAT IP when it resides

behind a NAT Router (Inside)
outside inside

PCD
- Static NAT support with PCD 10.5(2)+
CUCM
10.1.1.10 192.168.1.2
- PCD Behind NAT
outside inside
- CUCM Behind NAT
- PAT not enough need 1 to 1 Static NAT PCD
Source CUCM
192.168.1.2 10.1.1.10
Dest. CUCM
10.1.1.11
PCD
• PCD and CUCM communication sftp
- Remote SFTP Support for Upgrades HTTPs

SFTP Server in DC1
Platform
or COP file Installs SOAP
sftp
API
- Multi SFTP Server Support

SFTP Server in DC2
- Fresh Installs / Migrations must use
PCD NFS Mount
PCD
• PCD and CUCM communication sftp
- SFTP Server Details must be assigned HTTPs

SFTP Server in DC1
Platform
to each CUCM Node SOAP
sftp
API
- Default is localhost = PCD Local Folder

/upgrade SFTP Server in DC2
PCD Assisted Upgrades and Migrations
PCD Upgrade (Virtual to Virtual)
From CUCM Version Target CUCM Version

U 8.6(1),8.6(2),9.0.(1),9.1(1),9.1(2),10.0(1), 10.X or 11.X
10.5(1),10.5(2),11.0(1),11.5(1)
Types of
PCD Migration (Physical to Virtual)
Upgrades/
Migrations From CUCM Version Target CUCM Version
6.1(5),7.1(3),7.1(5),8.0(1),8.0(2),8.0(3), 10.X or 11.X
M 8.5(1),8.6(1),8.6(2),9.0.(1),9.1(1),9.1(2)
Simple Migration: Same network settings (IP

addresses and/or hostnames)
Network Migration: New network settings (IP
addresses and/or hostnames)
Bare Metal to virtualized with PCD (PCDM)
Detailed step by step with screen captures are

in the appendix (25 slides)
CUCM on Virtualized
MCS PCD CUCM 11.5
• Bare metal CUCM to virtualized CUCM (P2V)

- Installs ciscocm.ucmap_platformconfig.cop & ciscocm.migrate-export-vX.Y.cop file to the
source servers to export data
- Builds a new migration cluster (Manual Task Required to first deploy OVAs)
Sample Powershell Script in
- Exports and Imports data Appendix**
• Same or different destination IP address and/or hostname

NEW
• Source or Destination Migration Cluster can be behind NAT PCD
10.5(2)
• Scheduled or immediate execution
Automated Platform Conversion with PCD
 CUCM Bootable ISO provided to ESXi Hosts via
NFS service running on PCD
5
1  Migration (M1) Steps
CUCM 6.X
4 1. Add Source CUCM Clusters to PCD
Inventory
Create
CUCM 2. Add ESXi Hosts to PCD Inventory
VMs via
CUCM 7.X OVA
PCD 2 3. Add CUCM Bootable ISOs to PCD SFTP
Server (adminsftp user / fresh_install folder)
4. Deploy Empty CUCM VM on ESXi Hosts via
OVA
CUCM 8.X 3
5. Map Physical Nodes to Virtual VMs and
Schedule Migration Tasks
ESXi
Host
PCD Considerations and Planning
• Cisco UC Virtualization Hypervisor with older Cisco BE6K and BE7K
• ESXi Support for Vmware APIs (Fresh Install, Migration Tasks)
• Lab testing with or without NAT feature
• Remember vSphere DRS (Distributed Resource Scheduler) is not Supported
• Consider network traffic to and from PCD (NFS, SFTP)
• PCD does not auto install SU/RU upgrade required COP file(s)
- ciscocm.version3-keys.cop.sgn
- ciscocm.refresh_upgrade_v1.3.cop.sgn
• Inspect PCD logs via activelog tomcat/logs/ucmap/log4j/ucmap*.log

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/pcdadmin/11_5_3/cucm_b_pcd-admin-guide-1153.html
CUCM Licensing Overview & Prime
License Manager
4
CUCM License Evolution
• Overview of CUCM Licensing
License Model License Tracking License Type
Previous
DLU, Node and
Device Based Local CUCM
Software Feature
Current
User Based ELM/PLM UCL and CUWL
Future
Smart Software
User Based UCL and CUWL
Licensing
Cisco Unified Communications 11.0 and 10.x Licensing Solution Overview

http://www.cisco.com/c/en/us/products/collateral/unified-communications/unified-communications-licensing/product_solution_overview0900aecd806cc7a4.html
Prime License Manager (PLM)
Cisco Prime License Manager (PLM)
PLM Implementation Products
PLM
Bootable Standalone PLM
Prime_LM
Co-resident with CUCM PLM + CUCM
PLM + CUCM Co-resident with CUCMBE 6K PLM + CUCMBE 6K
Bootable
CUCM PLM + CUC Co-resident with CUC PLM + CUC
10.X/11.x
• PLM is a centralized enterprise-wide license management solution for Cisco collaboration applications
- CUCM, CUCM SME and CUCMBE 6K
- Cisco Unity Connection (CUC)
- Cisco Emergency Responder (CER)
• PLM deployment can be standalone or co-resident with CUCM, CUCM-BE 6K or CUC
• CUCM/ CUC 10.5(1)SU1+, PLM can be removed from the co-resident product
OS Admin CLI command - license management system remove
Cisco Prime License Manager User Guide:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/plm/11_5_1_SU_1/userguide/cplm_b_user-guide-rel-1151SU1.html
Reference
License Manager Versions and Builds
License Manager
Version Build
Enterprise License Manager (ELM) Same as CUCM Same as CUCM
9.0 – 9.1 e.g. 9.1(2) SU3 9.1.2.13900-10
Prime License Manager (PLM) Version Build

10.X-11.X 11.5(1)SU1a NEW
11.5.1.11900-5
11.0(1) 11.0.1.10000-2
10.5(2) 10.5.2.10000-6
10.5(1) 10.5.1.10000-9
10.0(1) 10.0.1.1000-19
• ELM is built into CUCM ISO Co-resident: same Standalone: Different
build as CUCM build as CUCM
• PLM is built into CUCM ISO or installed as independent / Standalone
Deployment with its own Bootable ISO 56
Prime License Manager Support as of 11.X
First First
node of node of
CUC 1 CUC 2 CER 1
First Node of First Node of
CUCM Cluster 1 CUCM Cluster 2
CER
License License License License License
Manager Manager Manager Manager Manager
API API API API API
PLM
PLM
License file
• License Manager API in CUCM 11.X, CUC 11.X and CER 11.X interacts with PLM for
license request and approval
• License Manager API was added CUCM in version 9.0, CUC in version 9.0 and CER in
version 10.0
License Manager Product Support and Usage
Product Version ELM 9.X (Bare Metal PLM 10.X (Virtualized) PLM 11.X
or Virtualized) (Virtualized)
CUCM 9.X Yes Yes Yes
/ CUC 9.X
CUCM 10.X Yes w/ License Yes Yes
/ CUC 10.X Definition (1 or 2)
CUCM 11.X Yes w/ License Yes w/ License Yes
/ CUC 11.X Definition (2) Definition (3)
CER 10.X No Yes Yes
CER 11.0 No Yes w/ License Yes

Definition (3)
1. License Definition for 9.1 = elm_LicenseDef_9_1_v1.cop.sgn

3. License Definition for 10.0 = license-def-11-for-PLM-10x.def
• For CER 10.X/11.X, use PLM

• Use license definition file to support the higher version of the products (CUCM, CUC and CER)
• For Virtualized PLM / Virtualized CUCM with co-resident PLM, manually set MAC address since
license is tied to VM’s MAC address (Edit virtual machine settings  Machine Network adapter
 Manual) before requesting license file
ELM to PLM Upgrade
ELM 9.X ELM 9.X
PC
ELM/PLM
ELM 9.X Upgrade PLM 11.0
PLM
PLM 10.X Upgrade PLM 11.0
• Use “Replacing a Single Server for Cisco Unified Communications Manager” procedure
to change from bare metal ELM to virtualized ELM. No PCD migration support.
• Use ELM/PLM upgrade COP file (elm_Elm_v9_1_1_PlmUpgrade.cop.sgn) to allow for
ELM to PLM10.X/11.X upgrade
• Use pre-upgrade RSA keys COP file (ciscocm.version3-keys.cop.sgn) to upgrade to
PLM 10.5 and later for 9.X
• Re-host license by using Product License Registration (www.cisco.com/go/license)
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/install/11_0_1/replace/CUCM_BK_R13B8C48_00_replacing-a-single-server-cluster_1101.html
CUCM and PLM Interaction
• PLM polls all registered CUCM clusters
• CUCM cluster evaluates license usage and sends
license usage back to PLM
CUCM PLM
• Evaluate phone, • Poll all products
• PLM evaluate all CUCM cluster responses to see
users and every 24 hours if there is adequate licenses for the requested
features usage • Evaluate types
• Send license adequate
usage to PLM licenses • PLM performs license substitution if does not have
• Receive license • Perform license adequate license of the requested type
response and substitution
operate in the • Provide Valid or • PLM response back to with either valid or invalid
appropriate Invalid license (not enough licenses) to all CUCM clusters
mode response
• CUCM receives the response from PLM and
function accordingly
Detailed CUCM and ELM/PLM interactions with

signaling are in the appendix
PLM License Substitution
• Licenses are based on hierarchical model where lower feature
license can be covered by a higher feature license
CUWL Standard
- I.E. UCL Basic can be covered by UCL Enhance
UCL Enhanced +
- I.E. UCL Enhance can be covered by UCL Enhance Plus
UCL Enhanced
• PLM evaluates ALL system license requirements on a per product
UCL Basic (CUCM, CUC and CER) basis and respond back with one
consistent response to ALL registered systems
UCL - Essential
- VALID: adequate license
User License
Substitution
- INVALID: inadequate license
• Centralize and enterprise-wide licensing view per product set
Grace Period and License Overage
Grace Behavior when license is exceeded
Period
License
Manager
API
CUCM 9.X-11.0 60 License Overage:
• System function normally
• Existing phones cannot be de-provisioned
• Additional phones cannot be provisioned
CER
CUC 9.X-10.5 60 Expire:
License
License
Manager
Manager
API
• System will not take calls
API • Users cannot retrieve messages
• Additional users or mailboxes cannot be provisioned
CUC 11.0 60 Expire:
• System will take calls
• Send or receive voicemails
• Additional voicemail boxes can not be provisioned
CER 10.X-11.0 60 License Overage:

• Responder system stops tracking and updating the phone
Location
CUCM License Usage
CUCM License Usage
• Extension mobility users: No license
1 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.
User • Device with Owner User ID association: UCL or CUWL
3 / 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
• TelePresence (TP) device
4 TelePresence • E.g. CTS, MX, SX, TX, etc.
List of devices and associated license are in the appendix
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
• Previous Methods:
- BAT, Run SQL via CLI, UDS and AXL
- Links in the Appendix
Recommend to perform this task before upgrading to
CUCM 9.X or later
Cisco Device Assignment Tool
(DAT)
Cisco Device Assignment Tool (DAT)
• Pre-upgrade or post-upgrade of CUCM 9.0
Device Assignment Tool 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 (OwnerUserID) to Based Licensing (CUCM 9.0 and later
3 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&flowid=77897&softwareid=282204704&release=COP-Files&relind=AVAILABLE&rellifecycle=&reltype=latest
Reference
• Based on sequence of 7 rules or manually
DAT edited xls file
(UdatApplication.jar)
License Migration from Device
Based License to User Based
License (9.X or later)
License Count Utility (UCT) for CUCM 6.X-8.X
CUCM 6.X
PLM
1. Number of public space
2. Pre-upgrade license report or
LCU-License-
Report.zip
licensing@cisco.com licensing case number
3. UCSS/ESW contract or SO
Pre-Upgrade number
CUCM 7.X
License License Report
Count
Utility
CUCM 8.X
• Perform AXL calls to existing CUCM (6.X, 7.X and 8.X) clusters for current license and license
usage and generate pre-upgrade license report
• Report can be send to licensing@cisco.com
• Include number of public space, license case number / MAC address and UCSS/ESW or SO
number, if send directly to licensing@cisco.com
License Count Utility 9.1.2 (LCUZIP-Ver9.1.2.zip):

https://software.cisco.com/download/release.html?mdfid=285963825&flowid=&softwareid=282204704&release=LCU&relind=AVAILABLE&rellifecycle=&reltype=latest
Opening Licensing Case
Web
• https://tools.cisco.com/ServiceRequestTool/scm/mgmt/case
• Type of problem = Licensing
Email
• licensing@cisco.com
Phone
• 1-800-553-2447
• Option 3, License Support
CUCM 11.5 Upgrade Paths
5
Appliance (MCS) to Virtualized CUCM 11.5
CUCM 6.1(5)
CUCM 7.1(3/5)
CUCM 11.5
CUCM 8.X PCD Migration
CUCM 9.X
CUCM 8.6
CUCM 11.5
CUCM 9.X Unified CM OS Admin
Migrate (DRS Backup)
• PCD Migration Method is recommended

• Unified CM OS Admin upgrade will work for some situations
• Access to media
• Server supporting CUCM 8.X or 9.X
Virtualized CUCM to Virtualized CUCM 11.5
CUCM 8.6
CUCM 9.X
CUCM 11.5
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
9.X RU ciscocm.version3-keys.cop.sgn
10.X SU
11.X SU
Reference
CUCM Upgrade Type and Upgrade Method
CUCM on MCS (Physical)
CUCM Version Upgrade Type Upgrade Method
6.1(5) NA PCD Migration
7.1(3/5) NA PCD Migration
8.X NA PCD Migration
8.6 RU PCD or Unified CM OS Admin Migration
9.X RU PCD or Unified CM OS Admin Migration
CUCM Virtualized
CUCM Version Upgrade Type Upgrade Method
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
CUCM Scale Improvement with 11.5
CUCM Scale Improvement with 10K OVA
CUCM Version Endpoints Endpoints per Endpoints per
per Server Standard Cluster Megacluster Cluster*
11.0(1) and ~10K ~40K ~80K

earlier
11.5(1) ~10K-18K * ~40K ~80K
• 10K CUCM OVA
CUCM 11.5
• CUCM Megacluster approval required (CST) * Call
• Server > 10K endpoints Processing 1 2 3 4
• Cluster > 40K endpoints Servers Pair
• Cluster > 8 call processing serversMax ~18K ~17K ~15K ~14K
Endpoints
• CUCM Megacluster Submission Requirements per Server
• Cisco account team, AS or partners Max ~18K ~34K ~46K ~56K
• CST http://tools.cisco.com/cucst Endpoints
• vse-megacluster@cisco.com per Cluster
CUCM Scale Improvement Use Cases
CUCM < 11.5 CUCM 11.5 CUCM 11.5
Upgrade Servers Consolidation
CUCM (MCS) CUCM 11.5 CUCM 11.5

Upgrade Servers Consolidation
• Servers (Subscribers) consolidation in a cluster

• Use cases
• Virtualized to Virtualized (CUCM version 11.5 upgrade) with potential OVA change
• MCS to UCS platform (Virtualized )conversion (MCS supports 7.5K endpoints per server)
• Deleting CUCM server in a cluster requires Cluster Reboot
Deleting a Server
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/7_1_2/ccmcfg/bccm-712-cm/b02servr.html#wp1024783
OVA Updates for Virtual to Virtual
CUCM Upgrades
Reference
Cisco Virtual Template (OVA) File
OVA
2
CCO
1
vSphere
Client
UCS B200 M4
• 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 generally provide OVA files with Virtual Machine Hardware Version
(VMV) 7 and VMV8 on CCO for collaboration applications deployment
• CUCM 11.5 which is supported with ESXi 5.0U1 + with VMV8
• CUCM 11.5 Not supported with ESXi 4.0 with VMV7
• Deploy the latest OVA version and the highest available VMV version that
matches to ESXi version
ESXi and CUCM VM Hardware Version
ESXi Version VMware Virtual Recommended Cisco CUCM 11.5 Collaboration Collaboration VMV Version Cisco
Machine Hardware OVA VMV Version Support Application Application Version OVA Version
Version (VMV)
cucm_11.5_vmv8_v1.0.ova
✖
4.0 7 7
4.1 7 7
CUCM 11.5 8 1.0
5.0 8 8
✔
5.1 9 8
5.5 10 8
6.0 11 8
• Use matching collaboration application OVA file to correct corresponding

ISO file
– E.g. cucm_11.5_vmv8_v1.0.ova  Bootable_UCSInstall_UCOS_11.5.1.10000-6.sgn.iso
• VMV can be upgraded to a Cisco supported version 7  8, but cannot be

downgraded
Virtual Machine Compatibility
http://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.vm_admin.doc%2FGUID-64D4B1C9-CD5D-4C68-8B50-585F6A87EBA0.htm l 82
CUCM 8/9 to CUCM 10/11 OVA Changes
Features CUCM 8.X / 9.X CUCM 10.X/11.X
RHEL Guest OS 5 (32bit) 6 (64 bit)
Adapter Type Flexible VMXNet3
NOT Compatible w/
RHEL 6 64-Bit
• Changes CAN be done Prior to upgrading to CUCM 10+ NEW
• CUCM must be Powered OFF

• Change the Guest OS from RHEL 5 (32 bit) to RHEL 6 (64 bit)
• “Check and upgrade Tools during power cycling” under Options  Vmware Tools
• Update Virtual Machine Hardware Version to 8 NEW
• Change Network adapter type from Flexible to VMXNET3

– Automatic MAC: Edit VMX file in the VM machine directory. Instruction in OVA Readme Files
– VMware vSphere PowerCLI for both automatic and manual MAC. Instruction in link below
– Sample Powershell Script in Appendix**
CUCM 11.5 OVA Readme:
http://www.cisco.com/web/software/283088407/133457/cucm-11.5.ova.readme.txt 83
CUCM 11.5 OVA vRAM / Memory Change
Product Scale vCPU vRAM vDisk Product Scale vCPU vRAM vDisk
(users) (GB) (GB) (users) (GB) (GB)
10,000 4 6 1 x 110 10,000 4 8 1 x 110

CUCM 7,500 2 6 1 x 110 CUCM 7,500 2 8 1 x 110
10.X 2,500 1 4 1 x 80 11.X 2,500 1 6 1 x 80
1,000 2 4 1 x 80 1,000 2 6 1 x 80
• Shutdown CUCM
• Increase vRAM Resources +2GB prior to upgrading to CUCM 11.X+
CUCM 11.5 OVA Readme:

http://www.cisco.com/web/software/283088407/133457/cucm-11.5.ova.readme.txt
CUCM 11.5 OVA Disk & CPU Changes
OVA Deployed OVA being Differences Method
Converted
2.5K (80GB) 10K 1vCPU, 2GB vRAM & Replacing A Single Server
110GB vDisk
7.5K (80GB) 10K 2vCPU, 2GB vRAM & Replacing A Single Server
110GB vDisk
7.5K (110GB) 10K 2vCPU, 2GB vRAM Resize Virtual Machine
• Replacing A Single Server (2.5K OVA or 7.5K OVA with 80GB vDisk)
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/install/11_5_1/replace/cucm_b_
replacing-single-server-or-cluster-1151.html
• Resize Virtual Machine (7.5K OVA)
http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements#Resize_Virt
ual_Machine
Adding vCPU is supported for all apps except Unity and Unity Connection, but requires VM
to be shutdown first
VMware Tools 10 and CUCM 10.X / 11.0(1)
VMware CUCM utils os secure

☠️
Tools 10.X 10.0/10.5/11.0 enforcing
!!Poof!!
🤦 🤦 ♂🤦
Refer to VMware tool version-mapping info for specific builds of ESXi 5.5 and 6.0
https://packages.vmware.com/tools/versions
Vmware
Tools 10.0.6
VMware Tools 10 and CUCM 10.X / 11.0(1)
• After Upgrading to ESXi 5.5u3b or 6.0u1b with CUCM 10.X and 11.0(1), tools
might be in “Not Running (Not Installed)” state
– Apply VMwareTools COP File or Upgrade CUCM
prior to attempting Interactive Vmtools Upgrade Method to recover
– Refer to http://docwiki.cisco.com/wiki/VMware_Tools
• !! DO NOT attempt the usual workaround to get Vmware Tools updated !!

– Put SELinux to Permissive Mode, Update VMware tools via Interactive Method, Put SELinux back to Enforcing Mode
• You may disable the “Check and upgrade VMware Tools (before each power on / during power
cycling)” until you can apply the VMwareTools COP file or upgrade to a CUCM version that has
this issue addressed.
Current CUCM version Recommendation before VMware Tools 10 Update

10.0(X)
Install COP file or Upgrade to 10.5(2)SU3a or 11.5(1)
10.5(2) – 10.5(2)SU3
11.0(1) – 11.0(1a)SU1 Install COP file or Upgrade to 11.0(1a)SU2 or 11.5(1)
ciscocm.VMwareTools2016c.cop.sgn COP File

https://software.cisco.com/download/release.html?mdfid=285963825&softwareid=282204704&release=COP-Files&relind=AVAILABLE&rellifecycle=&reltype=latest 87
Reference
Bulk Update VMware Tools Upgrade Settings
Using vSphere Web Client
If you have VMware Update
Manager Installed
Right Click on a Folder
Reference
Bulk Update VMware Tools Upgrade Settings
Using vSphere Client Interface
Unified Communications in a
Virtualized Environment
Virtualization DocWiki Changes
• New site for virtualization docwiki in the works

• Old bookmarks may not work
• Some obsolete content will be removed
• Use http://www.cisco.com/go/virtualized-collaboration as permanent link
• Will Redirect to
http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/cisco-
collaboration-virtualization.html
Appliance to Virtualized CUCM
Appliance to Virtualization Conversion
PCD UC App UC App UC App UC App
3 Migration
VOS VOS VOS VOS
ESXi 4/5/6 Hypervisor
1 Server Hardware
CPU Memory NIC Storage
1. Server platform selection

2. VMware ESXi requirements
3. Conversion of appliance to virtual machine or OVA
4. Leverage “Cisco Collaboration Virtualization” formerly Docwiki
Cisco Collaboration Virtualization

http://www.cisco.com/go/uc-virtualized
1. Server Platform Selection
Business Edition appliances Tested Reference Specs-Based- Specs-Based-3rd-
(Packaged Collaboration Solutions) Configurations (TRCs) UCS party
BE6000M BE7000M “UC on UCS” “UC on UCS” with 3rd-Party with
BE6000H BE7000H with fixed-configuration “min specs” “min specs”
<1000 users Most deals 500+ users
etc. etc.
Turnkey IT More Simpler, but Prescriptive
More Traditional IT
Flexible, but more Complex
“Do it for me…” “Tell me what to do…” “I know what I’m doing…”
Preferred
Prescriptive Solution Approach Simplification Alignment with existing infrastructure.
Strategy?
Preferred
Align with Collaboration 80% use cases. Align with Data Center use cases.
Pre-sales?
“Magic box” appliance.

Preferred Applications on generic shared HW.
Post-sales?
2. VMware ESXi Requirements
• ESXi Hypervisor: 4.0, 4.1, 5.0, 5.1, 5.5 and 6.0

VMware vCenter
Server
• ESXi Edition: VMware vSphere Hypervisor, Cisco UC
Virtualization Hypervisor, VMware vSphere Hypervisor
Foundation, Cisco UC Virtualization Foundation, Standard,
Enterprise or Enterprise Plus
ESXi Hypervisor • VMware vCenter: Essential, Foundation or Standard
• Recommended for large deployment. Centralize management, license
management, etc.
• Mandatory for Specs-Based deployment
• PCD Fresh Install & Migration Task Considerations
• VMware acquisition: Cisco, Partner or VMware
• https://www.vmware.com/files/pdf/vsphere_pricing.pdf
Virtualization Software Requirements

http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/virtualization-software-requirements.html
3. Conversion of Appliance to Virtual Machine or OVA
OVA
MCS
Server
Maximum
Number
OVA
Deployment
vCPU
• Smaller MCS server converts to a
Model of Phone Size standard 2500 device OVA or restricted
7845-I3 or 10000 10000 4 performance 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-I2/H2 7500 7500 2
or earlier
• Storage option for redundancy: FC SAN
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
earlier Restricted performance CPU (CUCMBE 6K)
Reference
Appliance vs 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.
System Level Planning and
Considerations
6
System Level Planning and Considerations
Entitlement Upgrade System Improve

Virtualization Execution
Methods Preparation Performance
Install PAKs < 8.6 - Virtualized CUCM - DSU - Deprecated - TFTP server - Phone firmware
- VMware changes - DRU phones performance - Application
- Software (PUT) - PCDU - Change freeze: - DB replication dependencies
- Product license - PCDM - MACD increase timeout & - Upgrade windows
registration (PAK) - EM < 9.X process count
- AXL, PCP - DB replication
- CUCM License: - LDAP Sync cleanup RIS / ATS
- LCT < 8.6 - RTMT alert Logs
- DAT - VM changes - Purge CDR
- License Manager - DB Replication (2)
(ELM/PLM) - DRS back up
- Licensing case - Baseline system
- Disk Space
- COP file(s)
Example: Minimize Upgrade Window
1Phase I:
2
Phase II:
3
Phase III:
4
Phase 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
Upgrade
applications and firmware compatibility
Check List to Improve Upgrade
Performance
Disk Space for Upgrade
25GB or more free disk space required

• Use ciscocm.free_common_space_v1.3.k3.cop.sgn
• CUCM 10.X or above, consider increasing VM disk size
• Reduce logs with RTMT:
• LogPartitionLowWaterMarkExceeded 30% (default 80%)
• LogPartitionHighWaterMarkExceeded 40% (default 85%)
• Delete old ATS & RIS Database Aborted Transaction
logs from Active & Inactive Locations
Refresh Upgrade Stuck Here
file delete activelog cm/log/informix/ats/* noconfirm
file delete inactivelog cm/log/informix/ats/* noconfirm
• If you can’t delete due to CSCux10858 contact TAC

© 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
CUCM + IM&P Upgrades
Start the IM&P Upgrade after the CUCM Upgrades are completed
• IM&P Publisher  CUCM Publisher Hostname (CSCva98249)
• Hostname Match is Case Sensitive when Upgrading to 10.5+
• Check for mismatch. Uppercase vs Lowercase (cucmpublisher vs CUCMPublisher)
CUCM Publisher IM&P Publisher
admin:show myself
Refresh Upgrade Stuck Here
Machine Name : cucmpublisher
Improve Upgrade Performance
• Check Raid Controller Battery Backup Unit Status

• Make sure Virtual Disk Is in “Write Back” Cache mode NOT in “Writethrough”
• ✔ Good BBU = Write Back Cache Mode
• ✖ Bad BBU = Write Through Mode
C2XX / BE6K /BE7K

M1/M2 Platforms w/ iBBU
Improve Upgrade Performance C2XX / BE6K /BE7K
M3/M4 Platforms w/
SuperCap
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
• Purge CAR Database
• CUCM Serviceability  Tools  CDR Analysis and Reporting  System  Database 
Manual Purge
Improve Database Replication Setup Performance
Set the following on the CUCM Publisher Node prior to initiating the Upgrade
• 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
• MACD Freeze & Minimize Database Updates by Admins or from Users

• Wait for CUCM Database Replication Setup before starting CUP/IM&P Refresh Upgrade
• Post Upgrade Consider Stopping Services until Database Replication Setup is complete
• AXL, BAT
• Extension Mobility
• Directory Sync
• UDS
Questions ?
Cisco Spark
Ask Questions, Get Answers, Continue the Experience
Use Cisco Spark to communicate with the Speaker and fellow

participants after the session
Download the Cisco Spark app from iTunes or Google Play

1. Go to the Cisco events Mobile app
2. Find this session
3. Click the Spark button under Speakers in the session description
4. Enter the room, room name = BRKUCC-2011
5. Join the conversation!
The Spark Room will be open for 2 weeks after Cisco Live
Complete Your Online Session Evaluation
• Please complete your Online
Session Evaluations after each
session
• Complete 4 Session Evaluations &
the Overall Conference Evaluation
(available from Thursday) to receive
your Cisco Live T-shirt
• All surveys can be completed via
the Cisco Live Mobile App or the
Don’t forget: Cisco Live sessions will be available
Communication Stations for viewing on-demand after the event at
CiscoLive.com/Online
Continue Your Education
• Demos in the Cisco campus
• Visit the Hub (2.2) for:
- Technical Solutions Clinic
• Lunch & Learn topics
• Meet the Engineer 1:1 meetings
• Related sessions
• Join the session’s spark room 👍
Thank You
Reference Links
Migration Recommendations
• Develop a comprehensive plan for the migration
• Partners can use PDI Helpdesk for migration plan review
• http://www.cisco.com/web/partners/tools/pdihd.html
• Break the upgrade into phases to minimize downtime
• Open a Global Licensing Operations (GLO) case with specific tags for fast
results
• https://communities.cisco.com/community/partner/collaboration/migration/blog/2013/0
5/30/how-to-get-the-efficient-support-for-drive-to-9
• Open a proactive TAC case for the upgrade
• http://cisco.com/tac/caseopen
• Check Unified Communications Virtualization docwiki often due to frequent
changes
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
Appendix
• W1 Upgrade
• Bridge Upgrade
• Jump Upgrade
• License Acquisition
• L2 and RU Upgrade in Detail
• Detailed ELM/PLM License
• User Count Tool
• License Conversion
• Phone and License Usage
Appendix
• ELM 9.1
• PLM 10.X
• Previous Methods for Owner User ID
• License Management Models with PLM
• Refresh Upgrade (RU) for MCS 7825 and
MCS 7828
• L2 and RU Upgrades for CUCM 9.X and
CUCM 10.X
• RU Upgrades for CUCM 11.X
Appendix
• RU COP File
• RSA COP File
• Detailed PCD Migration Steps
• CUCM-BE5K Migration
• RSA 3 signed cop file and CUCM 10.0
RSA 2/3
• Sample PowerShell Scripts
• CUCM License
Reference
Solution Names and Versions
CUCM / Unified CM /
License Manager
CallManager / UC Manager
Enterprise License Manager

Cisco CallManager
(ELM)
3.0-3.3
9.0 – 9.1
Prime License Manager

Cisco Unified CallManager
(PLM)
4.0-4.2
10.0-11.X
Cisco Unified
Communications Manager
(CUCM)
4.3-11.X
W1 Upgrade: Windows to Appliance Model
Existing Existing Existing New CUCM New CUCM New CUCM

CUCM 4.X CUCM 4.X CUCM 4.X 7.1 Cluster 7.1 Cluster 7.1 Cluster
Cluster Cluster Cluster
 CUCM 7.1
software
Back Up Install Install, Install Upload
Upload availability can
With and Run Run, and
Upgrade Download
CUCM DMA Licenses be an issue
BARS 7.1 File
Utility on All DMA from since CUCM
Servers Publisher
7.1 has EOS
Latest (End of Sales)
Upgrade Data Migration
Utility From Assistant
CCO (DMA) 7.1
Tape or Save DMA File CUCM Tape, FTP Node, DLU and
Network Download to Tape or 7.X or sFTP 7.1 Feature SW
Share From CCO Network Share DVD Kit Server License
1 2 3 4 5 6
CUCM Migration Definition
Bridge
Bridge Upgrade: Appliance to Appliance model
• Upgrade is allowed with Cisco CallManager service “Not Running”
• Long downtime due non-functional system and a platform change
• (e.g. Older servers that cannot newer version of CUCM)
Jump Jump Upgrade: Appliance to Virtualized model
• Virtualized CUCM with 6.1(4), 6.1(5), 7.1(3) and 7.1(5) for lab upgrade
• Minimal downtime due to lab upgrade
• (e.g. Older servers that cannot upgrade to 8.0(3) or later to virtualized)
Bridge Upgrade
Upgrade DRS DRS
DRS
File
Servers supported to run Servers supported to Virtualized CUCM
CUCM version X be in Bridge mode on Secure FTP
CUCM version Y Server
• Server platform change for discontinued servers that cannot run latest CUCM version
- Allows for a successful upgrade with Cisco CallManager service in in “Not Running” state
- Platform change is done with DRS backup and restore
- Use case include appliance to appliance and appliance to virtualized
• Requires rehost of license file due to MAC or License
MAC change caused by server change
• For a virtualized environment, use Answer File Generator to proactively obtain
license file
Bridge Upgrade
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/cucos/8_0_2/cucos/osg_802_cm/iptpch7.html#wp1058411
Jump Upgrade
Servers that cannot run Virtualized CUCM

CUCM 8.0(2) or later to Jump Upgrade Process 9.1(2)
virtualized
• Upgrade process of multiple steps:

- Upgrade from CUCM 6.1(4), 6.1(5), 7.1(3) or 7.1(5) ONLY
- Upgrade to CUCM 9.1(2) ONLY
- Lab migration ONLY
• Allows bare metal CUCM at version 6.1(4), 6.1(5), 7.1(3) or 7.1(5) migrating to
virtualized CUCM at version 9.1(2)
- Minimal down time
- Database lockdown time (i.e. No MACD)
- No license required for interim upgrades
Jump Upgrade Process
Disk
LAB Alignment
To
Production
New New Upgraded Upgraded New New
CUCM 6.X virtualized virtualized virtualized virtualized virtualized virtualized
or 7.X on CUCM 6.X CUCM 6.X CUCM CUCM CUCM CUCM
MCS or 7.X or 7.X 9.1(2) 9.1(2) 9.1(2) 9.1(2)
Build
same Upgrade Build new
DRS CUCM DRS to CUCM DRS CUCM DRS
Backup version Restore 9.1(2) Backup 9.1(2) Restore
CUCM CUCM CUCM

sFTP 6.x or sFTP 9.1(2) sFTP 9.1(2) sFTP
Server 7.X ISO Server ISO Server ISO Server
Image Image Image
1 2 3 4 5 6 7
License Acquisition with CUCM 5.X to 8.X
UPGRADE
Contract Number Product Upgrade SW Feature Upgraded
Tool Site License CUCM cluster
NEW
Product Product License Node Device New CUCM

Activation Key Registration Site License License Unit cluster
 Product Upgrade Tool site = http://tools.cisco.com/gct/Upgrade/jsp/index.jsp

 Product License Registration site = https://tools.cisco.com/SWIFT/LicensingUI/Home
 License files are uploaded and managed on the first node or Publisher of the cluster
 License files are locked to the MAC address of the first node or Publisher of the cluster
 License enforcement is perform on CUCM BRKUCC-2011 © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 127
L2 Upgrade: Appliance to Appliance Model
Active Partition Running InActive partition Dormant
InActive partition 1.RPMs Active Partition
installation Reboot
1. Firmware and
2.CUCM BIOS upgrade
installation 2.Post reboot
3.DB software
installation installation
4.Data
Migration
 Active partition is running while upgrade software is being install on inactive

partition
 Low downtime since upgrade can be done while system is functioning
Refresh Upgrade (RU): Appliance to Appliance
Model
Active Partition Running InActive partition Dormant
InActive partition 1. Data Active Partition 1. Firmware
exported Reboot Reboot
and BIOS
(CUCM and upgrade
CAR) into 2.VOS
/common installation
partition 3. Platform
import
InActive partition Dormant
Active Partition
1. CUCM
installation  Server is down while upgrade software is being install
2. DB
installation  More reboots
3. CUCM data
import  Higher downtime since upgrade cannot be done while
4.CAR DB
creation system is functioning
5.CAR DB
migration  Upgrade is equal to complete installation of CUCM
Cisco Unified Enterprise License Manager
Add CUCM or How and what do CUC, CUCM and ELM
CUC systems Register
communicate?
1 2 Success/Fail
ELM
Get License Usage – 24 hours 5 5

3 First node of
Usage X,Y,Z CUC CUCM
Analyze CUC Enforcement CUCM Enforcement

Set License Status
4
Get License Capability
6 Grant
 ELM can be stand alone or bundle with CUCM or CUC. Interaction is a logical flow
 CUCM and CUC sends license usage to ELM
 ELM handles the license grant or revoke based licensing logic
 CUCM and CUC perform license enforcement based ELM response
 CUCM and CUC enforcement rules are different
Process of CUCM and ELM Communications
1 2 3
CUCM License Evaluation ELM License Evaluation
4
[VALID or INVALID ] How does CUC, CUCM and ELM know
what to communicate?
 1. CUCM evaluates users to phones usage and feature usage to derives at

UCL/CUWL usage
 2. CUCM sends UCL/CUWL usage to ELM
 3. ELM evaluates license request, perform evaluation and license substitution before
sending a respond to CUCM (VALID or INVALID)
 Next slides will go over the HOW CUCM and ELM know how to evaluates license
usage in details
Using User Count Tool as Planning Tool to Migrate
1
2
 1. Cluster > Add: Add system in User Count Tool (UCT) using IP/hostname of system and
AXL credential
 2. Cluster: Ensure that system connected successfully
 Check versions of CUCM that the tool detects
License Conversion
CUWL
UCL 2-17
0-6 DLU
DLU
How can I
A La migrate  For CUCM, CUC included with CUWL or standalone CUC
1
Carte
these
DLU
license? Manual  Work with Global License Operation (GLO) licensing@cisco.com
 Manually provide data of current system to get new license file
from GLO
 Documentation of process at:
Pool of
DLUs https://communities.cisco.com/docs/DOC-33804
How many
of what
 Standalone CUC
2
type of
licenses
do I have?
Automated  Upgrade CUC to 9.X
 Self service license request using Product License
Registration
 Documentation of process at:
http://www.cisco.com/en/US/products/ps6509/products_tec
h_note09186a0080bf5921.shtml
 Available on CCO
 Perform AXL calls to existing CUCM clusters for licensing
information, recommends CUCM 9.X license usage, provides
CUCM 6.X
option for unused DLU to CUCM 9.X license and generate
report.
Detailed screen capture of UCT are in
the appendix
CUCM 7.X License

Count Tool
CUCM 8.X
1. Data for Manual License Migration
 Working with Global Licensing Operation (GLO) at licensing@cisco.com
 Provide current system usage
 Migrated system(s): ELM Usage Report
 CUCM 6.X to 8.X: License Report with License Count Utility (UCT)
 CUCM 3.X to 5.X: Print screen of system usage
 Provide
 Active ESW/UCSS contract number
 Site information
 Contact information for email and support contract
 MAC Address/License MAC from current CUCM system
 ELM generated license request
 Email to send licenses or software with contact information
 Intended CUCM 9.X user count and features for unused DLU
2. Automated License Migration with ELM
Contract Number Product Upgrade CUCM 9.X Upgrade

Tool site software CUCM cluster
 Log into Product Upgrade Tool site = http://tools.cisco.com/gct/Upgrade/jsp/index.jsp to order

upgrade kit
 Obtain upgrade software. There is an electronic version for download
 Upgrade CUCM cluster to 9.X and run licenses in Overage mode for 60 days before license is
required for ELM
2. Automated License Migration with ELM
CUCM License
Request
1 Text from ELM 3 Product License ELM

New upgraded ELM License Request Registration site License file
CUC 9.X
2
 1. In ELM, add the new upgraded CUC 9.X and get upgrade license request
 2. In ELM Upgrade wizard: License Management > Add or Upgrade Licenses > Upgrade Licenses
 Go through license planning for UCL and CUWL request based on DLU
 Capture license request text
 3. Go to:
 Product License Registration site = https://tools.cisco.com/SWIFT/LicensingUI/Home
 Go to Migration License section and select Register for Upgrade/Migrate License
Overview of CUCM 9.1 Installation MCS-781X
MCS7825
CUCM MCS7828
9.X DVD KIT MCS7835
MCS7845
INSTALLATION PROCESS (PROCEED)

1 2
Apply SR, ES or SU
Basic Install
Upgrade During New Installation, New
Installation Server—Flash Cut or
i.e., 9.1(1a) to 9.1(2) New Server—Migration
Installation Logs
• To capture installation logs failure, a USB key is required
for physical servers
 Plug USB key into the physical server
 Accept dumping of logs
• In a virtualized environment, dump logs is via serial port of

VM
 Add serial port when VM is off before CUCM 8.X installation
 On failure, edit guest OS to connect to a temporary file to virtual
serial port
 Accept dumping of logs
 Download 7zip from http://www.7-zip.org/download.html to unzip the
tar file
 Remove serial port after a successful installation of Unified
CM 8.X
CUCM 9.X Phone License
License Phone Type (2) # of Devices (3) Features (1)
Essential UCL Analog, 3905, 6901, VGC Phone, ATA186, ATA187 1 EM

Basic UCL 6911, 6921, CUC-RTX, Analog, 3905, 6901, VGC 1 EM, SNR
Phone, ATA186, ATA187
Enhance UCL 12S, 12SP, 12SP+, 30SP+, 30VIP, 3911, 3951, 6941, 1 EM, SNR
6945, 6961, 7902, 7905, 7906, 7910, 7911, 7912, 7920,
7921, 7925, 7926, 7931, 7935, 7936, 7937, 7940, 7941,
7941G-GE, 7942, 7945, 7960, 7961, 7961G-GE, 7962,
7965, 7970, 7971, 7975, 7985, 8941, 8945, 8961, 9951,
9971, Cius, E20, ISDN BRI Phone, Third-party SIP
Device, CIPC, CUPC, CIM, CSF, EX60, EX90, Jabber
(Android/iPhone/iPpad), CUMC, IIM, Nokia S60, H.323
Client, VXC 6215, 6911, 6921, CUC-RTX, Analog, 3905,
6901, VGC Phone, ATA186, ATA187
, Analog, 3905, 6901, VGC Phone, ATA186, ATA187
Enhance UCL Plus Same as Enhance UCL 2 EM, SNR
CUCM 9.X Phone License
License Phone Type (2) # of Devices (3) Features (1)
CUWL Standard 12S, 12SP, 12SP+, 30SP+, 30VIP, 3911, 3951, 6941, 10 EM, SNR
6945, 6961, 7902, 7905, 7906, 7910, 7911, 7912, 7920,
7921, 7925, 7926, 7931, 7935, 7936, 7937, 7940, 7941,
7941G-GE, 7942, 7945, 7960, 7961, 7961G-GE, 7962,
7965, 7970, 7971, 7975, 7985, 8941, 8945, 8961, 9951,
9971, Cius, E20, ISDN BRI Phone, Third-party SIP
Device, CIPC, CUPC, CIM, CSF, EX60, EX90, Jabber
(Android/iPhone/iPpad), CUMC, IIM, Nokia S60, H.323
Client, VXC 6215, 6911, 6921, CUC-RTX, Analog, 3905,
6901, VGC Phone, ATA186, ATA187
, Analog, 3905, 6901, VGC Phone, ATA186, ATA187
TelePresence TelePresence 1
CUCM 10.0 Licensing Summary Cont.
UCL Enhanced / Enhanced Plus
CUWL Standard TelePresence
CUWL Professional Room
69xx 89xx
UCL Basic
Jabber Desktop
TX / CTS / T Series
78xx
UCL Essential
99xx
6911
79xx
MX / Profile Series
Fax Analog DX650
Jabber Mobile
6921
792x
System Codecs and

Quickset Platforms
Third Party
3905 6901 7821
EX60 / EX90 SIP
7937 / 8831
Enterprise License Manager (ELM)
ELM Implementation Products
ELM
Standalone ELM
ELM + CUCM
Co-resident with CUCM ELM + CUCM
Bootable ELM + CUC Co-resident with CUC ELM + CUC

CUCM 9.X
• ELM is a centralized enterprise-wide license management solution for Cisco

collaboration applications
- CUCM
• ELM deployment can be standalone or co-resident with CUCM or CUC with the same
ISO file
• License file is uploaded onto ELM instead of CUCM or CUC and is based on ELM MAC
address and host ID
• License file is cumulative and is based on products (CUCM or CUC)
Enterprise Manager User Guide:

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/elmuserguide/9_1_2/CUCM_BK_E92F409A_00_elm-user-guide-912/CUCM_BK_E92F409A_00_elm-user-guide-912_chapter_011.html
License Manager Architecture 9.X and 10.X
First First
node of node of
CUC 1 CUC 2 CER 1
CER
API API API API API
ELM / PLM
ELM / PLM
License file
• License Manager API added to CUCM 9.X/10.X and CUC 9.X/10.X to interact with ELM /
PLM for license request and approval
• License Manager API added to CER 10.X to interact with PLM for license request and
approval
• Electronic fulfillment supports License Feature and Version Upgrades in PLM 10.X
Previous Methods for Owner User ID
• BAT: http://www.cisco.com/c/en/us/support/docs/voice-unified-
communications/bulk-administration-tool/110967-bat-00.html
• CLI SQL on logged in users:
https://crystalclearinsanity.wordpress.com/2014/03/07/cucm-set-device-owner-
id-to-em-logged-in-user-id-via-sql/
• CLI SQL: http://pandaeatsbamboo.blogspot.com/2014/01/associate-existing-
phones-to-users-with.html
• UDS and AXL: http://samiamsam.com/2014/06/24/cisco-api-series-the-uds-api-
with-a-side-of-axl/
License Management Models with PLM
License
Management
CUCM cluster CUCM cluster
License
Management ELM Stand Alone
CUCM cluster CUCM cluster
DISTRIBUTED CENTRALIZED
• PLM provides for both distributed and centralized license management model
• Separate virtual machine for ELM (recommended)
• Separate virtual machines based on UC applications, site or line of business
• Co-resident to CUCM or CUC corporate wide or based on UC applications, site or line of business
• Consideration when designing a licensing solution

• 60 days overage and redundancy/re-host (registration ID and MAC) of ELM
Reference
Refresh Upgrade (RU) for MCS 7825 and
MCS 7828 (CUCM 8.6 & 9.X Upgrade)
MCS-7825 H3/H4 MCS-7825 H3/H4

MCS-7825-I3/I4/I5 RU MCS-7825-I3/I4/I5
MCS-7828-H3 MCS-7828-H3
MCS-7828-I3/I4/I5 MCS-7828-I3/I4/I5
• Software raid and OS reinstallation by RHEL 5 requires USB key

• CUCM- 16 GB USB drive. CUC and CUCM BE 5000 – 128 GB USB drive
• External power USB drive. One per server. Do not remove until upgrade completes
• DRS back up before upgrade. USB data cannot be restore from new installation
• Reinstallation and DRS restore as the only reversion method
• Check memory required per server (MCS7825 – 4GB, MCS7828 – 6GB) before upgrade
• Recommend to virtualize at this point if possible
Upgrade and Migration Caveats with Diskspace
Upgrade Definition Scenario
W1 Upgrade Windows to appliance upgrade up to CUCM 7.1(5)
L2 Upgrade Appliance to appliance upgrade within same major RHEL release (before
CUCM 8.6)
RU Upgrade Appliance to appliance upgrade between major RHEL releases (starting with
CUCM 8.6)
Bridge Upgrade Servers too old to run latest CUCM version. Use DRS file to change platform
to continue upgrade
Jump Upgrade Servers too old to run CUCM version 8.0(2) or later to virtualized. Virtualized
in lab to perform upgrade
Manual Platform Changing servers platform. Typically from bare metal servers to virtualized
Change environment
Automated Platform
Change w/ PCD
In-Place L2 Upgrade Process
• Version 9 of license
manager is
Enterprise License
Existing Existing Existing New CUCM New CUCM ELM
Manager (ELM)
Cluster Cluster Cluster • ELM license is
required only when
Upgrade Upgrade Switch Switch Add going from 8.X or
Publisher Partition Partition License to
Subscribers earlier to 9.X
ELM and
Back Up Inactive Inactive on on add
With DRS Partition Partition Publisher Subscriber CUCM to • This scenario
ELM
applies to both bare
metal and
virtualized CUCM
CUCM CUCM
sFTP
Server
DVD Kit DVD Kit OS Admin OS Admin
1 2 3 4 5 6
In-Place RU Upgrade Process
manager is
Enterprise License
Existing Existing New CUCM Existing New CUCM ELM
Manager (ELM)
CUCM CUCM 9.X Cluster CUCM 9.X Cluster
Cluster Cluster Cluster • ELM license is
required only when
Upgrade Switch Upgrade Switch Add going from 8.X or
Publisher Partition Partition License to
Subscribers ELM and earlier to 9.X
Back Up Inactive on Inactive on add
With DRS Partition Publisher Subscriber
Partition CUCM to • This scenario
ELM
applies to both bare
metal and
virtualized CUCM
CUCM CUCM
sFTP
9.X CLI or 9.X CLI or
Server
DVD Kit OS Admin DVD Kit OS Admin
1 2 3 4 5 6
In-Place L2 Upgrade Process
manager is Prime
License Manager
Existing Existing Existing New CUCM New CUCM PLM (PLM)
Cluster Cluster Cluster • PLM license is
required only when
Upgrade
License to
going from 9.X or
Publisher Subscribers Partition Partition earlier to 10.X
PLM and
Back Up Inactive Inactive on on add
With DRS Partition Partition Publisher Subscriber CUCM to • This scenario applies
PLM to virtualized CUCM
only
CUCM CUCM • For 10.X to 10.5,

sFTP upgrade IM&P after
Server
ISO file ISO File OS Admin OS Admin CUCM cluster is
upgraded
1 2 3 4 5 6
manager is Prime
License Manager
Existing Existing New CUCM Existing New CUCM PLM (PLM)
Cluster Cluster Cluster • PLM license is
required only when
Upgrade
License to
going from 9.X or
Publisher Partition Subscribers Partition earlier to 10.X
PLM and
With DRS Partition Publisher Partition Subscriber CUCM to • This scenario applies
only
CUCM CUCM • For 9.X to 10.X,

sFTP upgrade IM&P after
Server
ISO file OS Admin ISO File OS Admin CUCM cluster is
upgraded
1 2 3 4 5 6
• Add version 11 of
license for the
appropriate ELM or
Existing Existing New CUCM Existing New CUCM PLM PLM
Cluster Cluster Cluster • For 9.X to 11.X,
upgrade IM&P after
Upgrade
License to
CUCM cluster is
Publisher Partition Subscribers Partition upgraded
PLM and
With DRS Partition Publisher Partition Subscriber CUCM to • This scenario applies
only
CUCM CUCM
sFTP
Server
ISO file OS Admin ISO File OS Admin
1 2 3 4 5 6
Refresh Upgrade (RU) and COP File
• Perform a DRS back up before upgrade
• Install Refresh Upgrade COP file v1.5 (ciscocm.refresh_upgrade_v1.5.cop.sgn) file on all CUCM
servers. Also for CUC, CUCM-BE 5K and IME
• Active version is CUCM 8.5 or earlier (i.e. No need for CUCM 8.6, 9.X or 10.X)
• Upgrade to CUCM version 8.6 or later (e.g. Required for upgrade from CUCM version 8.5 to 10.5)
• No reboot is required
• Installation fails if changes are already in CUCM code (e.g. ES that already have this code change)
• CLI: “show version active” or OS Admin: “Show > Software” to see installed COP file(s)
• Track console of server to monitor progress of upgrade – IP KVM, HP ILO, or IBM RSA for bare metal
server or virtual machine console for virtual machine
• CUCM RU COP file is for CUCM version 8.5 or earlier. Other collaboration solutions RU might be at a
different release (e.g. CUP 8.6(1) to CUP 8.6(4) requires CUP RU COP file v1.01)
• * RU COP file might be use once for older releases while RU can occur several times due to change in
RHEL version
CUCM Refresh Upgrade COP File v1.5

https://software.cisco.com/download/release.html?mdfid=285963825&flowid=50402&softwareid=282204704&release=COP-%2520Files&relind=AVAILABLE&rellifecycle=&reltype=latest
CUCM 10.5 Pre-Upgrade COP File
• Pre-Upgrade RSA keys Cisco Options Package
(COP) file (ciscocm.version3-keys.cop.sgn) for
software integrity protection
• Install Pre-Upgrade COP file (ciscocm.version3-
keys.cop.sgn) file on all CUCM servers. Also for
IM&P 10.5 and PLM 10.5
- Active version is 9.1(2) or earlier (i.e. No need for CUCM 10.0)
- Upgrade to CUCM version 10.5 or later (e.g. Required for

upgrade from CUCM version 8.6 to 10.5)
- No reboot is required
- CLI: “show version active” or OS Admin: “Show > Software” to

see installed COP file(s)
• PCD does not automate this COP file installation

• Install RU COP file prior to the Pre-Upgrade COP
Pre-Upgrade COP file
File
http://software.cisco.com/download/release.html?mdfid=284603137&flowid=47762&softwareid=282204704&release=COP-Files&relind=AVAILABLE&rellifecycle=&reltype=latest
2. Automated Platform Conversion with PCD
CUCM on Virtualized
MCS PCD CUCM 10.X
• Bare metal CUCM to virtualized CUCM (P2V)

- Install ciscocm.ucmap_platformconfig.cop file to the source servers to export data
- Build new cluster
- Import data
• Same or different destination IP address and/or hostname
• Scheduled or immediate execution
Automated Platform Conversion with PCD
 CUCM Bootable ISO provided to ESXi Hosts via
NFS service running on PCD
5
1  Migration (M1) Steps
CUCM 6.X
4 1. Add Source CUCM Clusters to PCD
Inventory
Create
CUCM 2. Add ESXi Hosts to PCD Inventory
VMs via
CUCM 7.X OVA
PCD 2 3. Add CUCM Bootable ISOs to PCD SFTP
Server (adminsftp user / fresh_install folder)
4. Deploy Empty CUCM VM on ESXi Hosts via
OVA
CUCM 8.X 3
5. Map Physical Nodes to Virtual VMs and
Schedule Migration Tasks
ESXi
Host
Reference
PCD Inventory Source Cluster Discovery
• First we need to
Discover the Source
CUCM 7.1(5) Cluster
PCD Inventory Source Cluster Discovery – Step
Reference
1
PCD Inventory Source Cluster Discovery – Step
Reference
2
Installs these COP Files

• ciscocm.ucmap_platformconfig.cop
• ciscocm.migrate-export-v1.13.cop
Reference
PCD Inventory Source Cluster Discovery – Step 3
• This Step can be skipped

• Not Required for Migration Job
Reference
PCD Inventory ESXi Hosts
Reference
PCD Inventory Add ESXi Hosts
Reference
Deploy Destination CUCM Virtual Machines

• Deploy CUCM using CUCM
10.0/11.0 OVA
• cucm_10.5_vmv8_v1.8.ova
• cucm_11.0_vmv8_v1.0.ova
• 7500 / 10k User Configuration
• Deploy CUCM VMs to their
assigned ESXi Hosts following
Hardware Sizing Guidelines
• Cisco Collaboration Virtual Machine
Placement Tool
• These Empty CUCM VMs will be
assigned to the Destination
Migration Cluster in the following
steps
Reference
Upload CUCM Bootable ISO to PCD Datastore

• Upload Bootable CUCM ISO Files to
PCD fresh_install folder
• Use SFTP to connect to PCD
• Username adminsftp
• Password OS Admin password
• Make sure the Uploaded file has
Group + World Read Access
• ESXi Hosts will mount PCD
fresh_install folder as NFS datastore
© 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Reference
PCD Inventory Define Destination Cluster
Reference
PCD Inventory Define Destination Cluster – Step 1
Reference
Reference
PCD Inventory Configure Destination Cluster
Reference
PCD Inventory Configure Destination Cluster
Reference
Reference
Reference

Must Use DNS on
destination if Source Cluster
is Already Enabled to Use
DNS
No Option to
Remove DNS on
Destination
Reference
Reference
Reference
PCD Add Migration Task
Reference
PCD Add Migration Task – Step 1
Reference
Reference
Reference
• By Default Migration is
Fully Serialized
• Delete Steps 6 - 14
Reference
Reference
• Click the Pencil for Step 3

• Add the half the subscribers
Reference
• Click the Pencil for Step 4

• Add the rest of the subscribers
Reference
CUCM-BE 5K to CUCM-BE 6K or CUCM/CUC
BAT Export BAT Data BAT Import
CUCM-BE 5K
Virtualized CUCM
and CUC 10.5
COBRAS COBRAS Data COBRAS Import
Export
• Upgrade CUCM-BE to version CUCM-BE 10.5

• Export data:
• BAT for call control and COBRAS for messaging
• Build virtualized CUCM and CUC
• Import data:
• BAT for CUCM and COBRAS for CUC
Migration CUCM-BE 5K to CUCM-BE 6K:
https://communities.cisco.com/docs/DOC-33988
CUCM and RSA (Rivest Shamir Adleman) Version
RSA version of ISO or COP file(s) have match what CUCM supports COP
(sgn)
file
ISO
CUCM RSA RSA Signed

Version Files
CUCM Build RSA Version CUCM Build Signed RSA Version

< 8.5.1.17123-1 RSA v2 5.0(4) – 10.0(X) RSA v2
< 8.6.2.24122-1 RSA v2 10.5(1) or higher RSA v3
< 9.1.2.11018-1 RSA v2 ciscocm.free_common_space_v1.1.k3.cop.sgn
10.X RSA v2 and v3 Third party COP files need RSA v3 signature
11.X RSA v3 Only RSA v3 files can be added to CUCM 11.X and later
CUCM and ISO/COP Files
CUCM accepts RSA v2
COP
(sgn)
CUCM accepts RSA v3
✔ CUCM 11.5 ISO is RSA v3
CUCM 9.1(2) COP file is RSA v3 file

ISO
ciscocm.version3-keys.cop CUCM 11.5
CUCM accepts RSA v2 CUCM accepts RSA v2 /v3

✔ CUCM 11.5 ISO is RSA v3
✔
ISO
ISO
CUCM 9.1(2) CUCM 10.0 ISO is RSA v2 CUCM 10.0 CUCM 11.5
CUCM 10.0
ciscocm.free_common_space_v1.0.cop.sgn
COP
(sgn)
CUCM accepts RSA v3 COP file is RSA v2 file
X
COP file is RSA v3 COP
✔ (sgn)
file
CUCM accepts RSA v3
CUCM 11.5 ciscocm.free_common_space_v1.3.k3.cop.sgn
Verify that Third-party COP files have been signed with RSA v3 if installed onto CUCM 11.X or later:
2N, Ascom, Avara, BT, DoCoMo, Fujitsu, Intelbras, IP Blue, IP Trade, Mindshare, Mobile Heartbeat, Nokia, RIM, Sony, Speakerbus,
Spectralink, Syn-Apps, Tandberg, Telecore, Telematrix, Verizon
Sample PowerShell Script to update CUCM 10.0
Virtual Machine
### Remember to Shutdown your CUCM first ###
param (
[string]$vCenter = ”vcenter.cisco.com",
[string]$vName = ”cucm1a",
[string]$toolsPolicy = "UpgradeAtPowerCycle"
)
if ( (Get-PSSnapin -Name VMware.VimAutomation.Core -ErrorAction SilentlyContinue) -eq $null )
{
Add-PsSnapin VMware.VimAutomation.Core
}
Connect-VIServer $vCenter -WarningAction 0
get-vm -Name $vName | Set-VM -GuestID "rhel6_64Guest" -confirm:$false
get-vm -Name $vName | get-networkadapter | set-networkadapter -type "vmxnet3" -confirm:$false
$vmConfigSpec = New-Object VMware.Vim.VirtualMachineConfigSpec
$vmConfigSpec.Tools = New-Object VMware.Vim.ToolsConfigInfo
$vmConfigSpec.Tools.ToolsUpgradePolicy = $toolsPolicy
#$vmConfigSpec.Tools.ToolsUpgradePolicy = "manual"
Get-View -ViewType VirtualMachine -Filter @{"Name" = $vName} | %{$_.ReconfigVM($vmConfigSpec)}
Get-View -ViewType VirtualMachine -Filter @{"Name" = $vName} | %{$_.reload()}
Sample PowerShell Script to update CUCM 10.0
Virtual Machines in a Folder
### Remember to Shutdown your CUCMs first ###
param (
[string]$vCenter = ”vcenter.cisco.com",
[string]$vFolder = ”CUCM Folder",
[string]$toolsPolicy = "UpgradeAtPowerCycle"
)
if ( (Get-PSSnapin -Name VMware.VimAutomation.Core -ErrorAction SilentlyContinue) -eq $null )
{
Add-PsSnapin VMware.VimAutomation.Core
}
Connect-VIServer $vCenter -WarningAction 0
Get-Folder $vFolder | get-vm | Set-VM -GuestID "rhel6_64Guest" -confirm:$false
Get-Folder $vFolder | get-vm | get-networkadapter | set-networkadapter -type "vmxnet3" -confirm:$false
$vmConfigSpec = New-Object VMware.Vim.VirtualMachineConfigSpec
$vmConfigSpec.Tools = New-Object VMware.Vim.ToolsConfigInfo
$vmConfigSpec.Tools.ToolsUpgradePolicy = $toolsPolicy
#$vmConfigSpec.Tools.ToolsUpgradePolicy = "manual"
$folder = Get-Folder $vFolder | Get-View
Get-View -SearchRoot $folder.MoRef -ViewType VirtualMachine | %{$_.ReconfigVM($vmConfigSpec)}
Get-View -SearchRoot $folder.MoRef -ViewType VirtualMachine | %{$_.reload()}© 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Sample PowerShell Script to Deploy CUCM VMs in
Bulk to use as PCD Migration Destination
### Deploy a Blank CUCM choosing the Deployment Size and convert to Template First###
### Here this template is named cucm_10.5_vmv8_v1.8.ova_7.5k , Script tested with PowerCLI 6.0 ###
$vCenter = ”vcenter1.cisco.com”
$vFolder = ”UCMDestination-Folder”
$template = "cucm_10.5_vmv8_v1.8.ova_7.5k”
$vmNames = @{}
$vmNames[”ucmdestpub"] = @("ecats-rtp-cc42-esxi-1.ecatsrtp.cisco.com","ecats-rtp-cc42-esxi-1-
datastore1”,”Vlan123")
$vmNames[”ucmdestsub1"] = @("ecats-rtp-cc42-esxi-1.ecatsrtp.cisco.com","ecats-rtp-cc42-esxi-2-
datastore1”,”Vlan124")
Get-vc -server $vCenter

foreach ($vmName in $vmNames.keys)
{
$vm = New-VM -Name $vmName -Location $vFolder -Template $template -Host $vmNames[$vmName][0] -Datastore
$vmNames[$vmName][1] -Confirm:$false
###### Deploy CUCM with Local Vswitch Example
# get-NetworkAdapter -VM $vm | Set-NetworkAdapter -NetworkName $vmNames[$vmName][2] -Confirm:$false
###### Deploy CUCM with Distributed VSwitch Example
$myNetworkAdapter = Get-NetworkAdapter -VM $vm
$myVDPortGroup = Get-VDPortGroup -Name $vmNames[$vmName][2] -VDSwitch ”myVDSwitch"
Set-NetworkAdapter -NetworkAdapter $myNetworkAdapter -Portgroup $myVDPortGroup -Confirm:$false
}
Echo Done
CUCM License
CUCM 6.X
PLM
1. Number of public space
2. Pre-upgrade license report or
LCU-License-
Report.zip
licensing@cisco.com licensing case number
3. UCSS/ESW contract or SO
Pre-Upgrade number
CUCM 7.X
License License Report
Count
Utility
CUCM 8.X
• Perform AXL calls to existing CUCM (6.X, 7.X and 8.X) clusters for current license and license
usage and generate pre-upgrade license report
• Report can be send to licensing@cisco.com
• Include number of public space, license case number / MAC address of existing system and SWSS
contract number, upgrade order number and send directly to licensing@cisco.com
License Count Utility 9.1.2 (LCUZIP-Ver9.1.2.zip):

https://software.cisco.com/download/release.html?mdfid=285963825&flowid=&softwareid=282204704&release=DAT&relind=AVAILABLE&rellifecycle=&reltype=latest
Web - Cisco TAC Support Case Manager
Email
Phone
• 1-800-553-2447
Cisco Unified Communications Licensing :

http://www.cisco.com/c/en/us/products/unified-communications/unified-communications-licensing/index.html
Previous CUCM 8.X and Earlier
Device Based License
Reference
CUCM 5.0 to 7.1(3) License Types
TECHNICAL ORDERING Description
Node Node
Number nodes per cluster
DLU DLU
Number of phones, type of phones, mobility feature
and presence users
SW Feature ESW/UCSS
Maintenance for minor and major version upgrade
• Three license types: Node, Device License Unit (DLU) and Software Feature license
• Node license is enforced based on the number of node running CM service. TFTP and
MOH also requires node licenses
• DLU is enforced based on provisioned phones, type of phones, mobility and presence
features
• Major version upgrade requires Software Feature license
• License files are locked to MAC address of the first node or Publisher of the cluster
• License enforcement is done on CUCM
Reference
CUCM 7.1(5) to 8.6 License Types
TECHNICAL ORDERING Description
Node UCL/CUWL
Number nodes per cluster
DLU UCL/CUWL
Number of phones, type of phones, mobility feature
and presence users
SW Feature ESW/UCSS
Maintenance for minor and major version upgrade
• Technical license enforcement is the same as before: Node, DLU and Software Feature
license. Device based
• Ordering is based on User based
• For bare metal servers (MCS), licenses are locked to MAC address of the first node or
Publisher of the cluster
• In virtualized environment, licenses are locked to the license MAC address of the first
node or Publisher of the cluster
• License enforcement is done on CUCM
Reference
License Type & DLU (CUCM 8.6 and earlier)
LICENSE TYPE DLU Comments
CUWL Pro 17/12 Prior to January 2012/After January 2012
CUWL Standard 11/8 Prior to January 2012/After January 2012
CUWL Entry 9 Migrate to Enhanced Plus UCL CUCM 9.X and later
CUWL Analog 2 Migrate to Essential UCL in CUCM 9.X and later
CUWL Public 5 Migrate to Enhanced UCL in CUCM 9.X and later
Space
Enhanced UCL 6 Migrate to Enhanced UCL or CUWL in CUCM 9.X and later
Basic UCL 4 Migrate to Basic UCL in CUCM 9.X and later
Essential UCL 0 Migrate to Essential UCL in CUCM 9.X and later
Public Space 5 Migrate to Enhanced UCL in CUCM 9.X and later
UCL Adjunct 5 Using corresponding license, migrate to Enhanced Plus UCL in CUCM 9.X and later
UCL TP 6 Migrate to TelePresence Room Based Endpoint, Single or Multi-Screen
Single/Multi-screen
Collaborate Now Upgrade Scenario Guide

New
http://www.cisco.com/web/partners/downloads/partner/WWChannels/promotions/download/collaborate-now-migration-scenario-guide-jpg.pptx
Current CUCM 9.X and Later User
Based License
CUCM License Usage
CUCM License Usage
• Extension mobility users: No license
1 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.
User • Device with Owner User ID association: UCL or CUWL
3 / 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
• TelePresence (TP) device
4 TelePresence • E.g. CTS, MX, SX, TX, etc.
List of devices and associated license are in the appendix
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
• Previous Methods:
- BAT, Run SQL via CLI, UDS and AXL
- Links in the Appendix
Recommend to perform this task before upgrading to
CUCM 9.X or later
Cisco Device Assignment Tool
(DAT)
• Pre-upgrade or post-upgrade of CUCM 9.0
Device Assignment Tool 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 (OwnerUserID) to Based Licensing (CUCM 9.0 and later
3 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
Reference
• Based on sequence of 7 rules or manually
DAT edited xls file
(UdatApplication.jar)
Web - Cisco TAC Support Case Manager
Email
Phone
• 1-800-553-2447
Cisco Unified Communications Licensing :

http://www.cisco.com/c/en/us/products/unified-communications/unified-communications-licensing/index.html
Prime License Manager (PLM)
Cisco Prime License Manager (PLM)
PLM Implementation Products
PLM
Bootable Standalone PLM
Prime_LM
Co-resident with CUCM PLM + CUCM
PLM + CUCM Co-resident with CUCMBE 6K PLM + CUCMBE 6K
Bootable
CUCM PLM + CUC Co-resident with CUC PLM + CUC
10.X/11.x
• PLM is a centralized enterprise-wide license management solution for Cisco collaboration applications
- CUCM, CUCM SME and CUCMBE 6K
- Cisco Emergency Responder (CER)
• PLM deployment can be standalone or co-resident with CUCM, CUCM-BE 6K or CUC
• In PLM 10.5(1)SU1, PLM can be removed from the product
Cisco Prime License Manager 11.5 User Guide:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/plm/11_5_1/userguide/CPLM_BK_CE0970F4_00_user-guide-rel-1151.html
Reference
License Manager Versions and Builds
License Manager
Version Build
Enterprise License Manager (ELM) Same as CUCM Same as CUCM
9.0 – 9.1 e.g. 9.1(2) SU3 9.1.2.13900-10
Prime License Manager (PLM) Version Build

10.X-11.X 11.5.(1) NEW 11.5.1.10000-5
11.0(1) 11.0.1.10000-2
10.5(2) 10.5.2.10000-6
10.0(1) 10.0.1.1000-19
• ELM is built into CUCM ISO Co-resident: same Standalone: Different

build as CUCM build as CUCM
• PLM is built into CUCM ISO or as independent ISO with standalone
deployment
License Manager Architecture 11.X
First First
node of node of
CUC 1 CUC 2 CER 1
CER
API API API API API
PLM
PLM
License file
• License Manager API in CUCM 11.X, CUC 11.X and CER 11.X interacts with PLM for
license request and approval
• License Manager API was added CUCM in version 9.0, CUC in version 9.0 and CER in
version 10.0
License Manager Product Support and Usage
Product Version ELM 9.X (Bare Metal PLM 10.X PLM 11.X
or Virtualized) (Virtualized) (Virtualized)
CUCM 9.X Yes Yes Yes
/ CUC 9.X
CUCM 10.X Yes w/ License Yes Yes
/ CUC 10.X Definition (1 or 2)
CUCM 11.X Yes w/ License Yes w/ License Yes
/ CUC 11.X Definition (2) Definition (3)
CER 10.X No Yes Yes
CER 11.X No Yes w/ License Yes

Definition (3)
3. License Definition for 10.X = license-def-11-for-PLM-10x.def
• For CER 10.X/11.X, use PLM

• Use license definition file to support the higher version of the products (CUCM, CUC and CER)
• For virtualized PLM and virtualized CUCM with co-resident PLM, manually set MAC address since
license is partly based on MAC address (Edit virtual machine settings > Machine Network adapter
> Manual) before requesting license file
ELM to PLM Upgrade
ELM 9.X ELM 9.X
PC
ELM/PLM
ELM 9.X Upgrade PLM 11.5
PLM
PLM 10.X Upgrade PLM 11.5
• Use “Replacing a Single Server for Cisco Unified Communications Manager” procedure
to change from bare metal ELM to virtualized ELM.
• Use ELM/PLM upgrade COP file (elm_Elm_v9_1_1_PlmUpgrade.cop.sgn) to allow for
ELM to PLM10.X/11.X upgrade
• Use pre-upgrade RSA keys COP file (ciscocm.version3-keys.cop.sgn) to upgrade to
PLM 10.5 and later for 9.X
• Re-host license by using Product License Registration (www.cisco.com/go/license)
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/install/11_5_1/replace/cucm_b_replacing-single-server-or-cluster-1151.html
CUCM and PLM Interaction
• PLM polls all registered CUCM clusters
• CUCM cluster evaluates license usage and sends
license usage back to PLM
CUCM PLM
• Evaluate phone, • Poll all products
• PLM evaluate all CUCM cluster responses to see
users and every 24 hours if there is adequate licenses for the requested
features usage • Evaluate types
• Send license adequate
usage to PLM licenses • PLM performs license substitution if does not have
• Receive license • Perform license adequate license of the requested type
response and substitution
operate in the • Provide Valid or • PLM response back to with either valid or invalid
appropriate Invalid license (not enough licenses) to all CUCM clusters
mode response
• CUCM receives the response from PLM and
function accordingly
Detailed CUCM and ELM/PLM interactions with

signaling are in the appendix
PLM License Substitution
• Licenses are based on hierarchical model where lower feature
license can be covered by a higher feature license
CUWL Standard
- I.E. UCL Basic can be covered by UCL Enhance
UCL Enhanced +
- I.E. UCL Enhance can be covered by UCL Enhance Plus
UCL Enhanced
• PLM evaluates ALL system license requirements on a per product
UCL Basic (CUCM, CUC and CER) basis and respond back with one
consistent response to ALL registered systems
UCL - Essential
- VALID: adequate license
User License
Substitution
- INVALID: inadequate license
• Centralize and enterprise-wide licensing view per product set
Reference
Grace Period and License Overage
Grace Behavior when license is exceeded
Period
License
Manager
API
CUCM 9.X-11.X 60 License Overage:
• System function normally
• Existing phones cannot be de-provisioning
• Additional phones cannot be provisioned
CER
CUC 9.X-10.5 60 Expire:
License
License
Manager
Manager
API
• System will not take calls
API • Users cannot retrieve messages
• Additional users or mailboxes cannot be provisioned
CUC 11.X 60 Expire:
• System will take calls
• Send or receive voicemails
• Additional voicemail boxes can not be provisioned
CER 10.X-11.X 60 License Overage:

• Responder system stops tracking and updating the phone
Location

Brkucc 2011

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Brkucc 2011

Enviado por

Direitos autorais:

Formatos disponíveis

Best Practices for Migrating

Previous Versions of Cisco Unified

1. Session Objectives and Scope

• Automated process with PCD

Prime Collaboration • CUCM Orchestration tool for operational tasks

Enterprise License Manager

Prime License Manager

Cisco UCS, Business Edition

2 Virtualized CUCM SU / RU Virtualized CUCM 11.5

8.0 8.5 and 8.6 - http://www.cisco.com/c/en/us/products/collateral

Before End-of-Sales Date Ability to deploying new cluster

After End-of-Sales Date Start planning for upgrades

End of SW Maintenance Desire to complete the upgrade 1 year

- Predictable End of Sales/Support milestone durations

End-of-Life and End-of-Sale Notices

Service and End-of-Life End-of-Life

Cisco Notification Service

11.5(1) 11.5.1.10000-6 10.5.2.10000-5

11.0(1) 11.0.1.10000-10 10.5.2.10000-5

10.5(2)SU3 10.5.2.13900-12 10.5.2.20000-5 (example)

Standard Upgrade (formerly called L2 Upgrade):

SU • Active partition is running while software upgraded on

RU • Server is down while software is upgraded

Detailed SU and RU upgrade process

CUCM 11 Active Partition (CUCM 10) Inactive Partition (CUCM 10)

• Always Upgrade Publisher node first

Endpoint Refresh Tool - Migration FX

Endpoint Refresh Tool - Migration FX

• Add version 11.X of

CUCM CUCM • This scenario applies

CUCM 9.1(2) COP file adds RSA v3 file

ciscocm.version3-keys.cop CUCM 11.5

CUCM 11.5 ISO RSA v3 Signed

MCS 7845-I3 C240M4 • E.g. MCS to UCS

PC • Virtual to Virtual Platform Conversion

PC • Virtual to Virtual Platform Conversion

Cisco DRS (Disaster Recovery System):

1 Traditional method leveraging DRS backup and DRS restore to

New New CUCM New New Virtualized

U Upgrade existing clusters

PCD • VMware vApp is pre-configured virtual machine with OS

PCD 11.5(3) Administration Guide:

PCD 11.5(3) Administration Guide:

VOS VOS VOS VOS

- 80 GB vDisk (Consider Increasing)

Virtualization Software Requirements

PCD Version Migrate or Fresh install Task

👍 Upgrade PCD to latest version 11.5(3) First 👍

PUT OVA PCD_VAPP.OVA for vSphere Client

PCD Version PCD Build

VMware vSphere ESXi

• PCD and CUCM communication

Set PCD’s NAT IP when it resides

• PCD and CUCM communication

- Remote SFTP Support for Upgrades HTTPs

- Multi SFTP Server Support

- SFTP Server Details must be assigned HTTPs

- Default is localhost = PCD Local Folder

From CUCM Version Target CUCM Version

Simple Migration: Same network settings (IP

Detailed step by step with screen captures are

• Bare metal CUCM to virtualized CUCM (P2V)

• Same or different destination IP address and/or hostname