Brkucc 2011 migrating-from_previous_versions_of_cisco_unified_communications_manager_(cucm)_to_version_12.0

Best Practices for Migrating
From Previous Versions of Cisco
Unified Communications
Manager (CUCM) to Version
12.0
Brandon Ta, Consulting Systems Engineer
bta@cisco.com
BRKUCC-2011

© 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Cisco Spark
Questions?
Use Cisco Spark to chat with the
speaker after the session
1. Find this session in the Cisco Live Mobile App
2. Click “Join the Discussion”
3. Install Spark or go directly to the space
4. Enter messages/questions in the space
How
cs.co/ciscolivebot#BRKUCC-2011Cisco Spark spaces will be
available until July 3, 2017.
BRKUCC-2011 3

AS
BRKUCC-
2011
(Participants)
Call Control
TigerTeam
SVS Lab
TAC
Engineering
Thank You!
• Revised Upgrade and Migration Guide
for Cisco Unified Communications
Manager and IM and Presence Service
Document on CCO
• Upgrade Simplification Initiative
(James Arias)
• AS
• BRKUCC-2011 Content (Participants)
• Call Control Tiger Team
• Engineering
• SVS Lab
• TAC
BRKUCC-2011 4

Previous Sessions for various CUCM Versions
• To CUCM 9.X
BRKUCC-2011 - Best Practices for Migrating Previous Versions of Cisco Unified
Communications Manager (CUCM) to CUCM 9.X (2012 San Diego & 2013 Orlando)
• To CUCM 10.X
BRKUCC-2011 - Best Practices for Migrating Previous Versions of CUCM to
version 10.5. (2014 San Francisco & 2015 San Diego)
• To CUCM 11.X
BRKUCC-2011 - Best Practices for Migrating Previous Versions of CUCM to
version 11 (2016 San Francisco)
Reference
Cisco Live Access Sessions On-demand
http://www.ciscolive.com/global/
BRKUCC-2011 5

Required GAAP Reconciliation
and Forward-Looking Statements
The Cisco products, service or features identified in this document may
not yet be available or may not be available in all areas and may be
subject to change without notice. Consult your local Cisco business
contact for information on the products or services available in your
area. You can find additional information via Cisco’s World Wide Web
server at http://www.cisco.com. Actual performance and environmental
costs of Cisco products will vary depending on individual customer
configurations and conditions.
BRKUCC-2011 6

Agenda
• Session Objectives and Scope
• Overview of System Level Planning
• Smart Licensing Planning and Design for CUCM 12.X
• CUCM Upgrade/Migration Methods and Tools
• Platform Support and Migration
• System Preparation and Optimizing Upgrade Speed for CUCM Upgrade
• Upgrade Execution and CUCM Registration with Smart Licensing

Session Objectives and Scope
1

Session Objectives
• To provide foundational knowledge for a successful upgrade or migration to
CUCM 12.0
• Planning
• Considerations
• Approaches
• To provide an overview of Smart Licensing and Smart Account as it relates to
CUCM including migration of CUCM licenses as well as CUCM registration to
CSSM (Cisco Smart Software Manager)
• To provide an overview and best practices to optimize upgrade and migration
from a holistic system level
BRKUCC-2011 9

Session Scope
• Platform conversion from bare
metal CUCM to virtualized
CUCM 12.0
• Upgrade or migrate to CUCM
12.0
• System level approach
• License conversion from
traditional node and ELM/PLM
license to Smart Licensing
1Bare Metal CUCM Virtualized CUCM 12.0
2Virtualized CUCM Virtualized CUCM 12.0
BRKUCC-2011 10

Overview of Systems Level Planning
for CUCM Upgrade and/or Migration
2

System Level Planning
License Management
Upgrade/Migration
Methods and
Tools
Platform
System
Preparation
Optimizing
Upgrade Speed
Execution
Smart Licensing
Smart Account
License Conversion
License Optimization
EOL <9..0 License
DSU
DRU
PCDU
PCDM
Servers
Virtualization
Virtualized CUCM
VMware changes
Deprecated phones
Disk Space
COP file(s)
Pre-Upgrade list
link
TFTP server
DB replication
Purge CDR
Phone firmware
Application
dependencies
Upgrade windows
Smart Registration
Post-Upgrade list
link
BRKUCC-2011 12

Smart Licensing Planning and
Design for CUCM 12.X
3

License Manager for CUCM by Versions
CUCM Version 5.0-8.6 9.0-11.5 12.0 and later
License Manager Publisher ELM/PLM Cisco Smart Software Manager (CSSM)
Focus of this section of the presentation
(Smart Licensing, CSSM and CUCM)
CUCMSTATUSSMARTAGENT
STATUS
BRKUCC-2011 14

Smart Licensing Requirements for Upgrade/Migration
Smart Account
Structure
(Account/Roles)
Smart License
Enabled
Products
Deployment
Model
CER
1 2 3
BRKUCC-2011 16

1.Smart Account Structure: Smart Account
Create or get access to
Smart Account
(e.g. abc.com, xyz.com,
etc.)
Design Smart Accounts
Structure
Create Virtual Accounts
and Define/Assign
Roles
Account Description and Usage Examples
Smart Account
Account that represent a company (domain
based)
abc.com, xyz.com, etc.
Virtual Account
• Sub-Account to Smart Account
• Represent different departments of the main
Smart Account or organization
• Where product registers to
• Where license are assigned to
• Equal to an instance of ELM/PLM
Geographical locations,
departments, product
types, etc.
E.G. Virtual Account “collaboration” have X,Y, Z, etc. quantity of collaboration licenses and where all
Smart Licensing enabled collaboration products will register to
Top Level:
Smart Account = abc.com
Sub Level:
Virtual Account =
Collaboration
Sub Level:
Virtual Account =
Infrastructure
ACCOUNT
BRKUCC-2011 17

1. Smart Account Structure: Roles
Create or get access to
Smart Account
(e.g. abc.com, xyz.com,
etc.)
Design Smart Accounts
Structure
Create Virtual Accounts
and Define/Assign
Roles
Top Level:
Smart Account Admin = Manager1
Smart Account User = TeamLead2 (view)
Sub Level for Collaboration Virtual Account:
Virtual Account Admin = TechLead3
Virtual Account User = Engineer4
Roles Privileges
Visibility/Typical
Assignment
Smart Account
Administrator
Highest level account that can create
accounts and roles at the Smart
Account level and Virtual Account level
Managers and admin of the
Smart Account
Smart Account User
View level at the Smart Account level
and Virtual Account level
Viewers of the Smart Account
Virtual Account
Administrator
• Manage properties of the assigned
Virtual Account
• User can register and view licenses
specific to the assigned Virtual
Account
Lead engineers
Virtual Account User
• View properties of the assigned
Virtual Account
• User can register and view licenses
specific to the Virtual Account
Deployment engineers
ROLES
BRKUCC-2011 18

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

2.Smart License Enabled Collaboration Products
Collaboration Products Version Licensing Mode
Cisco Unified Communications Manager 12.0 Smart ONLY
Session Management Edition 12.0 Smart ONLY
Unity Connection 12.0 Smart ONLY
Cisco Emergency Responder 12.0 Smart ONLY
Cisco Unified Communications Manager
Express
11.0 Hybrid
Cisco Unity Express Virtual June 2017 Smart ONLY
vCUSP 9.0 Smart ONLY
vCUBE Current Hybrid
Smart Licensing Enable Product Roadmap – Search for “roadmap”
https://ucrm-cisco.force.com/OperationsExchange/s/
BRKUCC-2011 20

3.Smart Licensing Deployment Models
Direct cloud access
Cisco product sends usage information directly over the internet. No
additional components are needed.
Options
Direct cloud access through an HTTPs proxy
Cisco Products send usage information over the internet via a
Proxy Server – Smart Call Home Transport Gateway (Free VM
Download) or off-the-shelf Proxy (such as Apache).
Mediated access through an on-premises collector –
connected
Cisco Products send usage information to a local connected collector,
which acts as a local license authority. Periodically, an exchange of
information will be performed to keep the databases in sync.
Mediated access through an on-premises collector –
disconnected
Cisco Products send usage information to a local disconnected
collector, which acts as a local license authority. Once a month,
an exchange of human readable information will be performed to
keep the databases in sync.
SecurityPolicy
Easeofuse
1
2
3
4
Cisco
Product HTTPs
Cisco
Product
Transport
Gateway or
HTTPs
Proxy
Cisco
Product
HTTPs
Cisco
Product
HTTPs
Your
Cisco
Softwar
e
Usage
Your
Cisco
Softwar
e
Usage
Your
Cisco
Softwar
e
Usage
Your
Cisco
Softwar
e
Usage
Cisco.com
Cisco.com
Cisco.comSmart Software
Manager satellite
Cisco.com
File
Transfer
Smart Software
Manager
satellite
BRKUCC-2011 21

ELM/PLM and Smart Licensing Comparison
Cisco Smart
Software Manager
satellite
(Optional)
Cisco
Smart
Software
Manager
(CSSM)
cisco.com
CUCM
CUC
CER
CER
CUCM
CUC
CER
CER
22
CUCM
CUC
CER
CER
CUCM
CUC
CER
CER
ELM/PLM
BRKUCC-2011 22

