Deploying Secure Access Link Gateway using Avaya Aura System Manager in the VMware Virtualized Environment

Transcription

1 Deploying Secure Access Link Gateway using Avaya Aura System Manager in the VMware Virtualized Environment Release 2.5 Issue 2 November 2016

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. Licenses THE SOFTWARE LICENSE TERMS OR SUPPORT TOOLS LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, SUPPORT.AVAYA.COM/LICENSEINFO 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 and Support Tools, 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. License 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. Database License (DL). End User may install and use each copy or an Instance of the Software on one Server or on multiple Servers provided that each of the Servers on which the Software is installed communicates with no more than one Instance of the same database. CPU License (CP). End User may install and use each copy or Instance of the Software on a number of Servers up to the number indicated in the order provided that the performance capacity of the Server(s) does not exceed the performance capacity specified for the Software. End User may not re-install or operate the Software on Server(s) with a larger performance capacity without Avaya s prior consent and payment of an upgrade fee. 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, 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 ). Support tools AVAYA SUPPORT TOOLS MEAN THOSE SUPPORT TOOLS PROVIDED TO PARTNERS OR CUSTOMERS IN CONNECTION WITH MAINTENANCE SUPPORT OF AVAYA EQUYIPMENT (E.G., SAL, SLA MON, AVAYA DIAGNOISTIC SERVER, ETC.) AVAYA SUPPORT TOOLS ARE INTENDED TO BE USED FOR LAWFUL DIAGNOSTIC AND NETWORK INTEGRITY PURPOSES ONLY. The customer is responsible for understanding and complying with applicable legal requirements with regard to its network. The Tools may contain diagnostic capabilities that allow Avaya, authorized Avaya partners, and authorized customer administrators to capture

3 packets, run diagnostics, capture key strokes and information from endpoints including contact lists, and remotely control and monitor end-user devices. The customer is responsible for enabling these diagnostic capabilities, for ensuring users are aware of activities or potential activities and for compliance with any legal requirements with respect to use of the Tools and diagnostic capabilities on its network, including, without limitation, compliance with laws regarding notifications regarding capture of personal data and call recording. Avaya Support Tools are provided as an entitlement of Avaya Support Coverage (e.g., maintenance) and the entitlements are established by Avaya. The scope of the license for each Tool is described in its License terms and/or the applicable service description document. 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. 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. 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. Downloading Documentation For the most current versions of Documentation, see the Avaya Support website: or such successor site as designated by Avaya. 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.

4 Contents Chapter 1: Introduction... 6 Purpose... 6 Intended audience... 6 Prerequisites... 6 Related resources... 7 Documentation... 7 Training... 8 Viewing Avaya Mentor videos... 8 Support... 9 Chapter 2: Avaya Aura architecture overview Avaya platform offer Fresh deployment of Avaya Aura applications Solution Deployment Manager Solution Deployment Manager overview Solution Deployment Manager options Solution Deployment Manager client Solution Deployment Manager Accessing the Solution Deployment Manager client dashboard Chapter 3: Planning and preconfiguration Planning checklist Supported 7.0 servers Server hardware and resources SAL Gateway virtual appliance resource requirements Specifications of bundled software in the OVA Capacity of SAL Gateway in the virtualized environment Chapter 4: Initial setup and predeployment Downloading software from PLDS Uploading a file to the software library Registering SAL Gateway Accessing Solution Deployment Manager Adding the ESXi host details on Solution Deployment Manager Adding a location Adding an ESXi host Chapter 5: Deployment process SAL Gateway OVA deployment overview Deployment checklist Deploying the SAL Gateway OVA VM Deployment field descriptions VM Deployment Configuration Parameters tab field descriptions November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 4

5 Contents Chapter 6: Initial configuration Virtual machine management Starting a virtual machine from Solution Deployment Manager Stopping a virtual machine from Solution Deployment Manager Restarting a virtual machine from Solution Deployment Manager Out-of-Band Management (OOBM) network configuration Overview OOBM network interface management Static routes configuration Starting the SAL Gateway services Chapter 7: Postinstallation verification Testing the alarming service of SAL Gateway Testing the remote access service of SAL Gateway Testing the SAL Watchdog service Testing the SAL Gateway UI Chapter 8: Postinstallation customer responsibilities Chapter 9: Upgrading from System Platform to VMware Virtualized Environment Overview Upgrade checklist Backing up SAL Gateway 1.8 on CDOM Backing up Services-VM Backing up Services-VM 2.0 or Restoring SAL Gateway or Services-VM on 2.5 virtual appliance Post upgrade activities Chapter 10: Maintenance procedures Backup and restore overview Backing up the virtual machine Restoring a virtual machine Creating a snapshot Restoring a snapshot Appendix A: Password management Password policies Resetting the password of an operating system account Resetting the password of the admin user Resetting the password of the root user November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 5

