Brkucc 2011 Brkucc 2014 Ta DDM

Brand Review has checked your presentation and noted the following items:
In the correct widescreen Cisco Live 2014 template: YES, but it is in a larger page size, and
will project fine, but please mention this to Brand Review onsite for the PDF process. Also,
several slides were not RESET to layouts, so I RESET them, and the titles and bullets
snapped into place.
Presentation ID filled in: YES
Slide numbers fixed and turned on: ADDED WHERE NEEDED
Footers fixed: OK
Missing (or misplaced) required slides added: Theme Graphic and Presenter Title Slide
(first 2 slides); Evaluation Layout, Continue Your Education, and End Slide (final three
slides) ADDED MANDATORY SLIDES BEFORE THE other slides section
Videos linked or embedded: NONE
Readability issues: NONE
Copyright infringement issues: NONE
Remember to run spell check on your presentation.
Delete this green note after review.
Best Practices for Migrating Previous Versions of

Cisco Unified Communications Manager (CUCM)
to Version 10.5
BRKUCC-2011
Brandon Ta, Technical Solutions Architect

bta@cisco.com
Solution Names and Versions

CUCM / Unified CM /
CallManager /UC Manager
Prime License Manager
Cisco CallManager
3.0-3.3
Enterprise License Manager

(ELM)
9.0 9.1
Cisco Unified CallManager

4.0-4.2
Prime License Manager

(PLM)
10.0-10.5
Cisco Unified
Communications Manager
(CUCM)
4.3-10.5
BRKUCC-2011
2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
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 Ciscos 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
Cisco Public
Agenda
Session Objectives and Scope
CUM 10.5 Upgrade Definition and Upgrade
Path
CUCM License and Prime License Manager
(PLM)
Virtualized CUCM
System Level Upgrade
Q&A
BRKUCC-2011
Cisco Public
Session Highlights
Licensing and
License Migration
CUCM Migration
Prime Collaboration
Deployment (PCD)
CUCM 10.X
Virtualized only
BRKUCC-2011
Manual process
Automated process
Traditional manual process
Automated process with PCD
Automated tool for operation tasks

CUCM upgrade, COP file installation, fresh
installation or hostname/IP Address change
Platform conversion
Highlight 10.X through out this presentation
Cisco Public
Session Objectives and Scope
Color Code for Versions of CUCM

CUCM 5.X
CUCM 6.X
CUCM 7.X
CUCM 8.X
CUCM 9.X
Virtualized CUCM 8.X and 9.X
Virtualized CUCM 10.X
BRKUCC-2011
Cisco Public
Session Objectives
To provide foundational knowledge for a successful upgrade or migration to
CUCM 10.5
Planning
Considerations
Installation
Approaches
To provide an overview and migration of CUCM licenses

To provide some best practice guidelines for platform conversion from bare
metal CUCM to a virtualized CUCM
BRKUCC-2011
Cisco Public
Session Scope
CUCM 6.1(X)
Covers in detail selected versions of CUCM that has a

direct one step upgrade to CUCM 10.5
CUCM 7.1(X)
CUCM 8.X
CUCM 10.5
Cover in detail platform conversion from bare metal

CUCM to virtualized CUCM
CUCM 9(X)
CUCM 9(X)
CUCM 10(1)
TRC
Specs-Based
Platform Conversion
VMware
Supported
MCS, HP or IBM Servers

Compatibility Information for Cisco Unified Communications Manager Release 10.x
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/compat/matrix/10_x/CUCM_BK_CD1DB914_00_compat_matrix.pdf
BRKUCC-2011
Cisco Public
10
Servers
NEW
CUM 10.5 Upgrade Definition

and Upgrade Path
Upgrade Definition
CUCM Major/Minor Version

CUCM Major
Version
CUCM Minor
Version
10.0
9.0
8.0
7.0
6.0
5.0
10.5
9.1
8.5 and 8.6
7.1
6.1
5.1
BRKUCC-2011
Cisco Public
13
Minor version upgrade requires active

Essential Operate Service (ESW) contract
Major version upgrade requires active

Unified Communication Software
Subscription (UCSS) contract
UCSS and ESW are merging into one

service offer named Cisco Software
Support Service (SWSS)
NEW
Sample CUCM Versions and Builds

CUCM Version
CUCM Build
10.5(1)
10.5.1.10000-7
10.0(1)su1
NEW
Numbering Convention
(A.B.C.XYzzz-x)
(A) Major version
10.0.1.11900-2
8.6.2.20000-2
(B) Minor version
10.0(1)
10.0.1.10000-24
9.1(2)su1
9.1.2.11900-12
(C) Maint. rel.
9.1(2)
9.1.2.10000-28
(X) Build
9.1(1a)
9.1.1.20000-5
9.1(1)
9.1.1.10000-11
9.0(1)
9.0.1.10000-37
8.6(2a)su2
8.6.2.22900-9
8.6(2a)su1
8.6.2.21900-5
8.6(2a)
8.6.2.20000-2
8.6(2)
8.6.2.10000-30
BRKUCC-2011
8.6.2.20000-2
8.6.2.20000-2
8.6.2.10000-2
8.6.2.20000-2
(Y) FCS:0, ES or SU: 1-9
8.6.2.10000-30 (FCS)
8.6.2.22900-1 (ES or SU look at last three digits)
(zzz) FCS:000, ES: 001-899, SU: 900-999
8.6.2.20000-2 (FCS)
8.6.2.21001-1 (ES)
8.6.2.22900-1 (SU)
Cisco Public
14
Reference
CUCM Upgrade Definition

W1
W1 Upgrade: Windows to Appliance model

High complexity with possible longest downtime
(e.g. CUCM 4.1(3), 4.2(3), or 4.3(2) to 7.1(5b))
L2
RU
Not covered in detail in this

session. More detail steps in
the appendix
L2 Upgrade: Appliance to Appliance model

Low complexity with possible shortest downtime
Between CUCM versions with the same Major RHEL versions
(e.g. CUCM 7.1(5) to 8.5 or CUCM 8.6 to 9.1)
RU (Refresh Upgrade): Appliance to Appliance model with major