Collaboration License Substitution within CSSM
CUWL Pro
CUWL-STD
UCL
Enhanced
Plus
UCL
Enhanced
UCL Basic
UCL Essential
CUWL STD
UCL
Enhanced
Plus
UCL
Enhanced
UCL Basic
UCL Essential
UCL Enhanced Plus
UCL
Enhanced
UCL Basic
UCL Essential
UCL Enhanced
UCL Basic
UCL Essential
UCL Basic
UCL Essential
Cisco
Smart
Software
Manager
(CSSM)
BRKUCC-2011 23

Smart Licensing Pre-Sales and Post-Sales Support
Smart
Account
White
Glove
Global License
Organization
(GLO)
Reference
• Licensing and Smart Account Questions
• Task specific real-time hands on
walk-through of Cisco Software Center
• General “how to” and issue resolution on Smart Account and Smart
Licensing creation and management
• Smart Demo license provisioning
• Assigning orders/licenses/PAKs to Smart Accounts
• Hands on, White Glove Smart Account Support
• Real-time hands on walk-through of Cisco Software Center
• Live instructions on Smart Account creation and management
• Assigning a Smart Account to an order.
• Using Cisco Smart Software Manager (CSSM) with Smart Software Licenses
• Specific topics, questions, advice, or situational expertise
BRKUCC-2011 24

Smart Licensing Reference Links
• Smart Account Information
• http://cisco.com/go/smartaccounts
• Smart Licensing Information
• http://cisco.com/go/smartlicensing
• Smart Accounts and Smart Licensing On-Demand Training Materials
• https://communities.cisco.com/docs/DOC-68582
• Request a new Sales Software Training Session at the time of your choosing
• https://www.ciscofeedback.vovici.com/se/7FAD612023A8BF7E
• Operational Exchange Community (search)
• https://ucrm-cisco.force.com/OperationsExchange/s/
Reference
BRKUCC-2011 25

Smart Licensing and Smart Account Commentary
• Create or get access to current Smart Account for lab or production deployment
• Transferring licenses within Smart Account/Virtual Accounts can be done within
an organization without Cisco intervention
• Transferring licenses between Smart Accounts requires engagement with GLO
(Global Licensing Organization). Reports are separate with separated Smart
Accounts
• Remember the Smart Account and the Virtual Account when orders are being
submitted. License will go into the Default Virtual Account is used if not
specified
• Balance between complexity (OPEX) versus control for Smart Account/Virtual
Account structure
• Take a holistic view when creating the account structure (legal requirements,
liabilities, asset management, budget alignment, policy, overhead, tax, etc.)
BRKUCC-2011 26

Smart Licensing and Smart Account Considerations
• DNS has to be enabled on CUCM to reach CSSM
• No support for Permanent License Reservation (PLR) Smart License in CUCM
12.0. Potentially in CUCM 12.5
• Consider creating a lab virtual account for each of the other virtual account to
ensure licenses are not mix up
• For other collaboration product with older Smart Agent (less than version 1.5)
and using Smart Software Manager satellite server like vCUBE, plan for 10 days
to get third tier certificates from CSSM for vCUBE to be register properly
BRKUCC-2011 27

Collaboration License Migration to Smart License
Original License
Version
Target License
Version
Time Frame (Planned) Method
8.6 or earlier 12.0 July 2017 – January 2018 Global Licensing Organization (GLO)
9.0 to 11.5 12.0 July 2017 – December 2017 Global Licensing Organization (GLO)
9.0 to 11.5 12.0 2018 CSSM
Types of Migration Approach
PAK Based Fulfilled, partial or unfulfilled PAK to Smart Licensing
Device Based PLM based to Smart Licensing
BRKUCC-2011 29

End of Life: License Migration for CUCM 8.6 or earlier
End of Life Notice 8.X (DLU) CUCM 8.5/8.6
End-of-Life Announcement Date July 22, 2014 January 25, 2014
Last Date of App. SW Support January 31, 2018 July 31, 2017
Important Event or Recommendation
June 2017 EOL Announcement
June 2017 – November 30, 2017 Customer should upgrade their CUCM 8.6 or earlier licenses to 10.X, 11.X or 12.X
November 30, 2017 Last day for license migration for CUCM 8.6 or earlier licenses to 10.X, 11.X or 12.X
December 1, 2017 to January 31, 2018 Customers with active 8.X SWSS contract can migrate their CUCM 8.6 or earlier licenses (Very few
customers will have active 8.X SWSS contract)
December 1, 2017 to Current Customers have to repurchase license for later versions of CUCM
PAKs, LCT, CUCM License report, etc.
BRKUCC-2011 30

CUCM License Usage
User
1
Device
2
• Extension mobility users: No license
• Extension mobility user with Unified Mobility (SNR): UCL Basic license
• Device without Owner User ID association: UCL
• Based on the device
• E.g. Public space phones, shared workspace phones, etc.
User
/ Device
3
• Device with Owner User ID association: UCL or CUWL
• 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
4
• TelePresence (TP) device
• 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
BRKUCC-2011 32

Device and Owner User ID Association
• 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
Device > Phone > Device Name
Recommend to perform this task before upgrading to
CUCM 9.X or later
BRKUCC-2011 33

Cisco Device Assignment Tool
(DAT)

Cisco Device Assignment Tool (DAT)
CUCM
6.X-9.1
CUCM
10.X-11.X
Device Name OwnerUserID CUCM Version
SEP123456789012 None 9.1(1a) or earlier
SEP098765432109 Anonymous 9.1(2) or later
Device Name OwnerUserID
SEP123456789012 UserX
SEP098765432109 UserY
Search for
Unassigned
Phones via AXL
per CUCM cluster
Match Users to
Unassigned
Phones based on
3 defaults and 4
optional rules
Assign Owners
(OwnerUserID) to
Phones
• Pre-upgrade or post-upgrade of CUCM 9.0
and later releases
• Align OwnerUserID to IP Phones for User
Based Licensing (CUCM 9.0 and later
releases).
• Windows PC (7 and later) or Apple Mac
(OSX 10.8 and later) Java application
35
Device Assignment Tool 11.5
https://software.cisco.com/download/release.html?mdfid=286284802&softwareid=282204704&release=COP-Files&relind=AVAILABLE&rellifecycle=&reltype=latest
Device Assignment Tool
BRKUCC-2011 35

Cisco Device Assignment Tool (DAT) Reference
DAT
(UdatApplication.jar)
• Based on sequence of 7 rules or manually
edited xls file
BRKUCC-2011 36

Opening Licensing Case
• https://tools.cisco.com/ServiceRequestTool/scm/mgmt/case
• Type of problem = Licensing
Web - Cisco TAC Support Case Manager
• licensing@cisco.com
Email
• 1-800-553-2447
• Option 3, License Support
Phone
Cisco Unified Communications Licensing :
http://www.cisco.com/c/en/us/products/unified-communications/unified-communications-licensing/index.html
BRKUCC-2011 37

CUCM Upgrade/Migration Methods
and Tools
4

CUCM Versions, Builds and
Requirements

Sample CUCM Versions and Builds
CUCM Version CUCM Build Numbering Convention
12.0(1) 12.0.1.10000-X (A.B.C.XYzzz-x)
(A) Major version (License)
11.5.1.10000-6
(B) Minor version (Long Life Release)
11.5.1.10000-6
(C) Maintenance release (Patch and/or Features)
11.5.1.10000-6
(X) Build (Patch)
11.5.1.10000-6
11.5.1.20000-5 (example)
(Y) FCS:0, ES or SU: 1-9
11.5.1.10000-6 (FCS)
11.5.1.12900-21 (ES or SU look at last three digits)
(zzz) FCS:000, ES: 001-899, SU: 900-999
11.5.1.10000-6 (FCS)
11.5.1.11001-5 (ES) (example)
11.5.1.12900-21 (SU)
11.5(1)SU2 11.5.1.12900-21
11.5(1)SU1 11.5.1.11900-26
11.5(1) 11.5.1.10000-6
11.0(1a)SU3 11.0.1.23900-5
11.0(1a)SU2 11.0.1.22900-14
11.0(1a)SU1 11.0.1.21900-11
11.0(1a) 11.0.1.20000-2
11.0(1) 11.0.1.10000-10
10.5(2)SU5 10.5.2.15900-8
10.5(2)SU4a 10.5.2.14901-1
10.5(2)SU4 10.5.2.14900-16
NEW
Reference
BRKUCC-2011 40

Build Requirements
Build Matching
Use Case Matching Example
Servers in CUCM Cluster AA.B.C.Xyzzz-x 11.5.1.10000-6
Upgrade During An Installation AA.B 11.5. to 11.5 newer
CUCM and IM&P Servers AA.B 11.5 and 11.5
Servers in IM&P Cluster AA.B.C.Xyzzz-x 11.5.1.10000-4
CUCM and Device Packs AA.B.C 10.5.2 and 10.5.2
Reference
BRKUCC-2011 41

Separate CUCM & Unity Connection 12.X
CUCM & Unity Connection
7.X-11.5 ISO
CUCM 12.X ISO
Unity Connection 12.X
ISO
BRKUCC-2011 42

Upgrade Method
CUCM 12.0
CUCM 7.1(3/5)
CUCM 8.X
CUCM 6.1(5)
CUCM 9.XAppliance
CUCM 9.X
CUCM 10.X
CUCM 8.X
CUCM 11.X
Virtualized
What
Upgrade
Method?
BRKUCC-2011 44

Upgrade Methods and Tools – Unified CM OS
Upgrades
Method
Direct
Standard
Upgrade
Direct
Refresh
Upgrade
PCD
Upgrade
PCD
Migrate
DSU
DRU
PCDU
PCDM
Prime Collaboration Deployment
(PCD) Upgrades and Migrations
Unified CM OS Admin Upgrades
Native and embedded tool
External tool (virtual machine)
BRKUCC-2011 46

