Planning Virtual UC Solutions on UCS Platform

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

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

BRKUCC-2782_syali © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 2

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

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


Fundamentals of UC on UCS Architecture

Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 6

Prerequisites 

Do you know the basics of Answer

CUCM or CallManager Yes. That’s why I am here 

Virtualization/VMware Running server apps as VMs.
VMware ESX vs. ESXi hypervisor
vSphere
Storage Area Networking Separation of storage from the compute
FC, iSCSI & FCoE protocol

Cisco UCS It is a new computing architecture from Cisco.
Beside other components it offers B and C
series x86 based servers


DAS, iSCSI and SAN Comparison
 DAS (Direct Attached DAS SAN iSCSI
Storage): Rack Mount Computer System Computer System Computer System

HP/IBM MCS Servers Host/
Application Application Application

File System File System File System

 Popular DAS Protocol: SCSI Server
Volume Manager Volume Manager Volume Manager
SCSI Device Driver
SCSI Device Driver SCSI Device Driver iSCSI Driver

 iSCSI: Access SCSI storage SCSI Bus Adapter FC HBA
TCP/IP Stack
NIC

media using IP network Block I/O
 SAN: Storage (Hard Drives) SAN IP
away from physical server Storage
Transport NIC
or compute TCP/IP Stack

 Popular SAN Protocol: FC
iSCSI Layer
SCSI FC Bus Adapter

Storage
Media


Storage Area Network (SAN)

 SAN: Way to access the storage
Clients
sitting away from compute
 Remove Hard Drive and put it
1km away LAN

 High-performance interconnect
Servers
providing high I/O throughput
 Lower TCO relative to direct SAN
attached storage, storage can be
shared
Block
Storage
Devices

Separation of Storage from the Server


Unified Fabric – FCoE Standard
DAS iSCSI FCoE FC

SCSI SCSI SCSI SCSI
iSCSI FCP FCP
FC FC

TCP
IP FCoE
Ethernet Ethernet
Physical Wire

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

UC on UCS - Virtual DC Overview
Network vs. Server Virtualization

UC Application UC Application UC Application

5
4
VMware ESXi , Unified Computing System

2 3
1


Compute/Server


Compute: Cisco UCS B-Series
Blade Servers Examples UCS B230
UCS B440

UCS B200
UCS B250

Blade CPU Size Memory Disks VMs

32 DIMM 4 3.5”
UCS B440 M1
4x Intel 7500 Full Width SAS/SATA NA
256 GB Drives
2x Intel 5540 or 48 DIMM 2x 3.5” SAS
UCS B250 Full Width NA
5640 for M2 384 GB Drives

2x Intel 6500 or 32 DIMM 2x 3.5” SSD
UCS B230 Half Size NA
7500 for M2 256 GB Drives
2x Intel 5540 or
12 DIMM 2x 3.5” SAS
UCS B200 5640 M2 Half Width 4
96GB Drives

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

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
64 DIMM 12 SAS/SATA
UCS C460 M1 4x Intel 7500 4RU 10 PCIe NA
512 GB Drives
48 DIMM 8 SFF
UCS C250 M1
2x Intel 5540 2RU SAS/SATA 5 PCIe NA
(memory intensive) 384 GB Drives
12 DIMM 16 SFF
2x Intel 5540
UCS C210 M1 2RU SAS/SATA 5 PCIe 4
(5640) 96 GB Drives
2x Intel 5506 12 DIMM 4 x 3.5”
UCS C200 M2 1RU SAS/SATA 2 PCIe 4
96GB Drives

UC Server Virtualization


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


Virtual UC on UCS Architecture
MCS 7816/25/28 UCS 5108 Chassis
Virtual UC Apps

Hypervisor
MCS 7835/45 UCS C210/C200 UCS B200 with CNA

UCS 2100
Fabric Extender
FEX
UCS 6100XP
Fabric Interconnect Switch

10/100/1GbE
10GbE FC

Catalyst

