Deploying Avaya Aura Utility Services

Transcription

1 Deploying Avaya Aura Utility Services Release Issue 3 May 2017

2 , Avaya, Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Documentation means information published in varying mediums which may include product information, operating instructions and performance specifications that are generally made available to users of products. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of Documentation unless such modifications, additions, or deletions were performed by or on the express behalf of Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked websites referenced within this site or Documentation provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on Avaya hardware and software. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product while under warranty is available to Avaya customers and other parties through the Avaya Support website: getgenericdetails?detailid=c under the link Warranty & Product Lifecycle or such successor site as designated by Avaya. Please note that if You acquired the product(s) from an authorized Avaya Channel Partner outside of the United States and Canada, the warranty is provided to You by said Avaya Channel Partner and not by Avaya. Licenses THE SOFTWARE LICENSE TERMS 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 types Designated System(s) License (DS). End User may install and use each copy or an Instance of the Software only on a number of Designated Processors up to the number indicated in the order. Avaya may require the Designated Processor(s) to be identified in the order by type, serial number, feature key, Instance, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A Unit means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Units may be linked to a specific, identified Server or an Instance of the Software. Database License (DL). End User may install and use each copy or an Instance of the Software on one Server or on multiple Servers provided that each of the Servers on which the Software is installed communicates with no more than one Instance of the same database. CPU License (CP). End User may install and use each copy or Instance of the Software on a number of Servers up to the number indicated in the order provided that the performance capacity of the Server(s) does not exceed the performance capacity specified for the Software. End User may not reinstall 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 the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use 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

3 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. 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 Change History... 6 Warranty... 7 Chapter 2: Architecture overview... 8 Utility Services overview... 8 Avaya Aura Virtualized Environment overview... 8 Virtualized components... 9 Deployment guidelines... 9 Services Port VM Utility Services deployment mode Services Port and Utility Services mode Services Port-only mode Utility Services only mode Out of Band Management Enabling or disabling the Out of Band Management feature for Utility Services Assigning a static route to the Out of Band Management network Enabling IP forwarding using Services Port VM for Utility Services Browser support Chapter 3: Planning and configuration Planning Downloading software from PLDS Supported servers S8300E support for Utility Services Server hardware and resources for VMware Utility Services resource requirements Software requirements VMware software requirements New plugin support on Utility Services Chapter 4: Deploying and configuring Utility Services Open Virtual Application Deployment methods Installing the Solution Deployment Manager client on your computer Deploying the Utility Services OVA file Deployment and configuration on the ESXi host through the vsphere client Deployment and configuration of Utility Services OVA on VCenter vsphere client Installation of the RFA Authentication file on Utility Services Installing software patches Viewing the status of the NTP server Deployment of cloned and copied OVAs May 2017 Deploying Avaya Aura Utility Services 4

5 Contents Chapter 5: Configuration Configuring the virtual machine automatic startup settings Post deployment reconfiguration Reconfiguring the Utility Services OVA through the ESXi host Reconfiguring the Utility Services OVA through vcenter Updating System Manager details in the /etc/hosts file Chapter 6: Maintenance Upgrading the Utility Services virtual machine Updating patches and service packs Backup and restore Include/Exclude IP Firmware option Disaster Recovery Creating a backup of Utility Services Restoring a backup of Utility Services Transferring files using WinSCP Chapter 7: Resources Documentation Finding documents on the Avaya Support website Training Viewing Avaya Mentor videos Support Appendix A: Best Practices for VMware performance and features BIOS Intel Virtualization Technology Dell PowerEdge Server HP ProLiant Servers VMware Tools Timekeeping VMware networking best practices Thin vs. thick deployments VMware Features VMware Snapshots VMware Cloning VMware High Availability VMware vmotion VMware Storage vmotion Appendix B: PCN and PSN notifications PCN and PSN notifications Viewing PCNs and PSNs Signing up for PCNs and PSNs Appendix B: Glossary May 2017 Deploying Avaya Aura Utility Services 5

6 Chapter 1: Introduction Purpose This document provides installation, configuration, initial administration, and basic maintenance checklists and procedures. This document is intended for people who install and configure a verified reference configuration at a customer site. Change History The following changes have been made to this document since the last issue: Issue Date Summary of changes 3.0 March 2017 Updated the following sections for clarity: Assigning a static route to the Out of Band Management network Network Parameters and Configuration Parameters field descriptions Properties field descriptions on the vsphere client Properties field descriptions for vcenter vsphere client Updating System Manager details in the /etc/hosts file 2.0 May 2016 Added the Installing software patches section. Added the Supported servers section. Added the Out of Band Management section with information about full out-of- Table continues May 2017 Deploying Avaya Aura Utility Services 6

7 Warranty Issue Date Summary of changes band management configuration. 1.0 August 2015 Initial draft Added the New plug-in support on Utility Services section. Added VMware vcenter Server 6.0 in the VMware software requirements section. Warranty Avaya provides a 90-day limited warranty on Communication Manager. To understand the terms of the limited warranty, see the sales agreement or other applicable documentation. In addition, the standard warranty of Avaya and the details regarding support for Communication Manager in the warranty period is available on the Avaya Support website at under Help & Policies > Policies & Legal > Warranty & Product Lifecycle. See also Help & Policies > Policies & Legal > License Terms. May 2017 Deploying Avaya Aura Utility Services 7

8 Chapter 2: Architecture overview Utility Services overview Avaya Aura Utility Services provides the tools to help analyze, configure, optimize, and maintain the Avaya Aura applications in a VMware solution. With Avaya solution a VMware user to improve business collaboration and communication by adding UC collaboration features such as Bring Your Own Device (BYOD), mobility, and video supported by a virtualized server infrastructure. Avaya Aura Virtualized Environment overview Avaya Aura Virtualized Environment integrates real-time Avaya Aura applications with VMware virtualized server architecture. Using Avaya Aura Virtualized Environment, customers with a VMware IT infrastructure can upgrade to the next release level of collaboration using their own VMware infrastructure. For customers who need to add more capacity or application interfaces, Avaya Aura applications on VMware offer flexible solutions for expansion. For customers who want to migrate to the latest collaboration solutions, Avaya Aura Virtualized Environment provides a hardware-efficient simplified solution for upgrading to the latest Avaya Aura release and adding the latest Avaya Aura capabilities. The Virtualized Environment project applies only for Avaya Appliance Virtualization Platform and customer VMware, and does not include any other industry hypervisor. This document uses the following terms, and at times, uses the terms interchangeably. server and host reservations and configuration values Deployment considerations The following manage the deployment to the blade, cluster, and server: Avaya Appliance Virtualization Platform from System Manager Solution Deployment Manager or the Solution Deployment Manager client VMware vcenter and VMware vsphere May 2017 Deploying Avaya Aura Utility Services 8