Unified CM OS Admin Types of Upgrades
Unified
CM OS
Admin
SU
RU
Standard Upgrade (formerly called L2 Upgrade):
Appliance/Virtual to Appliance/Virtual model
• Low complexity with possible shortest downtime
• Between CUCM versions with the same major Linux
versions
• (e.g. CUCM 10.0 to 11.0 or CUCM 10.0 to 11.5)
RU (Refresh Upgrade): Appliance/Virtual to
Appliance/Virtual model with major Linux version
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)
BRKUCC-2011 47

SU versus RU Upgrade
• Active partition is running while upgrade software is
being install on inactive partition
• Low downtime since upgrade can be done while system
is functioning
SU
Upgrade
• Server is down while upgrade software is being install
• Higher downtime since upgrade cannot be done while
system is functioning
• Upgrade is equal to complete installation of CUCM
RU
Upgrade
Detailed SU and RU upgrade process
are in the appendix
BRKUCC-2011 48

CUCM Upgrade and Reboot Options (SU & RU)
CUCM
Publisher
CUCM
Subscriber
CUCM 12
Upgrade
ISO
Active Partition (CUCM 11)
Inactive Partition (CUCM 10)
CUCM
Publisher
CUCM
Subscriber
1
2
• Upgrade Publisher first
• Reboot options depends on the collaboration product
BRKUCC-2011 49

Reboot Options (preferred)
CUCM
Upgrade Type Switching Type Reboot Options
Standard Upgrade Automatic Switch to new version after upgrade (system reboots)
Manual Do not switch to new version after upgrade (no system
reboots)
Refresh Upgrade Automatic Switch to new version after upgrade (system reboots)
Manual Do not switch to new version after upgrade (no system
reboots)
Unity Connection
Upgrade Type Switching Type Reboot Options
Standard Upgrade Manual Do not switch to new version after upgrade (no system
reboots)
Refresh Upgrade Manual Do not switch to new version after upgrade (no system
reboots)
BRKUCC-2011 50

L2SUSU
RU
CUCM
Version
RHEL Release
5.1(x) & 6.X RHEL 3 Update 8
7.0(1) RHEL 4 Update 4
7.1(3) & 8.0(x) RHEL 4 Update 7
8.5 RHEL 4 Update 8
8.6* RHEL 5 Update 5
9.X RHEL 5 Update 7
12.0(1) CentOS 6
12.5(1) CentOS 7
SU
New
Planned
SU and RU Upgrade Table
CUCM / RHEL
Version X
CUCM / RHEL
Version Y
CUCM / RHEL
Version X
CUCM / CentOS
Version Z
New
BRKUCC-2011 51

SU Cluster Upgrade Sequence for Least
Service Impact
Sequence
SU
1 2 3 4 5 6 7 8
CUCM
Pub
Manual Switch DB Sync DB Sync
CUCM
Primary Subs
Manual
*
Switch DB Sync
CUCM
Secondary
Subs
Manual Switch DB Sync * DB Sync
IM&P
Pub
Manual Switch DB Sync
IM&P
Subs
Reboot Option
*Phone registration using CM Groups and/or disable CM Service on the other CUCM Subs
** Phone registration after upgrade
Reference
BRKUCC-2011 52

RU Cluster Upgrade Sequence for Least
Service Impact
Sequence
RU
1 2 3 4 5 6 7 8 9 10 11
CUCM
Pub
Manual Switch DB Sync DB Sync
CUCM
Primary Subs
*
Manual
**
Switch DB Sync
CUCM
Secondary Subs
Manual * Switch DB Sync * DB Sync
IM&P
Pub
Manual Switch
DB Sync
IM&P
Subs
Manual Switch
DB Sync
Reboot Option
*Phone registration using CM Groups and/or disable CM Service on the other CUCM Subs
** Phone registration after upgrade
Reference
BRKUCC-2011 53

Cluster Upgrade Sequence for Shortest Upgrade Time
Sequence
SU
1 2 3 4 5 6 7
CUCM
Pub
CUCM
Subs
IM&P
Pub
Manual Switch
DB Sync
IM&P
Subs
Sequence
RU
1 2 3 4 5 6 7 8 9
CUCM
Pub
CUCM
Subs
IM&P
Pub
Manual
Switch
DB Sync
IM&P
Subs
Reference
Reference
BRKUCC-2011 54

Minimal Upgrade Duration
Products SU
(hours)
RU
(hours)
Switch
(hours)
DB
Replication *
CUCM
Pub
2-4 3-5 1/2 ½ - 2 or more
CUCM
Subs
1-2 1-2 1/2 ½ - 2 or more
IM&P
Pub
2-4 3-5 1/2 ½ - 2 or more
IM&P
Subs
1-2 1-2 1/2 ½ - 2 or more
Sample Cluster Upgrade
(least impact)
12-15 16-20
• There are many characteristics and specific details that will negatively and excessively impact these
optimal durations especially DB replications. In some cases, it can take many hours especially over
slow WAN link. Clustering over the WAN duration for upgrades are in the appendix
• Use your specific past upgrade baseline
• Potential considerable replication time improvement in CUCM 12.5 for upgrades
Reference
BRKUCC-2011 55

Upgrade Methods and Tools – PCD
Upgrades
Method
Direct
Standard
Upgrade
Direct
Refresh
Upgrade
PCD
Upgrade
PCD
Migrate
DSU
DRU
PCDU
PCDM
Prime Collaboration Deployment
(PCD) Upgrades and Migrations
Unified CM OS Admin Upgrades
Native and embedded tool
External tool
BRKUCC-2011 56

PCD Upgrades and Migrations
Prime
Collaboration
Deployment
U
M
Direct Upgrade (SU and RU)
Migrate existing clusters
• Simple – same network settings (IP addresses and/or
hostnames)
• Network – new network settings (IP addresses and/or
hostnames)
BRKUCC-2011 58

Prime Collaboration Deployment CUCM Capabilities
PCD
CUCM Cluster
CUCM 12
Upgrade ISO
Upgrade Cluster
CUCM Cluster
Migrate Cluster
CUCM Cluster
CUCM Cluster
Restart
CUCM Cluster
Cluster Discovery
CUCM Cluster
Switch Version
CUCM Cluster
CUCM 12
Upgrade ISO
Fresh Install
CUCM Cluster
Readdress
Host1/IP1
Host2/IP2
BRKUCC-2011 59

PCD Capabilities for other Collaboration Applications
IM&P
Unity
Connection
Presence
CUCCX
Reference
BRKUCC-2011 60

PCD 12.0 Environment Requirements
PCD
PCD 12.0
vCPU
2
(2000Mhz)
vRAM 4GB
vDisk 80GB
Guest OS
CentOS 6
(64)
vNIC Adapter VMXNet3
OVA
ESXI Version
4.1
5.0
5.1
5.5
6.0
6.5
ESXI Version ESXI Edition
5.5 • Cisco UC Virtualization Foundation (appears as “Foundation
Edition” in vSphere Client)
• Cisco UC Virtualization Hypervisor Plus 6.0 or higher
• VMware vSphere Standard Edition, Enterprise Edition, or
Enterprise Plus Edition
• Evaluation mode license (for example, for lab deployments and not
production use)
6.0
6.5
BRKUCC-2011 61

PCD Upgrade
CUCM & IM/P Cluster
CUCM 12
Upgrade ISO,
COP files
sftp to /upgrade directory
PCD
Direct Upgrade
StandardUpgrade
RefreshUpgrade
BRKUCC-2011 62

PCD Migrate
PCD
CUCM & IM/P
Cluster
CUCM & IM/P
Cluster
Add Source CUCM Clusters to PCD
Add ESXi hosts to PCD
Migrate
Deploy OVAs
OVA
or
Map Source node to targeted Node
CUCM 12
Bootable ISO
sftp to /fresh_install directory
1
2
3
4
5
5
BRKUCC-2011 63

PCD Assisted Upgrades and Migrations
Prime
Collaboration
Deployment
U
M
Simple Migration: Same network settings (IP
addresses and/or hostnames)
Network Migration: New network settings (IP
addresses and/or hostnames)
PCD Upgrade (Virtual to Virtual)
From CUCM Version Target CUCM Version
8.6(1),8.6(2),9.0.(1),9.1(1),9.1(2),10.0(1),
10.5(1),10.5(2),11.0(1),11.5(1)
10.X, 11.X or 12.0
PCD Migration (Physical to Virtual)
From CUCM Version Target CUCM Version
6.1(5),7.1(3),7.1(5),8.0(1),8.0(2),8.0(3),
8.5(1),8.6(1),8.6(2),9.0.(1),9.1(1),9.1(2)
10.X, 11.X or 12.0
BRKUCC-2011 64

PCD Considerations and Planning
• Cisco UC Virtualization Hypervisor with BE6K and BE7K
• Lab testing with or without NAT feature
• Allow network traffic to and from PCD
• SU/RU upgrade does not automate COP file installation
- ciscocm.version3-keys.cop.sgn
- ciscocm.refresh_upgrade_v1.3.cop.sgn
• Inspect PCD logs via activelog tomcat/logs/ucmap/log4j/ucmap*.log
PCD Administration Guide:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/pcdadmin/11_5_2/cucm_b_pcd-admin-guide-1152.html
BRKUCC-2011 65

