1696 UC On UCS VoE FEB2011

UC on UCS Update
Feb 17, 2011
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 120 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 ones interest, some questions might be deferred towards the end
2010 Cisco and/or its affiliates. All rights reserved. Cisco Public
2010 Cisco and/or its affiliates. All rights reserved.
Cisco Public
Virtual DC, UCS Server Virtualization Architecture

UCS Hardware, LAN/SAN Interconnect UC on UCS Roadmap
Deployment models, scalability and capacity planning VM Sizing and Placement SAN & VMware Design Best Practices Network considerations , QoS, Redundancy / High Availability
Case Study
Migration Strategies
4
Cisco Public
Fundamentals of UC on UCS Architecture
Presentation_ID
Cisco Confidential
Prerequisites
Do you know the basics of CUCM or CallManager Virtualization/VMware Answer Yes. Thats 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
Storage Area Networking
Cisco UCS
Cisco Public
UC on UCS - Virtual DC Overview

Network vs. Server Virtualization
UC Application
UC Application
UC Application
2 3
VMware ESXi , Unified Computing System
Cisco Public
Compute/Server
Presentation_ID
Cisco Confidential
Cisco UCS B-Series Blade Servers

UCS B440
UCS B230
UCS B200 UCS B250
Blade
UCS B440 M1
CPU
4x Intel 7500
2x Intel 5540 (5640) 2x Intel 6500 or 7500 2x Intel 5540 (5640)
Size
Full Width
Memory
32 DIMM 256 GB 48 DIMM 384 GB 32 DIMM 256 GB 12 DIMM 96GB
Disks
4 3.5 SAS/SATA Drives 2x 3.5 SAS Drives 2x 3.5 SSD Drives
VMs
NA
UCS B250 M1(M2)
Full Width
NA
UCS B230 M1
Half Size
NA
UCS B200 M1(M2)
Half Width
2x 3.5 SAS Drives

Cisco Public
4
9
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
10
Cisco UCS C-Series Rack-Mount Servers

UCS C460 M1
UCS C250 M1
UCS C210 M1(M2) UCS C200 M2
Rack Server
UCS C460 M1 UCS C250 M1 (memory intensive) UCS C210 M1(M2)
CPU
4x Intel 7500 2x Intel 5540 2x Intel 5540 (5640) 2x Intel 5506
Size
4RU 2RU
Memory
64 DIMM 512 GB 48 DIMM 384 GB 12 DIMM 96 GB 12 DIMM 96GB
Disks
12 SAS/SATA Drives 8 SFF SAS/SATA Drives 16 SFF SAS/SATA Drives 4 x 3.5 SAS/SATA Drives
Cisco Public
Adaptor
10 PCIe 5 PCIe
VMs
NA NA
2RU
5 PCIe
UCS C200 M2
1RU
2 PCIe
4
11
Server Sourcing Strategy shift to Cisco on Cisco

Co-residency Virtualized
UCS B200
UCS C200 M2
Co-residency Bare-metal
UCS C210 M1/M2
MCS 7828
Standalone Bare-metal
Standalone Virtualized
MCS 7816
MCS 7825
MCS 7835
MCS 7845
Max Supportable Users
Cisco Public
12
1
Virtual Design Differences
Presentation_ID
Cisco Confidential
13
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
Cisco Public
14
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

Cisco Public
15
Virtual Machine Specification

Number of VMs typically the same as physical MCSs 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
Cisco Public
16
UC on UCS Tested Reference Configurations (TRC)
Presentation_ID
Cisco Confidential
17
Cisco UCS B200M2 (UCS-B200M2-VCS1) B200M2 TRC Example

UCS 5108 Chassis
UCS 2100 Fabric Extender
UCS 6100XP Fabric Interconnect Switch
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
10GbE
FC
Catalyst
PSTN/ PTT
LAN
Nexus
SAN
Storage Array (for UC Apps)
MDS
FC
Rest of Intranet
Management: - UCS Manager - vSphere/vCenter

Cisco Public
18
Cisco UCS C200M2 (UCS-C200M2-VCD2) C200M2 TRC Example

Configuration: - Dual Quad Core E5506 - 4 x 1TB SAS Drives - 24 GB RAM - 2 x 1GB NICs Ethernet - 1 x 1GB NIC for CIMC - Supports multiple VMs
UCS C200 M2
10/100/1GbE
Catalyst
PSTN/ PTT
LAN
Management: - CIMC for UCS - vSphere/vCenter
Rest of Intranet
Cisco Public
19
Tested Reference Configurations Summary

