CIN Technology Workshop

Transcription

1 CIN Technology Workshop Collaborate Anywhere, Anytime, on any Device with Cisco UC on UCS Overview May Cisco and/or its affiliates. All rights reserved. 1

2 Device Diversity is here to stay User Wants Consistent experience on multiple devices Seamless transitions between devices 89% 26% 75% Separation of work and personal data Keep up with tech and social trends 10% 36% IT Wants 1% 23% 22% Proactive adoption of consumer/mobile devices Embrace BYOD without sacrificing security, management, business standards Lower organizational costs Improved agility 2010 Cisco and/or its affiliates. All rights reserved. 2

3 VOIP, ICM CUCM 3.x/4.x Cisco UC 5.0+ Cisco UC 8.0(2)+ SAF 1990s ~ Future Legacy Voice Enhancement Server (Special-purpose) Appliance Virtualization Network Services Business Agility Footprint, Space, Energy, Cabling Investment Leverage Business Continuity Management Simplification Increasing Architectural Flexibility while Decreasing Barriers to Rapidly Deploy/Tailor Increasing Miniaturization, Consolidation & Avoidance while Increasing Efficiency No Forklifts Network Convergence Commodity Servers/Storage Virtualization Increasing Security, Resiliency and options for High Availability / Disaster Recovery Increasing Familiarity, Centralization, Scale and Efficiency 2010 Cisco and/or its affiliates. All rights reserved. 3

4 Same TCO Drivers: Technology, Facilities, Management Burden Data Center 1.0 with Traditional Communications Data Center 2.0 with Unified Communications Data Center 3.0 with Virtualized Communications Mainframe PBX Servers and Appliances Virtualized Compute/Storage Voice, Video, Mobility Data Too Many Networks Converged Network Data Center Too Many Fabrics The Network Unified Fabric & Networks Excessively Centralized with Duplicate Networks Inflexible High TCO Excessively Distributed with Duplicate Networks Sprawl Medium to High TCO Flexible Operations on a Single Network Agility + Governance Low TCO 2010 Cisco and/or its affiliates. All rights reserved. 4

5 E.g. Business Edition 6000 E.g. Hosted Collaboration Solution Private Cloud Provider Cloud or Hybrid Public Cloud 2010 Cisco and/or its affiliates. All rights reserved. 5

6 Rack Mount Blade B200 M2 2-Socket Intel 5600, 2 SFF Disk, 12 DIMM B250 M2 2-Socket Intel 5600, 2 SFF Disk, 48 DIMM B230 M2 2-Socket Intel E7-2800, 2 SSD, 32 DIMM B440 M2 4-Socket Intel E7-4800, 4 SFF Disk, 32 DIMM Updated Updated C200 M2 2-Socket Intel 5600, 4 Disks, 12 DIMM, 2 PCIe 1U C210 M2 2-Socket Intel 5600, 16 Disks, 12 DIMM, 5 PCIe 2U C250 M2 2-Socket Intel 5600, 8 Disks, 48 DIMM, 5 PCIe 2U C260 M2 2-Socket Intel E7-2800, 16 Disks, 64 DIMM, 6 PCIe 2U C460 M2 4-Socket Intel E7-4800, 12 Disks, 64 DIMM, 10 PCIe 4U New Updated MCS Appliance Configuration-based Highly Prescribed Only 1 app per server IBM x3650-m2 or x3250-m3 Only one CPU model supported (single 4-core) Fixed RAM Exact match at part number level for adapters. 1 storage option only Cisco owns app performance UC on UCS Tested Reference Configuration (TRC) Configuration-based Prescribed Typical 4-20 s per server UCS B200/B230/B440 M2, C210/C200 M2 E5640, E5506, E7-2870/4870 (4-core or 10-core) Fixed RAM Blades: you pick adapter Rack: exact match at part number level for adapters Pick from a few storage options Cisco owns app performance UC on UCS Specs-based Specs-based A Few Restrictions Typical 4-20 s per server Any UCS that satisfies policy 56xx / 75xx GHz 2.4+ GHz RAM depends on s Regardless of server, you pick the adapters. Any storage but you design it Customer owns app performance 2010 Cisco and/or its affiliates. All rights reserved. 6

