avaya_vmware

AVAYA AND VIRTUALIZATION

#CONVERGE2014

Avaya VMware Comparison

vCenter System Manager

ESXi System Platform

Host Common Server

Guest Template

Administration Tool

Hypervisor Application

Physical Server

Virtual Server

VMware Avaya

#CONVERGE2014

Avaya Aura Virtualized Environment

VMware vSphereVMware vSphereVMware vSphere

VMware vCenter Server

Avaya Aura 6.2 & 6.3Communication

Manager(includes Call Center Elite)

Session Manager

Presence Services

System Manager

Secure Access Link WebLM

Application Enablement

Server

Utility Services

Avaya Aura applications supporting virtualization with VMware

ACE

#CONVERGE2014

Additional Avaya VirtualizedApplications

VMware vSphereVMware vSphereVMware vSphere

VMware vCenter Server

Aura Messaging6.3

Aura Conferencing

8.0Sipera SBC

6.2 FP2*Scopia

Management

ExperiencePortal

Elite Multi-Channel

CMS R17

IP Office 9.0

Avaya Aura applications supporting virtualization with VMware

CMM6.2 FP4

#CONVERGE2014

Flexible Footprints

Adjust requirements of VMs based on User Count

Introduced in Feature Pack 3 Applies to AES, PS, and SM No more wasted resources

#CONVERGE2014

What does flexible resource mean?

500 users Max resourcevCPU RAM (GB) vCPU RAM (GB)

Communication Manager

1 4 1 4

Session Manager 2 4 12 12System Manager 3 7 4 9AES 1 2 4 4Totals 7 17 21 29

Comparing base OVA resource vs. flexible resource specification

Host serverdual processor, 4 core

Host serversdual processor, 6 core

#CONVERGE2014

Advantages of VirtualizingAvaya Aura

Continues to provide existing Avayaapplication level availability Communication Manager Software Duplication for

transparent instantaneous failover Communication Manager Survivable Core and Survivable

Remote Session Manager active-active clustering, N+M routing

And adds VMware availability methods vMotion vMotion Storage VMware High Availability VMware Snapshot DRS*

#CONVERGE2014

Reliability & Availability with VMware

Geo Redundancy: achieved through deployment of the necessary duplicated Avaya product

instances at different data centers (residing on but independent of VMware). examples; CM (SC), SM, SMGR, (AES FP4)

Zero Dropped Calls, Real Time Failover: achieved through current Avaya fail-over mechanisms on Avaya VE. examples; CM (SW dup), SM

Avaya Fast Reboot High Availability (FRHA): replaced Brief pause in operations associated with a node switchover/failover event,

plus the time it takes for all virtual machines to boot on the new active server. Provided by System Platform on Server appliances. No System Platform on

VMware. Avaya FRHA mechanisms are replaced by VMware HA, similar pause of

operations. examples: AES, SMGR

Avaya Machine Preserving High Availability (MPHA): not available Provided by System Platform, non-service affecting failover, zero delay. Not available for Avaya applications on VMware (no System Platform) To be replaced by VMware Fault Tolerance in the future. example: AES

VMWARE FEATURE DESCRIPTION

#CONVERGE2014

VMware vMotion

Description: Enables the live migration of virtual

machines from one host to another with continuous service availability.

Benefits: Revolutionary technology that is

the basis for automated virtual machine movement

Meets service level and performance goals

#CONVERGE2014

VMware vMotion

Cluster 1

SM02

Cluster 2

ESXi1

ESXi2 ESXi4

Management

CM01b and AES

ESXi3

Network

CM01a and US

Other VMs

CM01a - Communication Manager 01 aUS Utility Server

SM02 Session Manager 02 SM01 Session Manager 01

CM01b - Communication Manager 01 bAES Application Enablement Services

LegendDuplication LinkCustomer NetworkStorage NetworkVMware Management

Remote Storage

vCenterServer

vSphereClient PC

Goal is to perform maintenance on the host ESXI2. We will move the VM called SM02 to another hypervisor

#CONVERGE2014

vMotion - Operation

Cluster 1

SM02

Cluster 2

ESXi1

