Best Practices for Migrating Previous Versions of Cisco Unified Communications Manager (CUCM) to CUCM 9.0

Transcription

1

2 Best Practices for Migrating Previous Versions of Cisco Unified Communications Manager (CUCM) to CUCM 9.0 Baha Akman

3 Housekeeping We value your feedback- don't forget to complete your online session evaluations after each session & the Overall Conference Evaluation which will be available online from Thursday Visit the World of Solutions and Meet the Engineer Visit the Cisco Store to purchase your recommended readings Please switch off your mobile phones After the event don t forget to visit Cisco Live Virtual: 3

4 Session Objectives and Scope 1

5 Session Objectives To provide foundational knowledge for a successful upgrade or migration to Unified CM 9.0 Planning Considerations Installation Approaches To provide detail information on Cisco Unified Enterprise License Manager To provide some best practice guidelines for platform conversion from MCS to Cisco Virtualized Environment

6 Agenda Session Objectives and Scope Cisco Unified Communications Manager 9.0 Upgrade Definition and Upgrade Path Cisco Unified Communications Manager License and Cisco Unified Enterprise License Manager Cisco Unified Communications Manager Installation Process and Best Practices Servers, Clusters, and UC Application Upgrade/ Migration Definition Upgrade and Migration Strategy for Cisco Unified Communications Manager 6.1, 7.1, 8.0, 8.5 and 8.6 to 9.0 Platform Conversion from MCS to Cisco Virtualized Environment Q&A

7 Color Code for Versions of Unified CM Unified CM 3.X Unified CM 4.X Unified CM 5.X Unified CM 6.X Unified CM 7.X Unified CM 8.X Unified CM 9.X Unified CM on UCS

8 Session Scope Unified CM 6.1(X) Unified CM 7.1(X) Unified CM 8.X Unified CM 9(X) Unified CM 9.X Covers appliance (6.1, 7.1 and 8.X) version of Unified CM to upgrade to 9.0 Platform conversion from MCS to Cisco virtualized environment Platform Conversion C260 M2 TRC Specs-Based C210 M2 B200 M2 MCS, HP or IBM Servers C200 M2 B440 M2 B230 M2 Cisco Unified Communications Manager Software Compatibility Matrix

9 2 Cisco Unified Communications Manager 9.X Upgrade Definition and Upgrade Path

10 Unified CM Major/Minor Versions Major Unified CM Versions Major Unified CM Versions 5.0, 6.0 and 7.0 Minor Unified CM Versions 8.0 and 9.0 Minor Unified CM Versions 5.1, 6.1 and , 8.6 and 9.1 Previous major Unified CM versions 5.0, 6.0, and 7.0 Previous minor Unified CM version 5.1, 6.1 and 7.1 New major version Unified CM 8.0 and 9.0 New minor version Unified CM 8.5, 8.6 and 9.1 Introduced to align with system release numbering Version 8.X is the only version with 8.6 minor release

11 Sample Unified CM Versions and Builds Reference Unified CM Version Unified CM Build 9.1(1) (1) (2a)su (2a) (1a) (1) (1)su (1)su (1)su (1) (5b)su (5)su Numbering Convention (A.B.C.XYzzz-x) (A) Major version (B) Minor version (C) Maint. rel (X) FCS / Respin (Y) ES/SU Releases zzz (ZZZ) FCS, ES, SU

12 Unified CM Major/Minor Upgrade Definition W1 W1 Upgrade: Windows to Appliance model High complexity with possible longest downtime L2 I.E. Unified CM 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 Unified CM versions 5.X, 6.X, 7.X, 8.0 and 8.5 Between Unified CM versions with the same Major RHEL versions I.E. Unified CM 7.1(5) to 8.5 or Unified CM 8.6 to 9.0 RU RU (Refresh Upgrade): Appliance to Appliance model with major RHEL version change (starting with RHEL 5) Medium complexity with possible longer downtime From Unified CM versions 6.X, 7.X, 8.0 or 8.5 to 8.6 or 9.X I.E. Unified CM 8.5 to 8.6 or Unified CM 8.5 to 9.0

13 W1 Upgrade: Windows to Appliance model Existing Unified CM 4.X Cluster Existing Unified CM 4.X Cluster Existing Unified CM 4.X Cluster New Unified CM 7.1 Cluster New Unified CM 7.1 Cluster New Unified CM 7.1 Cluster Back Up With BARS Tape or Network Share Install and Run Upgrade Utility on All Servers Latest Upgrade Utility From CCO Download From CCO Install, Run, and Download DMA from Publisher Data Migration Assistant (DMA) 7.1 Save DMA File to Tape or Network Share Install Unified CM 7.1 Unified CM 7.X DVD Kit Upload DMA File Tape, FTP or sftp Server Upload Licenses Node, DLU and 7.1 Feature SW License

