Planning and Designing Virtual Unified Communications Solutions
BRKUCC-2225

BRKUCC-2225

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

Cisco Public

2

Introduction
Shahzad Ali
Technical Marketing Engineer syali@cisco.com

Laurent Pham
Technical Marketing Engineer lpham@cisco.com

BRKUCC-2225

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

Cisco Public

3

All rights reserved.Housekeeping  Please don't forget to complete session evaluation  Please switch off your mobile phones  Q/A Policy ‒ Questions may be asked during the session ‒ Due to time limit. Cisco Public 4 . flow and respecting every one’s interest. some questions might be deferred towards the end BRKUCC-2225 © 2012 Cisco and/or its affiliates.

Cisco Public 5 .Agenda  Platforms Tested Reference Configurations and Specs-Based Hardware Support  Deployment Models and HA  Sizing  LAN & SAN Best Practices  Migration BRKUCC-2225 © 2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public 6 .Appliance Model with MCS servers Cisco UC Application MCS Server Hardware MCS Server CPU Memory NI C Drive  Server with specific hardware components CPU. network card and hard drive  UC application has dedicated access to hardware components BRKUCC-2225 © 2012 Cisco and/or its affiliates. memory. All rights reserved.

Architectural Shift : Virtualization with VMware
UC App UC App UC App UC App

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

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

Cisco Public

7

MCS appliance vs Virtualized
Virtualized Non Virtualized

BRKUCC-2225

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

Cisco Public

8

Platforms
Tested Reference Configurations and Specs-based

C260 C200 Specs-Based (Subset of UC applications) © 2012 Cisco and/or its affiliates. All rights reserved. B230. B440 1 2 BRKUCC-2225 Tested Reference Configuration (TRC) C210.Platform Options B200. Cisco Public 10 .

All rights reserved.Tested Reference Configurations (TRCs)  Based on specific Hardware Configurations  Tested and documented by Cisco  Performance Guaranteed  For customers who want a packaged solution from Cisco with guaranteed performance BRKUCC-2225 © 2012 Cisco and/or its affiliates. Cisco Public 11 .

drivers. firmware. FEX (2100 or 2200). etc… BRKUCC-2225 © 2012 Cisco and/or its affiliates. Cisco Public 12 . latency) ‒ Configuration settings for BIOS. RAID options (use UCS best practices) ‒ Configuration settings or patch recommendations for VMware (use UCS and VMware best practices) ‒ Configuration settings for QoS parameters.Tested Reference Configurations (TRCs) Configurations not Restricted by TRC  TRC do not restrict: ‒ SAN vendor Any storage vendor could be used as long as the requirements are met (IOPS. upstream switch. All rights reserved. virtual-to-physical network mapping ‒ FI model (6100 or 6200).

FC SAN Storage Array Cisco Public 13 . C260 UCS C210 FCOE UCS 2100/2200 Fabric Extender UCS B-series (B200. B230. B440) UCS 6100/6200 Fabric Interconnect 10GbE FC Catalyst LAN Nexus SAN MDS FC BRKUCC-2225 © 2012 Cisco and/or its affiliates.LAN and SAN options with TRCs UCS 5108 Chassis UCS C200. All rights reserved.

cisco. All rights reserved.com/wiki/Tested_Reference_Configurations_(TRC) 14 . Cisco Public © docwiki: http://docwiki.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 B200 M2 TRC #2 B230 M2 B440 M2 TRC #1 TRC #1 BRKUCC-2225 Details in the2012 Cisco and/or its affiliates.

Details on the latest TRCs Server Model TRC CPU 2 x E7-2870 2. All rights reserved.com/wiki/Tested_Reference_Configurations_(TRC) BRKUCC-2225 © 2012 Cisco and/or its affiliates.4 GHz 20 cores total 4 x E7-4870 2.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 Details in the docwiki: http://docwiki.4 GHz 40 cores total RAM Adapter Storage DAS 16 disks 2 RAID Groups: . Cisco Public 15 .cisco.RAID 5 (8 disks) for UC apps only .4 GHz 20 cores total 2 x E7-2870 2.

Tested Reference Configurations (TRCs) Deviation from TRC Specification Server Model/Generation CPU quantity. HBA. All rights reserved. . type must match exactly B-series: Flexibility with Mezzanine card Cisco Public 16 Adapters BRKUCC-2225 © 2012 Cisco and/or its affiliates. and # cores Physical Memory DAS Off-box Storage Description Must match exactly Must match exactly Must be the same or higher Quantity. technology must match Size and speed might be higher FC only C-series: NIC. model. RAID.

FCoE. HP and IBM hardware on VMware HCL (Dell support not planned) UCS TRC only UCS. CNA.. FCoE. All rights reserved. NFS.com/wiki/Specification-Based_Hardware_Support © 2012 Cisco and/or its affiliates.53+ GHz E7-2800/E7-4800/E7-8800 with speed 2. Cisco Public 17 . iSCSI (NFS and iSCSI requires 10Gbps adapter) Adapter Any adapters on VMware HCL Select HBA & 1GbE NIC only  vCenter required (for logs and statistics) Details in the docwiki: BRKUCC-2225 Any supported and properly sized HBA.g.4+ GHz Limited DAS & FC only Flexible DAS FC. Other DAS configs. VIC http://docwiki.Specifications-Based Hardware Support Benefits  Offers platform flexibility beyond the TRCs Platforms Any Cisco. HP or IBM w/ certain CPUs & specs CPU Any Xeon 5600 or 7500 with speed 2. iSCSI. NFS Storage Any Storage protocols/systems on VMware HCL e. 1Gb/10Gb NIC.cisco.

cisco. 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 Details in the docwiki: http://docwiki. All rights reserved.com/wiki/Specification-Based_Hardware_Support BRKUCC-2225 © 2012 Cisco and/or its affiliates.Specification-Based Hardware Support Important Considerations and Performance  Cisco supports UC applications only. Cisco Public 18 .

All rights reserved.Specification-Based Hardware Support Examples Platforms UCS-SP4-UC-B200 UCSC-C210M2VCD3 UCSC-C200M2SFF 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) Comments Specs-based (CPU mismatch) Specs-based (CPU. RAID controller… mismatch) BRKUCC-2225 © 2012 Cisco and/or its affiliates. Cisco Public . # disks… mismatch) Specs-based (CPU. # disks.

