Brkucc 2011

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

to CUCM 8.6
BRKUCC-2011
Follow us on Twitter for real time updates of the event:
@ciscoliveeurope, #CLEUR
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 dont forget to visit Cisco Live Virtual:
www.ciscolivevirtual.com
Follow us on Twitter for real time updates of the event:
@ciscoliveeurope, #CLEUR
BRKUCC-2011
2012 Cisco and/or its affiliates. All rights reserved.
Cisco Public
Agenda
Session Objectives and Scope
Cisco Unified Communications Manager 8.6 Upgrade Definition
and Upgrade Path
Cisco Unified Communications Manager 8.X Licenses

Servers, Clusters, and UC Application Upgrade/
Migration Definition
Cisco Unified Communications Manager 7.1 and 8.6 Installation
Process and Best Practices
Upgrade and Migration Strategy for Cisco Unified Communications
Manager 6.1, 7.1, 8.0 and 8.5 to 8.6
Platform Conversion from MCS to UC on UCS
Q&A
BRKUCC-2011
Cisco Public
1
Session Objectives and Scope
Session Objectives
Planning for a successful upgrade or migration
to Unified CM 8.6
To understand some of the considerations and
approaches for migrating from Unified CM 4.X, 5.1, 6.1,
7.1, 8.0 and 8.5 to Unified CM 8.6
To provide some best practice guidelines for Unified CM
7.1 and 8.6 installation
To provide some best practice guidelines for platform
conversion from MCS to UC on UCS
BRKUCC-2011
Cisco Public
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 8.X on UCS
BRKUCC-2011
Cisco Public
Session Scope
Covers appliance (6.1, 7.1
and 8.X) version of
Unified CM to upgrade to
8.6(2a)
Unified CM 6.1(X)
Unified CM 7.1(X)
Unified CM 8.0(X)
Unified CM 8.6(2a)
Platform conversion from

MCS to UC on UCS
Unified CM 8.5(X)
Unified CM 8.6(1)
B440 M2
Platform Conversion
B230 M2
B200 M2
C250 M2
MCS Servers
HP or IBM Servers
C260 M2
C460 M2
C210 M2
C200 M2
More BRKUCC-2011
Detailed Unified CM
Version that can be upgrade
to 8.6(X) in Compatibility Matrix below7
Cisco Public
2
Cisco Unified Communications
Manager 8.6 Upgrade Definition
and Upgrade Path
Release Numbering Change with 8.X and Higher

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
New minor version Unified CM 8.5 and 8.6
Introduced to align with system release numbering

Version 8.X is the only version with 8.6 minor release
BRKUCC-2011
Cisco Public
Unified CM Major/Minor
Upgrade Definition
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 model

-Medium complexity with possible longer downtime
-From Unified CM versions 6.X, 7.X, 8.0 or 8.5 to 8.6
BRKUCC-2011
Cisco Public
10
W1 Upgrade: Windows to Appliance model
Existing
Unified CM
4.X Cluster
Existing
Unified CM
4.X Cluster
Install
and Run
Upgrade
Utility on All
Servers
Back Up
With
BARS
Tape or
Network
Share
BRKUCC-2011
Existing
Unified CM
4.X Cluster
Install,
Run, and
Download
DMA from
Publisher
New
Unified CM
7.1 Cluster
Install
Unified
CM 7.1
New
Unified CM
7.1 Cluster
Data Migration
Assistant (DMA)
7.1
Download
From CCO
Save DMA File

to Tape or
Network Share
Unified
CM 7.X
DVD Kit
Tape, FTP
or sFTP
Server
Details of W1 Upgrade is in Appendix A
Cisco Public
Upload
Licenses
Upload
DMA
File
Latest
Upgrade
Utility From
CCO
New
Unified CM
7.1 Cluster
Node, DLU and

7.1 Feature SW
License
11
L2 and RU Upgrade: Appliance to Appliance model

Updated
Unified CM
SW
Unified CM
Publisher
Unified CM
Publisher
Active Partition
InActive partition
Active Partition
inActive Partition
InActive partition
Active partition
Switch
Version via
OS Admin
or CLI
Unified CM
Subscriber
BRKUCC-2011
inActive Partition
Active partition
Unified CM
Subscriber
Cisco Public
12
L2 and RU Upgrade: Appliance to Appliance model

Is the existing
Unified CM
appliance version
CM 8.6?
Existing Unified
CM appliance
being upgraded
to Unified CM
8.6
YES
Perform a L2
Upgrade
NO
Perform a RU
Upgrade
Upgraded
Unified CM
8.6
Existing Unified CM and RHEL versions

RHEL 3: Unified CM 5.X and Unified CM 6.X
RHEL 4: Unified CM 7.X, Unified CM 8.0 and Unified CM 8.5

RHEL 5: Unified CM 8.6
Upgrade between RHEL 3 and RHEL 4 will be L2

Upgrade between from RHEL 3 or RHEL 4 to RHEL 5
will be RU
Future upgrades between RHEL versions will be RU
BRKUCC-2011
Cisco Public
13
L2 Upgrade: Appliance to Appliance model with Unified

CM 8.6
Active Partition
InActive partition
Running
1.RPMs
installation
2.Unified CM
installation
3.DB
installation
4.Data
Migration
InActive partition
Reboot
Dormant
Active Partition
1. Firmware and
BIOS upgrade
2.Post reboot
software
installation
Active partition is running while upgrade software is being

installed on inactive partition
Low downtime since upgrade can be done while system

is functioning
BRKUCC-2011
Cisco Public
14
Refresh Upgrade (RU): Appliance to Appliance model

