VMware in Your Environment

Download Report

Transcript VMware in Your Environment

Starting the Conversation:
VMware in your Environment
Erik Solberg: 651.393.6208 - [email protected]
Georgene MacLennan: 651.796.6425 - [email protected]
Avaya Aura® Virtualized Environment
Avaya Aura® applications supporting virtualization with VMware*
Avaya Aura®®
Communication
Manager 6.2
(includes Call Center Elite)
Secure
Access Link
2.2
Session
Manager 6.2
Presence
Services 6.1
WebLM
6.2
System
Manager 6.2
Application
Enablement
Server 6.2
Utility Services
6.2
ACE
6.2
VMware vCenter Server
VMware vSphere
VMware vSphere
VMware vSphere
This new VMWare offering does not replace current Avaya hardware solution
offerings!
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
The Evolution of Avaya Aura® and Virtualization
MBT- product
for midmarket
with 3
virtualized apps
Avaya combines UC
apps with VMware's
real-time solution.
Citrix XEN is agreed
upon as better
performing solution
Avaya Aura® for
Midsize Enterprise –
2400 users on a
single server
Avaya Aura® –
appliance model
with System
Platform
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
Avaya Aura® For
Virtualized
Environment
Avaya Integrates
Avaya Aura® on
VMware
CM Appliance versus a CM vApplication
CM vAppliance & ESXi Host
CM Appliance
iLO
UID
TOP
Duplication Link
Customer Network
VMware ESXi Host
US vApplication
CM vApplication
Services Port
vNIC
CM Application
Logical Representation
of CM Server Appliance
CM Application
VMware Tools
Linux OS
X
Services
VSS4
vNIC
Virtual
Switch
NIC
VSS3
NIC
CM & US
Network
VSS0
NIC
Management
Network
VSS1
NIC
Duplication
vNIC
Customer
VMware ESXi Hypervisor
Linux
iSCSI
Customer Server Hardware
XEN Hypervisor
Server HW
NIC
Services Port
Memory
NIC
Duplication Link
NIC
Customer Network
Disk
Dup
Link
Memory
Typically Disk is
External
Remote
Disk
SAN
Storage
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.
Supported Availability Models
•
•
Avaya Aura on VMware:
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
Differences between server and vAppliance
•
CM 6.2
•
•
•
•
SM 6.2
•
•
•
CM vAppliance does 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 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
VMware® vMotion
Cluster 1
ESXi1
Cluster 2
Remote
Storage
CM01a
and US
CM01a - Communication Manager 01 a
US – Utility Server
ESXi2
ESXi3
CM01b
and AES
CM01b - Communication Manager 01 b
AES – Application Enablement Services
Network
SM02
ESXi4
Other VMs
SM01 – Session Manager 01
SM02 – Session Manager 02
Management
vCenter
Server
Goal is to perform maintenance on the host ESXI2. We will
move the VM called SM02 to another hypervisor
vSphere
client PC
Legend
Duplication Link
Customer Network
Storage Network
VMware Management
vMotion -- Operation
Cluster 1
ESXi1
Base VM files
transferred
from storage
Remote
Storage
CM01a
and US
CM01a - Communication Manager 01 a
US – Utility Server
ESXi2
Cluster 2
ESXi3
CM01b
and AES
CM01b - Communication Manager 01 b
AES – Application Enablement Services
Network
SM02
ESXi4
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
VMware® vMotion – Operation (cont’d)
Cluster 1
ESXi1
Cluster 2
Remote
Storage
ESXi3
CM01b
and AES
CM01a
and US
ESXi2
ESXi4
Network
SM02
Other VMs
SM02
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
Example Deployment infrastructure
CM Software Duplication Links
CM
Active
CM
Standby
Thick Red Links
Cluster 1
Cluster 2
Remote
Storage
ESXi1
CM01a
and US
CM01a - Communication Manager 01 a
US – Utility Server
ESXi3
CM01b
and AES
CM01b - Communication Manager 01 b
AES – Application Enablement Services
ESXi2
Network
SM02
ESXi4
SM01
SM01 – Session Manager 01
SM02 – Session Manager 02
Management
CM Dup Links
1 Gb Minimum
vCenter
Server
vSphere
client PC
Legend
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)
CM Duplication Link
Customer Network
Storage Network
VMware Management
ESXi1 Host Failure
CM
Active
CM
Standby
Cluster 1
ESXi1
Cluster 2
Remote
Storage
CM01a
and US
ESXi2
Network
SM02
ESXi3
CM01b
and AES
ESXi4
SM01
Management
vCenter
Server
vSphere
client PC
Legend
CM Duplication Link
Customer Network
Storage Network
VMware Management
ESXi1 Host Offline – Software Duplication
CM
Active
CM instantly fails over to CM01b in Cluster 2
via CM Software duplication
Cluster 1
ESXi1
Cluster 2
Remote
Storage
CM01a
and US
ESXi2
CM
Active
Standby
Network
SM02
ESXi3
CM01b
and AES
ESXi4
SM01
Management
ESXi1 Host Fails
vCenter
Server
vSphere
client PC
- Communication Manager detects the CM01a is offline and CM01b goes ACTIVE.
- Utility Server is now offline
ESXi1 Host Offline – VMware HA
CM
Active
CM
Active
Standby
Cluster 1
ESXi1
Cluster 2
Remote
Storage
CM01a
and US
ESXi2
SM02 plus
SM02
CM01a
and US
CM
Standby
VMware HA boots
CM01a and Utility Server
on ESXi host 2
Network
ESXi3
CM01b
and AES
ESXi4
SM01
Management
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.
Example Deployment of Avaya Aura Geo Solution:
(Across geographically dispersed data centers)
Data Center 1 - Denver
CM Main
Data Centre 2 - Paris
Cluster 1
ESXi1
CM01a
Cluster 1
ESXi5
CM02a
CM01a - Communication Manager 01 a
ESXi2
SM02
SMGR01
Main
System
Manager
Remote
Storage
CM
Standby
CM02a - Communication Manager 02 a
Active/Active
Session
Managers
SM02 – Session Manager 02
SMGR01 - System Manager 01
Local
Network
Local
Network
Cluster 2
ESXi3
CM01b
CM01a - Communication Manager 01 b
ESXi4
SM01
Survivable
Core
ESXi8
SM03
SM03 – Session Manager 03
Local
Network
Local
Network
Enterprise
Customer Network and
Cloud
Remote
Storage
Cluster 2
ESXi7
CM02b
CM02a - Communication Manager 02 b
Survivable Remote (supported
on an Gateway S8300, not
vAppliance)
Survivable
Core
Standby
ESXi6
SM04
SMGR02
SM04 – Session Manager 04
SMGR02 - System Manager 02
SM02 – Session Manager 02
Management
Network
vCenter
Server
vSphere
client PC
Geo-Redundant
System Manager
Legend
WAN or Internet Links
Customer Network
Storage Network
VMware Management
Avaya Aura® Virtualized Environment
Avaya Aura®
on VMware
Release
Capacity
vCPU
(users)
(virtual
CPU) a
Virtual
Memory
Virtual
Storage
Minimum
CPU Speed
(GB)
(GB)
(GHZ) b
Communication
Manager
(Includes CC Elite)
6.2
36K
1
4
30
2.4
Communication
Manager
Sw-Duplication
(Includes CC Elite)
6.2
36K
3
5
30
2.9
Application
Enablement
Services
6.2
4K Endpoints or
20K simultaneous
MOC/LCS
4
4
20
2.4
Session Manager
6.2
6K
8
12
150
1.995
Presence Services
6.1
2.5K
8
8
82
2.4
Utility Services
6.2
Support 5k IP
Endpoints
1
1
20
2.4
System Manager
6.2
250K,
50 Administrators
simultaneously
4
6
70
2.4
Web LM
6.2
5K simultaneous
requests
1
1
10
2.4
ACE
6.2
4K
4
12
150
2.6
SAL
2.2
500 Elements
2
2
40
2.0
Note: a) vCPU = Number of virtual machine CPU(s) . With Intel hyper-threading
two vCPUs per physical core/CPU. With AMD one for one.
Note: b) minimum CPU speed based on
Xeon E5620 or equivalent
What can a
AND/OR
provide?
What does a pod “look like”?
Server “Slices”
CM A (Duplicated)
WebLM
AES
System Manager
CM B (Duplicated)
WebLM
Session Manager
VMware Vcenter
Utility Server
Session Manager
SAL
Pod’s are GREAT for high-availability
CM Duplex A
WebLM
AES
System
Manager
CM Duplex B
WebLM
AES
Now Active
Session
Manager
System
Manager
Utility Server
Session
Manager
VMware
Vcenter
SAL
VMware HA methods to ensure all applications
continue to run in the event of a server failure!
Potential Upgrades and Additions - Applications
CM Duplex A
WebLM
AES
System
Manager
Esnatech
Voicemail
WebLM
Session
Manager
VMware
Vcenter
Utility Server
Session
Manager
Ingate SBC
SAL
CM Duplex B
Ingate SBC
Doesn’t have to be Avaya only
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 server virtualization vendor
•
Delivering virtualization and VDI
software
•
#1 storage vendor; most commonly
selected with VMware
•
Delivering storage arrays for Avaya
VAR
VDI
Expanding Virtualization to the Desktop – VDI
What is VDI?
VDI virtual machine
Soft phone
Virtual Desktop Infrastructure
Virtual Desktop Interface
SIP
Session Manager
RTP
Deployment Model
Users PC runs virtually in Data Center
Monitor, Keyboard, & Attached Thin Client
on users desktop
Data Center
IT Apps
Voice
Controller
Software
Codecs
Citrix /VMware
Device and Graphics Drivers
HDX/ICA/P
CoIP
Citrix /VM
HDX Receiver
Citrix/VM
Visual Receiver
VDI Thin Client
Local
Audio Drivers
Graphics
& Camera
VDI Client Endpoints
(Thin Clients)
Why VDI?







