BRKUCC-2011 Best Practices For Migrating Previous Versions of Cisco Unified Communications Manager (CUCM) To CUCM 8.6

Best Practices for
Migrating Previous
Versions of Cisco Unified
Communications Manager
(CUCM) to CUCM 8.6
BRKUCC-2011
www.ciscolivevirtual.com
CM = CUCM = Cisco Unified
Agenda
Upgrade and Upgrade

Installation
Migration and
CM 8.6 Process Platform
definitions Migration
Upgrade CM 8.X and Best Conversion
for servers, Strategies
definitions Licensing Practices from MCS
clusters and for earlier
and paths for CM 7.1 to UCS
UC versions of
and 8.6
applications CM to 8.6
BRKUCC-2011 © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
Session Scope
Unified CM 6.1(X)
Unified CM 7.1(X)
Unified CM 8.0(X) Unified CM 8.6(2a)
Unified CM 8.5(X)
Unified CM 8.6(1)
B200 M2
Platform Conversion
C210 M2
C200 M2
MCS Servers HP or IBM Servers UC on UCS
CM 8.6 Upgrade Definitions and
Paths
Release Numbering Changes from 8.0
Major Releases 5.0, 6.0, 7.0 8.0
Minor Releases 5.1, 6.1, 7.1 8.5, 8.6
 Version 8.X is the only version with 8.6 minor release

 Change from .1 to .5 was introduced to align with system
release numbering
Unified CM Major/Minor Upgrade Definition
W1 W1 Upgrade: Windows to Appliance model
L2 L2 Upgrade: Appliance to Appliance model
RU RU (Refresh Upgrade): Appliance to Appliance
W1 W1 Upgrade: Windows to Appliance model
 High complexity with possible longest downtime

 I.E. Unified CM 4.1(3), 4.2(3), or 4.3(2) to 7.1(5b)
L2 L2 Upgrade: Appliance to Appliance model
 Low complexity with possible shortest downtime

 Only between Unified CM versions 5.X, 6.X, 7.X,
8.0 and 8.5
 I.E. Unified CM 5.1(3), 6.1(5) or 7.0(2) to 7.1(5b)
RU RU (Refresh Upgrade): Appliance to Appliance
 Medium complexity with possible longer downtime

 From Unified CM versions 6.X, 7.X, 8.0 or 8.5 to
8.6
 Server is down while upgrade software is installed
 Equal to a complete installation
W1 Upgrade: Windows to Appliance
Existing Existing Existing New Unified New Unified New Unified

Unified CM Unified CM Unified CM CM 7.1 CM 7.1 CM 7.1
4.X Cluster 4.X Cluster 4.X Cluster Cluster Cluster Cluster
Back Up Install Install, Run, Install Upload Upload
With BARS and Run and Unified DMA File Licenses
Upgrade Download CM 7.1
Utility on All DMA on
Servers Publisher
Data Migration
Latest Upgrade
Assistant (DMA)
Utility From
7.1
CCO Unified Node, DLU and
Tape or Save DMA File to Tape, FTP or
Network Tape or Network CM 7.X sFTP Server 7.1 Feature SW
Share Share DVD Kit License
1 2 3 4 5 6
BRKUCC-2011 Details of W1 Upgrade Cisco
is Public
in Appendix A
© 2012 Cisco and/or its affiliates. All rights reserved. 11
L2 and RU Upgrade: Appliance to Appliance
Updated
Unified CM
SW
2
Unified CM Unified CM
Publisher Active Partition inActive Partition Publisher
1 InActive partition Active partition
Switch
Active Partition Version via inActive Partition
Unified CM
Unified CM Subscriber
Subscriber InActive partition OS Admin Active partition
or CLI
InActive becomes Active
Is the existing
Unified CM
YES Perform a L2
appliance version Upgrade
CM 8.6?
Existing Unified
CM appliance NO
Upgraded
being upgraded Unified CM
to Unified CM
Perform a RU
Upgrade 8.6
8.6
RU
L2
RedHat RHEL 3 RHEL 4 RHEL 5

Enterprise Linux
Version
CUCM Version 5.0, 6.0 7.X, 8.0, 8.5 8.6

Future upgrades between RHEL versions will be RU
L2 Upgrade: Appliance to Appliance (8.6)
Active Partition Running InActive partition Dormant
InActive partition Active Partition
1.RPMs Reboot 1. Firmware and BIOS
installation upgrade
2.DB installation 2.Unified CM
3.Data Migration installation
3.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
Refresh Upgrade (RU): Appliance to Appliance
Active Partition Running InActive partition Dormant

InActive partition Active Partition
1. Data exported Reboot 1. Firmware and Reboot
(Unified CM and BIOS upgrade
CAR) into 2.VOS installation
/common partition 3. Platform import
InActive partition Dormant

Active Partition
1. Unified CM
installation
2. DB installation
3. Unified CM
data import
4.CAR DB
creation
5.CAR DB
migration
Refresh Upgrade (RU) Notes
 Publisher (1st Node)  MCS7825H3 –needs 16Gb

 Track console (KVM)  MCS7828H3 – needs 128Gb
 Install COP file before 8.6  Externally Powered
 Stay updated to keep upgrades simple  Log Files MCS7835/45
7825/28 – can’t access USB drive
“Unable to download the kickstart file. Please modify the kickstart
parameter below or press Cancel to proceed as an interactive installation.”
 Seen with 8.6(2a)

 Could happen if USB
drive is USB powered
and connected to the
front of the 7825
Try moving the USB
powered to the rear
USB ports and reboot
One-Step Minor Upgrades (Appliance)
Unified CM 6.1(4)
Unified CM 6.1(4a/b)
Unified CM 6.1(5)
Unified CM 7.1(3)
Unified CM 7.1(3a/b) RU Unified CM 8.6(2a)
Unified CM 7.1(5)
Unified CM 7.1(5a/b)
Unified CM 8.0(X)  CSCto45041 - 8.5.1 should be upgraded to
8.5.1SU1 before upgrading to 8.6(2a)
Unified CM 8.5(X)
Unified CM 8.6(1)
Unsupported Upgrade to Version 8.6(1a)
Unified CM 7.1(5)SU4 RU Unified CM 8.6(1a)
Unified CM 7.1(5)SU4 RU Unified CM 8.6(2a)
Latest SU updates of 7.1(5) SU4 are not supported