with Unified CM 8.6
Active Partition
InActive partition
InActive partition
Running
1. Data
exported
(Unified CM
and CAR) into
/common
partition
InActive partition
Reboot
Active Partition
Dormant
1. Firmware
and BIOS
upgrade
2.VOS
installation
3. Platform
import
Reboot
Dormant
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 installed
More reboots
Higher downtime since upgrade

cannot be done while system is
functioning
Upgrade is equal to fresh
installation of Unified CM
BRKUCC-2011
Cisco Public
15
Refresh Upgrade (RU) Notes

To minimize downtime, upgrade Publisher or first node while
Subscribers or secondary nodes perform call processing
No administrative tasks can be done
No user facing features will be retained after switching to new updated
Unified CM version
MCS7825H3 and MCS7828H3 will require external USB device to

export data (16GB to 128GB)
MCS7825H3 and MCS7828H3 will be a new installation with software
RAID so cannot be easily be reverted to older version
Track console of server to see progress of the installation

Must Install Refresh Upgrade COP file before upgrading to 8.6
(ciscocm.refresh_upgrade_v1.1.cop.sgn)
BRKUCC-2011
Cisco Public
16
One-Step Minor Upgrades (Appliance)

Unified CM 6.1(4)
EOS
Unified CM 6.1(4a/b)
Unified CM 6.1(5)
Unified CM 7.1(3)
RU
Unified CM 7.1(5)
Unified CM 8.6(2a)
Unified CM 8.0(X)
EOS
Unified CM 8.5(X)
Unified CM 8.6(1)
Announced
CSCto45041
Stay updated to avoid multiple steps upgrade. I.E.

6.1(3) or 7.1(2)
More
Detailed Unified
CM Versions that can be upgraded
to 8.6(1) in Compatibility Matrix
BRKUCC-2011
Cisco Public
17
Unsupported Upgrade to Version 8.6(1a)
Unified CM 7.1(5b)SU4
RU
Unified CM 8.6(1a)
Unified CM 7.1(5b)SU4
RU
Unified CM 8.6(2a)
Latest SU updates of 7.1(5b) SU4 can not be upgraded to version

8.6(1a)
More
Detailed Unified
CM Versions that can be upgraded
to 8.6(1) in Compatibility Matrix
BRKUCC-2011
Cisco Public
18
Two-Step Major/
Minor Upgrades (Windows)
EOS
Unified CM 4.1(3)
Unified CM 4.2(3)
W1
RU
Unified CM 7.1(5b)
Unified CM 8.6(2a)
Unified CM 4.3(2)
To minimize down time, this one-step upgrade from 4.X to the later version of
7.1(5b) might be one of the several upgrade phases
Supported upgrade is to specific version of 7.1(5b) which might require Service
Updates (SU4) before running in production
4.X -> 7.1(5b) - > 7.1(5b) SU4

Might consider staying with the later 7.1(5b) to align all other collaboration
applications before going to 8.6(2a)
BRKUCC-2011
End of 2012
Sales
Notices for Unified CM
4.X is in the notes section
Cisco Public
Cisco and/or its affiliates. All rights reserved.
19
Two-Step Minor Upgrades (Appliance)
EOS
L2
Unified CM 5.1(3)
RU
Unified CM 7.1(5b)
SU4
Unified CM 7.0(2)
Unified CM 8.6(2a)
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)
Can upgrade directly to an SU
BRKUCC-2011
Endof
Sales Notices for Unified Cisco
CMPublicis in the notes section
20
Three-Step Major/Minor
Upgrades (Windows)
EOS
Unified CM 3.3(5)
EOS
MAJOR
UPGRADE
W1
Unified CM 4.3(2)
RU
Unified CM 7.1(5b)
Unified CM 8.6(2a)
Unified CM 4.0(2a)
EOS
EOS
MINOR
UPGRADE
Unified CM 3.3(5)
Unified CM 4.1(3)
W1
RU
Unified CM 7.1(5b)
Unified CM 4.0(2a)
Unified CM 8.6(2a)
Unified CM 4.2(3)
For end of support and Windows version of Unified CM

Minimize major upgrade step(s)
Focus on the two key versions that can be upgraded to 7.1(5b) before going
to 8.6(2a)
MAJOR
Windows 2000 to Windows 2003
UPGRADE
4.1(3) and 4.2(3)
MINOR
UPGRADE
Windows 2000 to Windows 2000
End of Sales
Notices for Unified CM 3.XCisco
and
4.X are in the notes section
Public
BRKUCC-2011
21
Multi-step Minor
Upgrades (Appliance)
3-steps
4-steps
EOS
EOS
RU
Unified CM 6.1(1)
Unified CM 8.6(2a)
RU
Unified CM 6.0(1)
Unified CM 8.6(2a)
Various paths to get to target version with same number of upgrade steps
Minimize number of major version changes to minimize impact to users

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)
BRKUCC-2011
More 2012
complete
list of other versions
are in the notes section
Cisco Public
Cisco and/or its affiliates. All rights reserved.
22
Upgrades for Engineering

Special (Appliance)
EOS
Unified CM 6.X ES
RU
Unified CM 8.6(2a)
EOS
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
BRKUCC-2011
Cisco Public
23
Sample Unified CM 7 and 8 Versions and Builds

