VoE UC 8.5 Virtualization External

© 2009 Cisco Systems, Inc. All rights reserved. Cisco Confidential Presentation_ID 1

Unified Communications on

Unified Computing System

v8.5 Engineering TOI

Scott Meyer Technical Solutions Architect Voice CCIE #14649 Virtual Expert Team Architecture-Vertical Channels [email protected] Date: December 15, 2010

Cisco Confidential Do Not Disseminate Pursuant to the Terms of the Parties Non-Disclosure Agreement


Agenda Engineering Transfer of Information (TOI)   Virtualization Defined

  Unified Computing System

  UC on UCS Strategy

  Virtualization

  Solution Details

  Go To Market

  Partner Readiness


What is Virtualization? Defined

Refers to the abstraction of computer resources

Software implementation of a computer that executes programs like a real machine


Cisco Unified Computing System

System Overview


Cisco Unified Computing System (UCS) B-Series (Blade)

5 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Confidential Presentation_ID

A single system that unifies  Compute: Industry standard x86  Network: Unified fabric  Virtualization: Control, scale, performance  Storage Access: Wire once for SAN, NAS, iSCSI

Embedded management   Increase scalability without added complexity  Dynamic resource provisioning  Ability to integrate with broad partner ecosystem

Energy efficient  Fewer servers, switches, adapters, cables  Lower power and cooling requirements   Increase compute efficiency by removing I/O and

memory bottlenecks


UCS Manager Embedded in Fabric Switch

Fabric Switch 20 Port 10Gb FCoE 40 Port 10Gb FCoE

Fabric Extender Logically part of Fabric Switch Inserts into Blade Enclosure

Enclosure Flexible bay configurations Logically part of Fabric Switch

Server Blade Different blade types Mix blade types within enclosure

Adapters Three adapter options Mix adapters within blade

Cisco UCS B-Series Physical Building Blocks


Blade CPU Size Memory Disks VMs

UCS B440 M1 4x Intel 7500 Full Width

32 DIMM 256 GB

4 3.5” SAS/SATA Drives NA

UCS B250 M1 / M2 2x Intel 5540 (5640) Full Width

48 DIMM 384 GB

2x 3.5” SAS Drives NA

UCS B230 M1 2x Intel 6500 or 7500 Half Size 32 DIMM

256 GB 2x 3.5” SSD

Drives NA

UCS B200 M1 / M2 2x Intel 5540

(5640) Half Width 12 DIMM

96GB 2x 3.5” SAS

Drives 4

UCS B200

UCS B440

Cisco UCS B-Series Blade Servers

UCS B250

UCS B230


Rack Server CPU Size Memory Disks Adaptor VMs

UCS C460 M1 4x Intel 7500 4RU 64 DIMM 512 GB

12 SAS/SATA Drives 10 PCIe NA

UCS C250 M1 (memory intensive)

2x Intel 5540 2RU 48 DIMM 384 GB

8 SFF SAS/SATA Drives 5 PCIe NA

UCS C210 M1 / M2 2x Intel 5540 (5640) 2RU

12 DIMM 96 GB

16 SFF SAS/SATA Drives 5 PCIe 4

UCS C200 M2 2x Intel 5640

1RU 12 DIMM

96GB 4 x 3.5” SAS/SATA Drives 2 PCIe 4

UCS C200

UCS C210

UCS C250

Cisco UCS C-Series Rack-Mount Servers

UCS C460


Cisco UCS C-Series Hardware Redundancy

4) Redundant Application HDD RAID 5

3) Redundant ESXi HDD RAID 1

2) Redundant Network Connections FC (Host Bus Adapter), NIC

1) Redundant Power


Cisco UCS Compared with MCS 7800

MCS 7800

2 to 4 MCS 7835/45

2 to 4 MCS 7816/25/28

Single UCS B200 or C210 with co-residency

or

Single UCS C200 with co-residency

UC on UCS + VMware


Cisco UCS Detailed Comparison

UC on MCS 7845 UC on UCS B-series UC on UCS C-series Cisco on OEM Server, no VMware Cisco on Cisco Server, VMware-only

All major UC apps supported Phased support of UC apps

Standalone applications only Application Co-residency supported

Short life Running on VMware can artificially extend life

Many SKUs per server Just a few SKUs per server

Hardware/Software Incompatiblities Less Frequent Incompatibilities due to VMware

Local disks only SAN and Local disks required Local disks with Optional SAN