to be upgraded to version 8.6.(1a)
Two-Step Major / Minor Upgrades (Windows)
Unified CM 4.1(3) W1 RU
Unified CM 4.2(3) Unified CM 7.1(5b) Unified CM 8.6(2a)
Unified CM 4.3(2) + Security Update
 Upgrade from 4.X to 7.1(5b) – without SU

 Might upgrade to an SU release before running in production
 Might consider staying with the later 7.1(5b) to align all other
collaboration applications before going to 8.6(2a)
Two-Step Minor Upgrades (Appliance)
Unified CM 5.1(3) L2 RU
SU4
Unified CM 7.0(2a)
 For end of support and appliance versions of Unified CM

 Focus on the 7.1 key versions that can be upgraded to 8.6(2a)
 Appliance releases can upgrade directly to an SU
Three Step Major/Minor Upgrade (Windows)
Unified CM 3.3(5)
MAJOR
UPGRADE
W1 RU
Unified CM 4.0(2a)
MINOR
Unified CM 3.3(5) UPGRADE

Unified CM 4.1(3) W1 RU
Unified CM 7.1(5b) Unified CM 8.6(2a)
Unified CM 4.0(2a) Unified CM 4.2(3)
 Minimise major upgrade step(s)

 Focus on the two key versions that can be upgraded to 7.1(5b)
before going to 8.6(2a) - 4.1(3) and 4.2(3)
Multi-step Minor Upgrades (Appliance)
3-steps 4-steps
RU RU
Unified CM 6.1(1) Unified CM 8.6 (2a) Unified CM 6.0(1) Unified CM 8.6(2a)
 Various paths & same number of steps to get to target version

 Minimise major version changes to minimise user impact
i.e. 6.1(1) -> 6.1(3b) -> 6.1(5) SU3 -> 8.6(2a)
6.1(1) -> 7.0(2a) SU3 -> 8.0(3a) -> 8.6(2a)
i.e. 6.0(1) ->6.1(1) -> 6.1(3b) -> 6.1(5) SU3 -> 8.6(2a)
6.0(1) -> 6.1(1) -> 7.0(2a) SU3 -> 8.0(3a) -> 8.6(2a)
Upgrades for Engineering Special (Appliance)
Unified CM 6.X ES
RU Unified CM 8.6(2a)
Unified CM 7.X ES
 Engineering special does not have any impact on direct or

one-step upgrade
 Upgrade directly to the supported target version
 Follow the direct upgrade table in the compatibility matrix
Engineering Special (ES) and Windows SR Upgrade Note:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html#wp72412
CM 8.X Licensing Summary
License Types
Based on the Number of Unified CM

Servers in the Cluster
Unified CM Servers Node License
in Cluster
Based on the Number of IP Phones and the Types of

Phones in the Cluster Including Video Terminals, ATA Device
IP Phones in GW, and Mobility Feature License Unit
Cluster .
Upgrade Required for Major Version

(final Upgrade
SW Feature
Unified CM version) Unified CM License
4.x, 5.X, 6.X or 7.X 8.X
License MAC is new starting with 7.1(3) and 8.X and will be covered in a later slide
License BRKUCC-2011
File is based on© the MAC
2012 Cisco and/or itsaddress or LicenseCiscoMAC
affiliates. All rights reserved. Public of the First Node of Unified CM Cluster
27
CM 8.X New Installation License Request
Based on the Number of Cisco will Send in

Unified CM Servers in Product Email
UCL or CUWL the Cluster Activation Key Node License
Order (PAK)
Based on the Number and Cisco will Send in

Type of users Product Device Unit
Activation Key Email
UCL or CUWL License
(PAK)
Order
http://www.cisco.com/go/license
UCL is introduced with Unified CM version 7.1(5) or later and 8.0(1) or later
Unified CM 7.1 Upgrade License Req.
Migration Process *
Unified CM 4.X Unified CM 7.1 Temporary Node and
Cluster Cluster Device Unit License
Based on the Number Cisco will send in

servers in the cluster Product Email
Unified CM SW Feature
Activation Key License
Upgrade Order (PAK)
Cisco CallManager Device Upgrade License
Permanent
Temporary Node Node and
and Device Unit * DMA 7.1 will generate temporary Node and DLU license locally Device Unit
License on old publisher License
Unified CM Licensing:
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/admin/8_5_1/ccmfeat/fslicense.htmll
Unified CM 8.X Upgrade License Req
Major Version Upgrade

Unified CM Permanent Node and
Unified CM 5.X, 6.X 8.X Cluster Device Unit License
or 7.X Cluster
Based on the Cisco will send in

Number servers in Product Email
Unified CM SW Feature
the cluster Activation Key
Upgrade License
(PAK)
Order
Cisco CallManager Device Upgrade License
Unified CM Licensing:
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/admin/8_5_1/ccmfeat/fslicense.html
DLU and UCL License Migration
Unified CM 7.1(5)
Unified CM 7.1(4) and later
and earlier Unified CM 8.X
Device License User Connect
Unit (DLU) License (UCL)
 Upgrade to beyond 7.1(4) changes the licensing model from DLU to UCL
 License enforcement is still DLU with UCL
 UCL includes Single Number Reach (SNR) or Mobile Connect feature which
requires 2 DLUs per phone and is free for customers with current ESW and
UCSS contract
 Open case with licensing@cisco.com and provide upgrade order number for
major upgrade or UCSS contract number for minor upgrade downloaded
from CCO
License MAC for UC on UCS
 License MAC is 12 digit HEX value based on the hash of these 10

Unified CM settings
1. Certificate Information 3. IP Address or dhcp 7. NTP server 1

(Organisation, Unit, 4. IP Mask or dhcp 8. Primary DNS
Location, State, Country)
5. Gateway Address or dhcp 9. SMTP server or none
2. Hostname
6. NIC speed auto 10. Time zone
Cisco Unified Communications Answer File Generator for License MAC:

http://www.cisco.com/web/cuc_afg/index.html
License MAC for UC on UCS with 8.X
Show > Status Show > Network
Changes and Effect on License MAC
If you change one of

30 day grace Grace period > 30days
the 10 CUCM
period starts - CM service stops
license MAC
- License file is
settings
invalidated forever
Revert changes to
original settings,
30 day timer stops
Answer File Generator

Upgrade and Migration Definitions
for Servers, Clusters and UC
Applications
Server Upgrade and Migration Definition
Existing
Unified CM
Servers in
Cluster
1 Unified CM
New Server Upgrade
Unified CM 8.6
Upgraded
Unified CM
Servers in
Cluster
4.X/5.X/6.X/7.X/8.0/8.5
2 In-Place Server Upgrade/Migration
Unified CM Unified CM 8.6

