Deploying Avaya Aura applications from System Manager

Deploying Avaya Aura applications from System Manager Release 7.0.1 Issue 2 May 2016

2015-2016, 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: https://support.avaya.com/helpcenter/ getgenericdetails?detailid=c20091120112456651010 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, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO 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, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO, 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. License type(s) 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 e-mail 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 e-mail 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 2009. The Heritage Nortel Software is the software contained within the list of Heritage Nortel Products located at https://support.avaya.com/licenseinfo 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: https:// 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 HTTP://WWW.MPEGLA.COM. 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 WWW.SIPRO.COM/CONTACT.HTML. 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 HTTP:// WWW.MPEGLA.COM. 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 +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see

the Avaya Support website: https://support.avaya.com 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 https:// support.avaya.com/security. Suspected Avaya product security vulnerabilities are handled per the Avaya Product Security Support Flow (https:// support.avaya.com/css/p8/documents/100161515). Downloading Documentation For the most current versions of Documentation, see the Avaya Support website: https://support.avaya.com, or such successor site as designated by Avaya. Contact Avaya Support See the Avaya Support website: https://support.avaya.com for product or Hosted Service notices and articles, or to report a problem with your Avaya product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: https://support.avaya.com (or such successor site as designated by Avaya), scroll to the bottom of the page, and select Contact Avaya Support. Trademarks The trademarks, logos and service marks ( Marks ) displayed in this site, the Documentation, Hosted Service(s), and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, its licensors, its suppliers, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation, Hosted Service(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya and Avaya Aura are registered trademarks of Avaya Inc. All non-avaya trademarks are the property of their respective owners. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Contents Chapter 1: Introduction... 9 Purpose... 9 Prerequisites... 9 Change history... 9 Chapter 2: Avaya Aura overview... 11 Avaya Aura Virtualized offers... 11 Appliance Virtualization Platform overview... 11 Fresh deployment of Avaya Aura applications... 13 Solution Deployment Manager... 13 Solution Deployment Manager overview... 13 Solution Deployment Manager client... 14 Solution Deployment Manager... 20 Virtual machine management... 22 Utility Services in the Avaya Aura Virtualized Appliance offer... 23 Chapter 3: Planning and configuration... 24 Supported servers... 24 Software requirements... 24 Chapter 4: Initial setup and connectivity... 26 Accessing Solution Deployment Manager... 26 Deployment checklist... 26 Chapter 5: Preinstallation tasks... 29 Installing Appliance Virtualization Platform... 29 Configuring servers preinstalled with Appliance Virtualization Platform... 31 Uploading a file to the software library... 34 Downloading the OVA file to System Manager... 35 Chapter 6: Deploying Avaya Aura applications... 36 Managing the location... 36 Viewing a location... 36 Adding a location... 36 Editing the location... 37 Deleting a location... 37 VM Management field descriptions... 37 New and Edit location field descriptions... 42 Managing the host... 43 Adding an ESXi host... 43 Editing an ESXi host... 44 Installing the Appliance Virtualization Platform patch from Solution Deployment Manager... 44 Changing the network parameters for an Appliance Virtualization Platform host... 46 May 2016 Deploying Avaya Aura applications 5

Contents Changing the network settings for an Appliance Virtualization Platform host from Solution Deployment Manager... 47 Changing the password for an Appliance Virtualization Platform host... 50 Enabling and disabling SSH on Appliance Virtualization Platform from Solution Deployment Manager... 51 Enabling and disabling SSH on Appliance Virtualization Platform from System Manager CLI... 51 Changing the IP address and default gateway of the host... 52 Shutting down the Appliance Virtualization Platform host... 53 Restarting the Appliance Virtualization Platform host... 54 Deleting an ESXi host... 54 Mapping the ESXi host to an unknown location... 54 New and Edit host field descriptions... 55 Change Network Parameters field descriptions... 55 Host Network / IP Settings field descriptions... 56 Change Password field descriptions... 57 Update field descriptions... 58 Managing the virtual machine... 58 Deploying the System Manager OVA file by using the Solution Deployment Manager client... 58 VM Deployment field descriptions... 60 Installing service packs and software patches on System Manager by using the Solution Deployment Manager client... 63 Managing the virtual machine... 64 Deploying the Utility Services OVA file... 64 Deploying an OVA file for an Avaya Aura application... 66 Editing a virtual machine... 68 Deleting a virtual machine... 70 Changing the network parameters of Appliance Virtualization Platform and Avaya Aura applications... 70 Updating Services Port Static Routing on an Avaya Aura application... 72 Starting a virtual machine from Solution Deployment Manager... 72 Stopping a virtual machine from Solution Deployment Manager... 73 Restarting a virtual machine from Solution Deployment Manager... 73 VM Deployment field descriptions... 73 VM Deployment Configuration and Network Parameters field descriptions... 77 Update Static Routing field descriptions... 80 Installed Patches field descriptions... 80 Update VM field descriptions... 81 Reestablish Connection field descriptions... 81 Network parameter update for Avaya Aura applications... 82 Certificate validation... 83 Certification validation... 83 Generating and accepting certificates... 84 May 2016 Deploying Avaya Aura applications 6

Contents Updating the certificate on the ESXi host from VMware... 85 Managing certificates for existing hosts... 86 Generating new self-signed certificates for the ESXi host... 87 Managing vcenter... 88 Adding a vcenter to Solution Deployment Manager... 88 Editing vcenter... 89 Deleting vcenter from Solution Deployment Manager... 89 Map vcenter field descriptions... 90 New vcentre and Edit vcentre field descriptions... 91 Monitoring a host and virtual machine... 92 Monitoring a host... 92 Monitoring a virtual machine... 92 Chapter 7: Installing software patches, service packs, and feature packs for applications... 93 Installing software patches... 93 Installed Patches field descriptions... 94 Chapter 8: Out of Band Management configuration... 97 Avaya Aura Out of Band Management... 97 Appliance Virtualization Platform Out of Band Management... 98 Out of Band Management in Virtualized Environment... 100 Utility Services Out of Band Management... 100 System Manager Out of Band Management... 101 Out of Band Management in System Manager... 101 Configuring Out of Band Management on System Manager... 102 Configuring Out of Band Management on System Manager in the Geographic Redundancy setup... 103 Communication Manager Out of Band Management... 104 Detailed description of Out of Band Management... 104 Out of Band Management management administration... 105 Screens for administering Out-of-Band management... 105 Administering the Out of Band Management of management data... 105 Adding a static route between the Out-of-Band management interface and the enterprise network... 107 Session Manager Out of Band Management ports... 107 Application Enablement Services Out of Band Management... 108 Out of Band Management in Avaya Breeze... 109 Out of Band Management in SAL... 109 Chapter 9: Post Installation Verification... 111 Verifying the installation of System Manager... 111 Post installation checklist... 111 Verifying the connections... 112 Chapter 10: Postinstallation tasks... 113 Loading a customer-specific authentication file... 113 May 2016 Deploying Avaya Aura applications 7

Contents Downloading and installing an authentication file on the Avaya Aura application... 114 Chapter 11: Resources... 116 Documentation... 116 Finding documents on the Avaya Support website... 117 Training... 117 Viewing Avaya Mentor videos... 119 Support... 119 Glossary... 120 May 2016 Deploying Avaya Aura applications 8

Chapter 1: Introduction Purpose This document contains installation, configuration, initial administration, and basic maintenance checklist and procedures for deploying applications in Avaya Aura Virtualized Appliance on Appliance Virtualization Platform by using Avaya Aura System Manager Solution Deployment Manager. This document is intended for people who install and configure a verified Avaya Aura application reference configuration at a customer site. 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 Change history The following changes have been made to this document since the last issue: May 2016 Deploying Avaya Aura applications 9

Introduction Issue Date Summary of changes 2.0 May 2016 Added procedures for installing the Release 7.0.1 feature pack on Release 7.0. Added procedures for the following in VM Management: - Enabling and disabling SSH on Appliance Virtualization Platform. - Changing network settings that includes, changing VLAN ID, NIC speed, and NIC team and unteaming for an Appliance Virtualization Platform host. - Restarting the Appliance Virtualization Platform host. - Shutting down the Appliance Virtualization Platform host. - Viewing the job history of all operations that are performed on VM Management. - Updating the license status of hosts and virtual machines state. - Removing the Appliance Virtualization Platform patch. - Changing the IP address and default gateway of the host. - Validating the certificates. Cleaning up the current pending or pause state of applications during upgrade. Added procedure for installing custom patches for Avaya Aura applications. Added flexibility to select application and data port numbers during the Solution Deployment Manager client installation. Added support for Dell PowerEdge R630 and HP ProLiant DL360 G9 common servers. Added Out of Band Management configuration chapter. May 2016 Deploying Avaya Aura applications 10

Chapter 2: Avaya Aura overview Avaya Aura Virtualized offers Starting with Release 7.0, Avaya Aura supports the following two Avaya virtualization offers based on VMware: Avaya Aura Virtualized Appliance (VA) - Avaya-provided server, Avaya Appliance Virtualization Platform, based on the customized OEM version of VMware ESXi 5.5. Avaya Aura Virtualized Environment (VE) - Customer-provided VMware infrastructure The virtualization offers, provides the following benefits: Simplifies IT management using common software administration and maintenance. Requires fewer servers and racks which reduces the footprint. Lowers power consumption and cooling requirements. Enables capital equipment cost savings. Lowers operational expenses. Uses standard operating procedures for both Avaya and non-avaya products. Deploys Avaya Aura virtual products in a virtualized environment on Avaya provided servers or customer-specified servers and hardware. Business can scale rapidly to accommodate growth and to respond to changing business requirements Related links Appliance Virtualization Platform overview on page 11 Appliance Virtualization Platform overview From Release 7.0, Avaya uses the VMware -based Avaya Appliance Virtualization Platform to provide virtualization for Avaya Aura applications in Avaya Aura Virtualized Appliance offer. Avaya Aura Virtualized Appliance offer includes: Common Servers: Dell PowerEdge R610, Dell PowerEdge R620, HP ProLiant DL360 G7, HP ProLiant DL360p G8, Dell PowerEdge R630, and HP ProLiant DL360 G9 S8300D and S8300E Appliance Virtualization Platform is the customized OEM version of VMware ESXi 5.5. With Appliance Virtualization Platform, customers can run any combination of supported applications on May 2016 Deploying Avaya Aura applications 11

Avaya Aura overview Avaya-supplied servers. Appliance Virtualization Platform provides greater flexibility in scaling customer solutions to individual requirements. From Release 7.0, Appliance Virtualization Platform replaces System Platform. Avaya Aura Release 7.0.1 supports the following applications on Appliance Virtualization Platform: Utility Services 7.0.1 System Manager 7.0.1 Session Manager 7.0.1 Branch Session Manager 7.0.1 Communication Manager 7.0.1 Application Enablement Services 7.0.1 WebLM 7.0.1 Avaya Breeze 3.1.1 SAL 2.5 Communication Manager Messaging 7.0 Avaya Aura Media Server 7.7.0.292 (SP3) Avaya Scopia 8.3.5 May 2016 Deploying Avaya Aura applications 12

Fresh deployment of Avaya Aura applications Avaya Proactive Contact 5.1.2 For more information about installing Avaya Proactive Contact and administering Appliance Virtualization Platform with Avaya Proactive Contact, see the Avaya Proactive Contact documentation. Related links Avaya Aura Virtualized offers on page 11 Fresh deployment of Avaya Aura applications In Avaya Aura Virtualized Appliance model, for fresh deployments, Avaya Aura is available to endusers through a set of Avaya-supplied common servers. Avaya Aura Virtualized Applianceis 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. 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 Avaya Aura 7.0 applications. Solution Deployment Manager supports the operations on customer Virtualized Environment and Avaya Aura Virtualized Appliance model. Solution Deployment Manager provides the combined capabilities that Software Management, Avaya Virtual Application Manager, and System Platform provided in earlier releases. Note: In Release 7.0.1, Solution Deployment Manager does not support migration of Virtualized Environment-based 6.x applications to Release 7.0.1 in customer Virtualized Environment. Use vsphere Client to migrate to customer Virtualized Environment. Release 7.0 and later supports a standalone version of Solution Deployment Manager, the Solution Deployment Manager client. For more information, see Using the Solution Deployment Manager client. System Manager is the primary management solution for Avaya Aura 7.0 and later applications. System Manager with the Solution Deployment Manager runs on: Avaya Aura Virtualized Appliance: Contains a server, Appliance Virtualization Platform, and Avaya Aura application OVA. Appliance Virtualization Platform includes a VMware ESXi 5.5 hypervisor. May 2016 Deploying Avaya Aura applications 13

Avaya Aura overview From Release 7.0, Appliance Virtualization Platform replaces System Platform. Customer-provided Virtualized Environment solution: Avaya Aura applications are deployed on customer-provided, VMware certified hardware. With Solution Deployment Manager, you can perform the following operations in Virtualized Environment and Avaya Aura Virtualized 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 that is running on the Avaya Aura Virtualized Appliance. The upgrade process from Solution Deployment Manager involves the following key tasks: Discover the Avaya Aura applications. Refresh applications and associated devices, and download the necessary software components. Run the preupgrade check to ensure successful upgrade environment. Upgrade Avaya Aura applications. Install software patch, service pack, or feature pack on Avaya Aura applications. For more information about the setup of the Solution Deployment Manager functionality that is part of System Manager 7.x, see Avaya Aura System Manager Solution Deployment Manager Job-Aid. 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. The Solution Deployment Manager client provides the functionality to install the OVAs on an Avayaprovided server or customer-provided Virtualized Environment. 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 Avaya appliances and Virtualized Environment. May 2016 Deploying Avaya Aura applications 14

Solution Deployment Manager Upgrade System Platform-based System Manager. Install System Manager software patches, service packs, and feature packs. Install Appliance Virtualization Platform patches. Restart and shutdown the Appliance Virtualization Platform host. Start, stop, and restart a virtual machine. Change the footprint of Avaya Aura applications that support dynamic resizing. For example, Session Manager and Avaya Breeze. Note: 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 Related links Capability comparison between System Manager Solution Deployment Manager and the Solution Deployment Manager client on page 15 Installing the Solution Deployment Manager client on your computer on page 16 Accessing the Solution Deployment Manager client dashboard on page 18 Solution Deployment Manager client capabilities on page 19 Capability comparison between System Manager Solution Deployment Manager and the Solution Deployment Manager client Centralized Solution Deployment Manager Manage virtual machine lifecycle Deploy Avaya Aura applications Deploy hypervisor patches only for Appliance Virtualization Platform Upgrade Avaya Aura applications 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 Table continues May 2016 Deploying Avaya Aura applications 15

Avaya Aura overview Centralized Solution Deployment Manager Release 7.x supports upgrades from Linux-based or System Platform-based to Virtualized Environment or Appliance Virtualization Platform. Release 7.0.1 does not support Virtualized Environment to Virtualized Environment upgrades. Install software patches for Avaya Aura applications excluding System Manager application Discover Avaya Aura applications Analyze Avaya Aura applications - Create and use the software library - Related links Solution Deployment Manager client on page 14 Solution Deployment Manager client Install System Manager patches Deploy System Manager Installing the Solution Deployment Manager client on your computer About this task In Avaya Aura Virtualized Appliance offer, when the centralized Solution Deployment Manager on System Manager is unavailable, use the Solution Deployment Manager client to deploy the Avaya Aura applications. You can use the Solution Deployment Manager client to install software patches and hypervisor patches. Use the Solution Deployment Manager client to deploy, upgrade, and update System Manager. Note: Click Next only once, and wait for the installer to load the next screen. Before you begin 1. If an earlier version of the Solution Deployment Manager client is running on the computer, remove the older version from Control Panel > Programs > Programs and Features. If you are unable to uninstall, see Uninstalling the Solution Deployment Manager client. 2. Ensure that Windows 7 or 8.1 64-bit operating system is installed on the computer. Tip: On Computer, right-click properties, and ensure that Windows edition section displays the version of Windows operating system. 3. Ensure that at least 5 GB of disk space is available at the location where you want to install the client. Tip: Using the Windows file explorer, click Computer, and verify that the Hard Disk Drives section displays the available disk space available. 4. To avoid port conflict, stop any application server that is running on your computer. May 2016 Deploying Avaya Aura applications 16

Solution Deployment Manager Tip: From the system tray, open the application service monitor, select the application server that you want to stop, and click Stop. 5. Ensure that the firewall allows the ports that are required to install the Solution Deployment Manager client installation and use the Solution Deployment Manager functionality. 6. Ensure that ports support Avaya Aura 7.0.1 supported browsers. 7. Close all applications that are running on your computer. 8. Do not set CATALINA_HOME as environment variable on the computer where you install the Solution Deployment Manager client. Tip: On Computer, right-click properties, and perform the following: a. In the left navigation pane, click Advanced system settings. b. On the System Properties dialog box, click Advanced tab, and click Environment Variables. c. Verify the system variables. 9. Ensure that the computer on which the Solution Deployment Manager client is running is connected to the network. Procedure Operations that you perform might fail if the computer is not connected to the network. 1. Download the Avaya_SDMClient_win64_7.0.1.0.0620211_43.zip file from the Avaya PLDS website at https://plds.avaya.com/. On the Avaya PLDS website, at https://plds.avaya.com/, click Support by Products > Downloads, and provide the product System Manager, and version as 7.0.x. 2. Copy the zip file, and extract to a location on your computer by using the WinZip application. You can also copy the zip file to your software library directory, for example, c:/tmp/aura. 3. Right click on the executable, and select Run as administrator to run the Avaya_SDMClient_win64_7.0.1.0.0620211_43.exe file. The system displays the Avaya Solution Deployment Manager screen. 4. On the Welcome page, click Next. 5. On the License Agreement page, read the License Agreement, and if you agree to its terms, click I accept the terms of the license agreement and click Next. 6. On the Install Location page, perform 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. May 2016 Deploying Avaya Aura applications 17

Avaya Aura overview 8. On the Preinstallation Summary page, review the information, and click Next. 9. On the User Input page, perform 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. To change the default directory, in Select Location of Software Library Directory, click Choose and select a directory. The system saves the artifacts in the specified directory. During deployments, you can select the OVA file from the directory. c. In Data Port No, select the appropriate port from the range 1527 through 1627. d. In Application Port No, select the appropriate port from the range 443 through 543. e. (Optional) Click Reset All to Default. 10. On the Summary and Validation page, verify the product information and the system requirements. The system performs the 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 the ports available. 11. Click Install. 12. To exit the installer, on the Install Complete page, click Done. The installer creates a shortcut on the desktop. 13. To start the client, click the Solution Deployment Manager client icon,. Next steps Configure the laptop to get connected to the services port if you are using the services port to install. Connect the Solution Deployment Manager client to Appliance Virtualization Platform through the customer network or services port. For more information, see Methods to connect Solution Deployment Manager client to Appliance Virtualization Platform. Related links Solution Deployment Manager client on page 14 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. May 2016 Deploying Avaya Aura applications 18