6 Chapter 1: Introduction Purpose This document contains checklist and procedures for deploying the Secure Access Link (SAL) Gateway virtual appliance in the Avaya Aura Virtualized Environment by using Avaya Aura System Manager Solution Deployment Manager. The document includes installation, configuration, initial administration, and basic maintenance checklist and procedures. Intended audience The primary audience of this document is anyone who installs, configures, and verifies SAL Gateway in a virtualization environment at a customer site. The audience includes implementation engineers, field technicians, and solution providers from Avaya, BusinessPartners, and customers. Prerequisites Before you deploy the product, ensure that you have the following knowledge, skills, and tools: Knowledge Avaya Aura releases Linux operating system VMware and virtualized environment Skills VMware and virtualized environment Tools Avaya supported servers or VMware supported servers Solution Deployment Manager client if System Manager is unavailable or unreachable System Manager virtual machine resource requirements for each profile. Configuration tools and utilities November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 6

7 Related resources Related resources Documentation The following table lists the documents related to SAL Gateway and Avaya Aura Virtualized Environment. Download the documents from the Avaya Support website at support.avaya.com. Title Use this document to: Audience Design and overview Avaya Aura Virtualized Environment Solution Description Avaya Aura System Manager Overview and Specification Implementation Upgrading Avaya Aura System Manager to Release 7.0 Understand the virtualized environment solution from a functional view. Includes a high-level description of the solution, topology diagrams, customer requirements, and design considerations. Understand the high-level solution features and functionalities. Upgrade Avaya Aura System Manager from earlier releases to Release 7.0 on Avaya-provided appliance and customerprovided Virtualized Environment. Deploying Avaya Aura applications Install and configure Avaya Aura Upgrading and Migrating Avaya Aura applications to Release 7.0 Administration Administering Avaya Diagnostic Server SAL Gateway Administering Avaya Aura System Manager applications in Avaya Aura Virtualized Environment by using System Manager Solution Deployment Manager. Upgrade and migrate Avaya Aura applications, including Communication Manager and other associated applications, to Avaya Aura Release 7.0. Configure and administer SAL Gateway for remote servicing and alarm transfer facilities of Avaya products at a customer site. Perform administration tasks for System Manager and Avaya Aura applications that System Manager supports. Sales engineers, solution architects, and implementation engineers Sales engineers, solution architects, implementation engineers, support personnel Implementation engineers, support personnel Implementation engineers, support personnel Implementation engineers, support personnel Implementation engineers, support personnel, and system administrators System administrators, support personnel November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 7

8 Introduction Finding documents on the Avaya Support website About this task Use this procedure to find product documentation on the Avaya Support website. 1. Use a browser to navigate to the Avaya Support website at 2. At the top of the screen, enter your username and password and click Login. 3. Put your cursor over Support by Product. 4. Click Documents. 5. In the Enter your Product Here search box, type the product name and then select the product from the drop-down list. 6. If there is more than one release, select the appropriate release number from the Choose Release drop-down list. 7. Use the Content Type filter on the left to select the type of document you are looking for, or click Select All to see a list of all available documents. For example, if you are looking for user guides, select User Guides in the Content Type filter. Only documents in the selected category will appear in the list of documents. 8. Click Enter. Training The following courses are available on the Avaya Learning website at After logging in to the website, enter the course code or the course title in the Search field and press Enter or click > to search for the course. Course code Course title 2007V What is New in Avaya Aura V What is New in Avaya Aura Session Manager and System Manager V Migrating and Upgrading to Avaya Aura 7.0 Viewing Avaya Mentor videos Avaya Mentor videos provide technical content on how to install, configure, and troubleshoot Avaya products. About this task Videos are available on the Avaya Support website, listed under the video document type, and on the Avaya-run channel on YouTube. November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 8

