Brkucc 1903

Migration and Co-Existence Strategy for Unified
Communications (UC) or Collaboration Applications in a

Virtualized Environment
BRKUCC-1903
Brandon Ta, Technical Solutions Architect

bta@cisco.com
Required GAAP Reconciliation
and Forward-Looking Statements
The Cisco products, service or features identified in
this document may not yet be available or may not
be available in all areas and may be subject to
change without notice. Consult your local Cisco
business contact for information on the products or
services available in your area. You can find
additional information via Ciscos World Wide Web
server at http://www.cisco.com. Actual performance
and environmental costs of Cisco products will vary
depending on individual customer configurations and
conditions.
BRKUCC-1903 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
Agenda
Objectives and Scope
Overview of UCS
Supported UCS Platform
Bare Metal to Virtual Conversion
Option with Sizing and VM Placement
VMware Support
Migration
CUCM License
Q&A
Session Objectives and Scope
1
Session Objectives
To provide a foundational knowledge of UCS, VMware and Cisco
Collaboration in a virtualized environment
To understand some of the considerations and approaches for migrating
from a bare metal server to virtualization environment
Session Scope
Cover in detail platform conversion from bare metal server to virtualized
environment
Technical aspects of Cisco collaboration in a virtualization environment
Platform
VMware
Migration
TRC Specs-Based
Platform Conversion
PCS
VMware
Supported
Servers
MCS, HP or IBM Servers

Compatibility Information for Cisco Unified Communications Manager Release 10.x
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/compat/matrix/10_x/CUCM_BK_CD1DB914_00_compat_matrix.pdf
NEW
Overview of UCS
UCS Layout
2 x Unified Fabric Building Block: 2 x FI + chassis
Uplinks
Interconnects to Existing LAN/SAN
(Embedded mgmt,
access layer for multiple
UCS chassis)
2 x Fabric
BLADE CHASSIS Extenders
REAR VIEW (I/O MUX, CMC)
6U chassis
(one or more)
BLADE CHASSIS
FRONT VIEW Stateless compute
blades w/ CIMC,
CNA, opt. HDDs
UCS Logical View
ETH 1 ETH 2
SAN A SAN B MGMT
MGMT
Uplink Ports
OOB Mgmt
6200 6200
Fabric Switch
Server Ports
Fabric A Cluster Fabric B
Fabric Extenders I Chassis 1 I I Chassis 2 I

O O O O
M M M M
Virtualized Adapters A CNA B A CNA CNA B

Compute Blades B200 B440
Half / Full width
UCS Blade Servers
B22 M3 B200 M3 B230 M2 B260 M4 B420 M3 B440 M2 B460 M4

Slots 1 1 1 1 2 2 4
E7-2800/
CPU E5-2400 E5-2600 E7-2800/8800 E5-4600 E7-4800/8800 E7-4800/8800
4800/8800
Cores 16 16 20 30 32 40 60
DIMMs 12 24 32 48 48 32 96
Max GB 384GB 768GB 512GB 1.5TB 1.5TB 1TB 3.0TB
Disk 2 x 2.5 2 X 2.5 2 SSD 2 x 2.5, 2 SSD 4 x 2.5 4 x 2.5 4 x 2.5
Raid 0/1 0/1 0/1 0/1 0/1/5/10 0/1/5 0/1
Integrated I/O Dual 10Gb Dual 20Gb No No Dual 20Gb No No
Mezz 1 2 1 3 3 3 6
UCS Rackmount Servers
C22 M3 C24 M3 C220 M3 C240 M3 C260 M2 C420 M3 C460 M4

RU 1 2 1 2 2 2 4
CPU E5-2400 E5-2400 E5-2600 E5-2600 E7-2800/8800 E5-4600 E7-4800/8800
Cores 16 16 16 16 20 32 60
DIMMs 12 12 16 24 64 48 96
Max GB 384GB 384GB 512GB 768GB 1TB 1.5TB 6TB
8 x 2.5 or 24 x 2.5 or 8 x 2.5 or 24 x 2.5 or 16 x 2.5 or
Disk 16 x 2.5 16 x 2.5
4 x 3.5 12 x 3.5 4 x 3.5 12 x 3.5 32 x SSD
2 x 1Gb + 2 x 1Gb +
LoM 2 x 1Gb 2 x 1Gb 2 x 1Gb 4 x 1Gb 2 x 10Gb
2 x 10Gb 2 x 10Gb
PCIe 10 x PCIe
2 x PCIe 3.0 5 x PCIe 3.0 2 x PCIe 3.0 5 x PCIe 3.0 6 x PCIe 2.0 6 x PCIe 3.0
Slots 3.0
UCS E-Series Service Module
UCS-E140S UCS-E140D(P) UCS_E160D(P)

Slot Single-wide SM Double-wide SM Double-wide SM
CPU E3-1105C (1 GHz) E5-2418L (2 GHz) E5-2428L (1.8 GHz)
Cores 4 4 6
Memory 8 16GB 8 - 48GB 8 - 48 GB
200 GB 2 TB (2 HDD) 200 GB 3 TB (3 HDD) 200 GB 3 TB (3 HDD)
Storage
SATA, SAS, SED, SSD SATA, SAS, SED, SSD SATA, SAS, SED, SSD
Raid 0/1 0/1/5 0/1/5
Internal: 2 GE Ports
Internal: 2 GE Ports
External: 2 GE Ports
Internal: 2 GE Ports External: 2 GE Ports
Network With DP - PCIE Card: 1
External: 1 GE Port With DP - PCIE Card: 1
GE or 1 10 GE FCOE
GE or 1 10 GE FCOE
Supported UCS Platform
Platform Options
Packaged Tested Reference

Collaboration Configuration Specs-Based
Solution (PCS) (TRC)
Any vendor
TRC Cisco UCS Architecture Overview
UCS C-series TRCs UCS B-series TRCs
(C220 M3, C240 M3 , C260 M2) (B200 M3 , B230 M2, B440 M2)
UCS 6200
Fabric Interconnect
UCS 5108 Chassis

Catalyst
FC
UCS 2200
Nexus
Fabric Extender
BE6K MDS
LAN
BE7K
SAN FC
Packaged Collaboration Solution Storage Array

(BE6K with C220 M3 or BE7K
FC SAN
with C240 M3)
Tested Reference Configurations (TRC)
T Tested R Reference C Configuration

Tested by Cisco One size fits all for all Fixed-Configuration
Guaranteed the Collaboration apps from Cisco
Application Reference for Specs- Fixed HW
Performance Based configurations
TRC PCS
Chassis Based: FC Software and Hardware
SAN only, Full or Half- Business Business Bundle for ease of
UC on UCS
width blade Edition 6000 Edition 7000 deployment
Rack Mount Based: Rack Mount Based:

DAS only, 1 to 2 Rack DAS only, 1 or 2 Rack
Unit Unit depending on
Tested Reference Configurations (TRC): BE6K versus BE7K
http://docwiki.cisco.com/wiki/Tested_Reference_Configurations_(TRC)
TRC vs. Specs-Based
Packaged Collaboration
TRC Specs-Based
Solution
Business Business
Edition 6000 Edition 7000
UC on UCS UC on UCS 3rd-Party
Any Server
Choices
Less More
(Leverage Existing Investment)
Assurance Less
More
Simplicity
More Ease of Deployment Less
TAC Notes
http://www.cisco.com/en/US/customer/products/ps6884/products_tech_note09186a0080bf23f5.shtml
TRC Platform Selection
Size Visual TRC vCPU Storage
Failure domain
Extra-Extra UCS B440 M2 TRC#1
40 FC San
Large (2XL)
vCPU (Sizing)
Extra-Large UCS C260 M2 TRC#1
20 DAS
Storage Technology
(XL)
Extra-Large
UCS B230 M2 TRC#1
(XL) 20 FC San
DAS
:Large (L)
UCS C240 M3S (SFF)
16 DAS FC SAN: Redundancy
TRC#1
:Large (L)
UCS B200 M3 TRC#1
16 FC San Most deployed
Medium (M)
UCS C240
M3S (SFF) TRC#2 12 DAS
Platform longevity and
(BE7K) performance: Newer generation of
Medium (M)
UCS C220 M3S (SFF)
8 DAS
servers (M2 versus M3)
TRC#1
UCS C220 M3S (SFF)
Small Plus (S+) 16 DAS
TRC#3 (BE6K HD)
UCS C220 M3S (SFF)
Small (S) 8 DAS
TRC#2 (BE6K MD) Restricted performance CPU (CUCMBE 6K)
TRC: Allowed Deviations
Component Modifications Allowed?
Server Model/Generation
Model, CPU version Within the same family
CPU Quantity and # cores
Speed Yes, if higher
Physical Memory Yes, if higher
Quantity, RAID, technology

DAS Storage
Disk size and speed Yes, if higher
Off-box Storage FC protocol
C-series (NIC Type, vendor,

technology)
Adapters
C-series (NIC card quantity) Yes, if higher
B-series (Mezzanine card)
Specs-Based: Requirements
TRC Specs-Based
Limited Any server ANY Server on VMware HCL

Cisco UCS servers
Xeon 5600 or 7500 with speed 2.53+ GHz
E7-2800/4800/8800 with speed 2.4+ GHz
E5-2600/4600 with speed 2.5+ GHz
Limited CPUs More CPUs options E5-2400/4600 with speed 2.0+ GHz (Restricted UC Performance) NEW
E7-2800/4800/8800 with speed 2.0+ GHz (Restricted UC Performance) NEW
Any Storage compatible with Server and VMware

Limited DAS
E.g. Other DAS configs, FC, FCoE, iSCSI, NFS NAS
Flexible DAS & SAN
& FC SAN only
Any adapters compatible with server and VMware

Select HBA &
Flexible adapters
1GbE NIC only
vCenter required (for logs and statistics)
Optional Required Specification-Based Hardware Support
http://docwiki.cisco.com/wiki/Specification-Based_Hardware_Support
What about ISR Blades Support?
No Support
AXP SRE AXP SRE
Limited for US DoD only with

CUCM 8.6.(2) and later
UCS Express SREV-910 (controlled release)
CUC Specs-based only
MediaSense 8.5(4) and above
Specs-Based only
Restricted UC Perf CPU
UCS E140D
(E5-24XX at 2.00+ GHz)
Fewer than 100 users, < 4 VMs
UCS E-Series No Support generally
UCS E160D/DP
No TRC until Midmarket comes out
UCS E140DP
with extra-small option with BE 6000
on E-Series (not committed)
UCS E140S
TRC or Specs-Based Decision Tree
Evaluation criteria for platform decision
Start Virtualization
Proficiency
LOW
TRC 1 between TRC and Specs-Based varies
based on organization priorities
HIGH Virtualization proficiency
Performance guarantee
Performance
Guarantee
YES
TRC 1 Platform and vendor choices
Differences in supported
NO applications, noticeably
Contact Center
UC Applications
Supported by
Specs-Based
NO
TRC 1 Telepresence
WebEx Meeting Server
YES
Solution should be consistent, but can
Specs-
be hybrid
Based
Unified Communications Virtualization Supported Applications:
http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications
UCS Platform Emulator Available
Free
Reference
Full fledged UCS Manager emulated

in a VM
Runs right inside a laptop/desktop
Sports the entire UCS Manager API
Imports config/inventory from real
UCS setups
Used widely for training & API
development
Available as a VM (OVA) from
http://communities.cisco.com/ucs
Bare Metal to Virtual Conversion
Bare Metal to Virtual with TRC
Platform UC App UC App UC App UC App
Conversion
VOS VOS VOS VOS
ESXi 4 Hypervisor
CPU Memory NIC Storage
UCS Hardware
Bare Virtualized Virtualized Design Criteria

Metal w/C w/B
Server Series Series
CPU vCPU vCPU Calculate due limited vCPU
DRAM vRAM vRAM Not a limiting factor
DAS DAS FC SAN DAS: Not a limiting factor

