You are on page 1of 112

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

3

You can find additional information via Cisco’s World Wide Web server at http://www.cisco. BRKUCC-2011 © 2014 Cisco and/or its affiliates. Actual performance and environmental costs of Cisco products will vary depending on individual customer configurations and conditions. All rights reserved. Cisco Public 4 . 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.Required GAAP Reconciliation and Forward-Looking Statements The Cisco products. Consult your local Cisco business contact for information on the products or services available in your area.com.

Agenda • Session Objectives and Scope • CUM 10. All rights reserved. Cisco Public 5 .5 Upgrade Definition and Upgrade Path • CUCM License and Prime License Manager (PLM) • Virtualized CUCM • System Level Upgrade • Q&A BRKUCC-2011 © 2014 Cisco and/or its affiliates.

Session Highlights Licensing and License Migration CUCM Migration Prime Collaboration Deployment (PCD) CUCM 10. COP file installation. fresh installation or hostname/IP Address change • Platform conversion • Highlight 10. • Manual process • Automated process • Traditional manual process • Automated process with PCD • Automated tool for operation tasks • CUCM upgrade.X through out this presentation Cisco Public 6 . All rights reserved.X Virtualized only BRKUCC-2011 © 2014 Cisco and/or its affiliates.

Session Objectives and Scope 1 .

Color Code for Versions of CUCM CUCM 5.X CUCM 7.X CUCM 9.X CUCM 6.X Virtualized CUCM 8. All rights reserved. Cisco Public 8 .X CUCM 8.X Virtualized CUCM 10.X BRKUCC-2011 © 2014 Cisco and/or its affiliates.X and 9.

All rights reserved.Session Objectives • To provide foundational knowledge for a successful upgrade or migration to CUCM 10. Cisco Public 9 .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 © 2014 Cisco and/or its affiliates.

5 CUCM 7.X CUCM 10.Session Scope CUCM 6.1(X)  Covers in detail selected versions of CUCM that has a direct one step upgrade to CUCM 10.pdf BRKUCC-2011 © 2014 Cisco and/or its affiliates.x http://www.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.com/c/en/us/td/docs/voice_ip_comm/cucm/compat/matrix/10_x/CUCM_BK_CD1DB914_00_compat_matrix.1(X) CUCM 8.cisco. All rights reserved. Cisco Public 10 Servers NEW .

CUM 10.5 Upgrade Definition and Upgrade Path 2 .

Upgrade Definition .

CUCM Major/Minor Version CUCM Major Version CUCM Minor Version 10.0 6.1 5.0 7.0 9.1 8.0 10. All rights reserved.6 7. 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 .5 9.1 BRKUCC-2011 © 2014 Cisco and/or its affiliates.0 8.0 5.5 and 8.1 6.

0.6.10000-2 8.5(1) 10.6.6.10000-30 (FCS) 8.6.2.2.1. rel.C.1.2.22900-1 (SU) Cisco Public 14 Reference .2.20000-2 (B) Minor version 10.6.Sample CUCM Versions and Builds CUCM Version CUCM Build 10.1.2.1.2.2.2.10000-7 10.5.10000-28 (X) Build 9.0.6(2a)su1 8.2.10000-11 9.2.B.1(1) 9.6.1.6.2.0(1) 9.6(2a) 8.6.10000-24 9.6.20000-2 (FCS) 8.20000-2 (Y) FCS:0.0(1)su1 NEW Numbering Convention (A.2. ES or SU: 1-9 8. 9.6.21900-5 8.10000-37 8. SU: 900-999 8.1(2) 9.21001-1 (ES) 8.11900-2 8.1.1(2)su1 9.0(1) 10.2.2.0.2.6.20000-2 8.1.22900-1 (ES or SU look at last three digits) (zzz) FCS:000.1.6(2a)su2 8.11900-12 (C) Maint.22900-9 8.6.10000-30 BRKUCC-2011 © 2014 Cisco and/or its affiliates.XYzzz-x) (A) Major version 10.1(1a) 9. ES: 001-899.20000-2 8. 8.20000-2 8.1.2.6.1.20000-5 9. All rights reserved.6.6(2) 8.

8.6. 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 and 10.1(3). 7. or 4. 4.1 to 10.g.2(3). CUCM 4.g.0 or 8.X.g.0) BRKUCC-2011 © 2014 Cisco and/or its affiliates.CUCM Upgrade Definition W1 W1 Upgrade: Windows to Appliance model  High complexity with possible longest downtime  (e.1(5) to 8.5 to 8. CUCM 8.5 or CUCM 8.6 to 9.X  (e.1(5b)) L2 RU Not covered in detail in this session.6 or CUCM 9.3(2) to 7.5 to 8. All rights reserved. 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. Cisco Public 15 . CUCM 7.X.

6.1(5) for lab upgrade  Minimal downtime due to lab upgrade  (e.1(3) and 7. Cisco Public 16 1 To 9.X.0 or 8.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. 7.1(5).X and 10.X) BRKUCC-2011 Up to ) 9.1(4). 1( 2 © 2014 Cisco and/or its affiliates.6.X.X  (e. (2 ) .g. Older servers that cannot support the latest CUCM or CUCM 10. Older servers that cannot newer version of CUCM) Jump PC Jump Upgrade: Appliance to Virtualized model  Virtualized CUCM with 6. All rights reserved.0(3) or later to virtualized) Platform Change: Appliance to Virtualized model  Low complexity with minimal downtime  From CUCM versions 6. Older servers that cannot upgrade to 8. 9. 8.g. 7.5 to 8.g.