Solution Deployment Manager Procedure To start the Solution Deployment Manager client, perform one of the following: Click Start > All Programs > Avaya, and click SDM Client > Avaya SDM Client. Click. Related links Solution Deployment Manager client on page 14 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.1, 64-bit Professional or Enterprise Supports the same web browsers as System Manager Release 7.0.1. Provides the user interface with similar look and feel as the central Solution Deployment Manager in System Manager Release 7.0.1. Supports deploying the System Manager OVA. The Solution Deployment Manager client is the only option to deploy System Manager. Supports Flexible footprint feature. The size of the virtual resources depends on the capacity requirements of the Avaya Aura applications. Defines the physical location, Appliance Virtualization Platform or ESXi host, and discovers virtual machines that are required for application deployments and virtual machine life cycle management. Manages lifecycle of the OVA applications that are deployed on the ESXi host. The lifecycle includes start, stop, reset virtual machines, and establishing trust for virtual machines. Deploys the Avaya Aura applications that can be deployed from the central Solution Deployment Manager for Avaya Aura Virtualized Appliance and customer Virtualized Environment. You can deploy one application at a time. Configures 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 patches for the hypervisor on Appliance Virtualization Platform. Supports installing software patches, service packs, and feature packs only for System Manager. Avaya Aura applications must use centralized Solution Deployment Manager from System Manager to install software patches, service packs, and feature packs. May 2016 Deploying Avaya Aura applications 19

Avaya Aura overview Related links Solution Deployment Manager client on page 14 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 applications in Release 7.0.1: Utility Services 7.0.1 System Manager 7.0.1 Session Manager 7.0.1 Branch Session Manager 7.0.1 Communication Manager 7.0.1 Application Enablement Services 7.0.1 WebLM 7.0.1 Avaya Breeze 3.1.1 SAL 2.5 Communication Manager Messaging 7.0 Avaya Aura Media Server 7.7.0.292 (SP3) Avaya Scopia 8.3.5 Avaya Proactive Contact 5.1.2 For more information about installing Avaya Proactive Contact and administering Appliance Virtualization Platform with Avaya Proactive Contact, see the Avaya Proactive Contact documentation. Note: You must deploy the Release 7.0 OVA, and then install the Release 7.0.1 file on the Avaya Aura Release 7.0 application. With Solution Deployment Manager, you can migrate, upgrade, and update the following applications: Linux-based Communication Manager 5.x and the associated devices, such as Gateways, TN boards, and media modules. Note: In bare metal Linux-based deployments, the applications are directly installed on the server and not as a virtual machine. Linux-based Session Manager 6.x May 2016 Deploying Avaya Aura applications 20

Solution Deployment 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 virtual machine that is part of the template. The centralized deployment and upgrade process provide better support to customers who want to upgrade their systems to Avaya Aura Release 7.0.1. 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. 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 6.3.8 as the target upgrade. Release 7.0.1 is the default upgrade target. May 2016 Deploying Avaya Aura applications 21

Avaya Aura overview Manage Software: To upgrade IP Office. 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.1. 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. Upload Version XML: To save the version.xml file to System Manager. You require the version.xml file to perform upgrades. Virtual machine management The VM Management link from Solution Deployment Manager provides the virtual machine management. VM Management provides the following capabilities: Defines the physical location, Appliance Virtualization Platform or ESXi host, and discovers virtual machines that are required for application deployments and virtual machine life cycle management. Supports password change, patch installation, restart, shutdown, and certificate validation of host. Also, enables and disables SSH on the host. Manages lifecycle of the OVA applications that are deployed on the ESXi host. The lifecycle includes start, stop, reset virtual machines, and establishing trust for virtual machines. Deploys Avaya Aura application OVAs on customer-provided Virtualized Environment and Avaya Aura Virtualized Appliance environments. Removes the Avaya Aura application OVAs that are deployed on a virtual machine. Configures application and networking parameters required for application deployments. Supports flexible footprint definition based on capacity required for the deployment of the Avaya Aura application OVA. You can deploy the OVA file on the virtual machine by using the System Manager Solution Deployment Manager and the Solution Deployment Manager client. Related links Certification validation on page 83 May 2016 Deploying Avaya Aura applications 22

Utility Services in the Avaya Aura Virtualized Appliance offer Utility Services in the Avaya Aura Virtualized Appliance offer From Avaya Aura Release 7.0, Utility Services replaces the console domain (C-dom). Utility Services runs the Services Port connection that was previously run through Dom-0 on System Platform. Therefore, Utility Services with the Services Port is a key component of the Avaya Aura Virtualized Appliance offer in Release 7.0, You must deploy Utility Services on each Appliance Virtualization Platform. With Services Port, you can connect a laptop directly to Ethernet 1 on an Avaya-supported server, and connect the laptop to any of management interface of applications that run on an Appliance Virtualization Platform host. On the S8300D and S8300E servers, Services Port is on the front plate. The Services Port virtual machine also supports ASG logins and install of a customer ASG file on to the system. By default, a generic ASG file is available on the system. The Services Port virtual machine incorporates the Serviceability Agent for alarming and log collection from System Manager. From Avaya Aura Release 7.0, Utility Services does not include IP Phone firmware. The administrator must download the latest version of the firmware from PLDS and install on Utility Services. Utility Services migration In the Avaya Aura Virtualized Appliance offer on Appliance Virtualization Platform, you require Utility Services for services static routing. Therefore, you must deploy Utility Services if Utility Services is part of the solution. In the following two use cases, you might require to deploy Utility Services. 1. Migration of Communication Manager or Session Manager on the Linux server: Utility Services is mandatory for migration of systems running on the Linux server. In this case, before you migrate, you must deploy Utility Services from VM Management. 2. Migration of Communication Manager or Session Manager on System Platform: In this case, the template already contains Utility Services. In this case, the process migrates Utility Services, and you do not require to deploy Utility Services separately. May 2016 Deploying Avaya Aura applications 23

Chapter 3: Planning and configuration Supported servers In the Avaya appliance model, the customer can deploy or upgrade to Avaya Aura Release 7.0.1 applications on the following Avaya-provided servers: Dell PowerEdge R610 2CPU MID2 HP ProLiant DL360 G7 2CPU MID4 Dell PowerEdge R620 2CPU MID3 HP ProLiant DL360p G8 Dell PowerEdge R630 HP ProLiant DL360 G9 S8300D, for Communication Manager and Branch Session Manager S8300E, for Communication Manager and Branch Session Manager Intel 1006r server. Only to deploy Utility Services and Avaya Aura Messaging OVA files. Software requirements Avaya Aura supports the following software versions: Avaya Aura Virtualized Appliance offer: Appliance Virtualization Platform 7.0.x on a customized version of VMware ESXi 5.5 Customer-provided Virtualized Environment offer: Supports the following software versions: - VMware vsphere ESXi 5.0 - VMware vsphere ESXi 5.1 - VMware vsphere ESXi 5.5 - VMware vsphere ESXi 6.0 - VMware vcenter Server 5.0 - VMware vcenter Server 5.1 - VMware vcenter Server 5.5 - VMware vcenter Server 6.0 May 2016 Deploying Avaya Aura applications 24

Software requirements To view compatibility with other solution releases, see VMware Product Interoperability Matrix at http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php. Note: Avaya Aura Release 7.0 and later does not support ESXi releases earlier than 5.0. May 2016 Deploying Avaya Aura applications 25

Chapter 4: Initial setup and connectivity 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. Procedure 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. Deployment checklist Use the following checklist for the initial deployment of Appliance Virtualization Platform, Utility Services and System Manager by using the Solution Deployment Manager client. # Action Link/Notes 1 Download the Avaya_SDMClient_win64_7.0.1.0.0 620211_43.zip file from the Avaya Support website at http:// support.avaya.com. 2 Install the Avaya_SDMClient_win64_7.0.1.0.0 620211_43.exe file. 3 From the Avaya Support website at http:// support.avaya.com, download OVA files for Utility Services and System Manager, and Release 7.0.1 feature pack files for Utility Services, System Manager, and Appliance Virtualization Platform. Perform the task if System Manager is unavailable. Installing the Solution Deployment Manager client on your computer on page 16 - Table continues May 2016 Deploying Avaya Aura applications 26

Deployment checklist # Action Link/Notes 4 Ensure that the following is accessible: Hostnames Out of Band Management considerations Network configuration data such as naming conventions, IP address, netmask and gateway 5 For Avaya Aura Virtualized Appliance deployments, install the supported server. 6 Install Appliance Virtualization Platform on the server for applications such as Communication Manager and Branch Session Manager that use S8300D or S8300E. Appliance Virtualization Platform is preinstalled on Common Release 2 and 3 servers. 7 Using the Solution Deployment Manager client, add a location. 8 Using the Solution Deployment Manager client, add the Appliance Virtualization Platform host, 192.168.13.6, to the location. 9 Deploy Utility Services OVA, and select the appropriate footprint size and the service mode. 10 Install the Utility Services 7.0.1 feature pack. 11 Using the Solution Deployment Manager client, deploy System Manager virtual machine. 12 Install the System Manager Release 7.0.1 bin file. 13 To activate the serviceability agent registration, reset the Utility Services virtual machine. 14 Verify the installation of the System Manager virtual machine. - Supported servers on page 24 Installing Appliance Virtualization Platform on page 29 Adding a location on page 36 Adding an ESXi host on page 43 While deploying OVA, provide the IP address of System Manager that you want to deploy. Deploying the Utility Services OVA file on page 64 Installing software patches on page 93 Deploying the System Manager OVA file by using the Solution Deployment Manager client on page 58 Installing service packs and software patches on System Manager by using the Solution Deployment Manager client on page 63 - Verifying the installation of System Manager on page 111 May 2016 Deploying Avaya Aura applications 27

Initial setup and connectivity Use the following checklist to deploy all other Avaya Aura applications by using the Solution Deployment Manager client or from System Manager Solution Deployment Manager. # Action Link/Notes 1 From the Avaya Support website at http:// support.avaya.com, download OVA files and feature pack files for Avaya Aura applications that you want to deploy. 2 Ensure that the following is accessible: Hostnames Out of Band Management considerations Network configuration data such as naming conventions, IP address, netmask and gateway 3 For Avaya Aura Virtualized Appliance deployments, install the supported server. 4 Install Appliance Virtualization Platform on the server for applications such as Communication Manager and Branch Session Manager that use S8300D or S8300E. Appliance Virtualization Platform is preinstalled on Common Release 2 and 3 servers. - - Supported servers on page 24 Installing Appliance Virtualization Platform on page 29 5 Add a location. Adding a location on page 36 6 Add an Appliance Virtualization Platform host as 192.168.13.6. 7 Deploy Utility Services virtual machine, and install the Release 7.0.1 feature pack. 8 Deploy Avaya Aura applications one at a time, and then install the Release 7.0.1 feature pack for each application. Adding an ESXi host on page 43 Deploying the Utility Services OVA file on page 64 Installing software patches on page 93 Deploying an OVA file for an Avaya Aura application on page 66 Installing software patches on page 93 9 Verify the installation of all applications. Post installation checklist on page 111 May 2016 Deploying Avaya Aura applications 28

Chapter 5: Preinstallation tasks Installing Appliance Virtualization Platform About this task Warning: You can obtain the root password for the Appliance Virtualization Platform system from the USB configuration file. The file must be kept secure. After installation, you must change the root password for the Appliance Virtualization Platform host to a different value with the password change option from Solution Deployment Manager. Install Appliance Virtualization Platform on one of the following servers: Dell PowerEdge R610 2CPU MID2 HP ProLiant DL360 G7 2CPU MID4 Dell PowerEdge R620 2CPU MID3 HP ProLiant DL360p G8 Dell PowerEdge R630 HP ProLiant DL360 G9 S8300D for Communication Manager S8300E for Communication Manager Release 7.0 and later does not support S8510 and S8800 servers. Before you begin Configure the USB drive. Ensure that the backup file is saved on a different server because after the Appliance Virtualization Platform installation, server restarts, and all data is lost. To use the Solution Deployment Manager client for deploying the virtual machines, install the Solution Deployment Manager client on your computer. Note: To install Appliance Virtualization Platform server while connected to the customer network, ensure that the IP address used for Appliance Virtualization Platform is not in use by another system. If the configured IP address is already in use on the network during installation, the installation process stops. You must remove the duplicate IP address, and restart the installation. May 2016 Deploying Avaya Aura applications 29

Preinstallation tasks Procedure 1. Insert the USB drive and the Appliance Virtualization Platform CD-ROM into the server. Use an external Avaya-approved USB and CD-ROM drives for installing Appliance Virtualization Platform on S8300D or S8300E. The only supported USB CD-ROM drive is Digistor DIG73322, comcode 700406267. 2. Log on to the System Platform web console, and click Server Management > Server Reboot/Shutdown > Reboot to restart the server. Warning: When the server restarts, Appliance Virtualization Platform is installed, and all existing data on the server is lost. The system installs Appliance Virtualization Platform and ejects CD-ROM. The installation process might takes about 30 minutes to complete. Note: If using a monitor, the screen changes to black before the installation is complete. A message in red text might briefly display, which is an expected behavior. Do not take any action. 3. Remove the USB drive and CD-ROM. Note: When installing Appliance Virtualization Platform on an HP server, you must remove the USB drive when the server ejects CD-ROM. Otherwise, the server might become nonoperational on reboot. If the server becomes nonoperational, remove the USB drive, and restart the server. 4. Using an SSH client, connect to the server through the eth1 services port by using the following network parameters for your system: IP address: 192.168.13.5 Netmask: 255.255.255.248 Gateway: 192.168.13.1 The SSH client must use UTF-8. Alternatively, you can connect to the public network address that was configured during the installation from a computer on the customer network. 5. Log in to Appliance Virtualization Platform as root and provide the password that is configured in the spreadsheet. The system displays the End user license agreement (EULA) screen. 6. Read the EULA, and type Y to accept the terms. You can press any key to read EULA, and use the space bar to scroll down. May 2016 Deploying Avaya Aura applications 30

Configuring servers preinstalled with Appliance Virtualization Platform Warning: Accept EULA before you deploy virtual machines. If deployments are attempted before you accept EULA, deployments fail. 7. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 8. Install the Appliance Virtualization Platform patch. For more information, see Installing the Appliance Virtualization Platform patch from Solution Deployment Manager. 9. Deploy the Utility Services virtual machine, and then all other virtual machines with the data that you noted in System Platform and Template values. For instructions to deploy Utility Services and other virtual machines, see Deploying Avaya Aura applications from System Manager. 10. From System Manager Solution Deployment Manager, install the required software patches for the virtual machines. Configuring servers preinstalled with Appliance Virtualization Platform About this task You can obtain the root password for the Appliance Virtualization Platform system from the USB configuration file. The file must be kept secure. After installation, you must change the root password for the Appliance Virtualization Platform host to a different value with the password change option from Solution Deployment Manager. For newly purchased common servers, Appliance Virtualization Platform is preinstalled. This does not apply for migration. You must configure the customer network settings through the Solution Deployment Manager client that is installed on a computer that is running Windows. The media comes with the server. The new S8300D and S8300E servers require an installation at the customer site. Note: When possible, perform the deployment from the System Manager Solution Deployment Manager. Only when System Manager is unreachable, use the Solution Deployment Manager client that is installed on the computer. Procedure 1. Turn on the server. 2. Install the Solution Deployment Manager client on the computer. May 2016 Deploying Avaya Aura applications 31

Preinstallation tasks 3. Configure the computer with the following: IP address: 192.168.13.5 Netmask: 255.255.255.248 Gateway: 192.168.13.1 4. Connect to NIC2 with a network cable. 5. Start an SSH session, log in to 192.168.13.6 as root, and type Avaya123$ as password. The system prompts to change the password immediately. 6. To change the root password, perform the following: a. At the prompt, type the current UNIX password. b. Type the new password. For more information about password rules, see Password policy. c. Type the password again. The system changes the host password. 7. Read and accept the license terms. 8. Type cd /opt/avaya/bin. Not all commands are available in the /opt/avaya/bin location, and must be run with./. For example,./nic_port. The system only runs the commands that are specified in the procedure from /opt/avaya/bin or as directed by Avaya Services. The system might get incorrectly configured if you run commands that are not specified in the procedure. Most systems do not enable Out of Band Management. Use the set_oobm command only to enable Out of Band Management for the host and all virtual machines. 9. (Optional) To enable Out of Band Management on the Appliance Virtualization Platform host, type #./set_oobm on. The system displays Host Out of Band Management set up is complete. 10. At the prompt, do the following: a. Type./serverInitialNetworkConfig. The host IP address details are mandatory. Though DNS and NTP values are optional, you must provide the values. b. At the prompt, provide the following host details: System is not in a default setup, please use SDM to change IP addresses Do you wish to setup networking? (y/n) y Please enter IP addres for the AVP host in the format x.x.x.x For example 172.16.5.1 Please enter value 172.16.107.21 Please enter subnet mask for the AVP host in the format x.x.x.x For example 255.255.255.0 Please enter value 255.255.255.0 Please enter a default gateway for the AVP host in the format x.x.x.x For example 172.16.5.254 May 2016 Deploying Avaya Aura applications 32

Configuring servers preinstalled with Appliance Virtualization Platform Please enter value 172.16.107.1 Please enter a hostname for the AVP host. For example myhost Please enter value avphost Please enter a domain for the AVP host. For example mydomain.com Please enter value mydomain.com Please enter a main DNS server for the AVP host. For example 172.16.10.54 Please enter value 172.16.107.1 Please enter a secondary DNS server for the AVP host. For example 172.16.10.54 Please enter value 172.16.107.2 Please enter a NTP server for the AVP host For example 172.16.10.55 Please enter value 172.16.107.50 Stopping ntpd watchdog-ntpd: Terminating watchdog process with PID 33560 Starting ntpd 11. To verify the vmk0 settings, type # esxcli network ip interface ipv4 get. Note: Do not change the vmk1s address. vmk1s is fixed for the services port. The system displays the following details: Name IPv4 Address IPv4 Netmask IPv4 Broadcast Address Type DHCP DNS ---- ------------- --------------- -------------- ------------ -------- vmk1 192.168.13.6 255.255.255.248 192.168.13.7 STATIC false vmk0 172.16.107.21 255.255.255.0 172.16.107.255 STATIC false 12. While connected to the services port, start the Solution Deployment Manager client. 13. Add a location. 14. Add the Appliance Virtualization Platform host as 192.168.13.6. 15. Check the version, and install the Release 7.0.1 feature pack on Appliance Virtualization Platform if required. Note: The common Release 3 servers require you to install the Appliance Virtualization PlatformRelease 7.0.1 feature pack. 16. Deploy Utility Services. 17. Deploy other Avaya Aura applications that will reside on this Appliance Virtualization Platform host. 18. Install the Release 7.0.1 patch files for all Avaya Aura applications. May 2016 Deploying Avaya Aura applications 33