9 Virtualized components Virtualized components Software component ESXi Host ESXi Hypervisor vsphere Client vcenter Server Appliance Virtualization Platform Solution Deployment Manager Open Virtualization Appliance (OVA) Description The physical machine running the ESXi Hypervisor software. A platform that runs multiple operating systems on a host computer at the same time. vsphere Client is an application that installs and manages virtual machines. vsphere Client connects to a vcenter server or directly to an ESXi host if a vcenter Server is not used. The application is installed on a personal computer or accessible through a web interface. vcenter Server provides centralized control and visibility at every level of the virtual infrastructure. vcenter Server provides VMware features such as High Availability and vmotion. Avaya-provided virtualization turnkey solution that includes the hardware and all the software including the VMware hypervisor. Centralized software management solution of Avaya that provides deployment, upgrade, migration, and update capabilities for the Avaya Aura virtual applications. The virtualized OS and application packaged in a single file that is used to deploy a virtual machine. Deployment guidelines The high-level deployment steps are: 1. Deploy the OVA or OVAs. 2. Configure the application. 3. Verify the installation. The deployment guidelines for the virtual appliances are: Deploy as many virtual appliances on the same host as possible. Deploy the virtual appliances on the same cluster if the cluster goes beyond the host boundary. Segment redundant elements on a different cluster, or ensure that the redundant elements are not on the same host. Create a tiered or segmented cluster infrastructure that isolates critical applications, such as Avaya Aura applications, from other virtual machines. Plan for rainy day scenarios or conditions. Do not configure resources only for traffic or performance on an average day. Do not oversubscribe resources. Oversubscribing affects performance. Monitor the server, host, and virtual appliance performance. May 2017 Deploying Avaya Aura Utility Services 9

10 Architecture overview Important: The values for performance, occupancy, and usage can vary greatly. The blade server might run at 5% occupancy, but a virtual machine might run at 50% occupancy. Note that a virtual machine behaves differently when the CPU usage is higher. Services Port VM From Release 7.0, Utility Services replaces the console domain and runs the Services Port connection. For previous releases, the Services Port connection was run using dom0 on System Platform. The terms Services Port VM and Utility Services are interchangeable. You can deploy the Services Port VM on all Avaya appliance offers in 7.0. you can connect a laptop to the service port of the server or the Avaya Virtualization Platform(AVP) host. To gain access to the applications, you must provide authentication details.. Services Port VM is available only with the Virtualized Appliance offer for Avaya supported servers. For information about IP forwarding, see Enabling IP forwarding using Services Port VM for Utility Services. By using the admin command, you can either enable or disable the IP Forwarding feature, which is available only on Utility Services. Utility Services does not split management and user traffic, when Out of Band Management is disabled. If Out of Band Management is enabled, Utility Services splits the management and user traffic. Utility Services supports the out-of-band management feature through the Services Port VM. Related links Utility Services deployment mode on page 10 Services Port and Utility Services mode on page 11 Services Port-only mode on page 11 Utility Services only mode on page 12 Enabling IP forwarding using Services Port VM for Utility Services on page 15 Utility Services deployment mode Utility Services supports the following deployment modes for different scenarios: full_functionality: To support full Utility Services and Services Port VM. utility_ services_only: To support full Utility Services only. services_port_only: To support Services Port VM only. May 2017 Deploying Avaya Aura Utility Services 10

11 Services Port VM You can select the mode of operation only at the time of deployment. You cannot change the deployment mode later. full_functionality is the default option when deployed on an Avaya Appliance by installing an Avaya ESXi Hypervisor. utility_ services_only option is applicable to a customer-supplied ESXi Hypervisor and does not require configuration as the Services vswitch is not present. services_port_only option restricts the VM to only offer Services Port VM operation on an Avaya ESXi Hypervisor. Related links Services Port VM on page 10 Services Port and Utility Services mode You can use Services Port VM in the Services Port and Utility Services mode to access all Utility Services functions and Services Port VM routing. You can also access VM applications deployed on the Avaya ESXi Hypervisor. You can select the Services Port and Utility Services mode at the time of deployment time. But you cannot change the mode later. Changing the mode requires that Services Port VM be deleted and redeployed. Related links Services Port VM on page 10 Services Port-only mode You can use the Services Port-only mode to either shut down or permanently disable additional functions of Utility Services while running applications that do not require additional services. The following applications do not require additional services: MyPhone DHCP Server TFTP file server HTTP file server Administration tools You can select the Services Port-only mode at the time of deployment. But you cannot change the mode later. Changing the mode requires that Services Port VM be deleted and redeployed. During upgrades and updates, the selection mode does not interfere with system backup or restore. Related links Services Port VM on page 10 May 2017 Deploying Avaya Aura Utility Services 11

12 Architecture overview Utility Services only mode You can use the Services Port VM support for a Utility Services only mode for deployment without enabling the services port. Services port is not part of the VE offer. You can select the Utility Services only mode at the time of deployment. Once you select the mode, you cannot change the mode later. If you need to change the mode, you must delete and redeploy Services Port VM. Related links Services Port VM on page 10 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 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 2017 Deploying Avaya Aura Utility Services 12

13 Enabling or disabling the Out of Band Management feature for Utility Services 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 If a network is not mentioned for service when Out of Band Management is enabled, the service must be disabled on that interface. Enabling or disabling the Out of Band Management feature for Utility Services Procedure 1. Start an SSH session. 2. Log in to Utility Services as admin. 3. In the command line, perform one of the following: a. To enable Out of Band Management, type sudo /opt/avaya/common_services/ vami_set_oobm OOBM_Enabled. b. To disable Out of Band Management, type sudo /opt/avaya/common_services/ vami_set_oobm OOBM_Disabled. Assigning a static route to the Out of Band Management network May 2017 Deploying Avaya Aura Utility Services 13

14 Architecture overview About this task Use the procedure to assign static route to the Out of Band Management network on Ethernet Interface 2. Use the command only to pass through a gateway to reach machines that perform administration of Utility Services. You can assign a static route only from the command line interface. The vami_set_static command is available only in Utility Services Release Procedure 1. Start an SSH session. 2. Log in to Utility Services as admin. 3. In the command line, type /opt/avaya/common_services/vami_set_static a <route> <netmask> <via> to assign the static route. You can use the below commands. Command /opt/avaya/common_services/vami_set_static a <route> <netmask> <via> /opt/avaya/common_services/vami_set_static d /opt/avaya/common_services/vami_set_static r Description Assigns the static route. Displays the static route. Removes the static route. Example /opt/avaya/common_services/vami_set_static a Adding a static route of / via /opt/avaya/common_services/vami_set_static -d Output : ADDRESS0= NETMASK0= GATEWAY0= /opt/avaya/common_services/vami_set_static -r Output: The Static Route currently configured is: ADDRESS0= NETMASK0= GATEWAY0= The Static Route has been removed May 2017 Deploying Avaya Aura Utility Services 14

15 Enabling IP forwarding using Services Port VM for Utility Services Enabling IP forwarding using Services Port VM for Utility Services About this task You can access virtual machines on Utility Services by connecting a laptop to the Services Port VM. By default, the system enables IP forwarding. To configure IP forwarding manually, use the Services Port VM. For security reasons, you must always disable IP forwarding after finishing your task. Procedure 1. Start an SSH session. 2. Log in to Utility Services as admin. 3. In the command line, perform one of the following: Example To enable IP forwarding, type IP_Forward enable. To disable IP forwarding, type IP_Forward disable. To view the status of IP forwarding, type IP_Forward status. IP_Forward enable Enabling IP Forwarding Looking for net.ipv4.ip_forward in /etc/sysctl.conf Status of IP Forwarding..Enabled Browser support Services Port VM complies with the CEC browser support requirement that includes the following browsers: Internet Explorer version 9 Internet Explorer version 9 requires that SSL access is DISABLED and TLS access is ENABLED. If the user does not make the change, the user cannot access Utility Services Administration pages. Internet Explorer version 10 Internet Explorer version 11 Microsoft Edge (Spartan) Browser (included with Windows 10) Firefox version 43 Firefox version 44 May 2017 Deploying Avaya Aura Utility Services 15

16 Architecture overview Firefox version 45 May 2017 Deploying Avaya Aura Utility Services 16

