Deploying and Updating Avaya Aura Media Server Appliance

Transcription

1 Deploying and Updating Avaya Aura Media Server Appliance Release 7.7 Issue 3 May 2016

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

3 indicated in the order provided that the performance capacity of the Server(s) does not exceed the performance capacity specified for the Software. End User may not re-install or operate the Software on Server(s) with a larger performance capacity without Avaya s prior consent and payment of an upgrade fee. Named User License (NU). You may: (i) install and use each copy or Instance of the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use each copy or Instance of the Software on a Server so long as only authorized Named Users access and use the Software. Named User, means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya s sole discretion, a Named User may be, without limitation, designated by name, corporate function (e.g., webmaster or helpdesk), an or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Shrinkwrap License (SR). You may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as shrinkwrap or clickthrough license accompanying or applicable to the Software ( Shrinkwrap License ). Heritage Nortel Software Heritage Nortel Software means the software that was acquired by Avaya as part of its purchase of the Nortel Enterprise Solutions Business in December The Heritage Nortel Software is the software contained within the list of Heritage Nortel Products located at under the link Heritage Nortel Products or such successor site as designated by Avaya. For Heritage Nortel Software, Avaya grants Customer a license to use Heritage Nortel Software provided hereunder solely to the extent of the authorized activation or authorized usage level, solely for the purpose specified in the Documentation, and solely as embedded in, for execution on, or for communication with Avaya equipment. Charges for Heritage Nortel Software may be based on extent of activation or use authorized as specified in an order or invoice. Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, Hosted Service, or hardware provided by Avaya. All content on this site, the documentation, Hosted Service, and the product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Virtualization The following applies if the product is deployed on a virtual machine. Each product has its own ordering code and license types. Note that each Instance of a product must be separately licensed and ordered. For example, if the end user customer or Avaya Channel Partner would like to install two Instances of the same type of products, then two products of that type must be ordered. Third Party Components Third Party Components mean certain software programs or portions thereof included in the Software or Hosted Service may contain software (including open source software) distributed under third party agreements ( Third Party Components ), which contain terms regarding the rights to use certain portions of the Software ( Third Party Terms ). As required, information regarding distributed Linux OS source code (for those products that have distributed Linux OS source code) and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply is available in the products, Documentation or on Avaya s website at: support.avaya.com/copyright or such successor site as designated by Avaya. The open source software license terms provided as Third Party Terms are consistent with the license rights granted in these Software License Terms, and may contain additional rights benefiting You, such as modification and distribution of the open source software. The Third Party Terms shall take precedence over these Software License Terms, solely with respect to the applicable Third Party Components to the extent that these Software License Terms impose greater restrictions on You than the applicable Third Party Terms. The following applies only if the H.264 (AVC) codec is distributed with the product. THIS PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD ( AVC VIDEO ) AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE Preventing Toll Fraud Toll Fraud is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of Toll Fraud associated with your system and that, if Toll Fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya Toll Fraud intervention If You suspect that You are being victimized by Toll Fraud and You need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at for the United States and Canada. For additional support telephone numbers, see the Avaya Support website: or such successor site as designated by Avaya. Downloading Documentation For the most current versions of Documentation, see the Avaya Support website: or such successor site as designated by Avaya. Contact Avaya Support See the Avaya Support website: for product or Hosted Service notices and articles, or to report a problem with your Avaya product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: (or such successor site as designated by Avaya), scroll to the bottom of the page, and select Contact Avaya Support. Trademarks The trademarks, logos and service marks ( Marks ) displayed in this site, the Documentation, Hosted Service(s), and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, its licensors, its suppliers, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation, Hosted Service(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya 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.

4 Contents Chapter 1: Introduction... 6 Purpose... 6 Warranty... 7 Chapter 2: Overview... 8 About the Avaya Aura MS 7.7 appliance... 8 New in this release... 9 Virtual Appliance on Avaya Appliance Virtualization Platform... 9 Physical Appliance on Avaya Common Server... 9 System layer updates... 9 Chapter 3: Deploying in the Avaya AVP virtualized environment System requirements Best practice recommendations Choosing a Solution Deployment Manager Obtaining Avaya Aura MS OVA Adding the OVA file to a software library Deploying the OVA file by using Solution Deployment Manager Chapter 4: Deploying in the VMware virtualized environment System requirements Best practice recommendations Obtaining Avaya Aura MS OVA Deploying the OVA file by using vsphere Client Deploying the OVA file by using vsphere web client Deploying the OVA file without using vcenter Updating VMware Tools Chapter 5: Deploying Avaya Common Server physical appliances System requirements Dell R220XL active network ports HP DL360G9 active network ports Deploying the Avaya Aura MS physical appliance Obtaining physical appliance recovery software Reinstalling the Avaya Aura MS physical appliance Chapter 6: Signing in to the Avaya Aura MS appliance Element Manager Accessing Avaya Aura MS EM Accessing Linux shells Enabling Avaya support access Chapter 7: Configuration Configuring Avaya Aura MS Chapter 8: Network configuration May 2016 Deploying and Updating Avaya Aura Media Server Appliance 4

5 Contents Updating the network configuration Chapter 9: Backup and restore Performing a backup Uploading and restoring backup files Alternate procedure for uploading and restoring large backup files Chapter 10: Software Updates About media server updates Viewing the installed version and updates Uploading media server updates Uploading media server updates using a Linux shell Applying media server updates Removing media server updates Managing media server changes for 1+1 High Availability clusters Chapter 11: System layer updates System layer overview Viewing the system layer status Uploading system layer updates Uploading system layer updates using a Linux shell Applying system layer updates Rolling back system layer changes Managing system layer changes for 1+1 High Availability clusters Chapter 12: Upgrade from a previous release Upgrade overview Upgrading to Avaya Aura MS Upgrading 1+1 High Availability clusters Upgrading N+1 load sharing clusters Rollback to Chapter 13: Troubleshooting the Avaya Aura MS appliance Overview Unable to upload files larger than 2 GB Unable to upload updates Backup or restore tasks fail Resetting locked login accounts Restarting or shutting down from Linux shell Chapter 14: Related resources Documentation Viewing Avaya Mentor videos Support May 2016 Deploying and Updating Avaya Aura Media Server Appliance 5

6 Chapter 1: Introduction Purpose Use this document when you are working with the Avaya Aura Media Server (MS) 7.7 FP1 and later appliance. This document contains the procedures for: Deploying and updating Avaya Aura Media Server 7.7 appliances on the Avaya Appliance Virtualization Platform (AVP). Deploying, upgrading, and updating Avaya Aura Media Server 7.7 appliances in the VMware Virtualized Environment. Upgrading, updating, and reinstalling Avaya Aura Media Server 7.7 appliances on Avaya Common Servers. Important: Avaya also provides a non-appliance, software-only, application version of Avaya Aura Media Server which is installed on servers that you provide. For non-appliance installation, see Installing and Updating Avaya Aura Media Server Application on Customer Supplied Hardware and OS. Administrators of the appliance version of Avaya Aura Media Server 7.7 prior to Feature Pack 1 (FP1) must use this document. This document is intended for people who install, upgrade, and troubleshoot Avaya Aura Media Server 7.7 appliances prior to FP1. Avaya Aura Media Server FP1 is identified as follows: During initial physical or virtual appliance deployment, the version is _A15 or later. After the media server is deployed, the software layers are managed separately. For FP1, the Application layer is or later, and the System layer is or later. Administrators of the appliance version of Avaya Aura Media Server 7.7 must not use this document before referring to any other Avaya Aura Media Server 7.7 documents. Administrators of non-appliance versions of Avaya Aura Media Server 7.7 must not use this document. May 2016 Deploying and Updating Avaya Aura Media Server Appliance 6

7 Warranty Warranty Avaya provides a 90-day limited warranty on the Avaya Aura MS software. For detailed terms and conditions, see the sales agreement or other applicable documentation. Additionally, for the standard warranty description of Avaya and the details of support, see Help & Policies > Policies & Legal > Maintenance and Warranty Information on the Avaya Support website at support.avaya.com. For additional information, see Help & Policies > Policies & Legal > License Terms. For more details on the hardware maintenance for supported products, see ptlweb/services/sv0452. May 2016 Deploying and Updating Avaya Aura Media Server Appliance 7

8 Chapter 2: Overview About the Avaya Aura MS 7.7 appliance The Avaya Aura MS 7.7 appliance is a software appliance that combines the Avaya Aura MS 7.7 software and an optimized Linux operating system in a single and integrated package. A deployed Avaya Aura MS 7.7 appliance includes the following: Avaya Aura MS 7.7 software Avaya Aura MS Element Manager (EM) Security-hardened Linux operating system Pre-configured support accounts There are two types of Avaya Aura MS 7.7 appliances: Virtual appliances: Avaya Aura MS 7.7 appliances on the Appliance Virtualization Platform or VMware virtualized environment. Physical appliances: Avaya Aura MS 7.7 appliances on Avaya Common Servers. Note: This document contains the procedures for all types of appliances. Ensure that you use the procedures that are appropriate for your appliance type. Important: Avaya also provides a non-appliance, software-only, application version of Avaya Aura Media Server which is installed on servers that you provide. For non-appliance installations, see Installing and Updating Avaya Aura Media Server Application on Customer Supplied Hardware and OS. May 2016 Deploying and Updating Avaya Aura Media Server Appliance 8

9 New in this release New in this release Virtual Appliance on Avaya Appliance Virtualization Platform In addition to Avaya Aura MS 7.7 appliances on VMware Virtualized Environment, Avaya Aura MS 7.7 appliances are also supported on Avaya Appliance Virtualization Platform (AVP) as virtual appliances. Note: You can deploy and delete an Avaya Aura MS VM using Solution Deployment Manager (SDM), but you cannot use SDM to update, patch, or manage Avaya Aura MS. Instead, manage Avaya Aura MS using the update, backup, and restore procedures in this document. Related links Deploying in the Avaya AVP virtualized environment on page 10 Physical Appliance on Avaya Common Server In addition to virtual appliances, Avaya Aura MS 7.7 appliances are also available on Avaya Common Servers as physical appliances. Related links Deploying the Avaya Aura MS physical appliance on page 26 System layer updates The underlying operating system and other software that forms the required operational environment for Avaya Aura MS appliances can be updated. May 2016 Deploying and Updating Avaya Aura Media Server Appliance 9

10 Chapter 3: Deploying in the Avaya AVP virtualized environment System requirements Appliance Virtualization Platform (AVP) is a customized OEM version of VMware ESXi 5.5. Avaya uses the VMware -based AVP to provide virtualization for Avaya Aura applications in Avaya appliance offerings. The Avaya Aura MS appliance is deployed using Solution Deployment Manager (SDM). You can use a Windows -based SDM Client or SDM in System Manager to deploy a VM. AVP does not support VMware management tools, such as vcenter and vsphere Client for VM management. You must use Solution Deployment Manager to deploy and manage the media server VM. The AVP host must meet the following system requirements: CPU Memory Disk space Network bandwidth AVP host resource Requirement The core processor speed must be at least 2294 MHz. The total number of AVP host vcpus cannot exceed the total number of physical CPUs. Each media server appliance requires 4 vcpus.. Minimum 4670 MB of memory must be available for reservation and to accommodate 62 MB of overhead above the configured memory size of 4608 MB. Minimum 52 GB of available disk storage must be available in the AVP datastore. A dedicated pair of 1 Gbps network interfaces must be available in a teamed, failover configuration. Ensure that the required network interfaces are connected before deploying the OVA. The AVP and Utility Services IP addresses are available on NIC 1. Media server network interfaces are selected at the time of deployment and use a free network interface controller starting with NIC 4. Avaya Aura MS does not support out of band management. Out of band management must remain disabled on the AVP host. SDM deploys Avaya Aura MS with the correct CPU, memory settings and reservations to ensure correct operation. These VM parameters must not be altered. VMware management tools must not May 2016 Deploying and Updating Avaya Aura Media Server Appliance 10

11 Best practice recommendations be used to alter VM parameters or to configure the following vsphere features, which are not supported for Avaya Aura MS appliances: vmotion for running VMs Storage vmotion High Availability Fault tolerance VM snapshots, which adversely impact the VM disk and CPU performance Best practice recommendations Use the following best practices to deploy the Avaya Aura MS appliance in the Appliance Virtualization Platform enviroment. All physical servers that can host a VM must have the same CPU, memory, and networking specifications. Do not modify the CPU or memory reservations that are set for Avaya Aura MS OVA. Physical CPUs on the host must not be oversubscribed with respect to vcpu count across all VMs that share the host with Avaya Aura MS. A physical CPU refers to a physical CPU core and not to a hyper-thread. For example, the total number of vcpus across all VMs on an AVP host that has 12 physical cores with 24 hyper-threads, must not exceed 12. Note: This recommendation prevents CPU oversubscription. Therefore, the CPU reservation of the media server VM effectively enforces the minimum CPU core speed of the underlying hardware. The VM fails to start if the underlying hardware does not meet the core speed requirements. For maximum system performance, ensure that the energy savings features are disabled or that the maximum performance settings are enabled in the server BIOS. Deploy media server OVAs using the centralized Solution Deployment Manager in System Manager. Use the SDM Client on a Windows computer to deploy OVAs only when SDM in System Manager is not available. Old media server backup files must be removed to maintain free space on the system. Choosing a Solution Deployment Manager About this task The Avaya Aura MS appliance is deployed on AVP using Solution Deployment Manager. May 2016 Deploying and Updating Avaya Aura Media Server Appliance 11

12 Deploying in the Avaya AVP virtualized environment Note: You can deploy and delete an Avaya Aura MS VM using SDM, but you cannot use SDM to update, patch, or manage Avaya Aura MS. Instead, manage Avaya Aura MS using the update, backup, and restore procedures in this document. Avaya provides the following Solution Deployment Manager options: Centralized Solution Deployment Manager in System Manager. Solution Deployment Manager Client (SDM Client) for Windows computers. To learn about the capabilities of each option and to install the Avaya Solution Deployment Manager client, see Migrating and Installing Avaya Appliance Virtualization Platform. Avaya recommends using System Manager Solution Deployment Manager unless System Manager is unavailable. Next steps Obtain the Avaya Aura MS OVA file. Obtaining Avaya Aura MS OVA About this task You can download Avaya Aura MS OVA from the Avaya Product Licensing and Delivery System (Avaya PLDS) at You can also order DVDs containing the OVA using the following details: Material ID: Material Description: AAMS R7 MEDIA DVD - OVA DVD Label: Avaya Aura Media Server 7.7 Virtual Appliance for AVP and VMware Next steps Deploy the OVA file using vspere Client. Adding the OVA file to a software library About this task Use this task to upload an Avaya Aura MS OVA file when you are using Solution Deployment Manager (SDM) in System Manager to deploy the VM. Alternatively, you can use the SDM Client application, which you download and install on your Windows computer. You must transfer an Avaya Aura MS OVA file to System Manager before you can deploy it using SDM. The OVA file must be added to a software library on the system. OVA files are staged on System Manager and then a library that you specify pulls the staged file in from the staging area. The OVA file is available for deployment after it is in a software library. May 2016 Deploying and Updating Avaya Aura Media Server Appliance 12

13 Adding the OVA file to a software library Note: You can deploy and delete an Avaya Aura MS VM using SDM, but you cannot use SDM to update, patch, or manage Avaya Aura MS. Instead, manage Avaya Aura MS using the update, backup, and restore procedures in this document. Procedure 1. Transfer the OVA file to System Manager by using the sftp file transfer tool, or another similar tool. The file must be stored in the /swlibrary/staging/sync. 2. Log in to the Avaya Aura System Manager web console. 3. Navigate to Services > Solution Deployment Manager > Software Library Management. 4. Select the required software library. 5. Click Manage Files. 6. In the Sync Files from directory, select the checkbox next to the name of the required OVA file. 7. Enter the checksum of the OVA file in the MD5 Checksum field. 8. In the Software Library field, select a local System Manager library. 9. In the Product Family field, select Others. 10. In the Device Type field, select Others. 11. In the Software Type field, select Others. 12. Click Sync. Wait for the upload to complete. 13. (Optional) Perform the following steps to view the uploaded file in the software library: Next steps a. Navigate to Services > Software Library Management. b. Select the checkbox next to the name of the library containing the OVA. c. Click Manage Files. The uploaded OVA file is listed in the Software Library File section. Deploy the OVA file using Solution Deployment Manager. May 2016 Deploying and Updating Avaya Aura Media Server Appliance 13

14 Deploying in the Avaya AVP virtualized environment Deploying the OVA file by using Solution Deployment Manager About this task Use this task to deploy Avaya Aura MS virtual appliances on Avaya Appliance Virtualization Platform (AVP) systems using Solution Deployment Manager (SDM). Before you begin If you are not able to use SDM in System Manager, then install Avaya SDM Client on your Windows workstation. Upload the Avaya Aura MS 7.7 OVA file to an SDM software library or to your Windows workstation if you are using Avaya SDM Client. Obtain the following network configuration settings for the new VM. These settings can be from an existing system if you are redeploying the Avaya Aura MS OVA file. - Hostname - IP address - Netmask - Gateway IP address - Network domain - IP address of the DNS servers - IP address of the NTP servers Ensure that the required network interfaces are connected before deploying the OVA. The AVP and Utility Services IP addresses are available on NIC 1. Media server network interfaces are selected at the time of deployment and use a free network interface controller starting with NIC 4. NIC 1 is the connection for AVP and Utility Services management. The NIC you choose for the media server traffic and management during deployment must be on the same subnet as NIC1. To determine the current NIC configuration on the system and to make changes to the NIC configuration, see the Network chapter in Migrating and Installing Avaya Appliance Virtualization Platform. If you are redeploying an Avaya Aura MS VM appliance, ensure that you remove the current Avaya Aura MS VM from SDM. Procedure 1. To gain access to the SDM Dashboard, log in to System Manager and navigate to Services > Solution Deployment Manager or launch the Avaya SDM Client on your Windows computer. 2. Click VM Management. 3. Navigate the VM Management Tree and click on the name of the required AVP host. 4. On the Virtual Machines tab, click New. May 2016 Deploying and Updating Avaya Aura Media Server Appliance 14

15 Deploying the OVA file by using Solution Deployment Manager 5. In the Select Location and Host section, type a name for the new VM in the VM Name field. 6. In the Select Resource Pool and Data Store select the required data store from the Data Store drop-down menu. 7. In the Deploy OVA section, set Select Software Library to the library that contains the required OVA file. 8. In the Deploy OVA section, select the required Avaya Aura MS OVA file: If you are using SDM in System Manager, set the Select OVAs field to the required OVA file. If you are using SDM Client, select options in the Deploy OVA section that locate the required OVA file. Click Submit if required. 9. In the Network Settings section on the Configuration Parameters tab, enter the required network settings, as follows: a. Enter an IP address for the Avaya Aura MS in the Public IP address of the application field. The IP address you enter must be on the same subnet as AVP and Utility Services. b. Enter a hostname for the VM in the Short Hostname field. c. Enter the Network domain, Public interface netmask, Default gateway, and DNS Servers as required for your network. 10. In the System Time Settings section on the Configuration Parameters tab, enter the optional time settings. 11. In the Customer Login Settings section, on the Configuration Parameters, enter a Login Name and Password for your customer account. 12. On the Network Parameters tab, in the Management field, select a NIC for the media server. The NIC you select must be on the same subnet as AVP and Utility Services. 13. Click Deploy.. The system displays the end user license agreement. 14. Read the license agreement and click Accept. 15. To monitor the status of the deployment, click on the Virtual Machines tab. 16. (Optional) To monitor individual steps of the deployment process, click on Status Details in the Current Action Status column for the VM you are deploying. May 2016 Deploying and Updating Avaya Aura Media Server Appliance 15

16 Chapter 4: Deploying in the VMware virtualized environment System requirements The Avaya Aura MS appliance is deployed using a vsphere client connected to a vcenter or directly to a standalone ESXi host. You can deploy an Avaya Aura MS 7.7 appliance in an ESXi 5.1 or an ESXi 5.5 vsphere system. The ESXi host must meet the following system requirements: CPU Memory Disk space Network bandwidth ESXi host resource Requirement The core processor speed must be at least 2294 MHz. The total number of ESXi host vcpus cannot exceed the total number of physical CPUs. Each media server appliance requires 4 vcpus. Minimum 4670 MB of memory must be available for reservation and to accommodate 62 MB of overhead above the configured memory size of 4608 MB. Minimum 52 GB of available disk storage must be available in the ESXI datastore. A dedicated pair of 1 Gbps network interfaces must be available in a teamed, failover configuration. Alternatively, 1 Gbps of dedicated bandwidth on a pair of 10 Gbps network interfaces must be available in a teamed, failover configuration. The following vsphere features are not supported and must not be configured for Avaya Aura MS appliances: vmotion for running VMs Storage vmotion High Availability Fault tolerance VM snapshots, which adversely impact the VM disk and CPU performance May 2016 Deploying and Updating Avaya Aura Media Server Appliance 16

17 Best practice recommendations Best practice recommendations Use the following best practices to deploy the Avaya Aura MS appliance in the VMware virtualized environment: All physical servers that can host a VM must have the same CPU, memory, and networking specifications. Do not modify the CPU or memory reservation that are set for Avaya Aura MS OVA. Physical CPUs on the host must not be oversubscribed with respect to vcpu count across all VMs that share the host with the media server. A physical CPU refers to a physical CPU core and not to a hyper thread. For example, the total number of vcpus across all VMs on an ESXi host that has 12 physical cores with 24 hyper-threads, must not exceed 12. Note: This recommendation prevents CPU oversubscription. Therefore, the CPU reservation of the media server VM effectively enforces the minimum CPU core speed of the underlying hardware. The VM fails to start if the underlying hardware does not meet the core speed requirements. For maximum system performance, ensure that the energy savings features are disabled or that the maximum performance settings are enabled in the server BIOS. When deploying the OVA file, select Thick Provision Lazy Zeroed option for the VM virtual disks. If the physical network interfaces on the ESXi host are 10 Gbps interfaces, then NetIOC and traffic shaping must be performed. NetIOC and traffic shaping must allocate 1 Gbps of network bandwidth for the Avaya Aura MS VM. Old media server backup files must be removed to maintain free space on the system. Obtaining Avaya Aura MS OVA About this task You can download Avaya Aura MS OVA from the Avaya Product Licensing and Delivery System (Avaya PLDS) at You can also order DVDs containing the OVA using the following details: Material ID: Material Description: AAMS R7 MEDIA DVD - OVA DVD Label: Avaya Aura Media Server 7.7 Virtual Appliance for AVP and VMware Next steps Deploy the OVA file using vspere Client. May 2016 Deploying and Updating Avaya Aura Media Server Appliance 17

18 Deploying in the VMware virtualized environment Deploying the OVA file by using vsphere Client Before you begin Install the vsphere Client Windows application on the workstation. Alternatively, follow the procedure to use vsphere web client. Obtain the Avaya Aura MS 7.7 OVA file and save it on the workstation where you will run vsphere Client to configure the new VM. Obtain the following networking configuration settings for the new VM. These settings can be from an existing system if you are redeploying the Avaya Aura MS OVA file. - Hostname - IP address - Netmask - Gateway IP address - Network domain - IP address of the DNS servers - IP address of the NTP servers Ensure that you turn off the current Avaya Aura MS VM appliance. Procedure 1. Log in to the VMware host by using the vsphere Client Windows application provided by VMware. 2. Navigate to Home > Inventory > Hosts and Clusters. 3. Expand the inventory tree of hosts and clusters to locate and select the target deployment host. 4. From the menu, click File > Deploy OVF Template. 5. To locate the required Avaya Aura MS OVA file, click Browse. Select the required file and click Open. 6. Review the file selection and click Next. 7. Confirm the properties of the OVA file that you selected on the OVF Template Details page, and click Next. 8. To accept the End User License Agreement, click Accept, and click Next. 9. Enter a name for the new Avaya Aura MS VM, and click Next. 10. Select the required datastore for the new VM from the list, and click Next. 11. Select the Thick Provision Lazy Zeroed disk format option, and click Next. 12. Select the required destination network, and click Next. 13. Configure the details for the new VM on the Properties page, and click Next. May 2016 Deploying and Updating Avaya Aura Media Server Appliance 18

19 Deploying the OVA file by using vsphere web client 14. On the Ready to Complete page, verify the options. a. If the values are incorrect, click Back to make changes. b. Do not select the Power on after deployment option. c. If the values are correct, click Finish. Wait for the system to complete the deployment. The time taken to complete the deployment depends on the speed of the network connection and server. Tip: You can alter the configuration settings later by running the netsetup command in a Linux shell. 15. Locate the new VM in the inventory list, right-click on the VM entry in the list of the vsphere Client window, and click Power > Power On. 16. (Optional) To open a console window on your VM, right-click the VM entry in the inventory list and click Open Console. A console window displays the progress of the VM system initializing. 17. When the VM initialization is complete, you can log in by using the customer account that you set up earlier. 18. Perform the Updating VMware Tools procedure. Related links Updating VMware Tools on page 23 Deploying the OVA file by using vsphere web client About this task The steps in this procedure use the vsphere web client, which runs in a web browser. Alternatively, follow the procedure to use the vsphere Client, which is a Windows application you install on the workstation. Before you begin Obtain the Avaya Aura MS 7.7 OVA file. Save the file on the workstation where you will run vsphere web client to configure the new VM. Obtain the following networking configuration settings for the new VM. These settings can be from an existing system if you are redeploying Avaya Aura MS OVA. - Hostname - IP address - Netmask - Gateway IP address - Network domain May 2016 Deploying and Updating Avaya Aura Media Server Appliance 19

20 Deploying in the VMware virtualized environment - IP address of the DNS servers - IP address of the NTP servers Ensure that you turn off the current Avaya Aura MS VM appliance. Procedure 1. Log in to the VMware host by using the vsphere web client: 2. In the vsphere Web Client navigator area on the left, click vcenter. 3. In Inventory Trees, click Hosts and Clusters. 4. Expand the inventory tree of hosts and clusters to locate and select the target deployment host. 5. From the menu, right-click the host and select Deploy OVF Template. 6. (Optional) If the Client Integration Access Control window pops up, click Allow. 7. For 1a Select source, select Local file, and click Browse. 8. From the file filter drop-down menu in the lower right of the window, click OVA Packages (*.ova). 9. Select the required Avaya Aura MS OVA file, and click Next. 10. Confirm the properties of the OVA file that you selected on the Review details page, and click Next. 11. To accept the End User License Agreement, click Accept and Next. 12. Enter a name for the new Avaya Aura MS VM, and click Next. 13. Expand the tree under the vcenter server and select the required datacenter folder, and click Next. 14. Select Thick Provision Lazy Zeroed for the virtual disk format. 15. Select the required destination datastore, and click Next. 16. Select the required destination network, and click Next. 17. Expand Network Settings and configure the network details for the new VM on the Customize template page. 18. Expand System Time Settings and configure the time settings. 19. Expand Customer Login Settings and configure the account settings, click Next. 20. On the Ready to complete page, verify the options: a. If the values are incorrect, click Back to make changes. b. Do not select the Power on after deployment option. c. If the values are correct, click Finish. May 2016 Deploying and Updating Avaya Aura Media Server Appliance 20

21 Deploying the OVA file without using vcenter Wait for the system to complete deployment. The time that the system requires to complete the deployment depends on the speed of the network connection and server. The system displays the progress in Recent Tasks > All. Tip: You can alter the configuration settings later by running the netsetup command in a Linux shell. 21. Click the refresh arrow ( ) located to the left of your login ID at the top of the vsphere Web Client page. The system updates the inventory list and displays the new VM. 22. Select the new VM in the inventory list of the vsphere web client window and click the Summary tab. 23. Select Power On from the Actions menu. 24. (Optional) To open a console page on your VM, click Launch Console on the Summary tab. A console window displays the progress of the VM system initializing. 25. When the VM initialization is complete, you can log in by using the customer account that you set up earlier. 26. Perform the Updating VMware Tools procedure. Related links Updating VMware Tools on page 23 Deploying the OVA file without using vcenter Before you begin Install the vsphere Client Windows application on the workstation. Obtain the Avaya Aura MS 7.7 OVA file. Save the file on the workstation where you will run vsphere Client to configure the new VM. Obtain the following network configuration settings for the new VM. These settings can be from an existing system if you are redeploying Avaya Aura MS OVA. - Hostname - IP address - Netmask - Gateway IP address - Network domain - IP address of the DNS servers - IP address of the NTP servers May 2016 Deploying and Updating Avaya Aura Media Server Appliance 21

22 Deploying in the VMware virtualized environment Ensure that you turn off the current Avaya Aura MS appliance. Procedure 1. Log in to the VMware host using the vsphere Client Windows application provided by VMware. 2. Navigate to Home > Inventory, and select the target deployment host in the inventory list. 3. From the menu, click File > Deploy OVF Template. 4. To locate the required Avaya Aura MS OVA file, click Browse. Select the required file and click Open. 5. Review the file selection and click Next. 6. Review the OVF template details, and click Next. 7. To accept the End User License Agreement, click Accept and Next. 8. Enter a name for the new Avaya Aura MS VM, and click Next. 9. Select the Thick Provision Lazy Zeroed disk format option, and click Next. 10. Select the required destination network, and click Next. 11. On the Ready to Complete page, verify the options: a. If the values are incorrect, click Back to make changes. b. Do not select the Power on after deployment option. c. If the values are correct, click Finish. Wait for the system to complete the deployment. The time required to complete the deployment depends on the speed of the network connection and server. 12. Locate and right-click the new VM in the inventory list of the vsphere Client window, and click Power > Power On. 13. Immediately open a console window on the VM. a. Right-click the VM entry in the inventory list. b. Click Open Console. A console window displays the progress of the VM system. 14. Double-click the console window to establish keyboard focus in the console. 15. Read the End User License Agreement. Use the spacebar to scroll through the text. Type yes to accept the agreement and proceed. 16. After the VM system initialization is complete, you are prompted to configure the VM. Type Y to proceed. 17. Enter the network settings, date, time, and customer account information for the server. For Enable static route, use the default value of N. May 2016 Deploying and Updating Avaya Aura Media Server Appliance 22

23 Updating VMware Tools Tip: You can alter the configuration settings later by running the netsetup command in a Linux shell. 18. Perform the Updating VMware Tools procedure. Related links Updating VMware Tools on page 23 Updating VMware Tools About this task Perform the following procedure to update the version of VMware Tools to the version required by the ESXi host. Note: Do not update VMware Tools when Avaya Aura MS is deployed on AVP. Before you begin Perform updates during scheduled maintenance times. Ensure that the VM is running. Ensure that there is no traffic on Avaya Aura MS. Back up the system. In case of unforeseen problems during the update, you can redeploy the appliance and use the backup to restore the system to the current configuration. Ensure that you apply the tool updates to one node at a time in a cluster configuration while the other nodes in the cluster maintain service. Procedure 1. Determine if you need to update the VMware tools. If the VMware Tools field on the Summary tab indicates (Out-of-date) then update VMware Tools. If you are using vsphere Web Client: a. Click Interactive Upgrade. b. Select Interactive upgrade. c. Click Upgrade. Monitor the Recent Tasks section of vsphere Web Client page. Wait for the Initiated VMware Tools Installer Mount task to be complete. A green checkmark indicates that the task is complete. May 2016 Deploying and Updating Avaya Aura Media Server Appliance 23

24 Deploying in the VMware virtualized environment Result If you are using vsphere Client: a. Select the VM from the list of VMs. b. Right-click the VM and select Guest > Install/Upgrade VMware Tools. c. Select Interactive Tools Upgrade and click OK. Monitor the Recent Tasks section of vsphere Client and wait for the Initiated VMware Tools Installer Mount task to complete. 2. Using the customer login credentials, open a Linux shell and run the following command to update VMware Tools: updatevmwaretools 3. Review the important messages displayed by the tool. 4. Type Y and press Enter to update VMware Tools. After the tool update is complete, the VM is automatically restarted to apply the changes. Note: If vsphere Client displays a question about a locked CD-ROM door, accept the default answer No and click OK to continue. Important: The update is complete after a few minutes. Do not interrupt the update by typing Control+C or by using any other method that ends the updatevmwaretools process while it is running. Interrupting the VMware tools update can leave the tools in an inoperable state, requiring reinstallation. The VM also becomes unstable requiring you to redeploy the VM. 5. After the restart is complete, verify that the VMware Tools update is successful. The VMware Tools field on the Summary tab for the VM indicates (Current) after a successful update. If you are using vsphere Web Client, refresh the web page to update the display with the latest status May 2016 Deploying and Updating Avaya Aura Media Server Appliance 24