Preinstallation tasks 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. Procedure 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 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. May 2016 Deploying Avaya Aura applications 34

Downloading the OVA file to System Manager 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. Downloading the OVA file to System Manager About this task You can download the software from Avaya PLDS or from an alternate source to System Manager. Use the procedure to download the OVA files to your computer and upload the file to System Manager. Before you begin Set the local software library. Procedure 1. Download the OVA file on your computer. 2. On the System Manager web console, click Services > Solution Deployment Manager. 3. In the navigation pane, click Download Management. 4. On the Download Management page, perform the following: a. In the Select Software/Hardware Types section, select the family name, and click Show Files. b. In the Select Files Download Details section, in the Source field, select My Computer. c. Click Download. The system displays the Upload File page. 5. In the Software Library field, select a local System Manager software library. 6. Complete the details for the product family, device type, and the software type. 7. Click Browse and select the OVA file from the location on the system. This system uploads the OVA file from local computer to the designated software library on System Manager. May 2016 Deploying Avaya Aura applications 35

Chapter 6: Deploying Avaya Aura applications Managing the location Viewing a location Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. Click the Locations tab. The Locations section lists all locations. 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. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, 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. May 2016 Deploying Avaya Aura applications 36

Managing the location Related links New and Edit location field descriptions on page 42 Editing the location Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. On the Location tab, in the Locations section, select a location that you want to edit. 3. Click Edit. 4. In the Edit Location section, make the required changes. 5. Click Save. Related links New and Edit location field descriptions on page 42 Deleting a location Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. On the Location tab, in the Locations section, select one or more locations that you want to delete. 3. Click Delete. 4. On the Delete confirmation dialog box, click Yes. The system does not delete the virtual machines that are running on the host, and moves the host to Unknown location host mapping > Unknown location. VM Management field descriptions Name Auto-Reload VM Management Tree The option to automatically reload the VM Management Tree after the completion of operations such as refreshing virtual machines. May 2016 Deploying Avaya Aura applications 37

Deploying Avaya Aura applications Locations Name Location Name City Country Button New Edit Delete The location name. The city where the host is located. The country where the host is located. Displays the New Location section where you can provide the details of the location that you want to add. Displays the Edit Location section where you can change the details of an existing location. Deletes the locations that you select. The system moves the hosts associated with the deleted locations to unknown location. Hosts Name Host Name Host IP Host FQDN vcenter IP/FQDN Current Action Last Action License Status Host Version Offer Type SSH Status The name of the ESXi host. The IP address of the ESXi host. FQDN of the ESXi host. The IP address or FQDN of vcentre. The operation that is currently being performed on the ESXi host. The last completed operation on the ESXi host. The status of the license. The ESXi host version. The options are 5.5, 5.1, and 5.0. 6.0 only for VMware ESXi host. The ESXi host type. The options are: AVP: Appliance Virtualization Platform host Customer VE: customer-provided VMware ESXi host The SSH service status. The values are: enabled disabled Table continues May 2016 Deploying Avaya Aura applications 38

Managing the location Name Host Certificate vcenter Certificate The certificate status of the Appliance Virtualization Platform host. The values are: : The certificate is added in Solution Deployment Manager and correct. : The certificate is not accepted or invalid. You can click View for details of the certificate status. The certificate status of the ESXi host. The values are: : The certificate is correct. The system enables all the options in More Actions that apply to VMware ESXi host. : The certificate is not accepted or invalid. You can click View for details of the certificate status. Note: Depending on the Appliance Virtualization Platform host and vcenter certificate status, the system enables the options in More Actions. Button Auto Refresh Add Edit Remove Change Network Params > Change Host IP Settings The option to automatically refresh the page with the latest changes. For example, the page updates: The VM state when a virtual machine changes The license status or certificate status of host when host changes The system refreshes the data every minute. Displays the New Host section where you can provide the details of the host that you want to add. Displays the Host Information section where you can change the details of an existing host. Removes the hosts that you select. The system moves the hosts associated with the deleted locations to unknown location. Displays the Host Network/IP Settings section where you can change the host IP settings for the Appliance Virtualization Platform host. Table continues May 2016 Deploying Avaya Aura applications 39

Deploying Avaya Aura applications Button Change Network Params > Change Network Settings Refresh More Actions > Change Password More Actions > Update More Actions > Enable SSH More Actions > Disable SSH More Actions > Host Restart More Actions > Host Shutdown More Actions > Generate/Accept Certificate Displays the Host Network Setting section where you can change the network settings for the Appliance Virtualization Platform host. Refreshes the status of the hosts. Displays the Change Password section where you can change the password for the Appliance Virtualization Platform host. Displays the Update host page where you can select the file for updating the Appliance Virtualization Platform host. Enables SSH for the Appliance Virtualization Platform host. When SSH for the Appliance Virtualization Platform host is enabled, the system displays SSH enabled successfully. Disables SSH on the Appliance Virtualization Platform host. When SSH for Appliance Virtualization Platform is disabled, the system displays Disabling SSH for AVP host with <IP address> <FQDN>, <username>. Restarts the host and virtual machines that are running on the Appliance Virtualization Platform host. Shuts down the host and virtual machines that are running on the Appliance Virtualization Platform host. Displays the Certificate dialog box where you can manage certificates for the host. Depending on the host type, the options are: Generate Certificate: To generate certificate for Appliance Virtualization Platform host only. Accept Certificate: To accept a valid certificate for the host or vcenter. Decline Certificate: To decline the certificate for Appliance Virtualization Platform host only. You must regenerate the certificate and accept if you decline a host certificate. Virtual Machines Name VM Name The name of the virtual machine. Table continues May 2016 Deploying Avaya Aura applications 40

Managing the location Name VM IP VM FQDN VM App Name VM App Version VM State Current Action Status Last Action Host Name Trust Status Data Store Button New Edit Delete Start Stop Show Selected The IP address of the virtual machine. FQDN of the virtual machine. The name of the application virtual machine. For example, Session Manager. The version of the application virtual machine. For example, 7.0.0.0. The state of the virtual machine. The states are Started and Stopped. The status of the current operation. The statuses are: Deploying Starting Stopping The Status Details link provides the details of the operation in progress. The last action performed on the virtual machine. The hostname of the VMware host or Appliance Virtualization Platform host The status of the connection between System Manager and the virtual machine. The status can be Success or Failed. When the connection between System Manager and the virtual machine establishes, Trust Status changes to Success. Only when the trust status is Success, you can perform other operations. The data store with the available size. Displays the VM Deployment section where you can provide the host and deploy an application. Displays the VM Deployment section where you can change the details of a virtual machine. Turns off the virtual machines and deletes the selected virtual machines. Starts the selected virtual machines. Stops the selected virtual machines. Displays only the selected virtual machines. Table continues May 2016 Deploying Avaya Aura applications 41

Deploying Avaya Aura applications Button More Actions > Restart More Actions > Refresh VM More Actions > Reestablish Connection More Actions > Update Static Routing Starts the selected virtual machines that were stopped earlier. Updates the status of the virtual machines. Establishes the connection between System Manager and the virtual machine. When the connection between System Manager and the virtual machine establishes, the Trust Status changes to Success. Displays the VM Update Static Routing section where you can update the IP address of Utility Services for static routing. New and Edit location field descriptions Required Location Information Name Name Avaya Sold-To # Address City State/Province/Region Zip/Postal Code Country The location name. The customer contact number. Administrators use the field to check entitlements. The address where the host is located. The city where the host is located. The state, province, or region where the host is located. The zip code of the host location. The country where the host is located. Optional Location Information Name Default Gateway DNS Search List DNS Server 1 DNS Server 2 NetMask NTP Server The IP address of the virtual machine gateway. For example, 172.16.1.1. The search list of domain names. The DNS IP address of the primary virtual machine. For example, 172.16.1.2. The DNS IP address of the secondary virtual machine. For example, 172.16.1.4. The subnetwork mask of the virtual machine. The IP address or FQDN of the NTP server. Separate the IP addresses with commas (,). May 2016 Deploying Avaya Aura applications 42

Managing the host Button Save Edit Delete Cancel Saves the location information and returns to the Locations section. Updates the location information and returns to the Locations section. Deletes the location information, and moves the host to the Unknown location section. Cancels the add or edit operation, and returns to the Locations section. Managing the host 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. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In VM Management Tree, select a location. 3. On the Host tab, in the Hosts for Selected Location <location name> section, click New. 4. In the New Host section, provide the following: 5. Click Save. Host name, IP address, user name, and password. 6. On the Certificate dialog box, click Accept Certificate. The system generates the certificate and adds the Appliance Virtualization Platform host. For the ESXi host, you can only accept the certificate. If the certificate is invalid, to generate certificate, see the VMware documentation. In the VM Management Tree section, the system displays the new host in the specified location. The system also discovers applications. May 2016 Deploying Avaya Aura applications 43

Deploying Avaya Aura applications 7. To view the discovered application details, such as name and version, establish trust between the application and System Manager using the following: a. Click More Actions > Re-establish connection. b. Click Refresh VM. Important: When you change the IP address or FQDN of the Appliance Virtualization Platform host from the local inventory, you require Utility Services. To get the Utility Services application name during the IP address or FQDN change, refresh Utility Services to ensure that Utility Services is available. Related links New and Edit host field descriptions on page 55 Generating and accepting certificates on page 84 Editing an ESXi host Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In VM Management Tree, select a location. 3. On the Host tab, in the Hosts for Selected Location <location name> section, select an ESXi host that you want to update. 4. Change the ESXi host information. 5. Click Save. The system updates the ESXi host information. Related links New and Edit host field descriptions on page 55 Installing the Appliance Virtualization Platform patch from Solution Deployment Manager About this task Install the Release 7.0.1 feature pack on the existing Appliance Virtualization Platform Release 7.0 by using the Solution Deployment Manager client or System Manager Solution Deployment Manager. May 2016 Deploying Avaya Aura applications 44

Managing the host Note: From System Manager Solution Deployment Manager, you cannot update an Appliance Virtualization Platform that hosts this System Manager. Do not use this procedure for installing the Appliance Virtualization Platform patch on an S8300D server. Before you begin 1. Add a location. 2. Add a host. 3. Enable the SSH service on the Appliance Virtualization Platform host. 4. Stop all virtual machines that are running on the Appliance Virtualization Platform host. Note: Install only Avaya-approved service packs or software patches on Appliance Virtualization Platform. Do not install the software patches that are downloaded directly from VMware. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In VM Management Tree, select a location. 3. On the Host tab, in the Hosts for Selected Location <location name> section, select the Appliance Virtualization Platform host, and click More Actions > Update. 4. On the Update Host page, click Select patch from local SDM client machine. 5. In Select patch file, provide the absolute path to the patch file of the host, and click Update Host. For example, the absolute path on your computer can be /tmp/avp/avayaavp-7.0.0.1.0.5.zip. In the Hosts for Selected Location <location name> section, the system displays the update status in the Current Action column. 6. To view the details, in the Current Action column, click Patching. Next steps Host Patching Status window displays the details. The patch installation takes some time. When the patch installation is complete, the Current Action column displays the status. If virtual machines that were running on the Appliance Virtualization Platform host does not automatically start, manually start the machines. Related links Update field descriptions on page 58 May 2016 Deploying Avaya Aura applications 45

Deploying Avaya Aura applications Changing the network parameters for an Appliance Virtualization Platform host About this task Use this procedure to change the network parameters of Appliance Virtualization Platform after deployment. You can change network parameters only for the Appliance Virtualization Platform host. Note: If you are connecting to Appliance Virtualization Platform through the public management interface, you might lose connection during the process. Therefore, after the IP address changes, close Solution Deployment Manager, and restart Solution Deployment Manager by using the new IP address to reconnect. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In VM Management Tree, select a location. 3. On the Host tab, in the Hosts for Selected Location <location name> section, select an ESXi host and click Change Network Params > Change Host IP Settings. 4. In the Host Network/ IP Settings section, change the IP address, subnetmask, and other parameters as appropriate. 5. To change the gateway IP address, perform the following: a. Click Change Gateway. The Gateway field becomes available for providing the IP address. b. In Gateway, change the IP address. c. Click Save Gateway. 6. Click Save. The system updates the Appliance Virtualization Platform host information. Related links Change Network Parameters field descriptions on page 55 May 2016 Deploying Avaya Aura applications 46

Managing the host Changing the network settings for an Appliance Virtualization Platform host from Solution Deployment Manager About this task With Appliance Virtualization Platform, you can team NICs together to provide a backup connection when the server NIC or the Ethernet switch fails. You can also perform NIC teaming from the command line on Appliance Virtualization Platform. Appliance Virtualization Platform supports Active-Standby and Active-Active modes of NIC teaming. For more information, see NIC teaming modes. Note: If you add a host with service port IP address in Solution Deployment Manager and change the IP address of the host to the public IP address by using Host Network/ IP Settings, the system updates the public IP address in the database. Any further operations that you perform on the host fails because public IP address cannot be reached with the service port. To avoid this error, edit the host with the service port IP address again. If FQDN of the Appliance Virtualization Platform host is updated by using Host Network/IP setting for domain name, refresh the host to get the FQDN changes reflect in Solution Deployment Manager. Use this procedure to change network settings, such as changing VLAN ID, NIC speed, and NIC team and unteaming for an Appliance Virtualization Platform host. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In VM Management Tree, select a location. 3. On the Host tab, in the Host for Selected Location <location name>, select an Appliance Virtualization Platform host. May 2016 Deploying Avaya Aura applications 47

Deploying Avaya Aura applications 4. Click Change Network params > Change Network Settings. The Host Network/ IP Settings page displays the number of switches as 4. You can configure port groups for the following switches: vswitch0, reserved for the Public and Management traffic. vswitch1, reserved for services port. You cannot change the values. vswitch2, reserved for Out of Band Management. vswitch3. No reservations. 5. To change VLAN ID, perform the following: a. To expand the Standard Switch: vswitch<n> section, click. The section displays the vswitch details. b. Click on the VLANID link or the edit icon ( ). The system displays the Port Group Properties page where you can edit the VLAN ID port group property. c. In VLAN ID, select an ID from the available values. For more information about the value, see NIC teaming. d. Click OK. The system displays the new VLAN ID. Note: You can change the services port VLAN ID for S8300D servers only through Solution Deployment Manager. May 2016 Deploying Avaya Aura applications 48

Managing the host 6. To change the NIC speed, perform the following: a. Ensure that the system displays a vmnic in the NIC Name column. b. Click Change NIC speed. The system displays the selected vmnic dialog box. c. In Configured speed, Duplex, click a value. d. Click OK. For more information, see VLAN ID assignment. The system displays the updated NIC speed in the Speed column. If the NIC is connected, the system displays in Link Status. Note: You can change the speed only for common servers. You cannot change the speed for S8300D and S8300E servers. 7. To change the NIC teaming, perform the following: a. Select a vmnic. b. Click NIC team/unteam. The system displays the Out of Band Management Properties page. c. To perform NIC teaming or unteaming, select the vmnic and click Move Up or Move Down to move the vmnic from Active Adapters, Standby Adapters, or Unused Adapters. For more information, see NIC teaming modes. d. Click OK. The vmnic teams or unteams with Active Adapters, Standby Adapters, or Unused Adapters as required. e. To check the status of the vmnic, click NIC team/ unteam. 8. To get the latest data on host network IP settings, click Refresh. The system displays the current status of the vmnic. Note: You cannot perform NIC teaming for S8300D and S8300E servers. Related links Host Network / IP Settings field descriptions on page 56 May 2016 Deploying Avaya Aura applications 49

Deploying Avaya Aura applications Changing the password for an Appliance Virtualization Platform host About this task You can change the password only for the Appliance Virtualization Platform host. This is the password for the user that you provide when adding the Appliance Virtualization Platform host. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In VM Management Tree, select a location. 3. On the Host tab, in the Hosts for Selected Location <location name> section, select an ESXi host and click More Actions > Change Password. 4. In the Change Password section, enter the current password and the new password. For more information about password rules, see Password policy. 5. Click Change Password. The system updates the password of the Appliance Virtualization Platform host. Related links Password policy on page 50 Change Password field descriptions on page 57 Password policy The password must meet the following requirements: Must contain at least eight characters. Must contain at least one of each: an uppercase letter, a lowercase letter, a numerical, and a special character. Must not contain an uppercase letter at the beginning and a digit or a special character at the end. Examples of invalid passwords: Password1: Invalid. Uppercase in the beginning and a digit at the end. Password1!: Uppercase in the beginning and a special character at the end. Example of a valid password: mypassword!1ok If the password does not meet the requirements, the system prompts you to enter a new password. Enter the existing password and the new password in the correct fields. Ensure that you keep the root password safe. You need the password while adding the host to Solution Deployment Manager and for troubleshooting. May 2016 Deploying Avaya Aura applications 50

Managing the host Related links Changing the password for an Appliance Virtualization Platform host on page 50 Enabling and disabling SSH on Appliance Virtualization Platform from Solution Deployment Manager About this task For security purpose, SSH access to Appliance Virtualization Platform shuts down in the normal operation. You must enable the SSH service on Appliance Virtualization Platform from Solution Deployment Manager. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In VM Management Tree, select a location. 3. Select an Appliance Virtualization Platform host. 4. To enable SSH, click More Actions > Enable SSH. The system displays enabled in the SSH status column. 5. To disable SSH, click More Actions > Disable SSH. The system displays disabled in the SSH status column. Enabling and disabling SSH on Appliance Virtualization Platform from System Manager CLI About this task For security purpose, SSH access to Appliance Virtualization Platform shuts down in the normal operation. You must enable the SSH service on Appliance Virtualization Platform. You can enable SSH, disable SSH, and check the SSH status on the Appliance Virtualization Platform host. Before you begin Start an SSH session. Procedure 1. Log in to the System Manager command line interface as root. 2. Navigate to the $MGMT_HOME/infra/bin/avpSSHUtility location. 3. Type./enableDisableSSHOnAVP.sh. May 2016 Deploying Avaya Aura applications 51

