Deploying Avaya Aura Messaging using Solution Deployment Manager

Transcription

1 Deploying Avaya Aura Messaging using Solution Deployment Manager Release Issue 2 August 2018

2 , Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Documentation means information published in varying mediums which may include product information, operating instructions and performance specifications that are generally made available to users of products. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of Documentation unless such modifications, additions, or deletions were performed by or on the express behalf of Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked websites referenced within this site or Documentation provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on Avaya hardware and software. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product while under warranty is available to Avaya customers and other parties through the Avaya Support website: getgenericdetails?detailid=c under the link Warranty & Product Lifecycle or such successor site as designated by Avaya. Please note that if You acquired the product(s) from an authorized Avaya Channel Partner outside of the United States and Canada, the warranty is provided to You by said Avaya Channel Partner and not by Avaya. Hosted Service means an Avaya hosted service subscription that You acquire from either Avaya or an authorized Avaya Channel Partner (as applicable) and which is described further in Hosted SAS or other service description documentation regarding the applicable hosted service. If You purchase a Hosted Service subscription, the foregoing limited warranty may not apply but You may be entitled to support services in connection with the Hosted Service as described further in your service description documents for the applicable Hosted Service. Contact Avaya or Avaya Channel Partner (as applicable) for more information. Hosted Service THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA WEBSITE, UNDER THE LINK Avaya Terms of Use for Hosted Services OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE APPLICABLE TO ANYONE WHO ACCESSES OR USES THE HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER ), AGREE TO THE TERMS OF USE. IF YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU MUST NOT ACCESS OR USE THE HOSTED SERVICE OR AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED SERVICE. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, UNDER THE LINK AVAYA SOFTWARE LICENSE TERMS (Avaya Products) OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER ), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ( AVAYA ). Avaya grants You a license within the scope of the license types described below, with the exception of Heritage Nortel Software, for which the scope of the license is detailed below. Where the order documentation does not expressly identify a license type, the applicable license will be a Designated System License. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the documentation or other materials available to You. Software means computer programs in object code, provided by Avaya or an Avaya Channel Partner, whether as stand-alone products, pre-installed on hardware products, and any upgrades, updates, patches, bug fixes, or modified versions thereto. Designated Processor means a single stand-alone computing device. Server means a Designated Processor that hosts a software application to be accessed by multiple users. Instance means a single copy of the Software executing at a particular time: (i) on one physical machine; or (ii) on one deployed software virtual machine ( VM ) or similar deployment. Licence types Designated System(s) License (DS). End User may install and use each copy or an Instance of the Software only on a number of Designated Processors up to the number indicated in the order. Avaya may require the Designated Processor(s) to be identified in the order by type, serial number, feature key, Instance, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A Unit means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Units may be linked to a specific, identified Server or an Instance of the Software. Named User License (NU). You may: (i) install and use each copy or Instance of the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use each copy or Instance of the Software on a Server so long as only authorized Named Users access and use the Software. Named User, means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya s sole discretion, a Named User may be, without limitation, designated by name,