Investment for 4 CUCM nodes is $96K Minimum investment ~$74-129K (HW + VMware + % of SAN)

Minimum investment ~$78K (HW + VMware)

Investment for 8 CUCM nodes is $192K Minimum investment ~$94-149K (HW + VMware + % of SAN)

Minimum investment ~$156K (HW + VMware)

Appliance Not an appliance

No Server/Storage/Virtualization expertise required.

Requires Server, SAN, VMware expertise

Requires Server and some VMware expertise


UC on UCS UC on UCS

− Vision / Strategy − Roadmap


UCS B200 M2 Blade UCS B200 M1 Blade

UCS B250 M2 Blade UCS B250 M1 Blade

UCS C200 M2 UCS C200 M1



Memory Intensive

Computing

General Purpose

Computing

Processor & Memory Intensive

Computing; Mission

Critical RAS UCS C460 M1

UCS B440 M1 Blade

Blade Form Factor Rack-Mount Form Factor

Supported for select Collaboration applications Support is Planned, not Committed Support not Planned

B230 M1

Collaboration Support on UCS Portfolio Snapshot


Cisco UC Virtualization B-Series Enterprise Solution   Cisco Unified Communications (UC) 8.0(2) or greater

Unified Communications Manager

Unity Connection / Unity

Unified Presence

Unified Contact Center (Enterprise & Express)

Customer Voice Portal

  On Cisco Unified Computing System (UCS) New Cisco offered servers

Blade server (B-Series) for initial offer

  “Virtualized” leveraging VMware Leading industry vendor of software

Provides software layer to provide abstraction

Available since April 16, 2010

* MC

LAN SAN

PSTN Disk Array

UCS Blade Server Chassis with 1-8 “Half-width” blades


Cisco UC Virtualization C-Series Solution

  Initial Virtualized MCS solution, UC 8.0(3) • New Cisco C210 server, VCD2

•  Local Disk or SAN allowed

• Deployed like MCS solution today, but on VMware

• Multiple UC applications per server, 4:1 max Any combination of UC Manager and Unity Connection

•  OR Contact Center Express, 1:1 max

Available since July 23, 2010

Equivalent to MCS-7845 10x disks, increased RAM


UC Virtualization Pre-8.5 Where are we?!?!?

 Early Adopters

  Initial offering – April B-series offering

Co-res with major UC apps

 Move away from HP – June C-series offering

Limited UC app support

 Has been complex Four dimension matrix

What works with what?!?


UC on UCS Roadmap Details – UC 8.5  Updating to M2 processors (B200 & C210)

M1 Quad Core vs. M2 Hex Core

…but no increase of capacity with UC 8.5

  Introducing new C200 M2 platform 1RU model with price point for smaller customers

User count limited to 1000 users per VM

  Increased C-Series support w/ Co-Residency, 4:1 max CUP & UCCX on C210 and C200

UCCE, UCCE Apps and CVP on C210

 Additional applications include CER & CUAE Both B & C Series

Up to 4:1 co-residency support

Dec/Jan 2010


UC Virtualization Outstanding Items

 Virtualize rest of UC Applications MeetingPlace, etc

 ESXi 4.1 support (soon after 8.5 release)

  3rd party UC Apps ARC is big one

 More OVA options Small ones for more apps per server

Jumbo ones for expanded users per app

 QoS Well defined designs missing


UC on UCS Virtualization Beyond UC 8.5

Shipping Orderable Future • VMware feature support VMotion, DRS, Storage VMotion, Snapshots, Fault Tolerance

• More Server options (specs based) UCS (B250, C250)

3rd-party servers (IBM & HP)

• More Storage options Additional SAN’s

iSCSI, NAS/NFS

Boot from SAN

• Additional hypervisors

Hyper-V, RH Virtualization, Sun xVM


UC on UCS Virtualization

VMware ESXi VMkernel


VMware Licensing

Comparison between the various VMware vSphere Versions: http://www.vmware.com/files/pdf/key_features_vsphere.pdf


Deploying UC on UCS VMware OVA/OVF Files

vSphere Client

CCO

OVA

UCS B200 M1

http://en.wikipedia.org/wiki/Open_Virtualization_Format


Deploying UC on UCS Cisco OVA Files  Each Cisco UC Application has one or more defined OVAs

-  Cisco provides OVA files for UC applications deployment on VMware

-  Tested VM configurations for each UC applications

 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 OVA Files for UC on UCS deployment: http://www.cisco.com/go/uc-virtualized


UC on UCS Best Practices