14 L2 and RU Upgrade: Appliance to Appliance model Updated Unified CM SW Unified CM Publisher 1 2 Unified CM Publisher Active Partition inactive Partition InActive partition 3 Active partition Active Partition InActive partition Switch Version via OS Admin or CLI inactive Partition Active partition Unified CM Subscriber Unified CM Subscriber

15 L2 and RU Upgrade: Appliance to Appliance model Upgrade to same major RHEL version NO Perform a RU Upgrade Existing Unified CM cluster being upgraded YES Perform a L2 Upgrade Upgraded Unified CM cluster Unified CM RHEL Release 5.0(4) RHEL 3 Update 6 5.1(x) & 6.X RHEL 3 Update 8 7.0(1) RHEL 4 Update 4 7.1(2) RHEL 4 Update 6 7.1(3) & 8.0(1) RHEL 4 Update RHEL 4 Update RHEL 5 Update & 9.1 RHEL 5 Update 7 Starting with Unified CM 8.6 or RHEL 5

16 L2 Upgrade: Appliance to Appliance model Active Partition Running InActive partition Dormant InActive partition 1.RPMs installation 2.Unified CM installation 3.DB installation 4.Data Migration Reboot Active Partition 1. Firmware and BIOS upgrade 2.Post reboot software installation Active partition is running while upgrade software is being install on inactive partition Low downtime (20-30) min since upgrade can be done while system is functioning

17 Refresh Upgrade (RU): Appliance to Appliance model Active Partition InActive partition InActive partition Running 1. Data exported (Unified CM and CAR) into /common partition Dormant Reboot InActive partition Active Partition Dormant 1. Firmware and BIOS upgrade 2.VOS installation 3. Platform import Reboot Active Partition 1. Unified CM installation 2. DB installation 3. Unified CM data import 4.CAR DB creation 5.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 duration is equal to complete installation of Unified CM

18 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 Install the latest COP (ciscocm.refresh_upgrade_v1.1.cop.sgn) file to allow for successful upgrade and limit switch version after upgrade 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 Select automatic Switchover to the new version Best Practice

19 Refresh Upgrade (RU) for MCS 7825 and MCS 7828 MCS-7825 H3/H4 MCS-7825-I3/I4/I5 MCS-7828-H3 MCS-7828-I3/I4/I5 RU MCS-7825 H3/H4 MCS-7825-I3/I4/I5 MCS-7828-H3 MCS-7828-I3/I4/I5 Software raid and OS reinstallation by RHEL 5 requires USB key CUCM- 16 GB USB drive. CUC and CUCM BE 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 used for new installation Reinstallation and DRS restore as the only reversion method Check memory required per server (MCS7825 4GB, MCS7828 6GB) before upgrade

20 One-Step L2 Upgrades (Appliance) Unified CM 8.6(1) Unified CM 8.6(1a)) Unified CM 8.6(2) Unified CM 8.6(2a) L2 Unified CM 9.X Unified CM 9.X Short or no downtime (20 30 min) Same set of servers for Unified CM version 8.6 are supported Cisco Unified Communications Manager Software Compatibility Matrix

21 One-Step RU Upgrades (Appliance) Unified CM 6.1(4) Unified CM 6.1(4a) Unified CM 6.1(5) Unified CM 7.1(3) Unified CM 7.1(3a/b) RU Unified CM 9.X Unified CM 7.1(5) Unified CM 7.1(5a/b) Unified CM 8.0(X) Longer downtime Medium upgrade complexity Downgrade for MCS7825 & MCS7828 can be time consuming Unified CM 8.5(X) Cisco Unified Communications Manager Software Compatibility Matrix

22 Two-Step Upgrades (Appliance) Unified CM 5.1(3) Unified CM 7.0(2) Unified CM 7.0(2a) L2 Unified CM 7.1(5b) SU4 RU Unified CM 9.X For end of support and appliance versions of Unified CM Focus on the 7.1 key versions that can be upgraded to 9.X Minimize major version changes (I.E. 7.0 to 8.0) Can upgrade directly to an SU End of Sales Notices for Unified CM is in the notes section

23 Cisco Unified Communications 3 Manager License and Cisco Unified Enterprise License Manager

24 Foundational Knowledge of Cisco Unified Communications Manager 8.X and earlier Licenses

25 Unified CM 5.0 to 7.1(3) License Types TECHNICAL ORDERING Description Node Node Number nodes per cluster DLU DLU Number of phones, type of phones, mobility feature and presence users SW Feature ESW/UCSS Maintenance for minor and major version upgrade Three license types: Node, Device License Unit (DLU) and Software Feature license Node license is enforced based on the number of node running CM service. TFTP and MOH also requires node licenses DLU is enforced based on provisioned phones, type of phones, mobility and presence features Major version upgrade requires Software Feature license License files are locked to MAC address of the first node or Publisher of the cluster License enforcement is done on Unified CM