3 corporate function (e.g., webmaster or helpdesk), an or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Shrinkwrap License (SR). You may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as shrinkwrap or clickthrough license accompanying or applicable to the Software ( Shrinkwrap License ). Heritage Nortel Software Heritage Nortel Software means the software that was acquired by Avaya as part of its purchase of the Nortel Enterprise Solutions Business in December The Heritage Nortel Software is the software contained within the list of Heritage Nortel Products located at under the link Heritage Nortel Products or such successor site as designated by Avaya. For Heritage Nortel Software, Avaya grants Customer a license to use Heritage Nortel Software provided hereunder solely to the extent of the authorized activation or authorized usage level, solely for the purpose specified in the Documentation, and solely as embedded in, for execution on, or for communication with Avaya equipment. Charges for Heritage Nortel Software may be based on extent of activation or use authorized as specified in an order or invoice. Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, Hosted Service, or hardware provided by Avaya. All content on this site, the documentation, Hosted Service, and the product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Virtualization The following applies if the product is deployed on a virtual machine. Each product has its own ordering code and license types. Note that each Instance of a product must be separately licensed and ordered. For example, if the end user customer or Avaya Channel Partner would like to install two Instances of the same type of products, then two products of that type must be ordered. Third Party Components Third Party Components mean certain software programs or portions thereof included in the Software or Hosted Service may contain software (including open source software) distributed under third party agreements ( Third Party Components ), which contain terms regarding the rights to use certain portions of the Software ( Third Party Terms ). As required, information regarding distributed Linux OS source code (for those products that have distributed Linux OS source code) and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply is available in the products, Documentation or on Avaya s website at: support.avaya.com/copyright or such successor site as designated by Avaya. The open source software license terms provided as Third Party Terms are consistent with the license rights granted in these Software License Terms, and may contain additional rights benefiting You, such as modification and distribution of the open source software. The Third Party Terms shall take precedence over these Software License Terms, solely with respect to the applicable Third Party Components to the extent that these Software License Terms impose greater restrictions on You than the applicable Third Party Terms. The following applies only if the H.264 (AVC) codec is distributed with the product. THIS PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD ( AVC VIDEO ) AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE Service Provider THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER S HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY FROM THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL PARTNER S HOSTING OF AVAYA PRODUCTS MUST BE AUTHORIZED IN WRITING BY AVAYA AND IF THOSE HOSTED PRODUCTS USE OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING BUT NOT LIMITED TO MICROSOFT SOFTWARE OR CODECS, THE AVAYA CHANNEL PARTNER IS REQUIRED TO INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE AGREEMENTS, AT THE AVAYA CHANNEL PARTNER S EXPENSE, DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER. WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED THE G.729 CODEC, H.264 CODEC, OR H.265 CODEC, THE AVAYA CHANNEL PARTNER ACKNOWLEDGES AND AGREES THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY AND ALL RELATED FEES AND/OR ROYALTIES. THE G.729 CODEC IS LICENSED BY SIPRO LAB TELECOM INC. SEE THE H.264 (AVC) CODEC IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD ( AVC VIDEO ) AND/OR (II) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE Compliance with Laws You acknowledge and agree that it is Your responsibility for complying with any applicable laws and regulations, including, but not limited to laws and regulations related to call recording, data privacy, intellectual property, trade secret, fraud, and music performance rights, in the country or territory where the Avaya product is used. Preventing Toll Fraud Toll Fraud is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of Toll Fraud associated with your system and that, if Toll Fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya Toll Fraud intervention If You suspect that You are being victimized by Toll Fraud and You need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at for the United States and Canada. For additional support telephone numbers, see the Avaya Support website: or such successor site as designated by Avaya. Security Vulnerabilities Information about Avaya s security support policies can be found in the Security Policies and Support section of support.avaya.com/security. Suspected Avaya product security vulnerabilities are handled per the Avaya Product Security Support Flow ( support.avaya.com/css/p8/documents/ ). Downloading Documentation For the most current versions of Documentation, see the Avaya Support website: or such successor site as designated by Avaya.