Supported VM Configurations 8.5(1) Product Scale

(users) vCPU vRAM

(GB) vDisk (GB)

UC Release

CUCM 1,000 2 4 1 x 80 8.5 (C200) 2,500 1 2.25 1 x 80 8.x (C210 & B200)

7,500 2 6 2 x 80 8.x (C210 & B200)

UCxn 500 1 2 1 x 160 8.x 1,000 1 4 1 x 160 8.x 5,000 2 4 1 x 200 8.x

10,000 4 4 2 x 146 8.x 20,000 7 8 2 x 300 8.x

CUP 1,000 1 2 1 x 80 8.x 2,500 2 4 1 x 80 8.x 5,000 4 4 2 x 80 8.x

UCCX/IPIVR 100 2 4 1 x 146 8.5 300 2 4 2 x 146 8.x 400 4 8 2 x 146 8.5

1 vCPU for UCxn ESXi scheduler


Virtualization with VMware Hypothetical B-Series Layout

CPU-1 CPU-2 CPU-1 CPU-2

Blade 1 Blade 2


Blade 3 Blade 4


Blade 5 Blade 6


Blade 7 Blade 8

PUB1 UCxn (Active)

CUP

Spare

Core 1 Core 2 Core 3 Core 4 Core 1 Core 2 Core 3 Core 4 Core 1 Core 2 Core 3 Core 4 Core 1 Core 2 Core 3 Core 4




SUB1 (PRI)

SUB2 (SEC)

SUB3 (THD/PRI)

SUB4 (SEC)

DNS

Spare

CUCCX (SEC)

UCxn (Backup)

Res

erve

d fo

r V

Mw

are

Res

erve

d fo

r V

Mw

are

CUCCX (PRI)

CUP

Directory File/ Print


Virtualization with VMware Hypothetical C-Series Layout

CPU-1 CPU-2

Chassis 1

PUB1

Core 1 Core 2 Core 3 Core 4 Core 1 Core 2 Core 3 Core 4

SUB1 (PRI)

CPU-1 CPU-2

Chassis 2


SUB2 (SEC)

UCxn (Active)

Res

erve

d fo

r VM

war

e R

eser

ved

for V

Mw

are

UCxn (Backup)


UC Design Changes SRND Impact   SRND application-layer guidelines are

same as when on MCS Redundancy group design, etc.

Determine quantity/role of nodes

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

  CUCM-BE & Mega-Cluster are not supported (roadmap)


High Availability Design Rules

  Current Business Continuity and Disaster Recovery strategies still applicable

  UC application 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.)


Tested Reference Configurations (TRC)

 What is a “Tested Reference Configuration”? •  Specific UCS server configuration built to specific VTG

capacity/co-residency scenario

•  Specific server type and storage options

•  Orderable either single Cisco Collaboration SKU or built to order set of Cisco Data Center SKUs

•  Configuration tested in the lab with supplemental documentation provided

 TAC supported configurations

 Must also purchase VMWare ESXi license

http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/ solution_overview_c22-597556.html


Cisco UCS B200Mx (UCS-B200Mx-VCS1) B200M1/M2 TRC #1

UCS 5108 Chassis

UCS 6100XP Fabric Interconnect Switch

SAN LAN

UCS 2100 Fabric Extender

Storage Array (for UC Apps)

PSTN/ PTT

FC

10GbE

Catalyst

Nexus

MDS

FC

Rest of Intranet

Configuration (M1): - 32GB RAM - 2 x 5540 CPU - 2 x 146GB DAS Drives - M71kR-Q CNA Adapter Configuration (M2): -48GB RAM -2 x E5640 CPU -2 x 146GB DAS Drives -UCS M8IKR VIC

Management: -  Supports multiple VMs -  UCS Manager - vSphere/vCenter

M2 Pre-FCS


Cisco UCS C210Mx (UCS C210Mx-VCD2) C210M1 TRC #2 OR C210M2 TRC# 1

UCS C210 Mx

LAN PSTN/ PTT

10/100/1GbE

Catalyst

Rest of Intranet

Management: -  Supports multiple VMs -  CIMC for UCS - vSphere/vCenter

Configuration: -10x146GB DAS Drives

(w/ SAS Expander) -6x1GB NICs Ethernet 2 motherboard 4 on PCI card -1x1GB NIC for CIMC

M2 Pre-FCS


Cisco UCS C210Mx C210M1 TRC #3 OR C210M2 TRC# 2

UCS C210 Mx