Deploying Avaya Aura applications The system displays the following options: Enable SSH on the Appliance Virtualization Platform host. Disable SSH on the Appliance Virtualization Platform host. Check the SSH status on the Appliance Virtualization Platform host. 4. To enable SSH, perform the following: a. At the prompt, type 1 and press Enter. b. Type the IP address of the Appliance Virtualization Platform host. c. Type the time in minutes. The time is the duration after which the system blocks any new SSH connections. The valid range 10 to 120 minutes. The system displays the message and enables SSH on Appliance Virtualization Platform host. For example, if you set the time to 50 minutes, after 50 minutes, the system blocks any new SSH connections. If you reenable SSH before completion of 50 minutes, the system adds 50 minutes to the initial 50 minutes to reenable connections. 5. To disable SSH, perform the following: a. At the prompt, type 2 and press Enter. b. Type the IP address of the Appliance Virtualization Platform host. If SSH is already disabled, the system displays False and the message SSH is already disabled. No operation performed. Exiting. 6. (Optional) To view the status of SSH, perform the following: a. At the prompt, type 3 and press Enter. b. Type the IP address of the Appliance Virtualization Platform host. If SSH is enabled, the system displays Is SSH enable false. If SSH is disabled, the system displays Is SSH disable true. Changing the IP address and default gateway of the host About this task When you change the default gateway and IP address from the vsphere, the change might be unsuccessful. You cannot remotely change the IP address of the Appliance Virtualization Platform host to a different network. You can change the IP address remotely only within the same network. To change the Appliance Virtualization Platform host to a different network, perform Step 2 or Step 3. May 2016 Deploying Avaya Aura applications 52

Managing the host Before you begin Connect the computer to the services port. Procedure 1. Using an SSH client, log in to the Appliance Virtualization Platform host. 2. Connect the Solution Deployment Manager client to services port on the Appliance Virtualization Platform host, and do the following: a. To change the IP address, at the command prompt of the host, type the following: esxcli network ip interface ipv4 set -i vmk0 -I <old IP address of the host> - N <new IP address of the host> -t static For example: esxcli network ip interface ipv4 set -i vmk0 -I 135.27.162.121 -N 255.255.25 5.0 -t static b. To change the default gateway, type esxcfg-route <new gateway IP address>. For example: esxcfg-route 135.27.162.1 3. Enable SSH on the Appliance Virtualization Platform host and run the./ serverinitialnetworkconfig command. For more information, see Configuring servers preinstalled with Appliance Virtualization Platform. Shutting down the Appliance Virtualization Platform host About this task You can perform the shutdown operation on one Appliance Virtualization Platform host at a time. You cannot schedule the operation. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In VM Management Tree, select a location. 3. On the Host tab, in the Host for Selected Location <location name>, select an Appliance Virtualization Platform host. 4. Click More Actions > Host Shutdown. The Appliance Virtualization Platform host and virtual machines shut down. May 2016 Deploying Avaya Aura applications 53

Deploying Avaya Aura applications Restarting the Appliance Virtualization Platform host Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In VM Management Tree, select a location. 3. On the Host tab, in the Host for Selected Location <location name>, select an Appliance Virtualization Platform host. 4. Click More Actions > Host Restart. The system restarts the Appliance Virtualization Platform host and virtual machines. Deleting an ESXi host Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. On the Host tab, in the Hosts for Selected Location <location name> section, select one or more hosts that you want to delete. 3. Click Delete. 4. On the Delete confirmation page, click Yes. Mapping the ESXi host to an unknown location About this task When you delete a location, the system does not delete the virtual machines running on the host, and moves the host to Unknown location host mapping > Unknown location. You can configure the location of an ESXi host again. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In the left navigation pane, click the Unknown location host mapping link. 3. In the Host Location Mapping section, select an ESXi host and click Edit. The system displays the Host Information page. 4. Select a location to which you want to map the ESXi host. 5. Click Submit. May 2016 Deploying Avaya Aura applications 54

Managing the host The system displays the ESXi host in the selected location. New and Edit host field descriptions Name Location Host Name Host FQDN or IP User Name Password Button Save The location where the host is availabe. The field is read only. The hostname of Appliance Virtualization Platform or the ESXi host. For example, smgrdev. The IP address or FQDN of Appliance Virtualization Platform or the ESXi host. The user name to log in to Appliance Virtualization Platform or the ESXi host. Note: For Appliance Virtualization Platform, provide the root login and password that you configured in the spreadsheet. The password to log in to Appliance Virtualization Platform or the ESXi host. Saves the host information and returns to the Hosts for Selected Location <location name> section. Change Network Parameters field descriptions Network Parameters Name Name IP Subnet Mask Host Name Domain Name Preferred DNS Server The name of the Appliance Virtualization Platform host. The field is display-only. The IP address of the Appliance Virtualization Platform host The subnet mask the Appliance Virtualization Platform host The host name the Appliance Virtualization Platform host The domain name the Appliance Virtualization Platform host The preferred DNS server Table continues May 2016 Deploying Avaya Aura applications 55

Deploying Avaya Aura applications Name Alternate DNS Server Gateway Button Change Gateway Save Gateway Cancel Gateway Change Button Save The alternate DNS server The gateway IP address. The field is available only when you click Change Gateway. Makes the Gateway field available, and displays Save Gateway and Cancel Gateway Change buttons. Saves the gateway IP address value that you provide. Cancels the changes made to the gateway. Saves the changes that you made to network parameters. Host Network / IP Settings field descriptions Port Groups Standard Switch vswitch <n> displays the Port Groups and NICs sections. Name or VLAN ID link VLAN ID OK NIC speed Button Change NIC speed Name Configured speed, Duplex Displays the Port Group Properties page where you configure VLAN ID. Displays the VLAN ID. The options are: None (0) 1 to 4093 The field displays only unused IDs. Saves the changes. Displays the vmnic<n> dialog box. Displays the NIC speed. The options are: Autonegotiate Table continues May 2016 Deploying Avaya Aura applications 56

Managing the host Name 10,Half 10,Full 100,Half 100,Full 1000,Full OK Saves the changes. NIC teaming Button NIC team/unteam Button Move Up Move Down Refresh OK Displays the Out of Band Management Properties vswitch<n> dialog box. Moves the VMNIC from unused adapters to standby or active adapters or from standby to active adapter. Moves the VMNIC from active to standby adapter or from standby to unused adapter. Refreshes the page. Saves the changes. Change Password field descriptions Name Current Password New Password Confirm New Password Button Change Password The password for the user you input when adding the host. The new password The new password Saves the new password. May 2016 Deploying Avaya Aura applications 57

Deploying Avaya Aura applications Update field descriptions Name Patch location Select patch file Button Update Host The location where the Appliance Virtualization Platform patch is available. The options are: Select Patch from Local SMGR: To use the Appliance Virtualization Platform patch that is available on the local System Manager. Select Patch from software library: To use the Appliance Virtualization Platform patch that is available in the software library. The absolute path to the Appliance Virtualization Platform patch file. Installs the patch on the Appliance Virtualization Platform host. Managing the virtual machine Deploying the System Manager OVA file by using the Solution Deployment Manager client About this task Use the procedure to create a virtual machine on Appliance Virtualization Platform or ESXi host, and deploy OVA for System Manager virtual machine by using the Solution Deployment Manager client. Before you begin Install the Solution Deployment Manager client on your computer. Add a location. Add Appliance Virtualization Platform or an ESXi host to the location. Deploy Utility Services. Procedure 1. To start the Solution Deployment Manager client, click Start > All Programs > Avaya > Avaya SDM Client or the SDM icon ( 2. In VM Management Tree, select a host. ) on the desktop. May 2016 Deploying Avaya Aura applications 58

Managing the virtual machine 3. On the Virtual Machines tab, in the VMs for Selected Location <location name> section, click New. The system displays the VM Deployment section. 4. In the Select Location and Host section, do the following: a. In Select Location, select a location. b. In Select Host, select a host. c. In Host FQDN, type the virtual machine name. 5. In Data Store, select a data store. The page displays the capacity details. 6. Click Next. 7. In the Deploy OVA section, do the following: a. In Select Software Library, select the local or remote library where the OVA file is available. To deploy the OVA by using the Solution Deployment Manager client, you can use the default software library that is set during the client installation. b. In Select OVAs, select the OVA file that you want to deploy. c. In Flexi Footprint, select one of the following: 8. Click Next. SMGR Profile 2 Max User 250K: To support 250000 users. This configuration requires 6 vcpus and 12 GB memory. SMGR Profile 1 Max User 35K: To support 35000 users. This configuration requires 4 vcpus and 9 GB memory. In Configuration Parameters and Network Parameters sections, the system displays the fields that are specific to the application that you deploy. 9. In the Network Parameters section, ensure that page displays the following preconfigured fields: Public Out of Band Management: When Out of Band Management is enabled. 10. In the Configuration Parameters section, complete the fields. For more information, see VM Deployment field descriptions. For each application that you deploy, fill the appropriate fields. 11. Click Deploy. 12. Click Accept the license terms. In the Hosts for Selected Location <location name> section, the system displays the deployment status in the Current Action Status column. May 2016 Deploying Avaya Aura applications 59

Deploying Avaya Aura applications The system displays the virtual machine on the VMs for Selected Location <location name> page. 13. To view details, click the Status Details link. Next steps Install the System Manager Release 7.0.1 patch file. Update the user password for the system to synchronize the data from applications. When System Manager is operational, you can use Solution Deployment Manager from System Manager to deploy all other Avaya Aura applications or continue to use the Solution Deployment Manager client. Related links Uploading a file to the software library on page 34 VM Deployment field descriptions on page 60 VM Deployment field descriptions Select Location and Host Name Select Location Select Host Host FQDN VM Name ME Deployment The location name. The field is display-only. The hostname of the Appliance Virtualization Platform that you must select. For example, smgrdev. FQDN of the Appliance Virtualization Platform host. The field is display-only. The name of the virtual machine. The option to perform the Midsize Enterprise deployment. The option is available only while deploying Communication Manager simplex OVA. Deploy OVA Name Provide OVA path Select OVA File The option to specify the location from where you can get the OVA file. The absolute path to the.ova file of the virtual machine that you must provide. For example, C: \Program Files\SDM\smgr_7.ova The field is available only when you click Provide OVA path. Table continues May 2016 Deploying Avaya Aura applications 60

Managing the virtual machine Name Submit OVA from SW Library Software Library File Name Select Flexi Footprint Selects the.ova file of the virtual machine that you want to deploy. The field is available only when you click Provide OVA path. The option to specify the software library where the OVA file is saved. The default path provided during the installation of the Solution Deployment Manager client. The default path is C:\Program Files\Avaya\SDMClient \Default_Artifacts. The field is available only when you click OVA from SW Library The.ova file that you want to deploy. The field is available only when you click OVA from SW Library. The footprint size supported for the selected host. The options are: System Manager Profile 2 Max User 250K: To support 250000 users. This configuration requires 6 vcpus and 12 GB memory. System Manager Profile 1 Max User 35K: To support 35000 users. This configuration requires 4 vcpus and 9 GB memory. Configuration Parameters Important: The system populates most of the fields depending on the OVA file. Ensure that the required memory is available for the footprint sizes that you selected. The upgrade operation might fail due to insufficient memory. Name Management IP Address (Out of Band Management IP Address) Management Netmask The IP address of the System Manager virtual machine for out of band management. The field is optional network interface to isolate management traffic on a separate interface from the inbound signaling network. The Out of Band Management subnetwork mask to assign to the System Manager virtual machine. Table continues May 2016 Deploying Avaya Aura applications 61

Deploying Avaya Aura applications Name Management Gateway IP Address of DNS Server Management Hostname Default Search List NTP Server IP or FQDN Time Zone The gateway IP address to assign to the System Manager virtual machine. For example, 172.16.1.1. The DNS IP addresses to assign to the primary, secondary, and other System Manager virtual machines. Separate the IP addresses with commas (,). For example, 172.16.1.2, 172.16.1.4. The hostname to assign to the System Manager virtual machine. For example, bouldervm2. The search list of domain names. The field is optional. The IP address or FQDN of the NTP server. The field is optional. Separate the IP addresses with commas (,). The timezone where the System Manager virtual machine is located. A list is available where you select the name of the continent and the name of the country. Network Parameters Name Public Out of Band Management The port number that is mapped to public port group. You must configure Public network configuration parameters only when you configure Out of Band Management. Otherwise, Public network configuration is optional. The port number that is mapped to the out of band management port group. Virtual FQDN Name Virtual Hostname Virtual Domain The virtual hostname of the System Manager virtual machine. For example, grsmgr. The virtual domain name of the System Manager virtual machine. For example, dev.com. SNMPv3 Parameters Name SNMPv3 User Name Prefix SNMPv3 User Authentication Protocol Password The prefix for SNMPv3 user. The password for SNMPv3 user authentication. Table continues May 2016 Deploying Avaya Aura applications 62

Managing the virtual machine Name Confirm Password SNMPv3 User Privacy Protocol Password Confirm Password The password that you retype to confirm the SNMPv3 user authentication protocol. The password for SNMPv3 user privacy. The password that you must provide to confirm the SNMPv3 user privacy protocol. Public Network Settings Name Public IP Address Public Netmask Public Gateway Public Hostname Button Deploy The IP address to enable public access to different interfaces. The subnetwork mask to assign to System Manager virtual machine. The gateway IP address to assign to the System Manager virtual machine. For example, 172.16.1.1. The hostname to assign to the System Manager virtual machine. For example, bouldervm2. Displays the EULA acceptance screen where you must click Accept to start the deployment process. Installing service packs and software patches on System Manager by using the Solution Deployment Manager client About this task Use the procedure to install service packs, feature packs, or software patches on System Manager by using Solution Deployment Manager client. Before you begin Install the Solution Deployment Manager client. Procedure 1. To start the Solution Deployment Manager client, click Start > All Programs > Avaya > Avaya SDM Client or the SDM icon ( 2. Click VM Management. 3. In VM Management Tree, select a location. ) on the desktop. 4. On the Virtual Machines tab, in the VMs for Selected Location <location name> section, select System Manager on which you want to install the patch. May 2016 Deploying Avaya Aura applications 63

Deploying Avaya Aura applications 5. (Optional) If updating from a different client, perform the following: a. Click More Actions > Re-establish connection. b. Click on Refresh VM. c. To view the status, in the Current Action column, click Status Details. d. Proceed with the next step. 6. Click More Actions > Update VM. The system displays the System Manager Update dialog box. 7. In Select bin file from Local SDM Client, provide the absolute path to the software patch or service pack. Note: The absolute path is the path on the computer on which the Solution Deployment Manager client is running. The patch is uploaded to System Manager. 8. (Optional) Click the Auto commit the patch check box. 9. Click Install. In the VMs for Selected Location <location name> section, the system displays the status. 10. To view the details, in the Current Action column, click Status Details. SMGR Patching Status window displays the details. The system displays the Installed Patches page. The patch installation takes some time. 11. On the Installed Patches page, perform the following: a. In Action to be performed, click Commit. The system installs the patch, service pack or feature pack that you selected. b. Click Get Info. c. Select the patch, service pack or feature pack, and click Commit. Managing the virtual machine Deploying the Utility Services OVA file About this task Use the procedure to create a virtual machine on the ESXi host, and deploy Utility Services OVA on the Avaya-provided server. To deploy Utility Services, you can use Solution Deployment Manager from System Manager or the Solution Deployment Manager client, when System Manager is unavailable. Deploy Utility Services first, install the Release 7.0.1 feature pack, and then deploy all other applications one at a time. May 2016 Deploying Avaya Aura applications 64

Managing the virtual machine Before you begin Complete the deployment checklist. For information about the deployment checklist, see Deploying Avaya Aura applications from System Manager. Add a location. Add Appliance Virtualization Platform or an ESXi host to the location. Download the required OVA file to System Manager. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In VM Management Tree, select a host. 3. On the Virtual Machines tab, in the VMs for Selected Location <location name> section, click New. The system displays the VM Deployment section. 4. In the Select Location and Host section, do the following: a. In Select Location, select a location. b. In Select Host, select a host. c. In Host FQDN, type the virtual machine name. 5. In Data Store, select a data store. The page displays the capacity details. 6. Click Next. 7. In the Deploy OVA section, perform the following: a. In Select Software Library, select the local or remote library where the OVA file is available. If you are deploying the OVA from the Solution Deployment Manager client, you can use the default software library that is set during the client installation. b. In Select OVAs, select the OVA file that you want to deploy. c. In Flexi Footprint, select the footprint size that the application supports. 8. Click Next. S8300D: Due to the limited resources available on S8300D, the only footprint option is minimal Default: For all other server platforms. In Configuration Parameters and Network Parameters sections, the system displays the fields that are specific to the application that you deploy. May 2016 Deploying Avaya Aura applications 65

Deploying Avaya Aura applications 9. In the Network Parameters section, ensure that the following fields are preconfigured: Public Services: Only for Utility Services Duplicate Link: Only for duplex Communication Manager Out of Band Management: Only if Out of Band Management is enabled For more information, see VM Deployment field descriptions. 10. In the Configuration Parameters section, complete the fields. For more information about Configuration Parameters, see Network Parameters and Configuration Parameters field descriptions. 11. Click Deploy. 12. Click Accept the license terms. In the Hosts for Selected Location <location name> section, the system displays the deployment status in the Current Action Status column. The system displays the virtual machine on the VMs for Selected Location <location name> page. 13. To view details, click the Status Details link. For information about VM Management field descriptions, see Deploying Avaya Aura applications from System Manager. 14. Install the Release 7.0.1 feature pack. 15. Reboot the Utility Services virtual machine. Next steps 1. Deploy System Manager and install the Release 7.0.1 feature pack. 2. To activate the serviceability agent registration, reset the Utility Services virtual machine. 3. Deploy all other Avaya Aura applications one at a time. Related links VM Deployment field descriptions on page 73 Network Parameters and Configuration Parameters field descriptions VM Deployment field descriptions on page 73 Network Parameters and Configuration Parameters field descriptions Deploying an OVA file for an Avaya Aura application About this task Use the procedure to create a virtual machine on the ESXi host, and deploy OVA for an Avaya Aura application on the virtual machine. May 2016 Deploying Avaya Aura applications 66

Managing the virtual machine To deploy an Avaya Aura application, you can use Solution Deployment Manager from System Manager or the Solution Deployment Manager client if System Manager is unavailable. Deploy Utility Services first, and then deploy all other applications one at a time. Before you begin Add a location. Add Appliance Virtualization Platform or an ESXi host to the location. Ensure that the certificate is valid on the Appliance Virtualization Platform host or vcentre if used. Download the required OVA file to System Manager. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In VM Management Tree, select a host. 3. On the Virtual Machines tab, in the VMs for Selected Location <location name> section, click New. The system displays the VM Deployment section. 4. In the Select Location and Host section, do the following: a. In Select Location, select a location. b. In Select Host, select a host. c. In Host FQDN, type the virtual machine name. 5. In Data Store, select a data store. The page displays the capacity details. 6. Click Next. 7. In the Deploy OVA section, do the following: a. In Select Software Library, select the local or remote library where the OVA file is available. To deploy the OVA by using the Solution Deployment Manager client, you can use the default software library that is set during the client installation. b. In Select OVAs, select the OVA file that you want to deploy. c. In Flexi Footprint, select the footprint size that the application supports. 8. Click Next. In Configuration Parameters and Network Parameters sections, the system displays the fields that are specific to the application that you deploy. 9. In the Network Parameters section, ensure that the following fields are preconfigured: Public May 2016 Deploying Avaya Aura applications 67