26 Unified CM 7.1(5) to 8.6 License Types TECHNICAL ORDERING Description Node UCL/CUWL Number nodes per cluster DLU UCL/CUWL Number of phones, type of phones, mobility feature and presence users SW Feature ESW/UCSS Maintenance for minor and major version upgrade Technical license enforcement is the same as before: Node, DLU and Software Feature license. Device based Ordering is based on User based For bare metal servers (MCS), licenses are locked to MAC address of the first node or Publisher of the cluster In virtualized environment, licenses are locked to the license MAC address of the first node or Publisher of the cluster License enforcement is done on Unified CM

27 License MAC in a Virtualized Environment (8.X only and not valid in CUCM 9.X) License MAC is 12 digits HEX values based on the hash of these 10 Unified CM settings 1. Certificate Information (Organization, Unit, Location, State, Country) 2. Hostname 3. IP Address or dhcp 4. IP Mask or dhcp 5. Gateway Address or dhcp 6. NIC speed auto 7. NTP server 1 8. Primary DNS 9. SMTP server or none 10. Time zone Changes in any of the 10 values will start the 30 days grace period on the existing valid license file which require rehosting to the new license MAC. Login will alert the amount of days left before expiring To reset the 30 days timer, change back to original settings and then back to the desired settings If grace period is expired, then CM service still stop and license file is invalidated for good Use Cisco Unified Communications Answer File Generator proactively Cisco Unified OS Administration: Show > Status or Show > Network CLI: show status Cisco Unified Communications Answer File Generator for License MAC:

28 NEW UPGRADE License Acquisition with Unified CM 5.X to 8.X Contract Number Product Upgrade Tool Site SW Feature License Upgraded CUCM cluster Product Activation Key Product License Registration Site Node License 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 performed on Unified CM

29 Cisco Unified Communications Manager 9.X Licenses

30 Cisco Unified Enterprise License Manager CUCM + CUELM CUC + CUELM CUCM BE 5K + CUELM CUCM BE 3K CUELM 9.0 Installation DVD consisted of five products including Cisco Unified Enterprise License Manager (CUELM) bundled with three CUCM products or as stand alone deployment CUELM is a centralize licensing product running on top of Cisco Voice OS (VOS) CUELM supports Cisco Unified Communications Manager (CUCM) and Cisco Unity Connection (CUC) Cisco Unified Presence (CUP) leverages CUCM for licensing License file is uploaded onto CUELM instead of CUCM or CUC and is based on CUELM MAC address and host ID License file is cumulative and is based on products (CUCM or CUC)

31 Cisco Unified Enterprise License Architecture 9.0 First Node of CUCM Cluster 1 First Node of CUCM Cluster 2 First Node of CUCM Cluster 3 First node of CUC 1 First node of CUC 2 First node of CUC 3 License Manager API License Manager API License Manager API License Manager API License Manager API License Manager API CUELM License file CUELM 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 CUELM is available with CUCM 9.0 License Manager API added to CUCM 9.0 and CUC 9.0 to interact with CUELM for license request and approval CUELM

32 Cisco Unified Enterprise License Architecture 9.1+ First node cluster 1 First node cluster 2 First node cluster 3 First node of CUC 1 First node of CUC 2 First node of CUC 3 License Manager API License Manager API License Manager API License Manager API License Manager API License Manager API FNO SWIFT FNE Cisco Back Office for Licensing CUELM Electronic license fulfillment with CUELM is available with CUCM 9.1+ which reduces TCO and improve on response time for license acquisition FNE (Flexnet) toolkit added to CUELM 9.0 to interact with Cisco Back Office

33 Cisco Unified Enterprise License Manager Add CUCM or CUC systems 1 CUELM 2 Register Success/Fail Get License Usage 24 hours 3 Usage X,Y,Z How and what do CUC, CUCM and CUELM communicate? 5 5 CUC First node of CUCM License Request CUP Analyze 4 Set License Status Get License Capability CUC Enforcement CUCM Enforcement 6 Grant CUELM can be stand alone or bundle with CUCM or CUC. Interaction is a logical flow CUCM and CUC sends license usage to CUELM CUELM handles the license grant or revoke based licensing logic CUCM and CUC perform license enforcement based CUELM response CUCM and CUC enforcement rules are different

34 Process of CUCM and CUELM Communications 1 2 CUCM License Evaluation 4 [VALID or INVALID ] 3 CUELM License Evaluation How does CUC, CUCM and CUELM know what to communicate? 1. CUCM evaluates users to phones usage and feature usage and derives UCL/CUWL usage 2. CUCM sends UCL/CUWL usage to CUELM 3. CUELM evaluates license request, perform evaluation and license substitution before sending a respond to CUCM (VALID or INVALID) Next reference slides will go over how CUCM and CUELM evaluates license usage in detail