All rights reserved. inActive Partition Active partition CUCM Subscriber Cisco Public 17 .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 © 2014 Cisco and/or its affiliates.

6 or RHEL 5 18 .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 © 2014 Cisco and/or its affiliates. All rights reserved. L2 Upgrade to same major RHEL version Upgraded CUCM cluster Cisco Public 18 Started with CUCM 8.

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 © 2014 Cisco and/or its affiliates. Cisco Public 19 . All rights reserved.

HP ILO.1. All rights reserved.5 or earlier to allow for successful upgrade and limit switch version after upgrade • COP file is NOT required for CUCM version 8.X BRKUCC-2011 © 2014 Cisco and/or its affiliates.Refresh Upgrade (RU) Recommendations • Perform a DRS back up before upgrade • Track console of server to monitor progress of upgrade – IP KVM.refresh_upgrade_v1.cop.sgn) file on CUCM version 8. 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. or IBM RSA for bare metal server or virtual machine console for virtual machine • To minimize downtime. Cisco Public 20 .6 or later to upgrade to 9.

All rights reserved.Refresh Upgrade (RU) for MCS 7825 and MCS 7828 (CUCM 9. CUC and CUCM BE 5000 – 128 GB USB drive – External power USB drive. Cisco Public 21 .16 GB USB drive.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. MCS7828 – 6GB) before upgrade BRKUCC-2011 © 2014 Cisco and/or its affiliates. USB data cannot be restore from new installation • Reinstallation and DRS restore as the only reversion method • Check memory required per server (MCS7825 – 4GB. One per server. Do not remove until upgrade completes • DRS back up before upgrade.

Cisco Public 22 ) . use Answer File Generator to proactively obtain license file Bridge Upgrade: http://www.8.com/en/US/docs/voice_ip_comm/cucm/cucos/8_0_2/cucos/iptpch7.cisco.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. All rights reserved.html#wp1058411 BRKUCC-2011 © 2014 Cisco and/or its affiliates.

1(2) in a virtualized environment • Upgrade process of multiple steps: – Upgrade from CUCM 6. 7.1(2) ONLY – Lab migration ONLY • Allows virtualization of CUCM at 6.1(5).1(4).1(5) ONLY – Upgrade to CUCM 9.1(4). 6.1(3) or 7. All rights reserved.1(2 Jump Upgrade Servers that cannot run CUCM 8. 7.1(3) or 7.0(2) or later Jump Upgrade Process CUCM 9. Cisco Public 23 ) .1(5).1(5) in the lab for the purpose platform change and CUCM 9.9.1 upgrade – Minimal down time – Database lockdown time – No license required for interim upgrades BRKUCC-2011 © 2014 Cisco and/or its affiliates. 6.

Cisco Public BRKUCC-2011 Upgraded virtualized CUCM 9.X Upgrade to CUCM 9.1(2) ISO Image 6 sFTP Server 7 .X Build same CUCM version DRS Backup sFTP Server 1 New virtualized CUCM 6.X on MCS New virtualized CUCM 6.1(2) Build new CUCM 9.x or 7.1(2) sFTP Server 3 CUCM 9.X ISO Image 2 Upgraded virtualized CUCM 9.Jump Upgrade Process LAB CUCM 6. All rights reserved.1(2) ISO Image 4 New virtualized CUCM 9.X or 7.X or 7.1(2) DRS Restore * CUCM 6.X or 7.1(2) DRS Restore CUCM 9.1(2) DRS Backup * COP file ©has to be installed before DRS restore 24 2014 Cisco and/or its affiliates.1(2) sFTP Server 5 New virtualized CUCM 9.