17 Chapter 3: Planning and configuration Planning Ensure the customer completes the following steps before deploying the Utility Services OVA: # Action Notes 1 No license is required for Utility Services. However, the Remote Feature Activation (RFA) authentication file must be downloaded from AFS system and stored at a location from where a computer running the vsphere client can access the file. 2 Minimum of one ESXi host release 5.0 or later is required. The host must have at least one GB of RAM and 20 GB of storage. 3 The Utility Services OVA file must be downloaded from and stored at a location from where a computer running the vsphere client can gain access to the file. 4 Keep a copy of the license files for the Avaya Aura products so you can replicate with the new Host ID after the OVA file installation. You must ensure the license file copies are accessible. For information about downloading the ova file, see Downloading software from PLDS on page 17. Downloading software from PLDS When you place an order for an Avaya PLDS-licensed software product, PLDS creates the license entitlements of the order and sends an notification to you. The includes a license activation code (LAC) and instructions for accessing and logging into PLDS. Use the LAC to locate and download the purchased license entitlements. May 2017 Deploying Avaya Aura Utility Services 17

18 Planning and configuration In addition to PLDS, you can download the product software from using the Downloads and Documents tab at the top of the page. Only the latest service pack for each release is posted on the support site. Previous service packs are available only through PLDS. Procedure 1. Enter in your Web browser to access the Avaya PLDS website. 2. Enter your login ID and password. 3. On the PLDS home page, select Assets. 4. Click View Downloads. 5. Click on the search icon (magnifying glass) for Company Name. 6. In the %Name field, enter Avaya or the Partner company name. 7. Click Search Companies. 8. Locate the correct entry and click the Select link. 9. Enter the Download Pub ID. 10. Click Search Downloads. 11. Scroll down to the entry for the download file and click the Download link. 12. In the Download Manager box, click the appropriate download link. The first link, Click to download your file now, uses the Download Manager to download the file. The Download Manager provides features to manage the download (stop, resume, auto checksum). The click here link uses your standard browser download and does not provide the download integrity features. 13. If you use Internet Explorer and get an error message, click the install ActiveX message at the top of the page and continue with the download. 14. Select a location where you want to save the file and click Save. 15. If you used the Download Manager, click Details to view the download progress. Supported servers In the Avaya-appliance offer, you can deploy Utility Services Release 7.0 and later on the following Avaya-provided servers: Avaya S8300D and S8300E HP ProLiant DL360 G7 May 2017 Deploying Avaya Aura Utility Services 18

19 Server hardware and resources for VMware Dell PowerEdge R610 HP ProLiant DL360p G8 Dell PowerEdge R620 HP ProLiant DL360 G9 Dell PowerEdge R630 CallPilot 1006r server Related links S8300E support for Utility Services on page 19 S8300E support for Utility Services The S8300E server is based on a 2.0 GHz, dual core Intel Ivy Bridge processor. Utility Services Release 7.0 and later supports the S8300E server. The S8300E server is certified by VMware as VMware Ready. For more information see, Avaya Aura Communication Manager Hardware Description and Reference, Related links Supported servers on page 18 Server hardware and resources for VMware VMware offers compatibility guides that list servers, system, I/O, storage, and backup compatibility with VMware infrastructure. For more information about VMware-certified compatibility guides and product interoperability matrices, see Utility Services resource requirements In the customer environment, performance of Utility Services might vary from the average results. The following resources must be available on the ESXi host before deploying the Utility Services virtual machine: May 2017 Deploying Avaya Aura Utility Services 19

20 Planning and configuration VMware resource vcpu Core 1 Minimum CPU speed based on Xeon E5620 or equivalent processor CPU Reservation Memory Memory reservation Storage reservation Shared NICs Network Utilization Value 2.4 GHz n/a 1 GB n/a IOPS GB Utility Services Release 7.0 and later supports the Flexible Deployment option that supports the following: Default Resources: is supported by 1 GB of RAM for Utility Services and Service Port functionality. Minimal Resources: is supported by 512 MB of RAM for Utility Services and Service Port functionality and is intended for S8300D deployment only. Utility Services has three shared NICs, one each for Public, Services and Out of Band Management. Out of Band Management uses NIC 2. 5 Mbps Software requirements Utility Services Release 7.0 and later can be deployed on VMware vsphere Release 5.0, VMware vsphere Release 5.1, VMware vsphere Release 5.5, or VMware vsphere Release 6.0. VMware vsphere Release 4.1 does not support Utility Services. The Utility Services VMware virtualization environment is packaged as a virtual appliance ready for deployment on the VMware-certified hardware. The following table lists the software requirements: Utility Services has three shared NICs, one each for Public, Services and Out of Band Management. Out of Band Management uses NIC 2. Equipment Software Release VMware vcenter Server 5.0, or 5.1, or 5.5, or 6.0 VMware vsphere Client 5.0, or 5.1, or 5.5, or 6.0 VMware ESXi Host 5.0, or 5.1, or 5.5, or 6.0 Table continues May 2017 Deploying Avaya Aura Utility Services 20

21 VMware software requirements Equipment Software Release VMware Studio , VMware Tools , Avaya Aura Utility Services with Appliance Virtualization Platform or later with VMware software requirements Avaya Aura Utility Services in a virtualized environment supports the following VMware 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 To view compatibility with other solution releases, see VMware Product Interoperability Matrices at ESXi 4.1 is not supported. New plugin support on Utility Services Utility Services supports a plugin mechanism for upgrade from Release 7.0 to later releases. Solution Deployment Manager in System Manager needs to record information of existing application and virtual machine while the upgrade is in process. Types of information recorded are: IP address Networking information Configuration information File settings for the application May 2017 Deploying Avaya Aura Utility Services 21

22 Planning and configuration The plugin does not record and provide admin user names and passwords and System Manager enrollment password. Solution Deployment Manager uses key value pair to access the output information from the plugin and helps automatically deploy the new virtual machine. For more information, see Upgrading Avaya Aura System Manager to Release May 2017 Deploying Avaya Aura Utility Services 22

23 Chapter 4: Deploying and configuring Utility Services Open Virtual Application Deployment methods Use one of the following methods to deploy and configure Utility Services Open Virtual Application (OVA): Deployment through Avaya Aura System Manager, Solution Deployment Manager on Avayaprovided servers or through the Solution Deployment Manager client. For information about deploying Utility Services, see Deploying Avaya Aura applications from System Manager. Do not use DHCP for Solution Deployment Manager deployments and use static IP addresses. Direct deployment on the ESXi host through the vsphere client. Deployment on vcenter through the vsphere client. 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. Click Next only once, and wait for the installer to load the next screen. May 2017 Deploying Avaya Aura Utility Services 23

24 Deploying and configuring Utility Services Open Virtual Application 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, Windows bit, or Windows 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. 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 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_ _44.zip file from the Avaya PLDS website at On the Avaya PLDS website, at click Support by Products > Downloads, and provide the product System Manager, and version as 7.0.x. May 2017 Deploying Avaya Aura Utility Services 24

25 Deployment methods 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_ _44.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. 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 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. May 2017 Deploying Avaya Aura Utility Services 25

26 Deploying and configuring Utility Services Open Virtual Application 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. 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 feature pack, and then deploy all other applications one at a time. 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. May 2017 Deploying Avaya Aura Utility Services 26

27 Deployment methods 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. 9. In the Network Parameters section, ensure that the following fields are preconfigured: Public Services: Only for Utility Services 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 feature pack. 15. Reboot the Utility Services virtual machine. Next steps 1. Deploy System Manager and install the Release 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. May 2017 Deploying Avaya Aura Utility Services 27

