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.

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. 4/13/2017 Cisco Live 2014

Cisco Live 2014 4/13/2017 Best Practices for Migrating Previous Versions of Cisco Unified Communications Manager (CUCM) to Version 10.5 BRKUCC-2011 Brandon Ta, Technical Solutions Architect

Solution Names and Versions
CUCM / Unified CM / CallManager /UC Manager Cisco CallManager Cisco Unified CallManager Cisco Unified Communications Manager (CUCM) Prime License Manager Enterprise License Manager (ELM) 9.0 – 9.1 Prime License Manager (PLM) Official Naming Conventions mpat/ccmcompmatr1.pdf 3

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 Actual performance and environmental costs of Cisco products will vary depending on individual customer configurations and conditions.

Agenda Session Objectives and Scope
Cisco Live 2014 4/13/2017 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

Session Highlights Licensing and License Migration CUCM Migration
Manual process Automated process Licensing and License Migration Traditional manual process Automated process with PCD CUCM Migration Automated tool for operation tasks CUCM upgrade, COP file installation, fresh installation or hostname/IP Address change Prime Collaboration Deployment (PCD) Platform conversion Highlight 10.X through out this presentation CUCM 10.X Virtualized only 6

Session Objectives and Scope
Cisco Live 2014 4/13/2017 Session Objectives and Scope 1

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 8

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 Planning – break into phases Considerations for best practices Various approaches Installation of the software Platform conversion from bare metal to virtualized 9

Session Scope CUCM 6.1(X) Covers in detail selected versions of CUCM that has a direct one step upgrade to CUCM 10.5 Cover in detail platform conversion from bare metal CUCM to virtualized CUCM CUCM 7.1(X) CUCM 8.X CUCM 10.5 CUCM 9(X) CUCM 9(X) CUCM 10(1) TRC Specs-Based Behind on version might introduce additional upgrade steps. i.e. 4 and 5 Dot zero release of upgrade also introduce one or two upgrade steps i.e. 5.0 Cisco Unified Communications Manager Software Compatibility Matrix - compmatr.html#wp141921 Supported Cisco Unified Communications Manager Upgrades for Release 8.5(1) - compmatr.html#wp278167 Direct Upgrade - 8.0(3a)SU1, 8.0(3a), 8.0(3), 8.0(2c)SU1, 8.0(2c), 8.0(2b), 8.0(2a), 8.0(2), 8.0(1), 7.1(5b)SU3(restricted), 7.1(5b)SU2(restricted), 7.1(5b)(restricted), 7.1(5a)(restricted), 7.1(5)SU1a(restricted), 7.1(5)SU1(restricted), 7.1(5)(restricted), 7.1(3b)SU2, 7.1(3b)SU1, 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 6.1(5)SU2, 6.1(5)SU1, 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4) Supported Cisco Unified Communications Manager Upgrades for Release 8.0(3) - compmatr.html#wp133157 Direct Upgrade - 8.0(2c)SU1, 8.0(2c), 8.0(2b), 8.0(2a), 8.0(2), 8.0(1), 7.1(3b)SU2, 7.1(3b)SU1, 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a)SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 7.0(1)SU1a, 7.0(1)SU1, 7.0(1), 6.1(5)SU2, 6.1(5)SU1, 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3), 6.1(2)SU1a, 6.1(2)SU1, 6.1(2) Supported Cisco Unified Communications Manager Upgrades for Release 7.1(5b) compmatr.html#wp141921 Direct Upgrade - 7.1(5a)(restricted), 7.1(5)SU1a(restricted), 7.1(5)SU1(restricted), 7.1(5)(restricted), 7.1(3b)SU2, 7.1(3b)SU1, 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a) SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 6.1(5)SU2, 6.1(5)SU1, 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3), 5.1(3g), 5.1(3f), 5.1(3e)1 , 5.1(3d), 5.1(3c), 5.1(3b), 5.1(3a), 5.1(3) Platform Conversion Supported VMware Servers MCS, HP or IBM Servers Compatibility Information for Cisco Unified Communications Manager Release 10.x NEW 10

CUM 10.5 Upgrade Definition and Upgrade Path
Cisco Live 2014 4/13/2017 CUM 10.5 Upgrade Definition and Upgrade Path 2

Cisco Live 2014 4/13/2017 Upgrade Definition

CUCM Major/Minor Version
CUCM Major Version CUCM Minor Version 10.0 10.5 9.0 9.1 8.0 8.5 and 8.6 7.0 7.1 6.0 6.1 5.0 5.1 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 13

Sample CUCM Versions and Builds
Reference Sample CUCM Versions and Builds CUCM Version CUCM Build Numbering Convention 10.5(1) (A.B.C.XYzzz-x) (A) Major version (B) Minor version (C) Maint. rel. (X) Build (Y) FCS:0, ES or SU: 1-9 (FCS) (ES or SU look at last three digits) (zzz) FCS:000, ES: , SU: (FCS) (ES) (SU) 10.0(1)su1 10.0(1) 9.1(2)su1 9.1(2) 9.1(1a) 9.1(1) 9.0(1) 8.6(2a)su2 8.6(2a)su1 8.6(2a) 8.6(2) NEW Version-Numbering-Convention/ta-p/555126 Example for reading FCS Numbering Convention of : Version Major release = 8 Minor release = 6 Maintenance release = 2 Build = 2 FCS code = 0 (ES code = 1) FCS code = 000 (ES version = XX) Release candidate = 2 Example for reading ES Numbering Convention of : Version Major release = 8 Minor release = 6 Maintenance release = 2 Build = 2 ES code = 1 ES code = 001 Release candidate = 1 Example for reading SU Numbering Convention of : Version Major release = 8 Minor release = 6 Maintenance release = 2 Build = 2 FCS code = 2 SU code = 900 Release candidate = 1 General Rule Syntax: A.B.C.XYzzz-x A = Major Release Number B = Minor Release Number C = Maintenance Release Number X = Feature Branch, FCS and Respin number 0 = "below the line" Feature Branch 1 = FCS base [2-8] = FCS respins 9 = dev build Y = ES / SU releases 0 = FCS / FCS Respin [1-9] = ES (based on zzz) [1-9] = SU (based on zzz) zzz= FCS, ES and SU releases 000 = FCS / respin base = GGSG ES Branch = ES's (never resets) 900 = SU base SU Respins (resets with each SU) Abbrevations FCS - First Customer Shipment ES - Engineering Special SU - Service Upgrade

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 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) Not covered in detail in this session. More detail steps in the appendix L2 RU 15