Server Model/Generation & Collaboration SKU Tested Reference Configuration B200 M2 B200 M1 C210 M2 C210 M1 TRC #1 TRC #1 TRC #1 TRC #2 TRC #1 TRC #2 TRC #3 C200 M2 TRC #1 UCS-B200M2-VCS1 UCS-B200M1-VCS1 UCS-C210M2-VCD2 DC SKU only UCS-C210M1-VCD1 UCS-C210M1-VCD2 DC SKU only UCS-C200M2-VCD2 Notes Co-res, SAN Co-res, SAN Co-res, DAS Co-res, SAN Single VM, DAS Co-res, DAS Co-res, SAN 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)
20
Platform Roadmap (subject to change)

Upgrade via API
For CUCM 8.6 on MCS or VMware
Expanded VMware Support

For subset of UC on UCS apps ESXi 4.1 version compatibility Boot from SAN vMotion Clone VM
Expanded VMware Platform Support

For subset of UC on UCS apps Specs-based support for UCS, HP, IBM UCS Express (SRE-V 900) for Govt/Military deployments All C-series NIC, C.N.A, VIC, HBA options Storage: iSCSI, NFS, FCoE Exception-less Vblock support
Shipping
Q1CY11
Mid-CY11
Q4CY11
1HCY12
UC on UCS (TRCs)
UCS B200 M2 (FC SAN) UCS C210 M2 (DAS-only, or FC SAN) UCS C200 M2 (DAS-only)
Appliances
MCS 7816/25/28-I4/I5 and 7835/45-I3 HP Software-only DC Power option on IBM x3650-M2
Committed for CUCM

21
Roadmap to Server Hardware Independence

UC 8.0(1) Thru 2009 None UC 8.0(2) 1HCY10 Some UC 8.5(1) 2HCY10 More UC 8.5/8.6 2HCY11 A Lot Future Fully
MCS 7800 Vendor Make/Model
UC on UCS Prescribed Prescribed
Lightweight Process
Specs-based Support Phase 1
Specs-based Support Phase X Open
Open within supported vendors
Form Factor
Generation CPU Model CPU Cores Memory Prescribed Prescribed Prescribed
Prescribed
Prescribed Same or better Prescribed Same or greater
Rack/Blade within supported vendors

Open within supported models Min or better Open Min or better Open Open
Disk Size/Speed
Disk Qty/RAID Adapter Choice Vendor Parts List
Prescribed
Prescribed Prescribed Prescribed
Same or greater
Prescribed B-series: open C-series: prescribed
Min or better
Min or better TBD subject to Storage roadmap
Open
TBD subject to Storage roadmap Open Open
22
Flexible (subject to Specs restrictions)

2
Planning and Design
Presentation_ID
Cisco Confidential
23
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
http://www.cisco.com/go/ucsrnd 2010 Cisco and/or its affiliates. All rights reserved.
Cisco Public
24
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.)
Cisco Public
25
Virtual Machine Sizing and Placement
Presentation_ID
Cisco Confidential
26
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

http://en.wikipedia.org/wiki/Open_Virtualization_Format 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public
27
UC VM Configuration 8.5(1)
Product CUCM UnityConnection Scale (users) 7,500 2,500 20,000 10,000 5,000 1,000 500 Unity CUP UCCX/IPIVR 15,000 5,000 5,000 2,500 400 agents 300 agents
1 vCPU for Unity Connection ESXi scheduler SME = CUCM Session Management Edition
vCPU 2 1 7 4 2 1 1 4 2 4 2 4 2
vRAM (GB) 6 2.25 8 4 4 4 2 4 4 4 4 8 4
vDisk (GB) 2 x 80 1 x 80 2 x 300 2 x 146 1 x 200 1 x 160 1 x 160 4 x 24 4 x 24 2 x80 1 x 80 2 x 146 2 x 146
28
UC VM Configurations 8.5(1)
Product CER Scale (users) 30,000 vCPU Cores 2 vRAM (GB) 6 vDisk (GB) 2 x 80
20,000
12,000
1
1
2.25
2.25
1 x 80
1 x 80
CMBE 6000 (C200) VM Configurations 8.5(1)

Product CUCM Scale (users) 1,000 vCPU Cores 2 (600 MHz *R) vRAM (GB) 4 (*R) vDisk (GB) 1 x 80
UnityConnection
CUP UCCX/IPIVR
1,000
1,000 100
1
1 (800 MHz *R) 2
4
2 4
1 x 160
1 x 80 2 x 146
* R = Reserved
29
UCCE/CVP VM Configuration 8.5(1)