28 Deploying and configuring Utility Services Open Virtual Application Network Parameters and Configuration Parameters field descriptions During the Utility Services deployment, if you do not know the Communication Manager IP Address, System Manager IP Address, or Enrollment Password, then use the dummy values. Dummy values must pass validation. Use the localhost default for the IP address, and Dummy as the password. Name Configuration Parameters Communication Manager IP Description IP address of Communication Manager. Hostname 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. TImezone setting NTP Server IP Out of Band Management Mode The host name is regardless of the interface that is used to access. The Public interface is the default interface. 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. 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. 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. Table continues May 2017 Deploying Avaya Aura Utility Services 28

29 Deployment methods Name Description 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. For the Solution Deployment Manager client to connect to the services port features of Utility Services, change the IP address to on the computer of the technician Utility Services can gain access to the hypervisor and all virtual machines through the IP address 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. The default gateway should be configured for the Public network. You can use the vami_set_static command to allow a static route to be assigned to the OOBM network, enabling OOBM network to reach a second subnet. 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 The IP address for this interface. Table continues May 2017 Deploying Avaya Aura Utility Services 29

30 Deploying and configuring Utility Services Open Virtual Application Name Out of Band Management Netmask Description The netmask for this interface. Deployment and configuration on the ESXi host through the vsphere client Deploying the Utility Services OVA using vsphere client Procedure 1. Open the vsphere client. 2. In the vsphere client, enter the IP address of the vcenter server and the login credentials. 3. On the File menu, select Deploy OVF Template. 4. To select the file for deployment, use one of the following methods: If the OVA file is downloaded at a location accessible from your computer, click Browse and select the file. Click Next. If the OVA file is located on an HTTP server, enter the URL in the Deploy from a file or URL field. Click Next. 5. Verify the template details, and click Next. 6. Accept the End User License Agreement (EULA). Click Next. 7. In the Name field, assign a name of maximum 80 characters to the new virtual machine. Click Next. 8. Select the location to store the virtual machine files. Click Next. 9. Select Thick Provision Lazy Zeroed as the virtual disk format. Click Next. For more information about virtual disks, see Thin vs. thick deployments. 10. Verify the deployment settings and click Finish. Related links Thin vs. thick deployments on page 64 Configuring the Utility Services OVA using vsphere client Procedure 1. In the vsphere client, select the Utility Services virtual machine. 2. Click the Getting Started tab. 3. Click Power on the virtual machine. 4. Click the Console tab. 5. Log in to an account with administrative privileges. May 2017 Deploying Avaya Aura Utility Services 30

31 Deployment methods 6. Run the /opt/avaya/common_services/vmware_conf.sh command. 7. When the system prompts to continue, enter y. 8. For a standard direct ESXi install the mode of operation is Utility Services only. Enter the values for the following network entities: a. Default Gateway b. Hostname c. DNS d. IP address allocation for eth0 IP Address allocation for Eth0 and Eth2. For a direct ESXi deployment Eth2 is unused and the IP Address allocation can be left blank. For more information about the fields, see Properties field descriptions on the vsphere client. 9. To configure the timezone settings, select the region and the local area. 10. Enter the IP address of Communication Manager used for the Utility Services virtual machine. 11. Enter the IP address of the primary NTP server to be used for the Utility Services virtual machine. 12. The system installs the default authentication file. You must replace the file with the authentication file that you downloaded from RFA. For more information, see Installation of the RFA Authentication file on Utility Services. Related links Installation of the RFA Authentication file on Utility Services on page 37 Properties field descriptions on the vsphere client on page 31 Properties field descriptions on the vsphere client Name Default Gateway Description The IP address of the default gateway. x The default gateway should be configured for the Public network. You can use the vami_set_static command to allow a static route to be assigned to the OOBM network, enabling OOBM network to reach a second subnet. Table continues May 2017 Deploying Avaya Aura Utility Services 31

32 Deploying and configuring Utility Services Open Virtual Application Name Hostname DNS IP address allocation for eth0 Description The Linux hostname for the Utility Services virtual machine. The host name is regardless of the interface that is used to access. The Public interface is the default interface. The IP address of the Domain Name System (DNS) server. The IP address of Utility Services. Deployment and configuration of Utility Services OVA on VCenter vsphere client Deploying the Utility Services OVA on vcenter vsphere client Procedure 1. Open the vsphere client. 2. In the vsphere client, enter the IP address of the host vcenter server and the login credentials. 3. Login to vcenter, select the ESXi host to deploy the Utility Services. 4. On the File menu, select Deploy OVF Template. 5. To select the file to be deployed, use one of the following methods: If the OVA file is downloaded at a location accessible from your computer, click Browse and select the file. Click Next. If the OVA file is located on an HTTP server, enter the URL in the Deploy from a file or URL field. Click Next. 6. On the OVF Template Details screen, verify the template details, and click Next. 7. On the End User License Agreement screen, accept the End User License Agreement (EULA). Click Next. 8. On the Name and Location screen, in the Name field, assign a name of maximum 80 characters to the deployed template. Click Next. 9. On the Deployment Configuration menu, select one of the following: Default Resources: is supported by 1 GB of RAM for Utility Services and Service Port functionality. Minimal Resources: is supported by 512 MB of RAM for Utility Services and Service Port functionality and is intended for S8300 deployment only. 10. Select the location to store the virtual machine files. Click Next. May 2017 Deploying Avaya Aura Utility Services 32

33 Deployment methods 11. On the Disk Format screen, select Thick Provision Lazy Zeroed as the virtual disk format. Click Next. For more information about virtual disks, see Thin vs. thick deployments. 12. On the Network Mapping screen, verify the network interface that the OVF template uses and click Next. 13. On the IP Address Allocation screen, select an allocation scheme to allocate IP addresses. You must select Fixed. DHCP is not supported for Virtual Environment installation. 14. Select the IP Protocol, and click Next. 15. On the Properties screen, complete the following fields: a. In the Application section, complete the following fields: Communication Manager IP Hostname Timezone NTP Server IP Utility Services Mode Primary System Manager IP address for application registration Enrollment Password Confirmation password b. In the Networking section, complete the following fields: Public IP address Public Netmask Out of Band Management IP Address Out of Band Netmask Default Gateway DNS For more information about the fields, see Properties field descriptions for vcenter vsphere client. 16. On the Ready to Complete screen, verify the deployment settings and click Finish. Related links Thin vs. thick deployments on page 64 Viewing the status of the NTP server on page 41 May 2017 Deploying Avaya Aura Utility Services 33

34 Deploying and configuring Utility Services Open Virtual Application Configuring the Utility Services OVA on vcenter vsphere client Procedure 1. In the vsphere client, select the Utility Services virtual machine. 2. Click the Getting Started tab. 3. Click Power on the virtual machine. 4. Click Edit Virtual Machine Settings. The system displays a new window containing the details of the Utility Services virtual machine. 5. Click the Options tab. 6. Click Properties. 7. On the Properties screen, complete the following fields: a. In the Application section, complete the following fields: Communication Manager IP Hostname Timezone NTP Server IP Utility Services Mode Primary System Manager IP address for application registration Enrollment Password Confirmation password b. In the Networking section, complete the following fields: Public IP address Public Netmask Out of Band Management IP Address Out of Band Netmask Default Gateway DNS For more information about the fields, see Properties field descriptions for vcenter vsphere client. 8. Click OK. 9. The system installs the default authentication file. You must replace the default authentication file with the authentication file that you have downloaded from RFA. For more information, see Installation of the RFA Authentication file on Utility Services. Related links Installation of the RFA Authentication file on Utility Services on page 37 May 2017 Deploying Avaya Aura Utility Services 34