Deploying Avaya Aura applications Services: Only for Utility Services Duplicate Link: Only for duplex Communication Manager Out of Band Management: Only if Out of Band Management is enabled For more information, see VM Deployment field descriptions. 10. In the Configuration Parameters section, complete the fields. For each application that you deploy, fill the appropriate fields. For more information, see VM Deployment field descriptions. 11. Click Deploy. 12. Click Accept the license terms. In the Hosts for Selected Location <location name> section, the system displays the deployment status in the Current Action Status column. The system displays the virtual machine on the VMs for Selected Location <location name> page. 13. To view details, click Status Details. Next steps Install the Release 7.0.1 patch file for the Avaya Aura application. Perform the following: 1. From the Manage Elements link on System Manager, update the username password. 2. Before the synchronization and after deployment, add an SMNP profile on Communication Manager. Note: If you fail to update the password, the synchronization operation fails. Related links Installing software patches on page 93 VM Deployment field descriptions on page 73 Editing a virtual machine Before you begin Install the Solution Deployment Manager client. An ESXi host must be available. When you change the IP address or FQDN: - Utility Services must be available and must be discovered. May 2016 Deploying Avaya Aura applications 68

Managing the virtual machine - If Utility Services is discovered, the system must display Utility Services in the VM App Name column. If the application name in VM App Name is empty, perform the following to establish trust between the application and System Manager: Procedure Click More Actions > Re-establish connection. Click More Actions > Refresh VM. 1. To start the Solution Deployment Manager client, click Start > All Programs > Avaya > Avaya SDM Client or the SDM icon ( 2. In VM Management Tree, select a location. ) on the desktop. 3. On the Virtual Machines tab, in the VMs for Selected Location <location name> section, select a virtual machine, and click Edit. The system displays the Edit VMs section. 4. (Optional) Click Change Flexi Footprint and do the following: a. Click Change flexi foot print value. b. In Flexi Footprint, select a foot print that the application supports. Important: Each application must ensure that only the supported flexible footprint is selected. 5. To update the IP address and FQDN of the virtual machine, perform the following: a. Click More Actions > Re-establish connection. Note: To update IP address or FQDN for Utility Services, establish trust on all virtual machines that are running on the host on which Utility Services resides. b. Click More Actions > Refresh VM. Note: To update IP address or FQDN for Utility Services, refresh all virtual machines that are running on the host on which Utility Services resides. c. Click Update IP/FQDN in Local Inventory. d. Click Update VM IP/FQDN. e. Provide the IP address and FQDN of the virtual machine. 6. Click Save. Update IPFQDN in Local Inventory updates the IP address or FQDN only in the local database in System Manager. The actual IP address or FQDN of the host does not change. Use Update Network Params in the Host tab to update the IP address or FQDN of the host. May 2016 Deploying Avaya Aura applications 69

Deploying Avaya Aura applications Deleting a virtual machine Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In VM Management Tree, select a location. 3. On the right navigation pane, click Virtual Machines. 4. On the Virtual Machines page, select one or more virtual machines. 5. On the Delete page, click Delete, and click Yes to confirm the deletion. The system turns off the virtual machines, and deletes the selected virtual machines from the host. Changing the network parameters of Appliance Virtualization Platform and Avaya Aura applications About this task Change the network parameters for Appliance Virtualization Platform and each Avaya Aura application from the application, and then change the IP address and FQDN of Avaya Aura applications and Appliance Virtualization Platform from Solution Deployment Manager. Before you begin Connect the system on which Solution Deployment Manager is running to the new network for changing network parameters. When many Avaya Aura applications are running on an Appliance Virtualization Platform host, ensure that you change the network parameter in the following order: 1. Appliance Virtualization Platform 2. Avaya Aura applications that are running on the host except Utility Services. 3. Utility Services Note: Procedure If you fail to follow the order, Utility Services network parameter update might fail. 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In VM Management Tree, select a location. 3. On the Host tab, in the Hosts for Selected Location <location name> section, select an ESXi host and click Change Network Params > Change Host IP Settings. May 2016 Deploying Avaya Aura applications 70

Managing the virtual machine 4. In the Network Parameters section, change the following as appropriate, and click Save: IP address, subnetmask, and other parameters Gateway IP address For more information, see Change Network Parameters field descriptions. 5. Change the network parameters first for each Avaya Aura application on the host, and then for Utility Services. For more information, see Administering Avaya Aura application available for each application. Also, see Network Parameters for Avaya Aura applications. 6. On the Virtual Machines tab, in the VMs for Selected Location <location name> section, do the following first for all Avaya Aura applications except Utility Services, and then for Utility Services: a. In the Edit VMs section, select a virtual machine and click Edit. b. Click Update IP/FQDN in Local Inventory. c. Click Update VM IP/FQDN. d. Provide the IP address and FQDN of the virtual machine. 7. Click Save. Update IPFQDN in Local Inventory updates the IP address or FQDN only in the local database in System Manager. The actual IP address or FQDN of the host does not change. Use Update Network Params in the Host tab to update the IP address or FQDN of the host. 8. Do the following first for all Avaya Aura applications except Utility Services, and then for Utility Services: a. Click More Actions > Re-establish connection. Note: To update IP address or FQDN for Utility Services, establish trust on all virtual machines that are running on the host on which Utility Services resides. b. Click More Actions > Refresh VM. Note: To update IP address or FQDN for Utility Services, refresh all virtual machines that are running on the host where Utility Services resides. When you update the IP address and FQDN for Utility Services, the system also updates the Services Port static route for each application. Related links Change Network Parameters field descriptions on page 55 Changing the network parameters for an Appliance Virtualization Platform host on page 46 Network parameter update for Avaya Aura applications on page 82 May 2016 Deploying Avaya Aura applications 71

Deploying Avaya Aura applications Updating Services Port Static Routing on an Avaya Aura application About this task You might have to change the static routing if the Avaya Aura application that is running on the Appliance Virtualization Platform host is: Deployed by using the vsphere client and does not have the route. Non-operational or unreachable when you start the Avaya Aura application update. Before you begin Update network parameters of Utility Services if applicable. Ensure that the Avaya Aura application resides on the same subnetwork as Utility Services. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. On the Virtual Machines tab, in the VMs for Selected Location <location name> section, select an Avaya Aura application. 3. Click More Actions > Update Static Routing. The VM Update Static Routing page displays the details of Avaya Aura application and Utility Services. The fields are read-only. 4. Click Update. 5. On the Success dialog box, click OK. The system updates the Avaya Aura application with the new IP address of Utility Services for Services Port static routing. Related links Update Static Routing field descriptions on page 80 Starting a virtual machine from Solution Deployment Manager Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. From the virtual management tree, select a host to which you added virtual machines. 3. On the Virtual Machines tab, select one or more virtual machines that you want to start. 4. Click Start. In VM State, the system displays Started. May 2016 Deploying Avaya Aura applications 72

Managing the virtual machine Stopping a virtual machine from Solution Deployment Manager About this task System Manager is operational and ESXi or vcenter is added to the VM Management page to deploy Avaya Aura Application OVA on ESXi virtual machines. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. From the virtual management tree, select a ESXi or vcentre host to which you added virtual machines. 3. On the Virtual Machines tab, select one or more virtual machines that you want to stop. 4. Click Stop. In VM State, the system displays Stopped. Restarting a virtual machine from Solution Deployment Manager Before you begin System Manager is operational, and ESXi or vcenter is added to the VM Management page to deploy Avaya Aura Application OVA on ESXi virtual machines. Virtual machines must be in the running state. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. From the virtual management tree, select a host to which you added virtual machines. 3. On the Virtual Machines tab, select one or more virtual machines that you want to restart. 4. Click Restart. In VM State, the system displays Stopped and then Started. VM Deployment field descriptions Select Location and Host Name Select Location The location name. The field is display-only. Table continues May 2016 Deploying Avaya Aura applications 73

Deploying Avaya Aura applications Name Select Host Host FQDN Data Store Next The hostname of the ESXi host. For example, smgrdev. The field is display-only. FQDN of the ESXi host. The data store with the available size. The page populates the Capacity Details section. Displays the Deploy OVA section in the Location & Host Details screen where you provide the details required for deployment. Capacity Details The system displays the CPU and memory details of the host. The fields are read-only. Note: If the host is in a cluster, the system does not display the capacity details of CPU and memory. Ensure that the host resource requirements are met before you deploy the virtual machine. Name Name Full Capacity Free Capacity Reserved Capacity Status The name The maximum capacity The available capacity The reserved capacity The configuration status Deploy OVA on System Manager Solution Deployment Manager Name Select Software Library Select OVAs Flexi Footprint Next The software library where the.ova file is available. The.ova file that you want to deploy. The footprint size supported for the selected host. Important: Ensure that the required memory is available for the footprint sizes that you selected. The upgrade operation might fail due to insufficient memory. Ensure that the application contains the footprint size values that are supported. Displays the Configuration Parameters tab in the OVA Details screen where you provide the OVA details. May 2016 Deploying Avaya Aura applications 74

Managing the virtual machine Deploy OVA on the Solution Deployment Manager client Name Provide OVA path OVA File Submit File Flexi Footprint Next The option to select a.ova file of the virtual machine that is available on the system that hosts the Solution Deployment Manager client. The absolute path to the.ova file on the system that hosts the Solution Deployment Manager client. The field is available only when you click Select the OVA from Local SMGR. Selects the.ova file of System Manager that you want to deploy. The footprint size supported for the selected host. Important: Ensure that the required memory is available for the footprint sizes that you selected. The upgrade operation might fail due to insufficient memory. Displays the Configuration Parameters tab in the OVA Details screen where you provide the OVA details. Configuration Parameters The system populates most of the fields depending on the OVA file. Note: For configuration parameter fields, for Communication Manager Messaging and Utility Services, see VM Deployment Configuration and Network Parameters field descriptions on page 77. Name VM Name Product Version ME Deployment The name of the virtual machine. The name of the Avaya Aura application that is being deployed. The field is read-only. Release number of the Avaya Aura application that is being deployed. The field is read-only. The option to perform the Midsize Enterprise deployment. The option is available only while deploying Communication Manager simplex OVA. May 2016 Deploying Avaya Aura applications 75

Deploying Avaya Aura applications Table 1: Configuration Parameters for Communication Manager simplex OVA deployment Name CM IPv4 Address CM IPv4 Netmask CM IPv4 Gateway Out of Band Management IPv4 Address Out of Band Management Netmask CM Hostname NTP Servers DNS Servers Search Domain List WebLM Server IPv4 Address CM Privileged Administrator User Login CM Privileged Administrator User Password Confirm Password The IP address of the Communication Manager virtual machine. The network mask of the Communication Manager virtual machine. The default gateway of the Communication Manager virtual machine. The IP address of the Communication Manager virtual machine for out of band management. The field is optional network interface to isolate management traffic on a separate interface from the inband signaling network. The subnetwork mask of the Communication Manager virtual machine for out of band management. The hostname of the Communication Manager virtual machine. The IP address or FQDN of the NTP server. Separate the IP addresses with commas (,). The DNS IP address of the Communication Manager virtual machine. The search list of domain names. For example, mydomain.com. Separate the search list names with commas (,). The IP address of WebLM. The field is mandatory. The login name for the privileged administrator. You can change the value at any point of time. The password for the privileged administrator. You can change the value at any point of time. The password required to be confirmed. Network Parameters Name Public Services The port number that is mapped to public port group. You must configure Public network configuration parameters only when you configure Out of Band Management. Otherwise, Public network configuration is optional. The port number that is mapped to the services port group when Utility Services is deployed in the solution. Utility Services provides routing from the services port to the virtual machines and additional functions, such as alarm conversion. Table continues May 2016 Deploying Avaya Aura applications 76

Managing the virtual machine Name Duplication Link Out of Band Management Button Deploy The connection for server duplication. The field is available only when you deploy duplex Communication Manager. The port number that is mapped to the out of band management port group. Displays the EULA acceptance screen where you must click Accept to start the deployment process. Related links VM Deployment Configuration and Network Parameters field descriptions on page 77 VM Deployment Configuration and Network Parameters field descriptions Table 2: Configuration Parameters for Communication Manager Messaging deployment Name Messaging IPv4 address Messaging IPv4 Netmask Messaging IPv4 Gateway Out of Band Management IPv4 Address Out of Band Management IPv4 Netmask Messaging Hostname NTP Servers DNS Server(s) The IP address of the Communication Manager Messaging virtual machine. The network mask of the Communication Manager Messaging virtual machine. The default gateway of the Communication Manager Messaging virtual machine. For example, 172.16.1.1. The IP address of the Communication Manager Messaging virtual machine for out of band management. The field is optional network interface to isolate management traffic on a separate interface from the inbound signaling network. The subnetwork mask of the Communication Manager Messaging virtual machine for out of band management. The hostname of the Communication Manager Messaging virtual machine. The IP address or FQDN of the NTP server. Separate the IP addresses with commas (,). The field is optional. The DNS IP address of the Communication Manager Messaging virtual machine. Separate the IP addresses with commas(,). The field is optional. Table continues May 2016 Deploying Avaya Aura applications 77

Deploying Avaya Aura applications Name Search Domain List WebLM Server IPv4 Address Messaging Privileged Administrator User Login Messaging Privileged Administrator User Password Confirm Password The search list of domain names. For example, mydomain.com. Separate the search list names with commas (,). The IP address of WebLM. The field is mandatory. The login name for the privileged administrator. You can change the value at any point of time. The password for the privileged administrator. You can change the value at any point of time. The password required to be confirmed. Configuration and Network Parameters for Utility Services deployment Name Configuration Parameters Communication Manager IP IP address of Communication Manager. Note: Hostname TImezone setting NTP Server IP Out of Band Management Mode A unique Communication Manager IP address is required for each Utility Services. If you are not associated with a Communication Manager server, specify a static IP that is in your network range. Linux hostname or fully qualified domain name for Utility Services virtual machine. The selected timezone setting for the Utility Services virtual machine. IP address of a server running Network Time Protocol that Communication Manager can use for time synchronization. The Out of Band Management mode in which you want to deploy. The options are as follows: OOBM_Enabled: To enable Out of Band Management. OOBM_Disabled: To disable Out of Band Management. Note: Utility Services Mode OOBM_Disabled is the default setting. If the mode is set to OOBM_Disabled, then you do not need to configure Out of Band Management. The mode in which you want to deploy Utility Services. The options are: Services Port Only: Deploys Services Port only. Use when the customer already has Utility Services running on another virtual machine and providing the services. Table continues May 2016 Deploying Avaya Aura applications 78

Managing the virtual machine Name With the services port feature, through a laptop connected to the services port of Appliance Virtualization Platform, you can gain access to Avaya virtual machines and the hypervisor that are deployed. Utility Servers Only: Use to disable routing. Set this mode only for Virtualized Environment. If you set this mode for an Avaya appliance, the services port becomes non-operational. Full Functionality: Utility Services and services port enabled. The default mode for Appliance Virtualization Platform. You can set the mode only during the deployment. You cannot change the mode after the virtual machine is deployed. Note: For the Solution Deployment Manager client to connect to the services port features of Utility Services, change the IP address to 192.11.13.5 on the computer of the technician Utility Services can gain access to the hypervisor and all virtual machines. Utility Services provides application routing between the physical port and virtual applications. Primary System Manager IP address for application registration Enrollment Password Confirmation password Network Parameters Default Gateway The IP address of System Manager that is required for application registration. The enrollment password. The confirmation password. The IP address of the default gateway. Required field unless you use DHCP. DNS The IP address of domain name servers for the Utility Services virtual machine. Separate each IP address by a comma. Required field unless you use DHCP. Public IP address The IP address for this interface. Required field unless you use DHCP. Public Netmask The netmask for this interface. Required field unless you use DHCP. Out of Band Management IP Address Out of Band Management Netmask The IP address for this interface. The netmask for this interface. May 2016 Deploying Avaya Aura applications 79

Deploying Avaya Aura applications Update Static Routing field descriptions Name VM Name VM IP/FQDN Utility Services IP Button Update The virtual machine name The IP address or FQDN of the virtual machine The IP address of Utility Services Updates the static IP address for routing. Installed Patches field descriptions Button Action to be performed Get Info Commit Rollback Name VM Name VM IP Patch Name Patch Type Patch Version Patch State The operation that you want to perform on the software patch, service pack, or feature pack that you installed. The options are: All: Displays all the software patches. Commit: Displays the software patches that you can commit. Rollback: Displays the software patches that you can rollback. Displays software patches, service packs, and feature packs that you installed. Commits the selected software patch. Rolls back the selected software patch. The name of the System Manager virtual machine on which you want to install the patch. The IP address of System Manager on which you want to install the patch. The software patch name that you want to install. The patch type. The options are service pack and software patch. The software patch version. The software patch state. The states are: Activated Table continues May 2016 Deploying Avaya Aura applications 80

Managing the virtual machine Name Deactivated Removed Installed Patch Status The software patch status. Update VM field descriptions Name VM Name VM IP VM FQDN Host Name Select bin file from Local SMGR The System Manager virtual machine name The IP address of System Manager FQDN of System Manager The host name The option to select the software patch or service pack for System Manager. The absolute path is the path on the computer on which the Solution Deployment Manager client is running. The patch is uploaded to System Manager. This option is available only on the Solution Deployment Manager client. Auto commit the patch The option to commit the software patch or service pack automatically. If the check box is clear, you must commit the patch from More Actions > Installed Patches. Button Install Installs the software patch or service pack on System Manager. Reestablish Connection field descriptions Name VM Name VM IP/FQDN User Name Password The virtual machine name The IP address or FQDN of the virtual machine The user name The password May 2016 Deploying Avaya Aura applications 81

Deploying Avaya Aura applications Button Reestablish Connection Establishes connection between System Manager and the virtual machine. Network parameter update for Avaya Aura applications You can change the network parameters for Avaya Aura applications that run on an Appliance Virtualization Platform server. The commands listed might change. Therefore, from the Avaya Support website at https:// support.avaya.com, get the latest command update for an Avaya Aura application from the appropriate document. Tip: On the Avaya Support website navigate to Support by Product > Documents > <Avaya Aura application>, type the release number, click Installation, Upgrades & Config, click Enter, and search for the updates. Avaya Aura application Command Interface where you perform the task Appliance Virtualization Platform System Manager serverinitialnetworkconfi g changeipfqdn -IP <IP address> FQDN <FQDN> - GATEWAY <Gateway address> -NETMASK <Netmask address> -DNS <DNS address> -SEARCH <search list of domain names> CLI CLI or vsphere client Communication Manager - The Network Configuration page from Administration > server(maintenance) > ServerConfiguration on Communication Manager SMI. Session Manager SMnetSetup vsphere client Avaya Breeze and all installed snap-ins - vsphere client Utility Services VMware_conf.sh CLI Avaya Aura Media Server - See the Avaya support website. SAL Gateway - Currently, you cannot change Network Parameters for SAL Gateway May 2016 Deploying Avaya Aura applications 82

