Planning and Designing Virtual UC Solutions on UCS Platform BRKUCC-2782

Size: px

Start display at page:

Download "Planning and Designing Virtual UC Solutions on UCS Platform BRKUCC-2782"

Bernice O’Neal’
6 years ago
Views:

1 Planning and Designing Virtual UC Solutions on UCS Platform BRKUCC-2782

2 Housekeeping We value your feedback Please don't forget to complete session evaluation You might have visited World of Solutions already Please remember this is a 'non-smoking' venue! Please switch off your mobile phones Please make use of the recycling bins provided Please remember to wear your badge at all times 2

3 Abstract Attendees should have a working knowledge of Cisco UC product portfolio specially CUCM Knowing VMware, UCS and SAN concepts is must for this session UC applications on Cisco UCS B and C Series - As VMs 90 min Design Session - Based on UC 8.5 Will Not cover configuration and troubleshooting details Q/A Policy Questions may be asked during the session But due to time limit, flow and respecting every one s interest, some questions might be deferred towards the end 3

and Placement SAN & VMware Design Best Practices Network considerations, QoS,

4 Virtual DC, UCS Server Virtualization Architecture UCS Hardware, LAN/SAN Interconnect Deployment models, scalability and capacity planning VM Sizing and Placement SAN & VMware Design Best Practices Network considerations, QoS, Redundancy / High Availability Case Study Monitoring/Diagnostic Management Options 5

6 Prerequisites Do you know the basics of CUCM or CallManager Virtualization/VMware Storage Area Networking Cisco UCS Answer Yes. That s why I am here Running server apps as VMs. VMware ESX vs. ESXi hypervisor vsphere Separation of storage from the compute FC, iscsi & FCoE protocol It is a new computing architecture from Cisco. Beside other components it offers B and C series x86 based servers 7

7 DAS, iscsi and SAN Comparison DAS (Direct Attached Storage): Rack Mount HP/IBM MCS Servers Popular DAS Protocol: SCSI iscsi: Access SCSI storage media using IP network SAN: Storage (Hard Drives) away from physical server or compute Popular SAN Protocol: FC Host/ Server Storage Transport Storage Media DAS Computer System Application File System Volume Manager SCSI Device Driver SCSI Bus Adapter SCSI SAN Computer System Application File System Volume Manager SCSI Device Driver FC HBA SAN FC Block I/O iscsi Computer System Application File System Volume Manager SCSI Device Driver iscsi Driver TCP/IP Stack NIC IP NIC TCP/IP Stack iscsi Layer Bus Adapter 8

Storage Area Network (SAN) SAN: Way to access the storage sitting away from compute Remove Hard Drive and put it 1km away High-performance interconnect providing high

8 Storage Area Network (SAN) SAN: Way to access the storage sitting away from compute Remove Hard Drive and put it 1km away High-performance interconnect providing high I/O throughput Lower TCO relative to direct attached storage, storage can be shared SAN LAN Clients Servers Block Storage Devices Separation of Storage from the Server 9

9 Unified Fabric FCoE Standard DAS iscsi FCoE FC SCSI SCSI SCSI SCSI iscsi FCP FC FCP FC TCP IP Ethernet FCoE Ethernet Physical Wire 10

10 Unified I/O Architecture Consolidation Today I/O Consolidation with FCoE LAN SAN A SAN B LAN SAN A SAN B Nexus 5000 Ethernet FC FCoE 11

11 UC on UCS - Virtual DC Overview Network vs. Server Virtualization UC Application UC Application UC Application 5 4 VMware ESXi, Unified Computing System

Compute: Cisco UCS B-Series Blade Servers Examples UCS B440 UCS B250 UCS B230 UCS B200 Blade CPU Size Memory Disks VMs UCS B440 M1 4x Intel 7500 Full Width 32 DIMM 256 GB 4 3.

13 Compute: Cisco UCS B-Series Blade Servers Examples UCS B440 UCS B250 UCS B230 UCS B200 Blade CPU Size Memory Disks VMs UCS B440 M1 4x Intel 7500 Full Width 32 DIMM 256 GB SAS/SATA Drives NA UCS B250 2x Intel 5540 or 5640 for M2 Full Width 48 DIMM 384 GB 2x 3.5 SAS Drives NA UCS B230 2x Intel 6500 or 7500 for M2 Half Size 32 DIMM 256 GB 2x 3.5 SSD Drives NA UCS B200 2x Intel 5540 or 5640 M2 Half Width 12 DIMM 96GB 2x 3.5 SAS Drives 4 14