35 CUCM 9.0 Phone Models and Phone Types Reference Phone Type Phone Model Tin Copper 6911, 6921 Analog, 3905, 6901, VGC Phone Bronze 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 Silver Gold TelePresence Room CIPC, CUPC, Jabber Windows/MAC, EX60, EX90 Jabber for Mobile (Android/iPhone/iPad), CUMC CTS 500/1000/1100/1300/1310/3000/3200, C20/40/60/90, MX200/300

36 CUCM 9.0 Phone Types and Licensing License Phone Type # of Devices Reference Features Essential UCL Tin 1 EM Basic UCL Tin, Copper 1 EM, SNR Enhance UCL Tin, Copper, Bronze 1 EM, SNR Advance UCL Tin, Copper, Bronze, Silver 2 EM, SNR CUWL Standard Tin, Copper, Bronze, Silver 2 EM, SNR CUWL Premium Tin, Copper, Bronze, Silver, Gold 6 EM, SNR CUWL Professional Tin, Copper, Bronze, Silver, Gold 10 EM, SNR TelePresence TelePresence 1

37 CUCM 9.1 Phone Models and Phone Types Reference Phone Type Phone Model Tin Analog, 3905, 6901, VGC Phone, ATA186, ATA187 Copper 6911, 6921, CUC-RTX Bronze 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/iPad), CUMC, IIM, Nokia S60, H.323 Client, VXC 6215 TelePresence Room CTS 500/1000/1100/1300/1310/3000/3200, C20/40/60/90, MX200/300, Generic Single/Multi-screen, TX9000/9200, SX20, Profile 42 (C40) * In CUCM version 9.1, Silver and Gold Phone Type moves to Bronze

38 CUCM 9.1 Phone Types and Licensing License Phone Type # of Devices Reference Features Essential UCL Tin 1 EM Basic UCL Tin, Copper 1 EM, SNR Enhance UCL Tin, Copper, Bronze 1 EM, SNR Enhance UCL Plus Tin, Copper, Bronze 2 EM, SNR CUWL Standard Tin, Copper, Bronze 10 EM, SNR CUWL Professional Tin, Copper, Bronze 10 EM, SNR TelePresence TelePresence 1

39 DLU to UCL/CUWL Assessment Users with associated number of phones, model of phones and features are used as the basis for UCL/CUWL assessment Phone not assigned to a user will be deem as a UCL user license with one phone based on the phone model Users with 11 or more phones will consume two or more CUWL Standard This might be a good opportunity to assess phone associations in current system prior to conversion

40 CUCM 9.1 CUWL and DLU Reference CUWL (Prior to January 2012) DLU Standard 11 Professional 17 CUWL DLU Standard 8 Pro 12

41 Conversion: CUCM 9.1 License Type and DLU Usage Reference License Phone Type # of Devices DLU Usage Essential UCL Tin 1 0 Basic UCL Tin, Copper 1 4 Enhance UCL Tin, Copper, Bronze 1 6 Enhance UCL Plus Tin, Copper, Bronze 2 9 CUWL Standard Tin, Copper, Bronze CUWL Professional Tin, Copper, Bronze TelePresence TelePresence 1 11

42 Extension Mobility and UCL Basic UCL provides Extension Mobility (EM) feature Number of EM users less than or equal to the number of phones, then the number of UCL licenses required is based on the Phone Type Number of EM users greater than the number of phones, then additional UCL Basic licenses are required for these users

43 CUCM 9.0 Phone Types and License Request Systems > Licensing > License Usage Report CUCM demo mode is for 60 days with unlimited node, unlimited phones and unlimited users. CUC demo is as before with limited capability

44 CUCM 9.0 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. 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.

45 CUCM 9.0 License State Change Notes Reference To change from No-Provisioning state to Grace state, a reboot of the Publisher is required. One more day of MAC. 60 days grace period in non-compliant modes (Overage, Lost Connection to ELM and Security Mis-Match) will not reset until in Compliant mode.

46 CUELM License Structure and Substitution UCL - Essential UCL Basic UCL Enhance UCL Enhance + CUWL Standard CUWL Professional User 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 Enhance I.E. CUWL Standard can be covered by CUWL Professional Refer back to Phone Model and Phone Type slide for UCL/CUWL correlation CUELM 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