CUCM Migration 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) 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) Up to 9.1(2) Jump To 9.1(2) Goal: Appliance to Appliance or Virtual Process not upgrade task Bridge - Bridge Upgrade The bridge upgrade provides a migration path for customers who want to migrate from discontinued Cisco Unified Communications Manager server to a server that supports the newest release of Cisco Unified Communications Manager. Servers that are no longer supported, but are permitted to function as bridge upgrade servers, can upgrade and boot but will not allow Cisco Unified Communications Manager to function. When you attempt to upgrade your Cisco Unified Communications Manager version on a discontinued server model, Cisco Unified Communications Manager inserts a message into the upgrade log. The upgrade log is displayed on the web browser when the upgrade is initiated through the Cisco Unified Communications Operating System Administration window, or you can view it through CLI if you used CLI to perform the upgrade. This message notes that you can only use the new version to obtain a DRS backup. The warning message in the log is followed by a delay that allows you to cancel the upgrade if you do not want to do a bridge upgrade. When the system boots the new Cisco Unified Communications Manager version, a warning appears on the console that tells you that the only thing you can do with the new Cisco Unified Communications Manager version is to perform a DRS backup ("This hardware has limited functionality. Backup and Restore is the only supported functionality."). Because of the restricted visibility of the console, the warning displays during both CLI and GUI sessions. PC 16

L2 and RU Upgrade: Appliance to Appliance Model
Updated CUCM SW 1 CUCM Publisher CUCM Publisher 2 Active Partition inActive Partition InActive partition Active partition 3 User Facing Features: Call Forward All (CFA) •Message Waiting Indication (MWI) •Privacy Enable/Disable •Do Not Disturb Enable/Disable (DND) •Extension Mobility Login (EM) •Hunt Group Logout •Device Mobility •CTI CAPF status for end users and application users •Credential hacking and authentication •Recording enabling •Single Number Reach enabling Switch Version via OS Admin or CLI Active Partition inActive Partition InActive partition Active partition CUCM Subscriber CUCM Subscriber 17

L2 and RU Upgrade: Appliance to Appliance Decision Tree
Existing CUCM cluster being upgraded L2 L2 RU Upgrade to same major RHEL version YES Perform a L2 Upgrade L2 N O Started with CUCM 8.6 or RHEL 5 Upgraded CUCM cluster Perform a RU Upgrade 18 18

L2 Upgrade RU Upgrade L2 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 L2 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 RU Upgrade Detailed L2 and RU upgrade process are in the appendix 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 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 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 7816/25/28 H3 (DL320 G5) 7816/25/28 I3 (x3250) 7816/25/28 I4 (x3250 M2) 7816/25/28 I5 (x3250 M3) 7825 H4 (DL320 G5p) 7835/45 H2 (DL380 G5) 7835/45 I2 (x3650) 7835/45 H3 DL380 G6 7835/45 I3 (x3650 M2) 7890C1(Volaris) video/unified-comm-application?view=blog 21

Bridge Upgrade 8.0(2) Upgrade DRS DRS DRS File Servers supported to run CUCM version X Servers supported to be in Bridge mode on CUCM version Y CUCM in a virtualized environment Secure FTP Server Server platform change for discontinued servers that cannot run latest CUCM version Allows for a successful upgrade with Cisco CallManager service in in “Not Running” state Platform change is done with DRS backup and restore Use case include appliance to appliance and appliance to virtualized Requires rehost of license file due to MAC or License MAC change caused by server change For a virtualized environment, use Answer File Generator to proactively obtain license file Cisco Unified Communications Manager Software Compatibility Matrix - Supported Cisco Unified Communications Manager Upgrades for Release 8.0(x) - Direct Upgrade - 7.1(3b)SU2, 7.1(3b)SU1, 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a)SU1, 7.1(2a), 7.1(2), 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 7.0(1)SU1a, 7.0(1)SU1, 7.0(1), 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3), 6.1(2)SU1a, 6.1(2)SU1, 6.1(2) Supported Cisco Unified Communications Manager Upgrades for Release 7.1(3) - Direct Upgrade - 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a) SU1, 7.1(2a), 7.1(2), 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3), 5.1(3g), 5.1(3f), 5.1(3e)2, 5.1(3d), 5.1(3c), 5.1(3b), 5.1(3a), 5.1(3) Direct upgrade using DMA - 4.3(2), 4.2(3), 4.1(3) EOS for EOS for html Bridge Upgrade: 22

Jump Upgrade Upgrade process of multiple steps:
9.1(2) Servers that cannot run CUCM 8.0(2) or later CUCM 9.1(2) in a virtualized environment Jump Upgrade Process 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 23

Jump Upgrade Process * COP file has to be installed before DRS restore
LAB New virtualized CUCM 6.X or 7.X New virtualized CUCM 6.X or 7.X Upgraded virtualized CUCM 9.1(2) Upgraded virtualized CUCM 9.1(2) New virtualized CUCM 9.1(2) New virtualized CUCM 9.1(2) CUCM 6.X or 7.X on MCS Build same CUCM version Upgrade to CUCM 9.1(2) Build new CUCM 9.1(2) DRS Backup DRS Restore * DRS Backup DRS Restore CUCM 6.x or 7.X ISO Image CUCM 9.1(2) ISO Image CUCM 9.1(2) ISO Image sFTP Server sFTP Server sFTP Server sFTP Server 1 2 3 4 5 6 7 * COP file has to be installed before DRS restore 24

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