ESXi2 ESXi4

Management

CM01b and AES

ESXi3CM01a and US

Other VMs




LegendCM Duplication LinkCustomer NetworkStorage NetworkVMware Management

Remote Storage

vCenterServer

vSphereClient PC

Network

Base VM files transferred

from storage

#CONVERGE2014

vSphereClient PC

VMware vMotion Operation (contd)

Cluster 1 Cluster 2

ESXi1

ESXi2 ESXi4

Management

CM01b and AES

ESXi3CM01a and US

Other VMs


Active memory and precise execution state of the virtual machine is rapidly transferred over a high speed network, allowing the virtual machine to instantaneously switch from running on the source ESX host to the destination ESX host.

SM02 SM02

Remote Storage

vCenterServer

Network

#CONVERGE2014

VMware Storage vMotion

Description Live migration of virtual disks from

one storage location to another without disruption to users

Benefits Minimizes the need to

schedule application downtime due to storage maintenance, upgrades, or migration

#CONVERGE2014

VMware High Availability

Resource Pool

XDescription: Enables the high availability

of virtual machines by restarting them on a different vSphere host in the event of a failure

Benefits: Minimizes downtime and IT

service disruption Reduce cost and complexity

compared to traditional clustering VMware vSphere VMware vSphere VMware vSphere

#CONVERGE2014

Example Deployment Infrastructure

Cluster 1

SM02

Cluster 2

ESXi1

ESXi2 ESXi4

Management

CM01b and AES

ESXi3CM01a and US

SM01

CM Active

CMStandby


CM Software Duplication LinksThick Blue Links

CM Dup Links1 Gb Minimum




vCenterServer

vSphereClient PC

Network

Remote Storage

#CONVERGE2014

ESXi1 Host Failure

Cluster 1

SM02

Cluster 2

ESXi1

ESXi2 ESXi4

Management

CM01b and AES

ESXi3CM01a and US

SM01

CM Active

CMStandby


Remote Storage

Network

vCenterServer

vSphereClient PC

#CONVERGE2014

ESXi1 Host Offline Software Duplication

Cluster 1

SM02

Cluster 2

ESXi1

ESXi2 ESXi4

Management

CM01b and AES

ESXi3CM01a and US

SM01

CM Active

CMStandby

CMActive

CM instantly fails over to CM01b in Cluster 2 via CM Software duplication

ESXi1 Host Fails- Communication Manager detects the CM01a is offline and CM01b goes ACTIVE.- Utility Server is now offline

Remote Storage

Network

vCenterServer

vSphereClient PC

#CONVERGE2014

ESXi1 Host Offline VMware HA

Cluster 1

SM02

Cluster 2

ESXi1

ESXi2 ESXi4

Management

CM01b and AES

ESXi3CM01a and US

SM01

CM Active

CMStandby

CMActive

VMware detects the Host failure and moves applications to the other host server in the cluster (ESXi2).

- CM01a comes back online as the STANDBY server for the CM pair. Utility Server back online.

VMware HA boots CM01a and Utility

Server on ESXi host 2

CMStandby

SM02 plus CM01a and

US

Remote Storage

Network

vCenterServer

vSphereClient PC

#CONVERGE2014

VMware Snapshot

ProductionTest

Exact copy of production

123

Move changes into production

4

Faster testing More accurate testing on exact production copy Lower cost testing infrastructure

vAppOS

Web

OSAPP

OSDB

vAppOS

WebOSAPP

OSDB

vAppOS

WebOSAPP

OSDB

Run more tests faster

Archive for Fast Roll-back

DEPLOYMENT BEST PRACTICES

#CONVERGE2014

Flexible Resource Deployments

Ensure resource requirements are adjusted prior to Powering On Virtual Machine

Adjusting resources afterwards will cause errors shown to the right

#CONVERGE2014

Design Considerations

CMM not included in Simplex OVA CMM will have its own OVA with Feature Pack 4

You can mix physical Avaya appliances with VE guests Example: CM 6.2 Duplex VE with 1 Physical SMGR and

1 Physical SM at Core. Duplex VE Survivable Core with 1 VE SM at DR location