9 Support To find videos on the Avaya Support website, go to and perform one of the following actions: - In Search, type Avaya Mentor Videos to see a list of the available videos. - In Search, type the product name. On the Search Results page, select Video in the Content Type column on the left. To find the Avaya Mentor videos on YouTube, go to and perform one of the following actions: - Enter a key word or key words in the Search Channel to search for a specific product or topic. - Scroll down Playlists, and click the name of a topic to see the available list of videos posted on the website. Note: Videos are not available for all products. Support Go to the Avaya Support website at for the most up-to-date documentation, product notices, and knowledge articles. You can also search for release notes, downloads, and resolutions to issues. Use the online service request system to create a service request. Chat with live agents to get answers to questions, or request an agent to connect you to a support team if an issue requires additional expertise. November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 9

10 Chapter 2: Avaya Aura architecture overview Avaya platform offer Avaya supports the following models: Avaya-provided appliance: System Manager Release 7.0 with the Solution Deployment Manager service runs on an Avaya-provided appliance. Avaya-provided appliance contains server hardware and Appliance Virtualization Platform. Appliance Virtualization Platform contains the ESXi hypervisor and the application OVA. From Release 7.0, Avaya Aura does not support templates. The new Common Server Release 2 servers that Avaya offers contain preinstalled Appliance Virtualization Platform. For the new S8300D or S8300E server installation, Appliance Virtualization Platform is installed at the customer site. In this offer, System Manager is a mandatory application. Virtualized Environment: Customers provide Virtualized Environment with a standard ESXi environment on which customers can deploy the System Manager and other Avaya Aura virtual applications that Avaya provides. Avaya virtual appliance model The Avaya virtual appliance model includes: An Avaya-defined common server platform. An operating system for allocating and managing servers among virtual machine instances running on the server. The hardware resources include CPU, memory, disk storage, and network interfaces. A Secure Access Gateway that supports a Secure Access Link for remote diagnosis by Avaya or Avaya Business Partner. However, Secure Access Link is optional. Fresh deployment of Avaya Aura applications In Avaya-appliance model, for fresh deployments, Avaya Aura is available to end-users through a set of Avaya-supplied common servers. Avaya appliances are prepackaged with the virtualization software, and delivered to customers in a ready-to-run state. In a customer-provided environment, VMware user can install Avaya Aura applications by using vcenter that VMware provides. November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 10

11 Solution Deployment Manager Solution Deployment Manager Solution Deployment Manager overview Solution Deployment Manager is a centralized software management solution in System Manager that provides deployments, upgrades, migrations, and updates to suite of Avaya Aura 7.0 applications. Solution Deployment Manager supports the operations on customer Virtualized Environment and Avaya-provided appliance model. Solution Deployment Manager provides the combined capabilities that Software Management, Avaya Virtual Application Manager, and System Platform provided in earlier releases. System Manager Release 7.0 is the primary management solution for Avaya Aura 7.0 applications. System Manager with the Solution Deployment Manager runs on: An Avaya-provided appliance: Contains server, Appliance Virtualization Platform, and Avaya Aura application OVA. Appliance Virtualization Platform includes a VMware ESXi 5.5 hypervisor. From Release 7.0, Appliance Virtualization Platform replaces System Platform. Customer-provided Virtualized Environment solution: Avaya Aura applications are deployed on customer-provided, certified VMware hardware. With Solution Deployment Manager, you can perform the following operations in Virtualized Environment and Avaya appliance models. Deploy Avaya Aura applications Upgrade and migrate Avaya Aura applications Download Avaya Aura applications Install service packs, feature packs, and software patches for the following Avaya Aura applications: - Communication Manager and associated devices, such as gateways, media modules, and TN boards. - Session Manager - Branch Session Manager - Utility Services - Appliance Virtualization Platform. The ESXi host running on Avaya-provided appliance. The upgrade process involves the following key tasks: Discover the Avaya Aura application. Analyze and download the necessary software components. Run the preupgrade check to ensure successful upgrade environment. Upgrade the Avaya Aura application. November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 11