1. Manual Platform Conversion for 8.0(2) to 9.1(2)
New virtualized CUCM New virtualized CUCM New virtualized CUCM New virtualized CUCM CUCM on MCS DRS Restore on First node or Publisher Install on First node or Publisher Install on Secondary node or Subscriber DRS Backup Upload Licenses CUCM ISO Image All three types of licenses CUCM ISO Image sFTP Server sFTP Server 1 2 3 4 5 Replacing a Single Server or Cluster for Cisco Unified Communications Manager: 26

Upgrade Definition Table (reference)
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 27

Cisco Live 2014 4/13/2017 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 Stay updated. 6.1(3) /earlier or 7.1(2) /earlier introduces another upgrade step to 6.1(5) or 7.1(5) before going to 8.5(1) Staying on dot one release does not help with minimizing upgrade steps Stay updated within a dot one release might minimize upgrade steps and jump major releases Behind on version introduces upgrade steps. i.e. 4 and 5 .zero release of upgrade also introduce one or two upgrade steps i.e. 5.0 Cisco Unified Communications Manager Software Compatibility Matrix - compmatr.html#wp141921 Supported Cisco Unified Communications Manager Upgrades for Release 8.5(1) - compmatr.html#wp278167 Direct Upgrade - 8.0(3a)SU1, 8.0(3a), 8.0(3), 8.0(2c)SU1, 8.0(2c), 8.0(2b), 8.0(2a), 8.0(2), 8.0(1), 7.1(5b)SU3(restricted), 7.1(5b)SU2(restricted), 7.1(5b)(restricted), 7.1(5a)(restricted), 7.1(5)SU1a(restricted), 7.1(5)SU1(restricted), 7.1(5)(restricted), 7.1(3b)SU2, 7.1(3b)SU1, 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 6.1(5)SU2, 6.1(5)SU1, 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4) Supported Cisco Unified Communications Manager Upgrades for Release 8.0(3) - compmatr.html#wp133157 Direct Upgrade - 8.0(2c)SU1, 8.0(2c), 8.0(2b), 8.0(2a), 8.0(2), 8.0(1), 7.1(3b)SU2, 7.1(3b)SU1, 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a)SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 7.0(1)SU1a, 7.0(1)SU1, 7.0(1), 6.1(5)SU2, 6.1(5)SU1, 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3), 6.1(2)SU1a, 6.1(2)SU1, 6.1(2) Supported Cisco Unified Communications Manager Upgrades for Release 7.1(5b) compmatr.html#wp141921 Direct Upgrade - 7.1(5a)(restricted), 7.1(5)SU1a(restricted), 7.1(5)SU1(restricted), 7.1(5)(restricted), 7.1(3b)SU2, 7.1(3b)SU1, 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a) SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 6.1(5)SU2, 6.1(5)SU1, 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3), 5.1(3g), 5.1(3f), 5.1(3e)1 , 5.1(3d), 5.1(3c), 5.1(3b), 5.1(3a), 5.1(3) Direct upgrade using DMA - 4.3(2), 4.2(3), 4.1(3) EOS for /ps556/prod_end-of-life_notice0900aecd806f41d9.html EOS for /ps556/prod_end-of-life_notice0900aecd806ec7a2.html EOS for /ps556/end_of_life_notice_c html EOS for /ps556/prod_end-of-life_notice0900aecd807329a8.html EOS for /ps556/ps7036/end_of_life_notice_c html EOS for d_of_life_notice_c html EOS for /ps556/end_of_life_notice_c html Cisco Unified Communications Manager Software Compatibility Matrix 29

One-Step RU Upgrades (Appliance)
CUCM 6.1(4) CUCM 6.1(5) CUCM 7.1(3) CUCM 7.1(5) RU CUCM 9.X CUCM 8.0(X) Longer downtime Medium upgrade complexity Downgrade for MCS7825 & MCS7828 can be time consuming CUCM 8.5(X) Stay updated. 6.1(3) /earlier or 7.1(2) /earlier introduces another upgrade step to 6.1(5) or 7.1(5) before going to 8.5(1) Staying on dot one release does not help with minimizing upgrade steps Stay updated within a dot one release might minimize upgrade steps and jump major releases Behind on version introduces upgrade steps. i.e. 4 and 5 .zero release of upgrade also introduce one or two upgrade steps i.e. 5.0 Cisco Unified Communications Manager Software Compatibility Matrix - compmatr.html#wp141921 Supported Cisco Unified Communications Manager Upgrades for Release 8.5(1) - compmatr.html#wp278167 Direct Upgrade - 8.0(3a)SU1, 8.0(3a), 8.0(3), 8.0(2c)SU1, 8.0(2c), 8.0(2b), 8.0(2a), 8.0(2), 8.0(1), 7.1(5b)SU3(restricted), 7.1(5b)SU2(restricted), 7.1(5b)(restricted), 7.1(5a)(restricted), 7.1(5)SU1a(restricted), 7.1(5)SU1(restricted), 7.1(5)(restricted), 7.1(3b)SU2, 7.1(3b)SU1, 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 6.1(5)SU2, 6.1(5)SU1, 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4) Supported Cisco Unified Communications Manager Upgrades for Release 8.0(3) - compmatr.html#wp133157 Direct Upgrade - 8.0(2c)SU1, 8.0(2c), 8.0(2b), 8.0(2a), 8.0(2), 8.0(1), 7.1(3b)SU2, 7.1(3b)SU1, 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a)SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 7.0(1)SU1a, 7.0(1)SU1, 7.0(1), 6.1(5)SU2, 6.1(5)SU1, 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3), 6.1(2)SU1a, 6.1(2)SU1, 6.1(2) Supported Cisco Unified Communications Manager Upgrades for Release 7.1(5b) compmatr.html#wp141921 Direct Upgrade - 7.1(5a)(restricted), 7.1(5)SU1a(restricted), 7.1(5)SU1(restricted), 7.1(5)(restricted), 7.1(3b)SU2, 7.1(3b)SU1, 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a) SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 6.1(5)SU2, 6.1(5)SU1, 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3), 5.1(3g), 5.1(3f), 5.1(3e)1 , 5.1(3d), 5.1(3c), 5.1(3b), 5.1(3a), 5.1(3) Direct upgrade using DMA - 4.3(2), 4.2(3), 4.1(3) EOS for /ps556/prod_end-of-life_notice0900aecd806f41d9.html EOS for /ps556/prod_end-of-life_notice0900aecd806ec7a2.html EOS for /ps556/end_of_life_notice_c html EOS for /ps556/prod_end-of-life_notice0900aecd807329a8.html EOS for /ps556/ps7036/end_of_life_notice_c html EOS for d_of_life_notice_c html EOS for /ps556/end_of_life_notice_c html CUCM 8.6(X) Cisco Unified Communications Manager Software Compatibility Matrix 30