47 Example of License State Reference 1. CUCM new installation will be in CUCM demo mode for 60 days with unlimited users, phones and nodes capability 2. After 60 days, CUCM will be in no-provisioning mode. No MAC. 3. If CUELM add CUCM, then CUCM go off demo mode or no-provisioning mode and depends on licenses loaded on CUELM 4. CUELM without license will be in CUELM demo mode for 60 days. 1. CUELM response to CUCM with INVALID 2. CUCM will be in no-provisioning mode until CUELM is licensed 5. License evaluation is on a per product (CUCM or CUC) basis Non-Compliant mode are product specific 1. CUCM will be in Overage mode, works for 60 days and change to no-provisioning mode 2. CUC works for 60 days and then shutdown with no voice messaging services

48 DLU to UCL/CUWL Conversion Tools for Upgrade DLU User Count Tool CUELM CONVERSION TOOLS UCL Essential (0) UCL Basic (3) UCL Enhance (6) UCL Enhance + (9) CUWL Standard (11) CUWL Pro (17) TelePresence room (11) User Count Tool (UCT): Planning tool to convert from DLU to UCL/CUWL license CUELM: Actual conversion tool to convert and generate UCL/CUWL license request based on an upgraded cluster Tools recommend UCL or CUWL equivalence based on devices and allows for manual adjustments Conversion from DLU to UCL/CUWL should match what is licensed and might not use up all of the available DLU in the older systems The final UCL/CUWL conversion will result in ESW and UCSS changes

49 Using User Count Tool as Planning Tool to Migrate Cluster > Add: Add system in User Count Tool (UCT) using IP/hostname of system and AXL credential 2. Cluster: Ensure that system connected successfully 3. Check versions of CUCM that the tool detects

50 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 Remaining 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 CUELM during upgrades: Per systems Migration phase(s)

51 Use CUELM Upgrade Wizard for License Upgrade Upgrade License Wizard: License Management > Add or Upgrade License > Upgrade License Plan: Plan, Order and Install 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 CUELM Install is to install the license file CUW

52 License Acquisition with CUELM Upgrade 1/2 Contract Number Product Upgrade CUCM 9.X Tool site 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 CUELM

53 License Acquisition with CUELM Upgrade 2/2 CUCM License Request Newly upgraded CUCM 9.X cluster 1 CUELM 2 Text from CUELM License Request 3 Product License Registration site CUELM License file 1. In CUELM, add the newly upgraded CUCM 9.X cluster and get upgrade license request 2. In CUELM 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

54 License Acquisition with CUELM - New CUCM License Request New CUCM 9.X cluster 1 CUELM 2 Text from CUELM License Request Product Activation Key 3 Product License Registration Site 4 CUELM License file 1. Add new CUCM 9.X in CUELM and get license request 2. Login into CUELM: License Management > Licenses > Generate License Request and get license request text 3. Go to Product License Registration site = and submit both license request text and PAK 4. License file will be ed 5. Upload license onto CUELM

55 License Migration Models with CUELM License Management CUCM cluster CUCM cluster License Management CUELM Stand Alone CUCM or 8.X or earlier is a distributed license management model CUCM 9 and later provides for both distributed and centralized license management model of which centralized license model provides the following benefits: CUCM cluster DISTRIBUTED CUCM cluster CENTRALIZED License pooling: Mobility of users and reduce TCO Future electronic license model: Reduce TCO Central license management: Reduce TCO Consideration when designing a licensing solution 60 days overage and redundancy/re-host (registration ID and MAC) of CUELM

56 4 Cisco Unified Communications Manager Installation Process and Best Practices

57 Overview of Unified CM 7.1 Installation Unified CM 7.1 DVD KIT MCS-781X MCS7825 MCS7828 MCS7835 MCS7845 INSTALLATION PROCESS (PROCEED) 1 Apply SR, ES or SU 2 3 Import Data from Windows Basic Install Upgrade During Installation i.e., 7.1(3) to 7.1(5) Upgrade From Windows i.e., 4.1(3) to 7.1(5) New Installation, New Server Flash Cut or New Server Migration

58 Overview of Unified CM 8.0+ Installation Unified CM 8.X or 9.X DVD KIT MCS-781X MCS7825 MCS7828 MCS7835 MCS INSTALLATION PROCESS (PROCEED) 2 Basic Install Apply SR, ES or SU Upgrade During Installation i.e., 8.6(1) to 8.6(2) New Installation, New Server Flash Cut or New Server Migration

59 Installation Logs Reference 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 Unified CM 8.X installation On failure, edit guest OS to connect to a temporary file to virtual serial port Accept dumping of logs Download 7zip from to unzip the tar file Remove serial port after a successful installation of Unified CM 8.X

60 Unified CM 9.X Upgrade Considerations Upgrade or new installation of Unified CM 8.0 or higher will not support Cisco Attendant Console (CAC) Migrate to Cisco Unified X Attendant Console (CUxAC) before or during Unified CM 9.X upgrade Media size of some version of 8.6 and later will not fit on a single layer DVD. Check to ensure that servers supports dual layer DVD Clear out logs in /common partition for upgrade Minimize CAR to reduce upgrade time CCMUser pages is revamped or change for users with 9.X PAB is not migrated for Unified CM 9.X End-of-Sale and End-of-Life Announcement for the Cisco Unified Attendant Console::