Certificate validation Certificate validation Certification validation With System Manager Solution Deployment Manager and Solution Deployment Manager client, you can enable a certificate-based TLS connection between the Solution Deployment Manager service and a host that is running Avaya Aura 7.x applications. This enables to establish secure communications between System Manager Solution Deployment Manager or the Solution Deployment Manager client and Appliance Virtualization Platform or ESXi hosts. The certificate-based sessions apply to the Avaya Aura Virtualized Appliance offer using host selfsigned certificates and the customer-provided Virtualization Environment using host self-signed or third party certificates. You can check the following with certificate based TLS sessions: Certificate valid dates Origin of Certificate Authority Chain of Trust CRL or OCSP state Log Certificate Validation Events Solution Deployment Manager checks the certificate status of hosts. If the certificate is incorrect, Solution Deployment Manager does not connect to the host. For the correct certificate: The fully qualified domain or IP address of the host to which you are connecting must match the value in the certificate and the certificate must be in date. Appliance Virtualization Platform and VMware ESXi hosts do not automatically regenerate their certificates when host details such as IP address or hostname and domain changes. The certificate might become incorrect for the host. If the certificate is incorrect: For the Appliance Virtualization Platform host, Solution Deployment Manager regenerates the certificate on the host and then uses the corrected certificate for the connection. For the VMware ESXi host or vcenter, the system denies connection. The customer must update or correct the certificate on the host or vcenter. For more information about updating the certificate, see Updating the certificate on the ESXi host from VMware. Note: Solution Deployment Manager: Validates certificate of vcenter Does not validate certificates for hosts that vcenter manages With Solution Deployment Manager, you can only accept certificate while adding vcenter. If a certificate changes, the system gives a warning that the certificate does not match the certificate in May 2016 Deploying Avaya Aura applications 83

Deploying Avaya Aura applications the trust store on Solution Deployment Manager. You must get a new certificate, accept the certificate as valid, and save the certificate on the system. To validate certificates, you can directly log on to the host and confirm that the details in the /etc/ vmware/ssl/rui.crt file match the details displayed on the screen. Generating and accepting certificates About this task With Solution Deployment Manager, you can generate certificates only for Appliance Virtualization Platform hosts. For the VMware ESXi hosts, if the certificate is invalid: Get a correct certificate for the host and add the certificate. Regenerate a self-signed certificate on the host. For more information, see Generating new self-signed certificates for the ESXi host. Before you begin Require permissions to add a host to generate certificates. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In VM Management Tree, select a location. 3. On the Host tab, in the Host for Selected Location <location name>, select an Appliance Virtualization Platform host. 4. Click More Actions > Generate/Accept Certificate. 5. On the Certificate window, do the following: Next steps a. Click Generate Certificate. Note: You can generate certificate only for the Appliance Virtualization Platform host. b. Click Accept Certificate. In the Hosts for Selected Location <location name> section, the Host Certificate column must display. If the system displays an SSL verification error when you gain access to the Appliance Virtualization Platform host from the vsphere client, restart the Appliance Virtualization Platform host. Related links Adding an ESXi host on page 43 Generating new self-signed certificates for the ESXi host on page 87 May 2016 Deploying Avaya Aura applications 84

Certificate validation Updating the certificate on the ESXi host from VMware About this task Use the procedure to update the ESXi host certificate. For information about updating vcenter certificates, see the VMware documentation. Before you begin Start an SSH session on the ESXi host. Procedure 1. Start vsphere client, and log in to the ESXi host as admin or root user. 2. Ensure that the domain name and the hostname of the ESXi host is set correctly and matches the FQDN that is present on the DNS servers, correct the entries to match if required. For security reason, the common name in the certificate must match the hostname to which you connect. 3. To generate new certificates, type /sbin/generate-certificates. The system generates and installs the certificate. 4. Restart the ESXi host. 5. (Optional) Do the following: a. Move the ESXi host to the maintenance mode. b. Install the new certificate. c. From the Direct Console User Interface (DCUI), restart management agents. Note: The host certificate must now match the fully qualified domain name of the host. VMware places only FQDN in certificates that are generated on the host. Therefore, use a fully qualified domain name to connect to ESXi hosts and vcenter from Solution Deployment Manager. Appliance Virtualization Platform places an IP address and FQDN in generated certificates. Therefore, from Solution Deployment Manager, you can connect to Appliance Virtualization Platform hosts through IP address or FQDN. The connection from Solution Deployment Manager 7.0.1 to a vcenter or ESXi host by using an IP address fails because the IP address is absent in the certificate and the connection is not sufficiently secure. Related links Generating new self-signed certificates for the ESXi host on page 87 May 2016 Deploying Avaya Aura applications 85

Deploying Avaya Aura applications Managing certificates for existing hosts About this task By default, the certificate status of the host or vcenter that is migrated from earlier release is invalid. To perform any operation on the host from Solution Deployment Manager, you require a valid certificate. Therefore, you must get the valid certificate and accept the certificate. Depending on the host type and the validity of the certificate, use appropriate steps to generate the certificate, and then accept the certificate. Before you begin Require permissions to add a host to generate certificates. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In VM Management Tree, select a location. 3. On the Host tab, in the Host for Selected Location <location name>, select a host. 4. (Optional) On an Appliance Virtualization Platform host, click More Actions > Generate/ Accept Certificate, and on the Certificate dialog box, do one of the following: If the certificate is valid, click Accept Certificate. If the certificate is invalid, click Generate Certificate, and then click Accept Certificate. 5. For the ESXi host, do one of the following: If the certificate is valid, on the Certificate dialog box, click More Actions > Generate/ Accept Certificate, and click Accept Certificate. If the certificate is invalid, log in to the ESXi host, validate the certificate, and then from Solution Deployment Manager, accept the certificate. For more information, see Generating new self-signed certificates for the ESXi host. 6. For vcenter, do the following: a. Click Map vcenter, select the vcenter server, and click Edit. b. In the Certificate dialog box, accept certificate, and click Save. Related links Generating new self-signed certificates for the ESXi host on page 87 Generating and accepting certificates on page 84 May 2016 Deploying Avaya Aura applications 86

Certificate validation Generating new self-signed certificates for the ESXi host About this task Generate new certificates only if you change the host name or accidentally delete the certificate. Under certain circumstances, you must force the host to generate new certificates. To receive the full benefit of certificate checking, particularly if you want to use encrypted remote connections externally, do not use a self-signed certificate. Instead, install new certificates that are signed by a valid internal certificate authority or purchase a certificate from a trusted security authority. Before you begin Start an SSH session on the ESXi host. Procedure 1. Log in to the ESXi host as an admin user. 2. To create a backup of any existing certificates, in the /etc/vmware/ssl directory, rename the certificates by using the following commands: mv rui.crt orig.rui.crt mv rui.key orig.rui.key Note: Do not perform the step if you are regenerating certificates because you deleted the certificates. 3. To generate new certificates, type /sbin/generate-certificates. 4. Restart the ESXi host. The generation process places the certificates places in the correct location. 5. (Optional) Do the following: a. Move the ESXi host to the maintenance mode. b. Install the new certificate. c. Restart management agents from Direct Console User Interface (DCUI). 6. Do the following to confirm that the host successfully generated new certificates: Next steps a. Type ls -la. b. Compare the time stamps of the new certificate files with orig.rui.crt and orig.rui.key. Replace the self-signed certificate and the key with a trusted certificate and key. May 2016 Deploying Avaya Aura applications 87

Deploying Avaya Aura applications Managing vcenter Adding a vcenter to Solution Deployment Manager About this task System Manager Solution Deployment Manager supports virtual machine management in vcenter 5.0, 5.1, 5.5, and 6.0. When you add vcenter, System Manager discovers the ESXi hosts that this vcenter manages, adds to the repository, and displays in the Managed Hosts section. Also, System Manager discovers virtual machines running on the ESXi host and adds to the repository. System Manager displays vcenter, ESXi host, and virtual machines on the Manage Elements page. Before you begin Ensure that you have the required permissions. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In the lower pane, click Map vcenter. 3. On the Map vcenter page, click Add. 4. In the New vcenter section, provide the following vcenter information: vcenter FQDN For increased security when using a vcenter with Solution Deployment Manager, use an FQDN for the vcenter. vcenter does not put IP addresses in its certificates. Therefore, you need FQDN to confirm the server identity through the certificate in Solution Deployment Manager. User Name Password Authentication Type 5. Click Save. 6. On the certificate dialog box, click Accept Certificate. The system generates the certificate and adds vcenter. In the Managed Hosts section, the system displays the ESXi hosts that this vcenter manages. Related links Editing vcenter on page 89 Map vcenter field descriptions on page 90 New vcentre and Edit vcentre field descriptions on page 91 May 2016 Deploying Avaya Aura applications 88

Managing vcenter Editing vcenter Before you begin Ensure that you have the required permissions. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In the lower pane, click Map vcenter. 3. On the Map vcenter page, select a vcenter server and click Edit. 4. In the Edit vcenter section, change the vcenter information as appropriate. 5. If vcenter is migrated from earlier release, on the Certificate page, click Accept Certificate, and click Save. 6. To edit the location of ESXi hosts, in the Managed Hosts section, do one of the following: Select an ESXi host and click the edit icon ( ). Select one or more ESXi hosts, select the location, and click Bulk Update and click Update. If you do not click Commit after you move the host from Managed Hosts to Unmanaged Hosts or vice versa, and you refresh the table, the page displays the same host in both the tables. Click Commit to get an updated list of managed and unmanaged hosts. Deleting vcenter from Solution Deployment Manager Before you begin Ensure that you have the required permissions. Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. In the lower pane, click Map vcenter. 3. On the Map vcenter page, select one or more vcenter servers and click Delete. 4. Click Yes to confirm the deletion of servers. The system deletes the vcenter from the inventory. May 2016 Deploying Avaya Aura applications 89

Deploying Avaya Aura applications Map vcenter field descriptions Name Name IP FQDN License Status Certificate Status Button View Generate/Accept Certificate Button Add Edit Delete Refresh The name of the vcenter server. The IP address of the vcenter server. The FQDN of the vcenter server. Note: Use FQDN to successfully map and log in to vcenter from Solution Deployment Manager. With IP address, the system displays an error message about the incorrect certificate and denies connection. The license type of the vcenter server. The license status of the vcenter server. The certificate status of the vcenter server. The values are: : The certificate is correct. : The certificate is not accepted or invalid. Displays the certificate status details of the vcenter server. Displays the certificate dialog box where you can generate and accept certificate for vcenter. For vcenter, you can only accept certificate. You cannot generate certificate. Displays the New vcenter page, where you can add a new ESXi host. Displays the Edit vcenter page, where you can update the details and location of ESXi hosts. Deletes the ESXi host. Updates the list of ESXi hosts in the Map vcenter section. May 2016 Deploying Avaya Aura applications 90

Managing vcenter New vcentre and Edit vcentre field descriptions Name vcenter FQDN User Name Password Authentication Type Button Save Refresh FQDN of vcenter. The user name to log in to vcenter. The password that you use to log in to vcenter. The authentication type that defines how Solution Deployment Manager performs user authentication. The options are: SSO: Global username used to log in to vcenter to authenticate to an external Active Directory authentication server. LOCAL: User created in vcenter Saves any changes you make to FQDN, username, and authentication type of vcenter. Refreshes the vcenter details. Managed Hosts Name Host IP/FQDN Host Name Location Edit Bulk Update Update Commit The name of the ESXi host. The IP address of the ESXi host. The physical location of the ESXi host. The option to edit the location and host. Provides an option to change the location of more than one ESXi hosts. Note: You must select a location before you click Bulk Update. Saves the changes that you make to the location or hostname of the ESXi host. Commits the changes that you make to the ESXi host with location that is managed by vcenter. Unmanaged Hosts Name Host IP/FQDN The name of the ESXi host. Table continues May 2016 Deploying Avaya Aura applications 91

Deploying Avaya Aura applications Name ESXi Version The version of the ESXi host. The options are: 5.0, 5.1, 5.5, and 6.0. Button Commit Saves all changes that you made to vcenter on the Map vcenter page. Monitoring a host and virtual machine Monitoring a host Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. Click the Monitor Hosts tab. 3. In the Monitor Hosts page, do the following: a. In Hosts, click a host. b. Click Generate Graph. The system displays the graph regarding the CPU/memory usage of the host that you selected. Monitoring a virtual machine Procedure 1. On the System Manager web console, click Services > Solution Deployment Manager, and then click VM Management. 2. Click the Monitor VMs tab. 3. In the Monitor VMs page, do the following: a. In Hosts, click a host. b. In Virtual machines, click a virtual machine on the host that you selected. 4. Click Generate Graph. The system displays the graph regarding the CPU/memory usage of the virtual machine that you selected. May 2016 Deploying Avaya Aura applications 92

Chapter 7: Installing software patches, service packs, and feature packs for applications Installing software patches About this task Use the procedure to install the software patches and service packs that are entitled for an Avaya Aura application, and commit the software patches that you installed. Before you begin Perform the preupgrade check. If you upgrade an application that was not deployed from Solution Deployment Manager, perform the following: Procedure 1. Select the virtual machine. 2. To establish trust, click More Actions > Re-establish Connection. 3. Click Refresh VM. 1. On the System Manager web console, click Services > Solution Deployment Manager. 2. In the left navigation pane, click Upgrade Management. 3. Select an Avaya Aura application on which you want to install the patch. 4. Click Upgrade Actions > Upgrade/Update. 5. On the Upgrade Configuration page, click Edit. 6. In the General Configuration Details section, in the Operation field, click Update. 7. In the Upgrade Source field, select the software library where you have downloaded the patch. 8. (Optional) Click the Auto Commit check box, if you want the system to automatically commit the patch. 9. In the Upgrade Configuration Details section, in the Select patches for update table, select the software patch that you want to install. 10. Click Save. May 2016 Deploying Avaya Aura applications 93

Installing software patches, service packs, and feature packs for applications 11. On the Upgrade Configuration page, ensure that the Configuration Status field displays. If the field displays 12. Click Upgrade., review the information on the Edit Upgrade Configuration page. 13. On the Job Schedule page, click one of the following: Run Immediately: To perform the job. Schedule later: To perform the job at a scheduled time. 14. Click Schedule. On the Upgrade Management page, the Update status and Last Action Status fields display. 15. To view the update status, click. The Upgrade Job Details page displays the detailed update checks that are in progress. Click Done to close the window. When the update is complete, the Update status and Last Action Status fields displays. 16. Click Upgrade Actions > Installed Patches. 17. On the Installed Patches page, in the Patch Operation section, click Commit. The page displays all software patches that you can commit. You can use Rollback and Uninstall options if you must rollback and uninstall the software patch. 18. Select the patch that you installed, in the Job Schedule section, click Run Immediately. You can schedule to commit the patch at a later time by using the Schedule later option. 19. Click Schedule. The Upgrade Management page displays the last action as Commit. 20. Ensure that Update status and Last Action Status fields display. Installed Patches field descriptions Name Commit Uninstall The option to select the patches that you can commit. The option to select the patches that you can uninstall. Table continues May 2016 Deploying Avaya Aura applications 94

Installed Patches field descriptions Name Rollback Show All Name Name Element Name Patch Version Patch Type Patch State Name Schedule Job Date Time Time Zone The option to select the patches that you can rollback. The option to display all the available options. The name of the software patch. The element on which the software patch is installed. The version of the software patch. The type of the software patch. The options are: service pack or software patch Kernel The state of the software patch. The options are: Installed Activated Deactivated Removed Uninstall Pending The option to schedule a job: Run immediately: To run the upgrade job immediately. Schedule later: To run the upgrade job at the specified date and time. The date on which you want to run the job. The date format is mm:dd:yyyy. Use the calendar icon to choose a date. This field is available when you select the Schedule later option for scheduling a job. The time when you want to run the job. The time format is hh:mm:ss and 12 (AM or PM) or 24-hour format. This field is available when you select the Schedule later option for scheduling a job. The time zone of your region. This field is available when you select the Schedule later option for scheduling a job. May 2016 Deploying Avaya Aura applications 95

Installing software patches, service packs, and feature packs for applications Name Schedule Runs the job or schedules to run at the time that you configured in Job Schedule. May 2016 Deploying Avaya Aura applications 96

Chapter 8: Out of Band Management configuration Avaya Aura Out of Band Management Out of Band Management is defined as a physical or logical separation of user and management traffic, either to different VLANs or different physical interfaces on the server for increased security of the system. Only administrator can gain access to the management interfaces from a specific network, users of the system cannot gain access. This prevents unauthorized login from the user network to applications. Only the ports and servers that are required for user functions are provided to the user network. Management interfaces are provided to the management network. In Out of Band Management setup, an administrator username and password is not sufficient to gain access to the system. The login attempt must also be able to access the Out of Band Management network. When out of band management is enabled, Avaya Aura applications run: User services on one network interface. For example, IP phone registration, user configuration, and media traffic Management services on another network interface. For example, administration webpages, SSH connections, and management traffic from System Manager. May 2016 Deploying Avaya Aura applications 97

Out of Band Management configuration The following Avaya Aura applications support Out of Band Management starting in Release 7.0: Communication Manager Session Manager System Manager Application Enablement Services Avaya Breeze with Presence Appliance Virtualization Platform SAL Utility Services Branch Session Manager WebLM Avaya Aura Media Server and Avaya Diagnostic Server does not support the Out of Band Management feature. Appliance Virtualization Platform Out of Band Management Overview When you install Appliance Virtualization Platform, the public network of virtual machines is assigned to vmnic0 or Server Ethernet port 1 of the server. In the installation spreadsheet, if Out of Band Management is: Disabled: The public and management interfaces of virtual machines are assigned on the public network. Assign public and management interfaces of virtual machines on the same network. Enabled: The public interfaces of virtual machines are assigned to vmnic0 or Server Ethernet port 1, and the Out of Band Management interfaces are assigned to vmnic2 or Server Ethernet port 3. Assign separate network ranges to the public and management interfaces of virtual machines. The management port must be given an appropriate IP address of the public and Out of Band Management network. Note: All virtual machines on an Out of Band Management enabled Appliance Virtualization Platform host must support and implement Out of Band Management. When Out of Band Management is: Disabled: The management port of Appliance Virtualization Platform is assigned to the public interface. Enabled: The management port of Appliance Virtualization Platform is assigned to the Out of Band Management network. May 2016 Deploying Avaya Aura applications 98