Multi-Step Upgrade to CUCM 9.1: Source
RU CUCM 7.1(5b) CUCM 5.1(3) CUCM 9.X 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 - Direct Upgrade Procedure and High Available Upgrade documents - gSet=2089 Cisco Unified Communications Manager Software Compatibility Matrix - compmatr.html#wp141921 Supported Cisco Unified Communications Manager Upgrades for Release 8.5(1) - compmatr.html#wp278167 Direct Upgrade - 8.0(3a)SU1, 8.0(3a), 8.0(3), 8.0(2c)SU1, 8.0(2c), 8.0(2b), 8.0(2a), 8.0(2), 8.0(1), 7.1(5b)SU3(restricted), 7.1(5b)SU2(restricted), 7.1(5b)(restricted), 7.1(5a)(restricted), 7.1(5)SU1a(restricted), 7.1(5)SU1(restricted), 7.1(5)(restricted), 7.1(3b)SU2, 7.1(3b)SU1, 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 6.1(5)SU2, 6.1(5)SU1, 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4) Supported Cisco Unified Communications Manager Upgrades for Release 8.0(3) - compmatr.html#wp133157 Direct Upgrade - 8.0(2c)SU1, 8.0(2c), 8.0(2b), 8.0(2a), 8.0(2), 8.0(1), 7.1(3b)SU2, 7.1(3b)SU1, 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a)SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 7.0(1)SU1a, 7.0(1)SU1, 7.0(1), 6.1(5)SU2, 6.1(5)SU1, 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3), 6.1(2)SU1a, 6.1(2)SU1, 6.1(2) Supported Cisco Unified Communications Manager Upgrades for Release 7.1(5b) compmatr.html#wp141921 Direct Upgrade - 7.1(5a)(restricted), 7.1(5)SU1a(restricted), 7.1(5)SU1(restricted), 7.1(5)(restricted), 7.1(3b)SU2, 7.1(3b)SU1, 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a) SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 6.1(5)SU2, 6.1(5)SU1, 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3), 5.1(3g), 5.1(3f), 5.1(3e)1 , 5.1(3d), 5.1(3c), 5.1(3b), 5.1(3a), 5.1(3) EOS for /ps556/prod_end-of-life_notice0900aecd806f41d9.html EOS for /ps556/prod_end-of-life_notice0900aecd806ec7a2.html EOS for /ps556/end_of_life_notice_c html EOS for /ps556/prod_end-of-life_notice0900aecd807329a8.html EOS for /ps556/ps7036/end_of_life_notice_c html EOS for d_of_life_notice_c html EOS for /ps556/end_of_life_notice_c html End of Sales Notices for CUCM is in the notes section 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 32

CUCM-BE 5K to CUCM-BE 6K or CUCM/CUC
EOS BAT Export BAT Import BAT Data 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 Import data: BAT for CUCM and COBRAS for CUC End of Sales of CUCM-BE 5K /ps7273/end_of_life_notice_c html Migration CUCM-BE 5K to CUCM-BE 6K 33

CUCM License and Cisco Enterprise License Manager (ELM)
Cisco Live 2014 4/13/2017 CUCM License and Cisco Enterprise License Manager (ELM) 3

Foundational Knowledge of CUCM 8.X and Earlier License
Cisco Live 2014 4/13/2017 Foundational Knowledge of CUCM 8.X and Earlier License

CUCM 5.0 to 7.1(3) License Types
TECHNICAL ORDERING Description Node Number nodes per cluster 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 Three license types – DLU, Node and SW Feature Status of each license: Demo, Missing, Invalid, or Uploaded. Shown on login. Version 6.0 or higher is out of the box licensed for 1 node and 50 Version 7.0 or later has a starter license of 3 nodes and 150 36

CUCM 7.1(5) to 8.6 License Types
TECHNICAL ORDERING Description Node UCL/CUWL Number nodes per cluster DLU 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 Three license types – DLU, Node and SW Feature Status of each license: Demo, Missing, Invalid, or Uploaded. Shown on login. Version 6.0 or higher is out of the box licensed for 1 node and 50 Version 7.0 or later has a starter license of 3 nodes and 150 37

License Type and DLU (CUCM 8.6 and earlier)
Comments CUWL Pro 17/12 Prior to January 2012/After January 2012 CUWL Standard 11/8 CUWL Entry 9 Migrate to UCL Enhance Plus in CUCM 9.X and later CUWL Analog 2 Migrate to UCL Essential in CUCM 9.X and later CUWL Public Space 5 Migrate to UCL Enhance in CUCM 9.X and later UCL Enhance 6 UCL Basic 4 UCL Essential UCL Public Space UCL Adjunct UCL TP Single/Multi-screen Migrate to TP Room in CUCM 9.X and later Three license types – DLU, Node and SW Feature Status of each license: Demo, Missing, Invalid, or Uploaded. Shown on login. Version 6.0 or higher is out of the box licensed for 1 node and 50 Version 7.0 or later has a starter license of 3 nodes and 150 38

