Best Practices for Migrating Previous Versions of Cisco ...events.cisco.hu/2014/techtorial/doc/Cisco Techtorial FY14_Pinter... · Best Practices for Migrating Previous Versions of

Best Practices for Migrating Previous Versions of Cisco Unified Communications Manager (CUCM) to 9.x/10.X

Zoltan Pinter Cisco TSN – Collaboration VSE

February 2014

Cisco Confidential 2 © 2013-2014 Cisco and/or its affiliates. All rights reserved.

- CUCM main features - Supported hardwares - 5 step upgrade path

Cisco Confidential © 2011 Cisco and/or its affiliates. All rights reserved. 3

Cisco UCM Feature Matrix Features 4.X-7.x 8.0.x 8.5/8.6 9.1 (2) 10.0

Virtualization X ü ü ü ü BYOD (Jabber on Win/MAC/IOS for voice/video) X X ü ü ü Video (Unified Voice/Video call Control) X X ü ü ü Mobility (SNR for Voice and Video) X X X ü ü B2B (SIP URI-Dialing & Expressway) X X X ü ü Central License Management (ELM/PLM) X X X ü ü Bandwidth Management (Locations Based CAC) X X X ü ü Collaboration Edge X X X ü ü Network-based Recording X X X X ü Video enabled Contact Center X X X X ü Prime Collaboration X X X X ü Self Provisioning and Self Care X X X X ü


Platform Options

4

Tested Reference Configuration (TRC) 1

2

B200 M3

B230 M2

B440 M2 C260 M2

Specs-Based

VMware Supported

Servers

C220 M3

C240 M3

- including BE6K server bundle - including BE7K server bundle

- vCenter mandatory

or ANY 3rd party as long as…: http://docwiki.cisco.com/wiki/UC_Virtualization_Supported_Hardware#.22Can_I_use_this_server.3F.22

•  MCS are EoS

•  Up to CUCM 8.6 EoS

•  CUCM 10.x; Unity Connection 10.x VM ONLY!!!


Cisco Business Edition 7000 Preloaded Server Ships Ready-to-Activate

Prime Collaboration Provisioning 9.5

Unified Communications Manager 9.1(2) IM & Presence 9.1(2)

Paging Server 8.4

Unity Connection 9.1(2)

VCS X7.2

Emergency Responder 9.0

Unified Contact Center Express 9.0è10.0

Server Hardware, Preconfigured -UCS C240 M3, with BIOS, RAID, disk formatting, firmware, drivers, ready-to-go

Preinstalled Virtualization Software - Same as BE6000: VMW-VS5-HYP-K9; licensed with v5.1 master serial number, eDelivery-only, ready-to-run

Preloaded Collaboration Software (unlicensed / licenses sold separately) - Same suite of apps and versions as BE6000, ready-to-install - Same preload files as BE6000 except for PCP and VCS - CUWL/UCL, VCS, PCP licensing sold separately

“Cisco Collaboration 9.1 suite”

Cisco UC Virtualization Hypervisor 5.1 U1

Cisco UCS C240 M3 SFF TRC#2 12vCPU, 8x8GB RAM, 12x300GB HDD


1 2 3 4 5

Readiness Assessment

Pre-upgrade Checklist

License Entitlement

Upgrade CUCM

Post-upgrade Checklist

Enable Customers to leverage next generation Collaboration Experiences by upgrading to Cisco Unified Communications Manager 9.1 or higher!

Drive to Collab Upgrade Process

Upgrade Procedure Step By Step Instructions



1 2 3 4 5

Run Readiness Assessment Perform readiness assessment including system compatibility checks with other UC applications

Web Tool - Upgrade Readiness Assessment:http://tools.cisco.com/cucst/upgrade/index.jsp

iPad App - CUCM Collaboration Central: https://itunes.apple.com/us/app/id650114526?mt=8

Ø  Use one of the tools to generate readiness report.