4.X/5.X/6.X/7.X/8.0/8.5
Cluster Upgrade and Migration Definition
In-Place Server—Flash Cut
In-Place Server—Hybrid Migration
New Server—Flash Cut
New Server—Migration
In-Place Server — Flash Cut
Appliance to Appliance
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  Switching versions should be done as soon as upgrade of all

servers is completed to avoid loss of admin / user changes
 This approach is recommended for appliance to appliance
New TFTP
upgrade
3 Existing
Backup
Subscriber
New Backup
Subscriber
4 Existing Active
Subscriber
BRKUCC-2011 For Existing Servers That Can Run Unified CM 7.X

© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public
New Active
Subscriber
39
In-Place Server — Hybrid Migration
Windows to Appliance
1 Existing
Backup
Subscriber
 Existing backup subscriber is not the call processing server
 Be careful about duplicate IP addresses
New
Publisher
TFTP
2 Existing TFTP  Can use new IP addresses in new cluster

 New DHCP option 150 points to new TFTP server
 Phones can re-home to new TFTP and new active subscriber
New Active
Subscriber
*Make sure existing 4.X active sub is off
3 Existing Active
Subscriber
 New backup subscriber is online for redundancy New Backup
Subscriber
4 Existing
Publisher
BRKUCC-2011
 Save the Existing Publisher for last in case of downgrade
 Once upgrade is deemed acceptable
Change DHCP option 150 back to new TFTP server
Revise activated services as required
New
TFTP
40
New Server — Flash Cut
Windows to Appliance or Appliance to Appliance
1 Existing
Publisher
 Build servers in the order shown
 New cluster can use the same IP address or new IP addresses;
New
Publisher
potential ACL impact
2 Existing TFTP  Option 1: Same IP addresses and switch host/ports

 Option 2: New IP addresses and change DHCP
option 150
New
TFTP
3 Existing
Backup
Subscriber
 Recommended for small to medium network without other
complex UC applications
New Backup
Subscriber
4 Existing Active
Subscriber
BRKUCC-2011 © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public
New
Active
Subscriber
41
New Server — Migration
Windows to Appliance or Appliance to Appliance
1 Existing
Publisher
 Build servers in the order shown
 New cluster uses a new set of IP addresses; potential ACL
New
Publisher
impact
2 Existing TFTP  Use CSS and partitions to ensure call routing is correct New
TFTP
3 Existing
Backup
Subscriber
 Build intercluster trunk between the existing and
new cluster
 Recommended where there are many UC applications and
phases of migration is important, i.e., CUCCX
New Backup
Subscriber
4 Existing Active  Recommended for medium to large network especially where

Subscriber
BRKUCC-2011
there are many sites and departments where migration is
important
 Recommended to minimise outages
New
Active
Subscriber
42
UC Application Upgrade / Migration Definition
Upgrade Time Increases with Various Dependencies
UC Applications Migration Strategy
CER
CUCCX
CUCCE
CUP
1 Pre-Upgrade Migration
UC Applications
Upgrade
Down Time
Unified CM
Upgrade
Down Time
MP MPE
2
Unity Post Upgrade Migration
Unity
Connection
Unified CM UC Applications
Upgrade Upgrade
Down Time
Cisco Unified Communications Manager Software Compatibility Matrix:

BRKUCC-2011 © 2012 Cisco and/or its affiliates. All rights reserved.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html Cisco Public 43
Overall Upgrade Strategy for One-step
Upgrade to Minimising Down Time
1Phase I:
2 3
Phase III:
Phase II:
IP Phone Unified CM and UC
UC Applications
Applications Post
Firmware Upgrade Upgrade Migration
Upgrade Migration
IP Phone UC Applications Unified CM

Firmware Upgrade Upgrade
 May repeat phase I,II or III in a multi-step upgrade

 Check Compatibility Matrix Collaboration UC Applications
applications and firmware compatibility Upgrade
Cisco IP Phone Firmware by Unified CM Releases:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html
Phase I: Phone Firmware Distribution
 PPID (P2P Image Distribution)  Temp change to TFTP service

parameter for dedicated
 Disabled by Default TFTP server on Unified CM
5.1(1c) or later:
 Enable via BAT or CCMAdmin
 1,500 for single processor dedicated
 Per Subnet distribution TFTP server (temp setting)
 3,000 for dual processors dedicated

TFTP server (temp setting)
Peer-to-Peer Image Distribution (PPID) :
http://www.cisco.com/en/US/docs/voice_ip_comm/cucmbe/admin/8_5_1/ccmsys/a08ipph.html#wp1141991
Phase I: Phone Firmware Upgrade Caveat
Some 3rd-gen IP phones All 3rd-gen
79x1 IP phones:
7970
7906
on CUCM 4.1.2 8.3(2)SR1
6.0(1) default fw Or earlier
CM 8.6(2) 7.0(3) 8.5(2)

Default Firmware
9.2(1)
8.5(2) 8.5(2)SR1
9.2(1) 9.2(1)
Firmware Release Notes 8.5(2)SR1:
http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/firmware/8_5_2/english/release/notes/7900_852SR1.html 46
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
 DB replication state
 Connectivity
Unified CM SRND:
www.cisco.com/go/ucsrnd
Installation Process and Best
Practices for CM 7.1. and 8.6
Overview of Unified CM 7.1 Installation
MCS-781X
MCS7825
Unified CM MCS7828
7.1 DVD KIT MCS7835
MCS7845
INSTALLATION PROCESS (PROCEED)
Import Data from Windows

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

1 2
Apply SR, ES or SU
Basic Install
Upgrade During New Installation, New Server—
Installation Flash Cut or New Server—
i.e., 8.6(1) to 8.6(2) Migration
Bridge Upgrade Feature in Unified CM 8.0(2)
MINOR
UPGRADE DRS
1 Unified CM 6.1/7.X
Supported server for

Unified CM 8.X
NOT supported for

Secure FTP
Server
production use of Unified production use of Unified

CM 6.1 and 7.X CM 8.X
2 DRS Unified CM 8.X Unified CM 8.X

DRS
or
Secure FTP Supported server for Secure FTP
Server production use of Unified Server
CM 8.X
Replacing a Single Server or Cluster for Cisco Unified Communications Manager:

http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/install/8_0_2/cluster/clstr802.html
Installation Logs
USB Key for Physical Add serial port to VM (before power on)
Server
 On failure, virtual serial port > temp file
 Accept Dumping of logs
 Accept dumping of the logs
Use 7Zip to unzip the TAR file
Remove serial port after install
Unified CM 7.1 Upgrade Install Caveat
Upgraded 7.1 New install 7.1 Upgrade or New

install 8.x
Will have CAC Plugin Will NOT have CAC Migrate to Cisco
Plugin. Unified X Attendant
Console
Contact TAC to be
directed to the plugin
link
Upgrade and Migration Strategies
for CM 6.1, 7.1, 8.0 and 8.5 to 8.6
Unified CM Upgrade Options
Existing 6.1 or
7.1 Cluster
Bridge Upgrade
Unsupported New Server - Migration

servers for
Unified CM 8.6
Existing
6.1,7.1, 8.0 or
8.5 Cluster
In-Place Server—Flash Cut
Supported
servers for
Unified CM 8.6
Bridge Upgrade Feature Process
Existing 6.1 or 7.1 New 8.6 Cluster on New 8.6 Cluster on New Cluster on new New 8.6 Cluster on New 8.6 Cluster on
Cluster old hardware old hardware hardware new hardware new hardware
Upgrade
Back Up With Install Restore With Upload
Inactive Switch Partition
DRS Unified CM DRS Licenses
Partition
8.X
Unified CM sFTP Server Unified CM 8.6 sFTP Server 8.X Licenses

8.6 DVD Kit CLI or Tape DVD Kit or Tape
or
OS Admin
1 3 4 5 6
2
New Server Migration
ICT
Existing Unified New Unified New Unified New Unified New Unified New Unified
CM 6.1 or 7.1 CM 8.6 Cluster CM 8.6 Cluster CM 8.6 Cluster CM 6.1 or 7.1 CM 6.1 or 7.1
Cluster Cluster Cluster
Back Up Upload Switch Upgrade Restore Install

With DRS Licenses Partition Inactive With DRS Unified
Partition and license CM
files
sFTP Feature SW Unified sFTP Unified CM 6.1

Server or License CLI CM 8.6 Server or or 7.1 DVD Kit
Tape or DVD Kit Tape
OS Admin
1 6 5 4 3 2
For existing servers

BRKUCC-2011 thatits cannot
© 2012 Cisco and/or run
affiliates. All rights Unified CM
reserved. Cisco8.6
Public in medium to large size network 57
Upgrade In-Place Server—Flash Cut
Existing 6.1, 7.1, Existing 6.1, 7.1, Existing 6.1, 7.1, New 8.6 Cluster New 8.6 Cluster New 8.6 Cluster
8.0 or 8.5 Cluster 8.0 or 8.5 Cluster 8.0 or 8.5 Cluster
Switch Switch
Back Up With Upgrade Upgrade Partition Partition Upload
DRS Publisher Subscribers on on 8.X SW
Inactive Inactive Partition Publisher Subscriber Feature
Partition License
sFTP Unified Unified Feature SW

Server or CM 8.6 CM 8.6 CLI CLI License for 6.1 and
Tape DVD Kit DVD Kit or or 7.1 Upgrade*
OS Admin OS Admin
1 2 3 4 5 6
BRKUCC-2011 For Existing Servers That Can Run Unified CM 7.1

© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 58
8.6 Downgrade to 6.1, 7.1, 8.0 or 8.5
 Reverting back to Unified CM
Unified CM Unified CM Unified CM, 6.1, 7.1, 8.0 or 8.5 requires
8.6 Cluster 8.6 Cluster 6.1, 7.1, 8.0
or 8.5 Cluster resetting DB replication
Switch Switch
CLI: utils dbreplication reset all
Partition Partition
on
Publisher
on
Subscriber
Utils dbreplication
reset all
 For MCS7825H3 or
MCS7828H3, reinstall and
perform DRS restore
IDS IDS
CLI CLI  Documented in caveats

or
OS Admin
or
OS Admin CLI CSCsl57629 and CSCsl57655
1 2 3
BRKUCC-2011 CSCsl57629 and CSCsl57655

© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 59
Platform Conversion from MCS to
UC on UCS
Platform Options
1
B200 M2
UC on UCS (Hardware) C210 M2
C200 M2
2 Specs-Based (Software)
(Subset of UC applications)
Unified Communications Virtualisation:

http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization
UC on UCS – Tested Reference Configurations
 UCS B200 M2:  UCS C210 M2:  UCS C200 M2:

 DAS (VMware) and  DAS (VMware & UC
 DAS (VMware & UC
FC SAN (UC Applications) *
Applications)
Applications)  DAS (VMware) and FC SAN
 FC SAN (VMware (UC Applications)
and UC Applications)  FC SAN (VMware & UC
Applications)
 Defined, tested and documented

 Positioned for customers fairly new to virtualisation
Tested Reference Configurations (TRC):

* Some TRC requires spare 62
drive
http://docwiki.cisco.com/wiki/Unified_Computing_System_Hardware
TRC Based Platform Decision Tree *
1000 or less YES
Start C200M2 1
user site
NO
Direct Attached YES

Storage only C210M2 2
NO
Centralised YES
Management B200M2 3
NO
C210M2 4
* UC applications and versions that are supported in selected TRC #
Unified Communications Virtualisation Supported Applications:

http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications Cisco Public 63
UC on Specs-Based
 VMware hardware compatible list (HCL) are supported

 Positioned for customer with extensive virtualisation
experience
 Cisco Supports UC applications only, not performance of
the server
VMware Hardware Compatibility List (use System and I/O tab):

http://www.vmware.com/go/hcl
Platform Decision Tree and Sizing
UC Application
Start supported with NO Total vCPUs, RAM, storage Select and customise
Specs-Based? 1
required per site based on
number of locations
platform based on cores,
memory and I/O
YES
Total vCPUs, RAM, storage
TRC-Based Select TRC platform base on
Systems
1
required per site based on
number of locations chassis and storage
 TRC-Based supports more UC applications than Specs-

Based
 Design approach for Specs-Based is to select and customise
the platform to maximise applicability
 Design approach for TRC-Based is to select the TRC # or
type and the quantity of TRC platforms
Unified Communications Virtualisation Supported Applications:
http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications
Platform Options
Complexity
DAS (SATA, SAS)

FC SAN (2Gbps+)
3rd-Party
Intel Xeon 5600
+ FCoE (10Gbps+)
NFS
Intel Xeon 7500 iSCSI
B200 M2 B200 M2 B440 M1 DAS (SATA, SAS)