Management:
PSTN/ LAN SAN MDS - UCS Manager
- CIMC for UCS
PTT Nexus - vSphere/vCenter
FC
Rest of
Intranet Storage Array
(for UC Apps)


1
Virtual Design Differences


Cluster Based on Virtual Resources
Unity Unity
Connection Connection

CUCCX CUCCX
Unified CM Unified CM

MCS Servers Virtual Machines (OVA)
CPU/Mem/HDD vCPU/vMem/SAN or DAS

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


UC on UCS
Tested Reference Configurations (TRC)


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

Cisco UCS C200M2 (UCS-C200M2-VCD2)
C200M2 TRC Example
Configuration:
- Dual Quad Core E5506
UCS C200 M2
- 4 x 1TB SAS Drives
- 24 GB RAM
- 2 x 1GB NICs Ethernet
10/100/1GbE - 1 x 1GB NIC for CIMC

Catalyst

Management:
PSTN/ LAN - CIMC for UCS
PTT
- vSphere/vCenter
Rest of
Intranet


Tested Reference Configurations Summary
Server Model/Generation & Collaboration SKU Notes
Tested Reference Configuration
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)


2
Planning and Design


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

BRKUCC-2782_syali http://www.cisco.com/go/ucsrnd
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 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.)


Virtual Machine Sizing and Placement


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

BRKUCC-2782_syali http://en.wikipedia.org/wiki/Open_Virtualization_Format

UC VM Configuration 8.5(1)
Product Scale (users) vCPU vRAM (GB) vDisk (GB)
CUCM 7,500 2 6 2 x 80
2,500 1 2.25 1 x 80
UnityConnection 20,000 7 8 2 x 300
10,000 4 4 2 x 146
5,000 2 4 1 x 200
500 1 2 1 x 160
Unity 15,000 4 4 4 x 24
5,000 2 4 4 x 24
CUP 5,000 4 4 2 x80
2,500 2 4 1 x 80
UCCX/IPIVR 400 agents 4 8 2 x 146
300 agents 2 4 2 x 146

1 vCPU for Unity Connection ESXi scheduler
SME = CUCM Session Management Edition

UC VM Configurations 8.5(1)
Product Scale (users) vCPU Cores vRAM vDisk
(GB) (GB)
CER 30,000 2 6 2 x 80
20,000 1 2.25 1 x 80
12,000 1 2.25 1 x 80

CMBE 6000 (C200) VM Configurations 8.5(1)
Product Scale (users) vCPU Cores vRAM vDisk
(GB) (GB)
CUCM 1,000 2 (600 MHz *R) 4 (*R) 1 x 80
UnityConnection 1,000 1 4 1 x 160
CUP 1,000 1 (800 MHz *R) 2 1 x 80
UCCX/IPIVR 100 2 4 2 x 146

* R = Reserved

UCCE/CVP VM Configuration 8.5(1)
CVP
Component & Scale * vCPU vRAM (GB) vDisk (GB) vNIC

Call+VXML Server (900 Calls) 4 4 1 x 146 1
Reporting (Large) (840 Msg/sec) 4 4 1 x 72 1
1 x 438
OAMP Server 2 2 1 x 20 1

UCCE
Component & Scale * vCPU vRAM (GB) vDisk (GB) vNIC

Router 8000 agents 2 4 1 x 80 2

Logger 8000 users 4 4 1 x150 2

Agent PG 2000 users 2 4 1 x 80 2

VRU PG 9600 ports, 10 PIMs 2 2 1 x 80 2

AW Server (25 clients) 1 2 1 x 40 1


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
 PROs:
CPU-1 CPU-2  7:2 server consolidation
PUB/ CCX-1  4 RU’s
UCxn
UCxn
ESXi

(Act)

TFTP CUP
 App Redundancy
 Extra ‘server’ at no HW cost
Core 1 Core 2 Core 3 Core 4 Core 1 Core 2 Core 3 Core 4