Ø  Remediate any gaps, including UC system application compatibility, CUCM HW, Gateways and endpoints

Ø  Download the required software from PUT: http://tools.cisco.com/gct/Upgrade/jsp/index.jsp

Ø  Chose one of the recommended upgrade options provided by the readiness assessment.


“CUCM Upgrade Central” – iPad app

ü CUCM v9.1 and v10.0 ü Unity/Unity Connection ü MeetingPlace

ü  Presence Server ü Contact Center Express ü  Attendant Console ü  ANDTEK Application Server

ü  License Count Usage report ü  Support and Collateral for BE6K/BE7K ü  Support for English, French, German,

Spanish, Portuguese and Mandarin

Available

Now on the

App Store

iPad App: https://itunes.apple.com/us/app/id650114526

Readiness Assessment iPad App:


“Upgrade Readiness Assesment Tool” – WEB app

Web Tool: http://tools.cisco.com/cucst/upgrade/index.jsp


1 2 3 4 5 Pre-Upgrade

Checklist Perform pre-upgrade tasks in preparation of the upgrade

ü Review the Release notes for 9.x/10.x ü Perform bug-scrubs and evaluate impact of any open

bugs to your configuration ü Remediate any gaps as identified in Readiness Report ü Schedule maintenance windows ü Plan for required downtime during maintenance windows ü Upgrade Phone Firmware/ IOS Voice Gateway/

Associated UC Applications like Presence, UCCX, etc ü Migrate to Cisco Unified X Attendant Console (CUxAC)

before or during Unified CM 9.X upgrade ü USB live MoH, Phone proxy/TLS Proxy – not supported

ü Document Production CUCM Locales and Phone Locales

ü Manual back-up of background images and customized ringtones

ü Document network parameters of Production Cluster ü Document registered device count ü Purge CDR records to reduce upgrade time ü Make sure the DB Replication Status is ‘2’ before

upgrade ü Restrict admin access during upgrade to avoid upgrade

failures

•  Proactive TAC case can be opened for you to help you through the upgrade http://www.cisco.com/web/partners/tools/pdi.html

•  Cisco PDI Help Desk has been trained specifically on upgrades and will be available 12x5 for partners [email protected]


1 2 3 4 5

License Planning/Ordering

Email GLO: [email protected]

Worldwide Telephone Numbers (Press 3 for Licensing): www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html

Open a Case Online (Select Problem Type as “Licensing”): http://cisco.com/tac/caseopen

ü  Fulfill any unused license PAKs ü  Install all pre-9.x licenses prior to upgrade ü Assign users to phones – if possible ü Run License Count Utility (LCU) on existing system for 6.x/

higher. Download from Cisco Download site License Count Utility

ü Contact GLO to understand current license entitlement ü Use the Drive to Collab promotions through CB+ to up level

current licenses or convert unused DLUs ü  For more information:

https://communities.cisco.com/docs/DOC-33804

•  Plan for growth, unused DLU allocation and additional UCSS. •  You must apply all pre-9.x licenses to CUCM before you upgrade. After upgrade, you cannot install pre-9.x

licenses to the Enterprise License Manager.

Contact GLO for your 10.0 license entitlement



License Migration When migrating, customers can choose to:

Ø  Keep the same quantity and type of licenses

Ø  Decrease their license quantity and type (without refund)

Ø  Increase their quantity and select additional license types by converting DLUs, or

Ø  Up level their license types using Drive to Collab Promotions

•  After the upgrade, customer entitlement record will be locked in moving forward.

•  At the time of the next renewal, the terms and price will be based on licenses issued during

migration, plus any users purchased after migration. (Exception: Drive to Collab Promotions)


License Migration Process

•  Policy – “Customers with UCSS will be assured the same licensing capability and capacity at no cost as they migrate to CUCM 9.1(2) and 10.0”

Pre-9.x Licenses With UCSS Contract

No Licensing Cost 9.1(2) or 10.0 Licenses Same Licensing