7 Target Customer Profiles Ready, willing, able to support servers, ware, storage Ready to move off appliance-oriented operations UCS B-series for centralized medium to high server count UCS C-series for low to medium server count or highly distributed 3 rd -party server options for investment leverage Platform Support Virtual Machine Templates - defined by each UC app Application Co-residency mix & match, UC with UC for most UC apps Requries ware vsphere 4/5 ESXi only, feature support depends on app. vcenter is also required for specs-based. UCS, HP and IBM server hardware options DAS, SAN, NAS and Diskless storage options Various NIC, HBA, C.N.A. and Cisco VIC network options (1GB through 10GB) 2010 Cisco and/or its affiliates. All rights reserved. 7

8 UC on UCS Solution Components UC on UCS B-Series UCS 5100 Blade Server Chassis UCS 2100 Fabric Extender UCS B-Series Blade Servers LAN PSTN UCS 6100 Fabric Interconnect Switches SAN Required Shared Storage Cisco Unified Communications UC on UCS C-Series LAN PSTN UCS C-Series General-Purpose Rack-Mount Servers SAN Optional Shared Storage Presentation_ID 2009 Cisco Systems, Inc. All rights reserved. 8

9 Cisco Hosted Collaboration Solution Combining virtualization, management & architecture elements for a comprehensive platform Unified Communication System 8.0 Voice, Video, Presence, Mobility, Customer Care Available in flexible deployment models Deliver a unparalleled user experience HCS Management System Zero-touch fulfillment & provisioning with self service Service assurance for enabling high quality of services Coordinated management and integration across domains Cisco Business Edition 6000 Midmarket user solution for call control, mobility, rich media presence and contact center. Optimized Virtualization Platform (UC on UCS B-series) Resource optimized for reduced hardware capex Installation & upgrade automation Provides flexibility, customization, & additional redundancy Scalable System Architecture Customer Aggregation & SIP Trunking SLA Enablement, Security, Scalability Cloud Based SaaS Integration Infrastructure Solutions Data Center building blocks. Vblock FlexPod* * UC on FlexPod planned, not committed 2010 Cisco and/or its affiliates. All rights reserved. 9

10 Rack Mount Blade Supported Hardware: UC on UCS B200 M3 SFF 2-Socket Intel E5-2600, 2 SFF Disk, 24 DIMM B200 M2 2-Socket Intel 5600, 2 SFF Disk, 12 DIMM B250 M2 2-Socket Intel 5600, 2 SFF Disk, 48 DIMM B230 M2 2-Socket Intel E7-2800, 2 SSD, 32 DIMM B440 M2 4-Socket Intel E7-4800, 4 SFF Disk, 32 DIMM C200 M2 (LFF) 2-Socket Intel 5600, 4 Disks, 12 DIMM, 2 PCIe 1U C210 M2 2-Socket Intel 5600, 16 Disks, 12 DIMM, 5 PCIe 2U C220 M3 SFF 2-Socket Intel E5-2600, 8 Disks, 16 DIMM, 2 PCIe 1U C240 M3 SFF 2-Socket Intel E5-2600, 24 Disks, 24 DIMM, 5 PCIe 2U C250 M2 2-Socket Intel 5600, 8 Disks, 48 DIMM, 5 PCIe 2U C260 M2 2-Socket Intel E7-2800, 16 Disks, 64 DIMM, 6 PCIe 2U C460 M2 4-Socket Intel E7-4800, 12 Disks, 64 DIMM, 10 PCIe 4U BE6K (Note: UCS Express not supported) Target support Fall 2012 Target support Fall 2012 Target support Fall 2012 UC on UCS Tested Reference Configuration UC on UCS Specs-based 2010 Cisco and/or its affiliates. All rights reserved. 10

11 Must be on ware HCL Allowed Server Vendors Server model and IO devices on All parts must be supported by server vendor No hardware oversubscription allowed for UC ware vcenter is REQUIRED. UCS B/C UCS Express Other 3 rd -parties Processor Intel Xeon GHz or 2.4+ GHz CPU support varies by UC app Required physical core count = UC s vcpu (+1 if Unity Cxn) Memory Capacity = UC s vram + 2GB for ware Follow server vendor for module density/configuration Adapters (e.g. LAN/Storage Access) Must be on ware HCL and supported by server vendor E.g. 1GbE/10GbE NIC, 2Gb FC HBA, 10Gb C.N.A. or VIC Storage / Network SAN (FCoE, FC, iscsi), NAS (NFS), Variable DAS/RAID Storage capacity = UC s vdisk + ware/raid overhead Storage performance = UC IOPS 2010 Cisco and/or its affiliates. All rights reserved. 11