CUCM 9.X License Conversion
Cisco Live 2014 4/13/2017 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) 40

ELM Architecture 9.1 First node of CUC 1 First node of CUC 2 First node of CUC 3 First Node of CUCM Cluster 1 First Node of CUCM Cluster 2 First Node of CUCM Cluster 3 License Manager API License Manager API License Manager API 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 41

CUCM and ELM Interaction
Evaluate phone, users and features usage Send license usage to ELM Receive license response and operate in the appropriate mode ELM: Poll all products every 24 hours Evaluate adequate licenses Perform license substitution Provide Valid or Invalid license response ELM polls all registered CUCM clusters CUCM evaluates license usage and sends license usage back to ELM ELM evaluate all CUCM responses to see if there is adequate licenses for the requested types 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 42

1 2 3 CUCM License Usage User Phones User / Phone
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 2 Phones Phones without Owner User ID association Based on the phone model 3 User / Phone Phones with Owner User ID association Based on the number of phones assigned to the user 43

CUCM 9.X Phone License Essential UCL 1 EM Basic UCL EM, SNR
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 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 Enhance UCL Plus Same as Enhance UCL 2 Advance UCL becomes Enhance UCL Plus Silver is deleted CUWL Standard went from 2 phones to 10 phones CUWL Premium is deleted 44

CUCM 9.X Phone License CUWL Standard 10 EM, SNR TelePresence 1
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 1 Advance UCL becomes Enhance UCL Plus Silver is deleted CUWL Standard went from 2 phones to 10 phones CUWL Premium is deleted 45

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 1 Based on the model of phone 2 Enhanced UCL Plus 3-10 CUWL Standard Recommend to perform before upgrading to CUCM 9.X 46

Sample CUCM License Usage Send to ELM
Advance UCL becomes Enhance UCL Plus Silver is deleted CUWL Standard went from 2 phones to 10 phones CUWL Premium is deleted 47

ELM License Evaluation and License Substitution
Two license types: User license and Feature license 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 INVALID: inadequate license Centralize and system level licensing view CUWL Standard UCL Enhanced + UCL Enhanced UCL Basic UCL - Essential Take a cluster out or remove devices to be compliance. System view User License Substitution Enterprise License Manager 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. Base on response from ELM or no response from ELM, these are the CUCM license state 49

License Count Tool (UCT):
License Conversion A La Carte DLU UCL 0-6 DLU CUWL 2-17 DLU 1 How can I migrate these license? For CUCM, CUC included with CUWL or standalone CUC Work with Global License Operation (GLO) Manually provide data of current system to get new license file from GLO Documentation of process at: Manual Pool of DLUs 2 How many of what type of licenses do I have? CUCM License: Unity Connection License 186a0080bf5921.shtml Standalone CUC Upgrade CUC to 9.X Self service license request using Product License Registration Documentation of process at: Automated Detailed automated process in the appendix License Count Tool (UCT): 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 ade/uct/CUCM_BK_UCT_Admin_Guide.html CUCM 8.X 51

1. Data for Manual License Migration (recommended)
Working with Global Licensing Operation (GLO) at 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 and support contract MAC Address/License MAC from current CUCM system ELM generated license request to send licenses or software with contact information Intended CUCM 9.X user count and features for unused DLU 52

License Management Models with ELM
CUCM cluster CUCM cluster License Management ELM Stand Alone CUCM cluster CUCM cluster DISTRIBUTED 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 53

Planning and Migration with ELM
1 3 ELM 9.X PLM 10.X CER 2 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 Upgrade ELM 9.X to PLM 10.X Migrate CUCM or CUC to 10.X. Migrate CUCM or CUC license to 10.X Upgrade and add CER to PLM 54

Cisco Live 2014 4/13/2017 Virtualized CUCM 4

Cisco Live 2014 4/13/2017 Platform Support

1 2 Platform Options Tested Reference Configuration (TRC) Specs-Based
C220 M3 B200 M3 1 Tested Reference Configuration (TRC) B230 M2 C240 M3 B440 M2 C260 M2 2 Specs-Based (Software) Supported VMware Servers

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 1 to 2 rack unit UC Virtualization Supported Hardware:

TRC Based Platform Decision Tree
Start FC SAN YES FC SAN or DAS New E5 Processor B200 M3 TRC1 DAS N O YES NO C220 M3 TRC1 NO Low Server Distribution New E5 Processor Low Server Distribution B230 M2 TRC1 N O YES YES C260 M2 TRC1 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 © 2009, Cisco Systems, Inc. All rights reserved. Presentation_ID.scr

Specification-Based Hardware Support
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 required CPU requirements Intel Xeon 5600 or 7500 family with minimum physical core speed of 2.53 GHz Intel Xeon E7-2800, E or E family with minimum physical core speed of 2.4 GHz Intel Xeon E 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 VMware vCenter Server vCenter is mandatory Specification-Based Hardware Support

TRC or Specs-Based Decision Tree
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 be hybrid Start LOW TRC Virtualization Proficiency 1 HIGH TRC YES 1 Performance Guarantee NO TRC UC Applications Supported by Specs-Based NO 1 Unified Communications Virtualization Supported Applications ons_Virtualization_Supported_Applications YES Specs-Based Unified Communications Virtualization Supported Applications: © 2009, Cisco Systems, Inc. All rights reserved. Presentation_ID.scr

Virtualization Support
Cisco Live 2014 4/13/2017 Virtualization Support

Hypervisor Support for Virtualized UC:
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: 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 VMware Pricing: vSphere-and-vCenter-licensing-and-pricing- explained-a-VMWare-license-guide pdf UCS ESXi Software download: o_oem_iso/ZHcqYnRkdHdiZCVodw Hypervisor Support for Virtualized UC: © 2009, Cisco Systems, Inc. All rights reserved. Presentation_ID.scr

