Starting the Conversation: VMware in your Environment

1. Starting the Conversation:VMwarein your Environment Erik Solberg: 651.393.6208 - esolberg@nacr.com Georgene MacLennan: 651.796.6425 - gmaclennan@nacr.com

2. Avaya Aura®® Avaya Aura® Virtualized Environment VMware vCenter Server Avaya Aura® applications supporting virtualization with VMware* Communication Manager 6.2 (includes Call Center Elite) Session Manager 6.2 System Manager 6.2 Utility Services 6.2 Presence Services 6.1 Secure Access Link 2.2 Application Enablement Server 6.2 WebLM 6.2 ACE 6.2 VMware vSphere VMware vSphere VMware vSphere This new VMWare offering does not replace current Avaya hardware solution offerings!

3. Why Avaya Aura on VMware? • VMware Facts: • VMware 1Q2012 revenues up 25% year over year, operating income up 41% and license revenues up 15%* • For 2012 VMware has projected revenues will grow between 20% to 23% from 2011, and annual license revenues are expected to grow between 12% and 16%* • 94% of Fortune 1000 are VMware customers • 85% of Fortune 1000 are Avaya customers • 42% of customers using virtualization today are virtualizing or planning to virtualize their UC An Avaya Aura/VMware offer is a must in the market for those customers having VMware IT infrastructure

4. The Evolution of Avaya Aura® and Virtualization Avaya Aura® for Midsize Enterprise – 2400 users on a single server MBT- product for midmarket with 3 virtualized apps Avaya Aura® – appliance model with System Platform 2006 2008 2010 2012 Avaya Aura® For Virtualized Environment Avaya Integrates Avaya Aura® on VMware Avaya combines UC apps with VMware's real-time solution. Citrix XEN is agreed upon as better performing solution XEN leads to Avaya’s System Platform Virtualization. System Platform optimizes XEN for real-time, control and management System Platform leads to 7 apps per virtualized server. Avaya Aura® Contact Center Supports apps to VMware

5. CM Appliance versus a CM vApplication iLO UID CM vAppliance & ESXi Host CM Appliance VMware ESXi Host US vApplication TOP Duplication Link CM vApplication Customer Network X Services Port CM Application VSS4 Virtual Switch Services Dup Link Duplication VMware Tools Logical Representation of CM Server Appliance & US CM Network VSS3 Linux OS Customer NIC NIC NIC vNIC NIC NIC NIC NIC vNIC vNIC Management Network VSS0 CM Application VMware ESXi Hypervisor VSS1 Linux iSCSI Customer Server Hardware XEN Hypervisor Typically Disk is External Remote Disk Memory Server HW Services Port Memory Duplication Link SAN Storage Disk Customer Network

6. VMware Software Component Description ESXi Host- The physical machine running the ESXi Hypervisor software. ESXi Hypervisor - A platform that runs multiple operating systems on a host computer at the same time. vSphere Client- The client application that is installed on a personal computer or accessible through a Web interface. Enables the installation and management of virtual machines. vCenter-vCenter provides centralized control and visibility at every level of the virtual infrastructure. vSS-VMware Standard Switch, it is a virtual L2 switch that resides in the EXSi Host.

7. Supported Availability Models • Avaya Aura on VMware: • Continues to provide existing Avayaapplicationlevel 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 VMwareavailability methods • vMotion • vMotion Storage • VMware High Availability • VMware Snapshot

8. Differences between server and vAppliance • CM 6.2 • CM vAppliancedoes not contain CMM. Roadmap for VMware is Avaya Aura Messaging. • Survivable remote (formerly known as LSP) is not virtualized, CM vAppliance is compatible with the existing version. • CM vAppliance first release will not support Avaya Aura Contact Center. This is to be fully tested & supported in the future. CC Elite is supported. • SM 6.2 • SM vAppliance footprint is smaller than SM on Avaya server offer • Branch Session Manager is not virtualized but SM vAppliance will work with existing versions. • SMGR 6.2 • SMGR on Avaya server offer utilizes System Platform FRHA, SMGR vAppliance utilizes VMware HA

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

10. vMotion -- Operation Base VM files transferred from storage Cluster 1 Cluster 2 Remote Storage ESXi1 ESXi3 CM01a and US CM01b and AES CM01a - Communication Manager 01 a US – Utility Server CM01b - Communication Manager 01 b AES – Application Enablement Services ESXi2 ESXi4 Network SM02 Other VMs SM01 – Session Manager 01 SM02 – Session Manager 02 Management vCenter Server vSphere client PC Legend CM Duplication Link Customer Network Storage Network VMware Management

11. VMware® vMotion – Operation (cont’d) Cluster 1 Cluster 2 Remote Storage ESXi1 ESXi3 CM01a and US CM01b and AES ESXi2 ESXi4 Network SM02 SM02 Other VMs Management 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

12. Example Deployment infrastructure CM Software Duplication Links CM Standby Thick Red Links CM Active Cluster 1 Cluster 2 Remote Storage ESXi1 ESXi3 CM01a and US CM01b and AES CM01a - Communication Manager 01 a US – Utility Server CM01b - Communication Manager 01 b AES – Application Enablement Services ESXi2 ESXi4 Network SM02 SM01 SM01 – Session Manager 01 SM02 – Session Manager 02 Management CM Dup Links 1 Gb Minimum vCenter Server vSphere client PC Legend CM Duplication Link Customer Network Storage Network VMware Management Important: - Dark black links represent physical wiring and a physical L2 switch arrangement (VLANs applicable). - Dup Link must still adhere to PSN 003556u (Server Separation)