4 Contact Avaya Support See the Avaya Support website: 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: (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.

5 Contents Chapter 1: Introduction... 8 Purpose of this guide... 8 Change history... 8 Prerequisites... 8 Chapter 2: Architecture overview Avaya Aura Virtualized Appliance overview Appliance Virtualization Platform overview Solution Deployment Manager overview Solution Deployment Manager options Solution Deployment Manager client Solution Deployment Manager client capabilities Components Avaya components VMware components Third-party components Chapter 3: Deployment process Chapter 4: Planning and preconfiguration Planning checklist Key customer configuration information Supported servers Configuration tools and utilities Software requirements Downloading the Messaging OVA Registering for PLDS Downloading software from PLDS Chapter 5: Initial setup and connectivity Overview Prerequisites for installing the Solution Deployment Manager client Verifying the Windows version Verifying the hard disk space Verifying the compatibility between the application and the port Configuring ports Configuring Windows firewall Verifying system variables Installing the Solution Deployment Manager client on your computer Checklist for deploying Messaging on server provided by Avaya using Solution Deployment Manager client Deploying Messaging OVA using Solution Deployment Manager client VM Deployment field descriptions August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 5

6 Contents Checklist for deploying Messaging on Avaya-provided server using Solution Deployment Manager Deploying Messaging OVA using System Manager Solution Deployment Manager VM Deployment field descriptions Deploying Messaging on Appliance Virtualization Platform using Vsphere client Updating Services Port Static Routing on Avaya Aura Messaging Update Static Routing field descriptions Managing the virtual machine Editing a virtual machine Starting a virtual machine from Solution Deployment Manager Stopping a virtual machine from Solution Deployment Manager Restarting a virtual machine from Solution Deployment Manager Deleting a virtual machine Monitoring a host and virtual machine Monitoring a host Monitoring a virtual machine Chapter 6: Configuration Configuration checklist Changing the network parameters of an ESXi host Change Network Parameters field description Changing the password for an ESXi host Change Password field descriptions IPv Enabling IPv Disabling IPv Configuring the network settings Network Configuration field descriptions Setting the time zone Setting up the network time protocol Service pack installation Messaging service packs Downloading service packs Installing a service pack Removing a service pack Configuring languages Languages field descriptions Configuring MWI MWI administration Enabling SIP telephony integration Telephony Integration field descriptions Creating a SIP entity of a storage server on System Manager Chapter 7: Initial administration Initial administration checklist August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 6

7 Contents Account management License management Data backup and restore Backing up the system Backing up Messaging data Backup Now field descriptions Restoring data Stopping Messaging Starting Messaging Shutting down the server Shutting down Appliance Virtualization Platform host from CLI Resetting the Appliance Virtualization Platform host from CLI Chapter 8: Resources Documentation Administration Security User functions Hardware Training Viewing Avaya Mentor videos Support Using the Avaya InSite Knowledge Base Appendix A: Migration Overview Migration roadmap and limitations System Platform and template values worksheet IP address mapping Migrating Messaging to Virtualized Appliance Backing up data from the old system Restoring Messaging data on the new system Rolling back to System Platform August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 7

8 Chapter 1: Introduction Purpose of this guide This document provides procedures for deploying the Avaya Aura Messaging virtual application in the Appliance Virtualization Platform. 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 7.1.0, Issue 2 August 2018 Indicated that Avaya Aura Messaging supports Red Hat Enterprise Linux 7.2. Indicated that the following servers are not supported: - Dell PowerEdge R610 - HP ProLiant DL360 G7 Minor rephrasing throughout the document. Prerequisites Before deploying Avaya Aura Messaging, ensure that you have the following knowledge, skills, and tools: Knowledge Skills Avaya Telephony platforms such as Communication Manager Linux Operating System Executing commands from the CLI. August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 8

9 Prerequisites VMware and Virtualized Environment Tools Avaya supported servers Solution Deployment Manager client when System Manager is unavailable SFTP client SSH client August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 9

10 Chapter 2: Architecture overview Avaya Aura Virtualized Appliance overview From Release 7.0.0, Avaya supports a new virtualization offer based on VMware called Avaya Aura Virtualized Appliance. In the Avaya Aura Virtualized Appliance offer, Avaya provides server hardware, Appliance Virtualization Platform that is based on the customized OEM version of VMware ESXi 5.5, and the license for the software product. Deployment on Appliance Virtualization Platform is performed from System Manager Solution Deployment Manager or the Solution Deployment Manager standalone Windows client. Appliance Virtualization Platform overview From Release 7.0.0, Avaya offers a new VMware offer called the appliance offer that uses the VMware -based Appliance Virtualization Platform to provide virtualization for Avaya Aura applications. The Avaya appliance offer includes: Common Servers: Dell PowerEdge R620, HP ProLiant DL360p G8, HP ProLiant DL360 G9, and Dell PowerEdge R630. Appliance Virtualization Platform is the customized OEM version of VMware ESXi 5.5 and is installed on top of the hardware provided by Avaya to deliver the virtualization technology. You can configure and manage Appliance Virtualization Platform by using Solution Deployment Manager that is part of System Manager, or by installing the Solution Deployment Manager client. Note: Any combination of supported applications can be installed on Appliance Virtualization Platformon common server, but the resources of the common server are enough to deploy only one Avaya Aura Messaging application. August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 10

11 Solution Deployment Manager overview Solution Deployment Manager overview Solution Deployment Manager is a centralized management tool in System Manager and is used for both Appliance offer and Virtualized Environment (VE). It replaces System Platform and supports deployments, upgrades, migrations, and updates to Avaya Aura Messaging on VMware (Appliance Virtualization Platform and ESXi). In System Manager, Solution Deployment Manager runs on: An Avaya-provided appliance: Contains a server, Appliance Virtualization Platform, and Avaya Aura Messaging OVA. Appliance Virtualization Platform includes a VMware ESXi 5.5 hypervisor. A customer-provided Virtualized Environment solution: Avaya Aura Messaging is deployed on a customer-provided, certified VMware hardware. August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 11

12 Architecture overview Solution Deployment Manager options Avaya provides the following Solution Deployment Manager options: Solution Deployment Manager: A centralized capability of System Manager to deploy, upgrade, and migrate Avaya Aura Messaging. However, in Release 7.0.0, Solution Deployment Manager does not support migration of Virtualized Environment-based 6.x applications to in the customer s Virtualized Environment. Use vsphere client to migrate to a customer s Virtualized Environment. Solution Deployment Manager client: A lightweight tool that can reside on the computer of a technician. The technician can gain access to the client by using the web browser. These options provide the following capabilities: Capabilities Centralized Solution Deployment Manager Solution Deployment Manager client Description Manage virtual machine lifecycle. - Deploy Avaya Aura Messaging. - Deploy hypervisor patches only for Appliance Virtualization Platform. - Upgrade Avaya Aura Messaging. - Release supports upgrades from Linuxbased or System Platform based Avaya Aura Messaging to Virtualized Environment or Appliance Virtualization Platform based Avaya Aura Messaging. Release does not support Virtualized Environment to Virtualized Environment upgrades. Discover Avaya Aura Messaging. To manage and upgrade software from System Manager, the system makes use of discovery profile for discovering applications in the network. For more information, see Table continues August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 12

13 Solution Deployment Manager client Capabilities Analyze Avaya Aura Messaging. Create and use the software library. Centralized Solution Deployment Manager Solution Deployment Manager client Description Administering Avaya Aura System Manager. - During upgrade, Analyze is an important function to get and recommend the latest and entitled (major release/ update) versions for Avaya Aura Messaging. For more information, see Avaya Aura System Manager Solution Deployment Manager Job Aid. - - Solution Deployment Manager client When System Manager is inaccessible, you can use the Solution Deployment Manager client. You can use the Solution Deployment Manager client to install the OVAs on a server provided by Avaya or customer-provided Virtualized Environment. The user interface of the Solution Deployment Manager client looks similar to the centralized Solution Deployment Manager. Solution Deployment Manager client capabilities The Solution Deployment Manager client provides the following capabilities and functionality: Runs on the technician computer on the following operating systems: - Windows 7, 64-bit Professional or Enterprise - Windows 8, 64 bit Professional or Enterprise - Windows 8.1, 64-bit Professional or Enterprise - Windows 10, 64 bit Professional or Enterprise Supports Microsoft Internet Explorer Release 9.x, 10.x, and 11.x Provides a user interface with a similar look and feel as the central Solution Deployment Manager in System Manager Release Supports deploying System Manager and Avaya Aura Messaging OVA in a Virtualized Environment or on the Avaya appliances. Supports upgrading and installing of Avaya Aura Messaging. August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 13

14 Architecture overview Supports the Flexible footprint feature. The size of the virtual resources depends on the capacity requirements of Avaya Aura Messaging. Defines the physical location, Appliance Virtualization Platform or ESXi host, and discovers virtual machines that are required for application deployments. Manages the lifecycle of the OVA applications that are deployed on the ESXi host. Deploys the Avaya Aura Applications OVAs, for example, Avaya Aura Messaging that can be deployed from the central Solution Deployment Manager for Appliance Virtualization Platform and customer Virtualized Environment. You can deploy one application at a time. Configures the application and networking parameters required for application deployments. Supports the local computer or an HTTP URL to select the application OVA file for deployment. You do not need access to PLDS. Supports changing the hypervisor IP address on Appliance Virtualization Platform. Supports installing software patches, service packs, and feature packs only for System Manager. Components Avaya components Component Version Platform Description Avaya Aura components Avaya Aura Communication Manager Avaya Aura Session Manager Avaya Aura System Manager Avaya Virtualization Platform Avaya Virtualization Platform Avaya Virtualization Platform Avaya Virtualization Platform The IP telephony foundation on which Avaya delivers intelligent communications to large and small enterprises. A part of the Avaya Aura architecture, but Messaging can also be used in other environments. A SIP routing and integration tool that 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. A product that takes a solution-level approach to network administration. Table continues August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 14

15 Components Component Version Platform Description 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. Solution Deployment Manager Avaya Solution Deployment Manager client Other Avaya components Avaya Voice Message Form Avaya WebLM Avaya Virtualization Platform A centralized software management solution in System Manager that provides deployments, upgrades, migrations, and updates to Release Avaya Aura Messaging Microsoft Windows A tool that provides the functionality to install the OVAs on an Avayaprovided server or customerprovided Virtualized Environment Microsoft Exchange Server Avaya Virtualization Platform Message Networking 6.3 Avaya server with Linux Operating System one-x Speech 6.3 Windows Server 2003 for one-x Speech Release 5.2 Avaya service components Windows Server 2012 for one-x Speech Release 6.3 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. A web-based license manager that manages licenses of one or more Avaya software products. A component that supports interoperability with legacy voice mail products. A component that supports speechbased commands and text-tospeech functions for voice mail, , calendar, and telephony functions. Secure Access Link A component that remotely manages Messaging and sends alarms to Avaya Services. For more information about interoperability between these products, see Avaya Aura Messaging Overview and Specification at the Avaya Support website: August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 15

16 Architecture overview VMware components Component Version Description ESXi Host 5.5 The Appliance Virtualization Platform which is the customized OEM version of ESXi 5.5. Third-party components Component AudioCodes SIP gateway Nuance Loquendo Text-to- Speech EVM Plus gistt Storage Area Network Description 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. This component supports conversion of text-to-speech. This component is a unified messaging application that provides speechto-text functions for voice mail. Using this application, you can read, listen, and control your voice mail. SAN is a high-speed network of storage devices that also connects those storage devices with servers. August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 16

17 Chapter 3: Deployment process August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 17

18 Chapter 4: Planning and preconfiguration Planning checklist No Task References Notes 1 Download the required documentation. 2 Identify the customer configuration data. 3 Identify the configuration tools and utilities. See Documentation on page 78. See Customer configuration data on page 18. See Configuration tools and utilities on page Download Messaging. See Downloading software from PLDS on page Key customer configuration information The following table lists the customer configuration information that you must enter during the deployment and configuration processes: Required data 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 Value for the system Table continues August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 18

19 Supported servers Required data (optional) DNS Servers Search Domain List Value for the system (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) Supported servers In the Avaya appliance model, the customer can deploy or upgrade to Avaya Aura Messaging on the following servers provided by Avaya. Dell PowerEdge R620 Dell PowerEdge R630 HP ProLiant DL360p G8 HP ProLiant DL360 G9 Configuration tools and utilities You must have the following tools and utilities for deploying and configuring Messaging open virtual application (OVA): A Solution Deployment Manager client when Solution Deployment Manager through System Manager is unavailable 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 August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 19

20 Planning and preconfiguration Software requirements The following table lists the required software and the supported versions for Messaging in the Appliance Virtualization Platform environment: Table 1: Appliance Virtualization Platform software requirement Equipment Appliance Virtualization Platform Table 2: Messaging software requirement Software Messaging Software versions Software versions Table 3: Operating system requirement for Messaging application and storage servers Software Operating system Software versions Red Hat Enterprise Linux version 7.2 with 64 bit operating system. Table 4: Service pack requirement Software Kernel Security Communication Manager Messaging Software versions See Avaya Aura Messaging Release Notes. See Avaya Aura Messaging Release Notes. See Avaya Aura Messaging Release Notes. See Avaya Aura Messaging Release Notes. Table 5: Web browser Software Supported versions Messaging System Management Interface Microsoft Internet Explorer 11 Mozilla Firefox 45 or later Messaging User Preference 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 9, 10, and 11 Mozilla Firefox 30 or later Microsoft Edge Table continues August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 20

21 Downloading the Messaging OVA Software Supported versions Apple Safari 6 or later Google Chrome 35 or later Downloading the Messaging OVA Registering for PLDS 1. Go to the Avaya Product Licensing and Delivery System (PLDS) website at 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 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 About this task Note: You can download product software from also. 1. In your web browser, type to go to the Avaya PLDS website. 2. Enter your Login ID and password to log on to the PLDS website. 3. On the Home page, select Assets. August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 21

22 Planning and preconfiguration 4. Select View Downloads. 5. Search for the available downloads by using one of the following: An application type and the version number Download name 6. Click the download icon from the appropriate download. 7. When the system displays the confirmation box, select Click to download your file now. 8. If you receive an error message, click the message, install Active X, and continue with the download. 9. 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. August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 22

23 Chapter 5: Initial setup and connectivity Overview After you complete the planning and preconfiguration tasks, you must perform the following highlevel tasks to complete the initial setup and connectivity to deploy Messaging: 1. Complete the prerequisites for installing the Solution Deployment Manager client. 2. Install the Solution Deployment Manager client. 3. Deploy Messaging using the Solution Deployment Manager client or Solution Deployment Manager in System Manager. 4. Manage virtual machines. Prerequisites for installing the Solution Deployment Manager client When the centralized Solution Deployment Manager on System Manager is unavailable, use the Solution Deployment Manager client to deploy Messaging. No. Task References Notes 1 Ensure that Windows 7.0, 8.1, or 10 operating system is installed on the computer. For more information, see Verifying Windows version on page Ensure that at least 5 GB disk space is available at the location where you want to install the client. For more information, see Verifying the hard disk space on page To avoid port conflict, stop any application that is running on your computer. For more information, see Verifying the compatibility between the application and the port on page Ensure that the firewall allows the ports that are required to install the For more information, see Configuring Windows firewall on page Table continues August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 23

24 Initial setup and connectivity No. Task References Notes Solution Deployment Manager client and use the Solution Deployment Manager functionality. 5 Ensure that 443 and 1527 ports are available. 6 Do not set CATALINA_HOME as an environment variable on the computer where you install the Solution Deployment Manager client. For more information, see Configuring ports on page 25. Note: Close the applications that use port 443 and For more information, see Verifying system variables on page Verifying the Windows version About this task Use this procedure to verify that Windows 7.0, 8.1, or 10 is installed on the computer. 1. On the computer, press Windows+R. 2. In the Run dialog box, type winver and click OK. The system displays the About windows window and the version of Windows. Verifying the hard disk space About this task Use this procedure to ensure that at least 5 GB space is available to install the Solution Deployment Manager client. 1. On the computer, click Start > File Explorer. 2. In the File Explorer window, click This PC. The system displays a list of hard disk drives and the corresponding available space. August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 24

25 Verifying the compatibility between the application and the port Verifying the compatibility between the application and the port About this task When you start the Solution Deployment Manager client, the system launches a web application that uses port 443. For the web application to start, ensure that port 443 is not used by any other application on the computer. Use this procedure to stop any application that is using port On the computer, right-click on the taskbar, and click Properties > Customize. 2. In the System window, click Select which icons appear on the taskbar. 3. In the Select which icons appear on the taskbar window, click Turn System Icons On or Off. The system displays any application that is using port Change the status of the application to Off state. Configuring ports About this task Use this procedure to ensure that ports 443 and 1527 are available for use by the Solution Deployment Manager. Close any application that is installed on the computer such as Skype that is using port 443 and On the command prompt, type netstat an. The system displays a list of ports that are in use. 2. Close any application that is using port 443 and Configuring Windows firewall About this task Use this procedure to ensure that the firewall allows the ports required to install the Solution Deployment Manager client and use the Solution Deployment Manager functionality. 1. On the computer, press Windows+R. August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 25

26 Initial setup and connectivity 2. In the Run dialog box, type Control Panel and click OK. 3. On the Control Panel, click System and Security > Windows Firewall. 4. Click Allow an app through Windows Firewall. The system displays a list of applications and ports. Verifying system variables About this task Use this procedure to ensure that you have not set CATALINA_HOME as an environment variable on your computer. 1. On the computer, press Windows+R. 2. In the Run dialog box, type Control Panel and click OK. 3. In the Control Panel, click System and Security > System > Advanced system settings. 4. In the System Properties window, click Environment Variables. The system displays a list of system variables. 5. To disable CATALINA_HOME as an environment variable, select it and delete the variable. Installing the Solution Deployment Manager client on your computer About this task In an Avaya appliance offer, when the centralized Solution Deployment Manager in System Manager is unavailable, use the Solution Deployment Manager client to deploy Messaging. Important: For deployments through service port by using the Solution Deployment Manager client, get the Solution Deployment Manager client software from the Avaya Support site at support.avaya.com. The Solution Deployment Manager client software version available in the media does not support the service port deployment. 1. Download the Avaya Solution Deployment Manager client file from the Avaya PLDS website at On the Avaya PLDS website, you can provide the application name as System Manager, and version as August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 26

27 Installing the Solution Deployment Manager client on your computer 2. Copy the zip file, and extract to a location on your computer by using the WinZip application. 3. Using the Run as administrator option, run the Avaya Solution Deployment Manager client file. The system displays the Avaya Solution Deployment Manager screen. 4. On the Welcome page, click Next. 5. On the License Agreement page, click I accept the terms of the license agreement and click Next. 6. On the Install Location page, do one of the following: To install the Solution Deployment Manager client in the system-defined folder, click Restore Default Folder. To specify a different location for installation, click Choose and browse to an empty folder. 7. Click Next. 8. On the Preinstallation Summary page, review the information, and click Next. 9. On the Summary and Validation page, do the following: a. To start the Solution Deployment Manager client at the start of the system, select the Automatically start SDM service at startup check box. b. Verify the product information and the system requirements. The system performs feasibility checks, such as disk space and memory. If the requirements are not met, the system displays an error message. To continue with the installation, make the disk space, memory, and ports available. 10. Click Install. Important: When you start the Solution Deployment Manager client, the system launches a web application that uses port 443. For the web application to start, ensure that port 443 is not used by any other application installed on the computer. For more information, see Using the Solution Deployment Manager client. 11. To exit the installer, click Done on the Install Complete page. The installer creates a shortcut on the desktop. August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 27

28 Initial setup and connectivity Checklist for deploying Messaging on server provided by Avaya using Solution Deployment Manager client # Task Reference Notes 1 From the Avaya Support website at download the following: Avaya Solution Deployment Manager client Messaging OVA 2 Install Appliance Virtualization Platform on the server. 3 Install the Avaya Solution Deployment Manager client. - Download the Avaya Solution Deployment Manager client only when System Manager is unavailable. For more information, see Deploying Avaya Aura applications from System Manager. For more information, see Installing the Solution Deployment Manager client on your computer on page Add a location. For more information, see Deploying Avaya Aura applications from System Manager. 5 Add an Appliance Virtualization Platform host. 6 Create the virtual machine, deploy Utility Services, and complete the required configuration. 7 Close the Solution Deployment Manager client. 8 Set the parameters on the computer on which the Solution Deployment Manager client is installed. 9 Start the Solution Deployment Manager client with the new IP address. For more information, see Deploying Avaya Aura applications from System Manager. For more information, see Deploying Avaya Aura applications from System Manager. - - Key customer configuration information on page For the latest Solution Deployment Manager client, see Avaya Aura Messaging Release Notes Table continues August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 28

29 Checklist for deploying Messaging on server provided by Avaya using Solution Deployment Manager client # Task Reference Notes 10 Deploy Messaging. For more information, see Deploying Messaging using Solution Deployment Manager client on page Verify that Messaging is functional. For more information, see Administering Avaya Aura Messaging. - Go to the Messaging SMI, click Messaging > Server Information > System Status. Deploying Messaging OVA using Solution Deployment Manager client About this task Use the procedure to create a virtual machine on the ESXi host and deploy Messaging OVA on the server provided by Avaya. To deploy Messaging, use the Solution Deployment Manager client if System Manager is unavailable. Before you begin Ensure that you complete the deployment checklist: Add a location Add Appliance Virtualization Platform to a location Download Messaging OVA 1. On the desktop, click the SDM icon and then click VM Management. 2. In the VM Management Tree, in the left pane, select a host. 3. On the Virtual Machines tab, in the VMs for Selected Host <Host name> section, click New. The system displays the VM Deployment section. 4. In the Select Location and Host section, the system displays the: a. Location b. Host FQDN 5. In VM Name, type the name of the virtual machine. August 2018 Deploying Avaya Aura Messaging using Solution Deployment Manager 29