35 Deployment methods Viewing the status of the NTP server on page 41 Properties field descriptions for vcenter vsphere client on page 35 Properties field descriptions for vcenter vsphere client At the time of deploying Utility Services, if you do not know the Communication Manager IP Address, System Manager IP Address, or Enrollment Password then use the dummy values. Dummy values need to pass validation. Use the localhost default of for the IP addresses and use Dummy as the password. Name Communication Manager IP Hostname Timezone NTP Server IP Out of Band Management Mode Description The IP address of Communication Manager used for CDR collection, MyPhone, and Phone Firmware Manager. 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. The Linux hostname. The host name is regardless of the interface that is used to access. The Public interface is the default interface. The Linux standard timezone to be applied to the Utility Services virtual machine. The IP Address of the primary Network Time Protocol (NTP) server for the Utility Services virtual machine. The Out of Band Management mode in which you want to deploy. The options are as follows: OOBM_Enabled: Used to enable the Out of Band Management feature. OOBM_Disabled: Used to disable the Out of Band Management feature. OOBM_Disabled is the default setting. If the mode is set to OOBM_Disabled, then there is no need to configure the Out of Band Management elements. Table continues May 2017 Deploying Avaya Aura Utility Services 35

36 Deploying and configuring Utility Services Open Virtual Application Name Utility Services Mode Primary System Manager IP address for application registration Enrollment Password Confirmation password Public IP address Public Netmask Out of Band Management IP Address Description The Utility Services mode in which you want to deploy. 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. 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. This is 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. For the Solution Deployment Manager client to connect to the Services Port features of Utility Services, change the IP address to on the computer of the technician Utility Services can gain access to the hypervisor and all virtual machines through the IP address The Utility Services application provides application routing between the physical port and virtual applications. The IP address of System Manager that is required for application registration. For deployment on Appliance Virtualization Platform the real and valid values of IP Address of System Manager and the enrolment passwords are configured. Otherwise, these values can be artificial. The enrollment password. The confirmation password. The IP address for this interface. The netmask for this interface. The IP address for this interface. Table continues May 2017 Deploying Avaya Aura Utility Services 36

37 Deployment methods Name Out of Band Netmask Default Gateway DNS Description At the time of initial deployment, the values for Out of Band Management IP Address and Netmask are artificial. The real and valid values are configured at the starting time of OOBM operation. The netmask for this interface. The IP address of the default gateway. The default gateway should be configured for the Public network. You can use the vami_set_static command to allow a static route to be assigned to the OOBM network, enabling OOBM network to reach a second subnet. The IP address of the Domain Name System (DNS) server. Related links Viewing the status of the NTP server on page 41 Installation of the RFA Authentication file on Utility Services You must use one of the following methods to install the RFA Authentication file: Through the vsphere client Through the Utility Services Web page Installing the RFA Authentication file through the vsphere client Procedure 1. In the vsphere Client, select the Utility Services virtual machine. 2. Click the Getting Start tab. 3. Click Power on the virtual machine. 4. Click the console tab. 5. Log in with administrative privileges. 6. Rename the authentication file to asg_auth_file.xml using the mv source destination command, where source is the authentication file name. 7. Use scp or WinSCP to transfer files. For more information about transferring files using WinSCP, see Transferring files using WinSCP. May 2017 Deploying Avaya Aura Utility Services 37

38 Deploying and configuring Utility Services Open Virtual Application You can use the scp command to copy the authentication file to the Utility Services virtual machine. You must download the following programs to enable scp: Pscp.exe WinSCP 8. Depending on the privilege of the account, move the authentication file that is currently in the default home directory to the /tmp directory. Type the mv source destination command and press Enter. 9. To activate the authentication file, type /opt/avaya/common_services/vami_set_asg, and press Enter. 10. The system installs the file immediately. You do not need to reboot the system. Related links Transferring files using WinSCP on page 50 Installing the RFA Authentication file through the Utility Services Web page Procedure 1. Use an account with the administrator privileges to log on to the Avaya Aura Utility Services System Management Interface (SMI) Web page. 2. Click Utilities > Utility Admin. 3. In the navigation pane, in the Miscellaneous section, click Upload Files. 4. Click Browse, and select the RFA Authentication file. The name of the file must be asg_auth_file.xml 5. Click Upload File. 6. In the navigation pane, in the Miscellaneous section, click RFA License Activation. The A Valid Authentication File is currently field must show Available. If the file is missing or has an incorrect name, the A Valid Authentication File is currently field shows Not Available. 7. Click Activate the Authentication File. The activation is immediate and applies to all the future login attempts. Installing software patches About this task Use the procedure to install software patches, service packs, and feature packs that are entitled for an Avaya Aura application, and commit the patches that you installed. Before you begin Perform the preupgrade check. May 2017 Deploying Avaya Aura Utility Services 38

39 Deployment methods If you upgrade an application that was not deployed from Solution Deployment Manager: 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 Upgrade Source, 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. If an application is unreachable, the auto commit operation might fail and the Update Patch Status window displays a warning message. You must wait for some time, select the same patch in the Installed Patches section, and perform the commit operation again. 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. 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. May 2017 Deploying Avaya Aura Utility Services 39

40 Deploying and configuring Utility Services Open Virtual Application 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 Rollback Show All Name Name Element Name Patch Version Patch Type Patch State Description The option to select the patches that you can commit. The option to select the patches that you can uninstall. The option to select the patches that you can rollback. The option to display all the available options. Description 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 May 2017 Deploying Avaya Aura Utility Services 40

41 Deployment methods Name Schedule Job Date Time Time Zone Name Schedule Description 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. Description Runs the job or schedules to run at the time that you configured in Job Schedule. Viewing the status of the NTP server Procedure 1. Use an account with administrator-level privileges to log on to the Avaya Aura Utility Services System Management Interface (SMI) Web page. 2. Click Utility Services > Utility Admin. 3. In the navigation pane, in the Miscellaneous section, click NTP Status. On the NTP Synchronization Status page, the system displays: The status of the NTP server. The estimated accuracy of the clock. An indication of the delay to the next polling interval. The status of the NTP Peer servers. May 2017 Deploying Avaya Aura Utility Services 41

42 Deploying and configuring Utility Services Open Virtual Application Deployment of cloned and copied OVAs To redeploy a virtual machine, do not create a copy of the virtual machine or clone the virtual machine. These processes have subtle technical details that require a thorough understanding of the effects of these approaches. To avoid any complexities and unexpected behavior, deploy a new OVA on the virtual machine. At this time, Avaya only supports the deployment of new OVAs. May 2017 Deploying Avaya Aura Utility Services 42

43 Chapter 5: Configuration Configuring the virtual machine automatic startup settings About this task This procedure does not apply for deployments and upgrades of applications running on Appliance Virtualization Platform. When a vsphere ESXi host restarts after a power failure, the virtual machines that are deployed on the host do not start automatically. You must configure the virtual machines to start automatically. In high availability (HA) clusters, the VMware HA software ignores the startup selections. Before you begin Verify with the system administrator that you have the proper level of permissions to configure the automatic startup settings. Procedure 1. In the vsphere Client inventory, select the host where the virtual machine is located. 2. Click the Configuration tab. 3. In the Software section, click Virtual Machine Startup/Shutdown. 4. Click Properties in the upper-right corner of the screen. 5. In the System Settings section, select Allow virtual machines to start and stop automatically with the system. 6. In the Manual Startup section, select the virtual machine. 7. Use the Move up button to move the virtual machine to the Automatic Startup section. 8. Click OK. Example The following is an example of the Virtual Machine Startup/Shutdown screen. May 2017 Deploying Avaya Aura Utility Services 43

