AVAYA AND VIRTUALIZATION

AVAYA AND VIRTUALIZATION

Avaya VMware Comparison VMware vcenter Administration Tool Avaya System Manager ESXi Hypervisor Application System Platform Host Physical Server Common Server Guest Virtual Server Template

Avaya Aura Virtualized Environment Avaya Aura applications supporting virtualization with VMware Avaya Aura 6.2 & 6.3 Communication Manager (includes Call Center Elite) Session Manager Presence Services System Manager Utility Services Secure Access Link WebLM Application Enablement Server ACE VMware vcenter Server VMware vsphere VMware vsphere VMware vsphere

Additional Avaya Virtualized Applications Avaya Aura applications supporting virtualization with VMware Aura Messaging 6.3 Aura Conferencing 8.0 Sipera SBC 6.2 FP2* Scopia Management IP Office 9.0 Experience Portal Elite Multi- Channel CMS R17 CMM 6.2 FP4 VMware vcenter Server VMware vsphere VMware vsphere VMware vsphere

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

What does flexible resource mean? Communication Manager 500 users Max resource vcpu RAM (GB) vcpu RAM (GB) 1 4 1 4 Session Manager 2 4 12 12 System Manager 3 7 4 9 AES 1 2 4 4 Totals 7 17 21 29 Host server dual processor, 4 core Host servers dual processor, 6 core Comparing base OVA resource vs. flexible resource specification

Advantages of Virtualizing Avaya Aura Continues to provide existing Avaya application 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*

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

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

VMware vmotion Cluster 1 ESXi1 CM01a and US CM01a - Communication Manager 01 a US Utility Server ESXi2 SM02 Remote Storage Network Cluster 2 ESXi3 CM01b and AES CM01b - Communication Manager 01 b AES Application Enablement Services ESXi4 Other VMs SM02 Session Manager 02 SM01 Session Manager 01 Managemen t vcenter Server vsphere Client PC Goal is to perform maintenance on the host ESXI2. We will move the VM called SM02 to another hypervisor Legend Duplication Link Customer Network Storage Network VMware Management

vmotion - Operation Cluster 1 ESXi1 CM01a and US CM01a - Communication Manager 01 a US Utility Server ESXi2 SM02 Remote Storage Network Base VM files transferred from storage Cluster 2 ESXi3 CM01b and AES CM01b - Communication Manager 01 b AES Application Enablement Services ESXi4 Other VMs SM02 Session Manager 02 SM01 Session Manager 01 Legend CM Duplication Link Customer Network Storage Network VMware Management Managemen t vcenter Server vsphere Client PC

VMware vmotion Operation (cont d) Cluster 1 Cluster 2 Remote Storage ESXi1 CM01a and US ESXi3 CM01b and AES ESXi2 SM02 Network ESXi4 SM02 Other VMs Managemen t vcenter Server vsphere Client PC 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. Legend CM Duplication Link Customer Network Storage Network VMware Management

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

VMware High Availability Description: Enables the high availability of virtual machines by restarting them on a different vsphere host in the event of a failure X Benefits: Resource Pool Minimizes downtime and IT service disruption Reduce cost and complexity compared to traditional clustering VMware vsphere VMware vsphere VMware vsphere

CM Active Cluster 1 ESXi1 CM01a and US CM01a - Communication Manager 01 a US Utility Server ESXi2 SM02 Example Deployment Infrastructure CM Software Duplication Links Thick Blue Links Remote Storage Network Cluster 2 ESXi3 CM01b and AES ESXi4 SM01 CM Standby CM01b - Communication Manager 01 b AES Application Enablement Services SM02 Session Manager 02 SM01 Session Manager 01 CM Dup Links 1 Gb Minimum Management vcenter Server vsphere Client PC Legend CM Duplication Link Customer Network Storage Network VMware Management

ESXi1 Host Failure CM Active Cluster 1 Cluster 2 CM Standby ESXi1 CM01a and US Remote Storage ESXi3 CM01b and AES ESXi2 Network ESXi4 SM02 SM01 Management vcenter Server vsphere Client PC Legend CM Duplication Link Customer Network Storage Network VMware Management

ESXi1 Host Offline Software Duplication CM Active Cluster 1 ESXi1 CM01a and US CM instantly fails over to CM01b in Cluster 2 via CM Software duplication Remote Storage Cluster 2 ESXi3 CM01b and AES CM Standby Active ESXi2 SM02 Network ESXi4 SM01 Management ESXi1 Host Fails - Communication Manager detects the CM01a is offline and CM01b goes ACTIVE. - Utility Server is now offline vcenter Server vsphere Client PC

ESXi1 Host Offline VMware HA CM Active Cluster 1 ESXi1 CM01a and US Remote Storage Cluster 2 ESXi3 CM01b and AES CM Standby Active ESXi2 SM02 plus CM01a SM02and US Network ESXi4 SM01 CM Standby VMware HA boots CM01a and Utility Server on ESXi host 2 Managemen t vcenter Server vsphere Client PC 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 Snapshot Test 4 Move changes into production Production 3 Run more tests faster Web OS APP OS vapp DB OS 2 Exact copy of 1 production Archive for Fast Roll-back Web OS APP OS vapp DB OS Web OS APP OS vapp DB OS Faster testing More accurate testing on exact production copy Lower cost testing infrastructure

DEPLOYMENT BEST PRACTICES

Flexible Resource Deployments Ensure resource requirements are adjusted prior to Powering On Virtual Machine Adjusting resources afterwards will cause errors shown to the right

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

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 NOT recommended 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

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

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

AES Geo Redundancy VMware HA DC1: Main site DC2: DR site AES VM Active GRHA AES VM Standby (AE Services are restarted) Active VMware host LAN/WAN < 100ms RTT Active VMware host Active datacenter Standby datacenter Note: AE Services servers can have virtual IP address Note: not using System Platform. Using VMware instead Only supported in 6.3.3 DMCC states are reconstructed upon failover

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

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

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

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 ACE-6.2.1.29.31212-e51-00.ova support for the 10 VE1.0 & FP4 Applications Application File Name PLDS ID File Size ACE00000003 4 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

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.

AVAM Administration Feature Pack & Flexible Footprint Feature Pack Flexible Footprint Select the Feature Pack you will deploy post- Install. Choose the proper footprint based on your install. The Feature Pack is NOT installed with the OVA.

AVAM Administration Add a Deployment AVAM validates application required resources are available. Accept the EULA when prompted.

REAL WORLD DEPLOYMENT

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

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

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

What else can I Virtualize? Polycom RealPresence Collaboration (RMX) Polycom RealPresence DMA Polycom RealPresence Resource Manager Polycom RealPresence Access Director Polycom RealPresence Capture Server Polycom RealPresence Platform Director Oracle (Acme) SBC Audiocodes SBC Sonus SBC NICE Verint And Many More..

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