12 Avaya Aura architecture overview Solution Deployment Manager options Avaya provides the following Solution Deployment Manager options: Centralized Solution Deployment Manager: The System Manager capability to deploy, upgrade, migrate, and install software patches for Avaya Aura applications. Release 7.0 supports migration of System Platform-based Avaya Aura 6.x applications to Release 7.0 on Avaya-provided appliance. However, in Release 7.0, Solution Deployment Manager does not support migration of Virtualized Environment-based 6.x applications to 7.0 in customer Virtualized Environment. Use vsphere Client to migrate to customer 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. Use the Solution Deployment Manager client to: - Deploy virtual appliances on Virtualized Environment or Avaya-provided appliance. - Upgrade System Manager, install System Manager patches, and install hypervisor patches. - Start, stop, and restart a virtual machine. - Change the footprint size based on the capacity requirements of the Avaya Aura application. The centralized and client Solution Deployment Manager provide the following capabilities: Centralized Solution Deployment Manager Manage virtual machine lifecycle Deploy Avaya Aura applications Deploy hypervisor patches only for Appliance Virtualization Platform Upgrade Avaya Aura applications Release 7.0 supports upgrades from Linux-based or System Platform-based to Virtualized Environment or Appliance Virtualization Platform. Release 7.0 does not support Virtualized Environment to Virtualized Environment upgrades. Install software patches for Avaya Aura applications Discover Avaya Aura applications Analyze Avaya Aura applications - Create and use the software library - Solution Deployment Manager client Manage virtual machine lifecycle Deploy Avaya Aura applications Deploy hypervisor patches only for Appliance Virtualization Platform Upgrade System Platform-based System Manager Install System Manager patches Deploy System Manager Solution Deployment Manager client For the initial System Manager deployment or when System Manager is inaccessible, you can use the Solution Deployment Manager client. The client can reside on the computer of the technician. November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 12

13 Solution Deployment Manager The Solution Deployment Manager client provides the functionality to install the OVAs on an Avayaprovided server or customer-provided Virtualized Environment. The user interface of the Solution Deployment Manager client looks similar to the centralized Solution Deployment Manager. System Manager supports the Solution Deployment Manager client. A technician can gain access to the user interface of the Solution Deployment Manager client from the computer or web browser. The Solution Deployment Manager client runs on Windows 7.0 and Windows 8, 64 bit. Use the Solution Deployment Manager client to: Deploy System Manager and Avaya Aura applications on Virtualized Environment or Avaya appliances. Upgrade System Platform-based System Manager and install System Manager and hypervisor patches. Start, stop, and restart a virtual machine. Change the footprint size based on the capacity requirements of the Avaya Aura application. You can deploy or upgrade the System Manager virtual machine only by using the Solution Deployment Manager client. Figure 1: Solution Deployment Manager client dashboard Solution Deployment Manager The Solution Deployment Manager capability simplifies and automates the deployment and upgrade process. With Solution Deployment Manager, you can deploy the following Avaya Aura Release 7.0 applications: Utility Services 7.0 System Manager 7.0 Session Manager 7.0 Branch Session Manager 7.0 Communication Manager 7.0 November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 13

14 Avaya Aura architecture overview Application Enablement Services 7.0 WebLM 7.0 Avaya Breeze 3.1 SAL 2.5 Communication Manager Messaging 7.0 Avaya Aura Media Server 7.7 With Solution Deployment Manager, you can migrate, upgrade, and update the following applications: Linux-based Communication Manager and the associated devices, such as Gateways, TN boards, and media modules. Linux-based Session Manager System Platform-based Communication Manager - Duplex CM Main / Survivable Core with Communication Manager - Simplex CM Main / Survivable Core with Communication Manager, Communication Manager Messaging, and Utility Services - Simplex Survivable Remote with Communication Manager, Branch Session Manager, and Utility Services - Embedded CM Main with Communication Manager, Communication Manager Messaging, and Utility Services - Embedded Survivable Remote with Communication Manager, Branch Session Manager, and Utility Services System Platform-based Branch Session Manager - Simplex Survivable Remote with Communication Manager, Branch Session Manager, and Utility Services - Embedded Survivable Remote with Communication Manager, Branch Session Manager, and Utility Services Note: However, you must manually migrate Services VM that is part of the template. You require only one SAL or Services VM per enterprise to support an Avaya Services offer. The centralized deployment and upgrade process provide better support to customers who want to upgrade their systems to Avaya Aura Release 7.0. The process reduces the upgrade time and error rate. Solution Deployment Manager dashboard You can gain access to the Solution Deployment Manager dashboard from the System Manager web console or by installing the Solution Deployment Manager client. November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 14