12 Not Currently Supported by UC Intel Program Nehalem- EP Nehalem- EX Westmere- EP Westmere- EX Romley- EP CPU Family 55xx 65xx 75xx 56xx E7-28xx E7-48xx E7-88xx E5-26xx CPU Cores 4 4,6,8 4,6 6,8,10 4,6,8 CPU Speed GHz GHz GHz GHz 1-3 GHz Example UCS Models with these CPUs B200/250 M1 C210 M1 C250 M1/M2 C200 M2 B230 M1 B440 M1 C460 M1 B200/250 M2 C210 M2 C250 M2 B230 M2 B440 M2 C260 M2 C460 M2 B200 M3 C220 M3 C240 M3 UC on UCS Certifications TRCs for B200 M1 TRCs for C210 M1 (E5540) TRCs for B200 M2 TRCs for C210 M2 (E5640) TRC for B230 M2 TRC for B440 M2 (E7-2870/4870) TRC for C200M2 (E5506) Specs-based (75xx GHz) Specs-based (56xx at GHz) Specs-based (E7 at 2.4+ GHz) 2010 Cisco and/or its affiliates. All rights reserved. 12

13 Small Medium 19 UC app copies 19 UC s with total 40 vcpu s Large 19 MCS Appliances 5 virtualized servers (dual 4-core B200 M2 TRC) 4 virtualized servers (dual 6-core B200 M2 specs-based) 2 virtualized servers (dual 10-core B230 M2 TRC) 2010 Cisco and/or its affiliates. All rights reserved. 13

14 UC on UCS Products with Owner UC on UCS TRC UC on UCS Specs-based Unified Communications Manager Business Edition 6000 C200 M2 only Not supported Unity Connection Unified Presence Unified Contact Center Express Cisco Emergency Responder Session Manager Edition InterCompany Media Engine Unified Attendant Consoles Unity Unified Workforce Optimization (WFO) Unified Contact Center Enterprise Planned Unified Intelligence Center Unified Customer Voice Portal Planned MediaSense Planned Unified Contact Center Mgmt Portal SocialMiner Finesse Planned Unified /Web Interaction Mgr Prime UCMS (OM,PM,SM,SSM) Webex Premise Planned Planned Unified MeetingPlace Planned Planned TMS/CTMS Planned Planned VCS Planned Planned 2010 Cisco and/or its affiliates. All rights reserved. 14

15 Why virtualize on UCS? Lower TCO Business Agility Why virtualize your UC? Reduce Servers/Storage Reduced Power, Cooling, Cabling, Space, Weight Investment Leverage & Easy Server Repurposing Efficient App Expansion Accelerated UC rollouts Better Business Continuity Portable/Mobile s Additional Savings and Increased Agility End to End Solution Single Support UCS is the industry s only fully unified and virtualizationaware compute solution. Infrastructure Simplification (Cables, Adapters, Switching) Converge Communications and DC Networks wire once Consolidates System Mgmt Easier Service Provisioning Tested Reference Configurations Vblocks Cisco options VCE Vblock options 2010 Cisco and/or its affiliates. All rights reserved. 15

16 Example: 5,000 users Dial tone, voic and Presence, 10% are Contact Center Agents 11 non-virtualized rack servers required for UC, more for other business apps CAPEX Reduced Server Count (50-75%) Network/Storage Consolidation (50+%) Reduced Cabling (50+%) OPEX Reduced Rack & Floor Space (36%) Reduced Power/Cooling (20+%) Fewer Servers to Manage (50-75% less) Reduced Maintenance/Support Costs (~20%) 2010 Cisco and/or its affiliates. All rights reserved. 16