CVP
Component & Scale * vCPU vRAM (GB) vDisk (GB) vNIC
Call+VXML Server (900 Calls) Reporting (Large) (840 Msg/sec) OAMP Server
4 4 2
4 4 2
1 x 146 1 x 72 1 x 438 1 x 20
1 1 1
UCCE
Component & Scale * vCPU vRAM (GB) vDisk (GB) vNIC
Router 8000 agents Logger 8000 users
2 4
4 4
1 x 80 1 x150
2 2
Agent PG 2000 users

VRU PG 9600 ports, 10 PIMs AW Server (25 clients)
2
2 1
4
2 2
1 x 80
1 x 80 1 x 40
Cisco Public
2
2 1
30
Virtualized Server Placement

Hypothetical C-Series Layout Small site, 500 users w/ VM and 50 Contact Center agents Consolidate 5 servers into 1 C-Series
Chassis 1 CPU-1 (standby) CPU-2
PROs:
5:1 server consolidation
UCCx
(PRI)
PUB1
SUB1
UCxn
UCxn
Core 1
Core 2
Core 3
Core 4
Core 1
Core 2
CUP
ESXi UCxn
(Act)
(SEC)
(PRI)
2 RUs
Core 3
Core 4
CONs:
Single point of failure! Got to pass the Duh test
Cisco Public
31
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
Rack Server #1 CPU-1 CPU-2
PROs:
7:2 server consolidation
CCX-1
UCxn
ESXi UCxn
(Act)
CUP
PUB/ TFTP
Core 1 Core 2
4 RUs
App Redundancy Extra server at no HW cost
Core 3
Core 4
Core 1
Core 2
Core 3
Core 4
Rack Server #2 CPU-1 (Stnadby) CPU-2
CONs:
CCX-2
UCxn
Core 1
Core 2
Core 3
ESXi UCxn
SUB
Extra server
Core 4
Core 1
Core 2
Core 3
Core 4
Cisco Public
32
Hypothetical blade/chassis layout example

Blade 1 CPU-1 CPU-2 CPU-1 Blade 2 CPU-2
PUB1
Core 1 Core 2
SUB1
(PRI) Core 3 Core 4
SUB2
(SEC) Core 1 Core 2
SUB3
(PRI) Core 3 Core 4
SUB4
(SEC)
CCX
Core 3 Core 4 Core 1
CUP
Core 1
Core 2
Blade 3
CPU-1 ESXi UCxn
Core 1
Blade 4 CPU-2 CPU-1 CPU-2
UCxn Active Srvr

UCxn Active Srvr

Core 1 Core 2 Core 3 Core 4
DHCP
Core 1 Core 2
TFTP
Core 3 Core 4
SQL
Core 1 Core 2
DNS
Core 3 Core 4
Blade 6 CPU-2
Spare
Core 1 Core 2 Core 3 Core 4 Core 1 Core 2 Core 3 Core 4 Core 1 Core 2 Core 3
Spare
Core 4 Core 1 Core 2 Core 3 Core 4
Blade 8 CPU-2
Spare
Core 1 Core 2 Core 3 Core 4 Core 1 Core 2 Core 3 Core 4 Core 1 Core 2 Core 3
Spare
Core 4 Core 1 Core 2 Core 3 Core 4
Maximum Cisco CUCM appsreserved. B200M1 Blade 2010 4 and/or its affiliates. All rights per Cisco Public
33
Hypothetical blade/chassis layout example

Blade 1 CPU-1 CPU-2 CPU-1 ESXi UCxn
Core 4
Blade 2 CPU-2
SUB1
(PRI) Core 1 Core 2 Core 3 Core 4
UCxn Active Srvr

PUB
Core 1
Core 2
SUB3
(PRI) Core 3 Core 4 Core 1 Core 2
CUP
Core 3 Core 4
Blade 3
CPU-1 CPU-2 ESXi CPU-1
Blade 4 CPU-2
SUB2
(SEC) Core 1 Core 2 Core 3 Core 4
UCxn Active Srvr