15 Solution Deployment Manager Solution Deployment Manager capabilities With Solution Deployment Manager, you can perform deployment and upgrade-related tasks by using the following links: Upgrade Release Setting: To select Release 7.0 or as the target upgrade. Release 7.0 is the default upgrade target. Manage Software: To upgrade the legacy IP Office and B5800. VM Management: To deploy OVA files for the supported Avaya Aura application. Upgrade Management: To upgrade Communication Manager that includes TN boards, media gateways and media modules, Session Manager, Communication Manager Messaging, Utility Services, Branch Session Manager to Release 7.0. User Settings: To configure the location from where System Manager displays information about the latest software and firmware releases. Download Management: To download the OVA files and firmware to which the customer is entitled. The download source can be the Avaya PLDS or an alternate source. Software Library Management: To configure the local or remote software library for storing the downloaded software and firmware files. Accessing the Solution Deployment Manager client dashboard About this task Note: If you perform deploy, upgrade, and update operations from the Solution Deployment Manager client, ignore the steps that instruct you to access System Manager Solution Deployment Manager and the related navigation links. To start the Solution Deployment Manager client, perform one of the following: Click Start > All Programs > Avaya, and click SDM Client > Avaya SDM Client. November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 15

16 Avaya Aura architecture overview Click. November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 16

17 Chapter 3: Planning and preconfiguration Planning checklist As an Avaya customer, ensure that you complete the following before deploying the SAL Gateway open virtual appliance (OVA): No. Action Notes 1 Ensure that a supported server for the Avaya appliance model is installed. 2 Ensure that Appliance Virtualization Platform is installed on the supported server. 3 Ensure that you have all required hardware for the VMware environment. 4 Ensure that the virtualization environment has enough resources to be assigned for the SAL Gateway virtual appliance. 5 Ensure that System Manager 7.0 is available in the environment. 6 Download the SAL Gateway OVA file from PLDS. 7 Copy the downloaded SAL Gateway OVA file to a directory on the local System Manager. 8 Upload the SAL Gateway OVA to the software library of System Manager. 9 Ensure that the SAL Gateway registration process is complete and you have received the Solution Element ID and Alarm ID for the new SAL Gateway. See Supported 7.0 servers on page 18. See Upgrading and Migrating Avaya Aura applications to Release 7.0. See Server hardware and resources on page 19. See SAL Gateway virtual appliance resource requirements on page 19. See Upgrading Avaya Aura System Manager to Release 7.0 and Upgrading and Migrating Avaya Aura applications to Release 7.0. To log on to the PLDS website, use your Avaya Single Sign On (SSO) login, which is associated with the Sold-To number that identifies the location where you want to install SAL Gateway. Copy the OVA file to the /swlibrary/ staging/sync/ directory. See Uploading a file to the software library on page 22. See Registering SAL Gateway on page 23. You must provide a registered Solution Element ID to make SAL Gateway Table continues November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 17

18 Planning and preconfiguration No. Action Notes 10 (Optional) Install the Solution Deployment Manager client for Windows. 11 Through Solution Deployment Manager, configure a location. 12 Through Solution Deployment Manager, configure an ESXi host and associate the host with the location. 13 Ensure that the Appliance Virtualization Platform host and all virtual machines running on the host are on the same subnet mask. operational. Until you enter a correct Solution Element ID, the SAL Gateway services do not start. See Upgrading and Migrating Avaya Aura applications to Release 7.0. If System Manager is unavailable for some reason, you can use the Solution Deployment Manager client for managing the virtual machines. See Adding a location on page 25. See Adding an ESXi host on page 25. If Out of Band Management is configured in an Appliance Virtualization Platform deployment, you need two subnet masks, one for each of the following: Public or signaling traffic, Appliance Virtualization Platform, and all virtual machines public traffic. Management, Appliance Virtualization Platform, and all virtual machine management ports. Supported 7.0 servers In the Avaya appliance model, the customer can deploy or upgrade to Avaya Aura Release 7.0 applications on the following Avaya-provided servers: Dell PowerEdge R610 2CPU MID2 HP ProLiant DL360 G7 2CPU MID4 Dell PowerEdge R620 1CPU MID3 HP ProLiant DL360p G8 S8300D, for Communication Manager and Branch Session Manager S8300E, for Communication Manager and Branch Session Manager November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 18

