cisco confidential © 2013 cisco and/or its affiliates. all rights reserved. 1 uc on ucs design...

Cisco Confidential© 2013 Cisco and/or its affiliates. All rights reserved. 1

UC on UCS Design UpdatePedro Zevallos

Systems Engineer

[email protected]

Nov 2013

© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 2

Agenda

• General Updates Specs-based update, UCS-E, Packaged Collaboration Solution, Platform Roadmap, VMPT, OVA changes, etc…

• Music On Hold UpdateFixed/live audio source (implications with virtualization, limitations, configuration)

• Prime Collaboration Deployment (PCD)PCD description and benefits

Demo

Cisco Confidential 3© 2013 Cisco and/or its affiliates. All rights reserved.

General Updates


Specs-Based for restricted UC perf CPU platforms• Specs-based used to be only for full UC perf CPU ([email protected]+, [email protected]+, or E5600/[email protected]+).

• Since August 2013, Extending to Restricted UC perf CPU with [email protected]+ (not for older Hardware)

• Supported with many apps (e.g. CUCM, CUC, IM&P, CCX,…)… But not supported with all OVAs (typically, support for OVA compatible with Small Platform only)


What about ISR blades?

AXPSRE

UCS Express√ SREV-910X Other SREV-9xx

UCS E-Series• E140D/DP M1

Other UCS E-Series• E160D M1• E160DP M1• E140DP M1• E140S M1

Older - limited support- CUCM 8.6 controlled release: US DoD only.- CUC “specs-based” only- MediaSense 8.5(4)+

Older - no support

Specs-based-only support- “Restricted UC Perf. CPU” (E5-24xx at 2.00+ GHz)- Expect low scale (<4 VMs, few 100 users) due to IOPS bottlenecks- DP: to check if less drive. Uncommitted Roadmap for UCS E-Series

- Plans to provide UCS E-series based TRC - No TRC until Midmarket packaged offer figured out.- UCS E-Series M1 vs. M2 roadmap may impact timing

No support in general (except for CUC/specs-based)- CPU GHz too slow for Specs-based ([email protected]) or not enough available drives/IOPS - No TRC until Midmarket does one – see the BE6K PMs.

mailto:[email protected]


Cisco Packaged Collaboration Solution

• Target FCS: early Q2FY14 (stretch late Q1FY14)

• UC on UCS Medium TRC with preloaded softwareNot another BE6K

Licenses sold separately (no free PCP, no free VCS, no free 25 user licenses)

Just a simplified quote, delivery, install option for UC on UCS

C240 M3S TRC#2: total 12 cores, total 12 disks (2 RAID volumes)