FC SAN (2Gbps+)
Cisco C210 M2 C210 M2 B230 M1
C460 M1
C250 M2
+ FCoE (10Gbps+)
NFS
iSCSI
C200 M2 C200 M2 B250 M2
TRC Specs-Based Platform

flexibility
* Design tip: Ensure that all UC applications are supported on selected platform
Tested Reference Configurations (TRC):
http://docwiki.cisco.com/wiki/Unified_Computing_System_Hardware
VMware Sphere Support
 No ESX. ESXi 4.0, 4.1 and 5.0 only
ISO for Cisco UCS for appropriate driver support is at
http://downloads.vmware.com/d/details/esxi41_cisco_oe
m_iso/ZHcqYnRkdHdiZCVodw
 VMware vCenter Server

Essential, Foundation or Standard
vCenter
Server  VMware Pricing
https://www.vmware.com/files/pdf/vsphere_pricing.pdf
 Cisco UC Virtualisation Hypervisor and Foundation
Hypervisor Support for Virtualised UC:

http://docwiki.cisco.com/wiki/Unified_Communications_VMWare_Requirements
Cisco UC Virtualistion
Cisco UC Virtualisation Cisco UC Virtualisation VMware vSphere Standard
Hypervisor Foundation
Used for BE6K UC on UCS and BE6K UC on UCS or general-

purpose
Allowed Ships as either 4.1 or 5.0 depending on SKU Ships 5.0 only, option to
Versions downgrade to 4.x at time of
license activation
Feature set None vCenter vCenter + HA + vMotion
Max CPUs / 2 sockets >2 sockets
UCS
Max vcpu / VM 4-way (8-way with 5.0) 8-way 4-way (8-way with 5.0)
Max ∑vRAM 14 GB 30 GB Unlimited (62 GB with 5.0)
/UCS
Cisco Virtual Appliance OVA/OVF File
OVA
2
CCO 1
vSphere
Client
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
 Download OVA file from CCO for Cisco UC applications
OVA Files for UC on UCS Deployments:

http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29 69
UC on UCS Application Co-Res Support
 Co-residence on the same server or blade is only with
UC applications only
B200 M2
 Separate server or blade for 3rd-party applications (i.e.
DNS), VMware (vCenter) and Cisco (Nexus 1000V)
 High level UC application allocation:
Total server cores = Total UC application vCPU requirement
Server memory = Total UC application memory requirement
+ 2GB *
Unified CM Unified CM Unified CM Unified CM Unity Connection requires one idle or free vCPU per server
* Newer versions of CUC requires more memory so change OVA settings

Application Co-residency Support and Server/Storage Selection:
http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Sizing_Guidelines Cisco Public 70
Example B Series UC on UCS
CUCM 8.6 VMware Guest OS Type
RHEL 4 RHEL 5
Upgrade
CUCM CUCM
8.0 or 8.5 8.6
MCS Server and Supported Unified CM Versions
TYPE 1 Servers
CUCM 8.0 in Production CUCM 8.5 in Production CUCM 8.6 in Production
TYPE 2 Servers
CUCM 8.0 in Production CUCM 8.5 in Bridge mode
TYPE 3 Servers
CUCM 8.0 in Bridge mode CUCM 8.5 in Bridge mode
TYPE 4 Servers
CUCM 8.0 in Bridge mode
TYPE 5 Servers
CUCM 7.X in Production
* List of servers by type is in the appendix

* Check the link below to ensure accuracy
Supported Servers for Releases of Cisco Unified Communications Manager:
http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd8062a4f9.html
Type 1: UC on UCS Platform Conversion
TYPE 1 Servers
Refresh Platform
Upgrade Conversion
CUCM 8.6 on MCS with DRS CUCM 8.6 on UCS
in Production in Production
 Type 1 servers can run CUCM 8.6

 Upgrade to CUCM 8.6 and run in production
 Upgrade and align all of the other UC applications to CUCM 8.6
 Migrate to UCS as required
Co-exist with other MCS servers for SMDI or USB MOH
Upgraded New New New New

Unified CM Unified CM Unified CM Unified CM Unified CM
8.6 on MCS 8.6 on UCS 8.6 on UCS 8.6 on UCS 8.6 on UCS
Install on
Install on DRS Upload
DRS Secondary
First node or Restore on Licenses
Backup node or
Publisher First node or
Subscriber
Publisher
Unified Unified
All three types CM 8.6
sFTP CM 8.6 sFTP
of licenses ISO Image
Server ISO Image Server
1 2 3 4 5
TYPE 2 Servers
L2 Upgrade Platform
Conversion
in Production in Production
 Type 2 servers can run CUCM 8.0 in production and bridge mode with CUCM 8.5
 Upgrade to CUCM 8.0 and run in production
 Upgrade and align all of the other UC applications to CUCM 8.0 or 8.6 if possible
 Migrate to UCS as required

Co-exist with other MCS servers for SMDI or USB MOH
 Refresh upgrade to CUCM 8.6. Guest OS change.

Install on
DRS secondary node
Backup or Subscriber
Publisher
Unified Unified
sFTP CM 8.0 sFTP
1 2 3 4 5
TYPE 3 Servers
L2 Upgrade Platform
Conversion
in Bridge mode in Production
 Type 3 servers can run CUCM 8.0 or CUCM 8.5 in bridge mode, but cannot be
upgraded to CUCM 8.6
 Upgrade to CUCM 8.5 in bridge mode
 Use DRS for platform conversion
 No migration
 Flash cut only
 Refresh upgrade to CUCM 8.6 once on UCS
 Guest OS change in VMware


Install on
DRS secondary node
Publisher
Unified Unified
sFTP CM 8.5 sFTP
1 2 3 4 5
TYPE 4 Servers
L2 Upgrade Platform
Conversion
in Bridge mode in Production
 Type 4 servers can run CUCM 8.0 in bridge mode, but cannot be upgraded to
CUCM 8.5 or CUCM 8.6
 Upgrade to CUCM 8.0 in bridge mode
 Use DRS for platform conversion
 No migration
 Flash cut only
 Refresh upgrade to CUCM 8.6 once on UCS
 Guest OS change in VMware