Unified CM 8.6(2a)
Unified CM 8.6(1a)
Unified CM 8.5(1)
SU3
Unified CM 8.5(1)
SU2
Unified CM 8.5(1)
SU1
Unified CM 8.5(1)
8.6.2.20000-2
8.6.1.20000-1
8.5.1.13900-5
Unified CM 7.1(5b)
SU4
Unified CM 7.1(5b)
SU3
Unified CM 7.1(5b)
SU2
7.1.5.33900-10
(A) Major version
7.1.5.32900-2
7.1.5.31900-3
7.1.5.30000-1
8.5.1.11900-7
Unified CM 7.1(5a)
7.1.5.20000-6
8.5.1.10000-26
Unified CM 7.1(5)
SU1a
8.0.3.23900-5
Unified CM 7.1(5)
Unified CM 8.0(3a)
8.0.3.20000-2
Unified CM 7.1(3b)
SU2
Unified CM 7.1(3b)
SU1
8.0.2.40000-1
8.6.2.20000-2
(X) FCS / Respin
8.6.2.10000-2
7.1.5.11901-1
8.6.2.20000-2
(Y) ES/SU Releases
Unified CM 8.0(3a)
SU3
Unified CM 8.0(2c)
8.6.2.20000-2
(C) Maint. rel.
Unified CM 7.1(5b)
8.0.2.41900-3
8.6.2.20000-2
(B) Minor version
8.5.1.12900-7
Unified CM 8.0(2c)
SU1
Numbering
Convention
(A.B.C.XYzzz-x)
Unified CM 7.1(3b)
7.1.5.10000-12
7.1.3.32900-4
8.6.2.21zzz-1
8.6.2.22900-1
(ZZZ) FCS, ES, SU
7.1.3.31900-1
7.1.3.30000-1
8.6.2.20000-2
8.6.2.21001-1
8.6.2.22900-1
BRKUCC-2011
Cisco Public
24
3
Manager 8.X Licenses
Unified CM 8.X License TypesNode, Device Unit and

SW Feature License
Based on the Number of Unified
CM Servers in the Cluster
Unified CM
Servers in
Cluster
Based on the Number of IP Phones and the
Types of Phones in the Cluster Including Video
Terminals, ATA GW, and Mobility Feature
IP Phones
in Cluster
Upgrade
(final
Unified CM version)
4.x, 5.X, 6.X or 7.X
Required for Major Version

Upgrade
Unified CM
8.X
Node
License
Device Unit
License
SW
Feature
License
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 address or LicenseCiscoMAC
of the First Node of Unified CM Cluster
Public
26
Unified CM 8.X New Installation

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

in Email
Cisco will Send

in Email
Node
License
Device Unit
License
http://www.cisco.com/go/license
UCL is introduced with Unified CM version 7.1(5) or later and 8.0(1) or later
License BRKUCC-2011
File is based on the
MAC address or LicenseCiscoMAC
of the First Node of Unified CM Cluster
Public
27
Unified CM 7.1 Upgrade

Migration Process *
Unified CM
7.1
Cluster
Unified CM
4.X Cluster
Unified CM
Upgrade
Order
Based on the
Number servers
in the cluster
Product
Activation
Key (PAK)
Cisco will send

in Email
Temporary Node
and Device Unit
License
SW Feature
License
Cisco CallManager Device Upgrade License
Temporary
Node and
Device Unit
License
* DMA 7.1 will generate temporary Node and DLU

license locally on old publisher
Permanent
Node and
Device Unit
License
Unified CM Licensing:
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/admin/8_5_1/ccmfeat/fslicense.html
BRKUCC-2011
Cisco Public
28
Unified CM 8.X Upgrade

Major Version Upgrade
Unified CM
8.X
Cluster
Unified CM 5.X,
6.X or 7.X Cluster
Unified CM
Upgrade
Order
Based on the
Number servers
in the cluster
Cisco will send

in Email
Product
Activation
Key (PAK)
Permanent Node
and Device Unit
License
SW Feature
License
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
BRKUCC-2011
Cisco Public
29
DLU and UCL Licensing Migration

Unified CM 7.1(4)
and earlier
Device License
Unit (DLU)
Unified CM 7.1(5)
and later
Unified CM 8.X
User Connect
License (UCL)
Upgrade to beyond 7.1(4) changes the licensing model from DLU to UCL
License enforcement is still DLU

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
BRKUCC-2011
Cisco Public
30
License MAC for UC on UCS

Show > Status
Impacts the following scenarios:

Migration of CUCM on UCS
Cisco Unified OS Administration

Show > Status or Show > Network
CLI: show status (details shown in notes

section below)
Show > Network
Started with Unified 7.1(3) (build

7.1.2.39000-149 and greater), 8.0(1)
and greater
Cisco Does not Provide Any Support for a VMware Deployment
for Customer/Partner Production or Lab Use for Versions Prior to
8.0. Production Support for VMware Installations of Cisco Unified
Communications Manager on Version 8.0 Are Limited to
Installations to Cisco Unified Computing System (UCS)
Hardware Only.
BRKUCC-2011
Cisco Public
31
4
Servers, Clusters, and UC Application
Upgrade/Migration Definition
Server Upgrade/Migration Definition
Existing
Unified CM
Servers in
Cluster
New Server Upgrade
Unified CM
4.X/5.X/6.X/7.X/8.0/8.5
In-Place Server Upgrade/Migration
Unified CM
4.X/5.X/6.X/7.X/8.0/8.5
BRKUCC-2011
Unified CM 8.6
Upgraded
Unified CM
Servers in
Cluster
Unified CM 8.6
Cisco Public
33
Cluster Upgrade/Migration Definition
1
2
3
4
In-Place ServerFlash Cut

New Unified
CM Cluster
Existing Unified
CM Cluster
In-Place ServerHybrid Migration

New Unified
CM Cluster
Existing Unified
CM Cluster
New ServerFlash Cut
Existing Unified
CM Cluster
New Unified
CM Cluster
New ServerMigration
New Unified
CM Cluster
Existing Unified
CM Cluster
BRKUCC-2011
Cisco Public
34

