Planning and Designing a Virtual Unified Communication Solution

Transcription

1

2 Planning and Designing a Virtual Unified Communication Solution Laurent Pham Technical Marketing Engineer

3 Cisco Collaboration Design Traditional Deployments New Deployments Cisco Collaboration Release 10 virtual only MCS End-of-Sale

4 AGENDA Overview Platform Options How to Design Other Design Considerations How to Deploy Laurent Pham Technical Marketing Engineer

5 Server Virtualization Traditional Architecture Virtual Architecture

6 Moving towards Virtualization With MCS servers Virtualization

7 Virtualization Overview and Definitions Guest - Cisco Collaboration application VM Hypervisor - VMware vsphere ESXi Host - Physical server Definition Support Guest Virtual Machine Cisco Collaboration application release 8.0(2)+ in general Hypervisor Software allowing to run VMs on a host VMware vsphere ESXi only. Release 4.0, 4.1, 5.0, 5.1, or 5.5 Host Physical Server Cisco UCS or other VMware compatible servers

8 OVA Open Virtualization Archive OVA Application OVA VMFS Storage Application VMFS Storage Block Block Block Chunk Block Block Block Chunk Block Block Block Block Chunk Block Block Chunk Partition Alignment OVA (Open Virtualization Archive) Definition Support File containing VM configuration (e.g. virtual hardware) OVAs must be used when installing a VM. Ensure proper VM configuration and application partition alignment

9 DocWiki : Main Reference for UC Virtualization for n ide zatio u i G al irtu V UC Covers all aspects of Cisco Collaboration Virtualization (Collaboration applications, VMware and platform support for UC virtualization) Frequent changes with new updates check back often

10 AGENDA Overview Hardware Options How to Design Other Design Considerations How to Deploy

11 Hardware Options Tested Reference Configuration (TRC) Business Edition 6000/7000 Specs-Based UC on UCS UC on UCS UC on 3rd party servers Any vendor

12 Cisco UCS Architecture Overview with TRCs Business Edition 6000/7000 UCS C-series TRCs (C220, C240, C260) UCS B-series TRCs (B200, B230, B440) UCS 6200 Fabric Interconnect FC Catalyst FC Gb be 10 1G E oe UCS 2200 Fabric Extender Nexus MDS LAN SAN Fiber Channel Storage Array UCS 5108 Chassis

13 TRC Servers Full Performance Restricted Performance VM VM VM VM VM VM VM VM VM VM VM VM BE6000 VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM BE7000 VM VM VM VM VM 2X-Large TRC*, 40c Extra-Large TRCs*, 20c # Apps * VM VM VM VM VM BE 6000 HD Server Small Plus TRC,16c Large TRCs*, 16c Medium TRC*, 12c Legend 8c: 8 cores VM VM VM VM VM VM VM VM VM BE 6000 MD Server Small TRC, 8c *VM counts are averages/examples only and vary by design. Medium TRC*, 8c #Users <1K users ( K devices) 1K-5K users (<15K devices) >5K users (>15K devices)

14 TRC Allowed Allowed Deviations deviations Component Server Model/Generation CPU Modifications Allowed? Model Within the same family Quantity and # cores Speed Yes, if higher Yes, if higher Yes, if higher Yes, if higher Physical Memory DAS Storage Quantity, RAID, technology Disk speed and size C-series (NIC Type, vendor, technology) Adapters C-series (NIC card quantity) B-series (Mezzanine card)

15 Specs-Based Flexibility Tested Reference Configuration (TRC) Business Edition 6000 Business Edition 7000 Specs-Based UC on UCS UC on UCS 3rd-Party Any Server Less More Choices Existing Investment Leverage More Assurance Simplicity Less I know what I m doing Tell me what to do TAC Notes

16 Specs-Based - Requirements TRC Specs-Based Limited Cisco UCS servers Limited CPUs ANY Server (VMware compatible) Any server More CPUs options UCS C: Limited DAS options UCS B: FC SAN only Flexible DAS & SAN Xeon 5600 or GHz E5-2400/2600/4600 v1/v GHz (Restricted Performance) E5-2600/4600 v1/v GHz E7-2800/4800/ GHz (Restricted Performance) E7-2800/4800/ GHz Any Storage compatible with Server and VMware E.g. Flexible DAS config, FC, FCoE, iscsi, NFS NAS Any adapters compatible with server and VMware UCS C: Limited Options UCS B: Flexible Adapters Optional Flexible adapters Required vcenter required (for historical logs and statistics)