17 Example: 5,000 users Dial tone, voic and Presence, 10% are Contact Center Agents 11 non-virtualized rack servers required for UC, more for other business apps CAPEX/OPEX Similar Consolidation and Operational Efficiency/Scale benefits as with UC on UCS B- series Other Benefits Lower initial investment Simple entry/migration to virtualized UC Data Center expertise not required unless using SAN option 2010 Cisco and/or its affiliates. All rights reserved. 17

18 $3,000 $2,500 $2,000 $1,500 C210 M2 vs. MCS 7845 B230 M2 vs. B200 M2 UCS B230 M2 TRC OPEX ($K) UCS B230 M2 TRC CAPEX ($K) UCS B200 M2 TRC OPEX ($K) UCS B200 M2 TRC CAPEX ($K) UCS C210 M2 TRC OPEX ($K) UCS C210 M2 TRC CAPEX ($K) Dual Site Scenario: LAN PSTN SAN LAN UC on UCS B200 / B230 PSTN SAN $1,000 MCS 7845-I3 OPEX ($K) MCS 7845-I3 CAPEX ($K) UC on UCS C210 $500 $ Appliance or Count MCS 7845 Assumptions: UC only, no other business applications included. Spare or hot standby hosts not included. Server is either an MCS Appliance or a 2-vcpu-core Virtual Machine Dual sites, split MCS or UCS TRC servers across sites, no single point of failure redundant sites, switching, blade chassis, rack/blade servers Using list pricing for MCS-7845-I3-IPC1, UCS-C210M2-VCD2, UCS-B200M2-VCS1, UCS-B230M2-VCDL1, and ware Enterprise Plus Edition 2010 Cisco and/or its affiliates. All rights reserved. 18

19 Current Offers: Technical Overview 2010 Cisco and/or its affiliates. All rights reserved. 20

20 Unified CM Unity Connection Unified CCX or for Unified CM Pub for Unified CM Sub for Unity Cxn for Unified CCX E.g. 4 physical servers Each MCS 7800 hosts only one UC app instance 2010 Cisco and/or its affiliates. All rights reserved. 4 virtual servers ( s) on 1 physical server Single virtualized server with total 8 physical cores hosts all UC app instances 21

21 Server Model TRC CPU RAM Storage Adapters UCS B200 M2 Blade Server TRC #1 UCS B230 M2 Blade Server TRC #2 TRC #1 Dual E5640 (8 physical cores total) Dual E5640 (8 physical cores total) Dual E (20 physical cores total) 48 GB DAS (RAID1) for ware, FC SAN for UC apps Cisco VIC 48 GB Diskless Cisco VIC 128 GB Diskless Cisco VIC UCS B440 M2 Blade Server TRC#1 Dual E (40 physical cores total) 256 GB Diskless Cisco VIC UCS C260 M2 Rack- Mount Server TRC #1 Dual E (20 physical cores total) 128 GB DAS (2x RAID5) 1GbE NIC UCS C210 M2 General-Purpose Rack-Mount Server TRC #1 TRC #2 TRC #3 Dual E5640 (8 physical cores total) Dual E5640 (8 physical cores total) Dual E5640 (8 physical cores total) 48 GB 48 GB DAS (2 disks RAID1) for ware + DAS (8 disks RAID5) for UC apps DAS (2 disks RAID1) for ware, FC SAN for UC apps 48 GB Diskless 1GbE NIC 1GbE NIC and 4G FC HBA 1GbE NIC and 4G FC HBA UCS C200 M2 General-Purpose Rack-Mount Server TRC #1 Dual E5506 (8 physical cores total) 24 GB DAS (4 disks RAID10) for ware + UC apps 1GbE NIC 2010 Cisco and/or its affiliates. All rights reserved. 22

22 Not exhaustive, subject to change, see for latest UC app Unified CM Scale ( users* ) vcpu (cores) Usually GHz per core required vram (GB) vdisk (GB) Notes 1, x 80 UCS C200 or BE6K only 2, x 80 Not for use with C200/BE6K 7, x 80 10, x 80 Unity Connection Unified Presence x 160 1, x 160 5, x , x 146 Not for use with C200/BE6K 20, x 300 1, x 80 2, x 80 Not for use with C200/BE6K 5, x 80 Unified CCX x 146 UCS C200 or BE6K only x 146 Not for use with C200/BE6K x 146 * i.e. user count for particular values of BHCA, trace level, encryption, CTI and other factors. Actual supportable user count may vary by deployment Cisco and/or its affiliates. All rights reserved. 23

