Professional Documents
Culture Documents
BRKUCC-2225
BRKUCC-2225
Cisco Public
Introduction
Shahzad Ali
Technical Marketing Engineer syali@cisco.com
Laurent Pham
Technical Marketing Engineer lpham@cisco.com
BRKUCC-2225
Cisco Public
Housekeeping
Please don't forget to complete session evaluation
BRKUCC-2225
Cisco Public
Agenda
Platforms
Tested Reference Configurations and Specs-Based Hardware Support
Deployment Models and HA Sizing LAN & SAN Best Practices Migration
BRKUCC-2225
Cisco Public
MCS Server
CPU
Memory
NI C
Drive
BRKUCC-2225
Cisco Public
ESXi Hypervisor
UCS Hardware
CPU
Memory
NIC
Storage
UCS with specific hardware components CPU, memory, network card and storage VMware ESXi 4.x or 5.0 running on top of dedicated UCS server UC application running as a virtual machine (VM) on ESXi hypervisor UC application has shared access to hardware components
BRKUCC-2225
Cisco Public
BRKUCC-2225
Cisco Public
Platforms
Tested Reference Configurations and Specs-based
Platform Options
B200, B230, B440
1 2
BRKUCC-2225
Specs-Based
(Subset of UC applications)
Cisco Public
10
BRKUCC-2225
Cisco Public
11
BRKUCC-2225
Cisco Public
12
UCS C210
FCOE
UCS 2100/2200 Fabric Extender
10GbE
FC
Catalyst
LAN
Nexus
SAN
MDS
FC
BRKUCC-2225
Cisco Public
13
TRCs
Server Model
C200 M2
TRC
TRC #1 TRC #1
CPU
2 x E5506 (4 cores/socket) 2 x E5640 (4 cores/socket) 2 x E5640 (4 cores/socket) 2 x E5640 (4 cores/socket) 2 x E7-2870 (10 cores/socket) 2 x E5640 (4 cores/socket) 2 x E5640 (4 cores/socket) 2 x E7-2870 (10 cores/socket) 4 x E7-4870 (10 cores/socket)
RAM
24 GB 48 GB 48 GB 48 GB 128 GB 48 GB 48 GB 128 GB 256 GB
ESXi Storage
DAS DAS DAS FC SAN DAS DAS FC SAN FC SAN FC SAN
VMs Storage
DAS DAS FC SAN FC SAN DAS FC SAN FC SAN FC SAN FC SAN
C210 M2
TRC #2 TRC #3
C260 M2
TRC #1 TRC #1
BRKUCC-2225
Details in the2012 Cisco and/or its affiliates. All rights reserved. Cisco Public docwiki: http://docwiki.cisco.com/wiki/Tested_Reference_Configurations_(TRC)
14
RAM
Adapter
Storage
DAS 16 disks 2 RAID Groups: - RAID 5 (8 disks) for UC apps only - RAID 5 (8 disks for UC apps and ESXi) FC SAN
C260 M2
TRC #1
128 GB
Cisco VIC
B230 M2
TRC #1
128 GB
Cisco VIC
B440 M2
TRC #1
256 GB
Cisco VIC
FC SAN
Specification Server Model/Generation CPU quantity, model, and # cores Physical Memory
DAS Off-box Storage
Adapters
BRKUCC-2225
CPU
Any Xeon 5600 or 7500 with speed 2.53+ GHz E7-2800/E7-4800/E7-8800 with speed 2.4+ GHz
Limited DAS & FC only
Storage
Any Storage protocols/systems on VMware HCL e.g. Other DAS configs, FCoE, NFS, iSCSI (NFS and iSCSI requires 10Gbps adapter)
Adapter
Any adapters on VMware HCL
Any supported and properly sized HBA, 1Gb/10Gb NIC, CNA., VIC
Cisco Public
17
Cisco supports UC applications only, not performance of the platform Cisco cannot provide performance numbers Use TRC for guidance when building a Specs-based solution Cisco is not responsible for performance problems when the problem can be resolved for example by migrating or powering off some of the other VMs on the server or by using a faster hardware Customers who needs some guidance on their hardware performance or configuration should not use Specs-based
Specifications CPU: 2 x X5650 (6 cores/socket) CPU: 2 x X5650 (6 cores/socket) DAS (16 drives) CPU: 2 x E5649 (6 cores/socket) DAS (8 drives)
BRKUCC-2225
Cisco Public
Small
Small
BRKUCC-2225
Cisco Public
22
Quiz
BRKUCC-2225
Cisco Public
UC Deployment Models
All UC Deployment Models are supported
No change in the current deployment models Base deployment model Single Site, Multi Site with Centralized Call Processing, etc. are not changing Clustering over WAN Megacluster (from 8.5)
Mixed/Hybrid Cluster supported Services based on USB and Serial Port not supported (e.g. Live audio MOH using USB)
More details in the UC SRND: www.cisco.com/go/ucsrnd
BRKUCC-2225 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 25
VMware Redundancy
VMware HA
Blade 3 (spare)
Spare unused servers have to be available Failover must not result in an unsupported deployment model (e.g. no vCPU or memory oversubscription) VMware HA doesnt provide redundancy in case VM filesystem is corrupted But UC app built-in redundancy (eg. primary/subscriber) covers this VM will be restarted on spare hardware, which can take some time Built-in redundancy faster
BRKUCC-2225 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 26
BRKUCC-2225
Cisco Public
27
Back-Up Strategies
1. UC application built-in Back-Up Utility
Disaster Recovery System (DRS) for most UC applications
Backup can be performed while UC application is running Small storage footprint
2. Full VM Backup
VM copy is supported for some UC applications, but the UC applications has to be shut down Could also use VMware Data Recovery (vDR) but the UC application has to be shut down Requires more storage than Disaster Recovery System Fast to restore
vMotion Support
UC Applications
Unified CM Unity Connection Unified Presence Contact Center Express
vMotion Support
Yes * Partial Partial Yes *
Yes * : vMotion supported, even with live traffic. During live traffic, small risk of calls being impacted Partial: in maintenance mode only
BRKUCC-2225
Cisco Public
29
Quiz
1. Can I mix MCS platforms and UCS platforms in the same CUCM cluster?
Answer: Yes
BRKUCC-2225
Cisco Public
Sizing
Capacity
An VM template is associated with a specific capacity The capacity associated to an template typically matches the one with a MCS server
CUCM_8.6_vmv7_v1.5.ova
BRKUCC-2225
Cisco Public
32
http://tools.cisco.com/cucst
BRKUCC-2225 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 33
Notes
Not for C200/BE6k Not for C200/BE6k Not for C200/BE6k For C200/BE6k only Not for C200/BE6k Not for C200/BE6k
Unified CM 8.6
5,000
1,000 5,000 1,000 400 agents
2
1 4 1 4 2 2
6
4 6 2 8 4 4
1 x 200
1 x 160 2 x80 1 x 80 2 x 146 2 x 146 1 x 146
Supports C200/BE6k
Supports C200/BE6k Not for C200/BE6k Supports C200/BE6k Not for C200/BE6k Not for C200/BE6k Supports C200/BE6k
http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_(including_OVA/OVF_Templates)
BRKUCC-2225 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 34
CUCM OVA
Device Capacity Comparison
CUCM OVA 1k OVA (2vCPU) 2.5k OVA (1vCPU) 7.5k OVA (2vCPU) 10k OVA (4vCPU) Number of devices per vCPU 500 2,500 3,750 2,500
The 7.5k-user OVA provides support for the highest number of devices per vCPU The 10k-user OVA useful for large deployment when minimizing the number of nodes is critical. For example, deployment with 40k devices can fit in a single cluster with the 10k-user OVA
BRKUCC-2225 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 35
With Hyperthreading
Memory
The sum of the UC applications RAM (plus 2GB for ESXi) must not exceed the total physical memory of the server
Core 1
Core 2
Core 3
ESXi CUC
SUB1
CCX
CUP
CUC
Core 4
Core 1
Core 2
Core 3
Core 4
Storage
The storage from all vDisks must not exceed the physical disk space BRKUCC-2225 2012 Cisco and/or its affiliates. All rights reserved.
Cisco Public 36
VM Placement Co-residency
Co-residency Types
1. None
2. Limited
3. UC with UC only
Notes: Nexus 1kv, vCenter are NOT considered as a UC application
4. Full
Full co-residency UC applications in this category can be co-resident with 3rd party applications
VM Placement Co-residency
Full Co-residency (with 3rd party VMs)
UC on UCS rules also imposed on 3rd party VMs (e.g. no resource oversubscription) Cisco cannot guarantee the VMs will never starved for resources. If this occurs, Cisco could require to power off or relocated all 3rd party applications
TAC TechNote:
http://www.cisco.com/en/US/products/ps6884/products_tech_note09186a0080bbd913.shtml
VM Placement Co-residency
UC Applications Support
UC Applications
Unified CM Unity Connection Unified Presence Unified Contact Center Express
Co-residency Support
8.0(2) to 8.6(1): UC with UC only 8.6(2)+: Full 8.0(2) to 8.6(1): UC with UC only 8.6(2)+: Full 8.0(2) to 8.5: UC with UC only 8.6(1)+: Full 8.0(x): UC with UC only 8.5(x): Full
VM Placement
Best Practices
Distribute UC application nodes across UCS blades, chassis and sites to minimize failure impact On same blade, mix Subscribers with TFTP/MoH instead of only Subscribers Rack Server #1
CPU-1 CPU-2 ESXi CUC
SUB1
CUP-1
CUC
(Active)
Core 1
Core 2
Core 3
Core 4
Core 1
Core 2
Core 3
Core 4
SUB2
ESXi CUC
CUP-2
CUC
(Standby)
Core 1
Core 2
Core 3
Core 4
Core 1
Core 2
Core 3
Core 4
BRKUCC-2225
Cisco Public
40
VM Placement Example
CUCM VM OVAs Messaging VM OVAs
Presence VM OVAs Contact Center VM OVAs
Spare blades
BRKUCC-2225
Cisco Public
41
Quiz
1. Is oversubscription supported with UC applications?
Answer: No
1. With CUCM 8.6(2)+, can I install CUCM and vCenter on the same server?
Answer: Yes (CUCM full co-residency starting from 8.6(2))
BRKUCC-2225
Cisco Public
UC Server Selection
Start
YES
NO
Expertise in VMware / Virtualization
NO
NO YES
Specs-based supported by UC apps?
Specs-Based
YES
Select hardware and Size your deployment using TRC as a reference
BRKUCC-2225
Cisco Public
44
UC-centric
Typically UC only
Partner Requirements
Vblock Available? What HW does TRC cover?
Higher
Yes Just the blade
Not UCS 2100/5100/6x00
Lower
Not currently Whole box
Compute+Network+Storage
BRKUCC-2225
Cisco Public
45
B230, B440 or eq
B200, C260, B230, B440 or eq C210, C260 or eq C210 or eq
Yes
Already have or planned to build a SAN
~16<vCPU<=~24
<=~16
SAN
>~16 No
Start <1k users and < 8 vCPU? Yes No How many vCPU are needed?
C260 or eq
<=~16
DAS
BRKUCC-2225
Cisco Public
46
CIMC
MGMT
VM Traffic
ESXi Management
Best Practice
Use 2 GE ports from the Motherboard and 2 GE ports from the PCIe card for the VM traffic. Configure them with NIC teaming. Use 2 GE ports from the PCIe card for ESXi Management
BRKUCC-2225
Cisco Public
48
No EtherChannel
No EtherChannel
No EtherChannel
No EtherChannel
vmnic0
vmnic1
vmnic2
vmnic3
vmnic0
vmnic1
vmnic2
vmnic3
ESXi HOST
vNIC 2
BRKUCC-2225
Cisco Public
49
vPC Peerlink
vmnic0
vmnic1
vmnic2
vmnic3
vmnic0
vmnic1
vmnic2
vmnic3
vSwitch
vSwitch1
vNIC 1
vSwitch2
vNIC 2
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004048 http://www.cisco.com/application/pdf/en/us/guest/netsol/ns304/c649/ccmigration_09186a00807a15d0.pdf http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/white_paper_c11-623265.html Cisco Public BRKUCC-2225 2012 Cisco and/or its affiliates. All rights reserved.
50
LAN
With UCS, QoS done at layer 2 Layer 3 markings (DSCP) not examined nor mapped to Layer 2 markings (CoS) If there is congestion between the ESXi host and the physical switch, high priority packets (e.g CS3 or EF) are not prioritized over lower priority packets
L2:0
L2:0
L3:CS3
Possible Congestion
UCS FI
Possible Congestion
FEX A
L3:CS3
vHBA 1
Possible Congestion
VIC
vHBA 2 vmnic 1 vmnic2
vSwitch or vDS
vNIC 1 vNIC 2 vNIC 3 vNIC 4
BRKUCC-2225
Cisco Public
L2:3
L3:CS3
UCS FI
FEX A
L2:3 L3:CS3
vHBA 1
VIC
vHBA 2 vmnic 1 vmnic2
Nexus 1000v
vNIC 1 vNIC 2 vNIC 3 vNIC 4
BRKUCC-2225
Cisco Public
vMotion
vNIC1
Voice
Signaling
Other
BRKUCC-2225
Cisco Public
Between 4 & 8 (different UC apps require different space requirement based on OVA
Between 500 GB & 1.5 TB CUP1 SUB2 SUB3 UCCX2 CUP2
VM1
VM2
VM3
VM4
VM1
VM2
VM3
VM4
Tiered Storage
Overview
Tiered Storage
Definition: Assignment of different categories of data to different types of storage media to increase performance and reduce cost EMC FAST (Fully Automated Storage Tiering): Continuously monitors and identifies the activity level of data blocks in the virtual disk Automatically moves active data to SSDs and cold data to high capacity lower-cost tier
Highest Performance Highest Capacity
SSD cache
Continuously ensures that the hottest data is served from high-performance Flash SSD
BRKUCC-2225 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 55
Tiered Storage
Best Practice Storage Pool
FLASH FLASH FLASH FLASH FLASH
NL-SAS
NL-SAS
NL-SAS
NL-SAS
NL-SAS
NL-SAS
NL-SAS
SSD Cache
FLASH FLASH FLASH FLASH FLASH
Use NL-SAS drives (2 TB, 7.2k RPM) for capacity and SSD drives (200 GB) for performance
RAID 5 (4+1) for SSD drives and NL-SAS drives
BRKUCC-2225 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 56
Tiered Storage
Efficiency
Traditional Single Tier 300GB SAS
SAS R 5 4+1 SAS R 5 4+1 SAS R 5 4+1 SAS R 5 4+1 SAS R 5 4+1 SAS R 5 4+1 SAS R 5 4+1 SAS R 5 4+1 SAS R 5 4+1 SAS R 5 4+1
SAS R 5 4+1 SAS R 5 4+1 SAS R 5 4+1 SAS R 5 4+1 SAS R 5 4+1
SAS R 5 4+1 SAS R 5 4+1 SAS R 5 4+1 SAS R 5 4+1 SAS R 5 4+1
SAS R 5 4+1 SAS R 5 4+1 SAS R 5 4+1 SAS R 5 4+1 SAS R 5 4+1
125 disks
40 disks
Optimal Performance Lowest Cost
57
BRKUCC-2225
Cisco Public
BRKUCC-2225
Cisco Public
58
IOPS Guidelines
Unified CM BHCA 10K 25K 50K Unity Connection IOPS Type IOPS ~35 ~50 ~100 2 vCPU 4 vCPU
CUCM upgrades generate 800 to 1200 IOPS in addition to steady state IOPS
Avg per VM
Peak spike per VM Unified CCX IOPS Type Avg per VM Peak spike per VM
More details in the docwiki:
~130
~720 2 vCPU ~150 ~1500
~220
~870
http://docwiki.cisco.com/wiki/Storage_System_Performance_Specifications
BRKUCC-2225 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 59
Migration to UCS
Overview
2 steps
1. Upgrade Perform upgrade if current release does not support Virtualization (for example, 8.0(2)+ required with CUCM, CUC, CUP) 2. Hardware migration Follow the Hardware Replacement procedure (DRS backup, Install using the same UC release, DRS restore)
1
Upgrade
Hardware Migration
Migration to UCS
Bridge Upgrade
Bridge upgrade for old MCS hardware which might not support a UC release supported for Virtualization
1
Bridge Upgrade
With Bridge Upgrade, the old hardware can be used for the upgrade, but the UC application will be shut down after the upgrade. Only possible operation after the upgrade is DRS backup. Therefore, downtime during migration
Example:
MCS-7845H3.0/MCS-7845H1: Bridge Upgrade to CUCM 8.0.(2)-8.6(x) www.cisco.com/go/swonly
Hardware Migration
Note: Very Old MCS hardware may not support Bridged Upgrade, e.g. MCS-7845H2.4 with CUCM 8.0(2), then have to use temporary hardware for intermediate upgrade
For more info, refer to BRKUCC-1903: Migration and Co-Existence Strategy for UC or Collaboration Applications on UCS
BRKUCC-2225 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 62
Key Takeaways
Difference between TRC and Specs-based
Same Deployment Models and UC application level HA Added functionalities with VMware
Sizing
Size and number of VMs Placement on UCS server
www.cisco.com/go/uc-virtualized
BRKUCC-2225
Cisco Public
63
Dont forget to activate your Cisco Live Virtual account for access to all session material, communities, and on-demand and live activities throughout the year. Activate your account at the Cisco booth in the World of Solutions or visit www.ciscolive.com.
Cisco Public 64
BRKUCC-2225
Final Thoughts
Get hands-on experience with the Walk-in Labs located in World of Solutions, booth 1042 Come see demos of many key solutions and products in the main Cisco booth 2924 Visit www.ciscoLive365.com after the event for updated PDFs, ondemand session videos, networking, and more! Follow Cisco Live! using social media:
Facebook: https://www.facebook.com/ciscoliveus Twitter: https://twitter.com/#!/CiscoLive LinkedIn Group: http://linkd.in/CiscoLI
BRKUCC-2225
Cisco Public
65
BRKUCC-2225
Cisco Public
Release 1.8 supports virtualization on C210M2 with no co-residency support with CUCM, CTS Manager or CTMS
Release 1.9 supports B series blade with co-residency support between CTS Manager and CTMS for up to 50 endpoints Cisco TelePresence Management Suite (TMS) Release 13.0 or later. No co-residency Cisco TelePresence Video Communication Server (VCS) Release x7.1 or later. OVA includes application. 2 vCPUs, 6 GB RAM, 2 vDisks (4GB+128GB). ESXi 4.1 only. No ESXi 5.0 support