44 Configuration Post deployment reconfiguration With the post deployment reconfiguration, you can modify the parameters of the Utility Services OVA after initial deployment. You can modify the network parameters such as, IP address, Hostname, and DNS, and application parameters such as, Communication Manager IP Address. Use one of the following methods to reconfigure Utility Services OVA: Through the ESXi host Through vcenter Related links Reconfiguring the Utility Services OVA through the ESXi host on page 45 Reconfiguring the Utility Services OVA through vcenter on page 46 May 2017 Deploying Avaya Aura Utility Services 44

45 Post deployment reconfiguration Reconfiguring the Utility Services OVA through the ESXi host About this task The reconfiguration can be carried out at any time and the changes takes effect immediately. Procedure 1. In the vsphere client, select the Utility Services virtual machine. 2. Click the Getting Started tab. 3. Click Power on the virtual machine. 4. Click the Console tab. 5. Log in to an account with administrative privileges. 6. Run the /opt/avaya/common_services/vmware_conf.sh command. 7. When the system prompts to continue, enter y. 8. Enter the values for the following network entities: a. Default Gateway b. Hostname c. DNS d. IP address allocation for eth0 For more information about the fields, see Properties field descriptions. 9. To configure the timezone settings, select the region and the local area. 10. Enter the IP address of Communication Manager that is accessible from the Utility Services virtual machine. For an Out-of-band Management (OOBM) enabled deployment, either type the Public IP address or type the OOBM IP address of Communication Manager. For an Out-of-band Management disabled deployment, type the Public IP address of Communication Manager. 11. Enter the IP address of the primary NTP server to be used for the Utility Services virtual machine. 12. The system installs the default authentication file. You must replace the file with the authentication file that you downloaded from RFA. For more information, see Installation of the RFA Authentication file on Utility Services. Related links Post deployment reconfiguration on page 44 Installation of the RFA Authentication file on Utility Services on page 37 Properties field descriptions on the vsphere client on page 31 May 2017 Deploying Avaya Aura Utility Services 45

46 Configuration Reconfiguring the Utility Services OVA through vcenter About this task When the virtual machine is running, the system displays the properties as read-only. Therefore, you must stop the virtual machine to make any changes. The changes take effect on starting the virtual machine. Procedure 1. In the vsphere Client, select the Utility Services virtual machine. 2. Click the Getting Started tab. 3. Click Power on the virtual machine. 4. Click Edit Virtual Machine Settings. The system displays a new window containing the details of the Utility Services virtual machine. 5. Click the Options tab. 6. Click Properties. 7. On the Properties screen, complete the following fields: a. In the Application section, complete the following fields: Communication Manager IP Hostname Timezone NTP Server IP b. In the Networking section, complete the following fields: Default Gateway DNS For more information about the fields, see Properties field descriptions. 8. Click OK. 9. The system installs the default authentication file. You must replace the default authentication file with the authentication file that you have downloaded from RFA. For more information, see Installation of the RFA Authentication file on Utility Services. Related links Post deployment reconfiguration on page 44 Installation of the RFA Authentication file on Utility Services on page 37 Properties field descriptions for vcenter vsphere client on page 35 May 2017 Deploying Avaya Aura Utility Services 46

47 Updating System Manager details in the /etc/hosts file Updating System Manager details in the /etc/hosts file Procedure 1. Start an SSH session. 2. Log in to Utility Services as admin. 3. In the command line, type /opt/avaya/common_services/set_smgr. Example The Set_SMGR command is available in Utility Services Release and later /opt/avaya/common_services/set_smgr Using SMGR_FQDN is :- smgr-test.guildford.local The entry smgr-test.guildford.local will now be present in the /etc/ hosts file. May 2017 Deploying Avaya Aura Utility Services 47

48 Chapter 6: Maintenance Upgrading the Utility Services virtual machine Procedure 1. Create a backup including the IP firmware of the existing Utility Services virtual machine on your local machine. For more information about creating a backup, see Creating a backup of Utility Services. For a Utility Services Release 6.3 upgrade, while creating a backup of the previous release, you must exclude the IP phone firmware. 2. Stop the old Utility Services virtual machine. 3. Deploy and configure the new Utility Services virtual machine. For more information about deploying and configuring, see Deploying and configuring Utility Services Open Virtual Application. 4. Start the new Utility Services virtual machine. 5. Log in to the new Utility Services virtual machine. 6. Restore the local backup on the new Utility Services virtual machine. For more information on restoring a backup, see Restoring a backup of Utility Services. Related links Deployment methods on page 23 Creating a backup of Utility Services on page 49 Restoring a backup of Utility Services on page 50 Updating patches and service packs Procedure 1. Use an account with administrator-level privileges to log in to the Utility Services commandline interface. 2. Copy the patch or service pack to the /tmp directory. scp is the preferred method. However, some errors might occur because Utility Services supports only scp and most laptops do not support scp. May 2017 Deploying Avaya Aura Utility Services 48

49 Backup and restore To enable scp, you must download the following programs: Pscp.exe WinSCP 3. Use the /opt/avaya/common_services/update command to update the patch. You can enter the following arguments with this command. If you do not enter any arguments, the system displays a usage list. -i : to install a patch or a service pack. The patch or service pack must be in /tmp directory. -r <patchnumber>: to remove a patch or service pack. -l: to list all installed patches and service packs. -q <patchnumber>: to view the contents of the specified patch or service pack. Backup and restore Use the local backup and restore function of Utility Services for the long-term backup and recovery of the Utility Services data when running on VMware. You must schedule the backup and restore function to run periodically. Include/Exclude IP Firmware option You can choose to include or exclude the IP Firmware option while creating backups. By default, the IP Firmware option is included for backups. If you exclude the IP Firmware option, the backup process is much quicker and generates a smaller backup file. However, for any disaster recover procedures, you must have at least one backup with IP Firmware included. Disaster Recovery If the Utility Services virtual machine fails completely, you can redeploy the OVA with the same settings used originally and restore a full backup to regain full functionality. Creating a backup of Utility Services Procedure 1. Use an account with administrator-level privileges to log on to the Avaya Aura Utility Services System Management Interface (SMI) webpage. 2. Click Utility Services > Utility Admin. May 2017 Deploying Avaya Aura Utility Services 49

50 Maintenance 3. In the navigation pane on the left side of the page, click Miscellaneous > Utility Services Backup and Restore. 4. Use one of the following methods to create a backup: To include the IP firmware in backup, click Include Firmware in Backup. To exclude the IP firmware in backup, click Exclude Firmware in Backup. 5. Click Create Backup. The system creates a backup file. 6. The system displays the name and the location of the backup file. 7. Click Download the newly created Utility Services Backup File to save the backup file to the local machine. 8. Click Continue. Restoring a backup of Utility Services Procedure 1. Use an account with administrator-level privileges to log on to the Avaya Aura Utility Services System Management Interface (SMI) webpage. 2. Click Utility Services > Utility Admin. 3. In the navigation pane on the left side of the page, click Miscellaneous > Utility Services Backup and Restore. 4. Click Browse and select the backup file that you want to restore from the local machine. 5. Click Upload Backup. The system restores the backup file. 6. Click Continue. Transferring files using WinSCP Transfer files using the WinSCP utility from a remote system to the virtual machine. WinSCP is a SFTP client and FTP client for Windows. The main function of WinSCP is to securely transfer files between a local and a remote computer. WinSCP uses Secure Shell (SSH) and supports Secure FTP and legacy SCP protocol. Before you begin Ensure that WinSCP is installed on your computer. WinSCP is available as a download from the Internet. May 2017 Deploying Avaya Aura Utility Services 50