CUCM Upgrade COP Files
CUCM YCUCM X
Current Version Target Version COP File Required
<8.5.1.17123-1
<8.6(2)su5
<9.1(2)su1
10.5(1) or higher ciscocm.version3-keys.cop.sgn
8.5(x) or lower 8.6 or higher ciscocm.refresh_upgrade_v1.5.cop.sgn
* Details are in the notes and in the appendix
BRKUCC-2011 67

Virtualized CUCM to Virtualized CUCM 12.0
CUCM 12.0
CUCM 9.X
CUCM 10.X
CUCM 8.6
CUCM 11.X
PCD Upgrade or
Unified CM OS Admin
CUCM
CUCM Version Upgrade Type COP File(s)
8.6 RU ciscocm.version3-keys.cop.sgn (<8.6(2)su5)
9.X RU ciscocm.version3-keys.cop.sgn (<9.1(2)su1)
10.X SU
11.X SU
* Cop file information is in the appendix
BRKUCC-2011 69

Appliance (MCS) to Virtualized CUCM 12.0
CUCM 12.0
• PCD Migration is recommended
• Unified CM OS Admin upgrade will work for some situations
• Access to media
• Server supporting CUCM 8.X or 9.X
CUCM 7.1(3/5)
CUCM 8.X
CUCM 6.1(5)
CUCM 9.X
PCD Migration
CUCM 12.0
CUCM 8.6
CUCM 9.X Unified CM OS Admin
Migrate
BRKUCC-2011 70

CUCM Upgrade Type and Upgrade Method Reference
CUCM on MCS
CUCM Version Upgrade Type Upgrade Method
6.1(5) NA PCD
7.1(3/5) NA PCD
8.X NA PCD
8.6 RU PCD 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
BRKUCC-2011 71

Platform Support and Migration
5

Previous Sessions for UC on UCS Migration
• BRKUCC-1903 - Migration and Co-Existence Strategy for Collaboration
Applications in a Virtualized Environment (2014 San Francisco)
• BRKUCC-1903 - Migration and Co-Existence Strategy for Unified
Communications (UC) or Collaboration Applications on Unified Computing
Systems (UCS) (2013 Orlando)
Reference
BRKUCC-2011 73

Platform Selection and Migration

Appliance to Virtualization Conversion
Unified Communications in a Virtualized Environment” Docwiki
http://www.cisco.com/go/uc-virtualized
Platform
Conversion
CPU Memory NIC Storage
UC App
Server Hardware
VOS
ESXi 4/5/6 Hypervisor
UC App
VOS
UC App
VOS
UC App
VOS
1. Server platform selection
2. VMware ESXi requirements
3. Conversion of appliance to virtual machine or OVA
4. Leverage “Unified Communications in a Virtualized Environment”
Docwiki
1
2
3
BRKUCC-2011 75

Business
Edition 6000
UC on UCS
Less
Less More
More
UC on UCS 3rd-Party
1. Server Platform Selection
Any Server
Business
Edition 7000
Choices
(Leverage Existing Investment)
Assurance
Simplicity
TRC Specs-Based
Packaged Collaboration
Solution
LessMore Ease of Deployment
UC Virtualization Supported Hardware
http://docwiki.cisco.com/wiki/UC_Virtualization_Supported_Hardware#B200_M2_TRC.231
HyperFlex
HX240c M4SX TRC#1
BRKUCC-2011 76

2. VMware Requirements (Sample for CUCM)
vCenter Mandatory for
Spec-based
CUCM Version ESXi Version ESXi Edition
11.X 5.0 U1, 5.1, 5.5, and 6.0 VMware vSphere Hypervisor
Cisco UC Virtualization Hypervisor
VMware vSphere Hypervisor Foundation
Cisco UC Virtualization Foundation, Standard, Enterprise or
Enterprise Plus
10.X 4.0 U4, 4.1 U2, 5.0 U1, 5.1, 5.5, and 6.0
9.1 4.0 U3, 4.1 U1, 5.0, 5.1, 5.5, and 6.0
• Check for specific collaboration application and corresponding VMware version and edition
support
• Upgrade to latest version of ESXi updates, but be mindful of application specific requirements
(e.g. Expressway)
BRKUCC-2011 77

vSphere
Client
CCO
OVA
UCS B200 M4
2
1
Cisco Virtual Template (OVA) File
• Open Virtual Archive (OVA): Portable virtual appliance that defines configuration
(memory, storage space, etc.) for a virtual machine and is a compressed version
of OVF
• Cisco will provide OVA files with Virtual Machine Hardware Version (VMV) 7 and
VMV8 on CCO for collaboration applications deployment
• Deploy the latest OVA version and the highest available VMV version that
matches to ESXi version
BRKUCC-2011 78