Rack Server #2
CPU-1 CPU-2  CONs:
SUB CCX-2
(Stnadby)
UCxn

 Extra server
UCxn
ESXi

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


UCS Server Selection


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


Server Selection Guideline
UCS B200”
Yes
1 > 24
vCPU?

Yes No
Already $$
have C210Mx
DC/SAN? SAN”
No Yes
Building
Yes 2 DC for UC?

Start
> 10 No
“servers”

No C210Mx
DAS

Yes
> 8vCPU or
3 > 1000 users

No
1 Large
C200M2/
BE6000
2 Medium

3 Small

VMware/vCenter Design Best Practices


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 No No
Converter

Partial = Limited support (See following URL for details)
http://docwiki.cisco.com/wiki/Unified_Communications_VMWare_Requirements

VMware Management
 Cisco is not dictating management
of VMware images
1 vSphere Client
 Customer strategy will depend on
number of images

1 A  VMware vSphere Client
-Thick client downloaded to Windows PC

-Directly manages each VMware ESXi host (Model A)

-Can connect to VMware vCenter Server to centrally
manage all ESXi hosts (Model B)
1 vSphere Client

 VMware vCenter Server
2

B
-Windows server running vCenter 4.x

1 -Provides central point of configuration, provisioning and
vCenter Server management

-Only way to get chassis HW failure notification

LAN/SAN Design Best Practices


Virtual Software Switch Options UCS B200

VM
VMware VMware Cisco Nexus vNIC
vSwitch dvSwitch 1KV
Host based (local) Distributed Distributed Software Switch
ESXi Hypervisor
IEEE 802.1Q VLAN IEEE 802.1Q VLAN IEEE 802.1Q VLAN
tagging tagging tagging
CNA vmNIC
VLANs only visible to VLANs visible to all VLANs visible to all
local ESXi host ESXi hosts ESXi hosts
EtherChannel EtherChannel EtherChannel
-- -- Virtual PortChannel FCoE
-- -- QoS Marking
(DSCP/CoS)
-- -- ACL
-- -- SPAN
RADIUS/TACACS+
No VM needed No VM needed VM needed
vCenter not needed vCenter needed vCenter needed
LAN SAN


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
CAT6K
dc1-access-6k(config)#mls qos map dscp-cos 24 to 3 L2:3 L3:CS3
dc1-access-6k(config)#mls qos map dscp-cos 46 to 5

BRKUCC-2782_syali Physicaland/or its affiliates. All rights reserved. to L2 CoS
© 2010 Cisco
switch maps L3 DSCP Cisco Public 44

CUCM
UC QoS Concept – With B-Series
 6100 switch in middle – L2 based prioritization
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 CAT6K

Rest (“match any”) – Best Effort Queue

BRKUCC-2782_syali 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 UCS B200 Blade Server

FCoE

UCS-6100 FI Switch

Fibre Channel

10Gbps Ethernet

Catalyst
Ethernet
Switch SAN
UC Apps Disc
Disc Space Array

BRKUCC-2782_syali IP traffic competing with FC traffic

CUCM
B-Series QoS Best Practices
L2:0 L3:CS3

N1KV
L2:3 L3:CS3

N1Kv Considerations:
UCS 6100
• UC sig. traffic (CoS3) share queues with FCoE traffic (CoS3) L2:3 L3:CS3
• UC sig. traffic is given lossless behavior
• Default CoS value of 3 for FCoE traffic should never be
changed 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

FC Network Best Practices/Guidelines
3rd Party SAN Example Compute Layer Cisco
UCS 6100
Fabric
• 1 Rack; 12 DAE Interconnect
• Total capacity 28,000 IOPS
• 14,000 IOPS per controller Nexus
1000V
• 4 KByte block size
4x10GE 4x10G
E UCS 5100
Blade
14,000 IOPS x (4KB) ~ 428 Mbps 4x10GE 4x10G
E Server
600 Mbps throughput/controller