51 Transferring files using WinSCP Procedure 1. Use WinSCP to connect to the virtual machine. 2. Enter the credentials for SCP access. 3. Click OK or Continue as necessary in the warning dialogue boxes. 4. Change the file transfer protocol from SFTP to SCP. 5. Click Browse to locate and select the file. 6. In the WinSCP destination machine window, browse to /home/. 7. Select /home/customerloginname as the destination location for the file transfer. This is likely to be the first destination when WinSCP opens. 8. Click and drag the file from the WinSCP source window to /home/customerloginname in the WinSCP destination window. 9. Click the WinSCP Copy button to start the file transfer. 10. When the copy completes, close the WinSCP window and click OK. May 2017 Deploying Avaya Aura Utility Services 51

52 Chapter 7: Resources Documentation The following table lists the documents related to this product. Download the documents from the Avaya Support website at Title Description Audience Design Avaya Aura Virtualized Environment Solution Description Administration Accessing and Managing Avaya Aura Utility Services, Administering Avaya Aura System Manager Implementation and Upgrading Migrating and Installing Avaya Appliance Virtualization Platform Deploying Avaya Aura applications from System Manager Upgrading and Migrating Avaya Aura applications to Release from System Manager Describes the Virtualized Environment solution from a functional view. Includes a high-level description of the solution as well as topology diagrams, customer requirements, and design considerations. Describes procedures for managing the features that are part of Utility Services. Features include IP phone settings, ADVD Settings, IP phone firmware management, log viewer, CDR tools, and Enhanced System Directory Describes procedures for managing the features that are part of Utility Services. Describes Appliance Virtualization Platform migrating checklists and procedures used during migration from System Platform to Appliance Virtualization Platform. Describes the implementation instructions while deploying and configuring Utility Services Open Virtual Application for vcenter and vsphere. Describes the implementation instructions while deploying and configuring Utility Sales Engineers Sales Engineers, Solution Architects, Implementation Engineers, Support Personnel Sales Engineers, Solution Architects, Implementation Engineers, Support Personnel Implementation Engineers, Support Personnel, Solution Architects Implementation Engineers, Support Personnel, Solution Architects Implementation Engineers, Support Table continues May 2017 Deploying Avaya Aura Utility Services 52

53 Training Title Description Audience Understanding Avaya Aura Communication Manager Hardware Description and Reference, Services Open Virtual Application for vcenter and vsphere. Describes the hardware devices that can be incorporated in a Communication Manager telephony configuration. Personnel, Solution Architects Solution Architects, Implementation Engineers, Sales Engineers, Support 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 2. At the top of the screen, enter your username and password and click Login. 3. Put your cursor over Support by Product. 4. Click Documents. 5. In the Enter your Product Here search box, type the product name and then select the product from the drop-down list. 6. If there is more than one release, select the appropriate release number from the Choose Release drop-down list. 7. Use the Content Type filter on the left to select the type of document you are looking for, or click Select All to see a list of all available documents. For example, if you are looking for user guides, select User Guides in the Content Type filter. Only documents in the selected category will appear in the list of documents. 8. Click Enter. Training The following courses are available on the Avaya Learning website at After logging into the website, enter the course code or the course title in the Search field and click Go to search for the course. May 2017 Deploying Avaya Aura Utility Services 53

54 Resources Course code Understanding 1A00234E AVA00383WEN ATI01672VEN, AVA00832WEN, AVA00832VEN Course title Avaya Aura Fundamental Technology Avaya Aura Communication Manager Overview Avaya Aura Communication Manager Fundamentals 2007V What is New in Avaya Aura V What is New in Avaya Aura Communication Manager V 2009T 2013V 5U00060E Implementation and Upgrading 4U00030E ATC00838VEN AVA00838H00 ATC00838VEN What is New in Avaya Aura System Manager & Avaya Aura Session Manager 7.0 What is New in Avaya Aura Communication Manager 7.0 Online Test Avaya Aura 7.0 Solution Management Knowledge Access: ACSS - Avaya Aura Communication Manager and CM Messaging Embedded Support (6 months) Avaya Aura Communication Manager and CM Messaging Implementation Avaya Media Servers and Implementation Workshop Labs Avaya Media Servers and Media Gateways Implementation Workshop Avaya Media Servers and Gateways Implementation Workshop Labs 2012V Migrating and Upgrading to Avaya Aura 7.0 Administration AVA00279WEN AVA00836H00 AVA00835WEN 5U0041I AVA00833WEN AVA00834WEN 5U00051E Communication Manager - Configuring Basic Features Communication Manager Basic Administration Avaya Communication Manager Trunk and Routing Administration Avaya Aura Communication Manager Administration Avaya Communication Manager - Call Permissions Avaya Communication Manager - System Features and Administration Knowledge Access: Avaya Aura Communication Manager Administration Viewing Avaya Mentor videos Avaya Mentor videos provide technical content on how to install, configure, and troubleshoot Avaya products. May 2017 Deploying Avaya Aura Utility Services 54

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

56 Appendix A: Best Practices for VMware performance and features The following sections describe the best practices for VMware performance and features. Related links BIOS on page 56 VMware Tools on page 58 Timekeeping on page 58 VMware networking best practices on page 60 Thin vs. thick deployments on page 64 BIOS For optimal performance, turn off power saving server options. See the technical data provided by the manufacturer for your particular server regarding power saving options. For information about how to use BIOS settings to improve the environment for latency-sensitive workloads for an application, see the technical white paper at techpaper/vmw-tuning-latency-sensitive-workloads.pdf. The following sections describe the recommended BIOS settings for: Intel Virtualization Technology Dell PowerEdge Servers HP ProLiant Servers Related links Best Practices for VMware performance and features on page 56 Intel Virtualization Technology on page 57 Dell PowerEdge Server on page 57 HP ProLiant Servers on page 58 May 2017 Deploying Avaya Aura Utility Services 56

57 BIOS Intel Virtualization Technology Intel CPUs require EM64T and Virtualization Technology (VT) support in the chip and in the BIOS to run 64 bit virtual machines. All Intel Xeon processors include: Intel Virtualization Technology Intel Extended Memory 64 Technology Execute Disable Bit Ensure that VT is enabled in the host system BIOS. The feature is also known as VT, Vanderpool Technology, Virtualization Technology, VMX, or Virtual Machine Extensions. The VT setting is locked as either On or Off when the server starts. After enabling VT in the system BIOS, save your changes to the BIOS settings and exit. The BIOS changes take effect after the host server reboots. Other suggested BIOS settings Servers with Intel Nehalem class and newer Intel Xeon CPUs offer two more power management options: C-states and Intel Turbo Boost. These settings depend on the OEM make and model of the server. The BIOS parameter terminology for current Dell and HP servers are described in the following sections. Other server models might use other terminology for the same BIOS controls. Disabling C-states lowers latencies to activate the CPUs from halt or idle states to a fully active state. Intel Turbo Boost steps up the internal frequency of the processor if the workload requires more power. The default for this option is enabled. Do not change the default. Related links BIOS on page 56 Dell PowerEdge Server When the Dell server starts, press F2 to display the system setup options. Set the Power Management Mode to Maximum Performance. Set the CPU Power and Performance Management Mode to Maximum Performance. In Processor Settings, set: - Turbo Mode to enable. - C States to disabled. Related links BIOS on page 56 May 2017 Deploying Avaya Aura Utility Services 57