14 Compute: UCS B Series Components UCS Manager (Embedded) Fabric Interconnect Switch Fabric Extender (Up to 2) UCS 5108 Blade Server Chassis UCS B200M1 half size UCS B250M1 full size CPU: Intel Xeon E5540 I/O: M71KR-Q/E CNA & M81KR VIC Memory & Hard Drive 15

Intel 5540 2x Intel 5540 (5640) 2x Intel 5506 2RU 2RU 1RU 64 DIMM 512 GB 48 DIMM 384 GB 12 DIMM 96 GB 12 DIMM 96GB 12

15 Compute: Cisco UCS C-Series Rack-Mount Servers Examples UCS C460 M1 UCS C250 M1 UCS C210 M1(M2) UCS C200 M2 Rack Server CPU Size Memory Disks Adaptor VMs UCS C460 M1 4x Intel RU UCS C250 M1 (memory intensive) UCS C210 M1 UCS C200 M2 2x Intel x Intel 5540 (5640) 2x Intel RU 2RU 1RU 64 DIMM 512 GB 48 DIMM 384 GB 12 DIMM 96 GB 12 DIMM 96GB 12 SAS/SATA Drives 8 SFF SAS/SATA Drives 16 SFF SAS/SATA Drives 4 x 3.5 SAS/SATA Drives 10 PCIe NA 5 PCIe NA 5 PCIe 4 2 PCIe 4 16

New UC Deployment Building Blocks Thinking outside the (MCS) Box

Virtualization allows multiple Virtual Machines to access common

Building blocks change from physical servers with CPU/MEM/HDD to

17 New UC Deployment Building Blocks Thinking outside the (MCS) Box Deployments have been based on single application MCS servers Virtualization allows multiple Virtual Machines to access common HW resources Solution capacity and deployment models do not change Building blocks change from physical servers with CPU/MEM/HDD to VMs The number of required servers remains the same, but the HW will vary 18

18 Virtual UC on UCS Architecture MCS 7816/25/28 UCS 5108 Chassis Virtual UC Apps MCS 7835/45 UCS C210/C200 Hypervisor UCS B200 with CNA FEX UCS 2100 Fabric Extender UCS 6100XP Fabric Interconnect Switch 10/100/1GbE 10GbE FC Catalyst PSTN/ PTT LAN Nexus SAN FC MDS Management: - UCS Manager - CIMC for UCS - vsphere/vcenter Rest of Intranet Storage Array (for UC Apps) 19

20 Cluster Based on Virtual Resources Unity Connection Unity Connection Unified CM CUCCX Unified CM CUCCX MCS Servers CPU/Mem/HDD Virtual Machines (OVA) vcpu/vmem/san or DAS 21

21 Virtual Machine Specification Number of VMs typically the same as physical MCS s But Virtual Machines are measured by: -vcpu -vram -vdisk -vnics A VM solution can be deployed on any supported hardware mix that meets the specified resource Multiple VMs on same physical HW 22

Cisco UCS B200M2 (UCS-B200M2-VCS1) B200M2 TRC Example PSTN/ PTT Catalyst UCS 6100XP Fabric Interconnect Switch LAN Rest of Intranet UCS 2100 Fabric Extender 10GbE Nexus UCS 5108 Chassis FC SAN

23 Cisco UCS B200M2 (UCS-B200M2-VCS1) B200M2 TRC Example PSTN/ PTT Catalyst UCS 6100XP Fabric Interconnect Switch LAN Rest of Intranet UCS 2100 Fabric Extender 10GbE Nexus UCS 5108 Chassis FC SAN Storage Array (for UC Apps) 24 FC MDS Configuration (M1): - 32GB RAM - 2 x E5540 CPU - 2 x 146GB SAS Drives - M71KR-Q CNA Adapter - Supports multiple VMs Configuration (M2): - 48GB RAM - 2 x E5640 CPU - 2 x 146GB SAS Drives - UCS M81KR VIC - Supports multiple VMs Management: - UCS Manager - vsphere/vcenter