Appliance to Appliance
1
2
3
4
Existing Upgrade servers in the order shown

Publisher Upgrade should be done after hours if possible
Complete all server upgrades before switching versions
Existing
TFTP
Switching versions should be done as soon as upgrade

of all servers is completed to avoid loss of MAC
This approach is recommended for appliance to
appliance upgrade
New
Publisher
New
TFTP
Existing
Backup
Subscriber
New
Backup
Subscriber
Existing
Active
Subscriber
New
Active
Subscriber
BRKUCC-2011
For Existing Servers That Can Run Unified CM 8.X

Cisco Public
35
In-Place ServerHybrid Migration

Windows to Appliance
1
2
3
4
Existing
Backup
Subscriber
Existing
TFTP
Existing
Active
Subscriber
Existing
Publisher
Existing backup subscriber is not the call processing

server
Be careful about duplicate IP addresses
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 *Make sure existing 4.X active sub is off
New backup subscriber is online for redundancy
New
Publisher
TFTP
New Active
Subscriber
New
Backup
Subscriber
Save the Existing Publisher for last in case of downgrade

Once upgrade is deemed acceptable
New
TFTP
Change DHCP option 150 back to new TFTP server

Revise activated services as required
BRKUCC-2011
Cisco Public
36
New ServerFlash Cut

Windows to Appliance or Appliance to Appliance
1
2
3
4
Existing Build servers in the order shown

Publisher New cluster can use the same IP address or new IP
addresses; potential ACL impact
Existing
TFTP
Existing
Backup
Subscriber
Option 1: Same IP addresses and switch host/ports

Option 2: New IP addresses and change DHCP
option 150
Recommended for small to medium network without

other complex UC applications
Existing
Active
Subscriber
BRKUCC-2011
New
Publisher
New
TFTP
New
Backup
Subscriber
New
Active
Subscriber
Cisco Public
37
New ServerMigration
Windows to Appliance or Appliance to Appliance
1
2
3
4
Existing
Publisher
Existing
TFTP
Build servers in the order shown

New cluster uses a new set of IP addresses; potential
ACL impact
Use CSS and partitions to ensure call routing is correct
New
Publisher
New
TFTP
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
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
BRKUCC-2011
Cisco Public
38
UC Application Upgrade/
Migration Definition
Upgrade Time Increases with Various Dependencies
UC Applications
Migration Strategy
Pre-Upgrade Migration *
CER
CUCCX
CUCCE
CUP
UC Applications
Upgrade
Unified CM
Upgrade
Down Time
MP
MPE
Unity
Connection
Unity
* Some UC Application Requires a Complete

Reinstall for Upgrade
Down Time
Post Upgrade Migration *
Unified CM
Upgrade
UC Applications
Upgrade
Down Time
Cisco Unified Communications Manager Software Compatibility Matrix:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html
BRKUCC-2011
Cisco Public
39
Overall Upgrade Strategy for One-step Upgrade to

Minimizing Down Time
Phase I:
Phase II:
Phase III:
IP Phone
UC Applications PreUpgrade Migration
Unified CM and UC
Applications Post
Upgrade Migration
Firmware Upgrade
IP Phone
Firmware
UC Applications
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
Unified CM
Upgrade
UC Applications
Upgrade
Cisco IP Phone Firmware by Unified CM Releases:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html
BRKUCC-2011
Cisco Public
40
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)
- Temporarily increase to 1,500 for single processor dedicated TFTP server and 3,000
for dual processors dedicated TFTP server
- More detail information and testing experience in notes section
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
BRKUCC-2011
Cisco Public
41
Phase I:
Phone
Upgrade Caveat
Latest phone firmware on Windows version is older than the default
phone firmware on the target Unified CM version
- Phase I and Phase II can be combine into one downtime or another fw
upgrade step
Unified CM 8.6(2) default phone firmware is 9.2(1)

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:

http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/firmware/8_5_2/english/release/notes/7900_852SR1.html
BRKUCC-2011
Cisco Public
42
Phase III: Unified CM

Upgrade Consideration
Clustering over the WAN (COW) can increase
time for installation, upgrade and database (DB)
replication by 40%50%
Round Trip Delay most impact
Firewall between Unified

CM servers
After upgrade, check for the following using CLI,
RTMT and Unified Reporting (details in
notes section)
Connectivity
DB replication state
Unified CM SRND:
www.cisco.com/go/ucsrnd
BRKUCC-2011
Cisco Public
43
5
Manager 7.1 and 8.6 Installation
Process and Best Practices
Overview of Unified CM 7.1 Installation

MCS-781X
MCS7825
MCS7828
MCS7835
MCS7845
Unified CM
7.1 DVD KIT
INSTALLATION PROCESS (PROCEED)

2
BRKUCC-2011
Basic Install
Apply SR, ES or SU
Upgrade During
Installation
i.e., 7.1(2) to 7.1(2a)
Import Data from Windows
Upgrade From
Windows
i.e., 4.1(3) to 7.1(2a)
Cisco Public
New Installation, New

ServerFlash Cut or
New ServerMigration
45
Overview of Unified CM 8.6 Installation

MCS-781X
MCS7825
MCS7828
MCS7835
MCS7845
Unified CM
8.6 DVD KIT
INSTALLATION PROCESS (PROCEED)

1
BRKUCC-2011
Basic Install
Apply ES or SU
Upgrade During
Installation
i.e., 8.6(1) to 8.6(2)
New Installation, New

ServerFlash Cut or
New ServerMigration
Cisco Public
46
Bridge Upgrade Feature in

Unified CM 8.0(2) and later
MINOR
UPGRADE
DRS
Unified CM 8.X
Unified CM 6.1/7.X
Secure FTP
Server
NOT supported for