E. x Cisco Public Server Hardware CPU 25 Memory NIC Storage .X 1. Automated with Prime Collaboration Deployment (PCD – in later slides) NE W CPU NE W Memory NIC 1 2 Drive © 2014 Cisco and/or its affiliates. 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. 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)  Two approaches to this platform conversion  I.CUCM Platform Conversion PC Platform Conversion: Bare metal CUCM to virtualized CUCM (Required for CUCM 10. Manual 2. All rights reserved.

Manual Platform Conversion for 8.html BRKUCC-2011 © 2014 Cisco and/or its affiliates. All rights reserved.cisco.com/en/US/docs/voice_ip_comm/cucm/install/8_5_1/cluster/clstr851.0(2) to 9.1.1(2) CUCM on MCS New virtualized CUCM Install on First node or Publisher DRS Backup sFTP Server 1 New virtualized CUCM DRS Restore on First node or Publisher CUCM ISO Image 3 New virtualized CUCM Install on Secondary node or Subscriber Upload Licenses sFTP Server 2 New virtualized CUCM All three types of licenses 4 CUCM ISO Image 5 Replacing a Single Server or Cluster for Cisco Unified Communications Manager: http://www. Cisco Public 26 .

Use DRS file to change platform to continue upgrade Jump Upgrade Servers too old to run CUCM version 8.Upgrade Definition Table (reference) Upgrade Definition Scenario W1 Upgrade Windows to appliance upgrade up to CUCM 7.6) Bridge Upgrade Servers too old to run latest CUCM version.0(2) or later to virtualized.6) RU Upgrade Appliance to appliance upgrade between major RHEL releases (starting with CUCM 8.1(5) L2 Upgrade Appliance to appliance upgrade within same major RHEL release (before CUCM 8. All rights reserved. Cisco Public 27 . Typically from bare metal servers to virtualized environment BRKUCC-2011 © 2014 Cisco and/or its affiliates. Virtualized in lab to perform upgrade Platform Change Changing servers platform.

Upgrade Path .

com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.X • Short or minimal downtime Cisco Unified Communications Manager Software Compatibility Matrix http://www. All rights reserved. Cisco Public 29 .One-Step L2 Upgrades (Appliance) CUCM 8.html#wp278167 BRKUCC-2011 © 2014 Cisco and/or its affiliates.X • The CUCM versions that will support a L2 upgrade to 9.cisco.X CUCM 9.6(X) L2 CUCM 9.

html#wp278167 BRKUCC-2011 © 2014 Cisco and/or its affiliates.1(3) CUCM 7.0(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.One-Step RU Upgrades (Appliance) CUCM 6.1(5) CUCM 7. Cisco Public 30 .1(4) CUCM 6. All rights reserved.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.1(5) CUCM 8.cisco.5(X) CUCM 8.

1: Source L2 CUCM 5.cisco.pdf – Direct Upgrade Procedure and High Available Upgrade documents https://communities.com/community/partner/collaboration/migration?view=overview#/? tagSet=2089 End of Sales Notices for CUCM is in the notes section BRKUCC-2011 © 2014 Cisco and/or its affiliates.X • Sources for multi-steps upgrade path: – Cisco Unified Communications Manager Software Compatibility Matrix .cisco. All rights reserved.1(3) RU CUCM 9.Supported upgrade paths to/from table http://www.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr1.Multi-Step Upgrade to CUCM 9.1(5b) • For end of support and appliance versions of CUCM • Focus on the interim versions that can be upgraded to 9.X CUCM 7. Cisco Public 31 .

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 © 2014 Cisco and/or its affiliates. 7.E. Cisco Public 32 . All rights reserved.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.Multi-Step Upgrade to CUCM 9.

All rights reserved. Cisco Public 33 .1 COBRAS Export COBRAS Data COBRAS Import • Upgrade CUCM-BE to version CUCM-BE 9.com/docs/DOC-33988 • Import data: – BAT for CUCM and COBRAS for CUC BRKUCC-2011 © 2014 Cisco and/or its affiliates.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.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.

CUCM License and Cisco Enterprise License Manager (ELM) 3 .

X and Earlier License .Foundational Knowledge of CUCM 8.

type of phones.0 to 7. All rights reserved. Cisco Public 36 . Device License Unit (DLU) and Software Feature license  Node license is enforced based on the number of node running CM service. type of phones. mobility feature and presence users SW Feature ESW/UCSS Maintenance for minor and major version upgrade  Three license types: Node. TFTP and MOH also requires node licenses  DLU is enforced based on provisioned phones.CUCM 5. 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 © 2014 Cisco and/or its affiliates.1(3) License Types TECHNICAL ORDERING Description Node Node Number nodes per cluster DLU DLU Number of phones.

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 © 2014 Cisco and/or its affiliates.6 License Types TECHNICAL ORDERING Description Node UCL/CUWL Number nodes per cluster DLU UCL/CUWL Number of phones. licenses are locked to MAC address of the first node or Publisher of the cluster  In virtualized environment. DLU and Software Feature license. All rights reserved. Device based  Ordering is based on User based  For bare metal servers (MCS). type of phones. Cisco Public 37 .1(5) to 8.CUCM 7. 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.

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 9 Migrate to UCL Enhance Plus in CUCM 9. All rights reserved.X and later UCL TP Single/Multiscreen 6 Migrate to TP Room in CUCM 9.License Type and DLU (CUCM 8.X and later UCL Enhance 6 UCL Basic 4 UCL Essential 0 UCL Public Space 5 Migrate to UCL Enhance 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 Adjunct 5 Migrate to UCL Enhance in CUCM 9.X and later BRKUCC-2011 © 2014 Cisco and/or its affiliates. Cisco Public 38 .

CUCM 9.X License Conversion .

All rights reserved.Cisco Enterprise License Manager (ELM) CUCM + CUELM CUC + CUELM CUCM BE 5K CUCM BE 3K CUELM  CUCM 9. Cisco Public 40 .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 © 2014 Cisco and/or its affiliates.

ELM Architecture 9. Cisco Public 41 .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. 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. All rights reserved. license pooling.0 to interact with ELM for license request and approval  ELM provides for centralize license management.0 and above BRKUCC-2011 © 2014 Cisco and/or its affiliates.0 and CUC 9.

CUCM and ELM Interaction  ELM polls all registered CUCM clusters  CUCM evaluates license usage and sends license usage back to ELM CUCM: • Evaluate phone. All rights reserved. Cisco Public 42 . 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 © 2014 Cisco and/or its affiliates.

1(1a) and later  Extension mobility user with Unified Mobility feature uses one UCL Basic license 1 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 © 2014 Cisco and/or its affiliates. Cisco Public 43 . All rights reserved.CUCM License Usage BRKUCC-2011  Extension mobility users uses no license for CUCM 9.

CUC-RTX. 7961G-GE. 7931. # of Devices (3) Cisco Public 44 Features (1) . 7985. 6911. 9951. 6945. 7926. 3911. 7925. 7912. ATA187 . ATA187 1 EM. 6901. 7906. 30SP+. 7971. 6901. Jabber (Android/iPhone/iPpad). 7940. 7935. 30VIP.CUCM 9. E20. 3905. 9971. 7921. 3905. 7911. VGC Phone. VXC 6215. ATA186.X Phone License License Phone Type (2) Essential UCL Analog. Third-party SIP Device. 7902. 6921. CUPC. ATA186. 7941G-GE. H. 7965. 12SP. 3905. 8941. Analog. ATA187 1 EM Basic UCL 6911. SNR Enhance UCL 12S. 7961. 7945. 3905. Analog. ATA187 1 EM. 8945. CIM. 7920. 12SP+. All rights reserved. CIPC. 6921. 7941. 7937. Nokia S60. 7970. EX60. 8961. VGC Phone. ISDN BRI Phone. 7960. 6901. 7942. 7936. 6941. IIM. SNR BRKUCC-2011 © 2014 Cisco and/or its affiliates. Cius. 7975. 6901. 7910. VGC Phone. 3951. ATA186. ATA186. CSF. Analog. VGC Phone.323 Client. CUC-RTX. 7905. EX90. 7962. 6961. SNR Enhance UCL Plus Same as Enhance UCL 2 EM. CUMC.

CIPC. EX90. 7965. 7962. 7911. CSF.CUCM 9. E20. Nokia S60. 7941. 7935. 7960. 8961. Analog. 7970. 6941. CUMC. 7941G-GE. 3911. 7902. 7985. ATA186. 6961. SNR . 7937. ISDN BRI Phone. 6911. 9951. 6945. 7920. 7961. 6901. 7940. 30SP+. CUC-RTX. 7942. 7931. Analog. ATA187 . 7971. 9971. IIM. 30VIP. Jabber (Android/iPhone/iPpad). VGC Phone. # of Devices (3) 10 1 Cisco Public 45 Features (1) EM. Cius. 3905. 8945. 7910. 3951. VGC Phone. 7936. 7912.323 Client. ATA187 TelePresence TelePresence BRKUCC-2011 © 2014 Cisco and/or its affiliates. 7906. 6901. 8941. CUPC. VXC 6215. 7945. EX60. 7926. Third-party SIP Device. 3905. 7925. 7921. ATA186. All rights reserved. 7905. 12SP. H. 7975.X Phone License License Phone Type (2) CUWL Standard 12S. CIM. 12SP+. 6921. 7961G-GE.

Cisco Public 46 .Phones and Owner User ID Association Device > Phone > Device Name  Phones with Owner User ID field configured potentially uses less licenses  I. Extension mobility user with Unified Mobility feature and a phone uses one license  I.E.X BRKUCC-2011 © 2014 Cisco and/or its affiliates. All rights reserved. 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.E.

Sample CUCM License Usage Send to ELM

BRKUCC-2011

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

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

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

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

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

Cisco Public

49

com/download/release. All rights reserved.cisco.com  Manually provide data of current system to get new license file from GLO  Documentation of process at: https://communities.X Self service license request using Product License Registration Documentation of process at: http://www.License Conversion CUWL 2-17 DLU UCL 0-6 DLU A La Carte DLU How can I migrate these license? 1 Manual Pool of DLUs How many of what type of licenses do I have? 2 Automated Detailed automated process in the appendix  For CUCM.cisco. CUC included with CUWL or standalone CUC  Work with Global License Operation (GLO) licensing@cisco.com/en/US/products/ps6509/products_tec h_note09186a0080bf5921.com/docs/DOC-33804     Standalone CUC Upgrade CUC to 9. Cisco Public 50 .shtml License Count Tool (UCT): http://software.cisco.html?mdfid=283782839&softwareid=282204704&release=UCT&relind=AVAILABLE&rellifecycle=&reltype=latest BRKUCC-2011 © 2014 Cisco and/or its affiliates.

X-8. Cisco Public 51 . All rights reserved.X BRKUCC-2011 © 2014 Cisco and/or its affiliates. recommends CUCM 9.X  Available on CCO  Perform AXL calls to existing CUCM clusters for licensing information. CUCM 6.X Detailed screen capture of UCT are in the appendix CUCM 7. provides option for unused DLU to CUCM 9.X license and generate report.X license usage.X License Count Tool CUCM 8.License Count Utility (UCT) for CUCM 6.

X to 5.X to 8. count and Cisco Public features for unused DLU .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.user All rights reserved.X: License Report with License Count Utility (UCT) – CUCM 3.X affiliates.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.

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 © 2014 Cisco and/or its affiliates.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. Cisco Public 53 . All rights reserved.

X • Changes to Cisco Enterprise License Manager (ELM) – Cisco Enterprise License Manager (ELM) 9. Migrate CUCM or CUC license to 10.X CUCM 10.X – Cisco Emergency Responder support PLM 10. Cisco Public .X will be renamed to Cisco Collaboration Prime License Manager (PCLM) 10.Planning and Migration with ELM 1 3 ELM 9.X CUC 9.X CER PLM 10.X 3.X 2 CUCM 9.X CUCM 9. Upgrade ELM 9.X • Migrating ELM 1.X CUC 9. Upgrade and add CER to PLM 54 BRKUCC-2011 © 2014 Cisco and/or its affiliates.X CUC 10.X CUC 9.X CUCM 9. Migrate CUCM or CUC to 10.X 2. All rights reserved.X to PLM 10.X.

Virtualized CUCM 4 .

Platform Support .

Cisco Public 57 Servers B230 M2 B440 M2 . All rights reserved.Platform Options 1 Tested Reference Configuration (TRC) 2 Specs-Based (Software) C220 M3 B200 M3 C240 M3 C260 M2 VMware Supported BRKUCC-2011 © 2014 Cisco and/or its affiliates.

C240 M3 and C260 M2 – DAS only UC Virtualization Supported Hardware: – 1 to 2 rack unit http://docwiki. B230 M2 and B440 M2 – FC SAN only – Full width versus half width blade • Rack-Mount: – C220 M3. Cisco Public 58 .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.com/wiki/UC_Virtualization_Supported_Hardware BRKUCC-2011 © 2014 Cisco and/or its affiliates. All rights reserved.cisco.

All rights reserved. Cisco Public 59 .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 © 2014 Cisco and/or its affiliates.

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.com/wiki/Specification-Based_Hardware_Support BRKUCC-2011 © 2014 Cisco and/or its affiliates. All rights reserved.Specs-Based Hardware • Customers with extensive virtualization proficiency • Maximum hardware choices including Cisco.cisco.4 GHz Intel Xeon E5-2600 family with minimum physical core speed of 2. Cisco Public 60 .5 GHz Leverage TRC as a baseline for CPU model DAS only. E7-4800 or E7-8800 family with minimum physical core speed of 2. DAS & FC SAN or FC SAN only Specification-Based Hardware Support http://docwiki.53 GHz Intel Xeon E7-2800.

Cisco Public 61 . but can hybrid Unified Communications Virtualization Supportedbe Applications: http://docwiki. CTS Manager) • Cisco WebEx Meeting Server • Solution should be consistent.cisco. All rights reserved.com/wiki/Unified_Communications_Virtualization_Supported_Application BRKUCC-2011 © 2014 Cisco and/or its affiliates. noticeably • Contact Center • TelePresence (CTMS.TRC or Specs-Based Decision Tree Start Virtualization Proficiency LOW TRC 1 HIGH Performance Guarantee YES TRC NO TRC 1 NO UC Applications Supported by Specs-Based 1 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.

Virtualization Support .

license management.0. Partner or VMware – https://www. etc. Standard. Foundation or Standard) – Recommended for large deployment.com/files/pdf/vsphere_pricing.0 and 5. – Mandatory for Specs-Based deployment • VMware acquisition: Cisco.vmware.1 (with some specific UC application exceptions) – VMware vSphere Hypervisor. All rights reserved.com/web/vmware/info/slug/datacenter_cloud_infrastructure/vm ware_vsphere/5_0#drivers_tools • VMware vCenter (Essential. 5.vmware.VMware Sphere Support • ESXi 4. 4.com/wiki/Unified_Communications_VMWare_Requirements BRKUCC-2011 © 2014 Cisco and/or its affiliates.1. centralize management.pdf Hypervisor Support for Virtualized UC: http://docwiki.cisco. Enterprise or Enterprise Plus – ISO for Cisco UCS and third party for appropriate driver support is at: • https://my. Essential. Cisco Public 63 . Essential Plus. Acceleration Kit.

1 or 5.0 – VMV 8 = ESXi 5.0.0 ( To upgrade.cisco.Cisco Virtual Template (OVA) File OVA CCO 2 1 vSphere Client UCS B200 M3 • Open Virtual Archive (OVA): Portable virtual appliance that defines configuration (memory. right click and select upgrade virtual hardware). All rights reserved. 4. Cannot be downgraded to 7 OVA Files for UC on UCS Deployments: http://docwiki. Cisco Public 64 .com/wiki/Unified_Communications_Virtualization_Downloads_(including_OVA/OVF_Templates) BRKUCC-2011 © 2014 Cisco and/or its affiliates. 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.

All rights reserved. Cisco Public 65 .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 © 2014 Cisco and/or its affiliates.

Prime Collaboration Deployment (PCD) .

Prime Collaboration Deployment (PCD) 1 CUCM 6. Create virtual machine and install CUCM with data import ESXi Host BRKUCC-2011 © 2014 Cisco and/or its affiliates.X 3 PCD 4 1.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. Install Data Export COP file 2.X 3. Data export to PCD via sFTP CUCM 8. Power off CUCM 4. Cisco Public 67 . All rights reserved.X (see next slide for all features) 2 CUCM 7.

x Migration to 10. All rights reserved. X X Cisco Public 68 .1(5) CUCM 7.1(3)-7.6(1-2) CUCM 9.Prime Collaboration Deployment (PCD) Feature CUCM 6.1(5) CUCM 8.5(1) CUCM 8.x CUCM 10.0(1-3) CUCM 8.X X X X X X X X Fresh Install X Upgrade/COP Install X X X Switch Version X X X Reboot X X X X X X Export Data X X X Hostname/IP Address Change BRKUCC-2011 © 2014 Cisco and/or its affiliates.

X)  Two approaches to this platform conversion 1. CPU Cisco Public 69 Memory NIC Storage . 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 © 2014 Cisco and/or its affiliates. All rights reserved. Manual 2.CUCM Platform Conversion PC Platform Conversion: Bare metal CUCM to virtualized CUCM (Required for CUCM 10.

cisco.1. Cisco Public 70 . Manual Platform Conversion CUCM on MCS New virtualized CUCM Install on First node or Publisher DRS Backup sFTP Server 1 New virtualized CUCM DRS Restore on First node or Publisher CUCM ISO Image 3 New virtualized CUCM Install on Secondary node or Subscriber Upload Licenses sFTP Server 2 New virtualized CUCM All three types of licenses 4 CUCM ISO Image 5 Replacing a Single Server or Cluster for Cisco Unified Communications Manager: http://www.html BRKUCC-2011 © 2014 Cisco and/or its affiliates. All rights reserved.com/en/US/docs/voice_ip_comm/cucm/install/8_5_1/cluster/clstr851.

X nd a t a en vi em ISO g a d P an loa sFT M up 2 CUCM 7.X and 10. Cisco Public 10. 7.1(3). All rights reserved.2.1(5). 9. Automated Platform Conversion with PCD 1 CUCM 6.X  Can be a migration by using new set of IP address for virtualized CUCM 4 CUCM 8.1(5).X 3 PCD  Only can be use with upgrades to CUCM 10.X with this platform change  Only from CUCM version 6. 8.0(1-3). 7. X 71 .X ESXi Host BRKUCC-2011 © 2014 Cisco and/or its affiliates. 8.6(1-2).

5-9.1 NA Jump upgrade or upgrade to 8.5 8.0 to change platform 7 7.0 NA 8.5-9.1 NA Jump upgrade or upgrade to 8.0 to change platform 5 6.1-7.1 Jump upgrade or upgrade to 8.5-9.0 8.1-8.0 to change platform 4 6. Cisco Public 72 .1-8.1 8.6-9.0 to change platform 6 6.0-8.1 to change platform Supported Cisco Unified Communications Manager Releases by Server: http://www.html BRKUCC-2011 © 2014 Cisco and/or its affiliates.1 Jump upgrade 3 6.cisco.1-8.1 8.1(2) Platform Number Supported Normal Mode Supported Not Bridge Supported Upgrade Strategy 1 6.1 Jump upgrade 2 6.5 8.0 8.Platform Migration to Virtualized CUCM 9.5 8.1 Jump upgrade or upgrade to 8.1 NA NA Jump upgrade or upgrade to 9.1-8.0 8.1-9.6-9.5-9. All rights reserved.1-7.com/en/US/partner/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd8062a4f9.

System Level Upgrade 5 .

UC Application Caveats .

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.html BRKUCC-2011 © 2014 Cisco and/or its affiliates.com/en/US/prod/collateral/voicesw/ps6789/ps7046/ps7282/end_of_life_notice_c51-499091.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. All rights reserved. Cisco Public 75 .cisco.Attendant Console Considerations for CUCM 9.

Cluster Level Upgrade or Migration .

X ISO Image © 2014 Cisco and/or its affiliates.1(2) ISO Image sFTP Server 2 Upgraded virtualized CUCM 9.1(2) DRS Backup CUCM 9. All rights reserved.x or 7.1(2) 77 New virtualized CUCM 9. 3 4 Cisco Public Upgraded virtualized CUCM 9.X or 7.1(2) sFTP Server 5 New virtualized CUCM 9.X on MCS Build same CUCM version DRS Backup sFTP Server 1 BRKUCC-2011 New virtualized CUCM 6.X or 7.Jump Upgrade Process LAB CUCM 6.X New virtualized CUCM 6.1(2) DRS Restore CUCM 6.X or 7.1(2) Build new CUCM 9.1(2) ISO Image 6 sFTP Server 7 .X Upgrade to CUCM 9.1(2) DRS Restore CUCM 9.

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. Switch Partition on Subscriber CLI or OS Admin 4 5 78 ELM Add CUCM to ELM CLI or OS Admin 3 Cisco Public New CUCM 9.X DVD Kit New CUCM 9.X Cluster 6 High availability upgrade guide provides detailed steps to minimize outage .X Cluster Existing CUCM Cluster Switch Partition on Publisher Upgrade Subscribers Inactive Partition CUCM 9.X DVD Kit 2 © 2014 Cisco and/or its affiliates. All rights reserved.

All rights reserved. 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 © 2014 Cisco and/or its affiliates.Migration Option with L2. 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 4 3 2 To minimize outage and allows for migration of large deployment .

com/cucst/upgrade/index. Cisco Public 80 Unity/Unity Connection Upgrade guide . All rights reserved.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.jsp BRKUCC-2011 © 2014 Cisco and/or its affiliates.cisco.

System Level Upgrade or Migration .

All rights reserved.UC Application Upgrade/ Migration Definition Upgrade Time Increases with Various Dependencies UC Applications CER CUCCE CUCCX CUP Migration Strategy 1 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 * 2 CUCM Upgrade UC Applications Upgrade Down Time Replacing a Cisco Unified Communications Manager Software Compatibility Matrix: http://www.html BRKUCC-2011 © 2014 Cisco and/or its affiliates.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr. Cisco Public 82 .cisco.

Cisco Public 83 . All rights reserved.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 © 2014 Cisco and/or its affiliates.

com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr. All rights reserved.html BRKUCC-2011 4 © 2014 Cisco and/or its affiliates. Cisco Public 84 Phase IV: UC Applications Upgrade .cisco. 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.Overall Upgrade Strategy to Minimizing Down Time 1 2 3 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.

1 and later using CCMPPID.Phase II: Phone Firmware Distribution • Peer-to-Peer Image Distribution (PPID): – Configurable via AXL script with Unified 4.0 and later – Default is disable PPID on all phones models • Change TFTP service parameter for dedicated TFTP server on CUCM 5. (Readme in notes section) – Configurable via CM Administration or BAT from version 5.cisco.html#wp1141991 BRKUCC-2011 © 2014 Cisco and/or its affiliates. Cisco Public 85 .500 for single processor dedicated TFTP server and 3. All rights reserved.1(1c) or later: – System > Service Parameter > Cisco TFTP (Advance) – Maximum Serving Count (default is 200 for Windows and 500 for appliance) – 1.com/en/US/docs/voice_ip_comm/cucmbe/admin/8_5_1/ccmsys/a08ipph.exe.000 for dual processors dedicated TFTP server Peer-to-Peer Image Distribution (PPID): http://www.

5(2)SR1 or later – Factory phones or phones taken off another CUCM cluster Firmware Release Notes 8.ht ml BRKUCC-2011 © 2014 Cisco and/or its affiliates. 7961G.Phase II:Phone Upgrade Caveat • If possible.3(2)SR1 or earlier must upgrade to 8. Cisco Public 86 . 7961G-GE.5(2) before upgrading to 8.1(2) or earlier • All third-generation IP phones: – Firmware release 8.com/en/US/docs/voice_ip_comm/cuipph/firmware/8_5_2/english/release/notes/7900_852SR1. and 7906G): – Firmware release 6.cisco.0(3) – CUCM 4. choose final CUCM version default or recommended firmware. 7911G.0(1) or earlier needs to upgrade to 7. All rights reserved. 7970G. 7941G-GE.5(2)SR1: http://www. Avoid multiple upgrade and downgrades • Some third-generation IP phones (7971G-GE. 7941G.

All rights reserved. Cisco Public 87 . increase “maximum number of registered devices to 7500 or 10000” • Check for DB replication state of 2 before and after upgrade BRKUCC-2011 © 2014 Cisco and/or its affiliates.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.

All rights reserved.cisco. RTMT and Unified Reporting (details in notes section) – DB replication state CUCM SRND: www.com/go/ucsrnd BRKUCC-2011 © 2014 Cisco and/or its affiliates.Phase III: CUCM Upgrade Consideration • Clustering over the WAN (COW) can increase time for installation. check for the following using CLI. upgrade and database (DB) replication by 40%–50% • Firewall between Unified CM servers • After upgrade. Cisco Public 88 .

cisco.html • Break the upgrade into phases to minimize downtime • Open a Global Licensing Operations (GLO) case with specific tags for fast results – https:// communities. All rights reserved.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/web/partners/tools/pdihd.Migration Recommendations for CUCM Upgrade • Develop a comprehensive plan for the migration • Partners can use PDI Helpdesk for migration plan review – http://www. Cisco Public 89 .com/tac/caseopen BRKUCC-2011 © 2014 Cisco and/or its affiliates.cisco.

All rights reserved.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 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 follow @CiscoLive and @CiscoPress • View the official rules at http://bit. Cisco Public 90 .ly/CLUSwin BRKUCC-2011 © 2014 Cisco and/or its affiliates.

Cisco Public 91 . • Complete your session evaluation through the Cisco Live mobile app or visit one of the interactive kiosks located throughout the convention center.Complete Your Online Session Evaluation • Give us your feedback and you could win fabulous prizes. Don’t forget: Cisco Live sessions will be available for viewing on-demand after the event at CiscoLive. All rights reserved.com/Online BRKUCC-2011 © 2014 Cisco and/or its affiliates. Winners announced daily.

Cisco Public 92 . All rights reserved.Continue Your Education • Demos in the Cisco Campus • Walk-in Self-Paced Labs • Table Topics • Meet the Engineer 1:1 meetings BRKUCC-2011 © 2014 Cisco and/or its affiliates.

.

.

Appendix Questions ? .

W1 Upgrade: Windows to Appliance Model Not covered in detail in this session Existing CUCM 4.1 Cluster Tape. DLU and 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.1 Cluster Install Install. and CUCM Upgrade Download 7.1 software availability can be an issue since CUCM 7.1 Feature SW License 6 .X Cluster Download From CCO CUCM 7.X Cluster New CUCM New CUCM 7.X DVD Kit 2 3 4 © 2014 Cisco and/or its affiliates.X Cluster Existing CUCM 4. Install and Run Run. FTP or sFTP Server 5 Node.1 has EOS (End of Sales) Upload Licenses Upload DMA File Save DMA File to Tape or Network Share New CUCM 7. All rights reserved. Cisco Public 96  CUCM 7.1 Cluster 7.

jsp Product License Registration site = https://tools. Cisco Public 97 .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 © 2014 Cisco and/or its affiliates.com/gct/Upgrade/jsp/index.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.NEW UPGRADE License Acquisition with CUCM 5. All rights reserved.cisco.X to 8.

Data Migration InActive partition Reboot Dormant Active Partition 1. Firmware and BIOS upgrade 2. RPMs installation 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 © 2014 Cisco and/or its affiliates. CUCM installation 3.L2 Upgrade: Appliance to Appliance Model Active Partition Running InActive partition 1. All rights reserved. Cisco Public 98 . DB installation 4.

VOS installation 3. CUCM data import 4. Cisco Public InActive partition Dormant Active Partition 1. Data exported (CUCM and CAR) into /common partition Reboot InActive partition Dormant Active Partition 1.Refresh Upgrade (RU): Appliance to Appliance Model Active Partition InActive partition BRKUCC-2011 Running 1. CAR DB migration © 2014 Cisco and/or its affiliates. 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 . All rights reserved. Firmware and BIOS upgrade 2. DB installation 3. CUCM installation 2. CAR DB creation 5.

Cisco Unified Enterprise License Manager Add CUCM or CUC systems 1 2 ELM Success/Fail Get License Usage – 24 hours 3 Analyze 5 5 CUC Usage X. All rights reserved.Y. 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 © 2014 Cisco and/or its affiliates.Z Set License Status 4 CUC Enforcement First node of CUCM CUCM Enforcement Get License Capability 6      How and what do CUC. Cisco Public 100 . CUCM and ELM communicate? Register Grant ELM can be stand alone or bundle with CUCM or CUC.

CUCM evaluates users to phones usage and feature usage to derives at UCL/CUWL usage 2. 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 © 2014 Cisco and/or its affiliates.Process of CUCM and ELM Communications 1 2 CUCM License Evaluation 3 ELM License Evaluation 4 How does CUC. ELM evaluates license request. All rights reserved. CUCM sends UCL/CUWL usage to ELM 3. CUCM and ELM know what to communicate? [VALID or INVALID ] 1. Cisco Public 101 .

All rights reserved. Cluster: Ensure that system connected successfully . Cisco Public 102 . Cluster > Add: Add system in User Count Tool (UCT) using IP/hostname of system and AXL credential 2. Check versions of CUCM that the tool detects BRKUCC-2011 © 2014 Cisco and/or its affiliates.Using User Count Tool as Planning Tool to Migrate 1 2 1.

Cisco Public 103 .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 © 2014 Cisco and/or its affiliates. All rights reserved.

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

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

Cisco Public

104

License Conversion
CUWL
2-17
DLU

UCL
0-6
DLU

A La
Carte
DLU

How can I
migrate
these
license?

1

Manual

Pool of
DLUs

How many
of what
type of
licenses
do I have?

BRKUCC-2011

2

Automated

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

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
 Documentation of process at:
https://communities.cisco.com/docs/DOC-33804

 Standalone CUC
 Upgrade CUC to 9.X
 Self service license request using Product License
Registration
 Documentation of process at:
http://www.cisco.com/en/US/products/ps6509/products_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

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

Cisco Public

106

Data for Manual License Migration • Working with Global Licensing Operation (GLO) at licensing@cisco.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.1.X: License Report with License Count Utility (UCT) – CUCM 3.X affiliates.X to 8. count and Cisco Public features for unused DLU .X to 5.user All rights reserved.com • Provide current system usage – Migrated system(s): ELM Usage Report – CUCM 6.

X software Upgrade CUCM cluster  Log into Product Upgrade Tool site = http://tools.com/gct/Upgrade/jsp/index.jsp to order upgrade kit  Obtain upgrade software.X and run licenses in Overage mode for 60 days before license is required for ELM BRKUCC-2011 © 2014 Cisco and/or its affiliates. All rights reserved.2. Automated License Migration with ELM Contract Number Product Upgrade Tool site CUCM 9. There is an electronic version for download  Upgrade CUCM cluster to 9. Cisco Public 108 .cisco.

2. In ELM. All rights reserved.com/SWIFT/LicensingUI/Home – Go to Migration License section and select Register for Upgrade/Migrate License 109 BRKUCC-2011 © 2014 Cisco and/or its affiliates. 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. Automated License Migration with ELM CUCM License Request New upgraded CUC 9. Go to: – Product License Registration site = https://tools. add the new upgraded CUC 9.cisco.X and get upgrade license request • 2.X 1 Text from ELM License Request ELM 3 Product License Registration site ELM License file 2 • 1. Cisco Public .

9. New Installation.1 Installation MCS-781X MCS7825 MCS7828 MCS7835 MCS7845 CUCM 9..X DVD KIT INSTALLATION PROCESS (PROCEED) 1 2 Basic Install Apply SR.1(2) BRKUCC-2011 © 2014 Cisco and/or its affiliates. ES or SU Upgrade During Installation i.1(1a) to 9. All rights reserved.e.Overview of CUCM 9. New Server—Flash Cut or New Server—Migration Cisco Public 110 .

a USB key is required for physical servers – Plug USB key into the physical server – Accept dumping of logs • In a virtualized environment.html to unzip the tar file Remove serial port after a successful installation of Unified CM 8. dump logs is via serial port of VM – – – – – Add serial port when VM is off before CUCM 8. All rights reserved. Cisco Public 111 .X installation On failure.Installation Logs • To capture installation logs failure.7-zip. edit guest OS to connect to a temporary file to virtual serial port Accept dumping of logs Download 7zip from http://www.X BRKUCC-2011 © 2014 Cisco and/or its affiliates.org/download.