23 Policy still lives here: elines#application_co-residency_support_policy Three aspects: 1. Allowed App Mix on same physical server SAME RULES for TRC vs. specs-based UCS/HP/IBM 2. Allowed OVA choices DIFFERENT RULES for TRC vs. specs-based due to CPU differences 3. Max number of s on same physical server SAME RULES for TRC vs. specs-based to determine max, but specs-based might allow more s Note DAS IO bottlenecks may prevent very high counts even if CPU/RAM are sufficient 2010 Cisco and/or its affiliates. All rights reserved. 24

24 Which apps can share the same physical server? In general, any UC with UC from apps listed at But note: some UC apps restrict this, e.g. BE6K, CUCCE. See their rules on their docwiki child pages NMTG s UC Mgmt Suite (CUOM, CUSM, CUSSM, CUPM) counts as a UC app for this Note UCS C200 M2 TRC#1 for non-be6k no longer has special restrictions on UC App Mix SEPARATE PHYSICAL SERVER required for non-uc or 3 rd -party E.g. N1KV, ARC, SingleWire, vcenter, File/Print, Directory, CRM/ERP, Groupware, non-cucm TFTP, Nuance, etc. UC * UC * for ware vcenter for Nexus 1KV VSM for Solutions Plus/ CTDP app for Unaffiliated 3 rd -party app UC * UC * for ware vcenter for Nexus 1KV VSM for Solutions Plus/ CTDP app for Unaffiliated 3 rd -party app Different blades in same chassis OK UC * UC * for ware vcenter for Nexus 1KV VSM for Solutions Plus/ CTDP app for Unaffiliated 3 rd -party app UC * UC * for ware vcenter for Nexus 1KV VSM for Solutions Plus/ CTDP app for Unaffiliated 3 rd -party app Same blade, same chassis not OK 2010 Cisco and/or its affiliates. All rights reserved. 25

25 App to HW: some apps, e.g. CUCCE, don t allow any of their OVAs on certain TRCs See OVA to HW: Some OVAs are deliberately only for use with a particular TRC or CPU. See co-res policy page and Notes column in Why? Usually due to CPU model/speed dependencies. UCM 1K UCM 2.5K UCM 7.5K UCM 10K UCM 1K UCM 2.5K UCM 7.5K UCM 10K UCM 1K UCM 2.5K UCM 7.5K UCM 10K C200 M2 TRC#1 C200 M2 Specs-based B200/C210 M2 TRC or Specs-based (E5506, 2.13 GHz) (56xx, 2.53+GHz?) (E GHz on TRC 56xx/75xx, GHz on specs-based) 2010 Cisco and/or its affiliates. All rights reserved. 26

26 Small Medium Large Jumbo Jumbo + 1 reserved or Mixed sizes + 1 reserved or Mixed sizes V M V M Idle Idle V M Mixed sizes + 1 reserved or Mixed sizes V M V M Idle Idle V M or or 2:1 Large, e.g. UCM 10K or 4:1 Med., e.g. UCM 7.5K or 8:1 Small, e.g. UCM 2.5K V M Core V M Core V M Core V M Core V M Core V M Core V M Core V M Core 3:1 Large, e.g. UCM 10K or 6:1 Med., e.g. UCM 7.5K or 12:1 Small, e.g. UCM 2.5K V M Core V M Core V M Core V M Core V M Core V M Core V M Core V M Core V M Core V M Core V M Core V M Core Dual-socket, 4-core E.g. UCS C210 M2 TRC#1 with dual E5640 Dual-socket, 6-core E.g. UCS C210 M2 Specs-based with UC-supported CPU model and min speed 2010 Cisco and/or its affiliates. All rights reserved. 27

27 Virtual Software Switch Options UCS B200 ware vswitch ware dvswitch Cisco Nexus 1KV* vnic Host based (local) Distributed Distributed Software Switch 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 CNA ESXi Hypervisor vmnic EtherChannel EtherChannel EtherChannel Virtual PortChannel QoS Marking (DSCP/CoS) ACL SPAN RADIUS/TACACS+ No needed No needed needed for VSM FCoE * Strongly recommended for UC on UCS B-Series. Not required but recommended for UC on UCS C-Series. LAN SAN 2010 Cisco and/or its affiliates. All rights reserved. 28