UCx n
Core 4
DHCP
Core 1 Core 2
TFTP
Core 3 Core 4
SQL
Core 1 Core 2
DNS
Core 3 Core 4
Blade 6 CPU-2
Spare/Empty
Core 1 Core 2 Core 3 Core 4 Core 1 Core 2 Core 3 Core 4
SUB4
(SEC) Core 1 Core 2
CCX
Core 3 Core 4 Core 1 Core 2
CUP
Core 3 Core 4
Blade 8 CPU-2
Spare/Empty
Core 1 Core 2 Core 3 Core 4 Core 1 Core 2 Core 3 Core 4 Core 1 Core 2
Spare/Empty
Core 3 Core 4 Core 1 Core 2 Core 3 Core 4
Maximum Cisco CUCM appsreserved. B200M1 Blade 2010 4 and/or its affiliates. All rights per Cisco Public
34
UCS Server Selection
Presentation_ID
Cisco Confidential
35
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
Cisco Public
36
Server Selection Guideline

Yes
UCS B200
1
Yes
Already have DC/SAN? $$
> 24 vCPU?
No
C210Mx SAN
No
Yes
Building DC for UC?
Yes Start
> 10 servers
No
C210Mx DAS
No
Yes
3 1 2 3
Large
Medium
> 8vCPU or > 1000 users
No
C200M2/ BE6000
Small
37
VMware/vCenter Design Best Practices
Presentation_ID
Cisco Confidential
38
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 VM Template (OVAs) Copy Virtual Machine CUCM Yes Yes UnityConn Yes Yes
Resize Virtual Machine VMware Hot Add

VMware HA VMware vMotion VMware DRS P2V or vCenter Converter
Partial No
Yes Partial No No
Partial No
Yes Partial No No
Partial = Limited support (See following URL for details) http://docwiki.cisco.com/wiki/Unified_Communications_VMWare_Requirements 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public
39
LAN/SAN Design Best Practices
Presentation_ID
Cisco Confidential
40
Networking in Virtual Environment
pSwitch
NIC Teaming vmNIC
Physical Wires
Physical NIC
Physical Server
ESXi
Port Group
Hypervisor
vSwitch
vNIC
Soft Switch
Virtual NIC
VM
VM
VM
VMware
Generic
Cisco Public
41
Virtual Software Switch Options

VMware vSwitch
Host based (local) IEEE 802.1Q VLAN tagging VLANs only visible to local ESXi host EtherChannel ----No VM needed
UCS B200
VMware dvSwitch
Distributed IEEE 802.1Q VLAN tagging VLANs visible to all ESXi hosts EtherChannel ----No VM needed
Cisco Nexus 1KV

Distributed IEEE 802.1Q VLAN tagging VLANs visible to all ESXi hosts EtherChannel Virtual PortChannel QoS Marking (DSCP/CoS) ACL SPAN RADIUS/TACACS+ VM needed
VM vNIC
Software Switch
ESXi Hypervisor CNA vmNIC
FCoE
vCenter not needed
vCenter needed
vCenter needed
LAN SAN
42
Cisco Public
Nexus 1000v
Cisco Software Switch in Hypervisor Familiar network/ server operations & management model Enhanced diagnostic & monitoring capability Visibility direct to VM
pSwitch
Nexus 1000V VSM
ESXi
Nexus 1000V VEM Nexus 1000V VEM
ESXi
Cisco Public
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)
C S 3
dc1-access-6k(config)#mls qos map dscp-cos 24 to 3 dc1-access-6k(config)#mls qos map dscp-cos 46 to 5
CAT6K
L2:3 L3:CS3
Physicaland/or its affiliates. All rights reserved. to L2 CoS switch maps L3 DSCP 2010 Cisco
Cisco Public
44
UC QoS Concept With B-Series

6100 switch in middle L2 based prioritization
CUCM
L2:0
L3:CS3
DSCP value in IP header is not altered by 6100

UCS 6100
6100 sends packet to Physical ethernet switch Default QoS settings on UCS
FC (match cos 3) no drop policy
Rest (match any) Best Effort Queue
CAT6K
vSwitch &2010 Cisco and/or its affiliates. All rightsmap L3 DSCP to L2 CoS UCS 6100 can not reserved. Cisco Public
45
B-Series Potential Congestion Scenario
Up to 20 UCS 5108 Chassis FCoE UCS-6100 FI Switch Fibre Channel
UCS B200 Blade Server
10Gbps Ethernet
Catalyst Ethernet Switch

UC Apps Disc Space IP traffic competing with FC traffic
SAN Disc Array

Cisco Public
46
CUCM
B-Series QoS Best Practices

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
FC Network Best Practices/Guidelines