production use of
Unified CM 8.X
Supported server for

production use of
Unified CM 6.1 and 7.X
2
Secure FTP
Server
DRS
Unified CM 8.X
DRS
or
Supported server for
production use of
Unified CM 8.X
Unified CM 8.X
U
C
S
Secure FTP
Server
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
BRKUCC-2011
Cisco Public
47
Installation Logs
To capture installation logs failure, a USB key is required for
physical servers
- Plug USB key into the physical server
- Accept dumping of logs
For UC on UCS, 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 http://www.7-zip.org/download.html to unzip the
tar file
- Remove serial port after a successful installation of Unified
CM 8.X
BRKUCC-2011
Cisco Public
48
Unified CM 7.1 Upgrade Installation Caveat

Upgraded Unified CM 7.1 system will have Cisco Attendant Console
(CAC) Plug-in
New Unified CM system 7.1 will not have Cisco Attendant Console
(CAC) Plug-in
- Contact TAC if migration from previous release is a new installation of
Unified CM 7.1 on new servers
- Link is not in the plug-in page, but it is there to download
Upgrade or new installation of Unified CM 8.0 or higher will not

support CAC
Migrate to Cisco Unified X Attendant Console (CUxAC) before or
during Unified CM 8.X upgrade
End-of-Sale and End-of-Life Announcement for the Cisco Unified Attendant Console:
http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps7046/ps7282/end_of_life_notice_c51-499091.html
BRKUCC-2011
Cisco Public
49
6
Upgrade and Migration Strategy for Cisco Unified
Communications Manager 6.1, 7.1, 8.0 and 8.5 to 8.6
Unified CM 6.1, 7.1, 8.0 or 8.5 to 8.6

Upgrade Options
Existing
Unified CM
6.1 or 7.1
Cluster
Unsupported
servers for
Unified CM 8.6
Bridge Upgrade
New Server - Migration
Existing
Unified CM
6.1,7.1 or 8.0
or 8.5 Cluster

Supported
servers for
Unified CM 8.6
Supported Cisco Unified Communications Manager Releases by Server

http://www.cisco.com/en/US/partner/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd8062a4f9.html
BRKUCC-2011
Cisco Public
51
Bridge Upgrade Feature Process
New
Existing
Unified CM Unified CM
6.1 or 7.1 8.6 Cluster
on old
Cluster
hardware
Upgrade
Inactive
Partition
Back Up
With DRS
Switch
Partition
Unified
CM 8.6
DVD Kit
New
New Unified
New
New
Unified
CM
CM
8.6
Unified CM
Unified CM
8.6 Cluster Cluster on 8.6 Cluster 8.6 Cluster
on new
new
on old
on new
hardware
hardware
hardware
hardware
CLI
or
OS Admin
Restore
With
DRS
Install
Unified
CM 8.X
Upload
Licenses
sFTP
Server
or Tape
Unified CM
8.6 DVD Kit
sFTP
Server
or Tape
8.X
Licenses

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/install/8_6_1/cluster/clstr861.html
BRKUCC-2011
Cisco Public
52
Unified CM 6.1 or 7.1 to 8.6

New ServerMigration
ICT
Existing
Unified CM
6.1 or 7.1
Cluster
Back Up
With DRS
New
Unified CM
8.6 Cluster
Upload
Licenses
sFTP
Server
or Tape
Feature SW
License
New
Unified CM
8.6 Cluster
New
Unified CM
8.6 Cluster
CLI
or
OS Admin
New
Unified CM
6.1 or 7.1
Cluster
Install
Unified
CM
Restore
With
DRS and
license
files
Upgrade
Inactive
Partition
Switch
Partition
New
Unified CM
6.1 or 7.1
Cluster
Unified
CM 8.6
DVD Kit
sFTP
Server
or Tape
Unified CM
6.1 or 7.1
DVD Kit
For existing servers that cannot run Unified CM 8.6 in medium to large size network53
BRKUCC-2011
Cisco Public
Unified CM 6.1, 7.1, 8.0 or 8.5 to 8.6 Upgrade In-Place

ServerFlash Cut
Existing
Existing
Unified CM
Unified CM
6.1, 7.1, 8.0 6.1, 7.1, 8.0
or 8.5 Cluster or 8.5 Cluster
Upgrade
Publisher
Inactive
Partition
Back Up
With DRS
sFTP
Server
or Tape
BRKUCC-2011
Unified
CM 8.6
DVD Kit
Existing
Unified CM
6.1, 7.1, 8.0
or 8.5 Cluster
New Unified
CM 8.6
Cluster
Switch
Partition
on
Publisher
Upgrade
Subscribers
Inactive
Partition
Unified
CM 8.6
DVD Kit
New Unified
CM 8.6
Cluster
Switch
Partition
on
Subscriber
Upload
8.X SW
Feature
License
CLI
or
OS Admin
CLI
or
OS Admin
Feature SW
License for 6.1
and 7.1
Upgrade*
For Existing Servers That Can Run Unified CM 8.6

New Unified
CM 8.6
Cluster
Cisco Public
54
Unified CM 8.6 Downgrade to

6.1, 7.1, 8.0 or 8.5
Unified
CM 8.6
Cluster
Switch
Partition
on
Publisher
Unified
CM 8.6
Cluster
Switch
Partition
on
Subscriber
Unified
CM, 6.1,
7.1, 8.0 or
8.5
Cluster
Reverting back to Unified CM