24 Cisco UCS C200M2 (UCS-C200M2-VCD2) C200M2 TRC Example 10/100/1GbE UCS C200 M2 Configuration: - Dual Quad Core E x 1TB SAS Drives - 24 GB RAM - 2 x 1GB NICs Ethernet - 1 x 1GB NIC for CIMC - Supports multiple VMs Catalyst PSTN/ PTT LAN Rest of Intranet Management: - CIMC for UCS - vsphere/vcenter 25

Tested Reference Configurations Summary Server Model/Generation & Tested Reference Configuration Collaboration SKU Notes B200 M2 TRC #1 UCS-B200M2-VCS1 Co-res, SAN B200 M1 TRC #1 UCS-B200M1-VCS1

25 Tested Reference Configurations Summary Server Model/Generation & Tested Reference Configuration Collaboration SKU Notes B200 M2 TRC #1 UCS-B200M2-VCS1 Co-res, SAN B200 M1 TRC #1 UCS-B200M1-VCS1 Co-res, SAN C210 M2 TRC #1 UCS-C210M2-VCD2 Co-res, DAS TRC #2 DC SKU only Co-res, SAN C210 M1 TRC #1 UCS-C210M1-VCD1 Single VM, DAS TRC #2 UCS-C210M1-VCD2 Co-res, DAS TRC #3 DC SKU only Co-res, SAN C200 M2 TRC #1 UCS-C200M2-VCD2 Co-res, DAS (1K users) For B-Series DAS (for ESXi) and SAN (for VM) is required For C-Series C210 (Support DAS and SAN options) C200 (Support DAS option only) 26

are not changing NO software checks for design rules No rules or restrictions are in place in UC Apps to check if

27 UC Deployment Model (Application) All UC Deployment Models are supported No change in the current deployment models Base deployment model Single Site, Centralized Call Processing, etc. are not changing 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 Clustering over WAN (COW) Mega-Cluster Mixed/Hybrid Cluster vblock 28

Primary/secondary on different blade, chassis, sites On same blade, mix Subs with TFTP/MoH vs.

28 High Availability Design Rules Current Business Continuity and Disaster Recovery strategies are still applicable The UC apps redundancy rules are same Distribute UC application nodes across UCS blades, chassis and sites to minimize failure impact Primary/secondary on different blade, chassis, sites On same blade, mix Subs with TFTP/MoH vs. just Subs Redundancy of UCS components (blade, chassis, FEX links, Interconnect switching) Redundancy of new network types (10GbE, SAN multi-pathing, etc.) 29

30 Virtual Machine Sizing Virtual Machine characteristics store in OVA An OVF package consists of several files, placed in one directory A one-file alternative is the OVA package Each products has one or more defined OVAs OVA defines: -vcpu, vram, vdisk, vnics, OS Type -Network and Storage traffic profiles OVA naming scheme: -Includes product, user count and revision CUCM_7500_user_v1.0_vmv7.ova CUC_5000_user_v1.0_vmv7.ova Cisco UC OVAs include partition alignment 31

31 UC VM Configuration 8.5(1) Product Scale (users) vcpu vram (GB) vdisk (GB) CUCM 7, x 80 2, x 80 UnityConnection 20, x , x 146 5, x x 160 Unity 15, x 24 5, x 24 CUP 5, x80 2, x 80 UCCX/IPIVR 400 agents x agents x vcpu for Unity Connection ESXi scheduler SME = CUCM Session Management Edition 32

32 UC VM Configurations 8.5(1) Product Scale (users) vcpu Cores vram (GB) vdisk (GB) CER 30, x 80 20, x 80 12, x 80 CMBE 6000 (C200) VM Configurations 8.5(1) Product Scale (users) vcpu Cores vram (GB) vdisk (GB) CUCM 1,000 2 (600 MHz *R) 4 (*R) 1 x 80 UnityConnection 1, x 160 CUP 1,000 1 (800 MHz *R) 2 1 x 80 UCCX/IPIVR x 146 * R = Reserved 33