SAN LAN

Storage Array (for UC Apps)

PSTN/ PTT

FC

10/100/1GbE

Catalyst

Nexus

MDS

FC

Rest of Intranet

Configuration: -2x146GB DAS Drives -6x1GB NICs Ethernet 2 motherboard 4 on PCI card -1x1GB NIC for CIMC -HBA Adapter 2x4GB for FC


M2 Pre-FCS


Cisco UCS C200M2 (UCS C200M2-VCD2) C200M2 TRC #1

UCS C200 M2

LAN PSTN/ PTT

10/100/1GbE

Catalyst

Rest of Intranet


Configuration: -Dual Quad Core E5506 -4x1TB DAS Drives -24GB RAM -2x1GB NICs Ethernet -1x1GB NIC for CIMC

M2 Pre-FCS


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 CICM


Server Selection Guideline

> 10 “servers”

C210Mx SAN”

> 24 vCPU?

UCS B200”

Already have DC/

SAN?

C210Mx DAS

C200M2

> 8vCPU or > 1000 users

Building DC for UC?

$$

Yes

Yes

Yes

Yes

Yes

No

No

No

No

No

Start


Server design considerations

Customer requirement: -7500 users (5 ‘servers’)

-250 agent CCx (2 ‘servers’)

-Voice Mail (2 ‘servers’)

-Presence (2 ‘servers’)

-No data center currently, but investigating

-Application redundancy mandatory

Start


Production: 6x CUCM, 5x Unity (3x VM, 2x PDC/Exchange), 9x CUCCE (2xRogger, 2xCTIOS, 4xPG, 1xHDS), 2xQM

Lab: 1xCUCM, 1xCUCCE (Sprawler), 1xQM

  14 Blades on 2 Chassis

  1-2 Fabric Switches

  14 rack units of space

  25 Rack Servers

  40 ports of Catalyst Switching (10/100/1000 Ethernet)

  50+ rack units of space

With 2:1 Consolidation Ratio…

CM

CM

CM

CM

CM

CM

Rgr

Rgr

PG

PG

PG

PG

CTI

CTI

HDS

QM

QM

CM*

Spr*

QM*

=

Unity

Unity

Unity

Unity

Unity

Lab: Rgr

Rgr

CM

CM

QM

QM

CM* Spr* QM*

PG

PG

CM PG

CM PG

CM

CM

UCxn UCxn

UCxn

UCxn

UCxn

HDS

CTI

CTI

UC Customer Care Example ~1K users at HQ, 550 Agents, 4800 voicemail users


Commercial Customer Example ~1K users, 150 Agents, Presence/IM Enabled Production: 3x CUCM, 2x Unity, 2x CUP, 2x UCCX


CM

CM

CM

CUP

CUP

UCCX

= UCxn

UCxn

UCCX CM CUP

CM

CM

UCxn

UCxn

UCCX UCCX CUP

  5 Blades on 1 Chassis

  1-2 Fabric Switches

  7 rack units of space

  9 Rack Servers

  13 ports of Catalyst Switching (10/100/1000 Ethernet)

  18+ rack units of space



Branch B

Branch C

UC Single or Multi-site w/o UCS Small to Medium Business

  UCM, Voicemail, IVR == 3 servers

  Centralized dial plan and administration

PSTN

IP WAN SRST Headquarters

Applications (Vmail, IVR)

CUCM

SRST


Branch B

Branch C

UC Single or Multi-site on UCS C-Series supported on UC 8.5

PSTN


SRST

CPU-1 CPU-2

Server 1

UCCX Core 1 Core 2 Core 3 Core 4 Core 1 Core 2 Core 3 Core 4

PUB

C210M1

UC on UCS = 1 C-Series

SUB ESXi

U

Cxn

  PROs:   4:1 server consolidation

  2 RU’s

  CONs:   Single point of failure!

  Got to pass the ‘Duh’ test

UCxn


Branch B

Branch C

Multi-Site Distributed Call Processing MCS Deployment

  CUCM, VoiceMail and App’s at central site

  Distributed call processing across two sites

  3rd site is centralized back to HQ

PSTN


Applications (VMail, IVR, ICD, ...)

CUCM Cluster

CUCM Cluster


Branch B

Branch C

Multi-Site Distributed on UCS C-Series supported on UC 8.0(3) – Phase 1

PSTN



CUCM Cluster

CUCM Cluster

UC on UCS = Two (2) C-Series @ Branch B CPU-1 CPU-2