3rd 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 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
Compute Layer
Cisco UCS 6100 Fabric Interconnect
Nexus 1000V
4x10GE
4x10G E 4x10G E
4x10GE
UCS 5100 Blade Server
Cisco SAN Switch
FC
FC
SP-A
SP-B
3rd party layer
CUCM VM IOPS ~ 200 200 IOPS * 4KB ~ 6.4 Mbps per VM

FC Storage
48
SAN Array LUN Best Practices / Guidelines

HD Recommendation LUN Size Restriction UC VM App Per LUN 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
LUN Size Recommendation PUB

VM1
Between 500 GB & 1.5 TB
SUB1
VM2
UCCX1
UCCX2
CUP1
VM2
CUP2
VM3
VM3
VM1
LUN1 720 GB LUN 1 (720 GB)
LUN2 720 LUN 2 (720 GB) 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
Cisco Public
HD 5 450gig 15K RPM

49
3
Implement/Operate
Presentation_ID
Cisco Confidential Remember! OVA is your MCS Server Now
50
Case Study
Presentation_ID
Cisco Confidential
51
Deployment Model
Distributed Call Processing
Applications (UnityC, UCCX, CUP)
2000 IP Phones
CUCM cluster
UnityC, UCCX, CUP
CUCM cluster
PSTN
CUSP
IP WAN
CUCM cluster
SIP Proxy
12,000 IP Phones
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
Cisco Public
CUCM Server Requirement
Input
12K Phones 10K Messaging Users 10K CUPC Clients
240 UCCX Agents 10 Supervisors
MCS Servers
Unity Connection Server Requirement
CUCM UCxn CUP 11 2 2
UCCX
Total
2
17
CUP Server Requirement
UCCX Server Requirement
Cisco Public
53
Server Requirement 12K Devices/Users

B200-1 CPU-1
PUB
Core1 Core2
Input
B200-2 CPU-2
SUB-1
Core1 Core2
CPU-1
SUB-5
Core1 Core2 Core3
CPU-2
ESXi UCxn
Core4 Core1
TFTP-1
Core3 Core4
SUB-3
Core3 Core4
UCxn-1 Active
Core2 Core3 Core4
B200-3 CPU-1
SUB-7
Core1 Core2
B200-4 CPU-2
SUB-2
Core1 Core2 Core3 Core4
MCS Servers
CUCM UCxn CUP 11 2 2
CPU-1
SUB-6
Core1 Core2 Core3
CPU-2
ESXi UCxn
Core4 Core1
UCCX-1
Core3 Core4
UCxn-2 Active
Core2 Core3 Core4
UCCX
Total
2
17
B200-5 CPU-1
SUB-8
Core1 Core2
B200-6 CPU-2
CUP-1
CPU-1
SUB-4
Core1 Core2
CPU-2
CUP-1 CUP-2 UCCX-1 CUP-2
UCCX-2
Core3 Core4
TFTP-2
Core3 Core4
B200 Total 6 Servers
CUCM CUC CUP UCCX
2 vCPU 6 GB RAM 4 vCPU 4 GB RAM 4 vCPU 4 GB RAM 2 vCPU 4 GB RAM
7.5K users 10K users 5K users 300 agents

Cisco Public
54
Input
MCS Servers
CUCM CUC CUP 5 2 1
UCCX
Total
2
10

2 2
55
Server Requirement 2K Devices/Users

C210-1 CPU-1
PUB
Core1 Core2
Input
C210-2 CPU-2
SUB-1
Core1 Core2
CPU-1
TFTP-2
Core1 Core2
CPU-2
ESXi UCxn
Core1 Core2
TFTP-1
Core3 Core4
CCX-2
Core3 Core4
SUB-2
Core3 Core4
CUC-1 Primary
Core3 Core4
MCS Servers
CUCM 5 2 1 CUC CUP
C210-3 CPU-1
CUP
Core1 Core2
CPU-2
ESXi UCxn
Core1 Core2
CCX-1
Core3 Core4
CUC-2 Second
Core3 Core4
UCCX
Total
2
10
C210 Total 3 Servers
CUCM CUC CUP UCCX
7.5K users 5K users 2.5K users 100 agents

Cisco Public
56

1
3
Input
1
500 Phones 500 Messaging Users 500 CUPC Clients
MCS Servers
CUCM UnityC CUP 2 2 1
UCCX
2
7
Total
Cisco Public
57
Server Requirement 500 Devices/Users