Capability/Capacity

Contact GLO ([email protected]) for all CUCM Migrations Response Time: 3-5 Business Days

Process to Obtain Licenses (100% Manual Support)

•  GLO is your single point of contact for obtaining License Entitlement & Migration Licenses from pre-9.x (DLU based) to 9.1(2) or 10.x (user based)


License Migration Process

1.  “CUCM Upgrade Central” iPad App License Usage or LCU Output (Run on the CUCM Publisher)

2.  MAC Address of the Publisher (If available, include all previous Publisher or License Mac)

3.  ELM/PLM License Request file (in .txt/.csv as an attachment)

4.  Site information (name-all name permutations, City, state, country) for contract update

5.  UCSS/ESW, Email, CCO ID, Unused DLU Allocation – Optional

After Upgrading to 9.1(2)/10.0 - Email Subject: Drive to Collab Post-Migration Request

1.  “CUCM Upgrade Central” iPad App License Usage or LCU Output (Run on the CUCM Publisher)

2.  MAC Address of current Publisher (if available, include all previous Publisher or License Mac)

3.  UCSS/ESW information - Optional

Before Upgrading to 9.1(2)/10.0 – Email subject: Drive to Collab Pre-Migration Request

Escalation Process: Call GLO and speak with License Duty Manager


Drive-to-Collab + Collaboration Breakaway Plus (CB+)


1 2 3 4 5

Upgrade CUCM Perform the CUCM upgrade by following one of the customized procedures


•  Stop all configuration tasks •  Disable extension mobility for the cluster •  Follow one of the upgrade procedures available for your scenario

Direct Upgrade

Jump Upgrade

Email TAC: [email protected]

Worldwide Telephone Numbers: www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html

Open a Case Online: Select keyword “Communications Manager Upgrade to v9/10 (Drive-To-Collab Initiative)” http://cisco.com/tac/caseopen

Prime Collaboration Deployment Migration

High Availability Upgrade


CUCM Upgrade/Migration Paths to VM

Upgrade directly from current Unified CM release to 9.1(x) on existing HW (including bridged mode) Direct

Multi-hop upgrade for MCS hardware that does not support Unified CM release 9.1(x) AND requires maximum service availability.

High Availability

Multi-hop upgrade: Install current (6.x and 7.x) Unified CM release on UCS hardware in isolated network, then upgrade directly to Unified CM 9.1(x), and flash cut.

Jump

In-place upgrades

Parallel upgrade with flash cut

Multiple service windows


Upgrade Process Simplified Customized Collateral for Upgrade Procedures

Current Release Direct UCS Direct MCS High Availability Jump

8.6(1) – 9.0(1)

8.0.2 - 8.5.1

8.0.1, 7.1.3, 6.1.4 - 6.1.5

7.1.5

7.0.1 - 7.1.2, 6.1.2 - 6.1.3

5.x(x) http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/ upgrade/5_1/upgrd513.html

4.x(x) http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/ dma/7_0_1/dmaug701a.html

Direct upgrade versions 6.1.2-9.0.1 to 9.1.x

Direct upgrade virtual versions 8.0.2-9.0.1 to 9.1.x

EDCS-1244204

EDCS-1245432

TBD

In Progress

Reduced 76 down to 6+1 documents

EDCS-1245853

High Availability upgrade versions 8.0.2-9.0.1 to 9.1.x

High Availability upgrade versions 6.1.2-6.1.5, 7.0.1-7.1.3, 8.0.1 to 9.1.x

High Availability upgrade versions 6.1.2-6.1.5, 7.0.1-7.1.3, 8.0.1 to 9.1.x

High Availability upgrade versions 7.1.5 to 9.1.x Jump upgrade

versions 4.x*, 5.x*, 6.1.4-6.1.5, 7.1.3, 7.1.5 to 9.1.x


Simple Migration to 10.0 (on VM) via Prime Collaboration Deployment