19 Server hardware and resources Server hardware and resources 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 SAL Gateway virtual appliance resource requirements Before you deploy the SAL Gateway virtual appliance, you must ensure that the following minimal set of resources is available on the ESXi host. These resources are specified in the SAL Gateway OVA. VMware Resource vcpu 1 CPU speed Memory Storage reservation NIC Value 2.3 GHz 1GB 10 GB 1000 Mbps If you cannot guarantee the availability of the required resources on the ESXi host, do not deploy the SAL Gateway virtual appliance on that host. You might deploy the SAL Gateway virtual appliance on a host that does not have the resources to allocate to the virtual machine to start. If CPU resources are limited, the system displays the Insufficient capacity on each physical CPU, or a similar message after the start-up request. To correct such limitations, you can adjust the virtual machine properties. Sometimes, the CPU adjustments might not correct the start-up conditions. You might have to adjust other virtual machine resources as required. Important: Modifying the allocated resources might have a direct impact on the performance, capacity, and stability of the SAL Gateway virtual appliance. To run at full capacity, ensure that the virtual machine meets these resource size requirements. Removing or downsizing reservations might put this requirement at risk. For SAL Gateway to perform at maximum capacity, maintain the resource allocation of the virtual machine. Specifications of bundled software in the OVA The SAL Gateway OVA contains the application software, operating system, and other required software components, along with preinstalled VMware tools. November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 19

20 Planning and preconfiguration The following are the specifications of the software components included as part of the SAL Gateway OVA. Operating system CentOS 6.6, 64-bit Java Oracle JRE 1.7 update 75 Application software SAL Gateway Capacity of SAL Gateway in the virtualized environment The following table provides the capacity of SAL Gateway in the VMware virtualized environment: Maximum managed elements 15 Maximum alarm rate per minute 20 Maximum simultaneous remote connections 8 SAL Gateway performs at the maximum capacity when: The virtual machine meets the required specifications and the resource allocation. The alarm flow, remote sessions, and network conditions must the normal. Note: To ensure stable and predictable performance, do not exceed the limit of 15 managed elements. To support more than 15 managed elements, install either a software-only SAL Gateway on a standalone server or Avaya Diagnostic Server OVA on your VMware environment. November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 20

21 Chapter 4: Initial setup and predeployment Downloading software from PLDS When you place an order for an Avaya PLDS-licensed software product, PLDS creates the license entitlements of the order and sends an notification to you. The includes a license activation code (LAC) and instructions for accessing and logging into PLDS. Use the LAC to locate and download the purchased license entitlements. In addition to PLDS, you can download the product software from using the Downloads and Documents tab at the top of the page. Note: Only the latest service pack for each release is posted on the support site. Previous service packs are available only through PLDS. 1. Enter in your Web browser to access the Avaya PLDS website. 2. Enter your login ID and password. 3. On the PLDS home page, select Assets. 4. Click View Downloads. 5. Click on the search icon (magnifying glass) for Company Name. 6. In the %Name field, enter Avaya or the Partner company name. 7. Click Search Companies. 8. Locate the correct entry and click the Select link. 9. Enter the Download Pub ID. 10. Click Search Downloads. 11. Scroll down to the entry for the download file and click the Download link. 12. In the Download Manager box, click the appropriate download link. Note: The first link, Click to download your file now, uses the Download Manager to download the file. The Download Manager provides features to manage the download November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 21

22 Initial setup and predeployment (stop, resume, auto checksum). The click here link uses your standard browser download and does not provide the download integrity features. 13. If you use Internet Explorer and get an error message, click the install ActiveX message at the top of the page and continue with the download. 14. Select a location where you want to save the file and click Save. 15. If you used the Download Manager, click Details to view the download progress. Uploading a file to the software library About this task Use the procedure to upload software files such as OVA, images, and firmware that are required during the deployment, migration, upgrade, and update of Avaya Aura applications. Before you begin Start an SSH session. On Download Management page, click Refresh Families. When you add or update details in the versions.xml file, click Refresh Families again to get the updated information. 1. On the System Manager web console, click Services > Solution Deployment Manager. 2. In the left navigation pane, click Software Library Management. 3. Click Manage Files. 4. From System Manager command line interface, copy the required OVA file to the / swlibrary/staging/sync/ location that you had created in System Manager. Note: You require admin privileges to the /swlibrary/staging/sync/ location. The system displays the file that you copied in the Sync Files from directory section. 5. Provide the following information: MD5 Checksum: The value mentioned in the source or original location of the file. Software Library: The local or remote software library. Product Family Note: For SAL, in Product Family, Device Type, and Software Type fields, select Others. Device Type November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 22