5(1)+ Details in the docwiki: http://docwiki.0(2)+ 8.6(4)+ 8.com/wiki/Unified_Communications_Virtualization_Supported_Applications BRKUCC-2225 © 2012 Cisco and/or its affiliates.0(2)+ 8.0(2)+ 8.6(1)+ 8.Specification-Based Hardware Support UC Applications Support UC Applications Unified CM Unity Connection Unified Presence Contact Center Express Specs-based Xeon 56xx/75xx 8.cisco.5(1)+ Specs-based Xeon E7 8. Cisco Public 20 . All rights reserved.0(2)+ 8.

All rights reserved.VCE and vBlock Support  VCE is the Virtual Computing Environment coalition ‒ Partnership between Cisco. Vblock 700 Components Cisco UCS B-Series EMC VMAX Storage Cisco Nexus 5548 Cisco MDS 9148 Nexus 1000v Cisco Public 21 . infrastructure. storage and support services for rapid deployment 300 Series Vblocks B-Series Large 700 Series Vblocks B-Series Large Small Small Vblock 300 Components Cisco UCS B-Series EMC VNX Unified Storage Cisco Nexus 5548 Cisco MDS 9148 Nexus 1000v BRKUCC-2225 © 2012 Cisco and/or its affiliates. EMC and VMWare to accelerate the move to virtual computing ‒ Provides compute resources.

Cisco Public 22 .Vblock UCS Blade Options BRKUCC-2225 © 2012 Cisco and/or its affiliates. All rights reserved.

with Specs-based BRKUCC-2225 © 2012 Cisco and/or its affiliates. Should I use TRCs? Answer: YES 1. All rights reserved.Quiz 1. I am new to virtualization. Is NFS-based storage supported? Answer: Yes. Cisco Public .

Deployment Models and HA .