6.1, 7.1, 8.0 or 8.5 requires
resetting DB replication
-CLI: utils dbreplication reset all
For MCS7825H3 or
MCS7828H3, reinstall and
perform DRS restore
Utils
dbreplication
reset all
Documented in caveats
CSCsl57629 and CSCsl57655
IDS
IDS
CLI
or
OS Admin
CLI
or
OS Admin
CLI
BRKUCC-2011
CSCsl57629 and CSCsl57655
Cisco Public
55
7
Platform Conversion from MCS to UC on UCS
Platform Support
Platform Options
B200 M2
B230 M2
UC on UCS (Hardware)
B440 M2
C200 M2
C210 M2
C260 M2
C250 M2
Specs-Based (Software)
(Subset of UC applications)
C460 M2
* Server selection, sizing and design cover in later

sections
Unified Communications Virtualization:
http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization
BRKUCC-2011
Cisco Public
58
UC on UCS Tested Reference Configurations (TRC)

Defined, tested and documented
Positioned for customers fairly new to virtualization
UCS B200 M2:

1.
2.
DAS (VMware) and FC SAN (UC Applications)

FC SAN (VMware and UC Applications)
B200 M2
UCS C210 M2:

1.
2.
3.
DAS (VMware & UC Applications) *

DAS (VMware) and FC SAN (UC Applications)
FC SAN (VMware & UC Applications)
UCS C200 M2: DAS (VMware & UC Applications)
C210 M2
C200 M2
Flexibility: Higher CPU speed, more memory and different CNA
* Some TRC requires spare drives for specific implementation like CUC
Tested Reference Configurations (TRC):
http://docwiki.cisco.com/wiki/Unified_Computing_System_Hardware
BRKUCC-2011
Cisco Public
59
TRC Based Platform Decision Tree *

Start
1000 or less
user site
YES
1.
UCS C200 M2: DAS

(VMware & UC
Applications)
2.
UCS C210 M2: DAS only

(VMware & UC
Applications)
3.
UCS B200 M2:
C200M2 1
NO
Direct Attached
Storage only
YES
C210M2 2
DAS (VMware) and FC SAN

(UC Applications)
FC SAN (VMware UC &

Applications)
NO
Centralized
Management
YES
B200M2 3
4.
NO
C210M2 4
UCS C210 M2:
DAS (VMware) and FC SAN

(UC Applications)
FC SAN (VMware UC &

Applications)
* UC applications and versions that are supported in selected TRC #

Unified Communications Virtualization Supported Applications:
http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications
BRKUCC-2011
Cisco Public
60
UC on Specs-Based
UCS, HP and IBM servers that are on VMware hardware compatible
list (HCL) are supported
Cisco supports UC applications only and not performance of the
platform
Positioned for customers with extensive virtualization experience
CPU: B200 M2 and C210 CPU level or higher;
- Intel Xeon 5600 or 7500 Family CPUs only with minimum 2.53Ghz
- Intel E7 family CPUs are now supported with minimum 2.4Ghz
- Refer to Docwiki for detailed specifications
RAM: Total UC application RAM + 2GB for ESXi

Storage: DAS, FCOE, FC SAN, iSCSI, or NFS
Specification-Based Hardware Support

http://docwiki.cisco.com/wiki/Specification-Based_Hardware_Support
BRKUCC-2011
Cisco Public
61
Platform Decision Tree and Sizing

Start
UC Application
supported with
Specs-Based?
YES
Total vCPUs, RAM,

storage required per site
based on number of
locations
Select and customize

platform based on cores,
memory and I/O
Total vCPUs, RAM,

storage required per site
based on number of
locations
Select TRC platform base

on chassis and storage
NO
TRC-Based
Systems
TRC-Based supports more UC applications then

Specs-Based
Design approach for Specs-Based is to select and
customize the platform to maximize applicability
Design approach for TRC-Based is to select the
TRC # or type and the quantity of TRC platforms
Unified Communications Virtualization Supported Applications:
http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications
BRKUCC-2011
Cisco Public
62
Platform Options
Complexity
3rd-Party
Intel Xeon 5600
Intel Xeon 7500
DAS (SATA, SAS)

FC SAN (2Gbps+)
FCoE (10Gbps+)
NFS
iSCSI
B200 M2
B200 M2
B440 M2
B440 M2
Cisco
B230 M2
C200 M2
C460 M2
C210 M2
B230 M2
DAS (SATA, SAS)

FC SAN (2Gbps+)
FCoE (10Gbps+)
NFS
iSCSI
C250 M2
C200 M2
B250 M2
C260 M2
C210 M2
C260 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
BRKUCC-2011
Cisco Public
63
VMware Support
VMware Sphere Support

No ESX support. Only ESXi 4.0 or 4.1 and 5.0 supported
- VMware vSphere Hypervisor, Essential, Essential Plus,
Standard, Advance, Enterprise and Enterprise Plus (support
contract is required)
- ISO for Cisco UCS for appropriate driver support is at
http://downloads.vmware.com/d/details/esxi41_cisco_oem_i
so/ZHcqYnRkdHdiZCVodw
VMware vCenter Server

- Essential, Foundation or Standard
vCenter
Server
VMware Pricing
- https://www.vmware.com/files/pdf/vsphere_pricing.pdf
Hypervisor Support for Virtualized UC:

http://docwiki.cisco.com/wiki/Unified_Communications_VMWare_Requirements
BRKUCC-2011
Cisco Public
65
UC on UCS ESXi 4.1 Edition Decision Tree

Start
Unity
Connection
20K OVA
YES
Enterprise Plus
http://www.vmware.com/pro
ducts/vsphere/buy/editions_
comparison.htm
NO
Memory above
256GB
YES
Enterprise Plus
NO
Nexus 1000-V
or distributed
switch
YES
Enterprise Plus
NO
More than 6
cores per CPU
NO
Storage
vMotion
BRKUCC-2011
NO
Compare vSphere
Editions:
YES
Advance
http://blogs.vmware.com/vsphere
/2010/07/introducing-vmwaresphere-hypervisor-41-the-freeedition-of-vmware-vsphere41.html
Enterprise Plus
YES
YES
Free edition of VMware