All Data is maintained in Data Center
More Secure
Back-ups more reliable
Simplified deployment
Support
Maintenance
Lower TCO
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
o
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
Unified Communications in a VDI Environment
o
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
Avaya VDI Communicator User Interface
Everyday
scenario
 Avaya one-X Communicator
running on virtual PC in the
data center accessed via thin
client
Loss of connectivity or
VM machine down
 Avaya VDI Communicator client
running on the thin client
 Problem withVDI
theThin
virtual
machine
Client
 Problem in the data center
 Problem with the network between
data center and thin client
Avaya Real-Time UC Solution for VDI
VDI
Thin Client
Desktop
Avaya
VDI
Communicator
VDI Virtual PC
Citrix/
VMware
Receiver
Graphics
& Camera
Local
Audio
Drivers
Remote desktop
protocol
(e.g., Citrix ICA
VMware View
PCoIP)
Citrix/VM
Virtual
Device
And
Graphics
Drivers
One-X
Communicator
Business
Apps
GUI
Data Center
Session
Control
Control (SIP)
Control (SIP)
Media
Avaya Approach
• Media direct to client
• Lighter load on server
• QoS model supported
• Call path unaffected by VDI architecture
“Headless Client” on end-point
• Media terminated locally
• “Remote Control” of Real Time app is extended
to ‘local client’ on the VDI end point
• Session Down UI for loss of connection scenarios
Avaya VDI Communicator
… solving for scale & QoS for improved real-time communications in VDI
Performance
• off loads processing of real time
communications to thin client or PC
and Avaya Aura
Survivability
• basic voice if connection to data
center or virtual PC is down
Flexibility
• works in various customer
environments; choice of vendors
within the VDI ecosystem
Software only
• no Avaya hardware required
• desk phone is optional
Collaboration
• Voice, IM/Presence, contacts /
directory, conferencing, messaging
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
Avaya VDI Communicator Release 1.0
Avaya
Client
Avaya Infrastructure & Clients
Thin Client
OS
Avaya Aura Communication Manager 6.0+
HP T510
WES7 or ThinPro 4.1
Avaya Aura Session Manager 6.0+
HP T610
WES7 or ThinPro 4.1
Avaya one-X Communicator SIP 6.1 SP5
HP T5740e
WES7
HP T 5565
ThinPro (Linux) 4.1
Dell-Wyse R50L
SLETC11 SP1
Windows PC
Windows 7 32/64 bit
Windows PC
Windows XP SP3 32 bit
Agent
Headset
VDI Broker
Supported USB Headsets
VMware View 5.X
Plantronics Blackwire C300 Series
Citrix XenDesktop 5.X
Plantronics Blackwire C400 Series
Plantronics Blackwire C600 Series
Thank You