33 UCCE/CVP VM Configuration 8.5(1) CVP Component & Scale * vcpu vram (GB) vdisk (GB) vnic Call+VXML Server (900 Calls) x Reporting (Large) (840 Msg/sec) x 72 1 x 438 OAMP Server x UCCE Component & Scale * vcpu vram (GB) vdisk (GB) vnic Router 8000 agents x 80 2 Logger 8000 users x150 2 Agent PG 2000 users x 80 2 VRU PG 9600 ports, 10 PIMs x 80 2 AW Server (25 clients) x

34 Virtualized Server Placement Hypothetical C-Series Layout Small site, 500 users w/ VM and 50 Contact Center agents Consolidate 7 servers into 2 C-Series CPU-1 Rack Server #1 CPU-2 PROs: 7:2 server consolidation PUB/ TFTP ESXi UCxn UCxn (Act) CUP CCX-1 4 RU s App Redundancy Core 1 Core 2 Core 3 Core 4 Core 1 Core 2 Core 3 Core 4 Extra server at no HW cost CPU-1 Rack Server #2 CPU-2 CONs: SUB ESXi UCxn UCxn (Stnadby) CCX-2 Extra server Core 1 Core 2 Core 3 Core 4 Core 1 Core 2 Core 3 Core 4 35

36 Server design considerations Which UCS servers should be deployed? Does the customer already have Data Center w/ SAN? -ROI realized much earlier -SAN/DataCenter knowledge simplifies deployment Is UC a driver for implementing SAN? -SAN/DataCenter knowledge key to successful deployment -Much lower ROI due to SAN costs UCS chassis management -B Series Chassis have centralized management via UCS Manager -C Series are managed individually via CIMC 37

37 Server Selection Guideline 1 Yes > 24 vcpu? UCS B200 Yes Already have DC/SAN? No $$ Yes No C210Mx SAN Yes 2 Building DC for UC? Start > 10 servers No No C210Mx DAS Yes 3 > 8vCPU or > 1000 users 1 2 Large Medium No C200M2/ BE Small 38

4.0 Features CUCM UnityConn VM Template (OVAs) Yes Yes Copy Virtual Machine Yes Yes Resize Virtual Machine Partial Partial VMware Hot Add

39 Virtual Machine Planning/Designing ESXi 4.0 Only ESX not supported vsphere Hypervisor (free ESXi) and Standard to Enterprise Plus VMware feature support varies by application ESXi 4.0 Features CUCM UnityConn VM Template (OVAs) Yes Yes Copy Virtual Machine Yes Yes Resize Virtual Machine Partial Partial VMware Hot Add No No VMware HA Yes Yes VMware vmotion Partial Partial VMware DRS No No P2V or vcenter Converter No No Partial = Limited support (See following URL for details) 40

40 VMware Management 1 1 vsphere Client A Cisco is not dictating management of VMware images Customer strategy will depend on number of images VMware vsphere Client -Thick client downloaded to Windows PC -Directly manages each VMware ESXi host (Model A) 1 1 vsphere Client 2 B vcenter Server -Can connect to VMware vcenter Server to centrally manage all ESXi hosts (Model B) VMware vcenter Server -Windows server running vcenter 4.x -Provides central point of configuration, provisioning and management -Only way to get chassis HW failure notification 41

Virtual Software Switch Options UCS B200 VMware vswitch VMware dvswitch

802.1Q VLAN tagging VLANs only visible to local ESXi host IEEE 802.

1Q VLAN tagging VLANs visible to all ESXi hosts EtherChannel EtherChannel

PortChannel -- -- QoS Marking (DSCP/CoS) FCoE -- -- ACL -- -- SPAN

42 Virtual Software Switch Options UCS B200 VMware vswitch VMware dvswitch Cisco Nexus 1KV vnic VM Host based (local) Distributed Distributed IEEE 802.1Q VLAN tagging VLANs only visible to local ESXi host IEEE 802.1Q VLAN tagging VLANs visible to all ESXi hosts IEEE 802.1Q VLAN tagging VLANs visible to all ESXi hosts EtherChannel EtherChannel EtherChannel CNA Software Switch ESXi Hypervisor vmnic Virtual PortChannel QoS Marking (DSCP/CoS) FCoE ACL SPAN RADIUS/TACACS+ No VM needed No VM needed VM needed vcenter not needed vcenter needed vcenter needed LAN SAN 43