S8300 LSPs are supported to register against a CM VE core, however there is no S8300 CM vAppliance

ESS or Survivable Core servers are supported

#CONVERGE2014

Design Recommendations

CM Duplex Pair Customer to provide 2 new or existing ESX hosts to provide

service to Avaya CM based on the requirements Avaya has put forth VMWare HA is not supported by Avaya with Server A

and Server B running in the same cluster. If customer would like to use HA, multiple clusters would need to be available to support CM-Duplex.

Having both CM guests running on the same host is NOTrecommended and not supported

VMware HA is NOT a replacement for Duplex CM servers Customer should provide a Physical NIC on every host that

would support a CM Duplex server for SW-Dup Link

#CONVERGE2014

System Manager Geographic Redundancy

Both SMGR servers must be on VMware with the same Service Pack levels

Must have synchronized network time Ensure proper ports are open for both servers

to communicate to each other Requires 1.54MB of available bandwidth

between both SMGR servers for replication Latency must be under 500ms

#CONVERGE2014

AES using VMware HA

Using VMware HA for AES does have an outage window All links between AES and CM will go down while

virtual AES is being migrated to its new host If AES connectivity is critical you may want to

leverage Avaya AES MPHA. No disruption in service. Additional licensing required

#CONVERGE2014

AES Geo RedundancyVMware HA

DC1: Main site DC2: DR site

LAN/WAN< 100ms RTT

Active VMware

host

AES VMActive

Active VMware

host

AES VMStandby (AE Services are

restarted)

Standby datacenterActive datacenter

GRHA

Note: AE Services servers can have virtual IP addressNote: not using System Platform. Using VMware insteadOnly supported in 6.3.3

DMCC states are reconstructed upon failover

#CONVERGE2014

WebLM Recommendations

CM and AES vAppliances do not have an internal WebLM instance running

Licensing Deployment Options Install licenses on an existing or newly deployed System

Manager (Preferred method for CM) Install licenses on an existing WebLM server (Preferred for

AES) Deploy the WebLM vAppliance (Preferred for AES)

DEPLOYMENTS, UPGRADES, AND PATCH MANAGEMENT

#CONVERGE2014

Upgrading from 6.2 to 6.3 vAppliance

Plan upgrade for a maintenance window Perform current release backup data Install new release through VMware deployment.

Ensure any duplicate networking is network isolated Restore the backed-up data into the new release.

Validate operation Suspend service of the application appropriately Take a VMware snapshot and save for revert to current

version in case issues arise Operationalize new release VM and retire older VM.

6.2 vAppliance

6.3 vAppliance

#CONVERGE2014

Patch Management

Use the latest service-packs on each product May be applied differently

Product Server / Appliance patch process VMware patch process

CM System Platform (SP) Console CM SMI / Web pages

SM SM cli-command SM cli-command

SMGR SP Console SMGR cli-command

PS 6.1 SP Console, PS cli-command PS cli-command

AES SP Console, AES cli-command AES cli-command

ACE ACE cli-command ACE cli-command

US SP Console US cli-command

WebLM NA (WebLM not a separate product) WebLM cli-command

SAL SAL cli-commands SAL cli-commands

#CONVERGE2014

Application File Name PLDS ID File Size

ACE-6.2.1.29.31212-e51-00.ova ACE000000034

4.7GB

AES-6.3.0.0.212.20130403-e50-00.ova AES00000401 1.8GB

CM-Duplex-06.03.0.124.0-e51-1.ova CM000000378 915MB

CM-Simplex-06.03.0.124.0-e51-1.ova CM000000379 886MB

PS-6.2.0.0-182-VM-29.ova PS000000049 1.4GB

SALGateway-2.2.0.0-vApp-1.0.0.0-e50-09.ova SALVE000001 1.5GB

SM-6.3.2.0.632023-e50-00_OVF10.ova SM000000050 3.2GB

SMGR-6.3.0.8.5682-e50-64.ova SMGR6310005 3.0GB

US-6.3.0.0.20-e51-01_OVF10.ova US000000017 2.1GB

WebLM-6.3.2.4.6617-e50-4.16.ova SMGR6320004 947MB