28 Cisco Software Switch in Hypervisor Familiar network/ server operations & management model pswitch Enhanced diagnostic & monitoring capability Visibility direct to Nexus 1000V VSM Nexus 1000V VEM ESXi Nexus 1000V VEM ESXi 2010 Cisco and/or its affiliates. All rights reserved. 29

29 CUCM CTL Packet L3 L2:0 L3:CS3 CUCM marks traffic based on L3 DSCP values pswitch (CAT6K etc.) can do 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:CS Cisco and/or its affiliates. All rights reserved. 30 Physical switch maps L3 DSCP to L2 CoS

30 CUCM UCS 6100 doesn t look into L3 IP header DSCP/ToS setting in IP header is not altered by UCS 6100 sends packet to uplink pethernet switch Default QoS settings on UCS FCoE ( match cos 3 ) no drop policy Rest ( match any ) Best Effort Queue L2:0 L3:CS3 UCS 6100 CAT6K vswitch & UCS 6100 can not map L3 DSCP to L2 CoS 2010 Cisco and/or its affiliates. All rights reserved. 31

31 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 2010 Cisco and/or its affiliates. All rights reserved. 32

32 3 rd Party SAN Example Total capacity 28,000 IOPS 14,000 IOPS per controller 4 KByte block size Compute Layer Nexus 1000V Cisco UCS 6100 Fabric Interconnect 14,000 IOPS x (4KB) ~ 428 Mbps 600 Mbps throughput/controller 4x10GE 4x10GE 4x10GE 4x10GE 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 IOPS ~ IOPS * 4KB ~ 6.4 Mbps per 3 rd party layer FC Storage 2010 Cisco and/or its affiliates. All rights reserved. 33

33 2010 Cisco and/or its affiliates. All rights reserved. 34

34 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 machine layout on a blade and/or chassis Unity Connection requires one extra CPU core (vcpu) on blade 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 CoWAN rules/latency requirement are same Does not depend on CUCM code or hardware Cisco and/or its affiliates. All rights reserved. 35

35 SRND application-layer guidelines are same as when on MCS Redundancy Rules are the same Clustering over the WAN/latency numbers Mega Cluster supported in 8.5 Determine quantity/role of nodes For HA, No design checks validating proper placement of primary and secondary servers CUCCE private network requirement Mixed clusters of HP, IBM, UCS are supported Subject to common sense rules e.g. don t make Pub or Primary less powerful than Sub or Secondary Direct attach devices must be on physical MCS server -MOH Live audio stream -Tape Backup/Floppy New factors to consider for end-to-end QoS design/configuration 2010 Cisco and/or its affiliates. All rights reserved. 36

36 FROM CUCM / System Release To Unified CM 8.5 To UC System x Multi Hop thru 6.1(x)/7.1(x) Multi Hop thru 6.1(3) 5.1(2) Multi Hop thru 6.1(x)/7.1(x) NA 5.1(3) 2 Hop thru 7.1(3) NA 6.1(1) 2 Hop thru 6.1(x)/7.1(x) 2 Hop 6.1(2) 2 Hop thru 6.1(x)/7.1(x) NA 6.1(3) 2 Hop thru 6.1(x)/7.1(x) NA 6.1(4) Single Hop NA 6.1(5) Single Hop NA 7.0(1) 2 Hop thru 7.1(x) 2 Hop 7.1(2) 2 Hop thru 7.1(x) 2 Hop 7.1(3) Single Hop Single Hop, Multi stages/bwc supported 7.1(5) Single Hop NA 8.0(1) Single Hop Single Hop, Multi stages/bwc supported 8.0(2) / 8.0(3) Single Hop NA 2010 Cisco and/or its affiliates. All rights reserved. 37

37 ware Feature support ware feature support varies by application Some features are supported with Caveats, some Partially For example: Clone Virtual Machine Y (C) means: has to be powered off vmotion Y (C) means: vmotion supported for live traffic, calls shouldn t be dropped (but not guaranteed) Partial means: in maintenance mode only. ESXi Features CUCM CUC CUP CCX Clone Virtual Machine Y (C) Y (C) Y (C) Y (C) ware vmotion Y (C) Partial Partial Y (C) Resize Virtual Machine Partial Partial Partial Partial ware HA Y (C) Y (C) Y (C) Y (C) Boot From SAN Y (C) Y (C) Y (C) Y (C) ware DRS No No No No 2010 Cisco and/or its affiliates. All rights reserved. 38 Docwiki:

38 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.) 2010 Cisco and/or its affiliates. All rights reserved. 39

39 TAC Support Demarcation Server Hardware Shared Storage ware Cisco Application UC on UCS Tested Reference Configuration Cisco 3 rd -party Cisco 3 rd -party VCE VCE VCE Cisco UC on UCS Specs-based (including Vblock option) Cisco 3 rd -party Cisco 3 rd -party VCE VCE VCE Cisco 3 rd -party ware (HP, IBM) Specs-based 3 rd -party 3 rd -party 3 rd -party Cisco MCS 7800 Appliances Cisco N/A N/A Cisco Customer-provided MCS 7800 equivalent 3 rd party N/A N/A Cisco 2010 Cisco and/or its affiliates. All rights reserved. 40

40 Customer Example Primary Data Center CM PUB CM SUB CM SUB CM SUB TFTP MOH CER CM SUB UCxn CER UCxN CM SUB OLD NEW Hardware Nodes 62 Physical Servers ( EU, HQ clusters) 14 Approx. Software Version & Ucxn Version pairs -- Virtualized CER 2.0, Virtualized 2010 Cisco and/or its affiliates. All rights reserved. 41

41 Deployment Model Data Center # 1 CM PUB CM SUB CM SUB CM SUB TFTP MOH UCxN UCxn UCxn CER UCxn UCxn 2010 Cisco and/or its affiliates. All rights reserved. 42

42 Deployment Model Data Center #2 CM PUB CM SUB CM SUB CM SUB TFTP MOH Ucxn UCxn UCxn CER UCxn UCxn 2010 Cisco and/or its affiliates. All rights reserved. 43

43 Customer Design (3K phones) (11K phones) PSTN SIP Proxy CUSP IP WAN Unified Communications Manager Unity Connection Unified Presence Unified Contact Center Express Cisco UCS 5108 Chassis with UCS B200 Blade Servers Cisco UCS 6100 Fabric Interconnect Switch Cisco UCS C210 or C200 General-Purpose Rack-mount Server (400 phones) 2010 Cisco and/or its affiliates. All rights reserved. 44

44 HQ Details Blade #1 Blade #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 Blade #3 Blade #4 SUB-7 TFTP-1 CPU-1 CPU-2 CPU-1 CPU-2 UCCX-1 SUB-1 SUB-2 SUB-3 SUB-5 SUB-6 Leave idle for UCxn Leave idle for UCxn UCxn-1 Active UCxn-2 Active CUCM OVAs Messaging OVAs Presence OVAs Contact Center OVAs Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Blade #5 Blade #6 CPU-1 CPU-2 CPU-1 CPU-2 SUB-8 UCCX-2 CUP-1 SUB-4 TFTP-2 CUP-1 UCCX-1 CUP-2 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Blade Slot #7 Blade Slot #8 CPU-1 CPU-2 CPU-1 CPU-2 Spare blade slots available for non-uc workloads such as Cisco Nexus 1000V, ware vcenter or 3 rd -party workloads such as directories, , groupware or other business applications Cisco and/or its affiliates. All rights reserved. 45 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4

45 UCxn-1 UCxn-1 Branch Office Details CUCM OVAs Messaging OVAs Presence OVAs Rack Server #1 Rack Server #1 Contact Center OVAs CPU-1 CPU-2 CPU-1 CPU-2 PUB TFTP-1 SUB-1 CCX-2 PUB/TFTP Leave idle for UCxn CUP CCX-1 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Rack Server #2 CPU-1 CPU-2 Rack Server #2 CPU-1 CPU-2 TFTP-2 SUB-2 Leave idle for UCxn UCxn-1 SUB Leave idle for UCxn CCX-2 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Rack Server #3 CPU-1 CPU-2 CUP CCX-1 Leave idle for UCxn UCxn-2 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core Cisco and/or its affiliates. All rights reserved. 46