Old Medium TRC still available (C220 M3S TRC#1, total 8 cores, total 8 disks)

• What does it ship?Hardware “ready to run” (ships with BIOS, RAID, disk formatting, drivers all setup)

HYP virtualization software “ready to run” (factory-installed)

Collaboration suite apps “ready to install” (factory-loaded ISOs and OVAs).

• Deeper dives coming for partner and field readiness

COLLAB-MED-TRCCOLLAB-MED-TRC-XU9.1 applications5.x virtualization softwareUC on UCS New Medium TRC(UCS C240 M3S TRC#2)


Hardware Roadmap (subject to change)

Westmere-EX (E7v1)Sandy Bridge-EP/EN (E5v1) Ivy Bridge-EP/EN (E5v2) E5 successor

E7 successor

XS TRC

STRC

S+ TRC

M TRC

L TRC

XL TRC

2XL TRC

Specs-based

Q4CY13 1HCY14 2HCY14

E7-xxxx @ 2.0+ / 2.40+ GHzE5-xxxx @ 2.0+ / 2.50+ GHz

E5-xxxx v2 @ 2.0+ / 2.50+ GHzDefine Min CPU Spec

Cover via Min CPU SpecAdd Use

AddReplace

Replace

BE6K – planned, not committed

BE6K MD / C220 M3 TRC#2

BE6K HD / C220 M3 TRC#3

C220 M3 TRC#1

PCS / C240 M3 TRC#2

C240 M3 TRC#1

B200 M3 TRC#1

C260 M2 TRC#1

B230 M2 TRC#1

B440 M2 TRC#1

New BE6K MD / Rack TRC with new CPUs

New BE6K HD / Rack TRC with new CPUsReplace

Replace

New Rack TRC with new CPUs

Retire - use Large TRCs.EOS

Retire - use Large TRCs. EOS

New PCS / Rack TRC with new CPUs

Retire - use Large TRCs. EOS

http://www.intel.com/index.htm


Design: “Collaboration VM Placement Tool (VMPT)”www.cisco.com/go/vmpt

1. Optimized for BE6K and UC on UCS DAS TRCs. Future = improve Specs-based support.2. Implements most rules from www.cisco.com/go/uc-virtualized (still gaps with UCCE for example)3. Use after SRND or Sizing Tool – manually input. Future = launch from Sizing Tool with auto-populate.4. Exports PDF of your design. Manually convert to UCS/VMware SKUs. Exploring future BOM generation.5. Post roadmap asks here: https://communities.cisco.com/thread/35896

More Info at: http://docwiki.cisco.com/wiki/Readme_for_Cisco_Collaboration_Virtual_Machine_Placement_Tool

http://www.cisco.com/go/vmpt

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

https://communities.cisco.com/thread/35896


http://docwiki.cisco.com/wiki/Readme_for_Cisco_Collaboration_Virtual_Machine_Placement_Tool

http://docwiki.cisco.com/wiki/Readme_for_Cisco_Collaboration_Virtual_Machine_Placement_Tool


Some of the OVA changes (subject to change)• CUCM:

In 10.0, can increase disk size without having to do a DRS backup/restore. Just have to shutdown VM, change size, and start VM.

• CUCM IM&P: 15k OVA will require 8GB instead of 6GB

• New OVA for ELM

• VCS: Three OVAs with x8.0Small OVA for BE6K [email protected]+ (Standalone VCS)

Medium OVA [email protected]+

New large OVA in x8 for higher capacity: 8 [email protected], 8GB RAM, 132GB vDisk, 10GB vNIC. Capacity: 5k registrations, 500 video calls.

• UCCX OVAs not changing

• MediaSense2 vCPU template supported with B and C-series in 9.x.

Support in BE6K.

New 4 vCPU OVA (so will have OVAs with 2, 4, or 7 vCPUs) in 10.x.

• Virtual TelePresence Server available (release 3.1)


Miscellaneous Updates• RAID controller updated (9266 to 9271)

• Oversubscription roadmap: Still looking into MHz-based VM, but still not supported as of now.

• Reminder: Specs-based is vendor neutral (not limited to Cisco/IBM/HP anymore)

• Reminder: MCS end of Sale and 10.0 virtual only… (MCS 7845 already completely sold out)https://communities.cisco.com/thread/35194





Music on HoldFixed/Live Audio Source


Music on Hold SupportAudio File Source Live Source

Unicast/Multicast Multicast Unicast

MCS thru 9.x √ √ (USB dongle or ISR)

√(USB dongle)

Virtual 8.x, 9.x √ √(ISR only)

X*

Virtual 10.x √ √(ISR only)

X*

Virtual 11.0 √ √ Uncommitted Roadmap candidate**

* “MCS dongles” MOH-USB-AUDIO still available, but MCS are EoSale Dongle approach on virtual won’t work – bad audio.** Multiple approaches being investigated.


Fixed-source MOH with virtualization (Multicast)

EM/ FXO port

Fixed / live audio source

HQ

Branch Office

Another fixed / live audio source

EM/ FXO port


Fixed audio Multicast MoH with CUCM How does it work?

(HOLD pressed)

IGMP Membership Report

Multicast RTP Stream


SIP: INVITE(SDP a: sendonly) SIP: INVITE

(SDP a: inactive)

SIP: INVITE (SDP: 239.1.1.1 a: recvonly)

X


CUCM Subscriber

CUCM MOH Server

ISR Router


Multicast MoH: Limitations• Configuration complexity (Multicast needs to be configured in the network and have to

use an ISR to stream the audio)

• Multicast does not always across the WANCentralized call processing with multiple remote sites: Have to provide a local feed on each site

• Multicast does not work well with Teleworkers (CVO solution ok but issues with IPSEC or Anyconnect VPN)

• Multicast not supported by all endpointsLet us know if Multicast MOH solution for fixed/audio live audio is not acceptable for your customer.Send us an e-mail (James Arias, Laurent Pham, Danny Gerber) and provide input on:http://wwsalescollaboration.cisco.com/c/portal/layout?p_l_id=17226&_EXT_2_messageId=84487&p_p_mode=view&_EXT_4_isFromContainer=&_EXT_4_isFromContainer=&p_p_lifecycle=0&p_p_id=EXT_2&_EXT_2_struts_action=%2Fext%2Fidea_view%2Fview_message

http://wwsalescollaboration.cisco.com/c/portal/layout?p_l_id=17226&_EXT_2_messageId=84487&p_p_mode=view&_EXT_4_isFromContainer=&_EXT_4_isFromContainer=&p_p_lifecycle=0&p_p_id=EXT_2&_EXT_2_struts_action=/ext/idea_view/view_message




Configuration Overview• Multicast configuration on the network

• Configure CUCMConfigure Audio Source in CUCM

Configure MoH server

Configure MRG and MRGL

• Configure Multicast MoH on the ISR routerSRST, CME, or LMR configuration


Multicast Network Configuration

• Switches Configuration• Enable IGMP snooping: “ip igmp snooping” (enabled by default).

• Router Configuration• Enable IP Multicast Routing: “ip multicast-routing”.• Enable PIM on the interface. Different options: Sparse, dense, sparse-dense.

“ip pim dense-mode | sparse-mode | sparse-dense-mode”

• More details for example at: http://www.cisco.com/en/US/tech/tk828/technologies_tech_note09186a0080094821.shtml

IGMPJoin

IGMPJoin

PIM Route Multicast

ISR Router

http://www.cisco.com/en/US/tech/tk828/technologies_tech_note09186a0080094821.shtml

http://www.cisco.com/en/US/tech/tk828/technologies_tech_note09186a0080094821.shtml


CUCM Configuration• Enable IPVMS (to enable the MOH server)

• Configure Audio Source and enable Multicast.

• Configure the MoH server. Configure Multicast IP address. Increment by address.

• Configure MRG and MRGL

• On the network, Block CUCM stream


ISR connectivity to audio source• Two options: E&M and FXO.

E&M preferred over FXO because of impedance mismatch issues with FXO. With E&M RJ-45 Connector, use pin 3 and 6.

• With E&M:voice-port 0/0/0

operation 4-wire

auto-cut-through

signal immediate

! auto-cut-through and signal immediate commands disable E&M signaling on the voice port

no vad


“CME” Configuration• CME config:

voice-port 0/0/0

operation 4-wire

auto-cut-through

signal immediate

no vad

!

dial-peer voice 100 pots

description ** LIVE MOH FEED **

destination-pattern 5555

port 0/0/0

!

ephone-dn 100

number 6666

description ** LIVE MOH FEED **

moh out-call 5555

!

telephony-service

multicast moh 239.1.1.1 port 16384


“SRST” Configuration• SRST Config

voice-port 0/0/0

auto-cut-through

operation 4-wire

signal immediate

!

dial-peer voice 100 pots

destination-pattern 5555

port 0/0/0

!

ccm-manager music-on-hold

!

call-manager-fallback

max-conferences 8

max-dn 1

multicast moh 239.1.1.1 port 16384

moh-live dn-number 3333 out-call 5555

! Used for fixed audio source


Prime Collaboration Deployment (PCD)


Prime Collaboration Deployment (PCD)Cisco Management Application that allows to perform:

• MigrationManage the migration of legacy CUCM clusters (as old as 6.1.5) to new VM based servers on 10.0 to facilitate Migration.

• Upgrade UC app software

• Install cop files (locales or device packs) on a cluster

• Switch versions

• Reboot

• Change IP addresses or hostnames on existing 10.x clusters

• Fresh install a new Unified Communication or IM&P cluster on 10.x


Need for Prime Collaboration DeploymentCurrent Migration Challenges

• Customer might have old MCS hardware that do not support the target release, and therefore requires interim upgrades (more steps, license re-hosting).

For example, if CUCM is running 7.x and need to upgrade to 8.6 with a MCS 7845-H2/I2 with 72GB HD: 1- Upgrade to 8.0 or 8.5, 2- Migrate from MCS to UCS, 3- Upgrade to 8.6

• Customer might have even older MCS hardware that can’t be used with a release supporting virtualization, so bridge upgrade might be required, but this means additional downtime.

For example, MCS 7845-H1/I1 can’t be used with CUCM 8.0(2)+.

• Often new networking configuration is required, which also complicates the process.

• Attempts at in-place upgrades impact the production system.

• Jump Upgrade: Limited to 9.1(2). Complex: Dead Net configuration, rebuild VMs again on 9.1(2) for disk alignment.


Existing Migration Options and PCDUpgrade Method Characteristics

Traditional Migration - Typically: Upgrade and then Migrate- Old MCS servers might require interim upgrades (which typically

require license re-hosting)- Older MCS server might require downtime (with Bridge Upgrade for

example)- Long manual process…

Migration with Jump Upgrade - Benefit: direct upgrade to 9.1(2) but…• “Dead net” required• Need to re-install 9.1(2) again after migration (for disk alignment)• Cop files to install

PCD - Direct Migration (Upgrade and Migrate in one step)- New nodes can have the same or different hostnames/IP addresses- Scripted


CUCM Releases Support PCD Feature CUCM

6.1(5)7.1(3), 7.1(5)

8.0(1-3)8.5(1)

CUCM8.6(1-2)

CUCM 9.0(1)/9.1(1)/9.1(2)

Migration(From xx To 10.x)

Yes Yes Yes

Upgrade Yes Yes

Server restart Yes Yes

Switch VersionYes Yes

Re-address (only on 10+)

Fresh Install (only on 10+)

Note: • Migration to VMs can be done from many releases, but destination release must always be 10.x.• Upgrades can be performed on clusters 8.6.1 and up to any release that is a valid upgrade, including 10.x.

(PCD as a replacement for PAWS_M)


IM&P Releases Support PCD Feature CUP 8.5(4)

CUP 8.6(3), 8.6(4), 8.6(5)IM&P 9.0(1), 9.1(1)

Migration(From xx To 10.x) Yes

UpgradeYes

Switch Version Yes

Server restart Yes

Re-address (only on 10+)

Fresh Install (only on 10+)


Other UC application support• CUC

Fresh install and migration not available in 10.0. Other features should be available.

• CCXFresh install and migration not available in 10.0. Other features should be available.

• SMESame support as CUCM

• ELMELM Migration to 10.0 supported only if ELM co-resident with CUCM. Support for Standalone ELM migration planned in next PCD release.


PCD System Requirements• Cisco Prime Collaboration Deployment runs on a VM only

• It requires it’s own VM (not co-resident) (plan for co-residency in post 10.0 release)

• Pre-installed OVA

• OVA Specifications (subject to change):

1 vCPU

Memory: 4 MB

Disk: 80GB

• Why so much disk space? Customers will sftp the iso(s) they need for upgrade and fresh installs to PCD. In this way, PCD acts as the file server.

• Also, when the data is exported from the existing cluster (for transfer to new cluster during migration), those files are stored on PCD.

PCD App App

…


Migration Pre-RequisitesPre-requisites:

• Install ESXi (VMware)

• Deploy PCD virtual machine (delivered as virtual appliance)

• Download necessary 10.0 OVAs and create target VMs using the OVAs

• Download ISO images for target release and upload to PCD server


PCD

Migration: Initial Infrastructure Setup & Config

CUCM 6.1(5), cluster of 4 nodesRTU+DLU licensingEmbedded OS on MCS 7835-H1

Administrator

ISO & OVA

ESXiInventory


Migration: Cluster Discovery


PCD

SourceCluster

ISO & OVA

ESXiInventory


Migration: Define Mapping


PCD

SourceCluster

ISO & OVA

ESXiInventory

NewCluster

Pub-node1

Sub-node2Sub-node3

MOH-node4

Blank VM1

Blank VM2Blank VM3

Blank VM4


Migration: Export Data From Source Cluster


PCD

SourceCluster

ISO & OVA

ESXiInventory

NewCluster


Migration: Shutdown Source, Install & Import Data

CUCM 6.1(5), cluster of 4 nodesRTU+DLU licensingMCS 7835-H1

PCD

SourceCluster

ISO & OVA

ESXiInventory

NewCluster

CUCM 10.0(1) cluster of 4 nodesUser based licensingVirtual on UCS


PCD Migration Summary• Pre-requisites:

Deploy PCD virtual machine (delivered as virtual appliance) Install ESXi (VMware) Download necessary OVA and create target virtual machines using OVA Download ISO images for target release and upload to PCD

• Migration Set-up: Add ESXi hosts to PCD inventory “Discover Cluster” – Retrieves source cluster information. “Create Migration Cluster” – define mapping between MCS source nodes and target virtual machines. “Create Migration Task” – choose the iso to install on the new VMs, and choose time the migration will occur (set time,

or manual start).

• Migration Process: Export Data from old nodes Shutdown old nodes (if not changing the network configuration for the new VMs) Install 10.0 VMs Import data on new VMs


PCD other operational tasks• UC application upgrade:

Can use cop or iso files

Can upgrade one or multiple nodes and specify sequence

• Switch versionsPCD displays the other version to switch

Can upgrade one or multiple nodes and specify sequence

• Server restartCan upgrade one or multiple nodes and specify sequence

• UC application Fresh Install: CUCM 10.0+

• Server readdress. Change Hostname / IP address of one or multiple nodes.

CUCM 10.0+


Key Takeaways• General Updates

New low-end servers supported with Specs-based servers (CPU 2GHz+)

UCS-E 140D supported as Specs-based

New Cisco Packaged Collaboration Solution offering and Platform roadmap

VMPT updates

OVA changes and other Miscellaneous updates

• Music On Hold Update Multicast MoH is the only option for fixed audio MOH in 10.0.

Configuration is not difficult, but Multicast has limitations and ISR is required.

• Prime Collaboration Deployment (PCD)PCD will greatly facilitate Migrations. One step Migration for releases as old as 6.1(5).

Also perform other tasks: Upgrade, Switch Version, Restart, Readdress, Fresh Install.

Thank you.

cisco confidential © 2013 cisco and/or its affiliates. all rights reserved. 1 uc on ucs design...

Documents

trc xl trc

new rack trc

ucs medium trc

b200 m3 trc

cisco confidential

cisco andor

b230 m2 trc

c260 m2 trc