17 AGENDA Overview Hardware Options How To Design Other Design Considerations How To Deploy

18 How to Design - Overview 1 Application Design Overall Application Design Application Sizing 2 tuali r i V h t wi New VM Placement zation

19 Application Design 1 Application Design Overall Application Design - Architecture and Deployment Models - High Availability Design CS ith M w s a Same th Application Sizing - VM Configuration Selection - Determine Number of VMs Required s wi a e m st sa Almo MCS esign d d e i lif Simp BE6000 with Resources - Solution Reference Network Design (SRND): - Cisco Preferred Architecture: - Cisco Validated Design CVD: - Docwiki: - Cisco Collaboration Sizing Tool:

20 How to Select a VM Configuration Application Select Appropriate VM Config Consider: # users and # vcpu Unified CM 10.0 VM Config compatible with Hardware? No Change VM Config or Platform Yes IM & Presence 10.0 Unity Connection VM Config vcpu Restricted UC Performance CPU: BE6000, Small(+) TRC Full UC Performance CPU: BE7000, Medium TRC or larger 10, , , , , , , ,000 full UC 1 20, , , ,000 1 Docwiki:

21 How to Determine the Number of VMs Required Estimate Sizing Validate Sizing for complex deployment Design Guides - SRND Collaboration Sizing Tool (CST) 00 BE60 r o f ST No C Cisco Collaboration Sizing Tool (CST) available to Partners, Cisco Account Teams, and Cisco Advanced Services

22 VM Placement 2 VM Placement Goal: Determine the number of physical servers required How to do VM Placement? - Manual placement using the rules in the docwiki - Use VM Placement Tool (VMPT) Resources - Docwiki: - VM Placement Tool (VMPT): tuali r i V h t wi New zation

23 CPU Resources Physical Core Dual sockets, 6 cores per socket Core 1 Core 2 Core 1 Core 2 Core 3 Core 4 Core 3 Core 4 Core 5 Core 6 Core 5 Core 6 Consider the number of PHYSICAL cores on the server CPU Cores Do not consider the number of LOGICAL cores obtained through Hyperthreading Logical Processors

24 CPU Resources - Mapping Mapping: One vcpu = One physical core No oversubscription: The number of vcpus can t exceed the number of physical cores vcpu UCM-PUB UCM-SUB1 IM&P-1 Cores CER-1 CCX-1

25 CPU Resources Unity Connection With Unity Connection only: Reserve a spare core for the ESXi scheduler

26 Other Hardware Resources Memory No Oversubscription Reserve RAM for ESXi scheduler ESXi 5.1 or earlier: 2 GB ESXi 5.5: 4 GB Storage Ensure enough storage space is available Thick vs. Thin provisioning TRC with DAS: Thick provisioning required Specs-Based or SAN: Thick provisioning recommended, Thin provisioning allowed

27 Co-Residency: Mixing Applications Limited (includes no co-residency) Specific Cisco UC Specific Cisco UC Examples: CWMS CCE Logger 8.x UC with UC Only Cisco UC Cisco UC Examples: CUCM 8.6(1)IM&P 8.5(x)CUC 8.5(1)CCX 8.0 CCE Logger 9.x Full Cisco UC+ Non-UC/3rd party Cisco UC Examples: CUCM 8.6(2)+ IM&P 8.6(1)+ CUC 8.6(2)+ CCX 8.5+ CCE 10+ 3rd Party/Non-UC (e.g. Nexus 1000v, vcenter)

28 Co-residency with 3rd party applications UC on UCS rules also imposed on 3rd party VMs (e.g. no Oversubscription allowed for 3rd party apps) The co-residency rules and categories apply to TRC and Specs-Based Number and Type of 3rd party co-resident applications limited with Cisco Collaboration virtualization SW OEMs (Cisco UC Virt. Hypervisor/Foundation, default ship with BE6000/BE7000) TAC TechNote: More info in the docwiki:

29 VM Placement Tool Visual VM placement tool Greatly simplifies VM Placement Most co-residency rules are implemented Virtual Machine Placement Tool (VMPT):

30 VM Placement Tool

31 VM Placement Example with 5000 users Best Practices Spread VMs across different nodes to minimize failure impact. Provide spare capacity for future growth, server maintenance, or Collaboration application upgrades possibly requiring more resources.

32 AGENDA Overview Platforms How To Design Other Design Considerations: Storage and Network Considerations VMware features support How To Deploy

33 Storage Array Requirements UCS B-series TRC Storage Vendor Specs-Based Any Vendor compatible with Server and VMware Storage Technology FC only Flexible (FCoE, iscsi, NFS ) Meet Performance Requirements Thick Provisioning Recommended (not required) Flexible RAID Configuration Other Requirements Performance Requirements SAN Kernel Command Latency < 4ms Hypervisor Physical Device Command Latency < 20ms Reference: NAS Total Guest Latency < 24ms

34 Storage Array Performance Design Unified CM BHCA Average IOPS 10K ~35 25K ~50 50K ~100 CUCM upgrades generate 800 to 1200 IOPS in addition to steady state IOPS Presence VM Size Average IOPS Unity Connection 1000 users VM size ~60 Average IOPS Peak IOPS 2 vcpu (5,000 users) ~130 ~715 4 vcpu (10,000 users) ~220 ~870 VM Size Average IOPS Peak IOPS 2 vcpu (300 agents) ~150 ~1500 Unified CCX Traffic Type: In general, I/Os are mostly sequential writes Reference: > Collaboration Application

35 DAS Storage Requirements TRC and BE6000 / BE7000 Specs-Based BOM (Disks/RAID controllers) Fixed. Exceptions: Faster/Larger disks ok Flexible RAID configuration Fixed Flexible Thick/Thin Provisioning Thick only Thick recommended Storage Performance Design No IOPS calculation needed Use TRC as reference Or calculate IOPS

36 Networking Considerations with UCS C-series In general, use all ports available Or Calculate Bandwidth requirements for each VM Bandwidth Formulas available in the Design Guides and SRND. Only account for traffic in/out of the host (not within host) Consider traffic streams that carry media, especially Video Plan for upstream switch redundancy. With redundancy, need 2x number of ports.

37 VMware vsphere Release Compatibility Application ESXi 4.0 ESXi 4.1 ESXi 5.0 ESXi 5.1 ESXi 5.5 CUCM 8.0(2) and later 8.0(2) and later 8.0(2) and later 8.0(2) and later 9.X or later CUP/Unified IM&P 8.0(2) or later 8.0(2) or later 8.6(1) or later 8.6(4) or later 9.1(1) or later CUC 8.0(2) or later 8.0(2) or later 8.0(2) or later 8.0(2) or later 9.X or later CCX 8.0(2) to 9.x 8.0(2) or later 8.0(2) or later 8.5(1) or later 10.0(1) or later ESXi release support varies with UC application (many apps do not support ESXi 5.5) ESXi Updates (e.g. U1, U2, etc ) implicitly supported unless specified otherwise For the exact release of Cisco Collaboration application or ESXi, refer to the docwiki For details and latest support: > Application

38 VMware vsphere compatibility with Application Docwiki reference example For Your Reference

39 VMware Feature Support VMware Features vmotion Storage Copy HA vmotion Clone VMware Fault DRS Tolerance CUCM Y (C) Y (C) Y (C) Y (C) N N CUP / IM & Presence Y (P) N Y (C) Y (C) N N CUC Y (P) N Y (C) Y (C) N N vmotion LEGEND: Y(C) Supported with Caveats Y(P) Partial or Limited N Not Supported Caveat:YCan with live CCX Y(C): supported with Y (C) (C) be done Y (C) N traffic, N but slightnrisks to impact calls. Y(P): Partial: During maintenance window only. Copy / Clone Y(C): supported with Caveat: Shutdown VM first VMware Distributed Resource Scheduler (DRS) Not supported at this time. No real benefits since Oversubscription is not supported VMware vsphere Requirements