43 UC QoS Concepts With C-Series or MCS CUCM CTL Packet L3 L2:0 L3:CS3 CUCM VM or MCS is connected to a switch CUCM marks traffic based on L3 DSCP values Physical switch (e.g Cat6k) does mapping from L3 DSCP to L2 CoS (if needed) dc1-access-6k(config)#mls qos map dscp-cos 24 to 3 dc1-access-6k(config)#mls qos map dscp-cos 46 to 5 C S 3 CAT6K L2:3 L3:CS3 L2:3 L3:CS3 BRKUCC-2782_syali Physical switch maps L3 DSCP to L2 CoS 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 44

UC QoS Concept With B-Series 6100 switch in middle L2

altered by 6100 6100 sends packet to Physical ethernet

drop policy Rest ( match any ) Best Effort Queue CUCM L2:0

44 UC QoS Concept With B-Series 6100 switch in middle L2 based prioritization DSCP value in IP header is not altered by sends packet to Physical ethernet switch Default QoS settings on UCS FC ( match cos 3 ) no drop policy Rest ( match any ) Best Effort Queue CUCM L2:0 L3:CS3 UCS 6100 CAT6K vswitch & UCS 6100 can not map L3 DSCP to L2 CoS 45

Ethernet UC Apps Disc Space SAN Disc Array BRKUCC-2782_syali IP traffic competing

45 B-Series Potential Congestion Scenario Up to 20 UCS 5108 Chassis UCS B200 Blade Server FCoE UCS-6100 FI Switch Fibre Channel Catalyst Ethernet Switch 10Gbps Ethernet UC Apps Disc Space SAN Disc Array BRKUCC-2782_syali IP traffic competing with FC traffic 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 46

46 B-Series QoS Best Practices CUCM L2:0 L3:CS3 N1KV L2:3 L3:CS3 N1Kv Considerations: UC sig. traffic (CoS3) share queues with FCoE traffic (CoS3) UC sig. traffic is given lossless behavior Default CoS value of 3 for FCoE traffic should never be changed UCS 6100 L2:3 L3:CS3 CAT6K Without N1Kv: UC blades Network Adapters QoS policy set to Platinum (CoS=5; No Drop) Non-UC blades Network Adapters QoS policy set to best effort Caveat: All traffic types from virtual UC App will get CoS value of Platinum Non-UC application gets best-effort class might not be acceptable 47

47 FC Network Best Practices/Guidelines 3 rd Party SAN Example 1 Rack; 12 DAE Total capacity 28,000 IOPS 14,000 IOPS per controller 4 KByte block size 14,000 IOPS x (4KB) ~ 428 Mbps 600 Mbps throughput/controller Compute Layer Nexus 1000V 4x10GE 4x10GE 4x10G E 4x10G E Cisco UCS 6100 Fabric Interconnect UCS 5100 Blade Server Result One 4 Gbps FC interface is enough to handle the entire capacity of one Storage Array HA requires four FC interfaces SAN/Storage Layer Cisco SRND FC FC FC FC Cisco SAN Switch SP-A SP-B CUCM VM IOPS ~ IOPS * 4KB ~ 6.4 Mbps per VM 3 rd party layer FC Storage 48