Appliance Virtualization Platform Out of Band Management The vmnic1 or Server Ethernet port 2 of the server is assigned to the services port. The hypervisor is 192.168.13.6 on the services port network (VMNIC1 or eth1). After Utility Services OVA is deployed, from your computer by using an SSH client, gain access to the Utility Services shell from the services port with the following: IP address: 192.11.13.5 or 192.11.13.30 Gateway: 192.11.13.6 Common servers When Appliance Virtualization Platform is installed, VMNIC0 is assigned to the public interface of virtual machines. When deploying or reconfiguring Appliance Virtualization Platform, if Out of Band Management is: Disabled: VMNIC0 is used for both network and management traffic. Enabled: VMNIC2 is used for management by all the virtual machines on that hypervisor. S8300D When you install the connection through the media gateway using Appliance Virtualization Platform, Ethernet ports are assigned to the public interface of the virtual machines. When you install the connection through the media gateway backplane using Appliance Virtualization Platform, the LAN port on the G4x0 Gateway is assigned to the public interface of virtual machines. If Out of Band Management is enabled, the Out of Band Management network is assigned to a separate VLAN on the public interface. Otherwise all virtual machine interfaces are on the same network. The Appliance Virtualization Platform management interface is assigned to: The public VLAN if Out of Band Management is disabled The Out of Band Management VLAN if Out of Band Management is enabled Note: To support Out of Band Management on S8300D, you require specific versions of gateway firmware. To ensure that you are running the correct version, see the gateway documentation. S8300E When Appliance Virtualization Platform installs the connection through the media gateway, Ethernet ports are assigned to the public interface of virtual machines. When Appliance Virtualization Platform installs the connection through the media gateway backplane, the LAN port on the G4x0 Gateway is assigned to the public interface of virtual machines. If Out of Band Management is enabled, the Out of Band Management network is on the LAN2 interface on the S8300E faceplate. The Appliance Virtualization Platform management interface is assigned to: The public VLAN if Out of Band Management is disabled The Out of Band Management network if Out of Band Management is enabled May 2016 Deploying Avaya Aura applications 99

Out of Band Management configuration Out of Band Management in Virtualized Environment In the Virtualized Environment offer where the customer has control of the hypervisor network setup, the customer creates the desired networking and assigns the virtual Ethernet port of the applications on deployment. Public interfaces are assigned to the user network port groups and Out of Band Management ports are assigned to the management network port group. Utility Services Out of Band Management Out of Band Management is a physically and logically separate network connection. It connects to a customer s private IT management network and provides for secure management and administration of Avaya products. From Utility Services Release 7.0.1, you can activate out-of-band management even after deployment. Utility Services Release 7.0.1 and later support a full out of band management configuration. Therefore, you can deploy Utility Services with two IP addresses and split the user and management traffic to different Ethernet interfaces on different IP networks. When Utility Services is set for out of band management, the following services are allocated for full or Utility Services-only mode: Application Phone firmware download Phone settings file Gateway firmware download DHCP Server Myphone User SSH Myphone Admin CDR connection to CM Main admin web pages Alarm source SAL connection (SSH, HTTP) Interfaces for traffic Public Public Public Public Public Out of Band Management / Services Out of Band Management Out of Band Management Out of Band Management / Services Out of Band Management Out of Band Management When Utility Services is set for out of band management, the following services are allocated for services port-only mode: May 2016 Deploying Avaya Aura applications 100

System Manager Out of Band Management Application SSH Alarm source SAL connection (SSH, HTTP) Main admin web pages Phone firmware download Gateway firmware download Phone settings Gateway firmware download DHCP Server Myphone Server CDR connection to CM Myphone admin Interfaces for traffic Out of Band Management / Services Out of Band Management Out of Band Management Disabled Disabled Disabled Disabled Disabled Disabled Disabled Disabled Disabled Note: If a network is not mentioned for service when Out of Band Management is enabled, the service must be disabled on that interface. System Manager Out of Band Management Out of Band Management in System Manager System Manager provides the following network interfaces: The regular eth0 interface that was present in releases earlier than System Manager Release 7.0, is called the Management interface or Out of Band Management interface. The IP address is called as the Management IP address. The Management interface is mandatory for configuration. The following are the examples of System Manager Management network traffic: - Database replication with Session Manager - Element management. For example, Session Manager, Communication Manager, and Avaya Breeze. - User management - Solution deployment, upgrades, and software patch install If Out of Band Management is enabled, then the public interface is configured with Public IP address and used for the nonmanagement traffic. This is an optional configuration. May 2016 Deploying Avaya Aura applications 101

Out of Band Management configuration The following are the examples of System Manager nonmanagement or public network traffic: - End-user self-provisioning - Client devices getting certificates through SCEP - Tenant Management Out of Band Management configuration persists across System Manager upgrades, updates, and restarts. For configuring Out of Band Management in System Manager, System Manager must be installed on an Appliance Virtualization Platform host that is configured with Out of Band Management. Out of Band Management is enabled during the deployment of Appliance Virtualization Platform. Out of Band Management in a Geographic Redundancy setup When you configure Geographic Redundancy, provide Management network details only. Validation fails if you configure Geographic Redundancy with Public network details. In Geographic Redundancy setup, you do not disable or enable Out of Band Management on both primary and secondary System Manager virtual machine. You can enable Out of Band Management on the primary System Manager virtual machine and disable Out of Band Management on the secondary System Manager virtual machine, and vice versa. Restoring System Manager backup While restoring backup on System Manager with different Out of Band Management network details, the restore operation fails at validation phase. Tenant Management on Out of Band Management-enabled System Manager By default, the Multi Tenancy feature is disabled on System Manager when Out of Band Management is enabled. You must enable Multi Tenancy on Out of Band Management-enabled System Manager for the Tenant Management administrator to manage tenant users. Configuring Out of Band Management on System Manager About this task If you do not configure Out of Band Management during the deployment of System Manager OVA from Solution Deployment Manager on an Avaya-provided server, you can use the configureoobm command to configure Out of Band Management anytime after the deployment. Before you begin Enable Out of Band Management on Appliance Virtualization Platform. Install System Manager on the Appliance Virtualization Platform host on which Out of Band Management is installed. Ensure that IP address or hostname of Public network and Management network are different. If both are in the same network, Out of Band Management configuration might not function as expected. Log in to System Manager by using an SSH client utility. When you enable Out of Band Management configuration, you might lose the connection as the system does a network restart. You can login to System Manager from the Console of May 2016 Deploying Avaya Aura applications 102

System Manager Out of Band Management VMware vsphere Client. that is configured to connect to the Appliance Virtualization Platform host server. Procedure 1. To enable Out of Band Management, type configureoobm -EnableOOBM. The system enables Out of Band Management on the System Manager virtual machine. With EnableOOBM, the system configures the additional Ethernet interface, updates network configuration, and sets the firewall rules. 2. To disable Out of Band Management, type configureoobm -DisableOOBM. The system disables Out of Band Management on the System Manager virtual machine. With DisableOOBM, the system disables the additional Ethernet interface that you configured earlier and sets the firewall rules to default. 3. To add the IP address and subnet ranges in the Management IP range, type configureoobm -AddIPtoManagementIPRange. You can now gain access to System Manager from the network. Configuring Out of Band Management on System Manager in the Geographic Redundancy setup About this task Note: You cannot enable Out of Band Management on secondary System Manager server when Out of Band Management on primary System Manager server is disabled. Before you begin Identify one of the following: Enable Out of Band Management on both the primary and secondary System Manager server. Enable Out of Band Management on the primary System Manager server and not enable Out of Band Management on the secondary System Manager server. Disable Out of Band Management on secondary System Manager server. Disable Out of Band Management on both the primary and secondary System Manager server. Procedure 1. To enable Out of Band Management on both primary and secondary System Manager server, perform the following: a. Disable Geographic Redundancy replication on primary System Manager server. b. Convert primary System Manager server to standalone System Manager server and activate the secondary System Manager server. c. Enable Out of Band Management on both primary and secondary System Manager server. May 2016 Deploying Avaya Aura applications 103

Out of Band Management configuration d. Reconfigure the Geographic Redundancy on the secondary System Manager server. e. Enable Geographic Redundancy replication on primary System Manager server. 2. To enable Out of Band Management on the primary System Manager server and not enable Out of Band Management on secondary System Manager server, perform the following: a. Disable Geographic Redundancy replication on primary System Manager server. b. Convert primary System Manager server to standalone System Manager server. c. Enable Out of Band Management on primary System Manager server. d. Once Out of Band Management on primary System Manager server is enabled, reconfigure Geographic Redundancy on secondary System Manager server. e. Enable Geographic Redundancy replication on primary System Manager server. 3. To disable Out of Band Management on secondary server, perform the following: a. Disable Geographic Redundancy replication on primary System Manager server. b. Convert primary System Manager server to standalone System Manager server. c. Activate secondary System Manager server and disable Out of Band Management. d. Reconfigure primary System Manager server from the web console of the secondary System Manager server. e. Enable Geographic Redundancy replication on primary System Manager server. 4. To disable Out of Band Management on both servers, perform the following: a. Disable Geographic Redundancy replication on primary System Manager server. b. Convert primary System Manager server to standalone System Manager server and disable Out of Band Management. c. Activate secondary System Manager server and disable Out of Band Management. d. Reconfigure Geographic Redundancy on secondary System Manager server with old primary System Manager server which is now standalone. e. Enable Geographic Redundancy replication on primary System Manager server. Communication Manager Out of Band Management With the Out of Band Management feature, you can set up a dedicated network connection to securely manage Communication Manager. The network connection can be physical or virtual. Detailed description of Out of Band Management Communication Manager has a virtual NIC for a dedicated Ethernet connection for management functions. You can use System Management Interface (SMI) to manage the Avaya products using May 2016 Deploying Avaya Aura applications 104

Communication Manager Out of Band Management this dedicated Ethernet connection. The dedicated network connection administration persists after a Communication Manager upgrade. With the dedicated network connection, you can create separate channels for the user functions and the management functions. You can use the dedicated network connection for the management functions to manage the system, perform IA scans, and update the firmware. You can also use the network connection for other network services such as system logging, backup, NTP, and WebLM licensing. For the user functions, you can set up more specific user access controls. You can also have more specific auditing processes to detect insider threats. Out of Band Management management administration To configure the Out of Band Management of management data on Communication Manager, you must do the following: Depending on your Communication Manager configuration, assign an IP address and a subnetwork mask to the eth1 or eth2 Ethernet connection. Select Out of Band Management as the functional assignment. Enable Out of Band Management of management data. Add a static route between the Out of Band Management interface and the enterprise network. Screens for administering Out-of-Band management Screen name Purpose Fields Network Configuration Status Routes Configure the IP address and the subnetwork mask to administer the Ethernet connection. Create a static route between the Out-of-Band management interface and the enterprise network to route all management function data through the Out-of- Band management interface. IPv4 Address Mask Functional Assignment Restrict Management traffic to Out-of-Band interface is currently IP Address Mask / Prefix Gateway Interface Administering the Out of Band Management of management data Procedure 1. Log in to Communication Manager SMI. 2. Click Administration > Server (Maintenance). May 2016 Deploying Avaya Aura applications 105

Out of Band Management configuration 3. In the navigation pane, click Server Configuration > Network Configuration. 4. Configure the following eth1 fields: IPv4 Address: The IP address of the Ethernet connection Mask: The subnetwork mask of the IP address Functional Assignment: Out-of-Band Management If the Communication Manager instance is a duplex configuration, configure the eth2 fields. 5. Verify that you can gain access to Communication Manager using the Out-of-Band Ethernet interface. Important: You must be able to gain access to Communication Manager using the Out of Band Management Ethernet interface before you perform the next step. 6. Add a static route between the Out of Band Management interface and the enterprise network. You must ensure that you add a static route between the Out of Band Management interface and the enterprise network to restrict access. For more information, see Add a static route between the Out of Band Management interface and the enterprise network. 7. From the Restrict Management traffic to Out-of-Band interface is currently drop-down list, select enabled. Note: Port restriction Restrict Management traffic to Out-of-Band interface is set to enabled. Restrict Management traffic to Out-of-Band will restrict traffic on ports 80, 443, 22, 2222, 5022, 23, 5023, 161, and 162 to the management interface only. When the Restrict Management traffic to Out-of-Band field is set to enable, the system restricts traffic on the following ports: Port Use 22 ssh 23 telnet 80 http 161 snmp 162 snmp trap 443 https 2222 high priority ssh 5022 sat over ssh 5023 sat over telnet May 2016 Deploying Avaya Aura applications 106

Session Manager Out of Band Management ports Adding a static route between the Out-of-Band management interface and the enterprise network About this task Create a static route between the Out-of-Band management interface and the enterprise network to route all management functions data through the Out-of-Band management interface. Procedure 1. Log in to Communication Manager SMI. 2. Click Administration > Server (Maintenance). 3. In the navigation pane, click Server Configuration > Static Routes. 4. Configure the following fields: IP Address: Enter the enterprise network IP address. Mask / Prefix: Enter the subnetwork mask of the network IP address. Gateway: Enter the gateway address. Interface: Select eth1. If the Communication Manager instance is a duplex configuration, select eth2. 5. Click Add Route. Session Manager Out of Band Management ports Component Interface Security Module (secmod) th1(public IP) The interface that manages SIP and HTTP traffic to and from the WebSphere Application Server (WAS) traffic. Security Module is the front-end of Session Manager running Linux operating system 6.5 with Avaya proprietary applications providing SIP protection, TLS termination, and firewall. WebSphere (WAS) eth0 (public IP) A converged JSR289 container that processes SIP messages received from SIP entities or endpoints. Table continues May 2016 Deploying Avaya Aura applications 107

Out of Band Management configuration Component Interface Management Agent (MGMT) eth0 (public IP) A management console that is used to listen on port 8643 for an HTTPS connection to add, remove, restart, or monitor Session Manager. SAL-Agent eth0 (public IP) A Java application that receives events and collects inventory information from the product and converts them to its own internal format. It then encapsulates the message into HTTPS and sends the information to an Enterprise Server, usually at Avaya. Data Replication Service (DRS) eth0 (public IP) A service that synchronizes database changes between System Manager and Session Manager. DRS uses HTTPS for replication messages. JMX is used from remote management. For information on Management Port and Security Port, see Session Manager Port Matrix. Application Enablement Services Out of Band Management Out of Band Management provides the ability to move the AE Services Management Console Web based management and configuration traffic of the server to a dedicated subnetwork. Table 3: Application Enablement Services Out of Band Management Component Interface DMCC Service Eth0 (public IP) The Device, Media, and Call Control (DMCC) service provides both, first-party and third-party call control features using a Java API. It also provides XML and.net interfaces. Additionally, DMCC provides the integration for Microsoft LCS 2005, OCS 2007, LYNC, and Sametime. TCP/IP, TLS and SIP protocols may used to connect a DMCC Client to DMCC. DLG Service Eth0 (public IP) The DEFINITY LAN Gateway (DLG) service tunnels messages over TCP/IP. That is, the DLG service supports a set of TCP/IP connections for the communications channel between Avaya Aura Communication Manager and AE Services. The DLG service is also used for transporting ASAI/Q.931 messages. Table continues May 2016 Deploying Avaya Aura applications 108

Out of Band Management in Avaya Breeze Component Interface CVLAN Service Eth0 (public IP) The CallVisor LAN (CVLAN) service is a C/C++ based API that enables applications to exchange ASAI messages with the AE Services Server. CVLAN provides a full complement of thirdparty call control capabilities such as controlling specific calls or stations, completing routing of incoming calls, receiving notifications of events, invoking features, and querying Avaya Aura Communication Manager for information. TSAPI Service Eth0 (public IP) The Telephony Services API (TSAPI) is a C/C++ based API that provides a full complement of third party call control capabilities. The Java Telephony API (JTAPI) is a client side interface to the TSAPI service. It provides third party call control. Transport Service Eth0 (public IP) A Transport link is a secure TCP/IP connection between the AE Services server and a CLAN or Processor Ethernet board on Avaya Aura Communication Manager. System Management Service Telephony Web Service AES Management Console Eth0 (public IP) Eth0 (public IP) Eth0 (public IP) or Eth2 (Out of Band Mgmt IP) Listens on port 443 for HTTPS connection to provide users a web interface to enable SOAP-based access to Avaya Aura Communication Manager administration functions. Listens on port 8443 and 443 for HTTPS connection to provide users a web interface that enables high level call control functionality over standard web services interfaces (SOAP/ XML). The Application Enablement Services Management Console listens on port 443 for HTTPS connections, and provides an Operations, Administration and Management interface for maintenance of the AE Services server. The default interface is eth0, unless Out-of-Band Management has been configured. Out of Band Management in Avaya Breeze Avaya Breeze always has two IP addresses that reside on the same or different IP networks depending on the Out of Band Management network. The IP addresses for the security and management interface must be on: Same IP address network if Out of Band Management is disabled Different IP address networks if Out of Band Management is enabled Out of Band Management in SAL From Release 2.5, SAL supports Out of Band Management setups, but runs management interfaces on both public and SAL interfaces. May 2016 Deploying Avaya Aura applications 109

Out of Band Management configuration No. Default Destination Port (Configurab le Range) Network / Application Protocol INGRESS CONNECTIONS Optional ly Enabled / Disable d? Default Port State External Device 1 22 TCP/SSH No Open Admin terminal INGRESS CONNECTIONS (LOAD BALANCER TO SAL STC) 1 9443 (1-65535) EGRESS CONNECTIONS 1 443 (1-65535) TCP/HTTPS No Open Load Balancer TCP/HTTPS No N/A SAL Core Server These ports run against both interfaces. System management requiring shell access. The port on which the STC listens for incoming remote connection requests. The port on which the SAL Core server listens for requests. Hence, configure the value must accordingly in the stcconfig.properties file. Note s 1,2 Note: Avaya Diagnostic Server does not support Out of Band Management. May 2016 Deploying Avaya Aura applications 110

Chapter 9: Post Installation Verification Verifying the installation of System Manager About this task Perform the following verification procedure after you install System Manager Release 7.0.1 and configure System Manager. Procedure 1. On the web browser, type https:// <fully qualified domain name of System Manager>, and ensure that the system displays the System Manager web console. 2. On the upper-right corner, click and click About. The system displays the About SMGR window with the build details. 3. Verify the System Manager version number. Post installation checklist Perform the following steps to verify the Session Manager OVA installation. No. Task 1 Verify the connections of the deployed Session Manager. 2 Upgrade Session Manager to the latest release. 3 Run the maintenance tests on the deployed Session Manager. 4 Verify data replication. 5 Upgrade the Session Manager VMware tools. Deploying Session Manager on VMWare Administering Avaya Aura Session Manager Deploying Session Manager on VMWare May 2016 Deploying Avaya Aura applications 111