Multi Site with Centralized Call Processing. etc.g.5)  NO software checks for design rules ‒ No rules or restrictions are in place in UC Apps to check if you are running the primary and sub on the same blade  Mixed/Hybrid Cluster supported  Services based on USB and Serial Port not supported (e.com/go/ucsrnd BRKUCC-2225 © 2012 Cisco and/or its affiliates. All rights reserved.UC Deployment Models  All UC Deployment Models are supported • No change in the current deployment models • Base deployment model – Single Site. are not changing • Clustering over WAN • Megacluster (from 8. Cisco Public 25 . Live audio MOH using USB) More details in the UC SRND: www.cisco.

primary/subscriber) covers this ‒ VM will be restarted on spare hardware. All rights reserved.VMware Redundancy VMware HA  VMware HA automatically restarts VMs in case of server failure Blade 1 Blade 2 Blade 3 (spare) ‒ Spare unused servers have to be available ‒ Failover must not result in an unsupported deployment model (e. Cisco Public 26 . no vCPU or memory oversubscription) ‒ VMware HA doesn’t provide redundancy in case VM filesystem is corrupted But UC app built-in redundancy (eg. which can take some time Built-in redundancy faster BRKUCC-2225 © 2012 Cisco and/or its affiliates.g.

All rights reserved. manages and test recovery plans ‒ SAN mirroring between sites ‒ VMware HA doesn’t provide redundancy if issues with VM filesystem as opposed to the UC app built-in redundancy  Fault Tolerance (FT) ‒ Not supported at this time ‒ Only works with VMs with 1 vCPU ‒ Costly (a lot of spare hardware required.Other VMware Redundancy Features  Site Recovery Manager (SRM) ‒ Allows replication to another site. Cisco Public 27 . more than with VMware HA) ‒ VMware FT doesn’t provide redundancy if the UC app crashes (both VMs would crash) ‒ Instead of FT. use UC built-in redundancy and VMware HA (or boot VM manually on other server)  Dynamic Resource Scheduler (DRS) ‒ Not supported at this time ‒ No real benefits since Oversubscription is not supported BRKUCC-2225 © 2012 Cisco and/or its affiliates.

Cisco Public 28 . 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 Best Practice: Always perform a DRS Back-Up BRKUCC-2225 © 2012 Cisco and/or its affiliates.Back-Up Strategies 1. All rights reserved.

even with live traffic. Cisco Public 29 . small risk of calls being impacted • “Partial”: in maintenance mode only BRKUCC-2225 © 2012 Cisco and/or its affiliates.vMotion Support UC Applications Unified CM Unity Connection Unified Presence Contact Center Express vMotion Support Yes * Partial Partial Yes * • “Yes *” : vMotion supported. During live traffic. All rights reserved.

With virtualization. All rights reserved. Cisco Public . Can I mix MCS platforms and UCS platforms in the same CUCM cluster? Answer: Yes BRKUCC-2225 © 2012 Cisco and/or its affiliates.Quiz 1. do I still need CUCM backup subscribers? Answer: YES 1.

Sizing .

All rights reserved. template version BRKUCC-2225 © 2012 Cisco and/or its affiliates.0_vmv7_v2. VMware hardware version. vRAM.Virtual Machine Sizing  Virtual Machine virtual hardware defined by an VM template ‒ vCPU. Cisco Public 32 .1.5.ova ‒ CUCM_8.ova ‒ CUCM_8. For example: ‒ CUCM_8. vDisk.6_vmv7_v1.1.ova ‒ Includes product.5_vmv7_v2. product version. vNICs  Capacity • • An VM template is associated with a specific capacity The capacity associated to an template typically matches the one with a MCS server  VM templates are packaged in a OVA file  There are usually different VM template per release.

off-line version also available http://tools.Now.com/cucst BRKUCC-2225 © 2012 Cisco and/or its affiliates. Cisco Public 33 . All rights reserved.cisco.

5 300 agents 100 agents http://docwiki.000 1 x 80 or 1x55GB 1 x 80 2 x 300/500 2 x 146/300/500 Unity Connection 8.com/wiki/Unified_Communications_Virtualization_Downloads_(including_OVA/OVF_Templates) BRKUCC-2225 © 2012 Cisco and/or its affiliates.6 7.500 2.000 1.500 1.6 5. All rights reserved.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 Unified Presence 8.000 vCPU 4 2 1 2 7 4 vRAM (GB) 6 6 4 4 8 6 vDisk (GB) 2 x 80 2 x 80 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.Examples of Supported VM Configurations (OVAs) Product Scale (users) 10.000 10.000 20.6(1) Unified CCX 8.000 5.cisco.000 1. Cisco Public 34 .

For example.500 3.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.750 2.500  The 7.5k OVA (1vCPU) 7. deployment with 40k devices can fit in a single cluster with the 10k-user OVA BRKUCC-2225 © 2012 Cisco and/or its affiliates.CUCM OVA Device Capacity Comparison CUCM OVA 1k OVA (2vCPU) 2. Cisco Public 35 . All rights reserved.5k OVA (2vCPU) 10k OVA (4vCPU) Number of devices “per vCPU” 500 2.

reserve a physical core per server for ESXi Server (dual quad-core) CPU-1 CPU-2 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.Virtual Machine Placement Rules  CPU ‒ The sum of the UC applications vCPUs must not exceed the number of physical core ‒ Additional logical cores with Hyperthreading should NOT be accounted for ‒ Note: With Cisco Unity Connection only. Cisco Public 36 .

Full Full co-residency UC applications in this category can be co-resident with 3rd party applications Co-residency rules are the same for TRCs or Specs-based BRKUCC-2225 © 2012 Cisco and/or its affiliates. vCenter are NOT considered as a UC application 4. None 2.VM Placement – Co-residency Co-residency Types 1. UC with UC only Notes: Nexus 1kv. All rights reserved. Cisco Public 37 . Limited 3.

Cisco Public 38 . If this occurs.com/en/US/products/ps6884/products_tech_note09186a0080bbd913.VM Placement – Co-residency Full Co-residency (with 3rd party VMs)  UC on UCS rules also imposed on 3rd party VMs (e.shtml More info in the docwiki: http://docwiki.com/wiki/Unified_Communications_Virtualization_Sizing_Guidelines#Application_Co-residency_Support_Policy BRKUCC-2225 © 2012 Cisco and/or its affiliates.cisco.cisco. no resource oversubscription)  Cisco cannot guarantee the VMs will never starved for resources.g. All rights reserved. Cisco could require to power off or relocated all 3rd party applications  TAC TechNote: http://www.

cisco.6(2)+: Full 8.0(x): UC with UC only 8.6(1)+: Full 8.6(1): UC with UC only 8.5(x): Full More info in the docwiki: http://docwiki.0(2) to 8. All rights reserved.VM Placement – Co-residency UC Applications Support UC Applications Unified CM Unity Connection Unified Presence Unified Contact Center Express Co-residency Support 8.5: UC with UC only 8. Cisco Public 39 .0(2) to 8.0(2) to 8.com/wiki/Unified_Communications_Virtualization_Sizing_Guidelines BRKUCC-2225 © 2012 Cisco and/or its affiliates.6(1): UC with UC only 8.6(2)+: Full 8.

Cisco Public 40 . All rights reserved.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 Rack Server #2 CPU-1 CPU-2 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 © 2012 Cisco and/or its affiliates.

Cisco Public 41 .VM Placement – Example CUCM VM OVAs Messaging VM OVAs Presence VM OVAs Contact Center VM OVAs “Spare” blades BRKUCC-2225 © 2012 Cisco and/or its affiliates. All rights reserved.

can I install CUCM and vCenter on the same server? Answer: Yes (CUCM full co-residency starting from 8. can I count the additional logical processors? Answer: No 1. Cisco Public .6(2)) BRKUCC-2225 © 2012 Cisco and/or its affiliates. With CUCM 8. With Hyperthreading enabled. All rights reserved. Is oversubscription supported with UC applications? Answer: No 2.Quiz 1.6(2)+.

UC Server Selection .

TRC vs Specs Based Platform Decision Tree TRC Select TRC platform and Size your deployment Start Need HW performance guarantee? 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 1 BRKUCC-2225 © 2012 Cisco and/or its affiliates. Cisco Public 44 . All rights reserved.

Hardware Selection Guide B-series vs C-series B-Series Storage Typical Type of customer Typical Type of deployment Optimum deployment size Optimum geographic spread Cost of entry Costs at scale SAN Only DC-centric DC-centric Typically UC + other biz apps/VXI C-Series SAN or DAS UC-centric Not ready for blades or shared storage. Lower operational readiness for virtualization. Cisco Public 45 . All rights reserved. UC-centric Typically UC only Bigger Centralized Higher Lower Smaller Distributed or Centralized Lower Higher 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 © 2012 Cisco and/or its affiliates.

C260.Hardware Selection Guide Suggestion for New Deployment >~96 ~24<vCPU<=~96 B230. BE6K or eq DAS BRKUCC-2225 © 2012 Cisco and/or its affiliates. All rights reserved. B440 or eq C210. B440 or eq B200. B230. Cisco Public 46 . C260 or eq C210 or eq How many vCPU are needed? 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 C210 or eq C200.

LAN & SAN Best Practices .

Cisco Public 48 . LAN on Motherboard) 1 PCI express card with four additional Gigabit Ethernet ports  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 © 2012 Cisco and/or its affiliates.Cisco UCS C210/C260 Networking Ports Best Practices CIMC MGMT VM Traffic ESXi Management  Tested Reference Configurations (TRC) for the C210/C260 have: • • 2 built-in Gigabit Ethernet ports (LOM. All rights reserved.

Cisco Public 49 . All rights reserved.VMware NIC Teaming for C-series No Port Channel All ports active Active Ports with Standby Ports No EtherChannel No EtherChannel No EtherChannel No EtherChannel vmnic0 vmnic1 vmnic2 vmnic3 vmnic0 vmnic1 vmnic2 vmnic3 “Virtual Port ID” or “MAC hash” ESXi HOST “Virtual Port ID” or “MAC hash” vNIC 1 ESXi HOST vNIC 2 BRKUCC-2225 © 2012 Cisco and/or its affiliates.

vmware.com/application/pdf/en/us/guest/netsol/ns304/c649/ccmigration_09186a00807a15d0.cisco.com/selfservice/microsites/search.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/white_paper_c11-623265. 50 .pdf http://www.do?language=en_US&cmd=displayKC&externalId=1004048 http://www. All rights reserved.html Cisco Public BRKUCC-2225 © 2012 Cisco and/or its affiliates.VMware NIC Teaming for C-series Port Channel Single virtual Port Channel (vPC) Virtual Switching System (VSS) / virtual Port Channel (vPC) / cross-stack required Two Port Channel (no vPC) VSS/vPC not required but… No physical switch redundancy since most UC applications have only one vNIC EtherChannel EtherChannel vPC Peerlink vmnic0 vmnic1 vmnic2 vmnic3 vmnic0 vmnic1 vmnic2 vmnic3 vSwitch vSwitch1 vNIC 1 vSwitch2 vNIC 2 “Route based on IP hash” http://kb.

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. All rights reserved.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 © 2012 Cisco and/or its affiliates. high priority packets (e.UC applications QoS with Cisco UCS B-series Congestion scenario L2:3 L3:CS3 LAN  With UCS. Cisco Public .

All rights reserved. Cisco Public .UC applications QoS with Cisco UCS B-series Best Practice: Nexus 1000v  Nexus 1000v can map DSCP to CoS LAN  UCS can prioritize based on CoS  Best practice: Nexus 1000v for end-toend QoS 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 © 2012 Cisco and/or its affiliates.

UC applications QoS with Cisco UCS B-series Cisco VIC  All traffic from a VM have the same CoS value  Nexus 1000v is still the preferred solution for end-toend QoS vNIC2 Cisco VIC CoS 0 1 2 3 4 5 6 vHBA vmnic0 vmnic1 vmnic2 vmnic3 vSwitch or vDS FC MGMT vMotion vNIC1 Voice Signaling Other BRKUCC-2225 © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public .

g 450 GB 15K. 300 GB 15K) ~ 180 IOPS Must never be greater than 2 TB UC VM App Per LUN LUN Size Recommendation PUB SUB1 UCCX1 Between 4 & 8 (different UC apps require different space requirement based on OVA Between 500 GB & 1.4 TB Usable Space) HD 1 450gig 15K RPM BRKUCC-2225 HD 2 450gig 15K RPM HD 3 450gig 15K RPM HD 4 450gig 15K RPM Cisco Public HD 5 450gig 15K RPM 54 © 2012 Cisco and/or its affiliates.SAN Array LUN Best Practices / Guidelines HDD Recommendation LUN Size Restriction FC class (e. All rights reserved.5 TB CUP1 SUB2 SUB3 UCCX2 CUP2 VM1 VM2 VM3 VM4 VM1 VM2 VM3 VM4 LUN 1 (720 GB) LUN 2 (720 GB) Single RAID5 Group (1. .

Cisco Public 55 .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.

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. Cisco Public 56 .Tiered Storage Best Practice Storage Pool FLASH FLASH FLASH FLASH FLASH 95% of IOPS 5% of capacity NL-SAS NL-SAS NL-SAS NL-SAS NL-SAS NL-SAS NL-SAS NL-SAS NL-SAS NL-SAS SSD Cache FLASH FLASH FLASH FLASH FLASH Active Data from NL-SAS Tier  Use NL-SAS drives (2 TB. All rights reserved. 7.

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 With VNX – Tiered Storage 200GB Flash 2TB NL-SAS Flash R 5 4+1 NL-SAS R 5 4+1 NL-SAS R 5 4+1 Flash R 5 4+1 NL-SAS R 5 4+1 Flash R 5 4+1 NL-SAS R 5 4+1 NL-SAS R 5 4+1 125 disks 70% drop in disk count 40 disks Optimal Performance Lowest Cost 57 BRKUCC-2225 © 2012 Cisco and/or its affiliates. Cisco Public . All rights reserved.

Storage Network Latency Guidelines  Kernel Command Latency ‒ time vmkernel took to process SCSI command < 2-3 msec  Physical Device Command Latency ‒time physical storage devices took to complete SCSI command < 15-20 msec Kernel disk command latency found here BRKUCC-2225 © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 58 .

Cisco Public 59 .cisco.com/wiki/Storage_System_Performance_Specifications BRKUCC-2225 © 2012 Cisco and/or its affiliates. All rights reserved.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.

Migration and Upgrade .

CUC. Install using the same UC release.cisco.0(2)+ required with CUCM. Cisco Public 61 .Migration to UCS Overview 2 steps 1. All rights reserved. DRS restore) 1 Upgrade 2 Hardware Migration Replacing a Single Server or Cluster for Cisco Unified Communications Manager: http://www. CUP) 2. Upgrade Perform upgrade if current release does not support Virtualization (for example. 8.html BRKUCC-2225 © 2012 Cisco and/or its affiliates. Hardware migration Follow the Hardware Replacement procedure (DRS backup.com/en/US/docs/voice_ip_comm/cucm/install/8_6_1/cluster/clstr861.

downtime during migration  Example: MCS-7845H3. e. but the UC application will be shut down after the upgrade.0.4 with CUCM 8. then have to use temporary hardware for intermediate upgrade For more info. Therefore. Cisco Public 62 . the old hardware can be used for the upgrade. MCS-7845H2.(2)-8.0(2).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.0/MCS-7845H1: Bridge Upgrade to CUCM 8. Only possible operation after the upgrade is DRS backup. All rights reserved.g.com/go/swonly 2 Hardware Migration  Note: Very Old MCS hardware may not support Bridged Upgrade.cisco. refer to BRKUCC-1903: Migration and Co-Existence Strategy for UC or Collaboration Applications on UCS BRKUCC-2225 © 2012 Cisco and/or its affiliates.6(x) www.

cisco.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  Best Practices for Networking and Storage Docwiki www.com/go/uc-virtualized BRKUCC-2225 © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 63 .

 Complete your session evaluation online now (open a browser through our wireless network to access our portal) or visit one of the Internet stations throughout the Convention Center. and on-demand and live activities throughout the year.  Receive 20 Passport points for each session evaluation you complete. Don’t forget to activate your Cisco Live Virtual account for access to all session material.com. Cisco Public 64 BRKUCC-2225 © 2012 Cisco and/or its affiliates. Activate your account at the Cisco booth in the World of Solutions or visit www. .Complete Your Online Session Evaluation  Give us your feedback and you could win fabulous prizes. communities.ciscolive. All rights reserved. Winners announced daily.

Cisco Public 65 .Final Thoughts  Get hands-on experience with the Walk-in Labs located in World of Solutions. and more!  Follow Cisco Live! using social media: ‒ Facebook: https://www. All rights reserved.com after the event for updated PDFs.in/CiscoLI BRKUCC-2225 © 2012 Cisco and/or its affiliates.facebook.com/#!/CiscoLive ‒ LinkedIn Group: http://linkd.ciscoLive365.com/ciscoliveus ‒ Twitter: https://twitter. ondemand session videos. booth 1042  Come see demos of many key solutions and products in the main Cisco booth 2924  Visit www. networking.

Cisco Public .BRKUCC-2225 © 2012 Cisco and/or its affiliates. All rights reserved.

No ESXi 5.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. 2 vCPUs.  ESXi 4. No co-residency  Cisco TelePresence Video Communication Server (VCS)  Release x7.1 only. Cisco Public . 6 GB RAM. C210M2 and B200M2 BRKUCC-2225 © 2012 Cisco and/or its affiliates.0 support  C200M2.1 or later.Cisco TelePresence Virtualization  Cisco TelePresence Manager (CTS Manager) and Cisco TelePresence Multipoint Switch (CTMS)  Release 1. OVA includes application.0 or later. CTS Manager or CTMS  Release 1. All rights reserved.8 supports virtualization on C210M2 with no co-residency support with CUCM. 2 vDisks (4GB+128GB).