46 DAS: Rack Mount Server (Cisco C-Series) Popular DAS Protocol: SCSI iscsi: Access SCSI storage media using IP network Fibre Channel: The most popular SAN protocol today Cable distance ~ 2 km Popular speed - 4 Gb/s NAS (Network Attached Storage) uses NFS (Network File System) protocol over TCP/IP Host/ Server Storage Transport Storage Media DAS Computer System Application File System Volume Manager SCSI Device Driver SCSI Bus Adapter SCSI FC 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 2010 Cisco and/or its affiliates. All rights reserved. 47

47 NAS/SAN Array Best Practices for UC 4 to 8 UC s per LUN (max dependent on vdisks) PUB SUB1 UCCX1 UC #1 UC #2 UC #3 UCCX2 CUP1 CUP2 UC #4 UC #5 UC #6 Must be <2TB per LUN. Recommend 500GB to 1.5 TB. LUN 1 (720 GB) LUN 2 (720 GB) Use FC class disks with ~180 IOPS (e.g 450 GB 15K or 300 GB 15K) Single RAID5 Group (1.4 TB Usable Space) HDD 1 450gig 15K RPM HDD 2 450gig 15K RPM HDD 3 450gig 15K RPM HDD 4 450gig 15K RPM HDD 5 450gig 15K RPM 2010 Cisco and/or its affiliates. All rights reserved. 48

48 DAS Example: UCS C210 M2 TRC#1 Notes FS block size limits max vdisk size Could have >1 FS datastore on RAID volume PUB UC #1 UCCX1 UC #3 CUP1 UC #5 vsphere ESXi image FS Filestore (947 GB after FS overhead) Single RAID1 Volume Single RAID5 Volume (1022 GB after RAID overhead) HDD GB 15K RPM HDD GB 15K RPM HDD GB 15K RPM HDD GB 15K RPM HDD GB 15K RPM HDD GB 15K RPM HDD GB 15K RPM HDD GB 15K RPM HDD GB 15K RPM HDD GB 15K RPM 2010 Cisco and/or its affiliates. All rights reserved. 49

49 DAS Example: UCS C200 M2 TRC#1 for BE6K vsphere ESXi image PUB UC #1 UCCX1 UC #3 CUP1 UC #5 FS Filestore (1.8 TB after FS overhead) Single RAID10 Volume (2 TB after RAID overhead) HDD 1 1 TB 7.2K RPM HDD 2 1 TB 7.2K RPM HDD 3 1 TB 7.2K RPM HDD 4 1 TB 7.2K RPM 2010 Cisco and/or its affiliates. All rights reserved. 50

50 UC Application Co-residency See for latest Based on supported OVA for download OVA reserves cores, RAM, etc. to s Basic rule of thumb, fill up blade until out of capacity If blade contains for messaging, must reserve core for ESXi Hardware oversubscription not supported 2010 Cisco and/or its affiliates. All rights reserved. 51

51 Virtual Machine Sizing Virtual Machine virtual hardware defined by an template: vcpu, vram, vdisk, vnics Capacity An template is associated with a specific capacity templates are packaged in a OVA file There are usually different template per release. For example: CUCM_8.0_vmv7_v2.1.ova CUCM_8.5_vmv7_v2.1.ova CUCM_8.6_vmv7_v1.5.ova Includes product, product version, ware hardware version, template version 2010 Cisco and/or its affiliates. All rights reserved. 52

52 2010 Cisco and/or its affiliates. All rights reserved. 53

53 Customer-accessible UC on UCS: and and and (UCS page) UCS in general: Vblocks & Virtual Computing Environment: and FlexPods: Cisco Infrastructure as a Service (IaaS) Portal: Cisco Unified Service Delivery Portal: CUCM on Virtual Servers (summary of what s new/different when virtualized ): Virtualization and UCS 101 : UC on UCS tech value : 74.html 2010 Cisco and/or its affiliates. All rights reserved. 54

54 Partner Central: Servers, OS and Virtualization Partner Community: Servers, OS and Virtualization Design info: and What s new, what s different when on ware customer doc: Product Literature: and Ordering Guide: Virtual Computing Environment Portal: Cisco Infrastructure as a Service (IaaS) Portal: Cisco and/or its affiliates. All rights reserved. 55

55