48 SAN Array LUN Best Practices / Guidelines HD Recommendation LUN Size Restriction UC VM App Per LUN LUN Size Recommendation FC class (e.g 450 GB 15K, 300 GB 15K) ~ 180 IOPS Must never be greater than 2 TB Between 3 & 8 (different UC apps require different space requirement based on OVA Between 500 GB & 1.5 TB PUB SUB1 UCCX1 VM1 VM2 VM3 UCCX2 CUP1 CUP2 VM1 VM2 VM3 LUN1 720 GB LUN 1 (720 GB) LUN2 720 GB LUN 2 (720 GB) Single RAID5 Group (1.4 TB Usable Space) HD 1 450gig 15K RPM HD 2 450gig 15K RPM HD 3 450gig 15K RPM HD 4 450gig 15K RPM HD 5 450gig 15K RPM 49

51 Deployment Model Distributed Call Processing 2000 IP Phones Applications (UnityC, UCCX, CUP) CUCM cluster PSTN CUCM cluster UnityC, UCCX, CUP 12,000 IP Phones CUSP SIP Proxy IP WAN CUCM cluster UnityC, UCCX CUP CUCM and Applications located at each site Up to 30,000 lines per site 100+ sites Transparent use of PSTN if IP WAN unavailable 500 IP Phones 52

52 CUCM Server Requirement Input 12K Phones 10K Messaging Users 10K CUPC Clients 240 UCCX Agents 10 Supervisors Unity Connection Server Requirement MCS Servers CUCM 11 UCxn 2 CUP 2 UCCX 2 Total 17 CUP Server Requirement UCCX Server Requirement 53

Server Requirement 12K Devices/Users B200-1 B200-2 PUB CPU-1 CPU-2 CPU-1 CPU-2 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 B200-3 B200-4 SUB-7

CUP-1 SUB-3 SUB-5 SUB-6 SUB-4 TFTP-2 ESXi UCxn ESXi UCxn UCxn-1 Active UCxn-2 Active CUP-1 UCCX-1 CUP-2 Input 12K Phones 10K Messaging Users 10K CUPC Clients 240 UCCX Agents 10 Supervisors MCS

53 Server Requirement 12K Devices/Users B200-1 B200-2 PUB CPU-1 CPU-2 CPU-1 CPU-2 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 B200-3 B200-4 SUB-7 CPU-1 CPU-2 CPU-1 CPU-2 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 B200-5 B200-6 SUB-8 TFTP-1 UCCX-1 CPU-1 CPU-2 CPU-1 CPU-2 UCCX-2 SUB-1 SUB-2 CUP-1 SUB-3 SUB-5 SUB-6 SUB-4 TFTP-2 ESXi UCxn ESXi UCxn UCxn-1 Active UCxn-2 Active CUP-1 UCCX-1 CUP-2 Input 12K Phones 10K Messaging Users 10K CUPC Clients 240 UCCX Agents 10 Supervisors MCS Servers CUCM 11 UCxn 2 CUP 2 UCCX 2 Total 17 B200 Servers Total 6 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 CUCM 2 vcpu 6 GB RAM 7.5K users CUC 4 vcpu 4 GB RAM 10K users CUP 4 vcpu 4 GB RAM 5K users UCCX 2 vcpu 4 GB RAM 300 agents 54

54 Management Layers Virtual KVMoIP CIMC UCS Manager UCS C210 M1 vcenter vs. Standalone Depends on the vendor/dc team Web GUI/CLI (CUCM/UnityC/etc) Windows Apps (UCCE/CVP/etc) 55

55 Deploying UC Virtual Machine B&C Series 2 1 OVF Templates Provided by Cisco 3 4 ISO UCS C210 M1 UC VM OVF Templates: UCS B200 M1 56

56 Managing Virtual UC Application (B & C Series) At login to the CLI and GUI, the VM configuration is displayed Virtual UC Apps are NOT aware of the type of hardware being used (servers) nor the type of storage. No VM BIOS management No hardware management and monitoring New iostat information is added to RTMT and logged (perfomon counters) to help debug Disk I/O related issues on the SAN 57

Only 3 Slides Left Now :- ) Complete Your Online Session Evaluation Give us your feedback and you could win fabulous prizes. Winners announced daily.

57 Only 3 Slides Left Now :- ) Complete Your Online Session Evaluation Give us your feedback and you could win fabulous prizes. Winners announced daily. Receive 20 Cisco Preferred Access points for each session evaluation you complete. 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. Don t forget to activate your Cisco Live and Networkers Virtual account for access to all session materials, communities, and on-demand and live activities throughout the year. Activate your account at any internet station or visit 58

58 Questions? 59

59 External Resources Unified Communications Network Design Guide (SRND) UC Virtualization Supported UCS Hardware Specs UC on UCS Solution Overview and Ordering Information Customer Success Story Station Casino (12K Phones) Virtual UC Deployment Guide on B-Series by Shahzad Ali 60

60 Recommended Reading Please browse on-site Cisco Store for suitable reading. 61

61 62

Planning and Designing Virtual Unified Communications Solutions

Planning and Designing Virtual Unified Communications Solutions Housekeeping Please do not forget to complete session evaluation Please switch off your mobile phone Q&A Policy Questions may be asked during