23 Registering SAL Gateway Software Type If the file is already in versions.xml, the system populates the information. If the file does not already exist in versions.xml, the system does not display the file details. You cannot use the file for upgrade in Upgrade Management. You can use the file only for new deployment from VM Management. 6. Select the file. 7. Click Sync. In File Sync Started Message, the system displays a message about the status of the schedule of the job. 8. Click OK. When the job completes, the system displays the file in the Software Library Files section. 9. To check the status of the job, click Services > Scheduler > Pending Jobs. When the job is complete, the system displays the file in the Software Library Files and removes from Sync Files from directory. Registering SAL Gateway About this task Registering a product with Avaya is a process that uniquely identifies the product so that Avaya can service the product. When you register a new SAL Gateway, Avaya assigns a Solution Element ID and a Product ID to the SAL Gateway. You require these identifiers when you install SAL Gateway. SAL Gateway becomes operational only when you configure SAL Gateway with the correct identifiers. Through these IDs, Avaya can uniquely identify the SAL Gateway at your location. Use this procedure to register SAL Gateway and to generate the SAL Gateway identifiers through Global Registration Tool (GRT) without the use of any material codes. 1. Open the GRT website at The GRT website redirects you to the Avaya single sign-on (SSO) webpage. 2. Log in using your SSO ID and password. 3. On the GRT home page, click Create New Registration > SAL Migration Only. 4. In the Sold To/Functional Location field, enter the Sold To or customer functional location number that identifies the location where you want to deploy SAL Gateway. 5. On the Site Contact Validation page, complete the required contact information fields. Provide valid information so that Avaya can contact you to notify you about the registration status. November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 23

24 Initial setup and predeployment 6. Click Next. The SAL Gateway Migration List page lists the SAL Gateway instances available for the Sold To number that you provided. 7. Click Create New SAL Gateway. Next steps GRT starts an automatic end-to-end registration of a new SAL Gateway and performs the install base creation process. After the install base creation is complete, GRT automatically proceeds to the first step of the technical onboarding process to generate the Solution Element ID and Product ID of SAL Gateway. The SAL Onboarding Summary page displays the Solution Element ID and Product ID generated for the new SAL Gateway. You also receive an notification with the new IDs. Complete the SAL Gateway installation process. Perform the technical onboarding process for devices that require support through the new SAL Gateway. See Technical Onboarding Help Document at registration. Add the devices as managed elements to your SAL Gateway using the SEIDs provided. Accessing Solution Deployment Manager About this task You require to start Solution Deployment Manager to deploy and upgrade virtual machines, and install service packs or patches. Perform one of the following: If System Manager is not already deployed, double-click the Solution Deployment Manager client. If System Manager is available, on the web console, click Services > Solution Deployment Manager. November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 24

25 Adding the ESXi host details on Solution Deployment Manager Adding the ESXi host details on Solution Deployment Manager Note: Adding a location and a host are one-time activities on Solution Deployment Manager. If the ESXi host details are already available on Solution Deployment Manager, then you do not need to perform the following procedures. Adding a location About this task You can define the physical location of the host and configure the location specific information. You can update the information later. 1. Perform one of the following: For System Manager Solution Deployment Manager, on the web console, click Services > Solution Deployment Manager, and then click VM Management. For the Solution Deployment Manager client, on the desktop, click the SDM icon ( ), and then click VM Management. 2. On the Location tab, in the Locations section, click New. 3. In the New Location section, perform the following: a. In the Required Location Information section, type the location information. b. In the Optional Location Information section, type the network parameters for the virtual machine. 4. Click Save. The system displays the new location in the VM Management Tree section. Adding an ESXi host About this task Use the procedure to add an Appliance Virtualization Platform or ESXi host. You can associate an ESXi host with an existing location. Before you begin A location must be available. November 2016 Deploying SAL Gateway using System Manager in the Virtualized Environment 25