Cisco Virtual Template (OVA) File
2 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 Open Virtualization Format (OVF) by the DMTF (Distributed Management Task Force) is a vendor and platform independent format to describe VM meta data (configuration) and creation of VM packages OVF description file (.ovf) is one in a collection of OVF files (workload states, meta files, description file, etc.) describing virtual machine(s) OVA (Open Virtual Archive) is a compressed file (with specific restrictions) that contains all of the OVF files for VM distribution Cisco will provide OVA files on CCO for UC applications deployment on VMware Ease of distribution and deployment for customers Tested VM configurations for each UC applications OVA and OVF files: started/learn/ovf.html/ Search for How to create a virtual appliance Delineation of OVA and OVF: ova-dilemma.html Standard organization: _Tech_Note_Digital.pdf OVA Files for UC on UCS Deployments: © 2009, Cisco Systems, Inc. All rights reserved. Presentation_ID.scr

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 2. MCS servers that can be upgraded to 8.0 in production and migrate. Upgrade to second phase. Choose to migrate. RHEL kernel and implication or Bridge to 8.5.1, DRS, install and DRS restore. Flash cut MCS-7815-I2 !! MCS-7825-H2 !! MCS-7825-I2 !! 65

Prime Collaboration Deployment (PCD)
Cisco Live 2014 4/13/2017 Prime Collaboration Deployment (PCD)

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) Install Data Export COP file Data export to PCD via sFTP Power off CUCM Create virtual machine and install CUCM with data import Management and upload ISO via sFTP 1 CUCM 6.X PCD 2 CUCM 7.X 4 3 There are three cli commands that will be added when COP file is installed. utils system dataexport initiate utils system dataexport cancel utils system dataexport status CUCM 8.X ESXi Host © 2009, Cisco Systems, Inc. All rights reserved. Presentation_ID.scr

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 X Fresh Install Upgrade/COP Install Switch Version Reboot Export Data Hostname/IP Address Change Complex Design Changes: A lot of changes that cannot be execute in one down time: Pub/Subs physical relocations, blade, chassis and sites Pub/Sub distribution, HA Cluster definition for apps NIC teaming CM Group impact IP address changes © 2009, Cisco Systems, Inc. All rights reserved. Presentation_ID.scr

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

1. Manual Platform Conversion
New virtualized CUCM New virtualized CUCM New virtualized CUCM New virtualized CUCM CUCM on MCS DRS Restore on First node or Publisher Install on First node or Publisher Install on Secondary node or Subscriber DRS Backup Upload Licenses CUCM ISO Image All three types of licenses CUCM ISO Image sFTP Server sFTP Server 1 2 3 4 5 Replacing a Single Server or Cluster for Cisco Unified Communications Manager: 70

2. Automated Platform Conversion with PCD
10.X 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 Management and upload ISO via sFTP 1 CUCM 6.X PCD 2 CUCM 7.X 4 3 There are three cli commands that will be added when COP file is installed. utils system dataexport initiate utils system dataexport cancel utils system dataexport status CUCM 8.X ESXi Host © 2009, Cisco Systems, Inc. All rights reserved. Presentation_ID.scr

Platform Migration to Virtualized CUCM 9.1(2)
Platform Number Supported Normal Mode Bridge Not Supported Upgrade Strategy 1 8.0 Jump upgrade 2 3 NA Jump upgrade or upgrade to 8.0 to change platform 4 8.5 5 6 7 Jump upgrade or upgrade to 9.1 to change platform Supported Cisco Unified Communications Manager Releases by Server Jump Upgrade 1. Install new VM 2. Upgrade 3. Install 1. Backup 2. Restore 3. Backup 4. Restore Lab Manual Method 1. Upgrade 1a. Backup 2. Install 2a. Restore 3. Upgrade or Supported Cisco Unified Communications Manager Releases by Server: 72

Cisco Live 2014 4/13/2017 System Level Upgrade 5

UC Application Caveats
Cisco Live 2014 4/13/2017 UC Application Caveats

Attendant Console Considerations for CUCM 9.1
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 Unified Department Attendant Console Cisco Unified Business Attendant Console Cisco Attendant Console Cisco Unified Enterprise Attendant Console Cisco Premium Attendant Console Reverse engineer the CAC link and download the CAC plug in There are a couple of compatibility restrictions to be aware of: 1) CUxAC server OS must be Windows 2008 R1 (not R2) 2) CUCM version must be at least version 8.0(1) End-of-Sale and End-of-Life Announcement for the Cisco Unified Attendant Console::

Cluster Level Upgrade or Migration
Cisco Live 2014 4/13/2017 Cluster Level Upgrade or Migration

Jump Upgrade Process LAB 1 2 3 4 5 6 7 Build same CUCM version
New virtualized CUCM 6.X or 7.X New virtualized CUCM 6.X or 7.X Upgraded virtualized CUCM 9.1(2) Upgraded virtualized CUCM 9.1(2) New virtualized CUCM 9.1(2) New virtualized CUCM 9.1(2) CUCM 6.X or 7.X on MCS Build same CUCM version Upgrade to CUCM 9.1(2) Build new CUCM 9.1(2) DRS Backup DRS Restore DRS Backup DRS Restore CUCM 6.x or 7.X ISO Image CUCM 9.1(2) ISO Image CUCM 9.1(2) ISO Image sFTP Server sFTP Server sFTP Server sFTP Server 1 2 3 4 5 6 7 77

In-Place L2 or RU Upgrade Process
High availability upgrade guide provides detailed steps to minimize outage Existing CUCM Cluster Existing CUCM Cluster Existing CUCM Cluster New CUCM 9.X Cluster New CUCM 9.X Cluster ELM Switch Partition on Publisher Switch Partition on Subscriber Upgrade Publisher Inactive Partition Upgrade Subscribers Inactive Partition Add CUCM to ELM Back Up With DRS sFTP Server or Tape CUCM 9.X DVD Kit CUCM 9.X DVD Kit CLI or OS Admin CLI or OS Admin 1 2 3 4 5 6 78