Post Installation Verification Verifying the connections About this task Verify the connections of the deployed Session Manager and Branch Session Manager. Procedure On the home page of the System Manager Web Console, in Elements, click Session Manager. May 2016 Deploying Avaya Aura applications 112

Chapter 10: Postinstallation tasks Loading a customer-specific authentication file About this task Avaya provides the default authentication file for Appliance Virtualization Platform. You must download the customer-specific authentication file from the Authentication File System website. Procedure 1. To gain access to the Avaya RFA Home page, type http://rfa.avaya.com in the web browser. 2. Log on to the RFA Home page. 3. Click Start the AFS Application. 4. On the license page, click I Agree. 5. In the Product field, select Appliance Virtualization Platform. 6. In the Release field, click 7.x. 7. Click Next. 8. On the Deliver an Authentication File page, perform one of the following: To create an authentication file for a new system, click New System - Product: <Appliance Virtualization Platform Release: 7.x>. To create an authentication file for an upgrade or re-delivery for an existing system, click Upgrade or Re-deliver for Existing System or re-deliver for existing system - Product: <Appliance Virtualization Platform Release: 7.x>, and type the authentication file ID. 9. Click Next. 10. Ensure that SSH is enabled on the Appliance Virtualization Platform host, and if required, enable SSH through Utility Services. For more information, see Activating SSH to Appliance Virtualization Platform. 11. Click Download file to my PC. 12. Using WinSCP or a similar application, copy the authentication file on to the Appliance Virtualization Platform system by using the root account and the password set at installation. 13. Using PuTTy or a similar SSH client, log in to Appliance Virtualization Platform by using the root account and the password set at installation. May 2016 Deploying Avaya Aura applications 113

Postinstallation tasks 14. Type /opt/avaya/bin/loadauth -l AF-7001064472-150430-131707.xml - o /etc/asg/lacfile. Where AF-7001064472-150430-131707.xml, is the authentication file name and l.is the location where the system downloaded the xml file. Always include the -o option as o /etc/asg/lacfile. 15. Using the SSH client, log in to Appliance Virtualization Platform as sroot, and view the updated product ID displayed with the ASG challenge. Downloading and installing an authentication file on the Avaya Aura application About this task Avaya provides the default authentication file for an application. You must download the customerspecific authentication file from the AFS website. Each Avaya Aura application has a unique method to install an authentication file. For example, for: Communication Manager by using System Management Interface. Utility Services by using the web interface. Session Manager by using shell, log in to Session Manager with customer login account that is defined during deployment, and use command loadpwd. Therefore, use an appropriate procedure that applies to an Avaya Aura application. This is an example procedure for downloading the authentication file. Note: Do not use this procedure to download the authentication file for Utility Services. Procedure 1. To gain access to the Avaya RFA Home page, type http://rfa.avaya.com in the web browser. 2. Log on to the RFA Home page. 3. Click Start the AFS Application. 4. On the license page, click I Agree. 5. In the Product field, click <Avaya Aura application name>. Where <Avaya application> is the application that you want to deploy or upgrade. 6. In the Release field, click 7.x. 7. Perform one of the following: To create new authentication file for new installation, click New System - Product: <Avaya Aura application name Release: 7.x>. May 2016 Deploying Avaya Aura applications 114

Downloading and installing an authentication file on the Avaya Aura application To create new authentication file for an upgrades system, click Upgrade or Re-deliver for Existing System or re-deliver for existing system - Product: <Avaya Aura application name Release: 7.x>, and type the authentication file ID. 8. In the Enter the fully qualified domain name field, type FQDN or retain the default value. 9. Click Download file to my PC or Download file via email. Depending on the selection, the system downloads the authentication file on your computer or sends the file through email. 10. Using an appropriate procedure, copy the authentication file to the Avaya Aura application. 11. Using an appropriate procedure that applies to an Avaya Aura application, get the authentication file. For example, for Appliance Virtualization Platform type./opt/avaya/bin/loadauth -l AF-7001064472-150430-131707.xml -o /etc/asg/lacfile. Where AF-7001064472-150430-131707.xml is the authentication file name l is the location where the system downloaded the xml file. Always include o option as o /etc/asg/lacfile. 12. Using the SSH client, log in to the application, and view the updated product ID displayed with the ASG challenge. May 2016 Deploying Avaya Aura applications 115

Chapter 11: Resources Documentation The following table lists the documents related to this product. Download the documents from the Avaya Support website at http://support.avaya.com. Title Use this document to: Audience Overview Avaya Aura Virtualized Environment Solution Avaya Aura System Manager Overview and Specification Administering Administering Avaya Aura System Manager for Release 7.0.1 Administering Network Connectivity on Avaya Aura Communication Manager, 555-233-504 Administering Avaya Aura Communication Manager, 03-300509 Using Using the Solution Deployment Manager client Implementing Upgrading Avaya Aura System Manager to Release 7.0.1 Migrating and Installing Avaya Appliance Virtualization Platform Understand the high-level solution features and functionality Understand the high-level solution features and functionality Perform administration tasks Administer the network components of Communication Manager. Administer Communication Managercomponents, such as trunks, signalling groups, and dial plans. Set up telephony features, such as conferencing, transfer, and messaging.communication Manager. Deploy Avaya Aura applications and install patches on Avaya Aura applications. Install and configure Avaya applications Install Appliance Virtualization Platform on Avaya-provided servers, and migrate the data from System Platform to Appliance Virtualization Platform. Customers and sales, services, and support personnel Customers and sales, services, and support personnel System administrators System administrators System administrators System administrators Implementation personnel Implementation personnel Table continues May 2016 Deploying Avaya Aura applications 116

Training Title Use this document to: Audience Troubleshooting Troubleshooting Avaya Aura System Manager Perform troubleshooting tasks Related links Finding documents on the Avaya Support website on page 117 System administrators and IT personnel Finding documents on the Avaya Support website About this task Use this procedure to find product documentation on the Avaya Support website. Procedure 1. Use a browser to navigate to the Avaya Support website at http://support.avaya.com/. 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. Related links Documentation on page 116 Training The following courses are available on the Avaya Learning website at www.avaya-learning.com. After logging into the website, enter the course code or the course title in the Search field and click Go to search for the course. May 2016 Deploying Avaya Aura applications 117

Resources Course code Course title Avaya Aura core implementation 1A00234E 4U00040E 4U00030E 10U00030E 8U00170E AVA00838H00 ATC00838VEN Avaya Aura core support 5U00050E 5U00060E 4U00115I 4U00115V 1A00236E Avaya Aura Fundamental Technology Avaya Aura Session Manager and System Manager Implementation Avaya Aura Communication Manager and Communication Manager Messaging Implementation Avaya Aura Application Enablement Services Implementation Avaya Aura Presence Services Implement and Support Avaya Aura Media Server and Media Gateways Implementation Workshop Avaya Aura Media Server and Gateways Implementation Workshop Labs Session Manager and System Manager Support ACSS - Avaya Aura Communication Manager and CM Messaging Support Avaya Aura Communication Manager Implementation Upgrade (R5.x to R6.x) Avaya Aura Session Manager and System Manager Fundamentals 2008W What is New in Avaya Aura Application Enablement Services 7.0 2008T What is New in Avaya Aura Application Enablement Services 7.0 Online Test 2009W What is New in Avaya Aura Communication Manager 7 2009T What is New in Avaya Aura Communication Manager 7.0 Online Test 2010W What is New in Avaya Aura Presence Services 7.0 2010T 2011W 2011T 2013V What is New in Avaya Aura Presence Services 7.0 Online Test What is New in Avaya Aura Session Manager and Avaya Aura System Manager 7.0 What is New in Avaya Aura Session Manager and Avaya Aura System Manager 7.0 Online Test Avaya Aura 7 Administration Avaya Aura core administration and maintenance 9U00160E 1A00236E 5U00051E 5M00050A Avaya Aura Session Manager for System Administrators Avaya Aura Session Manager and Avaya Aura System Manager Fundamentals Avaya Aura Communication Manager Administration Avaya Aura Communication Manager Messaging Embedded Administration, Maintenance & Troubleshooting 2012V Migrating and Upgrading to Avaya Aura 7.0 2012I Migrating and Upgrading to Avaya Aura 7 2017 Avaya Aura 7 Administration Delta 2017V Avaya Aura 7 Administration Delta May 2016 Deploying Avaya Aura applications 118

Viewing Avaya Mentor videos 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. Procedure To find videos on the Avaya Support website, go to http://support.avaya.com 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 www.youtube.com/avayamentor 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 http://support.avaya.com 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. May 2016 Deploying Avaya Aura applications 119

Glossary Appliance Virtualization Platform Migration Update Upgrade Appliance Virtualization Platform is the customized OEM version of VMware ESXi 5.5. With Appliance Virtualization Platform, customers can run any combination of supported applications on Avaya-supplied servers. Appliance Virtualization Platform provides greater flexibility in scaling customer solutions to individual requirements. Appliance Virtualization Platform is available only in an Avaya-appliance offer. Avaya-appliance offer does not support VMware tools, such as vcenter and vsphere Client. 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. The migration process includes changing the server hardware, change the operating system, and reinstallation of software that includes hypervisor. During migration, you might need to perform backup and restore operations outside the normal upgrade process. You cannot rollback the upgrade easily. The update process includes installing patches of an application. For example, kernel patches, security patches, hotfixes, service packs, and feature packs. The upgrade process includes upgrading a product from earlier release to the latest release without the need to change the server hardware or hypervisor. The process is triggered through the normal process without requiring additional backup and restore operations. You can rollback an upgrade. May 2016 Deploying Avaya Aura applications 120

Index Special Characters /sbin/generate-certificates...87 A access Solution Deployment Manager... 26 access Solution Deployment Manager client...18 add virtual machine... 60, 73, 77 adding Appliance Virtualization Platform host... 43 AVP host...43 ESXi host...43 location... 36 vcenter to SDM... 88 adding certificates available hosts...86 existing hosts...86 migrated hosts... 86 adding ESXi host... 43 adding location...36 adding location to host...89 adding vcenter to SDM... 88 add virtual machine...60, 73, 77 administering Out-of-Band management... 105 Out-of-Band management static route... 107 administration Out-of-Band management... 105 Appliance Virtualization Platform... 11, 31, 47, 51, 56, 113 change password... 50 install... 29 networking... 98 restarting...54 shutting down... 53 update...44, 58 Appliance Virtualization Platform and Utility Services... 23 Appliance Virtualization Platform host Gateway change...46 edit...46 Appliance Virtualization Platform host IP address change...46 edit...46 Appliance Virtualization Platform host password changing... 50 Appliance Virtualization Platform network parameters... 46 Appliance Virtualization Platform overview...11 ASG file...113 ASG file installation on Appliance Virtualization Platform.. 113 ASG file installation on Avaya Aura application...114 authentication file ASG file... 114 download... 113, 114 install... 113, 114 Avaya Aura application deploy... 20 Services Port static routing update...72 upgrade... 20 Avaya Aura application deployment... 13 Avaya Aura applications Network Parameters change... 82 Avaya Aura Virtualized Appliance offer... 11 Avaya virtualization platform...11 Avaya Virtualized offers... 11 C capabilities Solution Deployment Manager client...15, 19 certificates accepting... 84 generating...84 certificate update ESXi host...85 vcenter... 85 VMware documentation...85 Certification validation...83 change Appliance Virtualization Platform host IP address... 46 Host/ IP Settings...47 network settings...56 Network Settings... 47 Change Gateway... 55 change IP address for AVP host...46 Change IP FQDN...68 change Netmask for Appliance Virtualization Platform host 46 Change Network Params...46 changing IP address and default gateway... 52 changing Appliance Virtualization Platform host password. 50 changing Network Parameters for Avaya Aura...82 checklist Avaya Aura applications deployment... 26 client Solution Deployment Manager... 13 Communication Manager deployment using Solution Deployment Manager... 26 Communication Manager update...93 Configuration Parameters...73, 77 configure server preinstalled with Appliance Virtualization Platform... 31 configuring Out of Band Management... 97, 109 configuring Out of Band Management on System Manager...102, 103 connections May 2016 Deploying Avaya Aura applications 121

Index connections (continued) verifying... 112 correcting ESXi host certificate...85 create virtual machine... 58, 66 creating authentication file... 113 D deleting ESXi host...54 location... 37 virtual machine... 70 deleting ESXi host... 54 deleting location...37 deleting vcenter...89 delivering authentication file... 113 deploy Branch Session Manager... 26, 66 Communication Manager... 26, 66 product knowledge... 9 Session Manager...26, 66 skills...9 System Manager... 58, 66 tools... 9 Utility Services... 26, 66 deploy application... 22 deploy Avaya Aura 7.0 application... 66 deploy Avaya Aura applications checklist...26 Deploying an OVA file utility services... 64 deployment Avaya Aura application...13 deploy OVA...58, 66 detailed description Out-of-Band management... 104 disabling SSH on Appliance Virtualization Platform... 51 disabling SSH... 51 documentation... 116 download ASG file... 113 authentication file...113 download software...35 E edit virtual machine... 68, 70 Edit Host... 55 editing ESXi host...44 location... 37 vcenter... 89 editing ESXi host... 44 editing location...37 editing vcenter...89 Edit Location... 42 Edit vcenter... 91 edit virtual machine...68 enabling SSH on Appliance Virtualization Platform... 51 enabling SSH...51 esxcfg-route... 52 esxcli network ip interface ipv4 set -i vmk0 -I... 52 ESXi host adding...43 deleting... 54 editing... 44 ESXi host certificate addition... 86 ESXi host certificate update...85 ESXi host map to unknown location... 54 existing hosts managing certificates...86 existing vcenter managing certificates...86 F field descriptions change password... 57 Edit Host... 55 Edit Location...42 Hosts... 37 Locations... 37 Map vcenter... 90 New Host... 55 New Location...42 Virtual Machines... 37 VM Deployment... 60, 73, 77 fresh deployment Avaya Aura application...13 G generating certificates... 84 new self-signed certificates for ESXi host... 87 H hardware supported...24 host... 47, 56 monitoring...92 Host update...58 Hosts...37 I install Application Enablement Services... 16 May 2016 Deploying Avaya Aura applications 122

Index install (continued) ASG file... 113, 114 authentication file...113, 114 Avaya Aura applications... 16 Avaya Aura Media Server...16 Avaya Breeze... 16 Branch Session Manager... 16 Communication Manager... 16 SAL...16 SDM...16 Session Manager...16 Solution Deployment manager client...16 System Manager... 16 WebLM... 16 install Appliance Virtualization Platform...29 install AVP host patch Solution Deployment Manager... 44 Installed Patches... 94 Installed Patches field descriptions...80 install patches... 93 install services packs... 93 install software patches... 93 Install System Manager patch... 81 IP address and default gateway changing... 52 L legal notice... Life cycle management...22 location adding...36 deleting... 37 editing... 37 view... 36 Locations... 37 M Management interface... 101 managing certificates migrated hosts... 86 map ESXi host to unknown location... 54 Map vcenter... 88 91 migrated hosts managing certificates...86 monitoring host...92 virtual machine... 92 VM... 92 N networking Appliance Virtualization Platform...98 network parameters change...55 Network Parameters change... 82 network parameters for AVP and virtual machines change...70 New Host... 55 New Location... 42 New vcenter... 91 O offer Avaya appliance... 11 Virtualized Environment...11 out of band management...100 Out of Band management...104 Out of Band Management...97, 101 Application Enablement Services... 108 Avaya Breeze... 109 disable... 102 enable...102 Geographic Redundancy...103 Network interface configurations... 100, 108 ports...107 SAL...109 Virtualized Environment...100 Out-of-Band management adding a static route... 107 administering... 105 administration overview... 105 administration screens...105 description... 104 P password change...57 password change Appliance Virtualization Platform host... 50 password policy... 50 password rules...50 perform System Manager tests...111 port restriction... 106 Post Installation Checklist...111 preinstall Appliance Virtualization Platform...31 product knowledge...9 Public interface... 101 R reestablish connection... 81 Reestablish Connection...37 related documentation... 116 removing location from host...89 removing vcenter... 89 restart virtual machine... 73 May 2016 Deploying Avaya Aura applications 123

Index restarting, AVP...54 restart virtual machine from SDM... 73 S screens Out-of-Band management... 105 SDM installation...16 SDM client... 14 SDM client capabilities...19 SDM client dashboard... 18 Select Flexi Footprint... 68 self-signed certificates for ESXi host generate... 87 servers supported... 24 Services Port static route update...72 Session Manager Out of Band Management ports... 107 Session Manager update...93 shutting down AVP... 53 skills to deploy... 9 software download... 35 software library software library management... 34 viewing a file... 34 software requirements... 24 Solution Deployment Manager... 13, 20, 50, 51 access... 26 restart virtual machine... 73 start...26 start virtual machine... 72 stop virtual machine...73 update Appliance Virtualization Platform host... 44 Solution Deployment Manager client... 13, 14 install... 16 Solution Deployment Manager client capabilities... 15, 19 Solution Deployment Manager client dashboard... 18 start virtual machine... 72 start Solution Deployment Manager... 26 start virtual machine from SDM... 72 static routing changing... 72 updating...72 stop virtual machine... 73 stop virtual machine from SDM...73 support...119 supported servers... 24 System Manager deploy... 58 installing patches... 63 Solution Deployment Manager... 63 Virtual Machines... 63 VM Management... 63 System Manager documentation... 116 System Manager installation verify... 111 System Manager Solution Deployment Manager and client capabilities... 15 System Manager VM management... 80 System Manager VM update... 81 T tools to deploy...9 training... 117 U Unknown location host mapping...54 update Appliance Virtualization Platform...58 Appliance Virtualization Platform host... 44 Communication Manager... 93 Session Manager...93 update software... 93 update static routing... 80 Update Static Routing...37 update System Manager VM... 81 Update VM IP/FQDN... 70 updating ESXi host or vcenter certificate... 85 updating Services Port static routing... 72 upgrade elements... 94 upgrade Avaya Aura application...20 Utility Services Avaya Aura virtualized appliance offer... 23 Utility Services and Appliance Virtualization Platform... 23 V vcenter add...91 adding...88 add location... 89 deleting... 89 edit...91 editing... 89 manage...89 remove location... 89 removing...89 unmanage...89 vcenter certificate update...85 vcentre... 90 verify System Manager installation... 111 verifying connections... 112 videos... 119 May 2016 Deploying Avaya Aura applications 124

Index view location... 36 view location... 36 virtual machine create...58, 66 deleting... 70 edit...68 monitoring...92 restart... 73 start...72 stop...73 Virtual machine management... 22 Virtual Machines... 37 VM connection reestablish...81 VM Deployment... 60, 73, 77 VMware software requirements... 24 May 2016 Deploying Avaya Aura applications 125