61 5 Servers, Clusters, and UC Application Upgrade/Migration Definition

62 Server Upgrade/Migration Definition New Server Upgrade Existing Unified CM Servers in Cluster Older Server New Server Upgraded Unified CM Servers in Cluster In-Place Server Upgrade Same Recent Server

63 Cluster Upgrade/Migration Definition 1 2 Existing Unified CM Cluster Existing Unified CM Cluster In-Place Server Flash Cut / Upgrade New Server Migration New Unified CM Cluster New Unified CM Cluster

64 In-Place Server Flash Cut 1 Existing Publisher Upgrade servers in the order shown Upgrade should be done after hours if possible New Publisher Complete all server upgrades before switching versions 2 Existing TFTP New TFTP 3 4 Existing Backup Subscriber New Backup Subscriber Existing Active Subscriber New Active Subscriber

65 In-Place Server Flash Cut: 8.X and Below Existing Unified CM Cluster Existing Unified CM Cluster Existing Unified CM Cluster New Unified CM Cluster New Unified CM Cluster New Unified CM Cluster Back Up With DRS Upgrade Publisher Inactive Partition Upgrade Subscribers Inactive Partition Switch Partition on Publisher Switch Partition on Subscriber Upload SW Feature License sftp Server or Tape Unified CM DVD Kit Unified CM DVD Kit CLI or OS Admin CLI or OS Admin Feature SW License

66 In-Place Server Flash Cut: 9.0 and Above Existing Unified CM Cluster Existing Unified CM Cluster Existing Unified CM Cluster New Unified CM 9.X Cluster New Unified CM 9.X Cluster CUELM Back Up With DRS Upgrade Publisher Inactive Partition Upgrade Subscribers Inactive Partition Switch Partition on Publisher Switch Partition on Subscriber Add CUCM to CUELM sftp Server or Tape Unified CM 9.X DVD Kit Unified CM 9.X DVD Kit CLI or OS Admin CLI or OS Admin

67 New Server Migration 1 Existing Publisher Build servers in the order shown New cluster uses a new set of IP addresses New Publisher 2 Existing TFTP Use CSS and partitions to ensure call routing is correct Build inter-cluster trunk between the existing and new cluster New TFTP Move data from existing cluster to new cluster 3 Existing Backup Subscriber Upgrade new cluster to new version of Unified CM Recommended where there are many UC applications and phases of migration is important, i.e., CUCCX New Backup Subscriber 4 Existing Active Subscriber Recommended for medium to large network especially where there are many sites and departments where migration is important Recommended to minimize outages New Active Subscriber

68 New Server Migration ICT Existing Unified CM Cluster New Unified CM Cluster New Unified CM Cluster New Unified CM Cluster New Unified CM Cluster New Unified CM Cluster Back Up With DRS Upload Licenses Switch Partition Upgrade Inactive Partition Restore With DRS and license files Install Unified CM sftp Server or Tape Feature SW License CLI or OS Admin Unified CM DVD Kit sftp Server or Tape Unified CM DVD Kit

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

70 Overall Upgrade Strategy for One-step Upgrade to Minimizing Down Time Phase I: Phase II: Phase III: Phase IV: IP Phone Firmware Upgrade UC Applications Pre- Upgrade Migration Unified CM and UC Applications Post Upgrade Migration License acquisition within 60 days phase III IP Phone Firmware UC Applications Upgrade Unified CM Upgrade Phase I, II or III might have to be repeated for each of the step in a multi-steps upgrade Check with Compatibility Matrix on Collaboration applications and firmware compatibility UC Applications Upgrade Cisco IP Phone Firmware by Unified CM Releases:

71 Phase I: 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 Unified CM 5.1(1c) or later: System > Service Parameter > Cisco TFTP (Advance) Maximum Serving Count (default is 200 for Windows and 500 for appliance) 1,500 for single processor dedicated TFTP server and 3,000 for dual processors dedicated TFTP server Peer-to-Peer Image Distribution (PPID):

72 Phase I: Upgrade Caveat Phone 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) Unified CM 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 Unified CM cluster Firmware Release Notes 8.5(2)SR1:

73 Phase III: Unified CM Upgrade Consideration Clustering over the WAN (COW) can increase time for installation, upgrade and database (DB) replication by 40% 50% Firewall between Unified CM servers After upgrade, check for the following using CLI, RTMT and Unified Reporting (details in notes section) Cluster Manager Connectivity CLI: show network cluster DB replication state Unified CM SRND:

74 Bridge Upgrade for Platform Change Servers supported to run Unified CM version X Upgrade Servers supported to be in Bridge mode on Unified CM version Y DRS Secure FTP Server DRS File DRS Unified CM in a virtualized environment Bridge Upgrade is available starting with 8.0(2) Allows for a successful upgrade with CM service in shutdown state Extended upgrade for older platforms to enable platform changes using DRS Use case for MCS and UCS platform change or older servers that need a platform change 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 Replacing a Single Server or Cluster for Cisco Unified Communications Manager:

75 6 Upgrade and Migration Strategy for Cisco Unified Communications Manager 6.1, 7.1, 8.0, 8.5 and 8.6 to 9.0

76 Platform Assessment for Bare Metal Servers Platform Number Supported Normal Mode Supported Bridge Supported Cisco Unified Communications Manager Releases by Server: Not Supported Upgrade Strategy Upgrade to 7.1 to change platform Upgrade to 7.1 to change platform NA Upgrade to 7.1 to change platform Upgrade to 7.1 to change platform NA Upgrade to 7.1 to change platform NA Upgrade to 7.1 or 8.5 to change platform NA NA Latest MCS 7835/45-I3 support 7.1 or above. This is a good version for platform change 8.0 is not widely deployed Avoid bridge mode to reduce phone outage

77 Platform 1 to 6 Upgrade Existing Unified CM Cluster Existing Unified CM 7.1 Cluster Existing Unified CM 7.1 Cluster on New Servers In-Place Server Flash Cut / Upgrade Server Replacement In-Place Server Flash Cut / Upgrade Existing Unified CM 7.1 Cluster Existing Unified CM 7.1 Cluster on New Servers New Unified CM 9.X Cluster on New Servers

78 Platform 1 to 6 Migration Existing Unified CM Cluster Existing Unified CM 7.1 Cluster Existing Unified CM 7.1 Cluster on New Servers In-Place Server Flash Cut / Upgrade New Server Migration ICT In-Place Server Flash Cut / Upgrade Existing Unified CM 7.1 Cluster Existing Unified CM 7.1 Cluster on New Servers New Unified CM 9.X Cluster on New Servers

79 Platform 7 Upgrade and Migration 1 Existing Unified CM Cluster In-Place Server Flash Cut / Upgrade Existing Unified CM 9.X Cluster

80 7 Platform Conversion from MCS to UC on UCS

81 Platform Support

82 Platform Options C260 M2 1 Tested Reference Configuration (TRC) C210 M2 C200 M2 B200 M2 B230 M2 B440 M2 2 Specs-Based (Software) * Server selection, sizing and design cover in later sections Unified Communications Virtualization:

83 Tested Reference Configurations (TRC) Customers with lower virtualization proficiency Cisco prescribed hardware specifications Performance guarantee for UC applications Tradeoffs between hardware choices Chassis based: B440 M2, B230 M2 and B200 M2 DAS & FC SAN or FC SAN only Full width versus half width blade Rack-Mount: C260 M2, C210 M2 and C200M2 DAS only, DAS & FC SAN or FC SAN only Tested Reference Configurations (TRC):

84 TRC Based Platform Decision Tree Reference Start Rack-Mount Server YES Low Server Distribution YES C260 M2 TRC1 NO NO YES Low Server Distribution YES New E7 Processor DAS Only YES C210 M2 TRC1 B440 M2 TRC1 B230 M2 TRC1 NO YES NO FC SAN Only NO NO FC SAN Only NO YES C210 M2 TRC3 B200 M2 TRC2 B200 M2 TRC1 C210 M2 TRC2 Unified Communications Virtualization Supported Applications:

85 Specs-Based Hardware Customers with extensive virtualization proficiency Maximum hardware choices including Cisco, HP and IBM 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 family with minimum physical core speed of 2.53 GHz Intel Xeon 7500 family with minimum physical core speed of 2.53 GHz Intel Xeon E family with minimum physical core speed of 2.4 GHz Intel Xeon E family with minimum physical core speed of 2.4 GHz Intel Xeon E family with minimum physical core speed of 2.4 GHz C260 M2 and C210 M2 vcenter is mandatory DAS only, DAS & FC SAN or FC SAN only Specification-Based Hardware Support

86 TRC or Specs-Based Decision Tree Reference Virtualization Start Proficiency 1 HIGH Performance Guarantee NO UC Applications Supported by Specs-Based YES Specs- Based LOW YES NO TRC TRC TRC 1 1 Evaluation criteria for platform decision varies based on organization priorities Virtualization proficiency Performance guarantee Supported applications Platform and vendor choices Solution should be consistent, but can be hybrid Unified Communications Virtualization Supported Applications:

87 Platform Options 3rd- Party Complexity Intel Xeon 5600 Intel Xeon 7500 DAS (SATA, SAS) FC SAN (2Gbps+) + FCoE (10Gbps+) NFS iscsi Intel Xeon E Intel Xeon E Intel Xeon E Cisco C260 M2 C210 M2 C200 M2 TRC B440 M2 B230 M2 B200 M2 B200 M2 C210 M2 C200 M2 B440 M2 B230 M2 B250 M2 C460 M2 C250 M2 C260 M2 Specs-Based * Design tip: Ensure that all UC applications are supported on selected platform + DAS (SATA, SAS) FC SAN (2Gbps+) FCoE (10Gbps+) NFS iscsi Platform flexibility Tested Reference Configurations (TRC):

88 VMware Support

89 VMware Sphere Support vcenter is mandatory ESXi 4.0, 4.1 and 5.0 (No ESX) VMware vsphere Hypervisor, Essential, Essential Plus, Acceleration Kit, Standard, Enterprise or Enterprise Plus ISO for Cisco UCS for appropriate driver support is at: dhdizcvodw AlJQ VMware vcenter (Essential, Foundation or Standard) Recommended for large deployment. centralize management, vram pooling, license management, etc. Mandatory for Specs-Based deployment VMware acquisition: Cisco, Partner or VMware Hypervisor Support for Virtualized UC:

90 ESXi 5.0 Edition Decision Tree for Cisco UC Reference Start Distributed vswitch NO Nexus 1000V YES YES Enterprise Plus Enterprise Plus System memory average can be adjusted by changing edition or adding CPU license Single memory pool is simpler and more efficient to manage NO System Average 96 GB per CPU YES Enterprise Plus NO System Average 64 GB per CPU YES Enterprise NO Storage vmotion NO YES Enterprise Standard

91 Cisco Virtual Template (OVA) File CCO OVA 1 vsphere Client OVA Files for UC on UCS Deployments: 2 UCS B200 M2 Open Virtual Format (OVF) is a collection of files (workload states, meta files, description file, etc.) describing virtual machines. 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

92 CUCM and VMware Guest OS Type RHEL 4 CUCM 8.0 or 8.5 Upgrade RHEL 5 CUCM 8.6/9.0 Unified CM RHEL Release 5.0(4) RHEL 3 Update 6 5.1(x) & 6.X RHEL 3 Update 8 7.0(1) RHEL 4 Update 4 7.1(2) RHEL 4 Update 6 7.1(3) & 8.0(1) RHEL 4 Update RHEL 4 Update RHEL 5 Update 5 9.0/9.1 RHEL 5 Update 7 * Upgrade to CUCM 8.6 from previous appliance is a new Refresh Upgrade with more downtime

93 UC Application Migration

94 Platform Assessment for Virtualization Platform Number Supported Normal Mode Supported Bridge Not Supported Upgrade Strategy Upgrade to 8.0 to go virtual Upgrade to 8.5 to go virtual NA Upgrade to 8.5 to go virtual Upgrade to 8.0 to go virtual NA Upgrade to 8.0 to go virtual NA Upgrade to 8.5 to go virtual NA NA Upgrade to ELM to go virtual Virtualization is only supported with 8.0 or above Avoid bridge mode to reduce phone outage Supported Cisco Unified Communications Manager Releases by Server:

95 Virtualization Conversion for Unsupported Servers TYPE 1 Servers Servers Platform Conversion with DRS TYPE 2 Servers TYPE 3 Servers TYPE 4 Servers For servers that can not be upgrade to CUCM 8.0 or later Use DRS to swap appliance to type 1 to type 7 server type (bridge hardware) Use the type 1 to type 7 platform conversion to get to UCS Using VMware in-lieu of bridge hardware is not supported

96 Virtualization Conversion with BAT Export TYPE 1-7 Servers BAT Export BAT Data BAT Import CUCM 8.6/9.0 on UCS in Production Leverage CUCM 7.1 or later Bulk Admin Tool (BAT) and export all data Use BAT to import all data in to the newly installed CUCM UCS system Normalize services in each CUCM node Migration can be done with dual clusters

97 Migration Recommendations for Unified CM Upgrade Break the system upgrade into phases to minimize downtime Phase 1: Upgrade phone firmware to match destination version Phase 2: Finish all of the pre-upgrade migration UC applications Phase 3: Upgrade Unified CM for flash cut or migration using ICT and CSS/partitions Have USB key available for diagnostic information dump in case of upgrade failure Check Unified Communications Virtualization docwiki often due to frequent changes Verify UC applications, ESXi version, ESXi edition, ESXi features, servers platform and storage type to ensure support of the complete system

98 Questions?

99 Call to Action Visit the Cisco Campus at the World of Solutions to experience Cisco innovations in action Get hands-on experience attending one of the Walk-in Labs Schedule face to face meeting with one of Cisco s engineers at the Meet the Engineer center Discuss your project s challenges at the Technical Solutions Clinics 99

100 100

101