C200-1 CPU-1
PUB/TFTP CUC-1
Core1 Core2
Input
500 Phones 500 Messaging Users 500 CUPC Clients
CPU-2
CUP CCX-1 CUP
Core4 Core1 Core2 Core3 Core4
ESXi CUC
Core3
MCS Servers
CUCM 2 2 1 UnityC CUP
C200-2 CPU-1
SUB
Core1
CPU-2
CCX-2
Core4 Core1 Core2 Core3 Core4
CUC-1
Core2
ESXi CUC
Core3
UCCX
Total
2
7
C200 Total 2 Servers
CUCM CUC CUP UCCX
1000 users 500 users 500 users 100 agents

Cisco Public
58
Migration Strategy
Presentation_ID
Cisco Confidential
59
Migration Options-All Servers

Start:
CUCM on v7.1(3)
Upgrade
Upgrade MCS pub to 8.0(2) or later* DRS backup Publisher
UCS Install
Install CUCM 8.0(2) on UCS DRS Restore data
Install subscribers on UCS

* Bridged server option
60
Migration Options- Publisher Only

Start:
CUCM on v8.0(2) or later DRS Backup the Publisher
Install
CUCM v8.0(2) or later on UCS DRS Restore data
Verify replication (correct if needed)
* Bridged server option

61
Migration Options-Subscriber only

Start:
CUCM on v8.0(2) or later Decommision backup sub
Install
Install CUCM v8.0(2) or later Failover to new backup
Decomission primary sub

Install CUCM v8.02 or later
Cisco Public
62
Migration Options- Existing Expansion

Start:
CUCM on v8.0(2) or later
Install
Install CUCM (must match pub version) Mix Physical and Virtual
Cisco Public
63
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)
Cisco Public
64
Deploying UC Virtual Machine B&C Series

2
OVF Templates Provided by Cisco
3 4
ISO
UCS C210 M1
UCS B200 M1
UC VM OVF Templates: its affiliates. All rights reserved. 2010 Cisco and/or http://www.cisco.com/go/uc-virtualized Cisco Public
65
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
66
Questions ?
Cisco Public
67
External Resources
Unified Communications Network Design Guide (SRND)
http://www.cisco.com/go/ucdesign
UC Virtualization
http://www.cisco.com/go/uc-virtualized
Supported UCS Hardware Specs

http://www.cisco.com/go/swonly
UC on UCS Solution Overview and Ordering Information

http://www.cisco.com/go/uconucs
Customer Success Story

Station Casino (12K Phones) http://newsroom.cisco.com/dlls/2010/prod_071310.html
Cisco Public
68
Cisco Public
69

1696 UC On UCS VoE FEB2011

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1696 UC On UCS VoE FEB2011

Uploaded by

Copyright:

Available Formats

UC on UCS Update

Feb 17, 2011

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

Virtual DC, UCS Server Virtualization Architecture

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

Fundamentals of UC on UCS Architecture

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

Storage Area Networking

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

UC on UCS - Virtual DC Overview

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

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

Cisco UCS B-Series Blade Servers

UCS B200 UCS B250

UCS B250 M1(M2)

UCS B200 M1(M2)

2x 3.5 SAS Drives

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

Compute: UCS B Series Components

Fabric Interconnect Switch

Fabric Extender (Up to 2)

UCS 5108 Blade Server Chassis

UCS B200M1 half size UCS B250M1 full size

Cisco UCS C-Series Rack-Mount Servers

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

Server Sourcing Strategy shift to Cisco on Cisco

UCS C210 M1/M2

Max Supportable Users

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

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

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

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

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

Cluster Based on Virtual Resources

MCS Servers CPU/Mem/HDD

Virtual Machines (OVA) vCPU/vMem/SAN or DAS

Virtual Machine Specification

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

UC on UCS Tested Reference Configurations (TRC)

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

Cisco UCS B200M2 (UCS-B200M2-VCS1) B200M2 TRC Example

UCS 2100 Fabric Extender

UCS 6100XP Fabric Interconnect Switch

Management: - UCS Manager - vSphere/vCenter

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

Cisco UCS C200M2 (UCS-C200M2-VCD2) C200M2 TRC Example

Management: - CIMC for UCS - vSphere/vCenter

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

Tested Reference Configurations Summary

Platform Roadmap (subject to change)

Expanded VMware Support

Expanded VMware Platform Support

Committed for CUCM

Roadmap to Server Hardware Independence

MCS 7800 Vendor Make/Model

UC on UCS Prescribed Prescribed

Specs-based Support Phase 1

Specs-based Support Phase X Open

Open within supported vendors

Rack/Blade within supported vendors

Flexible (subject to Specs restrictions)

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