Migration Option with L2, RU or Jump Upgrade
To minimize outage and allows for migration of large deployment ICT Existing CUCM Cluster ELM New CUCM Cluster New CUCM Cluster New CUCM Cluster New CUCM Cluster Back Up With DRS Add CUCM to ELM Upgrade Inactive Partition Restore With DRS and license files Install CUCM Switch Partition sFTP Server or Tape CUCM DVD Kit sFTP Server or Tape CUCM DVD Kit CLI or OS Admin 1 6 5 4 3 2 79

Upgrade Readiness Assessment Web Tool
Input Mode CUCM Gateway Unity/Unity Connection Automated CURT Reports NA Manual Version and server model Router model 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 Unity/Unity Connection Readiness Summary Software and hardware compatibility Customized Upgrade Procedures Upgrade guide NA Upgrade Readiness Assessment Web Tool Input - Current Environment 1. Cisco Unified Reporting Tool (CURT): Unified CM Cluster Overview Report Unified CM Device Counts Summary Report Or CUCM Release and Server Model 2. Gateways 3. Unity or Unity Connection version and Server Model Output: 1. Readiness Summary 2. Customize Upgrade Procedures Good as a baseline Good for small, medium and some potentially large customers Upgrade Readiness Assessment Web Tool Upgrade Readiness Assessment Web Tool 80

System Level Upgrade or Migration
Cisco Live 2014 4/13/2017 System Level Upgrade or Migration

UC Application Upgrade/ Migration Definition
Upgrade Time Increases with Various Dependencies UC Applications Migration Strategy Pre-Upgrade Migration * CER CUCCE 1 UC Applications Upgrade CUCM Upgrade CUCCX CUP Down Time Down Time MP MPE Post Upgrade Migration * Unity Connection Unity Cisco Unified Communications Manager Software Compatibility Matrix - compmatr.html 2 CUCM Upgrade UC Applications Upgrade * Some UC Application Requires a Complete Reinstall for Upgrade Down Time Replacing a Cisco Unified Communications Manager Software Compatibility Matrix:

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 Jump upgrade Manual method with L2 and RU Migration Target CUCM version 83

Overall Upgrade Strategy to Minimizing Down Time
1 2 3 4 Phase I: Owner User ID / phone association and license request Phase II: IP Phone Firmware Upgrade Phase III: UC Applications Pre-Upgrade Migration Phase IV: CUCM and UC Applications Post Upgrade Migration IP Phone Firmware UC Applications Upgrade CUCM Upgrade 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 UC Applications Upgrade Cisco IP Phone Firmware by CUCM Releases:

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 Readme on PPID for 4.X ser/ccmppid.readme.txt Testing: TFTP Max setting: Windows: Default = 200 Dedicated – 200 Co-located – 50 to 100 5.1(1c) or later Dedicated – 5000 Co-located Help file is 1,500 and 3,000 for single and dual processors Peer-to-Peer Image Distribution (PPID):

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 _2/english/release/notes/7900_852SR1.html (7962 and 4.1(3) upgrade to 7.1(3)) cause phone to upgrade twice With RTMT narrowed down the phones that were running Set the device defaults to SCCP S, reset TFTP, reset only the phones that were running 8.3(2). Once they were all upgraded, set the device defaults to SCCP SR1S, reset TFTP, reset only the phones that were running 8.3(2). CUCM 3.3(5) – 7970 with 6.0(2) CUCM 4.1(2) – 7970 with 6.0(1)0SR1--Need to go to 7.0(3) first CUCM 4.1(3) – 7970 with 6.0(2)SR10s CUCM 7.1(2) – 8.5(2)Need to go to this release prior to any other releases CUCM 7.1(3b) – 8.5(2)SR1 8.0(2) – 9.0(2)SR1 Log of bad upgrade from 8.3(2) to 8.5(2)SR1 NOT 11:22: TLoad: Authenticating loaded file /dnld/SCCP SR1S.loads NOT 11:22: IMG_AUTH: verify: verifying, /dnld/SCCP SR1S.loads NOT 11:22: IMG_AUTH: verify: verify with current RELEASE (built-in) key NOT 11:22: IMG_AUTH: parseHdr(): skipping 1 trail bytes (pad and/or unknown TLVs) ERR 11:22: IMG_AUTH: verifySignedFile(): file hash doesn't match hash in sig ERR 11:22: IMG_AUTH: verify: *** verify with current RELEASE (built-in) key failed *** WRN 11:22: IMG_AUTH: verify: *** no previous RELEASE platform key *** ERR 11:22: IMG_AUTH: verify: *** verify FAILED *** /dnld/SCCP SR1S.loads ERR 11:22: TLoad: imgAuth_vfy: ERROR: code 132: signature decryption/verification failed ERR 11:22: TLoad: Authentication *** FAILED *** code <132><- 1> 7971G-GE, 7970G, 7961G-GE, 7961G, 7941G-GE, 7941G, 7911G, and 7906G 6.0(1)--->7.0(3)--->8.5(2)--->9.0(2) 4.1(2)-CCO---- CCO and not 7.1(3b)---8.0 All other phones 8.3(2)--->8.5(2)--> CUCM 4.1(2)-load from CCO-load CCO (3b)---8.0 Firmware Release Notes 8.5(2)SR1:

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 Reverse engineer the CAC link and download the CAC plug in There are a couple of compatibility restrictions to be aware of: 1) CUxAC server OS must be Windows 2008 R1 (not R2) 2) CUCM version must be at least version 8.0(1)

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 Tools and Commands to check for Connectivity: utils diagnose module validate_network utils network connectivity show network ipprefs all utils firewall list utils network capture Cisco Unified Reporting > CUCM Cluster Overview report In CUCM there's a new command 'utils dbreplication runtimestate show perf query class "Number of Replicates Created and State of Replication What the replication state counter means: 0 = Initialization 1 = Number of replicates is not correct (old sys) 2 = Replication is good 3 = RealTime replication is reporting error 4 = Replication setup failed (this meaning is for 5.1.3, all 6.X and all 7.x versions) On and earlier, RTMT state of 2 is good (same as 6). But on these older versions, a state of 1=still setting up, and state of 3=broken. Unified Reporting – CUCM Database Status CUCM SRND:

Migration Recommendations for CUCM Upgrade
Develop a comprehensive plan for the migration Partners can use PDI Helpdesk for migration plan review Break the upgrade into phases to minimize downtime Open a Global Licensing Operations (GLO) case with specific tags for fast results /30/how-to-get-the-efficient-support-for-drive-to-9 Open a proactive TAC case for the upgrade Check Unified Communications Virtualization docwiki often due to frequent changes 89

Participate in the “My Favorite Speaker” Contest
Cisco Live 2014 4/13/2017 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 Send a tweet and include Your favorite speaker’s 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 Don’t forget to View the official rules at

4/13/2017 Cisco Live 2014

Continue Your Education
Cisco Live 2014 4/13/2017 Continue Your Education Demos in the Cisco Campus Walk-in Self-Paced Labs Table Topics Meet the Engineer 1:1 meetings

Cisco Live 2014 4/13/2017

4/13/2017 Cisco Live 2014

Appendix Questions ? I appreciate your attention today. Thank You! 95

W1 Upgrade: Windows to Appliance Model
Not covered in detail in this session Existing CUCM 4.X Cluster Existing CUCM 4.X Cluster Existing CUCM 4.X Cluster New CUCM 7.1 Cluster 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) Back Up With BARS Install and Run Upgrade Utility on All Servers Install, Run, and Download DMA from Publisher Install CUCM 7.1 Upload DMA File Upload Licenses Repost with 7.1 release notes Latest Upgrade Utility From CCO Data Migration Assistant (DMA) 7.1 CUCM 7.X DVD Kit Node, DLU and 7.1 Feature SW License Tape or Network Share Save DMA File to Tape or Network Share Tape, FTP or sFTP Server Download From CCO 1 2 3 4 5 6 96

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

L2 Upgrade: Appliance to Appliance Model
Active Partition Running InActive partition Dormant InActive partition RPMs installation CUCM installation DB installation Data Migration Active Partition Reboot Firmware and BIOS upgrade 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 98

Refresh Upgrade (RU): Appliance to Appliance Model
Active Partition Running InActive partition Dormant InActive partition Data exported (CUCM and CAR) into /common partition Active Partition Reboot Firmware and BIOS upgrade VOS installation Platform import Reboot InActive partition Dormant Active Partition CUCM installation DB installation CUCM data import CAR DB creation CAR DB migration 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
How and what do CUC, CUCM and ELM communicate? Add CUCM or CUC systems Register 1 2 Success/Fail ELM 5 5 Get License Usage – 24 hours 3 First node of CUCM CUC Usage X,Y,Z Analyze CUC Enforcement CUCM Enforcement Set License Status 4 Get License Capability 6 How does ELM and CUCM and CUC interact 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 100

Process of CUCM and ELM Communications
1 3 2 CUCM License Evaluation ELM License Evaluation 4 How does CUC, CUCM and ELM know what to communicate? [VALID or INVALID ] CUCM evaluates users to phones usage and feature usage to derives at UCL/CUWL usage CUCM sends UCL/CUWL usage to ELM 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 Put together slide 101

Using User Count Tool as Planning Tool to Migrate
1 2 Cluster > Add: Add system in User Count Tool (UCT) using IP/hostname of system and AXL credential Cluster: Ensure that system connected successfully Check versions of CUCM that the tool detects 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) 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 104

1 2 License Conversion Manual Automated
A La Carte DLU UCL 0-6 DLU CUWL 2-17 DLU 1 How can I migrate these license? Manual For CUCM, CUC included with CUWL or standalone CUC Work with Global License Operation (GLO) Manually provide data of current system to get new license file from GLO Documentation of process at: Pool of DLUs 2 How many of what type of licenses do I have? CUCM License: Unity Connection License 186a0080bf5921.shtml Automated Standalone CUC Upgrade CUC to 9.X Self service license request using Product License Registration Documentation of process at: 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 ade/uct/CUCM_BK_UCT_Admin_Guide.html CUCM 8.X 106

1. Data for Manual License Migration
Working with Global Licensing Operation (GLO) at 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 and support contract MAC Address/License MAC from current CUCM system ELM generated license request to send licenses or software with contact information Intended CUCM 9.X user count and features for unused DLU 107

2. Automated License Migration with ELM
Product Upgrade Tool site Contract Number CUCM 9.X software Upgrade CUCM cluster Log into Product Upgrade Tool site = 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 108

2. Automated License Migration with ELM
CUCM License Request Product License Registration site 1 3 Text from ELM License Request ELM License file New upgraded CUC 9.X ELM 2 1. In ELM, add the new upgraded CUC 9.X and get upgrade license request 2. In ELM Upgrade wizard: License Management > Add or Upgrade Licenses > Upgrade Licenses Go through license planning for UCL and CUWL request based on DLU Capture license request text 3. Go to: Product License Registration site = Go to Migration License section and select Register for Upgrade/Migrate License amp-A-Migrate-License-to-CUCM-9/ta-p/86580 109

Overview of CUCM 9.1 Installation
MCS-781X MCS7825 MCS7828 MCS7835 MCS7845 CUCM 9.X DVD KIT INSTALLATION PROCESS (PROCEED) 1 2 Apply SR, ES or SU Basic Install Upgrade During Installation i.e., 9.1(1a) to 9.1(2) New Installation, New Server—Flash Cut or New Server—Migration 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 Download 7zip from to unzip the tar file Remove serial port after a successful installation of Unified CM 8.X 111

4/13/2017 Cisco Live 2013

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.

Similar presentations

Presentation on theme: "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."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

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.

Similar presentations

Presentation on theme: "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."— Presentation transcript:

Similar presentations

About project

Feedback