Type 4: UC on UCS Platform Conversion`

Install on
DRS secondary node
Publisher
Unified Unified
sFTP CM 8.0 sFTP
1 2 3 4 5
TYPE 1 Servers
TYPE 2 Servers
TYPE 5 Servers
Platform TYPE 3 Servers
Conversion
with DRS
TYPE 4 Servers
 Type 5 servers can not be upgrade to CUCM 8.0 or later

 Use DRS to swap appliance to a type 1-4 server (bridge
hardware)
 Use the a type 1-4 platform conversion to get to UCS
 Using VMware in-lieu of bridge hardware is not supported
UC on UCS Platform Conversion with BAT Export
TYPE 1 Servers
TYPE 2 Servers
TYPE 3 Servers
BAT Export BAT Data BAT Import
TYPE 4 Servers CUCM 8.6 on UCS
in Production
TYPE 5 Servers
 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
 Normalise services in each CUCM node
 Migration can be done with dual clusters
Summary
Break the upgrade into Have a USB key available
phases for capturing the diagnostic
- Phone Firmware information dump in case of a
- Dependent UC Apps failure
- Flash cut or Migration
Check UC DocWiki frequently Verify UC Applications

for updated info against VMWare versions
and storage to ensure
support of the complete
system
Appendix
Sample Unified CM 7 and 8 Versions and Builds
Unified CM 8.6(1a) 8.6.1.20000-1 Unified CM 7.1(5b) SU3 7.1.5.32900-2
 FCS build
Unified CM 8.5(1) SU2 8.5.1.12900-7 Unified CM 7.1(5b) SU2 always have
7.1.5.31900-3
three zeros
Unified CM 8.5(1) SU1 8.5.1.11900-7 Unified CM 7.1(5b) 7.1.5.30000-1  SU posted on
CCO
Unified CM 8.5(1) 8.5.1.10000-26 Unified CM 7.1(5a) 7.1.5.20000-6
 Numbering
Unified CM 8.0(3a) SU1 8.0.3.21900-8 Unified CM 7.1(5) SU1a 7.1.5.11901-1 convention:
1. Major version
Unified CM 8.0(3a) 8.0.3.20000-2 Unified CM 7.1(5) 7.1.5.10000-12
2. Minor version
Unified CM 8.0(3a) 8.0.3.10000-8 Unified CM 7.1(3b) SU2 7.1.3.32900-4 3. Maint. rel.
Unified CM 8.0(2c) SU1 8.0.2.41900-3 Unified CM 7.1(3b) SU1 7.1.3.31900-1 4. Build
Unified CM 8.0(2c) 8.0.2.40000-1 Unified CM 7.1(3b) 7.1.3.30000-1 5. Non SU = 000
Type 1 Servers
MCS-7825-H3 MCS-7828-I5
MCS-7825-I3 MCS-7835-H2
MCS-7825-H4 MCS-7835-I2
MCS-7825-I4 MCS-7835-I3
MCS-7825-I5 MCS-7845-H2
MCS-7828-H3 MCS-7845-I2
MCS-7828-I3 MCS-7845-I3
MCS-7828-I4 HP DL380G6
HP DL380G6
Type 2 Servers
MCS-7815-I2
MCS-7825-H2
MCS-7825-I2
Type 3 Servers
MCS-7815I-3.0 MCS-7845H-3.0
MCS-7815-I1 MCS-7845I-3.0
MCS-7825H-3.0 MCS-7835-H1
MCS-7825I-3.0 MCS-7835-I1
MCS-7835H-3.0 MCS-7845-H1
MCS-7835I-3.0 MCS-7845-I1
Type 4 Servers
MCS-7825-H1
MCS-7825-I1
License MAC for UC on UCS
 License MAC is 12 digits HEX values based on the hash of these 10
Unified CM settings
1. Certificate Information 3. IP Address or dhcp 7. NTP server 1
(Organisation, Unit, 4. IP Mask or dhcp 8. Primary DNS
Location, State, Country)
5. Gateway Address or dhcp 9. SMTP server or none
2. Hostname
6. NIC speed auto 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
Upgrade and Migration Strategy for
Cisco Unified Communications
Manager 4.1, 4.2, or 4.3 to 7.1
Upgrade Primer for Cisco Unified
Installation Options and Recommendations
 Upgrading from Windows to appliance hostname and IP address
change
Unified CM 7.1 installed IP address override DMA file old
IP address
If issue occurs, try to upgrade with same IP address then change IP after upgrade is
done
Unified CM 7.1 installed hostname override DMA file
old hostname
If issue occurs, try in CLI: set network hostname (new Publisher hostname)
Changing IP address or hostname of appliances:

http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/install/7_1_2/ipchange/ipchg712.html
Overview of Unified CM 4.1, 4.2, or 4.3
Data Migration
Existing Unified Existing Unified Existing Unified New Unified New Unified New Unified
CM 4.X Cluster CM 4.X Cluster CM 4.X Cluster CM 7.1 Cluster CM 7.1 Cluster CM 7.1 Cluster
Back Up Install Install, Run, Install Upload Upload

With BARS and Run and Download Unified DMA File Licenses
Upgrade DMA from CM 7.1
Utility on All Publisher
Servers
Latest Upgrade
Utility From CCO Data Migration
Assistant (DMA) 7.1
Tape or Save DMA File to Unified Tape, FTP or Node, DLU and 7.1
Network Download From Tape or Network CM 7.X sFTP Server Feature SW License
Share CCO Share DVD Kit
1 2 3 4 5 6
Step 2 and 3 ©Should

BRKUCC-2011 Be itsDone
2012 Cisco and/or During
affiliates. All Non-Production
rights reserved. Cisco Public Hours Due to Load on Servers 95
Upgrade Utility, DMA and Unified CM 7.1
Upgrade Process
 Finish each process before going to
the next in the order of:
Upgrade Utility (UU) formerly named
Unified Upgrade Assistant (UA)
CM 7.X
Data Migration Assistant (DMA)
DMA Install and Import DMA file into new Unified
CM 7.X installation
 Each process are independent

Upgrade Utility
A successful upgrade utility check does not
guarantee DMA will
be successful
A successful and completed DMA run does
not guarantee Unified CM 7.1
will install successfully
Cisco Public 96
Upgrade Utility (UU)
 Install on Unified CM 4.1, 4.2 or 4.3
 Download from CCO and install on every Unified
CM servers in the cluster
SQL
Publisher Voice and Unified Communications > Cisco Unified
Communications Manager Version 4.X > Unified
Communications Manager/CallManager Upgrade Assistant
SQL  Use console or VNC to install and run; do not use

TFTP remote desktop client or ILO
Upgrade
Utility  Run during off hours and one server at a time, to
SQL
validate and check the health of all of the servers
Subscriber for upgrade to Unified CM 7.1; choose version
upgrade to when run
 Upgrade utility generates summary reports of
SQL
Subscriber errors and suggested corrective actions
 Keep fixing the issues until validation is successful
Data Migration Assistant (DMA)
 Install on Unified CM 4.1, 4.2 or 4.3
 Download from CCO and install on only
SQL Unified CM Publisher in the cluster; requires
Existing a reboot
Publisher Fix
issue Voice and Unified Communications > Cisco Unified
Communications Manager Version 7.0 > Unified
1. Export success Communications Manager Data Migration Assistant
and validation
DMA success but with  Use console or VNC to install and run, do not
warnings
use remote desktop client
2. Export success
and validation  Run during off hours to validate, fix and
failure export a backup of the Unified CM 4.X
3. Export failure information by creating a DMA tar file and
DMA tar file 4. Export success a configuration file*
and and validation
configuration success  New: Pre-DMA Export Tasks—detect
file and check
DMA Considerations
 DMA does not export:
Custom MOH files—save and reapply
Background pictures—save and reapply
Bulk Administration Tool Templates
Passwords and PINs—Users impact
 Install CAR on 4.x prior to upgrading to ensure that ART database is migrated to
Unified CM 7.1 CAR.
DMA: Custom Options – Time for ART DB to CAR migration
DMA will only migrate ART DB base on Configure Automatic Database Purge
Unified CM 7.1 will truncate CAR to 180 days after upgrade
Purge CAR data to minimise DMA file and Unified CM 7.1 install time
DMA tar file is limited to 2GB
 DMA: Pre-DMA Export Tasks will copy Attendant Console and CAPF files from
Subscribers to Publisher
Building the First Node of Unified CM 7.1
 Use DMA configuration file on USB
drive if no hostname or IP address
change during
New first New first the upgrade
node of node of
USB Drive
Unified CM  FTP or sFTP can be used to upload
Unified CM
7.1 server 7.1 server DMA tar file
Copy Plug in  Common issues with FTP with large
DMA USB port Upload files with Unified CM
config. of server DMA file 3Com FTP Daemon
file FreeFTP
<?xml version="1.0" encoding="UTF-8" ?>
- <PlatformData>
<Version>main/2</Version>
- <ProductDeployment>
Microsoft FTP on Microsoft Windows XP
<ParamNameText>Product Deployment</ParamNameText>
<ParamDefaultValue>callmanager</ParamDefaultValue>
<ParamValue>callmanager</ParamValue>
MS Windows FTP on Microsoft Windows
2000/2003
Use Tape, FTP or  No issues found with the following
DMA config file DMAconfig
(plattformConfig.xml) sFTP server tool for sFTP for small files
file for
unattended FreeFTP sFTP server on Microsoft Windows
1 3 XP, or Microsoft Windows 2000/2003 running
installation as an application
2 http://freeftpd.com/?ctt=download
Secure FTP Server Recommendations
 Any SFTP servers are supported
 Recommends SFTP products that have been certified with Cisco
through the Cisco Technology Developer Partner program (CTDP),
such as GlobalSCAPE
 Internally Cisco uses the following servers but you must contact the
vendor for support:
1. Open SSH (refer to http://sshwindows.sourceforge.net/)
2. Cygwin (refer to http://www.cygwin.com/)
3. Titan (refer to http://www.titanftp.com/)
4. Core ftp (refer to http://www.coreftp.com)
Partner Central > Find a Partner:

http://www.cisco.com/pcgi-bin/ctdp/Search.pl
Upgrade for Cisco Unified
Version 4.0, 4.1, and 4.2 to Version
7.1
Server and Cluster Upgrade/
Migration Strategy
 SW check: Unified CM 4.1(3), 4.2(3) or 4.3(2)
 HW check: server hardware requirements for 7.1 are
significantly different than 4.X; hardware check
is required
Cisco Unified Communications Manager Server Support Matrix
http://www.cisco.com/en/US/partner/prod/collateral/voicesw/ps679
0/ps5748/ps378/prod_brochure0900aecd8062a4f9.html
Recommended cluster migration strategy in preferred order
New server—migration
New server—flash cut
In-place server—hybrid migration
Cisco Unified Communications Manager Software Compatibility Matrix :
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html#wp141921
New Server—Migration  Build new Unified CM cluster
 Build intercluster trunk between
Unified the existing and
Contact
Centre new cluster
Express
Voice GW
Unity
Voice GW  Leverage CSS/partitions
to route calls to the appropriate
devices
(phones, applications, etc.)
Unified CM  Pay attention to UC applications
Unified CM
4.X Cluster
7.1 Cluster that cannot support multiple
Inter-Cluster clusters
Trunk
like CUCCX
 Break UC application
dependencies from Unified CM
Contact
compatibility
Centre Agent Enterprise Minimise upgrade duration
IP Phones Users IP Migrate as the organisation needs it
Phones Migrate applications that are not cluster-
aware at the desired pace
Leveraging Forward Unregister in
4.2 or Later for Migration Strategy
 Leverage forward unregister
Unified
Contact feature in 4.2 and later
Centre Unity
Voice GW Express Voice GW  BAT forward unregistered field or
all phones in the older cluster
with wild card to match extension
range (extension 1000 = XXXX)
Unified CM
4.X Cluster Unified CM  Move phones as needed from
7.1 Cluster
Inter-Cluster old cluster to new Unified CM 7.1
Trunk cluster
 All inbound calls should search
the old cluster first and then if
register than is forwarded to new
Contact
Centre Agent Enterprise cluster
IP Phones Users IP
Phones  Unity should be integrated to the
new cluster to catch last
forwarded extension
New Server—Flash Cut—
New IP Addresses 4 1. Shut down the new
Unified CM 7.1 cluster
TFTP server/service
Existing Unified CM Unity 2. Change first TFTP
4.X Cluster address back to the
first cluster
Revert 3. Reset phones via
Unified Unified CM
MeetingPlace administrator page or
Express network ports
New Unified CM 4. Take care of GWs and
7.1 Cluster applications
as needed
3 To ensure that phones

re-home properly: to a
1 cluster: (new or old)
1. Use DMA file to build new Unified CM 7.1
2 1. Reset (not restart)
Publisher using new IP address (optional new phones via the old
hostname) 1. Change first TFTP address to the new cluster admin
cluster TFTP server page
2. Add new Subscribers with new IP addresses that 2. Cold boot phone
points to the new Publisher 2. Reset phones, GWs and change
with switch port
applications as needed to re-home to disable/enable
3. Upload the Node, Device and SW feature license TFTP server/new cluster
file to new cluster and start services
New Server—Flash Cut—
Same IP Addresses
Existing Unified CM Unity
4.X Cluster
3 Revert
1. Gracefully shutdown
Unified the new Unified CM 7.1
MeetingPlace cluster.
Express 2. Gracefully bring up the
New Unified CM old Unified CM 4.X
cluster
7.1 Cluster
3. Reset phones via
network ports
4. Take care of GWs and
applications
1 as needed
22
1. Gracefully shutdown the new Unified
CM 7.1 cluster.
1. Use DMA file to build new Unified CM 7.1 cluster
using same IP addresses in isolated VLAN 2. Gracefully shutdown the old Unified
CM 4.X cluster
2. Upload the Node, Device and SW feature license
file to new cluster and start services 3. Change isolate VLAN to production
network and bring up new Unified CM
BRKUCC-2011
7.1 cluster
© 2012 Cisco and/or its affiliates. All rights reserved.
(ARP)
Cisco Public 107
In-Place Server—Hybrid Migration
 Use spare capacity servers in existing Unified CM
Primary
clusters to convert to Unified CM 7.1 servers
Secondary/  Upgrade as many backup subscribers to Unified CM
Backup 7.1 as possible to support the phones, GWs, etc. in
2,500 IP Phones the order shown
(5,000 Device Units)
1. Unified CM 7.1 Pub
Cisco MCS 7835 2. Unified CM 7.1 TFTP
Publisher and 3. Unified CM 7.1 subscribers
TFTP Server (Not
Req. < 1,000)  7x24 organisations need to be supported on Unified
CM 4.X and Unified CM 6.1 servers for fast switch
Primary over
1 to 2,500
 Try to retain as many Unified CM 4.X servers in case
Backup
downgrade is needed
 Save Unified CM 4.X Pub as last
upgraded server
Migration Considerations for Unified CM
7.1—Appendix A
 External Unified Communications applications
 Unsupported SW and HW
 Co-resident Cisco Unified Communications and network
applications
 Third-party Unified Communications applications and endpoint
dependencies
 Infrastructure dependencies
 Management interface changes
 Unified CM 4.X OS to Unified CM 7.1-related application
 Pre-/post-installation tasks
Q&A
Complete Your Online Session
Evaluation
Complete your session evaluation:
 Directly from your mobile device by visiting
www.ciscoliveaustralia.com/mobile and login
by entering your username and password
 Visit one of the Cisco Live internet

stations located throughout the venue
 Open a browser on your own computer

to access the Cisco Live onsite portal Don’t forget to activate your Cisco Live
Virtual account for access to all session
materials, communities, and on-demand and
live activities throughout the year. Activate your
account at any internet station or visit
www.ciscolivevirtual.com.

BRKUCC-2011 Best Practices For Migrating Previous Versions of Cisco Unified Communications Manager (CUCM) To CUCM 8.6

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

BRKUCC-2011 Best Practices For Migrating Previous Versions of Cisco Unified Communications Manager (CUCM) To CUCM 8.6

Caricato da

Copyright:

Formati disponibili

Best Practices for

Upgrade and Upgrade

Major Releases 5.0, 6.0, 7.0 8.0

Minor Releases 5.1, 6.1, 7.1 8.5, 8.6

 Version 8.X is the only version with 8.6 minor release

W1 W1 Upgrade: Windows to Appliance model

L2 L2 Upgrade: Appliance to Appliance model

RU RU (Refresh Upgrade): Appliance to Appliance

W1 W1 Upgrade: Windows to Appliance model

 High complexity with possible longest downtime

L2 L2 Upgrade: Appliance to Appliance model

 Low complexity with possible shortest downtime

RU RU (Refresh Upgrade): Appliance to Appliance

 Medium complexity with possible longer downtime

Existing Existing Existing New Unified New Unified New Unified

RedHat RHEL 3 RHEL 4 RHEL 5

CUCM Version 5.0, 6.0 7.X, 8.0, 8.5 8.6

 Active partition is running while upgrade software is being

Active Partition Running InActive partition Dormant

InActive partition Dormant

 Publisher (1st Node)  MCS7825H3 –needs 16Gb

 Seen with 8.6(2a)

Unified CM 7.1(5)SU4 RU Unified CM 8.6(1a)

Unified CM 7.1(5)SU4 RU Unified CM 8.6(2a)

Latest SU updates of 7.1(5) SU4 are not supported

 Upgrade from 4.X to 7.1(5b) – without SU

 For end of support and appliance versions of Unified CM

Unified CM 3.3(5) UPGRADE

 Minimise major upgrade step(s)

 Various paths & same number of steps to get to target version

 Engineering special does not have any impact on direct or

Engineering Special (ES) and Windows SR Upgrade Note:

Based on the Number of Unified CM

Based on the Number of IP Phones and the Types of

Upgrade Required for Major Version

Based on the Number of Cisco will Send in

Based on the Number and Cisco will Send in

Based on the Number Cisco will send in

Major Version Upgrade

Based on the Cisco will send in

 License MAC is 12 digit HEX value based on the hash of these 10

1. Certificate Information 3. IP Address or dhcp 7. NTP server 1

Cisco Unified Communications Answer File Generator for License MAC:

Show > Status Show > Network

If you change one of

Cisco Unified Communications Answer File Generator for License MAC:

2 In-Place Server Upgrade/Migration

Unified CM Unified CM 8.6

In-Place Server—Hybrid Migration

New Server—Flash Cut

2 Existing TFTP  Switching versions should be done as soon as upgrade of all

BRKUCC-2011 For Existing Servers That Can Run Unified CM 7.X

2 Existing TFTP  Can use new IP addresses in new cluster

*Make sure existing 4.X active sub is off

2 Existing TFTP  Option 1: Same IP addresses and switch host/ports

4 Existing Active  Recommended for medium to large network especially where

Cisco Unified Communications Manager Software Compatibility Matrix:

IP Phone UC Applications Unified CM

 May repeat phase I,II or III in a multi-step upgrade

Cisco IP Phone Firmware by Unified CM Releases:

 PPID (P2P Image Distribution)  Temp change to TFTP service

 3,000 for dual processors dedicated

CM 8.6(2) 7.0(3) 8.5(2)