13. ESXi1 Host Failure CM Standby CM Active Cluster 1 Cluster 2 Remote Storage ESXi1 ESXi3 CM01a and US CM01b and AES ESXi2 ESXi4 Network SM02 SM01 Management vCenter Server vSphere client PC Legend CM Duplication Link Customer Network Storage Network VMware Management

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

15. ESXi1 Host Offline – VMware HA CM Active CM Standby CM Active Cluster 1 Cluster 2 Remote Storage ESXi1 ESXi3 CM01a and US CM01b and AES ESXi2 ESXi4 Network SM02 plus CM01a and US SM02 SM01 Management CM Standby VMware HA boots CM01a and Utility Server on ESXi host 2 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.

16. Example Deployment of Avaya Aura Geo Solution: (Across geographically dispersed data centers) Data Center 1 - Denver Data Centre 2 - Paris Cluster 1 Cluster 1 CM Main Remote Storage Remote Storage Survivable Core ESXi1 ESXi5 CM01a CM02a CM01a - Communication Manager 01 a CM02a - Communication Manager 02 a Active/Active Session Managers ESXi2 ESXi8 Main System Manager SM02 SMGR01 SM03 SM03 – Session Manager 03 SM02 – Session Manager 02 SMGR01 - System Manager 01 Local Network Local Network Local Network Local Network Enterprise Customer Network and Cloud Cluster 2 Cluster 2 ESXi7 Survivable Core Standby ESXi3 CM02b CM01b CM02a - Communication Manager 02 b CM Standby ESXi6 CM01a - Communication Manager 01 b Survivable Remote (supported on an Gateway S8300, not vAppliance) SM04 SMGR02 ESXi4 SM01 SM04 – Session Manager 04 SMGR02 - System Manager 02 SM02 – Session Manager 02 vCenter Server Management Network vSphere client PC Geo-Redundant System Manager Legend WAN or Internet Links Customer Network Storage Network VMware Management

17. Avaya Aura® Virtualized Environment Note: b) minimum CPU speed based on Xeon E5620 or equivalent Note: a) vCPU = Number of virtual machine CPU(s) . With Intel hyper-threading two vCPUs per physical core/CPU. With AMD one for one.

18. What can a provide? AND/OR

19. What does a pod “look like”? Server “Slices”

20. Pod’s are GREAT for high-availability VMware HA methods to ensure all applications continue to run in the event of a server failure!

21. Potential Upgrades and Additions - Applications Doesn’t have to be Avaya only

22. Avaya Collaboration Pod w/ Best of Breed Technologies What you would build yourself with unlimited time and budget • Leading vendor in collaboration and customer experience • Delivering networking, applications, management & integration • #1 storage vendor; most commonly selected with VMware • Delivering storage arrays for Avaya VAR • #1 server virtualization vendor • Delivering virtualization and VDI software

23. VDI

24. Session Manager Expanding Virtualization to the Desktop – VDI VDI virtual machine Soft phone IT Apps SIP Voice Controller SoftwareCodecs RTP Citrix /VMwareDevice and Graphics Drivers Data Center HDX/ICA/PCoIP VDI Thin Client Citrix /VM HDX Receiver Citrix/VM Visual Receiver Local Audio Drivers Graphics& Camera VDI Client Endpoints (Thin Clients)

25. Why VDI? • All Data is maintained in Data Center • More Secure • Back-ups more reliable • Simplified deployment • Support • Maintenance • Lower TCO

26. Unified Communications in a VDI Environment • Standard VDI is not well suited to drive real time media directly to the desktop. • Avaya’s Real Time UC solution for VDI • Avaya VDI Communicator 1.0 • Software installed on VDI thin client (desktop) • Provides connectivity to Avaya Aura CM & Session Manager • Processes all voice media locally on thin client off loading media processing from data center

27. Unified Communications in a VDI Environment • Avaya one-X Communicator • Runs on users virtual machine in Data Center • Shared control mode • Must run in “Desk Phone” mode • User interface only does not process any voice traffic

28. Avaya VDI Communicator User Interface Everydayscenario Loss of connectivity orVM machine down • Avaya one-X Communicatorrunning on virtual PC in the data center accessed via thin client • Avaya VDI Communicator client running on the thin client VDI Thin Client • Problem with the virtual machine • Problem in the data center • Problem with the network betweendata center and thin client

29. Avaya Real-Time UC Solution for VDI VDI Virtual PC VDI Thin Client Citrix/VMwareReceiver Remote desktop protocol (e.g., Citrix ICAVMware View PCoIP) Citrix/VM Virtual Device And Graphics Drivers One-X Communicator Business Apps GUI Desktop Data Center Avaya VDI Communicator Graphics& Camera SessionControl LocalAudioDrivers Control (SIP) Control (SIP) Media

30. Avaya VDI Communicator… solving for scale & QoS for improved real-time communications in VDI • Virtual Desktop • Avaya one-X Communicator view • VDI Communicator on HP or Dell Wyse Thin Clients; or Windows PC • Support for VMware View & Citrix Xen Desktop

31. Avaya VDI Communicator Release 1.0 Avaya Client Agent Headset

32. Thank You