vSphere 4.1 (VMware
Sphere Hypervisor,
VMware ESXi Single
Server, free ESXi or
VMware:
Enterprise
Cisco Public
Standard
66
Cisco Virtual Appliance OVA/OVF File

OVA
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
Cisco will provide OVA files on CCO for UC applications
deployment on VMware
OVA Files for UC on UCS Deployments:

BRKUCC-2011
Cisco Public
http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29
67
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:
BRKUCC-2011
Cisco Public
http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Sizing_Guidelines
68
CUCM 8.6 VMware Guest OS Type

RHEL 4
CUCM 8.0 and 8.5 is

based on Red Hat
Enterprise Linux 4 32 bit
RHEL 5
Upgrade
CUCM
8.0 or 8.5
CUCM is based on Red

Hat Enterprise Linux 5
32 bit
CUCM
8.6
Upgrade in a UC on
UCS deployment to
CUCM 8.6 requires
Guest OS to be change
for the VM
* Upgrade to CUCM 8.6 from previous appliance is a new

Refresh Upgrade with more downtime
BRKUCC-2011
Cisco Public
69
UC Application Migration
MCS Server and Supported Unified CM Versions

TYPE 1 Servers
CUCM 8.0 in Production
CUCM 8.5 in Bridge mode
TYPE 2 Servers
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
BRKUCC-2011
Cisco Public
71
Type 1: UC on UCS Platform Conversion

TYPE 1 Servers
Refresh
Upgrade
CUCM 8.6 on MCS
in Production
Platform
Conversion
with DRS
CUCM 8.6 on UCS

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 by to UCS
Publisher first
Subscriber first
Co-exist with other MCS servers for SMDI or USB MOH
BRKUCC-2011
Cisco Public
72
Upgraded
Unified CM
8.6 on
MCS
New
Unified CM
8.6 on
UCS
Install on
First
node or
Publisher
DRS
Backup
sFTP
Server
DRS
Restore
on First
node or
Publisher
Unified
CM 8.6
ISO
Image
New
Unified CM
8.6 on
UCS
New
Unified CM
8.6 on
UCS
Install on
Secondary
node or
Subscriber
Upload
Licenses
sFTP
Server
New
Unified CM
8.6 on
UCS
All three
types of
licenses
Unified
CM 8.6
ISO
Image

BRKUCC-2011
Cisco Public
73

TYPE 2 Servers
L2 Upgrade
CUCM 8.0 on MCS
in Production
Platform
Conversion
with DRS
CUCM 8.0 on UCS

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
Publisher first
Subscriber first
Co-exist with other MCS servers for SMDI or USB MOH
Refresh upgrade to CUCM 8.6 once on UCS. Guest OS change.

BRKUCC-2011
Cisco Public
74
Upgraded
Unified CM
8.0 on
MCS
New
Unified CM
8.0 on
UCS
Install on
First
node or
Publisher
DRS
Backup
sFTP
Server
DRS
Restore
on First
node or
Publisher
Unified
CM 8.0
ISO
Image
New
Unified CM
8.0 on
UCS
New
Unified CM
8.0 on
UCS
Install on
secondary
node or
Subscriber
Upload
Licenses
sFTP
Server
New
Unified CM
8.0 on
UCS
All three
types of
licenses
Unified
CM 8.0
ISO
Image

BRKUCC-2011
Cisco Public
75

TYPE 3 Servers
L2 Upgrade
CUCM 8.5 on MCS
in Bridge mode
Platform
Conversion
with DRS
CUCM 8.5 on UCS

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
BRKUCC-2011
Cisco Public
76
Upgraded
Unified CM
8.5 on
MCS
New
Unified CM
8.5 on
UCS
Install on
First
node or
Publisher
DRS
Backup
sFTP
Server
DRS
Restore
on First
node or
Publisher
Unified
CM 8.5
ISO
Image
New
Unified CM
8.5 on
UCS
New
Unified CM
8.5 on
UCS
Install on
secondary
node or
Subscriber
Upload
Licenses
sFTP
Server
New
Unified CM
8.5 on
UCS
All three
types of
licenses
Unified
CM 8.5
ISO
Image

BRKUCC-2011
Cisco Public
77

TYPE 4 Servers
L2 Upgrade
CUCM 8.0 on MCS
in Bridge mode
Platform
Conversion
with DRS
CUCM 8.0 on UCS

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
BRKUCC-2011
Cisco Public
78
Upgraded
Unified CM
8.0 on
MCS
New
Unified CM
8.0 on
UCS
Install on
First
node or
Publisher
DRS
Backup
sFTP
Server
DRS
Restore
on First
node or
Publisher
Unified
CM 8.0
ISO
Image
New
Unified CM
8.0 on
UCS
New
Unified CM
8.0 on
UCS
Install on
secondary
node or
Subscriber
Upload
Licenses
sFTP
Server
New
Unified CM
8.0 on
UCS
All three
types of
licenses
Unified
CM 8.0
ISO
Image

BRKUCC-2011
Cisco Public
79

TYPE 1 Servers
TYPE 2 Servers
TYPE 5 Servers
Platform
Conversion
with DRS
TYPE 3 Servers
TYPE 4 Servers
Type 5 servers can not be upgrade to CUCM 8.0 or later
Use DRS to swap appliance to type 1 to type 4 server type

(bridge hardware)
Use the type 1 to type 4 platform conversion to get to UCS
Using VMware in-lieu of bridge hardware is not officially

supported
BRKUCC-2011
Cisco Public
80
UC on UCS Platform Conversion with BAT Export

TYPE 1 Servers
TYPE 2 Servers
TYPE 3 Servers
BAT Export
BAT Data
BAT Import
CUCM 8.6 on UCS

in Production
TYPE 4 Servers
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
Normalize services in each CUCM node
Migration can be done with dual clusters
CSCti96515 Bulk Admin Export doesnt work on large dial plan

runs out of heap space
Fixed in 8.5(1)SU3, 8.6(1), 7.1(5.33042-1)ES or above
BRKUCC-2011
Cisco Public
81
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
BRKUCC-2011
Cisco Public
82
Questions ?
BRKUCC-2011
Cisco Public
83
Connect with Your Peers and Cisco

Discuss business, IT, architecture,
adoption and product topics with peers
Cisco Collaboration Community

and User Group
-Unified communications, collaboration

applications, customer care, telepresence
Interact with Cisco Product Managers,

Technical Marketing Engineers and
Services Consultants
Learn about new product announcements
Join the Collaboration User Group
-Influence product direction
-Access to Beta trials
-Exclusive programs, advisory groups and
briefings
-Membership is free!
Visit the Collaboration Community and join the Collaboration User Group at:
www.cisco.com/go/joinconversation
BRKUCC-2011
Cisco Public
84
Please complete your Session Survey

We value your feedback
Don't forget to complete your online session evaluations after each session.
Complete 4 session evaluations & the Overall Conference Evaluation
(available from Thursday) to receive your Cisco Live T-shirt
Surveys can be found on the Attendee Website at www.ciscolivelondon.com/onsite
which can also be accessed through the screens at the Communication Stations
Or use the Cisco Live Mobile App to complete the
surveys from your phone, download the app at
www.ciscolivelondon.com/connect/mobile/app.html
1. Scan the QR code
(Go to http://tinyurl.com/qrmelist for QR code reader
software, alternatively type in the access URL above)
2. Download the app or access the mobile site
3. Log in to complete and submit the evaluations
http://m.cisco.com/mat/cleu12/
BRKUCC-2011
Cisco Public
85
Recommended Reading
Please visit the Cisco Store for suitable reading.
BRKUCC-2011
Cisco Public
87
Thank you.
BRKUCC-2011
Cisco Public
88

Brkucc 2011

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

Caricato da

Copyright:

Formati disponibili

Best Practices for Migrating Previous Versions of

Cisco Unified Communications Manager (CUCM)

Follow us on Twitter for real time updates of the event:

We value your feedback- don't forget to complete your online session

Visit the Cisco Store to purchase your recommended readings

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Unified Communications Manager 8.X Licenses

2012 Cisco and/or its affiliates. All rights reserved.

2012 Cisco and/or its affiliates. All rights reserved.

Color Code for Versions of Unified CM

2012 Cisco and/or its affiliates. All rights reserved.

Platform conversion from

Release Numbering Change with 8.X and Higher

Introduced to align with system release numbering

2012 Cisco and/or its affiliates. All rights reserved.

W1 Upgrade: Windows to Appliance model

-I.E. Unified CM 4.1(3), 4.2(3), or 4.3(2) to 7.1(5b)

L2 Upgrade: Appliance to Appliance model

RU (Refresh Upgrade): Appliance to Appliance model

2012 Cisco and/or its affiliates. All rights reserved.

W1 Upgrade: Windows to Appliance model

Save DMA File

Details of W1 Upgrade is in Appendix A

2012 Cisco and/or its affiliates. All rights reserved.

Node, DLU and

L2 and RU Upgrade: Appliance to Appliance model

2012 Cisco and/or its affiliates. All rights reserved.

L2 and RU Upgrade: Appliance to Appliance model

Existing Unified CM and RHEL versions

RHEL 4: Unified CM 7.X, Unified CM 8.0 and Unified CM 8.5

Upgrade between RHEL 3 and RHEL 4 will be L2

2012 Cisco and/or its affiliates. All rights reserved.

L2 Upgrade: Appliance to Appliance model with Unified

Active partition is running while upgrade software is being

Low downtime since upgrade can be done while system

2012 Cisco and/or its affiliates. All rights reserved.

Refresh Upgrade (RU): Appliance to Appliance model

Server is down while upgrade

Higher downtime since upgrade

2012 Cisco and/or its affiliates. All rights reserved.

Refresh Upgrade (RU) Notes

MCS7825H3 and MCS7828H3 will require external USB device to

Track console of server to see progress of the installation

2012 Cisco and/or its affiliates. All rights reserved.

One-Step Minor Upgrades (Appliance)

Stay updated to avoid multiple steps upgrade. I.E.

Unsupported Upgrade to Version 8.6(1a)

Latest SU updates of 7.1(5b) SU4 can not be upgraded to version

4.X -> 7.1(5b) - > 7.1(5b) SU4

Two-Step Minor Upgrades (Appliance)

For end of support and appliance versions of Unified CM

For end of support and Windows version of Unified CM

4.1(3) and 4.2(3)

Windows 2000 to Windows 2000

Minimize number of major version changes to minimize impact to users

6.1(1) 6.1(3b) 6.1(5) SU3 8.6(2a)

6.0(1) ->6.1(1) -> 6.1(3b) -> 6.1(5) SU3 -> 8.6(2a)

Upgrades for Engineering

Engineering special does not have any impact on direct or

Engineering Special (ES) and Windows SR Upgrade Note:

Sample Unified CM 7 and 8 Versions and Builds

(A) Major version

2012 Cisco and/or its affiliates. All rights reserved.