RHEL version change (starting with RHEL 5)
Medium complexity with possible longer downtime
From CUCM versions 6.X, 7.X, 8.0 or 8.5 to 8.6, 9.X and 10.X
(e.g. CUCM 8.5 to 8.6 or CUCM 9.1 to 10.0)
BRKUCC-2011
Cisco Public
15
CUCM Migration
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
PC
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)
Platform Change: Appliance to Virtualized model

Low complexity with minimal downtime
From CUCM versions 6.X, 7.X, 8.0 or 8.5 to 8.6, 9.X and 10.X
(e.g. Older servers that cannot support the latest CUCM or CUCM 10.X)
BRKUCC-2011
Up to
)
9. 1( 2
Cisco Public
16
1
To 9.
(2 )
L2 and RU Upgrade: Appliance to Appliance Model

Updated
CUCM SW
CUCM
Publisher
1
2
Active Partition
inActive Partition
InActive partition
Active Partition
InActive partition
Active partition
3
Switch
Version via
OS Admin
or CLI
CUCM
Subscriber
BRKUCC-2011
CUCM
Publisher
inActive Partition
Active partition
CUCM
Subscriber
Cisco Public
17
L2 and RU Upgrade: Appliance to Appliance

Decision Tree
L2
L2
Existing CUCM
cluster being
upgraded
RU
YES
Perform a L2
Upgrade
N
O
Perform a RU
Upgrade
BRKUCC-2011
L2
Upgrade to same
major RHEL
version
Upgraded
CUCM
cluster
Cisco Public
18
Started with
CUCM 8.6 or
RHEL 5
18
L2 versus RU Upgrade
L2
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
RU
Upgrade
Server is down while upgrade software is being install

More reboots for bare metal servers
Higher downtime since upgrade cannot be done while
system is functioning
Upgrade is equal to complete installation of CUCM
Detailed L2 and RU upgrade process are in the
appendix
BRKUCC-2011
Cisco Public
19
Refresh Upgrade (RU) Recommendations

Perform a DRS back up before upgrade
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
To minimize downtime, upgrade Publisher or first node until completion and then
upgrade first set of Subscribers or secondary nodes while leaving some nodes
performing call processing
Install the latest COP (ciscocm.refresh_upgrade_v1.1.cop.sgn) file on CUCM
version 8.5 or earlier to allow for successful upgrade and limit switch version
after upgrade
COP file is NOT required for CUCM version 8.6 or later to upgrade to 9.X
BRKUCC-2011
Cisco Public
20
Refresh Upgrade (RU) for MCS 7825 and MCS 7828

(CUCM 9.X Upgrade)
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
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
BRKUCC-2011
Cisco Public
21
8.0(2
Bridge Upgrade
Upgrade
DRS
DRS
DRS
File
Servers supported to
run CUCM version X
Servers supported to be
in Bridge mode on
CUCM version Y
Secure FTP
Server
CUCM in a
virtualized
environment
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/en/US/docs/voice_ip_comm/cucm/cucos/8_0_2/cucos/iptpch7.html#wp1058411
BRKUCC-2011
Cisco Public
22
9.1(2
Jump Upgrade
Servers that cannot run
CUCM 8.0(2) or later
Jump Upgrade Process
CUCM 9.1(2) in a
virtualized
environment
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 virtualization of CUCM at 6.1(4), 6.1(5), 7.1(3) or 7.1(5) in the lab for the
purpose platform change and CUCM 9.1 upgrade
Minimal down time
Database lockdown time
No license required for interim upgrades
BRKUCC-2011
Cisco Public
23

LAB
CUCM
6.X or 7.X
on MCS
New
virtualized
CUCM
6.X or 7.X
Build
same
CUCM
version
DRS
Backup
sFTP
Server
New
virtualized
CUCM
6.X or 7.X
Upgrade
to CUCM
9.1(2)
DRS
Restore *
CUCM
6.x or
7.X ISO
Image
Upgraded
virtualized
CUCM
9.1(2)
sFTP
Server
CUCM
9.1(2)
ISO
Image
New
virtualized
CUCM
9.1(2)
Build new
CUCM
9.1(2)
DRS
Backup
* COP file has

to be installed before DRS
restore
24
Cisco Public
BRKUCC-2011
Upgraded
virtualized
CUCM
9.1(2)
sFTP
Server
New
virtualized
CUCM
9.1(2)
DRS
Restore
CUCM
9.1(2)
ISO
Image
sFTP
Server
CUCM Platform Conversion

PC
Platform Conversion: Bare metal CUCM to virtualized CUCM

(Required for CUCM 10.X)
Two approaches to this platform conversion
I.E. Bare metal server to virtualization with VMware
Cisco
Cisco UC
UC Application
Application
Cisco
Cisco Voice
Voice Operating
Operating Systems
Systems
(VOS)
(VOS)
Server Hardware
BRKUCC-2011
10.X
1. Manual
2. Automated with Prime Collaboration Deployment (PCD in later slides)
NE
W
CPU
NE
W
Memory
NIC
1
2
Drive
Manual
UC
UC App
App
UC
UC App
App
UC
UC App
App
UC
UC App
App
VOS
VOS
VOS
VOS
VOS
VOS
VOS
VOS
ESXi
ESXi 4/5
4/5 Hypervisor
Hypervisor
Automated
10. x
Cisco Public
Server Hardware
CPU
25
Memory
NIC
Storage
1. Manual Platform Conversion for 8.0(2) to 9.1(2)

CUCM on
MCS
New
virtualized
CUCM
Install on
First node
or
Publisher
DRS
Backup
sFTP
Server
New
virtualized
CUCM
DRS
Restore
on First
node or
Publisher
CUCM
ISO
Image
New
virtualized
CUCM
Install on
Secondary
node or
Subscriber
Upload
Licenses
sFTP
Server
New
virtualized
CUCM
All three
types of
licenses
CUCM
ISO
Image
Replacing a Single Server or Cluster for Cisco Unified Communications Manager:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/install/8_5_1/cluster/clstr851.html
BRKUCC-2011
Cisco Public
26
Upgrade Definition Table (reference)

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
Platform Change
Changing servers platform. Typically from bare metal servers to virtualized

environment
BRKUCC-2011
Cisco Public
27
Upgrade Path
One-Step L2 Upgrades (Appliance)

CUCM 8.6(X)
L2
CUCM 9.X
CUCM 9.X
The CUCM versions that will support a L2 upgrade to 9.X

Short or minimal downtime
Cisco Unified Communications Manager Software Compatibility Matrix

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html#wp278167
BRKUCC-2011
Cisco Public
29
One-Step RU Upgrades (Appliance)

CUCM 6.1(4)
CUCM 6.1(5)
CUCM 7.1(3)
CUCM 7.1(5)
CUCM 8.0(X)
CUCM 8.5(X)
CUCM 8.6(X)
RU
CUCM 9.X
Longer downtime
Medium upgrade complexity
Downgrade for MCS7825 & MCS7828 can be time consuming
Cisco Unified Communications Manager Software Compatibility Matrix

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html#wp278167
BRKUCC-2011
Cisco Public
30
Multi-Step Upgrade to CUCM 9.1: Source

L2
CUCM 5.1(3)
RU
CUCM 9.X
CUCM 7.1(5b)
For end of support and appliance versions of CUCM

Focus on the interim versions that can be upgraded to 9.X
Sources for multi-steps upgrade path:
Cisco Unified Communications Manager Software Compatibility Matrix - Supported upgrade
paths to/from table http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr1.pdf
Direct Upgrade Procedure and High Available Upgrade documents https://communities.cisco.com/community/partner/collaboration/migration?view=overview#/?
tagSet=2089
End of Sales Notices for CUCM is in the notes section
BRKUCC-2011
Cisco Public
31
Multi-Step Upgrade to CUCM 9.1: Interim CUCM

Version
Interim CUCM version reference point:
Software Compatibility Matrix outlines all technical possible upgrade paths
Direct Upgrade Procedure and High Available Upgrade documents outline specific
upgrade paths
Interim CUCM version selection:

Interim CUCM version(s) to upgrade to which allows for eventually to upgrade to the
targeted version
Minimize major version changes (I.E. 7.0 to 8.0) for features and license requests
CUCM versions has patch to provide for stability (latest SU or Security Update)
CUCM version that support current server
Impact by other UC applications due to dependency
BRKUCC-2011
Cisco Public
32
CUCM-BE 5K to CUCM-BE 6K or CUCM/CUC

EO S
BAT Export
BAT Data
BAT Import
CUCM-BE 5K
Virtualized CUCM
and CUC 9.1
COBRAS
Export
COBRAS Data
COBRAS Import
Upgrade CUCM-BE to version CUCM-BE 9.1

Export data:
BAT for call control and COBRAS for messaging
Build virtualized CUCM and CUC

Migration CUCM-BE 5K to CUCM-BE 6K
https://communities.cisco.com/docs/DOC-33988
Import data:
BAT for CUCM and COBRAS for CUC
BRKUCC-2011
Cisco Public
33
CUCM License and Cisco Enterprise

License Manager (ELM)
Foundational Knowledge of CUCM 8.X and

Earlier License
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
BRKUCC-2011
Cisco Public
36
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
BRKUCC-2011
Cisco Public
37
License Type and DLU (CUCM 8.6 and earlier)

LICENSE TYPE
DLU
Comments
CUWL Pro
17/12
Prior to January 2012/After January 2012
11/8
Prior to January 2012/After January 2012
CUWL Standard
CUWL Entry
Migrate to UCL Enhance Plus in CUCM 9.X and later
CUWL Analog
Migrate to UCL Essential in CUCM 9.X and later
CUWL Public Space
Migrate to UCL Enhance in CUCM 9.X and later
UCL Enhance
UCL Basic
UCL Essential
UCL Public Space
UCL Adjunct
UCL TP Single/Multiscreen
Migrate to TP Room in CUCM 9.X and later
BRKUCC-2011
Cisco Public
38
CUCM 9.X License Conversion
Cisco Enterprise License Manager (ELM)

CUCM + CUELM
CUC + CUELM
CUCM BE 5K
CUCM BE 3K
CUELM
CUCM 9.X installation DVD consisted of five products including Cisco Enterprise License Manager
(ELM) bundled with two UC products or as stand alone deployment
ELM is a centralize licensing product running on top of Cisco Voice OS (VOS)
ELM supports Cisco Unified Communications Manager (CUCM) and Cisco Unity Connection (CUC)
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)
BRKUCC-2011
Cisco Public
40
ELM Architecture 9.1

First Node of
CUCM Cluster 1
License
Manager API
First Node of
CUCM Cluster 2
First Node of
CUCM Cluster 3
License
Manager API
License
Manager API
First
node of
CUC 1
First
node of
CUC 2
First
node of
CUC 3
License
Manager API
License
Manager API
License
Manager API
ELM
License file
ELM
License Manager API added to CUCM 9.0 and CUC 9.0 to interact with ELM for license
request and approval
ELM provides for centralize license management, license pooling, minimize re-hosting of
license files and eliminate dependency of license to versions of UC applications
Manual license file upload onto ELM is available with CUCM 9.0 and above
BRKUCC-2011
Cisco Public
41
CUCM and ELM Interaction

ELM polls all registered CUCM clusters
CUCM evaluates license usage and sends license
usage back to ELM
CUCM:
Evaluate phone,
users and features
usage
Send license
usage to ELM
Receive license
response and
operate in the
appropriate mode
ELM:
ELM evaluate all CUCM responses to see if there is

adequate licenses for the requested types
Poll all products

every 24 hours
Evaluate
adequate
licenses
Perform license
substitution
Provide Valid or
Invalid license
response
ELM performs license substitution if does not have

adequate license of the requested type
ELM response back to with either valid or invalid (not
enough) to all CUCM clusters
CUCM receives the response and function
accordingly
Detailed CUCM and ELM interactions with
signaling are in the appendix
BRKUCC-2011
Cisco Public
42
CUCM License Usage
BRKUCC-2011
Extension mobility users uses no license for CUCM 9.1(1a)

and later
Extension mobility user with Unified Mobility feature uses
one UCL Basic license
User
Phones
Phones without Owner User ID association

Based on the phone model
User
/ Phone
Phones with Owner User ID association

Based on the number of phones assigned to the user
Cisco Public
43
CUCM 9.X Phone License

License
Phone Type (2)
Essential UCL
Analog, 3905, 6901, VGC Phone, ATA186, ATA187
EM
Basic UCL
6911, 6921, CUC-RTX, Analog, 3905, 6901, VGC

Phone, ATA186, ATA187
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
EM, SNR
Enhance UCL
Plus
Same as Enhance UCL
EM, SNR
BRKUCC-2011
# of Devices (3)
Cisco Public
44
Features (1)
CUCM 9.X Phone License

License
Phone Type (2)
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
TelePresence
TelePresence
BRKUCC-2011
# of Devices (3)
10
Cisco Public
45
Features (1)
EM, SNR
Phones and Owner User ID Association

Device > Phone > Device Name
Phones 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
Number of Phones
Type of License
Based on the model of phone
Enhanced UCL Plus
3-10
CUWL Standard
Recommend to perform before upgrading to CUCM 9.X
BRKUCC-2011
Cisco Public
46
Sample CUCM License Usage Send to ELM
BRKUCC-2011
Cisco Public
47
ELM License Evaluation and License Substitution

Two license types: User license and Feature license
CUWL Standard
UCL Enhanced +
UCL Enhanced
UCL Basic
UCL - Essential
Licenses are based on hierarchical model where lower feature license

can be covered by a higher feature license
I.E. UCL Basic can be covered by UCL Enhanced
I.E. UCL Enhanced can be covered by UCL Enhanced Plus (+)
ELM evaluate ALL systems license requirements on a per product
(CUCM and CUC) basis and respond back with one consistent
response to ALL registered systems
VALID: adequate license
User License
Substitution
INVALID: inadequate license

Centralize and system level licensing view
Enterprise License Manager

http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/srnd/9x/callpros.html#wpxref61870
BRKUCC-2011
Cisco Public
48
CUCM 9.X License States (reference)

Demo: Warning displayed : The system is operating on demo licenses that will expire in <X> days. Add this
system to an Enterprise License Manager and install sufficient licenses to cover its usage before expiration in
order to avoid losing the ability to provision users and devices. Demo is 60 days.
No Provisioning: Warning displayed: The system is operating without any valid licenses. Configure licenses on
the system in order to restore the ability to provision users and devices.
Overage: Warning displayed: The system is operating with an insufficient number of licenses. If additional
licenses to cover the shortage are not configured in your Enterprise License Manager within <X> days, you will no
longer be able to provision users and devices.
Lost connection to ELM: Warning displayed: The system has not synchronized successfully with Enterprise
License Manager for <X> days. If successful synchronization does not occur within the next <60-X> days, you will
no longer be able to provision users and devices.
Security mismatch with ELM: Warning displayed: Due to a certificate mismatch, the system has not
synchronized successfully with Enterprise License Manager for <X> days. If successful synchronization does not
occur within the next <60-X> days, you will no longer be unable to provision users and devices.
Grace: Warning displayed: The system is operating under a licensing grace period that will expire in 1 day.
Install sufficient licenses in the Enterprise License Manager for this system to cover its usage in order to avoid
losing the ability to provision users and devices. If licenses for this system are not already being managed by an
Enterprise License Manager server, the system must first be added to one.
BRKUCC-2011
Cisco Public
49
License Conversion
CUWL
2-17
DLU
UCL
0-6
DLU
A La
Carte
DLU
How can I
migrate
these
license?
Manual
Pool of
DLUs
How many
of what
type of
licenses
do I have?
Automated
Detailed automated process in the

appendix
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
http://www.cisco.com/en/US/products/ps6509/products_tec
h_note09186a0080bf5921.shtml
License Count Tool (UCT):

http://software.cisco.com/download/release.html?mdfid=283782839&softwareid=282204704&release=UCT&relind=AVAILABLE&rellifecycle=&reltype=latest
BRKUCC-2011
Cisco Public
50
License Count Utility (UCT) for CUCM 6.X-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.
CUCM 6.X
Detailed screen capture of UCT are in

the appendix
CUCM 7.X
License
Count Tool
CUCM 8.X
BRKUCC-2011
Cisco Public
51
1. Data for Manual License Migration

(recommended)
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 pertinence license information:

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
52
BRKUCC-2011
2014CUCM
Cisco and/or its9.X
affiliates.user
All rights reserved.
count and
Cisco Public
features
for unused DLU
License Management Models with ELM

License
Management
CUCM cluster
CUCM cluster
License
Management
CUCM cluster
DISTRIBUTED
ELM Stand Alone

CUCM cluster
CENTRALIZED
ELM 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
BRKUCC-2011
Cisco Public
53
Planning and Migration with ELM

1
ELM 9.X
CER
PLM 10.X
CUCM 9.X
CUC 9.X
CUCM 9.X
CUC 9.X
CUCM 9.X
CUC 9.X
CUCM 10.X
CUC 10.X
Changes to Cisco Enterprise License Manager (ELM)

Cisco Enterprise License Manager (ELM) 9.X will be renamed to Cisco Collaboration Prime License
Manager (PCLM) 10.X
Cisco Emergency Responder support PLM 10.X
Migrating ELM
1. Upgrade ELM 9.X to PLM 10.X
2. Migrate CUCM or CUC to 10.X. Migrate CUCM or CUC license to 10.X
3. Upgrade
and add CER to PLM
54
BRKUCC-2011
Cisco Public
Virtualized CUCM
Platform Support
Platform Options
Tested Reference
Configuration (TRC)
Specs-Based
(Software)
C220 M3 B200 M3
C240 M3
C260 M2
VMware
Supported
BRKUCC-2011
Cisco Public
57
Servers
B230 M2
B440 M2
Tested Reference Configurations (TRC)
Customers with lower virtualization proficiency

Cisco prescribed hardware specifications
Performance guarantee for UC applications
Tradeoffs to hardware choices
Chassis based:
B200 M3, B230 M2 and B440 M2
FC SAN only
Full width versus half width blade
Rack-Mount:
C220 M3, C240 M3 and C260 M2
DAS only
UC Virtualization Supported Hardware:
1 to 2 rack unit
http://docwiki.cisco.com/wiki/UC_Virtualization_Supported_Hardware
BRKUCC-2011
Cisco Public
58
TRC Based Platform Decision Tree

Start
FC SAN or
DAS
FC SAN
NO
Low Server
Distribution
YES
YES
YES
B200 M3 TRC1
N
O
DAS
C220 M3 TRC1
New E5
Processor
New E5
Processor
N
O
C260 M2 TRC1
Low Server
Distribution
NO
B230 M2 TRC1
YES
B440 M2 TRC1
C240 M3 TRC1
FC SAN provides for higher redundancy in terms of storage redundancy and VMware
redundancy
Newer E5 processor for longevity
Lower server distribution might have larger failure domain
BRKUCC-2011
Cisco Public
59
Specs-Based Hardware
Customers with extensive virtualization proficiency
Maximum hardware choices including Cisco, HP, IBM and any servers that are on the VMware
Hardware Compatibility list
Use Tested Reference Configurations (TRC) for guidance
Cisco is not responsible for UC VM performance
VMware
vCenter is mandatory
vCenter Server
VMware vCenter is required

CPU requirements
Intel Xeon 5600 or 7500 family with minimum physical core speed of 2.53 GHz
Intel Xeon E7-2800, E7-4800 or E7-8800 family with minimum physical core speed of 2.4 GHz
Intel Xeon E5-2600 family with minimum physical core speed of 2.5 GHz
Leverage TRC as a baseline for CPU model
DAS only, DAS & FC SAN or FC SAN only
Specification-Based Hardware Support
http://docwiki.cisco.com/wiki/Specification-Based_Hardware_Support
BRKUCC-2011
Cisco Public
60
TRC or Specs-Based Decision Tree

Start
Virtualization
Proficiency
LOW
TRC 1
HIGH
Performance
Guarantee
YES
TRC
NO
TRC
NO
UC Applications
Supported by
Specs-Based
YES
Specs-Based
Evaluation criteria for platform decision

between TRC and Specs-Based varies
based on organization priorities
Virtualization proficiency
Performance guarantee
Platform and vendor choices
Differences in supported
applications, noticeably
Contact Center
TelePresence (CTMS, CTS
Manager)
Cisco WebEx Meeting Server
Solution should be consistent, but can

hybrid
Unified Communications Virtualization Supportedbe
Applications:
http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Application
BRKUCC-2011
Cisco Public
61
Virtualization Support
VMware Sphere Support

ESXi 4.0, 4.1, 5.0 and 5.1 (with some specific UC application exceptions)
VMware vSphere Hypervisor, Essential, Essential Plus, Acceleration Kit,
Standard, Enterprise or Enterprise Plus
ISO for Cisco UCS and third party for appropriate driver support is at:
https://my.vmware.com/web/vmware/info/slug/datacenter_cloud_infrastructure/vm
ware_vsphere/5_0#drivers_tools
VMware vCenter (Essential, Foundation or Standard)

Recommended for large deployment. centralize management, license
management, etc.
Mandatory for Specs-Based deployment
VMware acquisition: Cisco, Partner or VMware
https://www.vmware.com/files/pdf/vsphere_pricing.pdf
Hypervisor Support for Virtualized UC:
http://docwiki.cisco.com/wiki/Unified_Communications_VMWare_Requirements
BRKUCC-2011
Cisco Public
63
Cisco Virtual Template (OVA) File

OVA
CCO
1
vSphere
Client
UCS B200 M3
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 on CCO for UC applications deployment
VMware virtual machine hardware version (VMV)
VMV 7 = ESXi 4.0, 4.1 or 5.0
VMV 8 = ESXi 5.0 ( To upgrade, right click and select upgrade virtual hardware).
Cannot be downgraded to 7
OVA Files for UC on UCS Deployments:
http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_(including_OVA/OVF_Templates)
BRKUCC-2011
Cisco Public
64
Virtualization CUCM Implications

Serial support for SMDI
USB for UPS
Alternative to USB live audio source as music on hold (MOH):
Enable multicast on network
Leverage Land Mobile Radio (LMR) to the multicast audio source
Enable multicast MOH on CUCM
BRKUCC-2011
Cisco Public
65
Prime Collaboration Deployment (PCD)

1
CUCM 6.X
nd
a
t a
en vi
em ISO
g
a d P
an loa sFT
M up
Virtual machine with PCD software installed
Provides sFTP service for data export and ISO

images
Provides NFS services to ESXi host for mounting

CUCM software
Provides automated and scheduled of migration

to virtualized CUCM 10.X (see next slide for all
features)
CUCM 7.X
PCD
1. Install Data Export COP file

2. Data export to PCD via sFTP
CUCM 8.X
3. Power off CUCM

4. Create virtual machine and install CUCM with
data import
ESXi
Host
BRKUCC-2011
Cisco Public
67

Feature
CUCM
6.1(5)
CUCM
7.1(3)-7.1(5)
CUCM
8.0(1-3)
CUCM
8.5(1)
CUCM
8.6(1-2)
CUCM
9.x
CUCM
10.x
Migration to 10.X
Fresh Install
Upgrade/COP Install
Switch Version
Reboot
Export Data
Hostname/IP
Address Change
BRKUCC-2011
Cisco Public
68
CUCM Platform Conversion

PC
Platform Conversion: Bare metal CUCM to virtualized CUCM

(Required for CUCM 10.X)
Two approaches to this platform conversion
1. Manual
2. Automated with Prime Collaboration Deployment
Cisco
Cisco UC
UC Application
Application
Cisco
Cisco Voice
Voice Operating
Operating Systems
Systems
(VOS)
(VOS)
Server Hardware
CPU
BRKUCC-2011
Memory
NIC
1
2
Manual
UC
UC App
App
UC
UC App
App
UC
UC App
App
UC
UC App
App
VOS
VOS
VOS
VOS
VOS
VOS
VOS
VOS
ESXi
ESXi 4/5
4/5 Hypervisor
Hypervisor
Automated
Server Hardware
Drive
CPU
Cisco Public
69
Memory
NIC
Storage
1. Manual Platform Conversion

CUCM on
MCS
New
virtualized
CUCM
Install on
First node
or
Publisher
DRS
Backup
sFTP
Server
New
virtualized
CUCM
DRS
Restore
on First
node or
Publisher
CUCM
ISO
Image
New
virtualized
CUCM
Install on
Secondary
node or
Subscriber
Upload
Licenses
sFTP
Server
New
virtualized
CUCM
All three
types of
licenses
CUCM
ISO
Image
Replacing a Single Server or Cluster for Cisco Unified Communications Manager:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/install/8_5_1/cluster/clstr851.html
BRKUCC-2011
Cisco Public
70
2. Automated Platform Conversion with PCD

1
CUCM 6.X
nd
a
t a
en vi
em ISO
g
a d P
an loa sFT
M up
CUCM 7.X
PCD
Only can be use with upgrades to CUCM 10.X

with this platform change
Only from CUCM version 6.1(5), 7.1(3), 7.1(5),

8.0(1-3), 8.6(1-2), 9.X and 10.X
Can be a migration by using new set of IP

address for virtualized CUCM
CUCM 8.X
ESXi
Host
BRKUCC-2011
Cisco Public
10. X
71
Platform Migration to Virtualized CUCM 9.1(2)

Platform
Number
Supported
Normal Mode
Supported Not
Bridge
Supported
Upgrade Strategy
6.1-7.1
8.0
8.5-9.1
Jump upgrade
6.1-7.1
8.0-8.5
8.6-9.1
Jump upgrade
6.1-8.0
NA
8.5-9.1
Jump upgrade or upgrade to 8.0 to

change platform
6.1-8.0
8.5
8.6-9.1

change platform
6.1-8.0
8.5-9.1
NA

change platform
6.1-8.5
8.5-9.1
NA

change platform
7.1-9.1
NA
NA

change platform
Supported Cisco Unified Communications Manager Releases by Server:

http://www.cisco.com/en/US/partner/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd8062a4f9.html
BRKUCC-2011
Cisco Public
72
System Level Upgrade
UC Application Caveats
Attendant Console Considerations for CUCM 9.1

Cisco Unified
Department Attendant
Console
Cisco Attendant Console
Cisco Unified
Business Attendant
Console
Cisco Unified
Enterprise Attendant
Console
No support for Cisco Attendant

Console (CAC) with CUCM 8.0 or
later
Migrate to one of the four
attendant console solutions prior
to migration
Cisco Premium
Attendant Console
End-of-Sale and End-of-Life Announcement for the Cisco Unified Attendant Console::
http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps7046/ps7282/end_of_life_notice_c51-499091.html
BRKUCC-2011
Cisco Public
75
Cluster Level Upgrade or Migration

LAB
CUCM
6.X or 7.X
on MCS
Build
same
CUCM
version
DRS
Backup
sFTP
Server
1
BRKUCC-2011
New
virtualized
CUCM
6.X or 7.X
New
virtualized
CUCM
6.X or 7.X
Upgrade
to CUCM
9.1(2)
DRS
Restore
CUCM
6.x or
7.X ISO
Image
4
Cisco Public
Upgraded
virtualized
CUCM
9.1(2)
77
New
virtualized
CUCM
9.1(2)
Build new
CUCM
9.1(2)
DRS
Backup
CUCM
9.1(2)
ISO
Image
sFTP
Server
Upgraded
virtualized
CUCM
9.1(2)
sFTP
Server
New
virtualized
CUCM
9.1(2)
DRS
Restore
CUCM
9.1(2)
ISO
Image
sFTP
Server
In-Place L2 or RU Upgrade Process
Existing
CUCM
Cluster
Upgrade
Publisher
Inactive
Partition
Back Up
With DRS
sFTP
Server
or Tape
1
BRKUCC-2011
Existing
CUCM
Cluster
CUCM
9.X
DVD Kit
New CUCM
9.X Cluster
Existing
CUCM
Cluster
Switch
Partition
on
Publisher
Upgrade
Subscribers
Inactive
Partition
CUCM
9.X
DVD Kit
2
Switch
Partition
on
Subscriber
CLI
or
OS Admin
78
ELM
Add
CUCM to
ELM
CLI
or
OS Admin
3
Cisco Public
New CUCM
9.X Cluster
High availability
upgrade guide
provides detailed
steps to minimize
outage
Migration Option with L2, RU or Jump Upgrade

ICT
Existing
CUCM
Cluster
Back Up
With DRS
ELM
Add
CUCM to
ELM
New
CUCM
Cluster
1
BRKUCC-2011
CLI
or
OS Admin
6
5
Cisco Public
79
New
CUCM
Cluster
New
CUCM
Cluster
Install
CUCM
Restore
With
DRS and
license
files
Upgrade
Inactive
Partition
Switch
Partition
sFTP
Server
or Tape
New
CUCM
Cluster
CUCM
DVD Kit
sFTP
Server
or Tape
CUCM
DVD Kit
To minimize outage
and allows for
migration of large
deployment
Upgrade Readiness Assessment Web Tool

Input Mode
CUCM
Gateway
Unity/Unity
Connection
Automated
CURT
Reports
NA
NA
Version
and server
model
Router
model
Manual
Version and
server model
Upgrade Readiness
Assessment Web
Tool
Hardware for potential server replacement
Baseline for upgrade path with detailed steps
Does not check with compatibility matrix
Send results for proactive TAC case
CUCM Upgrade Central iPad application
Output
CUCM
Gateway
Readiness
Summary
Software and
hardware
compatibility
Software
Software and
and
hardware
hardware
compatibility
compatibility
Customized
Upgrade
Procedures
Upgrade
guide
NA
Upgrade Readiness Assessment Web Tool

http://tools.cisco.com/cucst/upgrade/index.jsp
BRKUCC-2011
Cisco Public
80
Unity/Unity
Connection
Upgrade guide
System Level Upgrade or Migration
UC Application Upgrade/
Migration Definition
Upgrade Time Increases with Various Dependencies
UC Applications
CER
CUCCE
CUCCX
CUP
Migration Strategy
Pre-Upgrade Migration *
UC Applications
Upgrade
CUCM
Upgrade
Down Time
MP
MPE
Unity
Connection
Unity
* Some UC Application Requires a

Complete Reinstall for Upgrade
Down Time
Post Upgrade Migration *
CUCM
Upgrade
UC Applications
Upgrade
Down Time
Replacing a Cisco Unified Communications Manager Software Compatibility Matrix:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html
BRKUCC-2011
Cisco Public
82
Developing Upgrade Path

Existing
CUCM
version
Interim versions for multi-hop upgrades

Supported upgrade paths in compatibility matrix
Customize Upgrade Procedures from Upgrade Readiness
Assessment Web Tool
UC applications dependencies
Selecting an upgrade method

Target
CUCM
version
BRKUCC-2011
Jump upgrade
Manual method with L2 and RU
Migration
Cisco Public
83
Overall Upgrade Strategy to Minimizing Down Time
Phase I:
Phase II:
Phase III:
Owner User ID / phone

association and
license request
IP Phone
UC Applications PreUpgrade Migration
CUCM and UC
Applications Post
Upgrade Migration
UC Applications
Upgrade
CUCM
Upgrade
Firmware Upgrade
IP Phone
Firmware
Phase II, III or III 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
Cisco IP Phone Firmware by CUCM Releases:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html
BRKUCC-2011
Cisco Public
84
Phase IV:
UC Applications
Upgrade
Phase II: Phone Firmware Distribution

Peer-to-Peer Image Distribution (PPID):
Configurable via AXL script with Unified 4.1 and later using CCMPPID.exe. (Readme in
notes section)
Configurable via CM Administration or BAT from version 5.0 and later
Default is disable PPID on all phones models
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 200 for Windows and 500 for appliance)
1,500 for single processor dedicated TFTP server and 3,000 for dual processors
dedicated TFTP server
Peer-to-Peer Image Distribution (PPID):
http://www.cisco.com/en/US/docs/voice_ip_comm/cucmbe/admin/8_5_1/ccmsys/a08ipph.html#wp1141991
BRKUCC-2011
Cisco Public
85
Phase II:Phone Upgrade Caveat

If possible, choose final CUCM version default or recommended firmware.
Avoid multiple upgrade and downgrades
Some third-generation IP phones (7971G-GE, 7970G, 7961G-GE, 7961G,
7941G-GE, 7941G, 7911G, and 7906G):
Firmware release 6.0(1) or earlier needs to upgrade to 7.0(3)
CUCM 4.1(2) or earlier
All third-generation IP phones:

Firmware release 8.3(2)SR1 or earlier must upgrade to 8.5(2) before upgrading to
8.5(2)SR1 or later
Factory phones or phones taken off another CUCM cluster
Firmware Release Notes 8.5(2)SR1:
http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/firmware/8_5_2/english/release/notes/7900_852SR1.ht
ml
BRKUCC-2011
Cisco Public
86
Phase II: CUCM Upgrade

Clear out logs in /common partition for upgrade
Disable extension mobility
Minimize CAR to reduce upgrade time
Stage software on CUCM server during download before upgrading
Starts secondary nodes or Subscribers when Publisher logs indicate that
upgrade can start on secondary nodes or Subscribers
Upgrade secondary nodes or Subscribers at the same time (15 minutes delay in
between nodes)
For large high availability upgrade, increase maximum number of registered
devices to 7500 or 10000
Check for DB replication state of 2 before and after upgrade
BRKUCC-2011
Cisco Public
87
Phase III: CUCM
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
CUCM SRND:
www.cisco.com/go/ucsrnd
BRKUCC-2011
Cisco Public
88
Migration Recommendations for

CUCM Upgrade
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/05/30/howo-get-the-efficient-support-for-drive-to-9
Open a proactive TAC case for the upgrade

http://cisco.com/tac/caseopen
BRKUCC-2011
Cisco Public
89
Participate in the My Favorite Speaker Contest

Promote Your Favorite Speaker and You Could be a Winner
Promote your favorite speaker through Twitter and you could win $200 of Cisco
Press products (@CiscoPress)
Send a tweet and include
Your favorite speakers Twitter handle <Speaker enter your twitter handle here>
Two hashtags: #CLUS #MyFavoriteSpeaker
You can submit an entry for more than one of your favorite speakers
Dont forget to follow @CiscoLive and @CiscoPress
View the official rules at http://bit.ly/CLUSwin
BRKUCC-2011
Cisco Public
90
Complete Your Online Session Evaluation

Give us your feedback and you
could win fabulous prizes. Winners
announced daily.
Complete your session evaluation
through the Cisco Live mobile app
or visit one of the interactive kiosks
located throughout the convention
center.
Dont forget: Cisco Live sessions will be available
for viewing on-demand after the event at
CiscoLive.com/Online
BRKUCC-2011
Cisco Public
91
Continue Your Education

Demos in the Cisco Campus
Walk-in Self-Paced Labs
Table Topics
Meet the Engineer 1:1 meetings
BRKUCC-2011
Cisco Public
92
Appendix
Questions ?
W1 Upgrade: Windows to Appliance Model

Not covered
in detail in
this session
Existing
CUCM 4.X
Cluster
Existing
CUCM 4.X
Cluster
New CUCM New CUCM

7.1 Cluster
7.1 Cluster
Install
Install,
Install
and Run
Run, and
CUCM
Upgrade
Download
7.1
Utility on All
DMA from
Servers
Publisher
Latest
Data Migration
Upgrade
Assistant
Utility From
(DMA) 7.1
CCO
Back Up
With
BARS
Tape or
Network
Share
1
BRKUCC-2011
Existing
CUCM 4.X
Cluster
Download
From CCO
CUCM
7.X
DVD Kit
Cisco Public
96
CUCM 7.1
software
availability can
be an issue
since CUCM
7.1 has EOS
(End of Sales)
Upload
Licenses
Upload
DMA
File
Save DMA File

to Tape or
Network Share
New CUCM
7.1 Cluster
Tape, FTP
or sFTP
Server
Node, DLU and

7.1 Feature SW
License
NEW
UPGRADE
License Acquisition with CUCM 5.X to 8.X
Product
Activation Key
Contract Number
Product Upgrade
Tool Site
SW Feature
License
Upgraded
CUCM cluster
Node
License
Device
License Unit
New CUCM
cluster
Product License
Registration Site
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
Cisco Public
97
L2 Upgrade: Appliance to Appliance Model

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

Model
Active Partition
InActive partition
BRKUCC-2011
Running
1. Data
exported
(CUCM
and CAR)
into
/common
partition
Reboot
InActive partition
Dormant
Active Partition
1. CUCM
installation
2. DB
installation
3. CUCM
data import
4. CAR DB
creation
5. CAR DB
migration
Cisco Public
InActive partition
Dormant
Active Partition
1. Firmware
and BIOS
upgrade
2. VOS
installation
3. Platform
import
Reboot
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
99
Cisco Unified Enterprise License Manager

Add CUCM or
CUC systems
2
ELM
Success/Fail
Get License Usage 24 hours
3
Analyze
5
CUC
Usage X,Y,Z
Set License Status
CUC Enforcement
First node of
CUCM
CUCM Enforcement
Get License Capability
How and what do CUC, CUCM and ELM

communicate?
Register
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
BRKUCC-2011
Cisco Public
100
Process of CUCM and ELM Communications

1
CUCM License Evaluation
3
ELM License Evaluation
How does CUC, CUCM and ELM know

what to communicate?
[VALID or INVALID ]
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
BRKUCC-2011
Cisco Public
101
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
Cisco Public
102
Using User Count Tool as Planning Tool to Migrate
Cluster > Generate Report: Generate report of ALL

systems and the corresponding UCL/CUWL usage
UCL and CUWL mode
CUWL mode has Public Space Phones
Adjustment can and should be perform to reflect

the migrated systems entitled licenses
Remain DLU does not need to be zero
The resulted UCL and CUWL will be the basis for ESW and UCSS renewal for next renewal cycle
Use this planning tool to perform proactive license resolution prior to the actual upgrade
Save the report(s) in csv format so that they can be use in the actual conversion in ELM during
upgrades:
Per systems
Migration phase(s)
BRKUCC-2011
Cisco Public
103
Use ELM Upgrade Wizard for License Upgrade

Upgrade License Wizard: License Management > Add or Upgrade License > Upgrade License
Plan, Order and Install
Plan:
Select CUCM or CUC for migration
Select what systems to migrate
Conversion is exactly like UCT so use saved UCT reports to adjust UCL/CUWL requirements
Order allows for license acquisition by capturing text from ELM
Install is to install the license file
BRKUCC-2011
Cisco Public
104
License Conversion
CUWL
2-17
DLU
UCL
0-6
DLU
A La
Carte
DLU
How can I
migrate
these
license?
Manual
Pool of
DLUs
How many
of what
type of
licenses
do I have?
BRKUCC-2011
Automated
Cisco Public
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
Standalone CUC
Upgrade CUC to 9.X
Self service license request using Product License
Registration
http://www.cisco.com/en/US/products/ps6509/products_t
ech_note09186a0080bf5921.shtml
105
License Count Utility (UCT) for CUCM 6.X-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.
CUCM 6.X
Detailed screen capture of UCT are in

the appendix
CUCM 7.X
License
Count Tool
CUCM 8.X
BRKUCC-2011
Cisco Public
106
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
107
BRKUCC-2011
2014CUCM
Cisco and/or its9.X
affiliates.user
All rights reserved.
count and
Cisco Public
features
for unused DLU
2. Automated License Migration with ELM
Contract Number
Product Upgrade
Tool site
CUCM 9.X
software
Upgrade
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
BRKUCC-2011
Cisco Public
108
2. Automated License Migration with ELM

CUCM License
Request
New upgraded
CUC 9.X
Text from ELM

License Request
ELM
Product License
Registration site
ELM
License file
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
109
BRKUCC-2011
Cisco Public
Overview of CUCM 9.1 Installation

MCS-781X
MCS7825
MCS7828
MCS7835
MCS7845
CUCM
9.X DVD KIT
INSTALLATION PROCESS (PROCEED)

1
2
Basic Install
Apply SR, ES or SU
Upgrade During
Installation
i.e., 9.1(1a) to 9.1(2)
BRKUCC-2011
New Installation, New

ServerFlash Cut or
New ServerMigration
Cisco Public
110
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
Cisco Public
111

Brkucc 2011 Brkucc 2014 Ta DDM

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Brkucc 2011 Brkucc 2014 Ta DDM

Diunggah oleh

Hak Cipta:

Format Tersedia

Brand Review has checked your presentation and noted the following items:

Best Practices for Migrating Previous Versions of

Brandon Ta, Technical Solutions Architect

Solution Names and Versions

Prime License Manager

Enterprise License Manager

Cisco Unified CallManager

Prime License Manager

2014 Cisco and/or its affiliates. All rights reserved.

Required GAAP Reconciliation

2014 Cisco and/or its affiliates. All rights reserved.

2014 Cisco and/or its affiliates. All rights reserved.

2014 Cisco and/or its affiliates. All rights reserved.

Automated tool for operation tasks

Session Objectives and Scope

Color Code for Versions of CUCM

2014 Cisco and/or its affiliates. All rights reserved.

To provide an overview and migration of CUCM licenses

2014 Cisco and/or its affiliates. All rights reserved.

Covers in detail selected versions of CUCM that has a

Cover in detail platform conversion from bare metal

MCS, HP or IBM Servers

2014 Cisco and/or its affiliates. All rights reserved.

CUM 10.5 Upgrade Definition

CUCM Major/Minor Version

2014 Cisco and/or its affiliates. All rights reserved.

Minor version upgrade requires active

Major version upgrade requires active

UCSS and ESW are merging into one

Sample CUCM Versions and Builds

(C) Maint. rel.

2014 Cisco and/or its affiliates. All rights reserved.

CUCM Upgrade Definition

W1 Upgrade: Windows to Appliance model

Not covered in detail in this

L2 Upgrade: Appliance to Appliance model

RU (Refresh Upgrade): Appliance to Appliance model with major

2014 Cisco and/or its affiliates. All rights reserved.

Bridge Upgrade: Appliance to Appliance model

Jump Upgrade: Appliance to Virtualized model

Platform Change: Appliance to Virtualized model

2014 Cisco and/or its affiliates. All rights reserved.

L2 and RU Upgrade: Appliance to Appliance Model

2014 Cisco and/or its affiliates. All rights reserved.

L2 and RU Upgrade: Appliance to Appliance

2014 Cisco and/or its affiliates. All rights reserved.

Active partition is running while upgrade software is being

Server is down while upgrade software is being install

2014 Cisco and/or its affiliates. All rights reserved.

Refresh Upgrade (RU) Recommendations

2014 Cisco and/or its affiliates. All rights reserved.

Refresh Upgrade (RU) for MCS 7825 and MCS 7828

Software raid and OS reinstallation by RHEL 5 requires USB key

2014 Cisco and/or its affiliates. All rights reserved.

2014 Cisco and/or its affiliates. All rights reserved.

Jump Upgrade Process

Upgrade process of multiple steps:

2014 Cisco and/or its affiliates. All rights reserved.

Jump Upgrade Process

* COP file has

CUCM Platform Conversion

Platform Conversion: Bare metal CUCM to virtualized CUCM

I.E. Bare metal server to virtualization with VMware