•  PCD = Prime Collaboration Deployment •  New (FREE) tool in 10.0 (replaces PAWS-M)

•  What does it do? •  Cluster-wide and multi-cluster upgrade/reboot

•  Installs, migrations, IP/hostname change management, file staging and notifications

•  Supported from 6.1+ (on MCS or VM), to 10.0 on VM only

•  Customer / partner benefits = bring joy back to migrations ☺ •  No multi-hop SW upgrades: single-step from 6.1+ to 10.0

•  Single-step MCS to VM or VM to VM •  No “deadnet” or “can’t clone my system” … in-place or to new system

while keeping or changing your old IP/hostnames •  Removes most of the “process” issues with CUCM migrations

•  Enhancements exposed to CDN developers

Cisco Prime Collaboration Deployment

… …

CUCM 10.0 IM & Presence

Nodes

CUCM 10.0 Voice/Video

Nodes …

SME 10.0 Nodes

Other clusters

MCS 7800 (6.1+)

CUCM + IM/P 10.0 via Cisco PCD

(UCM 8.0+)

PAWS API


Migration Methods - “Feature” Comparison Thru 8.x PAWS-M in 9.x VM-jump in 9.1(2) PCD in 10.0+

From UCM See UCM SW compatibility matrix

8.6.2, 9.x on MCS or VM 6.1.4/5 or 7.1.3/5 on MCS 6.1.5, 7.1.3/5 on MCS 8.x, 9.x on MCS or VM

To UCM 9.x on MCS or VM 9.1.2 on VM 10.0.1 on VM

Other UC app support? Many SME, CUP, IM&P, CUC, UCCX None Yes – see next slide

Cluster-wide, Multi-cluster, Multi-product orchestration?

No Yes No Yes

In-place SW upgrade? Yes Yes No Yes

Automated SW reboots? No Yes No Yes

Single-hop upgrade for all from/to paths?

No No No Yes

“Migration” - upgrade with Server change (P2V and MCSèUCS)

No No Yes Yes

“Readdress” - automated IP/hostname changes?

No No No Yes

“Install” - automated SW installs?

No No No Yes

Notifications Limited No No Yes


Prime Collaboration Deployment (PCD) – migration to v10 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 X X X X X X

Fresh Install X

Upgrade/COP Install X X X

Switch Version X X X

Reboot X X X

Export Data X X X X X X X

Hostname/IP Address Change X

CUCM SME IM&P

Unity Cxn UCCX / IPIVR

Paging Server CER CUxAC vTS VCS Conductor TMS WFO UCCE CUIC CCMP CVP MediaSense SocialMiner Finesse EIM/WIM CWMS PCP PCA

Upgrade (RU) •  “In-place” dual-partition •  Reboots

10.0(1)+ 10.0(1)+ 10.0(1)+ Not supported

Migrate (M1) •  MCS to VM •  VM to VM

10.0(1)+ Not

supported

Not supported Not supported

Readdress •  Hostname / IP 10.0(1)+ 10.0(1)+ Not supported Not supported

Install / Greenfield 10.0(1)+ Not supported Not supported Not supported


Prime Collaboration Deployment (PCD) Migration

6.1(4), 6.1(5), 7.1(3) or

7.1(5) MCS

8.0(3) MCS

8.0(3) UCS

10.0 UCS

Upgrade

Upgrade

Re-host Licenses Migrate Licenses

DRS restore

6.1(5), 7.1(3),7.1(5) 8.0(x), 8.5(1), 8.6(x),

9.(x) MCS

Install and Import Data to destination VM

Export Data from Source MCS

Using PCD Migration(v10.0) PCD

ü  Parallel Process ü  Minimum Downtime ü  Reduced Risk 10.0

UCS

Obtain Licenses

Migrate to 10.0

Without PCD


PCD Migration Paths From CUCM Release To CUCM 10.0(1)

4.x Multi-hop through 6.1(x)/7.1(x)