vCenter 6.5 and ESXi 6.5 Support
CUCM 12.0 OVA
OVA
ESXI Version vCenter
Version
6.5 6.5
vCenter or Direct
vCenter
Version
ESXI
Version
CSCvc74573 - CUCM, CSCve50781 - IM&P, CSCvd86760 - CER and CSCvd01111 - Finesse
6.5 6.0 • Deploy OVA directly to ESXi 6.0 host with vSphere client (C#) or Web client
• Editing OVA. Link in the notes (Remove "^M" characters and replace "," with "space" in OVA file at
https://cisco.jiveon.com/docs/DOC-1667650)
Workaround for vCenter 6.5 and ESXi 6.0
• New updated OVAs will be posted
on CCO for CUCM 11.5 and 10.5
after CUCM 12.0 is released
BRKUCC-2011 79

Example of ESXI and Collaboration OVA Version
ESXi Version VMware Virtual
Machine Hardware
Version (VMV)
Recommended Cisco
OVA VMV Version
5.0U1 8 8
5.1 9 8
5.5 10 8
6.0 11 8
6.5 13 8
Collaboration
Application
Collaboration
Application Version
VMV Version Cisco
OVA Version
cucm_11.5_vmv8_v1.1.ova
CUCM 11.5 8 1.1
• Use matching collaboration application to OVA file especially with the new
separated ISO files for CUCM and IM&P
– E.g. cucm_11.5_vmv8_v1.1.ova and
Bootable_UCSInstall_UCOS_11.5.1.12900-21.sgn.iso
• VMV can be upgraded, but cannot be downgraded. Keep as high as VMV 8
Virtual Machine Compatibility
http://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.vm_admin.doc%2FGUID-64D4B1C9-CD5D-4C68-8B50-585F6A87EBA0.html
BRKUCC-2011 80

3. Conversion of Appliance to Virtual Machine or OVA
MCS
Server
Model
Maximum
Number
of Phone
OVA
Deployment
Size
vCPU
7845-I3 or
earlier
10000 10000 4
7845-I3 or
earlier
7500 7500 2
7845-I2/H2
or earlier
7500 7500 2
7825-I5 or
earlier
1000 2500 2
7825-I5 or
earlier
1000 1000 2
7816-I5 or
earlier
500 1000 2
7828-I5 or
earlier
500 1000 2
• Smaller MCS server converts to a
standard 2500 device OVA or restricted
performance CPU OVA on CUCMBE 6K
• MCS and C series both has similar direct
attached storage (DAS)
• Storage option for redundancy: FC SAN
Restricted performance CPU (CUCMBE 6K)
OVA
BRKUCC-2011 81

Appliance versus Virtualization Support
Feature Appliance Virtual
Music on Hold (live source) USB audio (unicast and
multicast)
IOS or Barix (multicast only) *
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.
Reference
BRKUCC-2011 82

UCS, VMWare and Collaboration
Operational Support

Dependencies and Support: Applications, ESXi
Version and UCS Firmware/Hardware
• Upgrade of collaboration application might requires ESXi version upgrade
• Upgrade of ESXi version (application or ESXi standardization) might requires
• UCS firmware update (e.g. firmware 3.1(3) on C240M4S2)
• UCS hardware replacement (e.g. C210M2 and ESXi 6.0 or later)
CUCM
Version
ESXi Version
11.X 5.0 U1, 5.1, 5.5, and 6.0
http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_s
ystem/virtualization/virtualization-software-requirements.html
ESXi Version UCS hardware supported/not supported
6.0 C210M2, C210M1
6.0 C240M4S2: firmware 3.1(3)
https://ucshcltool.cloudapps.cisco.com/public/
Collaboration application to
supported version of ESXi
UCS hardware and
supported version of ESXi
BRKUCC-2011 84

VMware OVA Support and Virtual
Machine Migration

CUCM 7,500 Devices OVA Changes
CUCM 7500 8.5 8.6 9 9.1 10.X 11.X 12.0
vCPU 2
(1300Mhz)
2
(3600Mhz)
2
(3600Mhz)
2
(3600Mhz)
2
(3600Mhz)
2
(3600Mhz)
2
(3600Mhz)
vRAM
6GB 6GB 6GB 6GB 6GB 8GB 8GB
vDisk
2 x 80GB 2 x 80GB 2 x 80GB 110GB 110GB 110GB 110GB
Guest OS
RHEL 4 (32) RHEL 4 (32) RHEL 5 (32) RHEL 5 (32) RHEL 6 (64) RHEL 6 (64) CentOS 6 (64)
vNIC Adapter
Flexible Flexible Flexible Flexible VMXNet3 VMXNet3 VMXNet3
VMware
Tool/Advance
No No No No
Check and
upgrade Tools
Check and
upgrade Tools
Check and
upgrade Tools
• Shutdown virtual machine (vm) and apply changes BEFORE upgrade
• vCPU: Change “Reservation” values (Resources)
• vRAM: Change “Reservation” values (Resources)
• vDisk: Change “Provisioned Size” (Resources)
• vNIC: Change vNIC type. Instruction in the appendix and in README files
• Guest Operating System (OS): Change Guest OS and Version (Option)
optional
Reference
BRKUCC-2011 86

CUCM 10,000 Devices OVA Changes
CUCM 10000 8.6 9 9.1 10 11 12
vCPU 4
(7200Mhz)
4
(7200 Mhz)
4
(7200Mhz)
4
(7200Mhz)
4
(7200Mhz)
4
(7200Mhz)
vRAM
6GB 6GB 6GB 6GB 8GB 8GB
vDisk
2 x 80GB 2 x 80GB 110GB 110GB 110GB 110GB
Guest OS
RHEL 4 (32) RHEL 5 (32) RHEL 5 (32) RHEL 6 (64) RHEL 6 (64) CentOS 6 (64)
vNIC Adapter
Flexible Flexible Flexible VMXNet3 VMXNet3 VMXNet3
VMware
Tool/Advance
No No No
Check and
upgrade Tools
Check and
upgrade Tools
Check and
upgrade Tools
optional
Reference
• Shutdown virtual machine (vm) and apply changes BEFORE upgrade
• vCPU: Change “Reservation” values (Resources)
• vRAM: Change “Reservation” values (Resources)
• vDisk: Change “Provisioned Size” (Resources)
• vNIC: Change vNIC type. Instruction in the appendix and in README files
• Guest Operating System (OS): Change Guest OS and Version (Option)
BRKUCC-2011 87

Clarifications
• OVA with dual 80GB vDisk is supported with CUCM 9.X, 10.X, 11.X and 12.0
• Secondary vDisk on OVA with dual 80GB vDisk has the /common partition and can be
extended at release CUCM 10.0 and later for upgrade space
• Primary vDisk on OVA with dual 80GB vDisk are partitioned with various disk partitions
with respective sizes and cannot be resized to 110GB to match with the newer OVA
• Resize Virtual Machine
http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/virtuali
zation-software-requirements.html#resize_vm
• To change OVA that from dual 80GB vDisk to single 110GB vDisk
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/install/11_5_1/replace/cucm_
b_replacing-single-server-or-cluster-1151.html
BRKUCC-2011 88

CUCM 11 to CUCM 12.X Guest OS Change
Features CUCM 11.X CUCM 12.X
Guest OS RHEL 6
(64bit)
CentOS 6/7 (64)
• Shutdown CUCM
• Change the Guest OS from RHEL 6 (64 bit) to CentOS 4/5/6/7 (64 bit)
– ESXi 5.5 only has CentOS 4/5/6 and might need another change at CUCM 12.5
– Should be done before CUCM upgrade
• Upgrade to CUCM 12.X
BRKUCC-2011 89

CUCM 9 to CUCM 10/11/12 Adapter Change
Features CUCM 9.X CUCM 10.X/11.X/12.X
Guest OS 5 (32bit) RHEL 6 (64 bit)/CentOS 6
Adapter Type Flexible VMXNet3
• Update to the latest VMtools if not auto upgrade
• Shutdown CUCM
• Change Network adapter type from Flexible to VMXNET3
– Automatic MAC: Edit VMX file in the VM machine directory. Instruction in link below
– VMware vSphere PowerCLI for both automatic and manual MAC. Instruction in link
below
– Sample Powershell script in Appendix
• Upgrade CUCM
CUCM 10.0 OVA:
http://www.cisco.com/web/software/283088407/108296/cucm_10.0_vmv8_v1.7.ova.README.txt
Reference
BRKUCC-2011 90

VMware Tools Update
Reference
CUCM
Version
Options > VMware
Tools > Advance
8.X and 9.X Not checked
CUCM Version VMware Tools
10.0, 10.5 or 11.0 10.0.0 or higher
(ESXi 5.5EP9 or 6.0EP05)
https://packages.vmware.com/tools/versions
CSCux90747 and CSCuz50894
Options
Upgrade to 10.5(2)SU4, 11.0(1)SU3, 11.5(1) or higher
Install VMwareTools2016c COP File (ciscocm.VMwareTools2016c.cop.sgn)
BRKUCC-2011 91

System Preparation and Optimizing
Upgrade Speed for CUCM Upgrade
6

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

CUCM 12.0 AND 11.5 Deprecation Phone Models
• Field Notice
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/12_0_1/depre
cated_phones/cucm_b_deprecated-phone-models-for-
1201.html?emailclick=CNSemail
• Phones (17 models) will not be able to register to CUCM 12.0
• Check phone models for support and migrate IP phones using Endpoint Refresh
Tool - Migration FX before upgrading to CUCM 11.5
• Free Migration FX software for 1 years with a Cisco TMP of 100 78XX/88XX IP phones
(L-CP-MGFX-PROMO=)
• Free Trial Version of MigrationFX (up to 50 phones) from UnifiedFX
Endpoint Refresh Tool - Migration FX
http://refreshcollab.cisco.com/webportal/66/Endpoint%20Refresh%20Tool 3
BRKUCC-2011 95

Disk Space Required in /common
Partition for Upgrade

Disk Space for Upgrade
• Reduce log files:
• LogPartitionLowWaterMarkExceeded 30% (default 80%)
• LogPartitionHighWaterMarkExceeded 40% (default 85%)
• Delete old ATS & RIS Database Aborted Transaction logs
• file delete activelog cm/log/informix/ats/* noconfirm
• file delete inactivelog cm/log/informix/ats/* noconfirm
CUCM 12
Upgrade ISO
/common
partition
25GB Required
CUCM Version ESXi Version
10.X or later Resize vDisk (2nd vDisk if 2 X 80GB)
8.5(1), 8.6(2), 9.1(1),
9.1(2)
ciscocm.vmware-disk-size-reallocation-1.0.cop.sgn
Extending vDisk Space
CUCM Version ESXi Version
All CUCM Versions Reduce log files
9.1 and earlier ciscocm.free_common_space_v1.3.k3.cop.sgn
Deleting files
BRKUCC-2011 97

Improve Upgrade Performance
• Change TFTP service parameter for dedicated TFTP server on CUCM 5.1(1c) or
later:
• System > Service Parameter > Cisco TFTP (Advance)
• Maximum Serving Count (default is 500)
• 1,500 for single processor dedicated TFTP server and 3,000 for dual processors
dedicated TFTP server
• Increase database replication parallel processing count (Publisher)
• utils dbreplication setprocess 40 (default is 1)
• Increase database replication timeout for large cluster (Publisher)
• utils dbreplication setrepltimeout <3600> (default is 300)
• Range is 300 to 3600
BRKUCC-2011 99

Upgrade Optimization: Replication Time
Improvement – Previously Best Practices
• Disabling provisioning during upgrade. Previously
are best practices for upgrade in previous version
• Disable EM service in CUCM 9 and earlier not included
• IBM IDS new feature implementation for
transmitting files in bulk
• Sync Agent sync time optimization
Replication
Blocked
configuration
changes
Error and Warning Messages
AXL 503 error response: “Write Operations
denied because Cisco UCM or IM and
Presence upgrade is in progress.”
BAT Error message "Upgrade in Progress.
Job cannot be started"
LDAP Sync. "Upgrade in progress. Cannot be
synced"
Self Care Portal WARNING: Add/Update/Delete not
allow as a system upgrade is in
progress
UDS 503 error response
CM Admin MACD Banner and Status
CCM Service
Activation/Trace
Update failed
Add/Update/Delete not allow as a
system upgrade is in progress
Phone auto-
registration and
Self Provisioning
Auto-registration disabled/IVR return
error
Replication time
as a function of
bandwidth
DB changes that
impacts replication
time
BRKUCC-2011 100

Upgrade Execution and CUCM
Registration with Smart Licensing
7

Execution in Phases: Minimizing Upgrade Window
CUCM
Upgrade
3
UC Applications
Upgrade
Phase II:
IP Phone
Firmware Upgrade
Phase IV:
UC Applications Pre-
Upgrade Migration
Phase VI:
CUCM and UC
Applications Post
Upgrade Migration
Replacement
UC Applications
Upgrade
4 5
• 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
applications and firmware compatibility
2Phase I:
Owner User ID / phone
association and
license request
1
IP Phone
Firmware
Phase III:
Proactive
Replacement
6Phase V:
Prepare CUCM for
Upgrade
Apply COP files
BRKUCC-2011 102

CUCM Smart Licensing Overview
• Smart Licensing is enabled by default on CUCM 12.0 and later
• Evaluation mode 90 days with full capacity
• 90 days evaluation timer counts down when CUCM starts to consume licenses
regardless if register or unregister to Cisco Smart Software Manager (CSSM) or
Smart Software Manager satellite server
BRKUCC-2011 104

CUCM Smart License Management - Status
(System > Licensing > License Management)
Smart Software Licensing (Smart Agent)
Registration
Status
• Unidentified/Unregistered
• Registered
• Unregistered-Registration
Expired
License Authorization
Status
• No licenses in use
• Evaluation Mode
• Evaluation expired
• Authorized
• Out of compliance
• Authorization Expired
• Smart Software Licensing of CUCM is the status of the Smart Agent
communication to Cisco Smart Software Manager (CSSM)
• Status of CUCM license can be seen in the Status section or CUCM banner
BRKUCC-2011 105

Smart Licensing States in CUCM
Registration Status Authorization Status Evaluation Period
(90 days)
Overage Period (90
days)
Enforcement (No MACD)
Unregistered or
Registration Expired
Evaluation Mode Start with 90 and
will decrement if
UCM is consuming
licenses
NA No
Unregistered or
Evaluation Expired 0 days NA Yes
Registered or
Unregistered or
No Licenses in Use NA NA No
Registered Authorized NA NA No
Registered OOC NA Overage period
remaining
No till overage period is applicable
Yes after overage days(90 days) are over
Registered Authorization Expired NA Overage period
remaining
No till overage period is applicable
Yes after overage days(90 days) are over
* CUCM Smart License banner status in the slide notes
Reference
BRKUCC-2011 106

Direct CUCM Smart Licensing Registration
Cisco
Smart
Software
Manager
(CSSM)
cisco.com
Log into CSSM
• software.cisco.com > Smart Software Licensing
> Inventory > General
• Select the appropriate Smart Account and
Virtual Account
Registration
Token from
CSSM
• Copy existing Product Instance Registration
Token or
• Create New Token
• Copy or download token
Register CUCM
• System > License Management > Register
• Direct or HTTP/HTTPS Proxy transport setting
• Paste token and register
Reference
BRKUCC-2011 107

Transport Settings for CUCM for Smart Licensing
• Set communication between CUCM Publisher and CSSM or Smart Software
Manager satellite server
• Smart License Deployment Model
• Direct: Direct cloud access
• Transport Gateway: Mediated access through an on premise collector (Smart Software
Manager satellite)
• HTTP/HTTPS Proxy: Direct cloud access through an HTTPs proxy
BRKUCC-2011 108

Registering CUCM with Smart Licensing
Smart Software Central > Smart Software Licensing > Inventory > General System > Licensing > License Management
• Create or copy existing registration token from CSSM or Smart Software
Manager satellite server to CUCM
BRKUCC-2011 109

System Level Planning
License Management
Upgrade/Migration
Methods and
Tools
Platform
System
Preparation
Optimizing
Upgrade Speed
Execution
Smart Licensing
Smart Account
License Conversion
License Optimization
EOL <9..0 License
DSU
DRU
PCDU
PCDM
Servers
Virtualization
Virtualized CUCM
VMware changes
Deprecated phones
Disk Space
COP file(s)
Change freeze
MACD
Pre-Upgrade list
(in documentation)
TFTP server
DB replication
Purge CDR
Phone firmware
Application
dependencies
Upgrade windows
Smart Registration
Post-Upgrade list
(in documentation)
BRKUCC-2011 110

Upgrade Tasks
• Pre-Upgrade Task
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/11_5_1/cucm_
b_upgrade-guide-cucm-115/cucm_b_upgrade-guide-cucm-
115_chapter_010001.html
• Post-Upgrade Task List
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/11_5_1/cucm_
b_upgrade-guide-cucm-115/cucm_b_upgrade-guide-cucm-115_chapter_01000.html
Reference
BRKUCC-2011 111

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
BRKUCC-2011 112

AS
BRKUCC-
2011
(Participants)
Call Control
TigerTeam
SVS Lab
TAC
Engineering
Thank You!
• Revised Upgrade and Migration Guide
for Cisco Unified Communications
Manager and IM and Presence Service
Document on CCO
• Upgrade Simplification Initiative (James
Arias)
• AS
• BRKUCC-2011 Content (Participants)
• Call Control Tiger Team
• Engineering
• SVS Lab
• TAC
BRKUCC-2011 113

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
BRKUCC-2011 115

Reference links
• Unified Communications Licensing Availability by Release
https://communities.cisco.com/docs/DOC-57172
Reference
BRKUCC-2011 116

• Give us your feedback to be
entered into a Daily Survey
Drawing. A daily winner will
receive a $750 gift card.
• Complete your session surveys
through the Cisco Live mobile
app or on www.CiscoLive.com/us.
Complete Your Online
Session Evaluation
Don’t forget: Cisco Live sessions will be
available for viewing on demand after the
event at www.CiscoLive.com/Online.

Continue Your Education
• Demos in the Cisco campus
• Walk-in Self-Paced Labs
• Lunch & Learn
• Meet the Engineer 1:1 meetings
• Related sessions
BRKUCC-2011 119

Please join us for the Service Provider Innovation Talk featuring:
Yvette Kanouff | Senior Vice President and General Manager, SP Business
Joe Cozzolino | Senior Vice President, Cisco Services
Thursday, July 14th, 2016
11:30 am - 12:30 pm, In the Oceanside A room
What to expect from this innovation talk
• Insights on market trends and forecasts
• Preview of key technologies and capabilities
• Innovative demonstrations of the latest and greatest products
• Better understanding of how Cisco can help you succeed
Register to attend the session live now or
watch the broadcast on cisco.com

Appendix
• W1 Upgrade
• Bridge Upgrade
• Jump Upgrade
• License Acquisition
• L2 and RU Upgrade in Detail
• CDetailed 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
• CUCM-BE5K Migration
• PCD Migration from MCS to Virtualized
• RSA 3 signed cop file and CUCM 10.0 RSA 2/3
• Phone Deprecation Screen Captures

Appendix
• Upgrade over WAN (COW – Cluster Over the WAN)
• CUCM 11.5 Scale Improvements
• LCT (License Count Utility)
• CUCM License Types
• PLM

W1 Upgrade: Windows to Appliance Model
Existing
CUCM 4.X
Cluster
Back Up
With
BARS
Tape or
Network
Share
Upload
DMA
File
CUCM
7.X
DVD Kit
Tape, FTP
or sFTP
Server
Install
CUCM
7.1
Node, DLU and
7.1 Feature SW
License
Upload
Licenses
Download
From CCO
1 2 3 5 64
New CUCM
7.1 Cluster
Existing
CUCM 4.X
Cluster
Install
and Run
Upgrade
Utility on All
Servers
Latest
Upgrade
Utility From
CCO
Save DMA File
to Tape or
Network Share
Existing
CUCM 4.X
Cluster
Install,
Run, and
Download
DMA from
Publisher
Data Migration
Assistant
(DMA) 7.1
New CUCM
7.1 Cluster
New CUCM
7.1 Cluster
 CUCM 7.1
software
availability can
be an issue
since CUCM
7.1 has EOS
(End of Sales)
BRKUCC-2011 127

CUCM Migration Definition
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 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)
Jump
Bridge
BRKUCC-2011 128

Bridge Upgrade
DRS
Secure FTP
Server
Servers supported to run
CUCM version X
Upgrade
Servers supported to
be in Bridge mode on
CUCM version Y
DRS
File
DRS
Virtualized CUCM
• 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
BRKUCC-2011 129

Jump Upgrade
Servers that cannot run
CUCM 8.0(2) or later to
virtualized
Virtualized CUCM
9.1(2)
• 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
BRKUCC-2011 130

Jump Upgrade Process
DRS
Backup
sFTP
Server
CUCM
6.x or
7.X ISO
Image
Build
same
CUCM
version
Upgrade
to CUCM
9.1(2)
1 52 3 4
CUCM 6.X
or 7.X on
MCS
New
virtualized
CUCM 6.X
or 7.X
New
virtualized
CUCM 6.X
or 7.X
DRS
Restore
sFTP
Server
Upgraded
virtualized
CUCM
9.1(2)
New
virtualized
CUCM
9.1(2)
Build new
CUCM
9.1(2)
CUCM
9.1(2)
ISO
Image
CUCM
9.1(2)
ISO
Image
DRS
Backup
sFTP
Server
Upgraded
virtualized
CUCM
9.1(2)
6 7
New
virtualized
CUCM
9.1(2)
DRS
Restore
sFTP
Server
LAB
To
Production
Disk
Alignment
BRKUCC-2011 131

License Acquisition with CUCM 5.X to 8.X
 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
Contract Number
Node
License
SW Feature
License
Upgraded
CUCM cluster
Product Upgrade
Tool Site
Device
License Unit
New CUCM
cluster
Product License
Registration Site
Product
Activation Key
UPGRADE
NEW
BRKUCC-2011 132

L2 Upgrade: Appliance to Appliance Model
 Active partition is running while upgrade software is being install on inactive
partition
 Low downtime since upgrade can be done while system is functioning
InActive partition
Active Partition Running
1.RPMs
installation
2.CUCM
installation
3.DB
installation
4.Data
Migration
Reboot
InActive partition
Active Partition
Dormant
1. Firmware and
BIOS upgrade
2.Post reboot
software
installation
BRKUCC-2011 133

Refresh Upgrade (RU): Appliance to Appliance
Model
 Server is down while upgrade software is being install
 More reboots
 Higher downtime since upgrade cannot be done while
system is functioning
 Upgrade is equal to complete installation of CUCM
InActive partition
Active Partition Running
1. Data
exported
(CUCM and
CAR) into
/common
partition
Reboot
InActive partition
Active Partition
Dormant
1. Firmware
and BIOS
upgrade
2.VOS
installation
3. Platform
import
Reboot
InActive partition
Active Partition
Dormant
1. CUCM
installation
2. DB
installation
3. CUCM data
import
4.CAR DB
creation
5.CAR DB
migration
BRKUCC-2011 134

Cisco Unified Enterprise License Manager
 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
ELM
First node of
CUCMCUC
1
Add CUCM or
CUC systems Register
Success/Fail
Get License Usage – 24 hours
Usage X,Y,Z
Set License Status
Analyze CUCM EnforcementCUC Enforcement
4
5 5
2
3
Get License Capability
6 Grant
How and what do CUC, CUCM and ELM
communicate?
BRKUCC-2011 135

Process of CUCM and ELM Communications
 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
3
How does CUC, CUCM and ELM know
what to communicate?
CUCM License Evaluation ELM License Evaluation
1 2
4
[VALID or INVALID ]
BRKUCC-2011 136

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
BRKUCC-2011 137

License Conversion
A La
Carte
DLU
UCL
0-6
DLU
CUWL
2-17
DLU
Pool of
DLUs
Manual
1
Automated
2
How many
of what
type of
licenses
do I have?
How can I
migrate
these
license?
 For CUCM, CUC included with CUWL or standalone CUC
 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:
 Standalone CUC
 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
BRKUCC-2011 138

License Count Utility (UCT) for CUCM 6.X-8.X
License
Count Tool
CUCM 6.X
CUCM 7.X
CUCM 8.X
 Available on CCO
 Perform AXL calls to existing CUCM clusters for licensing
information, recommends CUCM 9.X license usage, provides
option for unused DLU to CUCM 9.X license and generate
report.
Detailed screen capture of UCT are in
the appendix
BRKUCC-2011 139

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
BRKUCC-2011 140

2. Automated License Migration with ELM
 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
Contract Number CUCM 9.X
software
Upgrade
CUCM cluster
Product Upgrade
Tool site
BRKUCC-2011 141

2. Automated License Migration with ELM
 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
New upgraded
CUC 9.X
Product License
Registration siteELM
Text from ELM
License Request
ELM
License file
CUCM License
Request
1
2
3
BRKUCC-2011 142

Overview of CUCM 9.1 Installation
Upgrade During
Installation
i.e., 9.1(1a) to 9.1(2)
CUCM
9.X DVD KIT
MCS-781X
MCS7825
MCS7828
MCS7835
MCS7845
INSTALLATION PROCESS (PROCEED)
ApplySR,ESorSU
New Installation, New
Server—Flash Cut or
New Server—Migration
BasicInstall
21
BRKUCC-2011 143

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
BRKUCC-2011 144

CUCM 9.X Phone LicenseLicense 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
Phone, ATA186, ATA187
1 EM, SNR
Enhance UCL 12S, 12SP, 12SP+, 30SP+, 30VIP, 3911, 3951, 6941,
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
1 EM, SNR
Enhance UCL Plus Same as Enhance UCL 2 EM, SNR
BRKUCC-2011 145

CUCM 9.X Phone License
License Phone Type (2) # of Devices (3) Features (1)
CUWL Standard 12S, 12SP, 12SP+, 30SP+, 30VIP, 3911, 3951, 6941,
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
10 EM, SNR
TelePresence TelePresence 1
BRKUCC-2011 146

UCL Essential
UCL Basic
UCL Enhanced / Enhanced Plus
CUWL Standard
CUWL Professional
Analog
3905 6901
6921
6911
Fax
TelePresence
Room
MX / Profile Series
System Codecs and
Quickset Platforms
99xx
89xx
792x
Jabber Mobile
Third Party
SIPEX60 / EX90
7937 / 8831
TX / CTS / T Series
79xx
DX650
69xx
Jabber Desktop
78xx
7821
CUCM 10.0 Licensing Summary Cont.
BRKUCC-2011 147

Enterprise License Manager (ELM)
• ELM is a centralized enterprise-wide license management solution for Cisco
collaboration applications
- CUCM
- Cisco Unity Connection (CUC)
• 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)
ELM + CUCM
ELM + CUC
ELM
Bootable
CUCM 9.X
ELM Implementation Products
Standalone ELM
Co-resident with CUCM ELM + CUCM
Co-resident with CUC ELM + CUC
148
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
BRKUCC-2011 148

License Manager Architecture 9.X and 10.X
• 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
License
Manager
API
First Node of
CUCM Cluster 1
ELM / PLM
ELM / PLM
License file
License
Manager
API
License
Manager
API
First
node of
CUC 2
License
Manager
API
First
node of
CUC 1
First Node of
CUCM Cluster 2
License
Manager
API
CER
CER 1
BRKUCC-2011 149

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/
BRKUCC-2011 150

License Management Models with PLM
• 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
CUCM cluster
License
Management
CUCM cluster
License
Management
CUCM cluster
CUCM cluster
ELM Stand Alone
DISTRIBUTED CENTRALIZED
BRKUCC-2011 151

• 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
MCS-7825 H3/H4
MCS-7825-I3/I4/I5
MCS-7828-H3
MCS-7828-I3/I4/I5
RU
MCS-7825 H3/H4
MCS-7825-I3/I4/I5
MCS-7828-H3
MCS-7828-I3/I4/I5
Refresh Upgrade (RU) for MCS 7825 and
MCS 7828 (CUCM 8.6 & 9.X Upgrade)
Reference
BRKUCC-2011 152

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
Change
Changing servers platform. Typically from bare metal servers to virtualized
environment
Automated Platform
Change w/ PCD
BRKUCC-2011 154

In-Place L2 Upgrade Process
Existing
CUCM
Cluster
Back Up
With DRS
sFTP
Server
CUCM
9.X
DVD Kit
Upgrade
Publisher
Inactive
Partition
CUCM
9.X
DVD Kit
Upgrade
Subscribers
Inactive
Partition
Add
License to
ELM and
add
CUCM to
ELM
Switch
Partition
on
Publisher
1 62 3 4 5
New CUCM
9.X Cluster
Switch
Partition
on
Subscriber
New CUCM
9.X Cluster
Existing
CUCM
Cluster
Existing
CUCM
Cluster
ELM
• Version 9 of license
manager is
Enterprise License
Manager (ELM)
• ELM license is
required only when
going from 8.X or
earlier to 9.X
• This scenario
applies to both bare
metal and
virtualized CUCM
CLI or
OS Admin
CLI or
OS Admin
BRKUCC-2011 155

In-Place RU Upgrade Process
Existing
CUCM
Cluster
Back Up
With DRS
sFTP
Server
CUCM
9.X
DVD Kit
Upgrade
Publisher
Inactive
Partition
CUCM
9.X
DVD Kit
Upgrade
Subscribers
Inactive
Partition
Add
License to
ELM and
add
CUCM to
ELM
CLI or
OS Admin
Switch
Partition
on
Publisher
1 62 43 5
New CUCM
9.X Cluster
CLI or
OS Admin
Switch
Partition
on
Subscriber
New CUCM
9.X Cluster
Existing
CUCM
Cluster
Existing
CUCM
Cluster
ELM
manager is
Enterprise License
Manager (ELM)
• ELM license is
required only when
going from 8.X or
earlier to 9.X
• This scenario
applies to both bare
metal and
virtualized CUCM
BRKUCC-2011 156

In-Place L2 Upgrade Process
Existing
CUCM
Cluster
Back Up
With DRS
sFTP
Server
CUCM
10.X
ISO file
Upgrade
Publisher
Inactive
Partition
CUCM
10.X
ISO File
Upgrade
Subscribers
Inactive
Partition
Add
License to
PLM and
add
CUCM to
PLM
CLI or
OS Admin
Switch
Partition
on
Publisher
1 62 3 4 5
New CUCM
10.X Cluster
CLI or
OS Admin
Switch
Partition
on
Subscriber
New CUCM
10.X Cluster
Existing
CUCM
Cluster
Existing
CUCM
Cluster
PLM
manager is Prime
License Manager
(PLM)
• PLM license is
required only when
going from 9.X or
earlier to 10.X
• This scenario applies
to virtualized CUCM
only
• For 10.X to 10.5,
upgrade IM&P after
CUCM cluster is
upgraded
BRKUCC-2011 157

Existing
CUCM
Cluster
Back Up
With DRS
sFTP
Server
CUCM
10.X
ISO file
Upgrade
Publisher
Inactive
Partition
CUCM
10.X
ISO File
Upgrade
Subscribers
Inactive
Partition
Add
License to
PLM and
add
CUCM to
PLM
CLI or
OS Admin
Switch
Partition
on
Publisher
1 62 43 5
New CUCM
10.X Cluster
CLI or
OS Admin
Switch
Partition
on
Subscriber
New CUCM
10.X Cluster
Existing
CUCM
Cluster
Existing
CUCM
Cluster
PLM
manager is Prime
License Manager
(PLM)
• PLM license is
required only when
going from 9.X or
earlier to 10.X
to virtualized CUCM
only
• For 9.X to 10.X,
upgrade IM&P after
CUCM cluster is
upgraded
BRKUCC-2011 158

Existing
CUCM
Cluster
Back Up
With DRS
sFTP
Server
CUCM
11.X
ISO file
Upgrade
Publisher
Inactive
Partition
CUCM
11.X
ISO File
Upgrade
Subscribers
Inactive
Partition
Add
License to
PLM and
add
CUCM to
PLM
CLI or
OS Admin
Switch
Partition
on
Publisher
1 62 43 5
New CUCM
11.X Cluster
CLI or
OS Admin
Switch
Partition
on
Subscriber
New CUCM
11.X Cluster
Existing
CUCM
Cluster
Existing
CUCM
Cluster
PLM
• Add version 11 of
license for the
appropriate ELM or
PLM
• For 9.X to 11.X,
upgrade IM&P after
CUCM cluster is
upgraded
to virtualized CUCM
only
BRKUCC-2011 159

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
BRKUCC-2011 160

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
filePre-Upgrade COP File
http://software.cisco.com/download/release.html?mdfid=284603137&flowid=47762&softwareid=282204704&release=COP-Files&relind=AVAILABLE&rellifecycle=&reltype=latest
BRKUCC-2011 161

2. Automated Platform Conversion with PCD
CUCM on
MCS
Virtualized
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
PCD
BRKUCC-2011 162

CUCM-BE 5K to CUCM-BE 6K or CUCM/CUC
• 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
CUCM-BE 5K
BAT Export BAT Data
Virtualized CUCM
and CUC 10.5
BAT Import
COBRAS ImportCOBRAS
Export COBRAS Data
Migration CUCM-BE 5K to CUCM-BE 6K:
BRKUCC-2011 163

 CUCM Bootable ISO provided to ESXi Hosts via
NFS service running on PCD
 Migration (M1) Steps
1. Add Source CUCM Clusters to PCD
Inventory
2. Add ESXi Hosts to PCD Inventory
3. Add CUCM Bootable ISOs to PCD SFTP
Server (adminsftp user / fresh_install folder)
4. Deploy Empty CUCM VM on ESXi Hosts via
OVA
5. Map Physical Nodes to Virtual VMs and
Schedule Migration Tasks
CUCM 6.X
CUCM 7.X
CUCM 8.X
PCD
1
2
ESXi
Host
4
3
Automated Platform Conversion with PCD
Create
CUCM
VMs via
OVA
5
BRKUCC-2011 164

PCD Inventory Source Cluster Discovery
• First we need to
Discover the Source
CUCM 7.1(5) Cluster
Reference
BRKUCC-2011 165

PCD Inventory Source Cluster Discovery – Step 1Reference
BRKUCC-2011 166

PCD Inventory Source Cluster Discovery – Step 2
Installs these COP Files
• ciscocm.ucmap_platformconfig.cop
• ciscocm.migrate-export-v1.13.cop
Reference
BRKUCC-2011 167

PCD Inventory Source Cluster Discovery – Step 3
• This Step can be skipped
• Not Required for Migration Job
Reference
BRKUCC-2011 168

PCD Inventory ESXi Hosts
Reference
BRKUCC-2011 169

PCD Inventory Add ESXi Hosts
Reference
BRKUCC-2011 170

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
BRKUCC-2011 171

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
Reference
172

PCD Inventory Define Destination Cluster
Reference
BRKUCC-2011 173

PCD Inventory Define Destination Cluster – Step 1
Reference
BRKUCC-2011 174

Reference
BRKUCC-2011 175

PCD Inventory Configure Destination Cluster
Reference
BRKUCC-2011 176

PCD Inventory Configure Destination Cluster
Reference
BRKUCC-2011 177

Reference
BRKUCC-2011 178

Reference
BRKUCC-2011 179

Reference
Must Use DNS on
destination if Source Cluster
is Already Enabled to Use
DNS
No Option to
Remove DNS on
Destination
BRKUCC-2011 180

Reference
BRKUCC-2011 181

Reference
BRKUCC-2011 182

PCD Add Migration Task
Reference
BRKUCC-2011 183

PCD Add Migration Task – Step 1
Reference
BRKUCC-2011 184

Reference
BRKUCC-2011 185

Reference
BRKUCC-2011 186

• By Default Migration is
Fully Serialized
• Delete Steps 6 - 14
Reference
BRKUCC-2011 187

Reference
BRKUCC-2011 188

• Click the Pencil for Step 3
• Add the half the subscribers
Reference
BRKUCC-2011 189

• Click the Pencil for Step 4
• Add the rest of the subscribers
Reference
BRKUCC-2011 190

Reference
BRKUCC-2011 191

CUCM and RSA (Rivest Shamir Adleman) Version
CUCM Build RSA Version
< 8.5.1.17123-1 RSA v2
< 8.6.2.24122-1 RSA v2
< 9.1.2.11018-1 RSA v2
10.X RSA v2 and v3
11.X RSA v3
CUCM RSA
Version
CUCM Build Signed RSA Version
5.0(4) – 10.0(X) RSA v2
10.5(1) or higher RSA v3
ciscocm.free_common_space_v1.1.k3.cop.sgn
Third party COP files need RSA v3 signature
RSA Signed
Files
ISO
COP
(sgn)
file
RSA version of ISO or COP file(s) have match what CUCM supports
Only RSA v3 files can be added to CUCM 11.X and later
BRKUCC-2011 192

CUCM and ISO/COP Files
CUCM 9.1(2)
ciscocm.version3-keys.cop CUCM 11.5
ISO
COP
(sgn)
file
CUCM accepts RSA v2
CUCM 11.5 ISO is RSA v3CUCM accepts RSA v3
✔
CUCM 9.1(2)
ISO
CUCM accepts RSA v2
CUCM 10.0 ISO is RSA v2
✔
CUCM 10.0
CUCM 10.0
CUCM accepts RSA v2 /v3
✔
CUCM 11.5
ISO
CUCM 11.5 ISO is RSA v3
CUCM 11.5
COP
(sgn)
fileCUCM accepts RSA v3
X
CUCM accepts RSA v3
COP file is RSA v3
ciscocm.free_common_space_v1.0.cop.sgn
COP
(sgn)
file
ciscocm.free_common_space_v1.3.k3.cop.sgn
COP file is RSA v2
COP file is RSA v3
✔
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 193

Sample PowerShell Script to update CUCM 10.0
Virtual Machines
### Remember to Shutdown your CUCMs first ###
$vCenter = ”vcenter1.cisco.com"
$vFolder = ”UCM10"
Get-vc -server $vCenter
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
$folder = Get-Folder $vFolder | Get-View
Get-View -SearchRoot $folder.MoRef -ViewType VirtualMachine | %{$_.reload()}
## Alernatively one CUCM VM at a time
Get-VM -Name ”cucm1" | Set-VM -GuestID "rhel6_64Guest" -confirm:$false
Get-VM -Name ”cucm1" | get-networkadapter | set-networkadapter -type "vmxnet3" -confirm:$false
Get-View -ViewType VirtualMachine -Filter @{"Name" = ”cucm1"} | %{$_.reload()}
BRKUCC-2011 194

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###
$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
$myVirtualPortGroup = Get-VirtualPortGroup -VirtualSwitch "uc-cseries" -name $vmNames[$vmName][2]
Set-NetworkAdapter -NetworkAdapter $myNetworkAdapter -Portgroup $myVirtualPortGroup -Confirm:$false
}
Echo Done
BRKUCC-2011 195

VMware Tools 10 and CUCM 10.5(X) and 11.0(X)
• Bug CSCux90747. VMware tool version 10 and CUCM 10.5(1) - 10.5(2)SU3 cause Active
partition to be full and potential CUCM server to crash
• ESXi 5.5 and ESXi 6.0 VMware tool version for specific versions of ESXi 5.5 and 6.0
– https://packages.vmware.com/tools/versions
• CUCM 8 and 9 OVA do NOT have the “Automatic Tools Upgrade” enabled “
• CUCM 10 and 11 OVA have the “Automatic Tools Upgrade” enabled “
• In EXSi 5.5 and 6.0 with CUCM 10.X and 11,X, VMware tools might be in “shutdown” state
• Workaround to install VMare tools version will install the VMware tools and if version 10,
then create the logging issue into the Active partition which will result in Active partition
being full
BRKUCC-2011 196

VMware Tools and CUCM 10.X
ciscocm.VMwareTools2016a.cop.sgn COP File
https://software.cisco.com/download/release.html?mdfid=285963825&softwareid=282204704&release=COP-Files&relind=AVAILABLE&rellifecycle=&reltype=latest
• Recommend to disable the “Automatic Tools Upgrade” when running CUCM 10.5 with build
of ESXi 5.5 or 6.0 that have VMware tools 10.0, unless following the recommendation
below.
Current CUCM version with VMware tool 10 Recommendation
10.5(X) Upgrade to 10.5(2)SU3a
10.5(2) – 10.5(2)SU3 Install COP file or upgrade to 10.5(2)SU3a
11.0(1) – 11.0(1a)SU1 Upgrade to 11.0(1a)SU2 or 11.5(1)
BRKUCC-2011 197

CUCM 11.5 Deprecation Phone Models
Endpoint Refresh Tool - Migration FX
http://refreshcollab.cisco.com/webportal/66/Endpoint%20Refresh%20Tool 3
Upgrade
to 11.5
After
Upgrade
BRKUCC-2011 198

CUCM 11.5 Deprecation Phone Models
Add
device
in11.5
BRKUCC-2011 199

Unified CM Upgrade Consideration
 Clustering over the WAN (COW)
can increase time for installation,
upgrade and database (DB)
replication by 40% - 50%
 Firewall between Unified CM
servers
 After upgrade, check for the
following using CLI, RTMT and
Unified Reporting (details in notes
section)
DB replication state
Connectivity
BRKUCC-2011 201

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

Brkucc 2011 migrating-from_previous_versions_of_cisco_unified_communications_manager_(cucm)_to_version_12.0

Brkucc 2011 migrating-from_previous_versions_of_cisco_unified_communications_manager_(cucm)_to_version_12.0

Recommended

Recommended

More Related Content

Similar to Brkucc 2011 migrating-from_previous_versions_of_cisco_unified_communications_manager_(cucm)_to_version_12.0

Similar to Brkucc 2011 migrating-from_previous_versions_of_cisco_unified_communications_manager_(cucm)_to_version_12.0 (20)

More from Michael Ganschuk

More from Michael Ganschuk (18)

Recently uploaded

Recently uploaded (20)

Brkucc 2011 migrating-from_previous_versions_of_cisco_unified_communications_manager_(cucm)_to_version_12.0