(Disk) (vDisk) (vDisk) FC SAN: Calculate and provide to storage team
Sample VM templates (OVA)
Product Capacity vCPU vRAM vDisk (GB) Cisco OVA provides virtual
(Devices) (GB)
hardware requirements (vCPU,
10,000 4 6 1 x 110 vRAM and vDisk) and disk
7,500 2 6 1 x 110
alignment for deployment
CUCM 10.X
2,500 1(2) 4 1 x 80 2500 devices 1 vCPU OVA might
1,000 2 4 1 x 80 suffer audio issue during (upgrade,
20,000 7 8 2 x 300/500
DRS or CDR write. Recommend to
Unity use 2 vCPUs
10,000 4 6 2 x 146/300/500
Connection
10.X 5,000 2 6 1 x 200 Add another 2 GB of vRAM and 30
1,000 1 4 1 x 160 GB vDisk becomes 7500 devices
OVA
15,000 full UC 4 6 2 x80
Unified IM & 5,000 full UC 2 4 2 x 80 10000 devices OVA uses only 2
Presence 10.x 2,000 full UC 1 4 1 x 80 more vCPUs, but multiply by the
1,000 full UC 2 2 1 x 80
number CUCM VMs
Restricted performance CPU (CUCMBE 6K)
CUCM Bare Metal Server to Virtual (OVA) Conversion
OVA Smaller MCS server converts to a
standard 2500 device OVA or restricted
MCS Maximum OVA vCPU
Server Number Deployment
performance CPU OVA on CUCMBE 6K
Model of Phone Size can be used
7845-I3 or 10000 10000 4
earlier Convert for all collaboration applications
7845-I3 or 7500 7500 2 per location and total the number of vCPU
earlier
7845-I2/H2
or earlier
7500 7500 2 vCPU is the critical factor in platform (TRC
7825-I5 or 1000 2500 2
or Specs-based) selection
earlier
7825-I5 or 1000 1000 2
MCS and C series both has similar direct
earlier attached storage (DAS)
7816-I5 or 500 1000 2
earlier Storage option for redundancy: FC SAN
7828-I5 or 500 1000 2
earlier
Restricted performance CPU (CUCMBE 6K)

Sample FC SAN IOP Requirement for Server Team
Solution BHCA Average IOPs No normalization of IOPs
data for every applications
10K ~35
Provide as much data and
CUCM 25K ~50 profile characteristic as
possible
50K ~100
Individual application IOPs
CUCM upgrades generate 800 to 1200 IOPS in addition to steady state IOPS based on BHCA and DRS
DRS: 50 IOPS (Pub only)
Solution VM Size Average IOPs Cluster IOPs based on
single or multiple concurrent
1000 ~50 servers upgrade
Presence
VM Size Average IOPs Peak IOPs

Unity Connection steady
Solution
state is average IOPs and
2 vCPU (5K Users) ~130 ~715 few minutes of spike at peak
IOPs
Unity Connection
4 vCPU (10K Users) ~220 ~870
Collaboration IOPs Requirements:

http://docwiki.cisco.com/wiki/UC_Virtualization_Storage_System_Design_Requirements
Sample C Series Connections for Network Team
C260 M2 TRC#1 6x 1GbE ports for LAN (2 LOM + 4 PCI-E) 4x dedicated 1GbE ports
LOM + NIC
C240 M3S TRC#1-2, 12x 1GbE ports for LAN (4 LOM + 8 PCI-E) 10x dedicated 1GbE ports
BE7K
LOM + NIC
C220 M3S TRC#1,3 6x 1GbE ports for LAN (2 LOM + 4 PCI-E) 4x dedicated 1GbE ports
BE6K HD
LOM + NIC
C220 M3S TRC#2 2x 1GbE ports for LAN (2 LOM) 2x 1GbE ports (shared with ESXi Mgt)
BE6K MD
LOM only
Use company standard or VMware best practices for various traffics (VM/applications, ESXi and
CIMC)
Distribute collaboration traffic between PCI-E card and LOM connections for redundancy
Separate ESXi management traffic if spare ports are available
Add same type of network card for TRC if additional ports are required
Summary
Conversion of bare metal to virtual yields 1:1 conversion
vCPU
vRAM
vDisk
Storage requirements for FC SAN (GB) including IOPs
Option with Sizing and VM Placement
Collaboration Sizing Tool (CST)
NEW
A tool to quickly and accurately size large and complex Cisco Collaboration
environment based on a system release (e.g. System Release 10.6 consisted of
CUCM 10.5(2))
New Preview Pane shown above
Formerly called Cisco Unified Sizing Tool (CUST)
On-line tool supports system release 5.1 to 8.6(1)
Excel based tool supports system release 8.0 and later
Recommended for virtualization environment and later system releases
Recommended due to auto-update
http://tools.cisco.com/cucst
Collaboration Sizing Tool (CST) NEW
Collaboration applications and virtualization results

Additional collaboration applications support such as PLM, Cisco
Expressway, TP Conductor, TP Server, Prime Collaboration, etc.
Generate summary in PDF, VMPT export in xml and Bill Of Material in
Excel format
Collaboration Sizing Tool (CST)
Cisco and specific UC partners have access to this tool
Does not support all virtualized collaboration applications
To baseline existing network to understand existing load and capacity
Used for Megacluster approval
Collaboration Virtual Machine Placement Tool
(VMPT )
Visual virtual machine(s) placement tool

Ensuring that the number of VM(s) fits into the selected platform
Application high availability enable by VM(s) placement
Resulted in server platform and usage
Navigation
Solution Type (9.1 or later)
TRC (current servers only) or Specs-based (also can be used for older UCS servers)
Collaboration applications (Use Custom application for 3rd party and CWMS)
http://tools.cisco.com/ucs
(VMPT )
Manual entry or import from CST

Support almost all of collaboration applications that can be virtualized
Does not checks or provides
ESXi version and edition support per host
Collaboration applications dependencies
IOPs data
(VMPT )
Support almost all of collaboration applications that can be virtualized

Use Custom applications for 3rd party applications or non-listed collaboration applications (e.g.
CWMS)
Does not checks or provides

ESXi version and edition support per host
Collaboration applications dependencies
IOPs data
System Level Virtual Machine Placement
System level
approach and
considerations
Application Application
Memory ESXi Version Hardware
Components that CPU Sizing
Sizing
Co-residency
Policy
and Edition
High
Availability
Optimization
are NOT checked by

VMPT
Virtual Machine CPU Sizing
Guest OS IDLE vCPU

CUCM
Total collaboration applications vCPUs Total physical Core
VM
Core Core
Socket Per host, total vCPU for all applications should not exceed the
number of physical cores on that host
1:1 mapping between vCPU (Guest OS core) to physical core
VMKernel
vCPU1 vCPU2
CPU Scheduler
Hyper threading should be enabled on VM host which yield twice as
many logical CPUs, but only 1:1 vCPU to physical core mapping
without any oversubscription
Physical layer
Core Core
Unity Connection requires an idle vCPU
Core Core
* NUMA Client and Node abstracted from diagram
Virtual Machine Memory Sizing
Reserved for
ESXi
Application 1 Application 2 Application 3 Application 4 Application 5
(vRAM 4GB) (vRAM 4GB) (vRAM 4GB) \(vRAM 4GB) (vRAM 4GB) (vRAM 4GB)
Physical Memory
Total collaboration applications vRAM + 4GB for ESXi Total physical

DRAM
Per host, total vRAM for all applications and 4GB for ESXi should not exceed the
number of physical DRAM on that host
4GB is reserved for ESXi 5.5 ( 2GB for ESXi 5.1 or earlier, but assume 4GB)
Virtual Machine Co-residency Policy
Types of Description Graphic Illustration Example
Co-residency
None Co-residency is not supported. No co-residency CWMS. MeetingPlace

UC
with ANY other VM is allowed
Co-resident application mix is restricted to specified CTS Manager & CTMS
Specific Specific
VM combinations and specific OVAs only BE6K applications
Limited Application 1 Application 2
UC with UC Co-resident application mix is restricted to VMs for CUCM 8.0 & 8.5, CER 8..5 & 8.6,
UC UC UC
UC application only. CUCCX 8.0(2)+,
Co-resident application mix may contain UC app CUCM 8.6+, IM&P 9+, CUC 8.+,
Full * VMs with Cisco non-UC VMs with 3rd-party
application VMs
UC Non-UC 3rd Party CER 8.7+, Expressway X8.1+,
VCS X7.1+, XC 1.2+, CUCCX
8.5+
* Specific conditions for co-residency TAC Technote Document ID: 113520

http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-
communications-system/113520-edcs1153298.html
http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Sizing_Guidelines#Table_of_Co-
residency_Support_Policy_by_Cisco_UC_Application
TAC Technote Document ID: 113520
1
Shutdown
4 2
3rd
Resize VMs Move VMs
UC Non-UC Cisco 3rd Party
Party UC Non-UC
3rd Party UC
Full: Co-res among Cisco UC Full: Co-res among Cisco UC Spare Server
application, Cisco non-UC and 3rd Party application, Cisco non-UC and 3rd Party
applications applications
3 Add Server Components

http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-system/113520-
edcs1153298.html
Virtual Machine Considerations
Match virtual machines that supports the same ESXi version
E.g. CUCM 10.5 supports ESXi 5.5 while Unity Connection supports ESXi 5.1
Match virtual machines that supports the same ESXi edition
Cisco UC Virtualization Hypervisor versus Foundation, Standard, Enterprise or
Enterprise plus
PCD only supports some applications. PCD is not supported with Cisco UC
Virtualization Hypervisor
vCenter is not supported with Cisco UC virtualization Hypervisor
Placement of virtual machines to distributing across ESXi hosts, chassis and
sites for:
Application level high availability. Same collaboration applications should be on different
ESXi host if possible
Distribute load for performance, failover scenarios, growth or changes in OVA size
Specific Virtual Machines Hardware Requirements
Guest OS Guest OS
Mixing hyper-threaded application versus
CUCM vTS non-hyper-threaded applications challenges
VM
VM
Core Core Core(2) Core(2)
(vTS 3.1(1.98) supports12 720p sessions)
Typical UC application vCPU ratio to Core is 1:1.
Socket Socket No hyper-thread is used
Virtual TelePresence Server (vTS) vCPU ratio to
Core is 1:2 or vCPU ratio to logical CPU is 1:1.
VMKernel
VMKernel
vCPU vCPU
vCPU1 vCPU2
1&2 3&4 Hyper-thread is used
CPU Scheduler CPU Scheduler
Cost implication to server standardization
Typical UC application requires low to medium
HT1 HT2 HT4 HT3 HT1 HT2 HT4 HT3
vCPU count, low memory and medium to high
Physical layer
Physical layer
Core Core Core Core

disk space
Core Core Core Core vTS vCPU requires high vCPU count, high
HT5 HT6 HT8 HT7 HT5 HT6 HT8 HT7
memory and very low disk space
UC Application vTS vCPU vTS 4.0(1.57) supports 8 720p sessions uses
vCPU to Core to Logical CPU 1:1 core
Summary
Baseline current environment
Re-size the virtual environment
Optimize the environment for redundancy
Placement of virtual machines in various ESXi hosts
VMware Support
Virtualization with VMware
UC Virtualization Support
Data Center & Description Support
Desktop Products
VMware Server A program that gets installed on an OS such as Windows or No
Linux
VMware Workstation Similar to Server, but adds features like snapshots. For No
developers.
ESX Hypervisor Bare-metal hypervisor in a linux-like operating system. No

Designed for datacenter use.
ESXi 4.X/5.X Hypervisor Bare-metal thin hypervisor. Designed for datacenter use. Yes
Appliance model.
vSphere 4.X/5.X Client Client software to manage vCenter or individual ESX/ESXi Yes
servers
vCenter Server Manages multiple ESX/ESXi hosts Yes

VMware Player Same as Server. Runs VMs. Cant create VMs. No
VMware Fusion Same as Player for Mac OS X No
VMware Sphere Support
ESXi Hypervisor: 4.0, 4.1, 5.0 and 5.5 (with some specific UC
VMware vCenter
Server
application exceptions)
ESXi Edition: VMware vSphere Hypervisor, Cisco UC
Virtualization Hypervisor, VMware vSphere Hypervisor
Foundation, Cisco UC Virtualization Foundation, Standard,
Enterprise or Enterprise Plus
ESXi Hypervisor
VMware vCenter: Essential, Foundation or Standard
Recommended for large deployment. centralize management, license
management, etc.
Mandatory for Specs-Based deployment
VMware acquisition: Cisco, Partner or VMware
https://www.vmware.com/files/pdf/vsphere_pricing.pdf
Hypervisor Support for Virtualized UC:
http://docwiki.cisco.com/wiki/Unified_Communications_VMWare_Requirements
VMware Feature Support and Deployment Options
LEGEND:
VMware Features vMotion Storage Copy HA Y(C) Supported with Caveats
vMotion Clone Y(P) Partial or Limited
N Not Supported
CUCM Y (C) Y (C) Y (C) Y
(C)
IM & Presence Y (P) N Y (C) Y
(C)
Unity Connection Y (P) N Y (C) Y
(C)
CCX Y (C) Y (C) Y (C) N
vMotion
Y(C): supported with Caveat: Can be done with live traffic, but slight risks to impact calls
Y(P): Partial: During maintenance window only
Copy / Clone
Y(C): supported with Caveat: Shutdown VM first
Unified Communications VMware Requirements:

http://docwiki.cisco.com/wiki/Unified_Communications_VMWare_Requirements
Cisco Virtual Template (OVA) File
OVA
2
CCO
1
vSphere
Client
UCS B200 M3
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 with Virtual Machine Hardware Version (VMV) 7 and
VMV8 on CCO for collaboration applications deployment
Deploy the latest OVA version and the highest available VMV version that
matches to ESXi version
ESXI and Collaboration OVA Version
ESXi Version VMware Virtual Recommended Cisco Collaboration Collaboration VMV Version Cisco
Machine Hardware OVA VMV Version Application Application Version OVA Version
Version (VMV)
4.0 7 7 cucm_10.5_vmv8_v1.8.ova
4.1 7 7
CUCM 10.5 8 1.8
5.0 8 8
5.1 9 8
5.5 10 8
Use matching collaboration application OVA file to correct corresponding

ISO file
E.g. plm_10.5_vmv8_v1.1.ova and
Bootable_UCSInstall_UCOS_10.5.1.10000-5.sgn.iso
VMV can be upgraded, but cannot be downgraded
CUCM 9 to CUCM 10 OVA Change
Features CUCM 9.X CUCM 10.X
RHEL Guest OS 5 (32bit) 6 (64 bit)
Adapter Type Flexible VMXNet3
Change the Guest OS from RHEL 5 (32 bit) to Guest OS 5 (32 bit)
Change Network adapter type from Flexible to VMXNET3
Manual MAC: Delete existing Network adapter then add new Ethernet Adapter with type
of VMXNET 3
Automatic MAC: Edit VMX file in the VM machine directory. Instruction in link below
VMware vSphere PowerCLI for both automatic and manual MAC. Instruction in link
below
CUCM 10.0 OVA:

http://www.cisco.com/web/software/283088407/108296/cucm_10.0_vmv8_v1.7.ova.README.txt
Bare Metal to Virtual Dependency and Support
Platform UC App UC App UC App UC App
Conversion
VOS VOS VOS VOS
ESXi 4 Hypervisor
UCS Hardware
Server Bare Metal Bare Metal Server Virtualization Virtualization Support

Layer Server Support Server Dependency
Dependency
Application / Included with Unified Communications in a Virtualized
Application Application /ESXi
Firmware CUCM ISO Environment Docwiki
ESXi / UCS
Hypervisor NA NA ESXi to C and B UCS Firmware Table
Firmware
Faster to use VOS
Hardware Firmware UCS Firmware Firmware ISO on CCO
Firmware ISO
Dependency and Support Links
MCS Server Firmware (Voice Application OS Firmware)
http://software.cisco.com/download/navigator.html?mdfid=268438148
Unified Communications in a Virtualized Environment DocWiki

www.cisco.com/go/uc-virtualized
ESXi to C and B series Firmware Table

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/release/notes/OL_26617.
html#pgfId-52774
ESXi ISO for Cisco UCS Servers

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/release/notes/OL_26617.
html#pgfId-48626
Bare Metal versus Virtualization Support
Feature Bare Metal Virtual
Music on Hold (live source) USB audio (unicast and IOS or Barix (multicast only)
multicast)
Install and upgrade error logs USB Virtual serial port
Answer file (platformConfig.xml) USB Virtual floppy
UPS via USB APC UPS via USB UPS on UCS/ESXi
Back up Tape Secure ftp
eToken encryption key USB on client and not server USB on client and not server
SMDI Serial port NA
Take these support into consideration and deploy prior to virtualizing

For CUCM 8.X and 9.X MCS server can be use for MOH and SMDI
Migration
CUCM Upgrade Definition
L2 L2 Upgrade: Appliance/Virtual to Appliance/Virtual model
Low complexity with possible shortest downtime
Between CUCM versions with the same Major RHEL versions
(e.g. CUCM 7.1(5) to 8.5 or CUCM 8.6 to 9.1)
RU RU (Refresh Upgrade): Appliance/Virtual to Appliance/Virtual model
with major RHEL version change (starting with RHEL 5)
Medium complexity with possible longer downtime
From CUCM versions 6.X, 7.X, 8.0 or 8.5 to 8.6, 9.X and 10.X
(e.g. CUCM 8.5 to 8.6 or CUCM 9.1 to 10.0)
L2 and RU Upgrade: Appliance/Virtual to
Appliance/Virtual Model
Updated
CUCM SW Order of switching version
between Publisher and
1 Subscribers during L2 and
CUCM CUCM RU is different
Publisher 2 Publisher
Active Partition inActive Partition
InActive partition Active partition

3
Switch
Version via
Active Partition inActive Partition
OS Admin
InActive partition or CLI Active partition
CUCM CUCM
Subscriber Subscriber
L2 and RU Upgrade: Appliance/Virtual to
Appliance/Virtual Decision Tree
CUCM RHEL Release
Existing CUCM Version
cluster being
upgraded 5.0(4) RHEL 3 Update 6
5.1(x) & 6.X RHEL 3 Update 8
L2
7.0(1) RHEL 4 Update 4
L2
Upgrade to same YES Perform a 7.1(3) & 8.0(x) RHEL 4 Update 7
RU
major RHEL
version L2 Upgrade 8.5 RHEL 4 Update 8
8.6* RHEL 5 Update 5
L2
NO
Upgraded 9.X RHEL 5 Update 7
Perform a CUCM
L2
RU Upgrade cluster
* RU starts with CUCM 8.6 or RHEL 5 for CUCM.
6
L2 versus RU Upgrade
L2 Active partition is running while upgrade

software is being install on inactive partition
Low downtime since upgrade can be done
Upgrade while system is functioning
Server is down while upgrade software is being install

RU More reboots for bare metal servers
Higher downtime since upgrade cannot be done while
Upgrade system is functioning

Upgrade is equal to complete installation of CUCM
Detailed L2 and RU upgrade process are

in the appendix
* Order of switching version between Publisher and Subscribers during L2 and RU is different
Refresh Upgrade (RU) and COP File
Perform a DRS back up before upgrade
Install Refresh Upgrade COP file v1.3 (ciscocm.refresh_upgrade_v1.3.cop.sgn) file on all CUCM
servers. Also for CUC, CUCM-BE 5K and IME
Active version is CUCM 8.5 or earlier (i.e. No need for CUCM 8.6, 9.X or 10.X)
Upgrade to CUCM version 8.6 or later (e.g. Required for upgrade from CUCM version 8.5 to 10.5)
No reboot is required
Installation fails if changes are already in CUCM code (e.g. ES that already have this code change)
CLI: show version active or OS Admin: Show > Software to see installed COP file(s)
Track console of server to monitor progress of upgrade IP KVM, HP ILO, or IBM RSA for bare metal
server or virtual machine console for virtual machine
CUCM RU COP file is for CUCM version 8.5 or earlier. Other collaboration solutions RU might be at a
different release (e.g. CUP 8.6(1) to CUP 8.6(4) requires CUP RU COP file v1.01)
* RU COP file might be use once for older releases while RU can occur several times due to change in
RHEL version
CUCM Refresh Upgrade COP File v1.3
http://software.cisco.com/download/release.html?mdfid=285963825&flowid=50402&softwareid=282204704&release=COP-
Files&relind=AVAILABLE&rellifecycle=&reltype=latest
In-Place L2 Upgrade Process
Version 9 of license
manager is
Enterprise License
Existing Existing Existing New CUCM New CUCM ELM
Manager (ELM)
CUCM CUCM CUCM 9.X Cluster 9.X Cluster
Cluster Cluster Cluster ELM license is
required only when
Upgrade Upgrade Switch Switch Add going from 8.X or
Publisher Partition Partition License to
Subscribers earlier to 9.X
ELM and
Back Up Inactive Inactive on on add
With DRS Partition Partition Publisher Subscriber CUCM to This scenario
ELM
applies to both bare
metal and
virtualized CUCM
CUCM CUCM
sFTP
9.X 9.X CLI or CLI or
Server
DVD Kit DVD Kit OS Admin OS Admin
1 2 3 4 5 6
In-Place RU Upgrade Process
manager is
Enterprise License
Existing Existing New CUCM Existing New CUCM ELM
Manager (ELM)
CUCM CUCM 9.X Cluster CUCM 9.X Cluster
Cluster Cluster Cluster ELM license is
required only when
Upgrade Switch Upgrade Switch Add going from 8.X or
Publisher Partition Partition License to
Subscribers ELM and earlier to 9.X
Back Up Inactive on Inactive on add
With DRS Partition Publisher Subscriber
Partition CUCM to This scenario
ELM
applies to both bare
metal and
virtualized CUCM
CUCM CUCM
sFTP
9.X CLI or 9.X CLI or
Server
DVD Kit OS Admin DVD Kit OS Admin
1 2 3 4 5 6
In-Place L2 Upgrade Process
manager is Prime
License Manager
Existing Existing Existing New CUCM New CUCM PLM (PLM)
CUCM CUCM CUCM 10.X Cluster 10.X Cluster
Cluster Cluster Cluster PLM license is
required only when
Upgrade Switch Switch Add
Upgrade
License to
going from 9.X or
Publisher Subscribers Partition Partition earlier to 10.X
PLM and
Back Up Inactive Inactive on on add
With DRS Partition Partition Publisher Subscriber CUCM to This scenario applies
PLM
to virtualized CUCM
only
CUCM CUCM Upgrade IM&P after

sFTP CUCM cluster is
10.X 10.X CLI or CLI or
Server
ISO file ISO File OS Admin OS Admin upgraded
1 2 3 4 5 6
In-Place RU Upgrade Process
manager is Prime
License Manager
Existing Existing New CUCM Existing New CUCM PLM (PLM)
CUCM CUCM 10.X Cluster CUCM 10.X Cluster
Cluster Cluster Cluster PLM license is
required only when
Upgrade Switch Switch Add
Upgrade
License to
going from 9.X or
Publisher Partition Subscribers Partition earlier to 10.X
PLM and
Back Up Inactive on Inactive on add
With DRS Partition Publisher Partition Subscriber CUCM to This scenario applies
PLM
to virtualized CUCM
only
CUCM CUCM Upgrade IM&P after

sFTP CUCM cluster is
10.X CLI or 10.X CLI or
Server
ISO file OS Admin ISO File OS Admin upgraded
1 2 3 4 5 6
CUCM 10.5 Pre-Upgrade COP File
Pre-Upgrade RSA keys Cisco Options Package
(COP) file (ciscocm.version3-keys.cop.sgn) for
software integrality protection
Install Pre-Upgrade COP file (ciscocm.version3-
keys.cop.sgn) file on all CUCM servers. Also for
IM&P 10.5 and PLM 10.5
- Active version is 9.1(2) or earlier (i.e. No need for CUCM 10.0)
- Upgrade to CUCM version 10.5 or later (e.g. Required for

upgrade from CUCM version 8.6 to 10.5)
- No reboot is required
- CLI: show version active or OS Admin: Show > Software to

see installed COP file(s)
PCD does not automate this COP file installation

Install RU COP file prior to the Pre-Upgrade COP
Pre-Upgrade COP file
File
http://software.cisco.com/download/release.html?mdfid=284603137&flowid=47762&softwareid=282204704&release=COP-Files&relind=AVAILABLE&rellifecycle=&reltype=latest
CUCM Migration Definition
Bridge
Bridge Upgrade: Appliance to Appliance model
Upgrade is allowed with Cisco CallManager service Not Running
Long downtime due non-functional system and a platform change
(e.g. Older servers that cannot newer version of CUCM)
Jump Jump Upgrade: Appliance to Virtualized model
Virtualized CUCM with 6.1(4), 6.1(5), 7.1(3) and 7.1(5) for lab upgrade
Minimal downtime due to lab upgrade
(e.g. Older servers that cannot upgrade to 8.0(3) or later to virtualized)
PC Platform Change: Appliance to Virtualized model
Variable complexity with variable downtime pending approach
(e.g. Older servers that cannot support the latest CUCM or CUCM 10.X)
Bridge Upgrade
Upgrade DRS DRS
DRS
File
Servers supported to run Servers supported to Virtualized CUCM
CUCM version X be in Bridge mode on Secure FTP
CUCM version Y Server
Server platform change for discontinued servers that cannot run latest CUCM version
- Allows for a successful upgrade with Cisco CallManager service in in Not Running state
- Platform change is done with DRS backup and restore
- Use case include appliance to appliance and appliance to virtualized
Requires rehost of license file due to MAC or License
MAC change caused by server change
For a virtualized environment, use Answer File Generator to proactively obtain
license file
Bridge Upgrade
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/cucos/8_0_2/cucos/osg_802_cm/iptpch7.html#wp1058411
Jump Upgrade
Servers that cannot run Virtualized CUCM

CUCM 8.0(2) or later to Jump Upgrade Process 9.1(2)
virtualized
Upgrade process of multiple steps:

- Upgrade from CUCM 6.1(4), 6.1(5), 7.1(3) or 7.1(5) ONLY
- Upgrade to CUCM 9.1(2) ONLY
- Lab migration ONLY
Allows bare metal CUCM at version 6.1(4), 6.1(5), 7.1(3) or 7.1(5) migrating to
virtualized CUCM at version 9.1(2)
- Minimal down time
- Database lockdown time (i.e. No MACD)
- No license required for interim upgrades
Jump Upgrade Process
Disk
LAB Alignment
To
Production
New New Upgraded Upgraded New New
CUCM 6.X virtualized virtualized virtualized virtualized virtualized virtualized
or 7.X on CUCM 6.X CUCM 6.X CUCM CUCM CUCM CUCM
MCS or 7.X or 7.X 9.1(2) 9.1(2) 9.1(2) 9.1(2)
Build
same Upgrade Build new
DRS CUCM DRS to CUCM DRS CUCM DRS
Backup version Restore 9.1(2) Backup 9.1(2) Restore
CUCM CUCM CUCM

sFTP 6.x or sFTP 9.1(2) sFTP 9.1(2) sFTP
Server 7.X ISO Server ISO Server ISO Server
Image Image Image
1 2 3 4 5 6 7
CUCM Platform Conversion
PC Platform Conversion: Bare metal CUCM to virtualized CUCM
(Required for CUCM 10.X)
Two approaches to this platform conversion NEW
1. Manual
2. Automated with CUCM 10.0 or later and Prime Collaboration Deployment
NEW (PCD)
E.g. Bare metal server to virtualized CUCM with VMware
Cisco UC Application
1 Manual UC App
VOS
UC App
VOS
UC App
VOS
UC App
VOS
Cisco Voice Operating Systems

(VOS)
ESXi 4/5 Hypervisor
Automated
Server Hardware
2 w/ PCD Server Hardware
CP Memor NI Drive
U y C CPU Memory NIC Storage
1. Manual Platform Conversion for 8.0(2) - 9.1(2)
Platform conversion with same
version with no upgrade
New New CUCM
CUCM on virtualized virtualized Publisher
New
virtualized License upload:
MCS CUCM CUCM or ELM CUCM
DRS - 8.X: Node, DLU and SW
Install on Restore Install on Feature with license MAC on
First node on First Secondary
DRS or node or Upload node or Publisher
Backup Publisher Publisher License(s) Subscriber
- 9.X: License to ELM
CUCM CUCM
sFTP ISO sFTP ISO
Server Image Server Image
1 2 3 4 5
Replacing a Single Server or Cluster for Cisco Unified Communications Manager:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/install/9_1_1/replace/CUCM_BK_R1B1A464_00_replace-server-cluster-cucm-91.html
1. Manual Platform Conversion/Upgrade for
8.0(2) - 9.1(2)
RU
Upgrade
New New CUCM New Virtualized

CUCM on virtualized virtualized Publisher virtualized CUCM 10.X
MCS CUCM CUCM or ELM CUCM
DRS Upgrade ELM to PLM before
Install on Restore Install on
First node on First Secondary RU upgrade CUCM to 10.X
DRS or node or Upload node or
Backup Publisher Publisher License(s) Subscriber License upload:
- 8.X: Node, DLU and SW
Feature with license MAC on
Publisher
CUCM CUCM
sFTP ISO sFTP ISO - 9.X: License to ELM
Server Image Server Image
5 - 10.X: License to PLM
1 2 3 4
1. Manual Platform Conversion/Upgrade for
6.1(4), 6.1(5), 7.1(3) or 7.1(5)
RU
Upgrade
CUCM on Virtualized Virtualized

MCS Jump Upgrade Process CUCM 9.1(2) CUCM 10.X
Leverage Jump Upgrade to by-pass MCS server limitation on running CUCM 8.X or later to get to
CUCM version 9.1(2)
RU upgrade to CUCM version 10.X
Jump Upgrade Procedure:

https://supportforums.cisco.com/sites/default/files/legacy/3/6/1/15365163-Drive_to_Nine_Jump_upgrade_versions_4.1.3-7.1.5_to_9.1.2%5B2%5D.pdf
1. Manual Platform Conversion Using New
Cluster Option for 6.X, 7.X, 8.X, 9.X and 10.X
New cluster:
- Existing data with DRS restore with same CUCM version
- New data without DRS restore and at any CUCM version *
ICT
Existing New Other use case:
CUCM CUCM
Cluster Cluster - Platform conversion for earlier releases that Jump Upgrade
does not support
- Cluster consolidation *
- Controlled migration of large deployment *
* Phones certificate will need to be considered with Bulk Certificate Export

**For CUCM 6.X and 7.X, platform conversion will be required on the new cluster
Bulk Certificate Export:

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/security/9_1_1/secugd/CUCM_BK_C0395F44_00_cucm-security-guide-91.html
Prime Collaboration Deployment (PCD)
PCD is a VMware vApp used for management of
Cisco collaboration applications:
CUCM 6.X
- CUCM
- CUC
- CUP / IM&P
CUCM 7.X
PC
- CUCCX
D
- Management tasks (Upgrade, Switch Versions,
Server Restart, Readdress, Install and Migrate)
are based on collaboration application and version
CUCM 8.X
of the application
VMware vApp is pre-configured virtual machine
ESXi Host with OS and PCD application (1.4GB)
- pcd_vApp_UCOS_10.5.1.10000-
6_vmv7_v1.2.ova
PCD Versions and Builds Reference
PCD Version PCD Build

10.5(1) NEW
10.0.1.10000-14
10.0(1) 10.5.1.10000-6
CUCM Supported Tasks by PCD 10.5
Feature CUCM CUCM CUCM CUCM CUCM CUCM CUCM
6.1(5) 7.1(3), 7.1(5) 8.0(1-3) 8.5(1) 8.6(1-2) 9.x 10.X
Migration to 10.X X X X X X X X
Fresh Install X
Upgrade (also COP X X X

Installation)
Switch Version X X X
Restart X X X
Readdress X
(Hostname/IP
Address Change)
Capability for other collaboration applications:

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/pcdadmin/10_5_1/CUCM_BK_U35347D2_00_pcd-administration-guide-1051.pdf
PCD Requirements PCD CUCM CUC CUCCX
VOS VOS VOS VOS

Virtual machine virtual requirements
- 2 vCPU ESXi 4/5 Hypervisor
- 4 GB vRAM Server Hardware
- 80 GB vDisk CPU Memory NIC Storage
VMware requirements
- ESXi 4.1, 5.0, 5.1 and 5.5
- VMware API:
- Cisco UC Virtualization Foundation, VMware vSphere Foundation, Standard Edition, Enterprise Edition, or
Enterprise Plus Edition
- CUCM-BE 6K and CUCM-BE 7K comes with Cisco UC Virtualization Hypervisor. Update to Cisco UC
Virtualization Foundation
PCD Administration Guide:

PCD Interactions with External Components
PCD and VMware ESXi communication
- ESXi host root credential
- NFS mount PCD /fresh_install directory
PCD
- Data center or server team coordination
PCD and CUCM communication ftp/sftp
- CUCM OS admin credential Virtualized

sftp CUCM 10.X
ucsinstall*.iso,*cop.sgn /upgrade
Management laptop and PCD bootable*.iso /fresh_install
- Web for GUI admin

- Secure ftp client to upload ISOs and COP files
VMware vSphere

2. Automated Platform Conversion with PCD
CUCM on Virtualized
MCS PCD CUCM 10.X
Bare metal CUCM to virtualized CUCM (P2V)

- Install ciscocm.ucmap_platformconfig.cop file to the source servers to export data
- Build new cluster
- Import data
Same or different destination IP address and/or hostname
Scheduled or immediate execution
PCD Considerations and Planning
Cisco UC Virtualization Hypervisor with BE6K and BE7K
Root access to ESXi host
ESXi host see another NFS datastore
Customer storage standard might not be or allow NFS
L2 and RU upgrade does not automate COP file installation
- ciscocm.version3-keys.cop.sgn
- ciscocm.refresh_upgrade_v1.3.cop.sgn
Might do a hybrid of manual and PCD upgrade due other applications
Instrumentation to monitor progress and troubleshoot
Source cluster data state and export

Reference
Upgrade and Migration Definition Table
Upgrade Definition Scenario
W1 Upgrade Windows to appliance upgrade up to CUCM 7.1(5)
L2 Upgrade Appliance to appliance upgrade within same major RHEL release (before
CUCM 8.6)
RU Upgrade Appliance to appliance upgrade between major RHEL releases (starting with
CUCM 8.6)
Bridge Upgrade Servers too old to run latest CUCM version. Use DRS file to change platform
to continue upgrade. Up to 9.1(2)
Jump Upgrade Servers too old to run CUCM version 8.0(2) or later to virtualized. Virtualized
in lab to perform upgrade. To 9.1(2) only.
Manual Platform Changing servers platform. Typically from bare metal servers to virtualized
Change environment. Might be multiple steps.
Automated Platform Automated. Potential data center access and storage standard concerns.
Change w/ PCD
Reference
Upgrade to CUCM 9.1(2)
Platform Supported Supported Not Upgrade Strategy
Number Normal Mode Bridge Supported
1 6.1-7.1 8.0 8.5-9.1 Jump upgrade
2 6.1-7.1 8.0-8.5 8.6-9.1 Jump upgrade
3 6.1-8.0 NA 8.5-9.1 Jump upgrade or upgrade to 8.0 to
change platform
4 6.1-8.0 8.5 8.6-9.1 Jump upgrade or upgrade to 8.0 to
change platform
5 6.1-8.0 8.5-9.1 NA Jump upgrade or upgrade to 8.0 to
change platform
change platform
7 7.1-9.1 NA NA Jump upgrade or upgrade to 9.1 to
change platform
Supported Cisco Unified Communications Manager Releases by Server:
http://www.cisco.com/en/US/partner/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd8062a4f9.html
Reference
Platform Migration to Virtualized CUCM 9.1(2)
1 6.1-7.1 8.0 8.5-9.1 Jump upgrade
2 6.1-7.1 8.0-8.5 8.6-9.1 Jump upgrade
3 6.1-8.0 NA 8.5-9.1 Jump upgrade or upgrade to 8.0 to
change platform
4 6.1-8.0 8.5 8.6-9.1 Jump upgrade or upgrade to 8.0 to
change platform
change platform
change platform
7 7.1-9.1 NA NA Jump upgrade or upgrade to 9.1 to
change platform
Upgrade and Platform Migration to Virtualized
CUCM 10.5
1 6.1-7.1 8.0 8.5-9.1 PCD, Jump Upgrade or manual PC at 8.0 then L2/RU to 10.5
2 6.1-7.1 8.0-8.5 8.6-9.1 PCD, Jump Upgrade or manual PC at 8.5 then L2/RU to 10.5
3 6.1-8.0 NA 8.5-9.1 PCD, Jump Upgrade or manual PC at 8.0 then L2/RU to 10.5
4 6.1-8.0 8.5 8.6-9.1 PCD, Jump Upgrade or manual PC at 8.0 then L2/RU to 10.5
5 6.1-8.0 8.5-9.1 10 PCD, Jump Upgrade or manual PC at 8.0 then L2/RU to 10.5
6 6.1-8.5 8.5-9.1 10 PCD, Jump Upgrade or manual PC at 8.5 then L2/RU to 10.5
7 7.1-9.1 NA 10 PCD, Jump Upgrade or manual PC at 9.1 then L2/RU to 10.5
Use PCD unless challenged by data center team, server team, complex hybrid migration, etc.
For manual platform conversion (PC), try to stay with Normal Mode that can be virtualized
CUCM License
CUCM 8 License MAC for Virtualized CUCM
License MAC is 12 digits HEX values based on the hash of these 10
Unified CM settings
1. Certificate Information 4. IP Mask or dhcp 8. Primary DNS
(Organization, Unit, Location, 5. Gateway Address or dhcp 9. SMTP server or none
State, Country)
6. NIC speed auto 10. Time zone
2. Hostname
7. NTP server 1
3. IP Address or dhcp
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
License Manager Versions and Builds
License Manager
Version Build
Enterprise License Manager (ELM) Same as CUCM Same as CUCM
9.0 9.1 e.g. 9.1(2) 9.1.2.10000-28
Version Build
Prime License Manager (PLM) 10.5(1) NEW 10.5.1.10000-9
10.0-10.5 10.0(1) 10.0.1.1000-19
Co-Resident Co-Resident
ELM is build into CUCM ISO Same as CUCM Same as CUCM
PLM is built into CUCM ISO or as independent ISO with standalone

deployment
Enterprise License Manager (ELM)
ELM Implementation Products
ELM
Standalone ELM
ELM + CUCM
Co-resident with CUCM ELM + CUCM
Bootable ELM + CUC Co-resident with CUC ELM + CUC

CUCM 9.X
ELM is a centralized enterprise-wide license management solution for Cisco

collaboration applications
- CUCM
- Cisco Unity Connection (CUC)
ELM deployment can be standalone or co-resident with CUCM or CUC with the same
ISO file
License file is uploaded onto ELM instead of CUCM or CUC and is based on ELM MAC
address and host ID
License file is cumulative andEnterprise
is based onUser
Manager products
Guide: (CUCM or CUC)
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/elmuserguide/9_0_1/CUCM_BK_E596FD72_00_enterprise-license-manager-user-90.html
Cisco Prime License Manager (PLM)
PLM ELM Implementation Products
Bootable
Prime_LM
Standalone PLM
Co-resident with CUCM PLM+ CUCM
Co-resident with CUCMBE 6K PLM+ CUCMBE 6K

PLM+ CUCM
Bootable Co-resident with CUC PLM+ CUC
CUCM
10.X PLM+ CUC
PLM is a centralized enterprise-wide license management solution for Cisco collaboration

applications
- CUCM, CUCM SME and CUCMBE 6K (standalone)
- Cisco Unity Connection (CUC)
- Cisco Emergency Responder (CER)
PLM deployment can be standalone or co-resident with CUCM, CUCM-BE 6K or CUC
Cisco Prime License Manager User Guide:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/plm/10_5_1/userguide/CPLM_BK_UD1156AD_00_user-guide-rel-1051.html
License Manager Architecture 9.X and 10.X
First First
node of node of
CUC 1 CUC 2 CER 1
First Node of First Node of
CUCM Cluster 1 CUCM Cluster 2
CER
License License License License License
Manager Manager Manager Manager Manager
API API API API API
ELM / PLM
ELM / PLM
License file
License Manager API added to CUCM 9.X/10.X and CUC 9.X/10.X to interact with ELM /
PLM for license request and approval
License Manager API added to CER 10.X to interact with PLM for license request and
approval
Electronic fulfillment supports License Feature and Version Upgrades in PLM 10.X
License Manager Product Support and Usage
Product Version ELM (Bare Metal or Virtualized) PLM (Virtualized)
CUCM 9.X Yes Yes
CUC 9.X Yes Yes
CUCM 10.X Yes w/ License Definition Yes
CUC 10.X Yes w/ License Definition Yes
CER 10.X No Yes
License Definition = elm_LicenseDef_9_1_v1.cop.sgn
For CER 10.X support, use PLM

For bare metal environment, use ELM
For virtualized PLM and virtualized CUCM with co-resident PLM manually set MAC
address since license is partly based on MAC address (Edit virtual machine settings >
Machine Network adapter > Manual) before requesting license file
ELM to PLM Upgrade
ELM 9.X ELM 9.X
PC
ELM/PLM
ELM 9.X Upgrade PLM 10.0
ELM/PLM
ELM 9.X Upgrade PLM 10.5
Use Replacing a Single Server for Cisco Unified Communications Manager procedure
to change from bare metal ELM to virtualized ELM
Use ELM/PLM upgrade COP file (elm_Elm_v9_1_1_PlmUpgrade.cop.sgn) to allow for
ELM to PLM upgrade
Use pre-upgrade RSA keys COP file (ciscocm.version3-keys.cop.sgn) to upgrade to
PLM 10.5
CUCM and ELM/PLM Interaction
ELM/PLM polls all registered CUCM clusters
CUCM evaluates license usage and sends license
usage back to ELM/PLM
CUCM ELM/PLM
Evaluate phone, Poll all products ELM/PLM evaluate all CUCM responses to see if
users and every 24 hours there is adequate licenses for the requested types
features usage Evaluate adequate
Send license
licenses ELM/PLM performs license substitution if does not
Perform license have adequate license of the requested type
usage to ELM substitution
Receive license Provide Valid or
response and Invalid license
ELM/PLM response back to with either valid or
operate in the response invalid (not enough) to all CUCM clusters
appropriate
mode CUCM receives the response and function
accordingly
Detailed CUCM and ELM/PLM interactions with
signaling are in the appendix
CUCM License Usage
Extension mobility users: No license
1 User Extension mobility user with Unified Mobility (SNR): UCL Basic license
Device without Owner User ID association: UCL
2 Device

Based on the device
E.g. Public space phones, shared workspace phones, etc.
Device with Owner User ID association: UCL or CUWL

User
3 / Device
Based on the model of device and the number of devices assigned to the user
I.e. 2 devices: UCL, 3 -10 devices: CUWL
TelePresence (TP) device
4 TelePresence E.g. CTS, MX, SX, TX, etc.

List of devices and associated license are in the appendix
Device and Owner User ID Association
Device > Phone > Device Name Device with Owner User ID field configured
potentially uses less licenses
- I.E. Extension mobility user with Unified
Mobility feature and a phone uses one
license
- I.E. Multiple phones with the same Owner
ID field
Number of Phones Type of License
1 Enhance UCL
2 Enhanced UCL Plus
3-10 CUWL Standard
Recommend to perform before upgrading to CUCM 9.X

or 10.X. BAT export and import can be use. New
assiciation tool is slated for Q4 CY 2014.
ELM/PLM License Substitution
Licenses are based on hierarchical model where lower feature
license can be covered by a higher feature license
CUWL Standard
- I.E. UCL Basic can be covered by UCL Enhance
UCL Enhanced +
- I.E. UCL Enhance can be covered by UCL Enhance Plus
UCL Enhanced
ELM/PLM evaluates ALL system license requirements on a per
UCL Basic product (CUCM, CUC and CER) basis and respond back with one
consistent response to ALL registered systems
UCL - Essential
- VALID: adequate license
User License
Substitution
- INVALID: inadequate license
Centralize and enterprise-wide licensing view per product

License Count Utility (UCT) for CUCM 6.X-8.X
1. Number of public space
2. Pre-upgrade license report or
CUCM 6.X licensing case number
PLM 3. UCSS/ESW contract or SO
number
LCU-License- Migrate License
Report.zip Wizard
CUCM 7.X Pre-Upgrade licensing@cisco.com

License License Report
Count LCU-License-
Utility Report.zip
License
Migration
CUCM 8.X Request
Perform AXL calls to existing CUCM (6.X, 7.X and 8.X) clusters for current license and license
usage and generate pre-upgrade license report
Report can be send to licensing@cisco.com or use with PLM Migrate License wizard
Include number of public space, pre-upgrade license report / license case number / MAC address
and UCSS/ESW or SO number, if send directly to licensing@cisco.com
License Count Utility (LCUZIP-Ver9.1.2.zip):
Opening Licensing Case
Web
https://tools.cisco.com/RUServiceRequestTool/create/launch.do
Type of problem = Licensing
Email
licensing@cisco.com
Phone
1-800-553-2447
Option 3, License Support
License Count Utility (LCUZIP-Ver9.1.2.zip):

Complete Your Online Session Evaluation
Give us your feedback and you
could win fabulous prizes. Winners
announced daily.
Complete your session evaluation
through the Cisco Live mobile app
or visit one of the interactive kiosks
located throughout the convention
center.
Dont forget: Cisco Live sessions will be available

for viewing on-demand after the event at
CiscoLive.com/Online
Continue Your Education
Demos in the Cisco Campus
Walk-in Self-Paced Labs
Table Topics
Meet the Engineer 1:1 meetings

Brkucc 1903

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Brkucc 1903

Загружено:

Авторское право:

Доступные форматы

Migration and Co-Existence Strategy for Unified

Communications (UC) or Collaboration Applications in a

Brandon Ta, Technical Solutions Architect

MCS, HP or IBM Servers

Fabric Extenders I Chassis 1 I I Chassis 2 I

Virtualized Adapters A CNA B A CNA CNA B

B22 M3 B200 M3 B230 M2 B260 M4 B420 M3 B440 M2 B460 M4

C22 M3 C24 M3 C220 M3 C240 M3 C260 M2 C420 M3 C460 M4

UCS-E140S UCS-E140D(P) UCS_E160D(P)

Packaged Tested Reference

UCS 5108 Chassis

Packaged Collaboration Solution Storage Array

T Tested R Reference C Configuration

Rack Mount Based: Rack Mount Based:

More Ease of Deployment Less

Physical Memory Yes, if higher

Quantity, RAID, technology

Limited Any server ANY Server on VMware HCL

Any Storage compatible with Server and VMware

Any adapters compatible with server and VMware

Limited for US DoD only with

Full fledged UCS Manager emulated

CPU Memory NIC Storage

Bare Virtualized Virtualized Design Criteria

CPU vCPU vCPU Calculate due limited vCPU

DRAM vRAM vRAM Not a limiting factor

DAS DAS FC SAN DAS: Not a limiting factor

Restricted performance CPU (CUCMBE 6K)

Restricted performance CPU (CUCMBE 6K)

VM Size Average IOPs Peak IOPs

Collaboration IOPs Requirements:

Collaboration applications and virtualization results

Visual virtual machine(s) placement tool

Manual entry or import from CST

Support almost all of collaboration applications that can be virtualized

Does not checks or provides

are NOT checked by

Guest OS IDLE vCPU

Total collaboration applications vRAM + 4GB for ESXi Total physical

None Co-residency is not supported. No co-residency CWMS. MeetingPlace

* Specific conditions for co-residency TAC Technote Document ID: 113520

CPU Memory NIC Storage

3 Add Server Components

Core Core Core Core

ESX Hypervisor Bare-metal hypervisor in a linux-like operating system. No

vCenter Server Manages multiple ESX/ESXi hosts Yes

Unified Communications VMware Requirements:

Use matching collaboration application OVA file to correct corresponding

RHEL Guest OS 5 (32bit) 6 (64 bit)

Adapter Type Flexible VMXNet3

CUCM 10.0 OVA:

CPU Memory NIC Storage

Server Bare Metal Bare Metal Server Virtualization Virtualization Support

Unified Communications in a Virtualized Environment DocWiki

ESXi to C and B series Firmware Table

ESXi ISO for Cisco UCS Servers

Answer file (platformConfig.xml) USB Virtual floppy

UPS via USB APC UPS via USB UPS on UCS/ESXi

Back up Tape Secure ftp

SMDI Serial port NA

Take these support into consideration and deploy prior to virtualizing

Active Partition inActive Partition

InActive partition Active partition