Server 1

SUB3


SUB1 PUB

C210M1

C210M1

CPU-1 CPU-2 Server 2


SUB4 SUB2


Branch B

Branch C


PSTN



CUCM Cluster

CUCM Cluster

UC on UCS = Three (3) C-Series @ HQ


SUB3


SUB2

C210M1

C210M1



SUB1

SUB4


UCxn - Backup


PUB

UCxn - Active

C210M1


Branch B

Branch C


PSTN



CUCM Cluster

CUCM Cluster

UC on UCS = Four (4) C-Series @ HQ


SUB3


SUB2

C210M1

C210M1



SUB1 SUB4


UCxn - Backup Core 1 Core 2 Core 3 Core 4 Core 1 Core 2 Core 3 Core 4

PUB

UCxn - Active

C210M1

C210M1



UCCX

UCCX

CUP


Design Support

 PDI-HD Team fully trained on UC on UCS

Has been part of Go-To-Market strategy

Available for Presales support & Design inquires

http://www.cisco.com/web/partners/tools/pdihd.html


UC on UCS Go to Market


CAPEX   Reduced Server Count (50-75%)

  Storage Consolidation (50+%)

  Reduced Network Ports (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%)

Example: 5,000 users Dial tone, voicemail and Presence, 10% are Contact Center Agents

11 non-virtualized rack servers required for UC, more for other business apps

UC on UCS B-Series Value Proposition Significant TCO Benefits to Customer


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

Example: 5,000 users Dial tone, voicemail and Presence, 10% are Contact Center Agents

11 non-virtualized rack servers required for UC, more for other business apps

Optional

UC on UCS C-Series Value Proposition Significant TCO Benefits to Customer


TCO/ROI Example

MCS 7845-I3 UC on UCS B200M1 UC on UCS C210 M1

  11 MCS Servers

  Space: 22 RU

  Power: 7.43 KW

  Cooling: 5.67 BTU/hour

  Network Ports/Cables: 33

  Power Cables: 22

  Estimated CAPEX: $308K

  Estimated OPEX: $560K/year

  4 B200 Servers + VMware and SAN

  Space: 8-14 RU

  Power: 2.16 KW

  Cooling: 1.65 BTU/hour


  Power Cables: 12

  Estimated CAPEX: ~$200K-$369K

  Estimated OPEX: ~$466K/year

  4 C210 Servers + VMware

  Space: 8 RU

  Power: ~2.7 kW

  Cooling: ~2 BTU/hour


  Power Cables: 8

  Estimated CAPEX: ~$150K

  Estimated OPEX: ~$200K/year


Ordering UCS B200 M2 UC SKU

  UCS-B200M1-VCS1 SKU:

Two 2.66GHz Xeon E5640 CPU, 48GB DRAM, two 146GB SAS local drives and one UCS M81KR Virtual Interface Card/PCIe/2-port 10Gb

  Customer requirements:

UCS Blade Server Chassis

UCS Fabric Interconnect Switch and Expansion Module

UCS Fabric Extender

Fiber Channel (FC) Storage Area Network (SAN)

  Supports all UC applications that can run on UCS

  Ordering Guide URL at end of deck, Resources

Half-width blade Q-Logic CNA

UCS-B200M2-VCS1

Orderable as of Dec 7, 2010


Ordering UCS VMware UC SKU

  VMW-UC-STD-K9-1A

ESXi 4.0 Standard License (no VMotion) per B-Series Blade or C-Series Chassis

Based on number of processors on physical host, per socket licensing

  CON-ISV1-UCSTD1A

1-year support agreement is required

Orders are validated via New Product Hold (NPH) process NPH for max of 90 days until support is validated or added to order

  Customer may use pre-owned licenses for VMware vSphere


ESXi Standard License

VMW-UC-STD-K9-1A VMware ESXi VMkernel


Ordering B-Series Process   Netformx is a requirement

Part of UCS ATP already

  Use UCS Advisor for B-Series chassis and fabric

  Use UC Advisor or DCT to add UC Blade + VMware SKU’s

  Also, add other UC components, including:

UC Application SKU’s

UCSS

Phones

Gateways, etc

  Upload the configuration to Cisco


B-Series M1 BOM Example Minimal, Single Chassis – Netformx

VMware Standard


Sales Strategy C-Series Strategy

 Solution for majority of customers

 Strong selling points Very competitive price point

Single vendor story for customer

Only Cisco servers for Virtualization

 Migration story Sample migration off MCS