Avaya Virtualized Application Manager

For engineers who are not comfortable with vSphere Deployment Only Tool Simplify deployment of Avaya virtualized

applications into VMware environments Supported on VMware 5.0, 5.1 & 5.5 AVAM 1.0 has support for the 10 VE1.0 & FP4 Applications

#CONVERGE2014

AVAM Administration

Add a Deployment

Enter the critical details for the Application deployment.

NOTE: Values are inherited from the Location.

Select Deploy on Submit or Schedule Deployment for the application to be installed.

#CONVERGE2014

AVAM Administration

Feature Pack & Flexible Footprint

Feature Pack

Select the Feature Pack you will deploy post-Install.

The Feature Pack is NOT installed with the OVA.

Flexible Footprint

Choose the proper footprint based on your install.

#CONVERGE2014

AVAM Administration

Add a DeploymentAVAM validates application required resources are available.

Accept the EULA when prompted.

REAL WORLD DEPLOYMENT

#CONVERGE2014

Large Entertainment Management Firm

CM 5.2.1 deployment in Southern California

Survivable Core Location in New York LSP locations in Miami, Nashville, London,

Plano, TX Large Digital Endpoint Deployment Wanted softclient for Boss/Admin

relationship to escalate calls to ad hoc conferencing to exceed the 6 party Meet-Me Limit

#CONVERGE2014

Proposed Solution

Beverly Hills Datacenter 3 ESX Hosts (CM Duplex, AES, SMGR, SM) 1 EMC VNXe SAN 1 vCenter Server

New York Datacenter 2 ESX Hosts (CM Duplex SC, AES, Geo-SMGR, SM) 1 EMC VNXe SAN 1 vCenter Server (Licensed for Heartbeat)

Avaya Aura Conferencing 7.2 Flare Experience for Windows* Integrate Polycom Video Solutions to Aura Carousel Managed Services - Smartpoint

#CONVERGE2014

Successful Deployment

Deployment completed in 30 days Customer required two quotes for

project Other Business Partner proposed an Avaya

appliance solution Customer saved $500,000.00 for going with

Carousel Industries Virtualized Proposal Customer used some of the savings for

Enterprise Video Solution Projects

#CONVERGE2014

What else can I Virtualize?

Polycom RealPresenceCollaboration (RMX)

Polycom RealPresenceDMA

Polycom RealPresenceResource Manager

Polycom RealPresenceAccess Director

Polycom RealPresenceCapture Server

Polycom RealPresencePlatform Director

Oracle (Acme) SBC Audiocodes SBC Sonus SBC NICE Verint And Many More..

#CONVERGE2014

Virtualization Roadmap

Avaya Aura R7.0 Avaya appliance with VMware hypervisor Expanded management options Flexibility in terms of applications and scale of appliance

(Midmarket vs. Enterprise)

VMware features Support for DRS (multiple applications) Reservation specification flexibility Processor support

THANK YOU

Avaya and virtualizationAvaya VMware ComparisonAvaya Aura Virtualized EnvironmentSlide Number 4Flexible FootprintsWhat does flexible resource mean?Advantages of VirtualizingAvaya AuraReliability & Availability with VMwareVmware feature descriptionVMware vMotionVMware vMotionvMotion - OperationVMware vMotion Operation (contd)VMware Storage vMotionVMware High Availability Example Deployment InfrastructureESXi1 Host FailureESXi1 Host Offline Software DuplicationESXi1 Host Offline VMware HAVMware SnapshotDeployment best practicesFlexible Resource DeploymentsDesign ConsiderationsDesign RecommendationsSystem Manager Geographic RedundancyAES using VMware HAAES Geo RedundancyVMware HAWebLM RecommendationsDeployments, Upgrades, and patch managementUpgrading from 6.2 to 6.3 vAppliancePatch ManagementAvaya Virtualized Application ManagerAVAM AdministrationAVAM AdministrationAVAM AdministrationReal world deploymentLarge Entertainment Management FirmProposed SolutionSuccessful DeploymentWhat else can I Virtualize?Virtualization RoadmapThank you

avaya_vmware

Documents