58 Best Practices for VMware performance and features HP ProLiant Servers The following are the recommended BIOS settings for the HP ProLiant servers: Set the Power Regulator Mode to Static High Mode. Disable Processor C-State Support. Disable Processor C1E Support. Disable QPI Power Management. Enable Intel Turbo Boost. Related links BIOS on page 56 VMware Tools The VMware Tools utility suite is built into the application OVA. The tools enhance the performance of the guest operating system on the virtual machine and improve the management of the virtual machine. VMware tools provide: VMware Network acceleration Host to Guest time synchronization Disk sizing For more information about VMware tools, see Overview of VMware Tools at kb.vmware.com/kb/340. Important: Do not upgrade the VMware tools software that is packaged with each OVA unless instructed to do so by Avaya. The supplied version is the supported release and has been thoroughly tested. Related links Best Practices for VMware performance and features on page 56 Timekeeping For accurate timekeeping, use the Network Time Protocol (NTP) as a time source instead of the ESXi hypervisor. May 2017 Deploying Avaya Aura Utility Services 58

59 Timekeeping The NTP servers can be local or over the Internet. If the NTP servers are on the Internet, the corporate firewall must open UDP port 123 so that the NTP service can communicate with the external NTP servers. The VMware tools time synchronization method is disabled at application deployment time to avoid dueling clock masters. You must configure the NTP service first because the applications are not receiving clock updates from the hypervisor. To verify that VMware Tools Timesync is disabled, run the command /usr/bin/vmware-toolbox-cmd timesync status. In certain situations, the ESXi hypervisor pushes an updated view of its clock into a virtual machine. These situations include starting the virtual machine and resuming a suspended virtual machine, If this view differs more than 1000 seconds from the view that is received over the network, the NTP service might shutdown. In this situation, the guest OS administrator must manually set the guest clock to be the same or as close as possible to the network time source clock. To keep the NTP service active, the clock on the ESXi host must also use an accurate clock source, such as the same network time source that is used by the guest operating system. The VMware recommendation is to add tinker panic 0 to the first line of the ntp.conf file so that the NTP can adjust to the network time even with large differences. If you use the names of the time servers instead of the IP address, you must configure the Domain Name Service in the guest OS before you administer the NTP service. Otherwise, the NTP service cannot locate the time servers. If you administer the NTP service first, you must restart the NTP service after administering the DNS service. After you administer the NTP service in the application, run the ntpstat or /usr/sbin/ntpq -p command from a command window. The results from these commands: Verify if the NTP service is getting time from a network time source. Indicate which network time source is in use. Display how closely the guest OS matches the network time. Display how often the guest OS checks the time. The guest OS polls the time source every 65 to 1024 seconds. Larger time intervals indicate that the guest clock is tracking the network time source closely. If the time source is local, then the NTP service is not using a network time source and a problem exists. If the clock value is consistently wrong, look through the system log for entries regarding ntpd. The NTP service writes the activities it performs to the log, including when the NTP service loses synchronization with a network time source. For more information, see Timekeeping best practices for Linux guests at The article presents best practices for Linux timekeeping to achieve best timekeeping results. The article includes: specifics on the particular kernel command line options to use for the Linux operating system of interest. recommended settings and usage for NTP time sync, configuration of VMware Tools time synchronization, and Virtual Hardware Clock configuration. Related links Best Practices for VMware performance and features on page 56 May 2017 Deploying Avaya Aura Utility Services 59

60 Best Practices for VMware performance and features VMware networking best practices You can administer networking in a VMware environment for many different configurations. The examples in this section describe some of the VMware networking possibilities. This section is not a substitute for the VMware documentation. Review the VMware networking best practices before deploying any applications on an ESXi host. The following are the suggested best practices for configuring a network that supports deployed applications on VMware Hosts: Separate the network services to achieve greater security and performance by creating a vsphere standard or distributed switch with dedicated NICs for each service. If you cannot use separate switches, use port groups with different VLAN IDs. Configure the vmotion connection on a separate network devoted to vmotion. For protection, deploy firewalls in the virtual machines that route between virtual networks that have uplinks to physical networks and pure virtual networks without uplinks. Specify virtual machine NIC hardware type vmxnet3 for best performance. Connect all physical NICs that are connected to the same vsphere standard switch to the same physical network. Connect all physical NICs that are connected to the same distributed switch to the same physical network. Configure all VMkernel vnics to be the same IP Maximum Transmission Unit (MTU). May 2017 Deploying Avaya Aura Utility Services 60

61 VMware networking best practices Networking Avaya applications on VMware ESXi Example 1 This configuration describes a simple version of networking Avaya applications within the same ESXi host. Highlights to note: Separation of networks: VMware Management, VMware vmotion, iscsi (SAN traffic), and virtual machine networks are segregated to separate physical NICs. Teamed network interfaces: vswitch 3 in Example 1 displays use of a load-balanced NIC team for the Virtual Machines Network. Load balancing provides additional bandwidth for the Virtual Machines Network, while also providing network connectivity for the virtual machines in the case of a single NIC failure. Communication Manager Duplex link: Communication Manager software duplication must be separated from all other network traffic. Example 1 displays one method of separating Communication Manager Duplex with a port group combined with a VLAN. The May 2017 Deploying Avaya Aura Utility Services 61

62 Best Practices for VMware performance and features Communication Manager software duplication link must meet specific network requirements. For more information, see Avaya PSN003556u at PSN003556u. The following are the minimum requirements of the Communication Manager software duplex connectivity: - The total capacity must be 1 Gbps or greater. Reserve 50 Mbps of bandwidth for duplication data. - The round-trip delay must be 8 ms or less. - The round-trip packet loss must be 0.1% or less. - Both servers duplication ports must be on the same IP subnet. - You must disable duplication link encryption for busy-hour call rates that result in greater than 40% CPU occupancy. You can view the CPU occupancy using the list measurements occupancy command and looking at the results under the Static + CPU occupancy heading. - The system must maintain CPU occupancy on the active server (Static + CPU) at less than 65% to provide memory refresh from the active to standby server. Session Manager vnic mapping: Session Manager OVA defines four separate virtual NICs within the VM. However, example 1 shows all interfaces networked through a single virtual machine network, which is supported. If the Session Manager Management and Session Manager Asset networks are separated by subnets, you can create a VLAN for the appropriate network. Virtual networking: The network connectivity between virtual machines that connect to the same vswitch is entirely virtual. In example 2, the virtual machine network of vswitch3 can communicate without entering the physical network. Virtual networks benefit from faster communication speeds and lower management overhead. May 2017 Deploying Avaya Aura Utility Services 62

63 VMware networking best practices Networking Avaya applications on VMware ESXi Example 2 This configuration shows a complex situation using multiple physical network interface cards. The key differences between example 1 and example 2 are: VMware Management Network redundancy: Example 2 includes a second VMkernel Port at vswitch2 to handle VMware Management Network traffic. In the event of a failure of vmnic0, VMware Management Network operations can continue on this redundant management network. Removal of Teaming for Virtual Machines Network: Example 2 removes the teamed physical NICs on vswitch3. vswitch3 was providing more bandwidth and tolerance of a single NIC failure instead of reallocating this NIC to other workloads. Communication Manager Duplex Link: vswitch4 is dedicated to Communication Manager Software Duplication. The physical NIC given to vswitch4 is on a separate physical network that follows the requirements described in PSN003556u at PSN003556u. May 2017 Deploying Avaya Aura Utility Services 63