Main UC Manager on C-Series Backup on MCS

Primary Unity Connection on C-Series Redundant on MCS

Full migration to C-Series after certain testing timeline


Ordering UCS C210 M2 UC SKU

  Platform specifications:

Two 2.66GHz Xeon E5640 CPU, 48GB DRAM and ten 146GB SAS local drives


  Data Center SKU BOM build out posted with VoE material

  See UC on UCS page for DC reference configuration:

www.cisco.com/go/swonly

C210 M2

UCS-C210M2-VCD2

Target Orderability Dec 20, 2010


Ordering UCS C200 M2 UC SKU

  Platform specifications:

Two 2.13GHz Xeon E5506 CPU, 24GB DRAM and four 1TB SAS local drives


  Data Center SKU BOM build out posted with VoE material

  See UC on UCS page for DC reference configuration:

www.cisco.com/go/swonly

C200 M2

UCS-C200M2-VCD2

Target Orderability Dec 20, 2010


Sales Strategy Upgrade Current Base

  Look at current customer base

 Create target account list Larger install base of handsets

Larger server count

Upgrading in next 6-9 months

3rd party applications in house

 Upgrade to Cisco UC 8.0

 Move to UCS platforms off older servers


Addition Sales Tools Coming Soon   TCO / ROI Tool

Under development between VTG and SABU

  Customer references Details of Cisco UC on UCS Beta customers coming soon

  Competitive material Selling UCS products into an account

UC competitors Virtualization direction


UC on UCS Partner Readiness


Partner Readiness Who Can Sell Solution?  B-Series OR C-Series SAN Solution

Recommend VMware VSP, VTSP & VCP

Advanced UC and UCS ATP

Otherwise, work with Cisco PSS for AS services •  AS SKU’s exist to sell UCS platform (not UC specific)

or Work with another partner who is

•  Work with you local Cisco CAM for engagement

•  Currently 10 DC only partners in US Theater

 C-Series w/o SAN Recommend VMware VSP, VTSP & VCP

Advanced UC (No planned AUC program changes)


Partner Readiness Virtualization Practice When should we invest into a Virtualization Practice?

  Build relationship with VMware sooner than later   Relationship and knowledge of VMware

  VTSP & VCP expertise for deep level discussions with customers

  Develop holistic Virtualization Practice   Understand solution positioning

  Hand off points between DC and UC practices

  Especially true for post sales organization

  Ongoing enablement offerings   Important to stay abreast of changes and addition solution offerings

  UC on UCS will continue to evolve throughout CY’2011


Partner Readiness Resources   VMWare Certifications

VMware Sales Professional (VSP) – Account Manager ~ 4-6 hrs

VMware Technical Sales (VTSP) – Pre-Sales SE ~ 7 hrs

VMware Certified Professional (VCP) – Post-Sales SE ~ 4-5 days + test prep

http://www.vmware.com/services/

  UC on UCS Bootcamps Both B-series and C-series

Monitor “My Cisco Community” UC training calendar

https://www.myciscocommunity.com/community/partner/collaboration/calendar

  Cisco UC Readiness Community Join the community to learn the latest regarding UC on UCS, ask questions and share feedback

https://www.myciscocommunity.com/community/partner/collaboration/uc/systemrelease


Partner Readiness Resources (cont.)   DocWiki

http://www.cisco.com/go/uc-virtualized

  Solution Page http://www.cisco.com/en/US/netsol/ns1067/index.html

  On CCO http://www.cisco.com/go/uconucs

  UC Design http://www.cisco.com/go/ucdesign

  Ordering Guide http://www.cisco.com/web/partners/downloads/partner/WWChannels/technology/ipc/downloads/

uc_sol_og_ucl_final.pdf

  Supported UCS Hardware Specs http://www.cisco.com/go/swonly

  “What’s new, what’s different” customer document http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/virtual/servers.html

  TechWise TV Episode 74 “Unified Communications Goes Virtual” http://www.cisco.com/en/US/netsol/ns914/networking_solutions_program_home.html


UC Virtualization Final Thoughts…

 UC 8.5 gets us closer!! Less complex

More mainstream going forward

 Continued patience is key Not everything supported still

Some applications even slipping to Jan

i.e. Still no MeetingPlace

 You must gain VMware knowledge!!!

 And, you MUST work with DC counterparts!!!


What Questions Do You Have?

VoE UC 8.5 Virtualization External

Documents

Transcript of VoE UC 8.5 Virtualization External