Result SAN/Storage
Layer – Cisco
• One 4 Gbps FC interface is enough to SRND
Cisco SAN
Switch
handle the entire capacity of one FC FC

Storage Array
• HA requires four FC interfaces FC FC

SP-A SP-B

3rd party layer FC Storage
CUCM VM IOPS ~ 200
200 IOPS * 4KB ~ 6.4 Mbps per VM


SAN Array LUN Best Practices / Guidelines
HD Recommendation FC class (e.g 450 GB 15K, 300 GB 15K) ~ 180 IOPS
LUN Size Restriction Must never be greater than 2 TB
UC VM App Per LUN Between 3 & 8 (different UC apps require different space
requirement based on OVA
LUN Size Between 500 GB & 1.5 TB
Recommendation

PUB SUB1 UCCX1 UCCX2 CUP1 CUP2
VM1 VM2 VM3 VM1 VM2 VM3

LUN1 – 720 GB
LUN 1 (720 GB) LUN 2 (720 GB) GB
LUN2 – 720

Single RAID5 Group (1.4 TB Usable Space)

HD 1 HD 2 HD 3 HD 4 HD 5
450gig 450gig 450gig 450gig 450gig
15K RPM 15K RPM 15K RPM 15K RPM 15K RPM

Case Study


Deployment Model
Distributed Call Processing 2000 IP Phones

Applications
(UnityC, UCCX, CUP) CUCM
cluster
UnityC, UCCX,
CUP
CUCM
cluster PSTN

CUSP
IP WAN
SIP Proxy
CUCM
12,000 IP Phones 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

CUCM Server Requirement Input
12K Phones
10K Messaging Users
10K CUPC Clients
240 UCCX Agents
10 Supervisors

MCS Servers
Unity Connection Server Requirement CUCM 11
UCxn 2
CUP 2
UCCX 2
Total 17

CUP Server Requirement

UCCX Server Requirement


Server Requirement – 12K Devices/Users Input
12K Phones
B200-1 B200-2 10K Messaging Users

CPU-1 CPU-2 CPU-1 CPU-2 10K CUPC Clients
240 UCCX Agents
ESXi UCxn-1 10 Supervisors
PUB TFTP-1 SUB-1 SUB-3 SUB-5 UCxn Active

Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4

B200-3 B200-4 MCS Servers
CUCM 11
CPU-1 CPU-2 CPU-1 CPU-2 UCxn 2

SUB-7 UCCX-1 SUB-2 SUB-6 ESXi UCxn-2 CUP 2
UCxn
Active UCCX 2
Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Core1 Core2 Core3 Core4 Total 17
B200-5 B200-6
CPU-1 CPU-2 CPU-1 CPU-2 B200
SUB-8 UCCX-2 CUP-1 SUB-4 TFTP-2
CUP-1
CUP-2
CUP-2
UCCX-1
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

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)


Deploying UC Virtual Machine – B&C Series
2

1 OVF Templates
Provided by Cisco 3

4
UCS C210 M1
ISO

UCS B200 M1

BRKUCC-2782_syali UC VM OVF ©Templates: http://www.cisco.com/go/uc-virtualized
2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 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


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
Don’t forget to activate your
network to access our portal) Cisco Live and Networkers Virtual
or visit one of the Internet account for access to all session
stations throughout the materials, communities, and on-demand
Convention Center. and live activities throughout the year.
Activate your account at any internet
station or visit www.ciscolivevirtual.com.

Questions ?


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
 Virtual UC Deployment Guide on B-Series by Shahzad Ali
https://supportforums.cisco.com/docs/DOC-6158


Recommended Reading

Please browse on-site Cisco Store for suitable reading.


Planning Virtual UC Solutions on UCS Platform

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Destaque

Destaque (12)

Semelhante a Planning Virtual UC Solutions on UCS Platform

Semelhante a Planning Virtual UC Solutions on UCS Platform (20)

Mais de Cisco Canada

Mais de Cisco Canada (20)

Planning Virtual UC Solutions on UCS Platform