5.1(2) Multi-hop through 6.1(x)/7.1(x)

5.1(3) Two hop through 6.1(5)/7.1(5)

6.1(1) – 6.1(4) Two hop through 6.1(5)/7.1(5)

6.1(5) Single Hop

7.0(1) 7.1(2) Two hop through 7.1(5)

7.1(3) 7.1(5) Single Hop

8.0(1) 8.0(2) 8.0(3) 8.5(1) 8.6(1) 8.6(2) Single Hop

9.0(1) - 9.1(2) Single Hop


The following are compatible with Cisco Prime Collaboration Deployment:

§  Cisco UC Virtualization Foundation (appears as “Foundation Edition” in vSphere Client)

§  VMware vSphere Standard Edition, Enterprise Edition, or Enterprise Plus Edition

The following are NOT compatible with Cisco Prime Collaboration Deployment:

§  Cisco UC Virtualization Hypervisor (appears as “Hypervisor Edition” in vSphere Client)

§  VMware vSphere Hypervisor Edition

>>> BE6K/BE7K servers with UC Virtualization Hypervisor NOT supported as “TO” destinations

Licensing requirements for VM to run PCD


Automated Platform Conversion with PCD

25

§  CUCM Software provided to ESXi Hosts via NFS services running on PCD

§  Migration (M1) Steps

1.  Add CUCM Clusters to PCD Inventory

2.  Add ESXi Hosts to PCD Inventory

3.  Add CUCM 10.X ISOs to PCD SFTP Server

4.  Deploy Empty CUCM VM on ESXi Hosts via OVA

5.  Map Physical Nodes to Virtual VMs and Schedule Migration Tasks

CUCM 6.X

CUCM 7.X

CUCM 8.X

PCD

1

2

ESXi Host

4

3

Create CUCM

VMs via OVA

5


PCD Home Page & Menus

http://www.youtube.com/watch?v=JzG4kz1_hL4 or search for “Prime Collaboration Deployment” phrase on YouTube

Video to check (includes real step-by-step migration process for CUCM, IM&Presence):


1 2 3 4 5

Post-Upgrade Checklist ü Add upgraded CUCM 10.0 cluster to PLM server

ü Migrate Licenses using PLM within 60 day grace period:

contact GLO with “Drive to Collab Post-Migration Request”

subject

ü Manual Restore of the Background images and Ringtones.

ü  Install Locale files

ü Verify DB Replication (Reporting>Database status>”2-good”)

ü  For secure cluster, re-run CTL client

ü Perform validation–confirm phone/gateway registration, call

flows, application interoperability

Perform post-upgrade tasks


For capturing details logs for troubleshooting: Change log level on PLM Diagnostic Logs Admin Page to Debug to maximize trace output

Note : starting 10.0, if you use standalone PLM, the installation iso is different than the cucm iso.


Key Takeaways

•  Consider BE7K as a migration platform

•  Run iPad/Web Readiness Assessment Tool

•  If needed open a proactive PDI/TAC migration support case

•  Contact GLO for license entitlement:

- LCU tool is a must!

- use the “Drive to Collab Pre-Migration Request” subject

•  Consider upgrading to 10.x, since PCD simplifies the process – brings back joy J

•  After the upgrade contact GLO with “Drive to Collab Post-Migration Request” subject for licenses


Drive to Collab - Resources

Landing Page for All Drive to Collab Resources:

Customer Landing Page: http://www.cisco.com/go/cucmupgrade Partner Landing Page: http://cisco.com/go/drivetocollab

Support Alias for Drive to Collab Questions

Drive to Collab Program Team: [email protected] Licensing Support: [email protected] Collaboration Breakaway Plus Team: [email protected]


Questions?

Thank you.

Documents

Best Practices for Migrating Previous Versions of Cisco ...events.cisco.hu/2014/techtorial/doc/Cisco Techtorial FY14_Pinter... · Best Practices for Migrating Previous Versions of