Deploying Avaya Aura Messaging using VMware in the Virtualized Environment - Release 7.2.0 Issue 3 November 2021
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
Deploying Avaya Aura® Messaging using
VMware® in the Virtualized Environment
Release 7.2.0
Issue 3
November 2021
© 2017-2021, Avaya Inc. YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU
All Rights Reserved. MUST NOT ACCESS OR USE THE HOSTED SERVICE OR
AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED
Notice SERVICE.
While reasonable efforts have been made to ensure that the Licenses
information in this document is complete and accurate at the time of THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
printing, Avaya assumes no liability for any errors. Avaya reserves WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO,
the right to make changes and corrections to the information in this UNDER THE LINK “AVAYA SOFTWARE LICENSE TERMS (Avaya
document without the obligation to notify any person or organization Products)” OR SUCH SUCCESSOR SITE AS DESIGNATED BY
of such changes. AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS,
Documentation disclaimer USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED
FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA
“Documentation” means information published in varying mediums CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL
which may include product information, operating instructions and AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER.
performance specifications that are generally made available to users UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING,
of products. Documentation does not include marketing materials. AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE
Avaya shall not be responsible for any modifications, additions, or WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA
deletions to the original published version of Documentation unless AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA
such modifications, additions, or deletions were performed by or on RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU
the express behalf of Avaya. End User agrees to indemnify and hold AND ANYONE ELSE USING OR SELLING THE SOFTWARE
harmless Avaya, Avaya's agents, servants and employees against all WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR
claims, lawsuits, demands and judgments arising out of, or in USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,
connection with, subsequent modifications, additions or deletions to YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM
this documentation, to the extent made by End User. YOU ARE INSTALLING, DOWNLOADING OR USING THE
Link disclaimer SOFTWARE (HEREINAFTER REFERRED TO
INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO
Avaya is not responsible for the contents or reliability of any linked THESE TERMS AND CONDITIONS AND CREATE A BINDING
websites referenced within this site or Documentation provided by CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
Avaya. Avaya is not responsible for the accuracy of any information, APPLICABLE AVAYA AFFILIATE (“AVAYA”).
statement or content provided on these sites and does not
necessarily endorse the products, services, or information described Avaya grants You a license within the scope of the license types
or offered within them. Avaya does not guarantee that these links will described below, with the exception of Heritage Nortel Software, for
work all the time and has no control over the availability of the linked which the scope of the license is detailed below. Where the order
pages. documentation does not expressly identify a license type, the
applicable license will be a Designated System License as set forth
Warranty below in the Designated System(s) License (DS) section as
applicable. The applicable number of licenses and units of capacity
Avaya provides a limited warranty on Avaya hardware and software.
for which the license is granted will be one (1), unless a different
Refer to your sales agreement to establish the terms of the limited
number of licenses or units of capacity is specified in the
warranty. In addition, Avaya’s standard warranty language, as well as
documentation or other materials available to You. “Software” means
information regarding support for this product while under warranty is
computer programs in object code, provided by Avaya or an Avaya
available to Avaya customers and other parties through the Avaya
Channel Partner, whether as stand-alone products, pre-installed on
Support website: https://support.avaya.com/helpcenter/
getGenericDetails?detailId=C20091120112456651010 under the link hardware products, and any upgrades, updates, patches, bug fixes,
“Warranty & Product Lifecycle” or such successor site as designated or modified versions thereto. “Designated Processor” means a single
by Avaya. Please note that if You acquired the product(s) from an stand-alone computing device. “Server” means a set of Designated
authorized Avaya Channel Partner outside of the United States and Processors that hosts (physically or virtually) a software application
Canada, the warranty is provided to You by said Avaya Channel to be accessed by multiple users. “Instance” means a single copy of
Partner and not by Avaya. the Software executing at a particular time: (i) on one physical
machine; or (ii) on one deployed software virtual machine (“VM”) or
“Hosted Service” means an Avaya hosted service subscription that similar deployment.
You acquire from either Avaya or an authorized Avaya Channel
Partner (as applicable) and which is described further in Hosted SAS Licence types
or other service description documentation regarding the applicable Designated System(s) License (DS). End User may install and use
hosted service. If You purchase a Hosted Service subscription, the each copy or an Instance of the Software only: 1) on a number of
foregoing limited warranty may not apply but You may be entitled to Designated Processors up to the number indicated in the order; or 2)
support services in connection with the Hosted Service as described up to the number of Instances of the Software as indicated in the
further in your service description documents for the applicable order, Documentation, or as authorized by Avaya in writing. Avaya
Hosted Service. Contact Avaya or Avaya Channel Partner (as may require the Designated Processor(s) to be identified in the order
applicable) for more information. by type, serial number, feature key, Instance, location or other
Hosted Service specific designation, or to be provided by End User to Avaya through
electronic means established by Avaya specifically for this purpose.
THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA
HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA Concurrent User License (CU). End User may install and use the
CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE Software on multiple Designated Processors or one or more Servers,
FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA so long as only the licensed number of Units are accessing and using
WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO UNDER the Software at any given time as indicated in the order,
THE LINK “Avaya Terms of Use for Hosted Services” OR SUCH Documentation, or as authorized by Avaya in writing. A “Unit” means
SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE the unit on which Avaya, at its sole discretion, bases the pricing of its
APPLICABLE TO ANYONE WHO ACCESSES OR USES THE licenses and can be, without limitation, an agent, port or user, an e-
HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED mail or voice mail account in the name of a person or corporate
SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON function (e.g., webmaster or helpdesk), or a directory entry in the
BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE administrative database utilized by the Software that permits one
DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY user to interface with the Software. Units may be linked to a specific,
AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF identified Server or an Instance of the Software.
YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A Named User License (NU). End User may: (i) install and use each
COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT copy or Instance of the Software on a single Designated Processor or
YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE Server per authorized Named User (defined below); or (ii) install and
TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF use each copy or Instance of the Software on a Server so long as
only authorized Named Users access and use the Software as The following applies only if the H.264 (AVC) codec is distributed with
indicated in the order, Documentation, or as authorized by Avaya in the product. THIS PRODUCT IS LICENSED UNDER THE AVC
writing. “Named User”, means a user or device that has been PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A
expressly authorized by Avaya to access and use the Software. At CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE
Avaya’s sole discretion, a “Named User” may be, without limitation, REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH
designated by name, corporate function (e.g., webmaster or THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC
helpdesk), an e-mail or voice mail account in the name of a person or VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A
corporate function, or a directory entry in the administrative database PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO
utilized by the Software that permits one user to interface with the PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS
Software. GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.
ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA,
Shrinkwrap License (SR). End User may install and use the Software L.L.C. SEE HTTP://WWW.MPEGLA.COM.
in accordance with the terms and conditions of the applicable license
agreements, such as “shrinkwrap” or “clickthrough” license Service Provider
accompanying or applicable to the Software (“Shrinkwrap License”)
as indicated in the order, Documentation, or as authorized by Avaya THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’S
in writing. HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT
OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS
Heritage Nortel Software SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE
PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY FROM
“Heritage Nortel Software” means the software that was acquired by
THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL PARTNER’S
Avaya as part of its purchase of the Nortel Enterprise Solutions
HOSTING OF AVAYA PRODUCTS MUST BE AUTHORIZED IN
Business in December 2009. The Heritage Nortel Software is the WRITING BY AVAYA AND IF THOSE HOSTED PRODUCTS USE
software contained within the list of Heritage Nortel Products located OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING
at https://support.avaya.com/LicenseInfo under the link “Heritage BUT NOT LIMITED TO MICROSOFT SOFTWARE OR CODECS,
Nortel Products” or such successor site as designated by Avaya. For THE AVAYA CHANNEL PARTNER IS REQUIRED TO
Heritage Nortel Software, Avaya grants Customer a license to use INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE
Heritage Nortel Software provided hereunder solely to the extent of AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’S EXPENSE,
the authorized activation or authorized usage level, solely for the DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER.
purpose specified in the Documentation, and solely as embedded in,
for execution on, or for communication with Avaya equipment. WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL
Charges for Heritage Nortel Software may be based on extent of PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED
activation or use authorized as specified in an order or invoice. THE H.264 CODEC OR H.265 CODEC, THE AVAYA CHANNEL
PARTNER ACKNOWLEDGES AND AGREES THE AVAYA
Copyright CHANNEL PARTNER IS RESPONSIBLE FOR ANY AND ALL
Except where expressly stated otherwise, no use should be made of RELATED FEES AND/OR ROYALTIES. THE H.264 (AVC) CODEC
materials on this site, the Documentation, Software, Hosted Service, IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE
or hardware provided by Avaya. All content on this site, the FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES
documentation, Hosted Service, and the product provided by Avaya IN WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I)
including the selection, arrangement and design of the content is ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD
owned either by Avaya or its licensors and is protected by copyright (“AVC VIDEO”) AND/OR (II) DECODE AVC VIDEO THAT WAS
and other intellectual property laws including the sui generis rights ENCODED BY A CONSUMER ENGAGED IN A PERSONAL
relating to the protection of databases. You may not modify, copy, ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER
reproduce, republish, upload, post, transmit or distribute in any way LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED
any content, in whole or in part, including any code and software OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL
unless expressly authorized by Avaya. Unauthorized reproduction, INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS
transmission, dissemination, storage, and or use without the express MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://
written consent of Avaya can be a criminal, as well as a civil offense WWW.MPEGLA.COM.
under the applicable law. Compliance with Laws
Virtualization You acknowledge and agree that it is Your responsibility for
The following applies if the product is deployed on a virtual machine. complying with any applicable laws and regulations, including, but not
Each product has its own ordering code and license types. Unless limited to laws and regulations related to call recording, data privacy,
otherwise stated, each Instance of a product must be separately intellectual property, trade secret, fraud, and music performance
licensed and ordered. For example, if the end user customer or rights, in the country or territory where the Avaya product is used.
Avaya Channel Partner would like to install two Instances of the Preventing Toll Fraud
same type of products, then two products of that type must be
ordered. “Toll Fraud” is the unauthorized use of your telecommunications
system by an unauthorized party (for example, a person who is not a
Third Party Components corporate employee, agent, subcontractor, or is not working on your
“Third Party Components” mean certain software programs or company's behalf). Be aware that there can be a risk of Toll Fraud
portions thereof included in the Software or Hosted Service may associated with your system and that, if Toll Fraud occurs, it can
contain software (including open source software) distributed under result in substantial additional charges for your telecommunications
third party agreements (“Third Party Components”), which contain services.
terms regarding the rights to use certain portions of the Software Avaya Toll Fraud intervention
(“Third Party Terms”). As required, information regarding distributed
Linux OS source code (for those products that have distributed Linux If You suspect that You are being victimized by Toll Fraud and You
OS source code) and identifying the copyright holders of the Third need technical assistance or support, call Technical Service Center
Party Components and the Third Party Terms that apply is available Toll Fraud Intervention Hotline at +1-800-643-2353 for the United
in the products, Documentation or on Avaya’s website at: https:// States and Canada. For additional support telephone numbers, see
support.avaya.com/Copyright or such successor site as designated the Avaya Support website: https://support.avaya.com or such
by Avaya. The open source software license terms provided as Third successor site as designated by Avaya.
Party Terms are consistent with the license rights granted in these
Security Vulnerabilities
Software License Terms, and may contain additional rights benefiting
You, such as modification and distribution of the open source Information about Avaya’s security support policies can be found in
software. The Third Party Terms shall take precedence over these the Security Policies and Support section of https://
Software License Terms, solely with respect to the applicable Third support.avaya.com/security.
Party Components to the extent that these Software License Terms
impose greater restrictions on You than the applicable Third Party
Terms.
Suspected Avaya product security vulnerabilities are handled per the Avaya Product Security Support Flow (https:// support.avaya.com/css/P8/documents/100161515). Downloading Documentation For the most current versions of Documentation, see the Avaya Support website: https://support.avaya.com, or such successor site as designated by Avaya. Contact Avaya Support See the Avaya Support website: https://support.avaya.com for product or Hosted Service notices and articles, or to report a problem with your Avaya product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: https://support.avaya.com (or such successor site as designated by Avaya), scroll to the bottom of the page, and select Contact Avaya Support. Trademarks The trademarks, logos and service marks (“Marks”) displayed in this site, the Documentation, Hosted Service(s), and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, its licensors, its suppliers, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation, Hosted Service(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. All non-Avaya trademarks are the property of their respective owners. Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
Contents
Chapter 1: Introduction............................................................................................................ 8
Purpose of this guide............................................................................................................... 8
Change history........................................................................................................................ 8
Prerequisites........................................................................................................................... 9
®
Chapter 2: Avaya Aura Virtualized Environment overview.............................................. 10
Topology............................................................................................................................... 12
Components......................................................................................................................... 13
Avaya components.......................................................................................................... 13
VMware components....................................................................................................... 14
Third-party components................................................................................................... 15
Chapter 3: Deployment process............................................................................................ 16
Chapter 4: Planning and preconfiguration........................................................................... 17
Planning checklist.................................................................................................................. 17
Software requirements..................................................................................................... 17
WebLM........................................................................................................................... 19
Key customer configuration information............................................................................. 19
Configuration tools and utilities......................................................................................... 20
Downloading the Messaging OVA........................................................................................... 21
Registering for PLDS....................................................................................................... 21
Downloading software from PLDS.................................................................................... 21
Chapter 5: Initial setup and connectivity.............................................................................. 23
Deployment guidelines........................................................................................................... 23
Hardware requirements......................................................................................................... 23
Supported hardware for VMware...................................................................................... 23
Messaging virtual machine resource requirements............................................................. 23
Software installation checklist................................................................................................. 26
Deploying Messaging using vSphere Client....................................................................... 26
Deploying Messaging using vSphere Web Client............................................................... 29
Deploying the Messaging OVA using the vSphere client connected to vCenter..................... 32
Starting the Messaging virtual machine............................................................................. 34
Chapter 6: Configuration........................................................................................................ 36
Configuration checklist........................................................................................................... 36
Configuring the virtual machine automatic startup settings........................................................ 37
Configuring network settings and adding a privileged administrator account............................... 37
Changing a temporary administrator password........................................................................ 38
IPv6..................................................................................................................................... 39
Enabling IPv6.................................................................................................................. 40
Disabling IPv6................................................................................................................. 41
Configuring additional network settings................................................................................... 41
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 5
Comments on this document? infodev@avaya.comContents
Network Configuration field descriptions.................................................................................. 42
Setting the time zone............................................................................................................. 43
Setting up the network time protocol....................................................................................... 44
Service pack installation......................................................................................................... 44
Messaging service packs................................................................................................. 44
Downloading service packs.............................................................................................. 45
Installing a service pack................................................................................................... 45
Removing a service pack................................................................................................. 47
Configuring languages........................................................................................................... 49
Languages field descriptions.................................................................................................. 51
Configuring MWI................................................................................................................... 52
MWI administration.......................................................................................................... 52
Enabling SIP telephony integration................................................................................... 52
Telephony Integration field descriptions............................................................................. 52
Creating a SIP entity of a storage server on System Manager............................................. 54
Chapter 7: Initial administration............................................................................................ 57
Initial administration checklist................................................................................................. 57
Account management...................................................................................................... 57
License management...................................................................................................... 59
Data backup and restore.................................................................................................. 62
Stopping Messaging........................................................................................................ 66
Starting Messaging.......................................................................................................... 67
Shutting down the server................................................................................................. 67
Transferring files using WinSCP....................................................................................... 67
Chapter 8: Optimization and scalability................................................................................ 69
BIOS.................................................................................................................................... 69
Intel Virtualization Technology.......................................................................................... 69
Dell PowerEdge Server ................................................................................................... 70
HP ProLiant G8 and G9 Servers....................................................................................... 70
VMware Tools....................................................................................................................... 70
Timekeeping......................................................................................................................... 71
VMware networking best practices.......................................................................................... 72
Thin vs. thick deployments..................................................................................................... 75
Chapter 9: Related resources................................................................................................ 76
Documentation...................................................................................................................... 76
Security.......................................................................................................................... 76
VMware configurations.................................................................................................... 76
Administration................................................................................................................. 77
User functions................................................................................................................. 77
Training................................................................................................................................ 78
Viewing Avaya Mentor videos................................................................................................. 78
Support................................................................................................................................ 79
Using the Avaya InSite Knowledge Base........................................................................... 79
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 6
Comments on this document? infodev@avaya.comContents
Appendix A: Messaging upgrade operations....................................................................... 80
Overview.............................................................................................................................. 80
Backing up data from the old system....................................................................................... 80
Restoring data on the new Messaging VMware Virtual Machine................................................ 81
Appendix B: Migration............................................................................................................ 84
Overview.............................................................................................................................. 84
Migration roadmap and limitations.................................................................................... 84
Migrating Messaging to Virtualized Environment...................................................................... 85
Backing up data from the old system................................................................................. 85
Restoring data on the new system.................................................................................... 86
Appendix C: Upgrading Avaya Converged Platform from Release 4.0 to 5.0 with
®
Avaya Aura Messaging 7.2................................................................................................... 88
Glossary................................................................................................................................... 91
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 7
Comments on this document? infodev@avaya.comChapter 1: Introduction
Purpose of this guide
This document provides procedures for deploying the Avaya Aura® Messaging virtual application
in the Avaya Aura® Virtualized Environment. The procedures relate to installation, configuration,
initial administration, troubleshooting, and basic maintenance of the application.
This document is intended for people who install and configure a verified reference configuration
at a customer site.
Change history
Issue Date Summary of changes
Release November 2021 • Removed unsupported upgrade and migration paths for Avaya
7.2.0, Aura® Messaging Releases 6.3.2 and 6.2.5 from Overview on
Issue 3 page 80 and Migration roadmap and limitations on page 84.
• Removed steps related to Avaya Aura® Messaging Releases 6.3.2
and 6.2.5 from Restoring data on the new Messaging VMware
Virtual Machine on page 81 and Restoring data on the new
system on page 86.
• Updated supported migration paths in Migration roadmap and
limitations on page 84.
• Added Upgrading Avaya Converged Platform from Release 4.0 to
5.0 with Avaya Aura Messaging 7.2 on page 88.
Release June 2021 • Added information about vSphere Web Client and vSphere Client
7.2.0, (HTML5) to VMware components on page 14.
Issue 2
• Indicated that Avaya Aura® Messaging supports VMware release
7.0 and does not support VMware releases 5.x in Software
requirements on page 17.
• Updated the Next steps section in Deploying the Messaging OVA
using vSphere Web Client on page 29 and Deploying the
Messaging OVA using the vSphere client connected to vCenter on
page 32.
Table continues…
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 8
Comments on this document? infodev@avaya.comPrerequisites
Issue Date Summary of changes
• Updated links in VMware networking best practices on page 72.
Release October 2020 • Indicated that Avaya Aura® Messaging supports Red Hat
7.2.0, Enterprise Linux® 7.6.
Issue 1
• Indicated that a password for a privileged administrator account
must be changed at the first login to the Messaging SMI in
Configuration checklist on page 36.
• Added Changing a temporary administrator password on
page 38.
• Updated supported upgrade paths in Overview on page 80.
Prerequisites
Before deploying Avaya Aura® Messaging, ensure that you have the following knowledge, skills,
and tools:
Knowledge
Avaya Telephony platforms such as Communication Manager.
Tools
• VMware tools
• SFTP client
• SSH client
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 9
Comments on this document? infodev@avaya.comChapter 2: Avaya Aura® Virtualized
Environment overview
Avaya Aura® Virtualized Environment integrates real-time Avaya Aura® applications with the
virtualized server architecture of VMware. Virtualized Environment provides the following benefits:
• Simplifies IT management using common software administration and maintenance.
• Requires fewer servers and racks, which reduces the footprint.
• Lowers cooling requirements, which reduces power consumption.
• Enables cost savings on capital equipment.
• Lowers operational expenses.
• Uses standard operating procedures for both Avaya and non-Avaya products.
• Enables deployment of Avaya products in a virtualized environment on customer-specified
servers and hardware.
• Accommodates business scalability and rapid response to changing business needs.
Note:
The following terms are often used interchangeably in the document:
• Server and host
• Reservations and configuration values
Customer deployment
For customers who have a VMware IT infrastructure, Avaya Aura® Virtualized Environment provides
an opportunity to deploy using their own VMware infrastructure.
The Virtualized Environment capability is only for VMware and is not intended to include any other
industry hypervisor.
You can deploy Avaya Aura® Messaging on Virtual Environment in the following ways:
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 10
Comments on this document? infodev@avaya.comDeployment Deployment client Deployment Flexible Footprint
Environment configuration
vCenter with vCenter client The system You have to manually set the
prompts for hard disk size after deployment
Networking, NTP, through Edit Settings.
DNS, customer
login at the
deployment time.
without vCenter client, on ESXi The user needs Not applicable.
host use System
Management
Interface to
configure the
parameters.
with vSphere web client
Software delivery
The software is delivered as prepackaged Open Virtualization Appliance (OVA) files with the
following components:
• The application software and operating system
• Preinstalled VMware tools
• Preset configuration details for:
- RAM and CPU reservations and storage requirements
- Network Interface Card (NIC)
Patches and updates
A minimum patch level is required for each supported application. For more information, see the
compatibility matrix tool at http://support.avaya.com/CompatibilityMatrix/Index.aspx.
Performance and capacities
The OVA file is built with configuration values that optimize performance and follow recommended
best practices. You must change the preconfigured settings in the OVA.
For more information about supported resource requirements, see Messaging virtual machine
resource requirements on page 23.
Security
You can use Out Of Band Management (OOBM) feature for secure management and administration
of Avaya products. OOBM physically and logically separates each network connection to a
customer’s private IT management network from the other.
You can use System Management Interface to configure the system and restrict management
traffic to the administered out-of-band interface.
You can configure OOBM through vCenter:
• while you are deploying the OVA, using System Management Interface
• after the OVA deployment, using System Management Interface > Server Configuration >
Network Configuration
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 11
Comments on this document? infodev@avaya.comAvaya Aura® Virtualized Environment overview
Best Practices for VMware performance and features
For more information about Avaya Aura® Virtualized Environment, see Avaya Aura® Virtualized
Environment Solution Description.
Important:
Do not use VMware Snapshots because Snapshot operations can adversely affect Messaging
service.
Topology
The following diagram shows the high-level topology for deploying Messaging in Virtualized
Environment.
The VMware virtualization platform, VMware vSphere, supports the virtual machines. Each Avaya
Aura® application, including Messaging, is installed as a separate virtual machine. You can install
Messaging in one or more virtual machines depending on capacity requirement. The VMware
vCenter Server management system manages the applications as virtual machines and provides
management and implementation features in addition to the standard System Manager features.
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 12
Comments on this document? infodev@avaya.comComponents
Components
Avaya components
The following table lists components that interwork with Avaya Aura® Messaging. For more
information about interoperability and supported product versions, see the following documents:
• Compatibility matrix for Avaya Aura® Messaging Release 7.2.
Note:
You might need to log in to your Avaya account to see the Compatibility matrix.
• Avaya Aura® Messaging Overview and Specification on the Avaya Support website.
Component Platform Description
®
Avaya Aura components
Avaya Aura® Communication Virtualized Environment The IP telephony foundation on which
Manager Avaya delivers intelligent communications
to large and small enterprises.
Avaya Aura® Session Virtualized Environment A SIP routing and integration tool that
Manager integrates SIP entities across the
enterprise network. You can view and
manage each location, branch, and
application in totality, not as separate units
within the enterprise.
Avaya Aura® System Virtualized Environment A product that takes a solution-level
Manager approach to network administration.
System Manager centralizes provisioning,
maintenance, and troubleshooting to
simplify and reduce management
complexity and solution servicing. System
Manager provides a common management
framework that reduces the complexity of
operations for distributed multisite
networks with multiple control points
inherent in SIP.
Other Avaya components
Avaya Voice Message Form Microsoft Exchange Server A component that provides a toolbar for
Microsoft Office Outlook and Exchange
Server. The tool supports playback of voice
messages on your telephone through the
computer.
Table continues…
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 13
Comments on this document? infodev@avaya.comAvaya Aura® Virtualized Environment overview
Component Platform Description
Avaya WebLM Virtualized Environment A web-based license manager that
manages licenses of one or more Avaya
software products.
Message Networking Avaya server with Linux® A component that supports interoperability
Operating System with legacy voice mail products.
one-X Speech Windows Server 2003 for A component that supports speech-based
one-X Speech Release 5.2 commands and text-to-speech functions for
voice mail, email, calendar, and telephony
Windows Server 2012 for
functions.
one-X Speech Release 6.3
Avaya service components
Avaya Diagnostic Server with — A component that remotely manages
Secure Access Link Messaging and sends alarms to Avaya
Services.
VMware components
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 vSphere Client is an application that installs and manages virtual machines.
vSphere Client connects to a vCenter Server or directly to an ESXi host if a
vCenter Server is not used. The application is installed on a personal
computer or accessible through a web interface. The installable vSphere
Client is not available in vSphere 6.5 and later releases.
vSphere Web Client Using a web browser, vSphere Web Client connects to a vCenter Server or
directly to an ESXi host if a vCenter Server is not used.
vSphere Client (HTML5) vSphere Client (HTML5) is available as of vSphere release 6.5. Using a web
browser, it connects to a vCenter Server or directly to an ESXi host if a
vCenter Server is not used.
As of vSphere release 7.0, vSphere Client (HTML5) is the only supported
vSphere client administration tool.
vCenter Server vCenter Server provides centralized control and visibility at every level of the
virtual infrastructure. vCenter Server provides VMware features such as High
Availability and vMotion.
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 14
Comments on this document? infodev@avaya.comComponents
Third-party components
Component Description
AudioCodes SIP gateway Messaging uses SIP for integration with mixed telephony server
environments. With the AudioCodes Mediant 1000 and 1000B gateways,
Messaging connects to third-party telephony servers that Session
Manager does not support.
Nuance Loquendo Text-to- This component supports conversion of text-to-speech.
Speech
EVM Plus giSTT This component is a unified messaging application that provides speech-
to-text functions for voice mail. Using this application, you can read,
listen, and control your voice mail.
Storage Area Network SAN is a high-speed network of storage devices that also connects those
storage devices with servers.
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 15
Comments on this document? infodev@avaya.comChapter 3: Deployment process
The following image shows the high-level tasks for deploying Messaging in a Virtualized
Environment configuration.
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 16
Comments on this document? infodev@avaya.comChapter 4: Planning and preconfiguration
Planning checklist
No. Task References Notes
1 Download the required See Documentation on page 76. —
documentation.
2 Identify the hypervisor and See Server hardware and —
verify that the capacity resources on page 23.
meets the OVA
requirements.
3 Plan the staging and See Messaging virtual machine —
verification activities and resource requirements on
assign the resources. page 23.
4 Download Messaging OVA. See Downloading software from —
PLDS on page 21.
Software requirements
The following table lists the required software and the supported versions for Messaging in the
Virtualized Environment:
Table 1: VMware software requirement
Equipment Software versions
VMware vSphere ESXi 6.0, 6.5, 6.7, and 7.0
Note:
You cannot deploy Avaya Aura® Messaging 7.2.0 using ESXi Embedded
Host Client.
VMware vCenter 6.0, 6.5, 6.7, and 7.0
Server
Note:
VMware requires the version of vCenter be the same or greater than the
version running on the hosts that it manages.
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 17
Comments on this document? infodev@avaya.comPlanning and preconfiguration
Table 2: Messaging software requirement
Software Software versions
Messaging 7.2.0
Table 3: Operating system requirement for Messaging application and storage servers
Software Software versions
Operating system Red Hat Enterprise Linux® version 7.6 or later with 64–bit operating system.
Table 4: Service pack requirement
Software Software versions
Kernel See Avaya Aura® Messaging Release Notes.
Security See Avaya Aura® Messaging Release Notes.
Communication Manager See Avaya Aura® Messaging Release Notes.
Messaging See Avaya Aura® Messaging Release Notes.
Table 5: Web browser
Software Supported versions
Messaging System Management • Microsoft Internet Explorer 11
Interface
• Mozilla Firefox 45 or later
Messaging User Preferences • Microsoft Internet Explorer 8, 9, 10, and 11
• Mozilla Firefox 30 or later
• Microsoft Edge
• Apple Safari 6 or later
• Google Chrome 35 or later
Messaging Web Access • Microsoft Internet Explorer 10 or later
• Microsoft Edge
• Mozilla Firefox 30 or later
• Apple Safari 7 or later
• Google Chrome 35 or later
HTML5 audio recording and playback support
All modern browsers support HTML5 recording and playback capabilities. Starting from release
7.1.0 Service Pack 3, Messaging Web Access and Messaging User Preferences use the HTML5
audio player and audio recorder by default in the following browsers:
• Microsoft Edge 76 or later
• Mozilla Firefox 30 or later
• Apple Safari 12.1 or later
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 18
Comments on this document? infodev@avaya.comPlanning checklist
• Google Chrome 35 or later
Other browsers, such as Internet Explorer or Apple Safari 12 or below, do not support HTML5
recording and playback capabilities. These browsers will continue using the Flash audio player
and audio recorder.
WebLM
Avaya provides a web-based license manager (WebLM) to manage licenses of one or more Avaya
software products.
To track and manage licenses in an organization, WebLM requires a license file from the Avaya
Product Licensing and Delivery System (PLDS) website at https://plds.avaya.com.
The license file is in XML format and contains information about the product such as the licensed
capacities of each feature that you purchase. You activate the license file in PLDS and install the
license file on the WebLM server.
You must run WebLM as a separate VMware virtual machine or use the WebLM running on
System Manager. For more information about WebLM administration, see Administering Avaya
Aura® System Manager.
Key customer configuration information
The following table lists the customer configuration information that you must enter during the
deployment and configuration processes:
Required data Value for the system
VM Name
Number of subscriber mailboxes
Messaging IPv4 IP address
Messaging IPv4 subnet mask
Messaging IPv4 Default Gateway address
Out of Bound Management IPv4 address
(optional)
Out of Bound Management IPv4 Netmask
(optional)
Messaging Hostname
NTP Server or servers
(optional)
DNS Servers
Table continues…
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 19
Comments on this document? infodev@avaya.comPlanning and preconfiguration
Required data Value for the system
Search Domain List
(optional)
WebLM Server IPv4 Address
Messaging Privileged Administrator User Login
Messaging Privileged Administrator User Password
Messaging IPv6 IP address
(optional)
Messaging IPv6 subnet mask
(optional)
Messaging IPv6 Default Gateway address
(optional)
Configuration tools and utilities
You must have the following tools and utilities for deploying and configuring Messaging open
virtual application (OVA):
• A remote computer running the VMware vSphere Client and vSphere web client
• A browser for accessing the Messaging System Management Interface pages
• An sftp client for Windows, for example, WinSCP
• An ssh client, for example, PuTTy
• WinZip
SAL Gateway
You require a Secure Access Link (SAL) Gateway for remote access and alarming.
Through SAL, support personnel or tools can gain remote access to managed devices to
troubleshoot and debug problems.
A SAL Gateway:
1. Receives alarms from Avaya products in the customer network.
2. Reformats the alarms.
3. Forwards the alarms to the Avaya support center or a customer-managed Network
Management System.
For more information about SAL Gateway and its deployment, see the Secure Access Link
documentation on the Avaya Support website at http://support.avaya.com.
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 20
Comments on this document? infodev@avaya.comDownloading the Messaging OVA
Downloading the Messaging OVA
Registering for PLDS
Procedure
1. Go to the Avaya Product Licensing and Delivery System (PLDS) website at https://
plds.avaya.com.
The PLDS website redirects you to the Avaya single sign-on (SSO) webpage.
2. Log in to SSO with your SSO ID and password.
3. On the PLDS registration page, register as:
• An Avaya Partner: Enter the Partner Link ID. To know your Partner Link ID, send an
email to prmadmin@avaya.com.
• A customer: Enter one of the following:
- Company Sold-To
- Ship-To number
- License authorization code (LAC)
4. Click Submit.
Avaya sends the PLDS access confirmation within one business day.
Downloading software from PLDS
Procedure
1. In your web browser, type http://plds.avaya.com to go to the Avaya PLDS website.
2. On the PLDS website, enter your Login ID and password.
3. On the Home page, select Assets.
4. Select View Downloads.
5. Click the search icon ( ) for Company Name.
6. In the Search Companies dialog box, do the following:
a. In the %Name field, type Avaya or the Partner company name.
b. Click Search Companies.
c. Locate the correct entry and click the Select link.
7. Search for the available downloads by using one of the following:
• In Download Pub ID, type the download pub ID.
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 21
Comments on this document? infodev@avaya.comPlanning and preconfiguration
• In the Application field, click the application name.
8. Click Search Downloads.
9. Scroll down to the entry for the download file, and click the Download link.
10. Select a location where you want to save the file, and click Save.
11. (Optional) If you receive an error message, click the message, install Active X, and
continue with the download.
12. (Optional) When the system displays the security warning, click Install.
When the installation is complete, PLDS displays the downloads again with a check mark
next to the downloads that have completed successfully.
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 22
Comments on this document? infodev@avaya.comChapter 5: Initial setup and connectivity
Deployment guidelines
• Deploy maximum number of virtualized environment on the same host.
• Deploy the virtualized environment on the same cluster if the cluster goes beyond the host
boundary.
• Segment redundant elements on a different cluster, or ensure that the redundant elements
are not on the same host.
• Plan for rainy day scenarios or conditions. Do not configure resources only for traffic or
performance on an average day.
• Do not oversubscribe resources. Oversubscribing affects performance.
• Monitor the server, host, and virtualized environment performance.
Hardware requirements
Supported hardware for VMware
VMware offers compatibility guides that list servers, system, I/O, storage, and backup compatibility
with VMware infrastructure. For more information about VMware-certified compatibility guides and
product interoperability matrices, see http://www.vmware.com/resources/guides.html.
Messaging virtual machine resource requirements
The Messaging OVA is built with configuration values that optimize performance and follow
recommended best practices. After installing the OVA, adjust resource settings as needed to meet
the guidelines set forth in the following table.
The following set of resources must be available on the ESXi host for deploying the Messaging
virtual machines:
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 23
Comments on this document? infodev@avaya.comInitial setup and connectivity
Resource requirements Combined application Two application virtual Three application virtual
and storage virtual machines and one machines and one
machine storage virtual machine storage virtual machine
Heavy traffic1 Medium traffic2 Heavy traffic3
Mailboxes 6000 10000 20000
Ports 100 150 300
Virtual Machines 1 3 4
Virtual CPUs 4 4 4
Minimum CPU speed 2 GHz 2 GHz 2 GHz
based on Xeon E5620 or
equivalent processor
Virtual CPU reservations 8 GHz 8 GHz 8 GHz
Virtual memory 8 GB Application: 8 GB Application: 8 GB
Storage: 8 GB Storage: 8 GB
Virtual memory 8GB Application: 8 GB Application: 8 GB
reservations
Storage: 8 GB Storage: 8 GB
Resource requirements Combined application Two application virtual Three application virtual
and storage virtual machines and one machines and one
machine storage virtual machine storage virtual machine
Heavy traffic4 Medium traffic5 Heavy traffic6
Virtual storage 174 GB (Thick 174 GB (Thick 174 GB (Thick
Provisioned) Provisioned) Provisioned)
Average I/OPS 208 Application: 35 Application: 106
Storage: 204 Storage: 382
Shared Network Interface One @ 1000 Mbps One @ 1000 Mbps One @ 1000 Mbps
Cards
Average network usage 25 Mbps 25 Mbps per virtual 25 Mbps per virtual
machine machine
1 Messaging is expecting to serve two calls per second. On average, each user receives nine voice messages every 24
hours.
2 Messaging is expecting to serve a new call every 1 to 6 seconds. On average, each user receives three to six voice
messages every 24 hours.
3 Messaging is expecting to serve two calls per second. On average, each user receives nine voice messages every 24
hours.
4 Messaging is expecting to serve two calls per second. On average, each user receives nine voice messages every 24
hours.
5 Messaging is expecting to serve a new call every 1 to 6 seconds. On average, each user receives three to six voice
messages every 24 hours.
6 Messaging is expecting to serve two calls per second. On average, each user receives nine voice messages every 24
hours.
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 24
Comments on this document? infodev@avaya.comHardware requirements
For Messaging to run at full capacity, ensure that the recommended resource requirements are
met.
• Values recommended in the table are for each virtual machine.
• The default value for the Messaging OVA is 4 vCPU and 8 GB memory without any
reservation. To meet the acceptable performance level, change the default values and use
the recommended CPU and memory reservations as shown in the table Messaging virtual
machine resource requirements on page 23. You can check the CPU reservations by viewing
the Summary tab of the virtual machine.
• Messaging might not perform adequately if the cumulative CPU or memory resources of the
virtual machines co-located on the same physical ESXi host as the Messaging virtual
machine exceeds 70% of the physical hardware of server. The customer assumes all risk if
this threshold is exceeded.
• The recommended resource requirements are based on the following hardware
configurations:
- iSCSI SAN storage: One Dell Equallogic PS6100XV array of 24 terabytes.
- ESXi 5.1 hosts: Six Dell R720 servers. Each server with two quad-core Xeon 2620 CPU
and 2 GHz, HyperThreaded. Each host server with 32 logical vCPUand each vCPU core
provides 2 GHz.
- vCenter server and Dell SAN Headquarter: One Dell R320 server running Windows
2008R2, with a single quad-core Xeon CPU and 500 GB RAID-1 hard disk drive array.
- LAN: A stacked pair of Avaya ERS4850GTS, dedicated and configured for each Dell
Equallogic SAN requirements. Each ESXi host server has four connections to the SAN
switch to take advantage of the Dell Equallogic Multi-I/O for max storage I/O performance.
A fifth SAN connection is dedicated for vMotion traffic.
Note:
If the virtual CPUs on the host where the Messaging is located are more than physical CPUs,
the CPU oversubscription occurs. The CPU oversubscription affects the performance of
Messaging. CPU oversubscription can create a dead air issue with cannot create recognizer
errors. While calculating the quantity of physical CPUs on the host, do not consider the
Hyperthreading feature.
Note:
• Avaya does not provide support for performance issues due to variance in the
recommended settings.
• If a problem occurs with the virtual machine, Avaya Global Support Services (GSS) might
not be able to assist in resolving the problem. Reset the values to the required values
before starting to investigate the problem.
November 2021 Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment 25
Comments on this document? infodev@avaya.comYou can also read