40 High Availability (HA) Design Application HA vs. VMware HA Collaboration application HA VMware HA DAS Storage Support Yes No (requires shared storage) VM file system corruption Protection Yes No Faster Longer Additional mechanisms required to ensure failover does not result in an unsupported configuration No Yes Fully Supported Yes No Failover Time Best Practice: VMware HA is allowed but Use Cisco Collaboration application built-in redundancy first

41 Backup Strategy Application vs. VMware Backup Cisco Disaster Recovery System (DRS) VMware Copy / Clone / vdp Yes No (Power Off VM) Longer Short Backup can be taken when VM is running Restore time Best Practice: Can use VMware Copy for fast restore but Always perform a DRS Back Up

42 AGENDA Overview Platforms How To Design Other Design Considerations How To Deploy Installation Migration to virtualization

43 Installation 1. Configure platform (e.g. RAID) 2. Install VMware ESXi 3. d with e d e e Not n /BE BE60 th ed wi d e e n 0 Not E700 B / 0 0 BE60 Deploy OVA template Application Block Application VMFS Storage Block Block Block Block VMFS Storage Block Chunk Block Block Chunk Block Block Block Block Chunk Chunk Use the OVA available on cisco.com for virtual HW settings and for Disk Alignment cucm_10.0_vmv8_v1.7.ova UC App UC App release VM Hardware Version ESXi4:vmv7, ESXi5:vmv8 OVA Version When deploying the VM template, select VM configuration 5. Install Cisco Collaboration application Cisco Collaboration on Virtual Servers:

44 Migration to Virtualization Migration CUCM on MCS CUCM release supporting virtualization Upgrade if current CUCM release doesn t support virtualization DRS CUCM Virtual Follow the normal Server Replacement procedure: DRS backup, Install using the same UC release, DRS restore. Upgrade if current CUCM release doesn t support virtualization. In general, virtualization requires 8.0(2)+.

45 Migration to Virtualization If done manually, could be long and laborious CUCM on MCS CUCM on MCS Upgrade Upgrade or Bridge Upgrade CUCM release supporting virtualization DRS Migrate CUCM Virtual Upgrade CUCM Virtual Jump Upgrade to 9.1(2) CUCM 6.1.4, 6.1.5, or on MCS DRS backup Jump to VM install 6.1.4, 6.1.5, or virtual Upgrade to Apply RU Cop file DRS Restore Interim CUCM virtual Reinstall VM (Partition alignment) DRS backup Isolated Lab Environment Final CUCM virtual DRS Restore migrate licenses to ELM

46 Migration path to UCM Migration to Virtualization Or it could be faster and simpler with Prime Collaboration Deployment (PCD)! Migration with PCD For Migration to CUCM / IM & Presence Direct upgrade to and Automated Migration Process Can change IP address / Hostname during migration Not based on Disaster Recovery System (DRS) CUCM 6.1.5, 7.1.3, 7.1.5, 8. x, 9.x on MCS PCD Migration CUCM virtual Also: Free of charge Can perform tasks (change IP/networking, upgrade, switch versions) Minimum virtualization SW license requirements: Cisco UC Virt. Foundation or vsphere Standard Edition

47 Summary Perform the Application Design as usual Deployment Model, High Availability, VM Config, Number of VMs SRND: Cisco Collaboration Sizing Tool: Application Design Docwiki: VM Placement Select type of platforms (TRC vs. Specs-based, B vs. C, ) VM placement: Sizing and Co-residency Storage, Networking, VMware considerations Docwiki: VM Placement Tool: Cisco Collaboration on Virtual Servers Plan how to install/migrate VM Placement

48 Questions?

49 Need more? Want more details? BRKUCC Migration and Co-Existence Strategy for Collaboration Applications in a Virtualized Environment (tomorrow, 8:00am) BRKUCC UC on UCS Overview (recording available on Cisco Live 365) Upgrade Resource Central com/community/partner/collaboration/migration Questions after you go home? Ask the BU at Collaboration User Group com/community/technology/collaboration/usergroups/collaboration Technical design information at

50 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. Don t forget: Cisco Live sessions will be available for viewing on-demand after the event at CiscoLive.com/Online

51 Continue Your Education Demos in the Cisco Campus Walk-in Self-Paced Labs Table Topics Meet the Engineer 1:1 meetings

52

53