Deploying Avaya Aura Presence Services on VMware

Transcription

1 Deploying Avaya Aura Presence Services on VMware Release 6.2 Issue 4 July 2014

2 2014, 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 by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya may generally make available to users of its products and Hosted Services. 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 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: 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, 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 Avaya s computer programs in object code, provided by Avaya or an Avaya Channel Partner, whether as stand-alone products, pre-installed, or remotely accessed on hardware products, and any upgrades, updates, 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 an Instance of the same database. CPU License (CP). End User may install and use each copy or Instance of the Software on a number of Servers up to the number indicated in the order provided that the performance capacity of the Server(s) does not exceed the performance capacity specified for the Software. End User may not re-install or operate the Software on Server(s) with a larger performance capacity without Avaya s prior consent and payment of an upgrade fee. Named User License (NU). You may: (i) install and use 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 currently available for license from Avaya is the software contained within the list of Heritage Nortel Products located at LicenseInfo/ under the link Heritage Nortel Products, or such successor site as designated by Avaya. For Heritage Nortel Software, Avaya grants Customer a license to use Heritage Nortel Software provided hereunder solely to the extent of the authorized activation or authorized usage level, solely for the purpose specified in the Documentation, and solely as embedded in, for execution on, or (in the event the applicable Documentation permits installation on non-avaya equipment) for communication with Avaya equipment.

3 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 Each virtual appliance has its own ordering code. Note that each instance of a virtual appliance must be ordered separately. If the enduser customer or Business Partner wants to install two of the same type of virtual appliances, then two virtual appliances 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 Documentation or on Avaya s website at: support.avaya.com/copyright or such successor site as designated by Avaya. You agree to the Third Party Terms for any such Third Party Components Certain software programs or portions thereof included in the Product are open-source products. The Open Source license file, OpenSourceLicense.txt, is available in the Licenses folder on the Presence Services server: /Licenses/OpenSourceLicense.txt 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. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: securityalerts@avaya.com. 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, 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 one-x are registered trademarks and Avaya Aura is a trademark of Avaya, Inc. All non-avaya trademarks are the property of their respective owners. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. 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.

4 Contents Chapter 1: Introduction... 7 Purpose... 7 Intended audience... 7 Document changes since last issue... 7 Related resources... 8 Documentation... 8 Training... 8 Viewing Avaya Mentor videos... 9 Support... 9 Chapter 2: Architecture overview Avaya Aura Virtualized Environment Overview Avaya Collaboration Pod for Enterprise Communications VMware components Deployment guidelines Chapter 3: Planning and configuration Server hardware and resources Configuration tools and utilities Customer configuration data Avaya Aura Presence Services virtual machine resource requirements Software requirements VMware software requirements SAL Gateway Chapter 4: Initial setup and pre-deployment Pre-deployment procedures Configuring Avaya Aura System Manager Chapter 5: Deploying the Avaya Aura Presence Services OVA Deployment of cloned and copied OVAs Deployment checklist Downloading software from PLDS Deploying Presence Services OVA Configuring virtual hardware and resource allocation reservations Starting the Presence Services VM Running Presence Services installation script High Availability HA requirements Example of setting Forged Transmits for the virtual switch Configuring HA during the Presence Services installation Upgrading Presence Services to support HA Starting or stopping the Presence Services server July 2014 Deploying Avaya Aura Presence Services on VMware 4

5 Contents Viewing the status of HA Failover and failback Scripts for HA Modifying Presence Services virtual machine properties Chapter 6: Configuration Configuring the virtual machine automatic start and stop settings Downloading and running the Presence Services Service Pack installation script Supporting up to 10,000 users Chapter 7: Post-installation verification Verifying the Presence Services VM status Checking the synchronization of Presence Services with System Manager Verifying user end points Chapter 8: Maintenance Updates/patches Avaya Aura Presence Services VM updates Upgrades Overview Backup and restore Migration Migration data Transferring files using WinSCP Migrating Presence Services installed on System Platform Changing Presence Services Network Identity Changing the Presence Services hostname changeip.sh tool Chapter 9: Troubleshooting Viewing the status of the Presence Services components presstatus Viewing monit using a CLI Presence Services logging Overview Changing the default logging level Viewing logs on System Manager 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 Storage Thin vs. thick deployments July 2014 Deploying Avaya Aura Presence Services on VMware 5

6 Contents VMware Features VMware Snapshots VMware Cloning VMware High Availability (HA) VMware vmotion Appendix B: Glossary July 2014 Deploying Avaya Aura Presence Services on VMware 6

7 Chapter 1: Introduction Purpose This document provides installation, configuration, initial administration, and basic maintenance checklists and procedures. Intended audience This document is intended for people who install and configure a verified reference configuration at a customer site. Document changes since last issue The following changes have been made to this document since the last issue: Updated the topic Software requirements on page 17 to include VMware vsphere 5.5. Updated the topic VMware software requirements on page 17 to include VMware vsphere ESXi 5.5 and VMware vcenter Server 5.5. Added the topic Example of setting Forged Transmits for the virtual switch on page 41. Added the topic High Availability on page 41. Added the topic HA requirements on page 41. Added the topic Configuring HA during the Presence Services installation on page 41. Added the topic Upgrading Presence Services to support HA on page 44. Added the topic Starting or stopping the Presence Services server on page 45. Added the topic Viewing the status of HA on page 45. Added the topic Failover and failback on page 46. Added the topic Scripts for HA on page 47. July 2014 Deploying Avaya Aura Presence Services on VMware 7

8 Introduction Related 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 Implementation Deploying Avaya Aura Presence Services Maintenance and Troubleshooting Troubleshooting Avaya Aura Presence Services Administration Administering Avaya Aura Presence Services 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 the implementation of Presence Services. Describes the required and optional components and requirements. Contains procedures for implementing, upgrading, and uninstalling Presence Services. Describes the troubleshooting procedures for Presence Services. Describes the administrative procedures for Presence Services. Describes the maintenance and configuration procedure for presence components. Sales Engineers Sales Engineers, Solution Architects, Implementation Engineers, Support Personnel Sales Engineers, Solution Architects, Implementation Engineers, Support Personnel Sales Engineers, Solution Architects, Implementation Engineers, Support Personnel Training The following courses are available on the Avaya Learning website at To search for the course, log in to the Avaya Learning Center, enter the course code in the Search field and click Go. Course code 3U00125O 8U00170E Course title Designing Avaya Aura Presence Services Tech Sales L1 Avaya Aura Presence Services Implementation and Maintenance July 2014 Deploying Avaya Aura Presence Services on VMware 8

9 Support Viewing Avaya Mentor videos Avaya Mentor videos provide technical content on how to install, configure, and troubleshoot Avaya products. About this task Videos are available on the Avaya Support web site, listed under the video document type, and on the Avaya-run channel on YouTube. Procedure To find videos on the Avaya Support web site, go to select the product name, and select the videos checkbox to see a list of available videos. 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 site. Note: Videos are not available for all products. Support Visit 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. July 2014 Deploying Avaya Aura Presence Services on VMware 9

10 Chapter 2: Architecture overview Avaya Aura Virtualized Environment Overview Avaya Aura Virtualized Environment integrates real-time Avaya Aura applications with VMware virtualized server architecture. Virtualized Environment provides the following benefits: simplifies IT management using common software administration and maintenance. requires fewer servers and racks which reduces the footprint. lowers power consumption and cooling requirements. enables capital equipment cost savings. lowers operational expenses. uses standard operating procedures for both Avaya and non-avaya products. customers can deploy Avaya products in a virtualized environment on customer-specified servers and hardware. business can scale rapidly to accommodate growth and to respond to changing business requirements. For existing customers who have a VMware IT infrastructure, Avaya Aura Virtualized Environment provides an opportunity to 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 hardwareefficient simplified solution for upgrading to the latest Avaya Aura release and adding the latest Avaya Aura capabilities. The Virtualized Environment project is only for VMware and is not intended to include any other industry hypervisor. Virtualized Environment is inclusive of the Avaya Aura portfolio. Note: This document uses the following terms, and at times, uses the terms interchangeably. server and host reservations and configuration values Customer deployment Deployment into the blade, cluster, and server is managed by vcenter Server and vsphere Client. The customer provides the servers and the VMware infrastructure including the VMware licenses. July 2014 Deploying Avaya Aura Presence Services on VMware 10

11 Avaya Collaboration Pod for Enterprise Communications Software delivery The software is delivered as one or more pre-packaged Open Virtualization Appliance (OVA) files that are posted on the Avaya Product Licensing and Download System (PLDS) and the Avaya support site. Each OVA contains the following components: the application software and operating system. pre-installed VMware tools. preset configuration details for - RAM and CPU reservations and storage requirements - Network Interface Card (NIC) Patches and upgrades A minimum patch level can be required for each supported application. For more information regarding the application patch requirements, see the compatibility matrix tool at support.avaya.com/compatibilitymatrix/index.aspx. 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. Performance and capacities The OVA template is built with configuration values which optimize performance and follow recommended Best Practices. Caution: Modifying these values can have a direct impact on the performance, capacity, and stability of the virtual machine. It is the responsibility of the customer to understand the aforementioned impacts when changing configuration values. Avaya Global Support Services (GSS) may not be able to assist in fully resolving a problem if the virtual hardware or resource allocation has been changed to unsupported values for a virtual application. Avaya GSS could require the customer to reset the values to the optimized values before starting to investigate the issue. Avaya Collaboration Pod for Enterprise Communications Avaya Collaboration Pod for Enterprise Communications is an alternative deployment option for Avaya Aura Virtualized Environment applications. Collaboration Pod is a full-stack turnkey solution that combines storage arrays from EMC, virtualization software from VMware, and networking, management, and real-time applications from Avaya. Collaboration Pod accelerates deployment of Avaya Aura applications and simplifies IT operations. Documentation The following table lists the Avaya Collaboration Pod for Enterprise Communications documents. These documents are available on the Avaya support website at July 2014 Deploying Avaya Aura Presence Services on VMware 11

12 Architecture overview Title Avaya Collaboration Pod for Enterprise Communications Technical Solutions Guide Avaya Collaboration Pod for Enterprise Communications Pod Orchestration Suite User Guide Avaya Collaboration Pod for Enterprise Communications Locating the latest product documentation Avaya Collaboration Pod for Enterprise Communications Release Notes Description Provides an overview of the solution, specifications, and components that Avaya Collaboration Pod for Enterprise Communications integrates. Provides an overview of the Avaya Pod Orchestration Suite (POS). The POS contains the applications which orchestrate, manage, and monitor the Collaboration Pod. This guide explains how to access and use the applications in the POS management suite. Identifies the Collaboration Pod customer documentation. Also includes the documentation for the Avaya and non-avaya products that are included in the Collaboration Pod solution. Describes fixed and known issues for Collaboration Pod. This document does not describe issues associated with each component in the Collaboration Pod. For information on the specific components, see the component Release Notes. VMware components VMware software component ESXi Host ESXi Hypervisor vsphere Client vcenter Server 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. Deployment guidelines The high-level deployment steps are: 1. Deploy the OVA or OVAs. 2. Configure the application. July 2014 Deploying Avaya Aura Presence Services on VMware 12

13 Deployment guidelines 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. 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. July 2014 Deploying Avaya Aura Presence Services on VMware 13

14 Chapter 3: Planning and configuration Server hardware and resources VMware offers compatibility guides that list servers, system, I/O, storage, and backup compatibility with VMware infrastructure. For more information about VMware-certified compatibility guides and product interoperability matrices, see Configuration tools and utilities You must have the following tools and utilities for deploying and configuring the Presence Services open virtual application (OVA). A remote PC running the VMware vsphere Client. An ssh client, for example, PuTTy. A PC X-Server, for example, Xming. An sftp client for Windows, for example WinSCP. A browser for accessing the Avaya Aura Presence Services Web Controller and Avaya Aura System Manager Web Console For more information about tools and utilities, see Deploying Avaya Aura Presence Services on the Avaya support website. Customer configuration data The following table identifies the key customer configuration information that will be required throughout the deployment and configuration process for Presence Services. Important: Special characters such as are not currently allowed in passwords. Password characters are restricted to uppercase letters, lowercase letters, and numbers only. July 2014 Deploying Avaya Aura Presence Services on VMware 14

15 Customer configuration data Required Data for Presence Services Router Service Name ROUTER_SERVICE_NAME Router Realm ROUTER_REALM Server IP Address IP_ADDRESS SAL Organization FQDN Name SPIRIT.FQDN SAL Platform Qualifier Name SPIRIT.platformqualifier Enrollment Password SCEP_PASSWORD Value for the system Sample Value Note: Ensure that the value you enter for the ROUTER_SERVICE_NAME field is in small case. Also, it is important to note that this is not the FQDN of the Presence server. The Realm is a unique string used to identify the router and all of its components. The realm was supplied during installation. If necessary, you can change the realm after you have installed the server. To do this, you must change the setting of realm in the Global Settings Configuration screen and in the web-cm.xml file. Server IP Address IP address of thepresence server defaults to current IP address. If it is xxx.xxx.xxx.xxx, change to a valid IP address. This value must match the SAL Organization fully qualified domain name (FQDN) on the System Manager server Note: A trailing dot (.) is required at the end of the this field. This value must match the SAL Platform Qualifier name on the System Manager server SAL Organisztion FQDN Name with trailing dot (. ) The SAL Organization FQDN Name and SAL Platform Qualifier Name values must match the values on the setting on the System Manager server. To obtain these values log into System Manager Web Console and click Services > Configurations > Settings > SPIRIT > Data Transport Config. This is the simple certificate enrollment password provided for Presence servers. Note: This System Manager enrollment password must not have expired. Note: For more information on the field descriptions, see Deploying Avaya Aura Presence Services on the Avaya support website. July 2014 Deploying Avaya Aura Presence Services on VMware 15

16 Planning and configuration Avaya Aura Presence Services virtual machine resource requirements The Avaya Aura Presence Services virtual machine requires the following set of resources to be available on the ESXi host before deployment. CPU and Memory requirements Maximum number of users CPU Cores Memory Size GB GB GB GB GB GB GB GB GB GB 10, GB 11, GB 12, GB Other requirements CPU reservation 100% Memory reservation 100% CPU Speed per Core Storage on datastore Network Interface Card Important: 2.4GHz 80GB 1@1Gbps Any modification to the resource settings mentioned in the CPU and Memory requirements and Other requirements tables impacts the performance, capacity, and stability of the Presence Services virtual machine. To run the system at full capacity, the resource size requirements must be met. If you deviate from the specified requirements, the performance of the system will be affected adversely. VM Interface Eth0 Application Management and Presence Services related traffic July 2014 Deploying Avaya Aura Presence Services on VMware 16

17 Software requirements Software requirements The Avaya Aura Presence Services uses the current release, 6.2, of software as its standard release on VMware vsphere 5.0, VMware vsphere 5.1, or VMware vsphere 5.5. VMware vsphere 4.1 is not currently supported. The Presence Services VMware virtualization environment is packaged as a vappliance (vappl) ready for deployment on VMware certified hardware. VMware software requirements Avaya Aura Presence 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 vcenter Server 5.0 VMware vcenter Server 5.1 VMware vcenter Server 5.5 To view compatibility with other solution releases, see VMware Product Interoperability Matrices at Note: ESXi 4.1 is not supported. SAL Gateway A Secure Access Link (SAL) Gateway is required for remote access and alarming. Through SAL, support personnel or tools can gain remote access to managed devices to troubleshoot and debug problems. A SAL Gateway: 1. Receives alarms from Avaya products in the customer network. 2. Reformats the alarms. 3. Forwards the alarms to the Avaya support center or a customer-managed Network Management System. You can deploy the SAL Gateway OVA using vcenter through a vsphere client. You can also deploy the SAL Gateway OVA directly to the ESXi server through a vsphere client. July 2014 Deploying Avaya Aura Presence Services on VMware 17

18 Planning and configuration For more information about the SAL Gateway, see the Secure Access Link documentation on the Avaya Support website at July 2014 Deploying Avaya Aura Presence Services on VMware 18

19 Chapter 4: Initial setup and pre-deployment Pre-deployment procedures Before you install and configure Presence Services on a virtual machine, do the following: On System Manager: 1. Define and validate Enrollment password. The Enrollment Password value must match the password on the System Manager server. To obtain this value log into System Manager Web Console and select Services > Security > Certificates > Enrollment Password. 2. The End Entity Profiles value must match with the System Manager server value. To see the available profiles, log in to System Manager Web Console and select Services > Security > Certificates > Authority > Edit End Entity Profiles. 3. Define FQDNs for System Manager and Presence Services. 4. Configure the FQDNs in the DNS servers for the network. Alternatively, add the FQDN of Presence Services to the /etc/hosts file of the System Manager server and add the FQDN of System Manager to the /etc/hosts file of the Presence server. 5. Configure the target Presence server. Caution: Avaya Aura Presence Services installation fails if System Manager is not configured or not available. For more information, see Administering Avaya Aura System Manager on the Avaya support website. Configure Avaya Aura Session Manager. Configure SAL. Configuring Avaya Aura System Manager Procedure 1. On the System Manager web console, click Services > Inventory > Manage Elements and add the target Presence Services. 2. Click Elements > Routing > SIP Entities > New. July 2014 Deploying Avaya Aura Presence Services on VMware 19

20 Initial setup and pre-deployment The system displays the SIP Entities Details page. 3. On the SIP Entities Details page, enter the following details: Name. SIP Entity name. For example, PresenceServer FQDN or IP Address. Presence Services IP address Type. Presence Services SIP Link Monitoring. Use Session Manager Configuration 4. Click Commit. 5. Click Elements > Routing > Entity Links > New and enter the following details: Name. Link name. For example, PresenceServerLink SIP Entity 1. Session Manager instance Protocol. TLS Port SIP Entity 2. The same Presence Services name that you created in the previous procedure. For example, PresenceServer Port Connection Policy. Trusted. 6. Click Commit. July 2014 Deploying Avaya Aura Presence Services on VMware 20

21 Chapter 5: Deploying the Avaya Aura Presence Services OVA 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. Deployment checklist Use the following checklist for deploying the Presence Services vappliance. # Action Link/Notes 1 Download the Presence Services OVA from PLDS See Downloading software from PLDS on page 21 2 Deploy Presence Services OVA See Deploying Presence Services OVA on page 22 3 Start the Presence Services VM See Starting the Presence Services VM on page 27 Downloading software from PLDS When you place an order for an Avaya PLDS-licensed software product, PLDS creates the license entitlements of the order and sends an notification to you. The includes a license activation code (LAC) and instructions for accessing and logging into PLDS. Use the LAC to locate and download the purchased license entitlements. In addition to PLDS, you can download the product software from using the Downloads and Documents tab at the top of the page. July 2014 Deploying Avaya Aura Presence Services on VMware 21

22 Deploying the Avaya Aura Presence Services OVA Note: 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. Select View Downloads. 5. Click on the search icon (magnifying glass) for Company Name. 6. In the %Name field, enter Avaya or the Partner company name. 7. Click Search Companies. 8. Locate the correct entry and click the Select link. 9. Enter the Download Pub ID. 10. Click Search Downloads. 11. Scroll down to the entry for the download file and click the Download link. 12. In the Download Manager box, click the appropriate download link. Note: The first link, Click to download your file now, uses the Download Manager to download the file. The Download Manager provides features to manage the download (stop, resume, auto checksum). The click here link uses your standard browser download and does not provide the download integrity features. 13. (Internet Explorer only) If you receive an error message, click on 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. Deploying Presence Services OVA Procedure 1. Using vsphere Client, select the host ESXi host for deploying Presence Services OVA. 2. From the Client menu, select File > Deploy OVF Template. July 2014 Deploying Avaya Aura Presence Services on VMware 22

23 Deploying Presence Services OVA 3. Use one of the following options to deploy the Presence Services OVA package: Click Browse and navigate to the.ova file on the local computer, network share, CD- ROM, or DVD, and then click Open. If the Presence Services OVA file is located on an http server, enter the full path to the.ova file in the Deploy from a file or URL field. 4. Click Next. The system displays the OVF Template Details window. 5. Verify the details of the OVA template and click Next. The system displays the End User License Agreement window. 6. Read the license agreement, click Accept to accept the license agreement and then click Next. The system displays the Name and Location window. 7. In the Name field, enter the name of the new virtual machine and select the inventory location to deploy the virtual machine. 8. Click Next. The system displays the Storage window. 9. Select the data store location and click Next. The system displays the Disk Format window. 10. Select Thick Provision Lazy Zeroed and then click Next. The system displays the Network Mapping window. 11. If there are multiple virtual machine networks configured on the host where you are deploying the Presence Services OVA, the wizard prompts you to associate networks specified in the OVA with networks available on the host. For a single source network, from the Destination Network drop-down box, select a host network and then click Next. The Ready to Complete window displays. The wizard does not prompt anything if there is only a single virtual machine network on the host where you want to deploy Presence Services OVA. 12. Verify the deployment settings and click Finish. To check the progress of the tasks, click Recent Tasks and wait until OVA template shows a completed status. For more information about deploying templates in VMware, see VMware documentation on deploying an OVF template. July 2014 Deploying Avaya Aura Presence Services on VMware 23

24 Deploying the Avaya Aura Presence Services OVA Configuring virtual hardware and resource allocation reservations About this task You can change the physical capacity and performance of the virtual machine by modifying the virtual hardware settings. To avoid software incompatibility, modify virtual hardware settings while deploying a new virtual machine. Procedure 1. Using the Deploy OVF Template option, deploy the Presence Services virtual machine in the vsphere Client. For more information on deploying OVF template, see Deploying Presence Services OVA on page On the Deploy OVF Template screen, ensure that you do not select the Power on after deployment check box. 3. After you finish the deployment, ensure that you are in the inventory view. To do so, press Ctrl+Shift+H. July 2014 Deploying Avaya Aura Presence Services on VMware 24

25 Configuring virtual hardware and resource allocation reservations 4. Select the newly deployed Presence Services virtual machine. 5. Ensure that the new Presence Services virtual machine is on a power off mode. If not, rightclick the new virtual machine and select Power > Shut Down guest. 6. Right-click the new virtual machine and then click Edit Settings... The system displays the Virtual Machine Properties page. July 2014 Deploying Avaya Aura Presence Services on VMware 25

26 Deploying the Avaya Aura Presence Services OVA 7. You can configure your system based upon the number of users you want to support. To do so, use the following table to configure virtual hardware in the Hardware Tab and reservations in the Resources tab: Maximum users CPU Sockets Hardware tab CPU Cores per Sockets Memory Size CPU Reservation Resources tab Memory Reservation GB 9600MHz 8192MB GB 9600MHz 8192MB GB 14400MHz 8192MB GB 14400MHz 12288MB GB 14400MHz 16384MB GB 19200MHz 20480MB GB 19200MHz 24576MB GB 19200MHz 28672MB GB 19200MHz 32768MB GB 19200MHz 32768MB 10, GB 19200MHz 32768MB 11, GB 28800MHz 32768MB 12, GB 28800MHz 32768MB 13, GB 28800MHz 32768MB 14, GB 28800MHz 32768MB 15, GB 28800MHz 32768MB 16, GB 28800MHz 32768MB Note: 8. Click OK. Ensure that your ESX Host supports these requirements in order to power up the VM. 9. Right-click the new virtual machine and select Power > Power On to restart the virtual machine. July 2014 Deploying Avaya Aura Presence Services on VMware 26

27 Starting the Presence Services VM Starting the Presence Services VM About this task Using VMware vsphere Client: Procedure 1. Select the recently deployed target Presence Services VM from the list of VMs on the ESXi Host. 2. Right-click Power On. 3. The vsphere Client may display a message, The available CPU resources in the parent resource pool are insufficient for the operation. This message means that are not enough resources on the host to support the user capacity or configuration provided for the VM. For more information about the user capacity and configuration, see Modifying virtual hardware to reevaluate the hardware configuration settings. You may have to go with a lower setting with support for less user capacity in order to run the Presence Services VM on your VMware host. a. Right-click the Avaya Aura Presence Services VM and click Edit Settings > Resources. Reserve the maximum limit available for each resource such as, CPU, memory. b. Once you make the change, click Power On again. In some cases, the noted CPU adjustments may not correct the power up conditions and the CPU speed may need to be lowered more. This same procedure can be followed to also lower other VM resources as is necessary. July 2014 Deploying Avaya Aura Presence Services on VMware 27

28 Deploying the Avaya Aura Presence Services OVA Important: Any modification to the resource settings is not recommended. Modifying these allocated resources could have a direct impact on the performance, capacity, and stability of the Presence Services virtual machine. To run at full capacity, these resource size requirements must be met; removing or greatly downsizing reservations could put this requirement at risk. Any deviation is at own risk of the customer. Caution: The.ova template is built with configuration values which optimize performance and follow recommended Best Practices. Modifying these values can have a direct impact on the performance, capacity, and stability of the virtual machine. It is the responsibility of the customer to understand the aforementioned impacts when changing configuration values. Avaya Global Support Services (GSS) may not be able to assist in fully resolving a problem if an Avaya Application issue occurs and the reservations have been modified by the customer. Avaya GSS could require the customer to reset the values to the optimized values before starting to investigate the issue. 4. Check the Recent Tasks window for the status of the virtual machine and wait until the Recent Tasks windows shows a completed status. 5. Right-click the deployed Presence Services VM and select Open Console. 6. When prompted, enter the following configuration data: PRESENCE SERVICES - Set Presence IP Address - Set Presence Netmask - Set Presence Default Gateway IP Address - Set Presence DNS Server IP Address - Set Presence FQDN SYSTEM MANAGER - Set System Manager IP Address - Set System Manager FQDN NTP SERVER - Set NTP Server IP Address TIMEZONE - Set Timezone 7. When you finish entering all data, do the following: Enter 10 to APPLY DATA. July 2014 Deploying Avaya Aura Presence Services on VMware 28

29 Running Presence Services installation script Next steps Note: It is not possible to successfully install Avaya Aura Presence Services unless this configuration data is defined. In case you want to re-open the the console for the configuration data, use the /opt/ PS_Install/Utilities/ps_net_conf.sh tool. However, ensure that you do not use the /opt/ps_install/utilities/ps_net_conf.sh tool after the Presence Services installation. If you do so, Presence Services will become nonfunctional. To complete the installation, see Running Presence Services installation script in the Deploying Avaya Aura Presence Services guide on the Avaya support website. Running Presence Services installation script The Presence Services Virtual Machine (VM) installation script uses the X11 Forwarding feature to collect configuration data. The system on which you perform the Presence Services installation must be capable of displaying an X11 window. On a Linux or Windows server, you can use PuTTy to set up an SSH connection to Presence Services VM with X11 Forwarding enabled. Refer to the VMware documentation for specific instructions. The exact instructions might be different based on switch type and VMware version you are running. July 2014 Deploying Avaya Aura Presence Services on VMware 29

30 Deploying the Avaya Aura Presence Services OVA Use the following procedure to start the installation remotely from a Windows server using PuTTY. 1. On the Windows server, launch an X Window System Server application such as XMing. 2. From the Windows server, open an SSH session on Presence Services VM with X11 Forwarding enabled. 3. In the X display location field of PuTTY, enter localhost. 4. Log in to the Presence Services server as a root user. The default password for root is root Change the directory to /opt/ps_install/. 6. On the command prompt, run the following installation script: a. Type./PS-xx.xx.xx.xx-xxxx.sh -ci. For example,./ps sh -ci. b. On the Windows server, a graphical installer is launched, displaying the Pre-Install Configuration Audit page. July 2014 Deploying Avaya Aura Presence Services on VMware 30

31 Running Presence Services installation script Note: 7. Installation Mode: If the system displays a FAIL status for Checking RAM message, ignore the message. A failed status for Checking RAM does not interrupt the installation process. Avaya recommends the Standard Installation. The Advanced Installation allows you to see and potentially modify additional system parameters. You may never need to change the default parameters. July 2014 Deploying Avaya Aura Presence Services on VMware 31

32 Deploying the Avaya Aura Presence Services OVA 8. System Manager Configuration: Specify the details of the System Manager server. 9. Presence Services Configuration: This screen displays the global Presence Services (PS) configuration settings. July 2014 Deploying Avaya Aura Presence Services on VMware 32

33 Running Presence Services installation script 10. Presence Components: Specify the components that you want to install. July 2014 Deploying Avaya Aura Presence Services on VMware 33

34 Deploying the Avaya Aura Presence Services OVA 11. Available XMPP-IM Components: The system displays this panel only if you enable the XMPP-IM Functionality on the Components panel. You can use this panel to allow the installation of additional XMPP-IMspecific components. 12. Session Manager Configuration: July 2014 Deploying Avaya Aura Presence Services on VMware 34

35 Running Presence Services installation script The system displays the Session Manager Configuration Panel only if Session Manager Integration is enabled on the Presence Components panel. 13. AES Component Configuration: The system displays the AES Configuration Panel only if the AES Collector is enabled on the Presence Components panel. 14. SIP Gateway for OCS Configuration: The system displays the SIP Gateway for OCS Panel if the SIP Gateway for OCS component is enabled on the XMPP-IM Components panel. July 2014 Deploying Avaya Aura Presence Services on VMware 35

36 Deploying the Avaya Aura Presence Services OVA 15. IM Transcript Configuration: The system displays the IM Transcript panel in the Advanced Mode if the IM Transcripts is enabled on the XMPP-IM Components Panel. This system does not display it in the Standard Mode as all of the default values can be safely accepted. 16. Local Presence Database Configuration: The system displays the Local Presence Database Configuration panel in the Advanced Mode. This system does not display it in the Standard Mode as all of the default values can be safely accepted. July 2014 Deploying Avaya Aura Presence Services on VMware 36

37 Running Presence Services installation script 17. Data Replication Service Configuration: The Data Replication panel defines data that is copied from System Manager to the local database. The system displays the Data Replication Panel only in the Advanced Mode. It does not display in the Standard Mode because all the default values can be safely accepted. 18. Licensing Service Configuration: The system displays the Licensing Configuration panel in the Advanced Mode. This system does not display it in the Standard Mode as all of the default values can be safely accepted. July 2014 Deploying Avaya Aura Presence Services on VMware 37

38 Deploying the Avaya Aura Presence Services OVA 19. SAL Logging Services Configuration: Specify Secure Access Link (SAL) Logging Service settings. 20. Trust Management Service Configuration: Specify trust management settings. July 2014 Deploying Avaya Aura Presence Services on VMware 38

39 Running Presence Services installation script 21. Installation summary: The Summary Panel reminds you which packs will be installed and to what location. If you do not want to install Presence Services, click Quit. 22. Installation panels: July 2014 Deploying Avaya Aura Presence Services on VMware 39

40 Deploying the Avaya Aura Presence Services OVA The Installation Panels show you how the installation is progressing. This information is written to a log file at: /opt/avaya/presence/. If the installation fails, this file contains useful diagnostic information. The installation takes about 25 minutes, depending on the components that need to be installed, hardware, and network performance. 23. Installation Summary and Post Install Instructions: The system displays the Installation Summary Panel when the installation is complete. The system prompts you to install the Presence Services License to System Manager before continuing. You can also open the Presence Services Web Controller home page. When you click the Done button, the silent installation files are written to /opt/avaya. 24. Click Done. July 2014 Deploying Avaya Aura Presence Services on VMware 40

41 High Availability High Availability Presence Services 6.2 supports High Availability (HA) in both clustered and standalone setups. With HA, you can assign a primary and a backup Presence Services server to each user configured in a cluster. Enabling HA for an N-node cluster requires N+1 Presence Services servers with N primary servers and 1 backup server where the value of N is from 1 to 8. Enabling HA for a standalone system requires one primary and one backup server running in the active-standby mode. The Forged Transmits field must be set to Accept on the port group of the Presence Services guest. For more information, see Example of setting Forget Transmits for the virtual switch. The instructions might be different based on the switch type and the VMware version that you are running. For specific instructions, see VMware documentation. HA requirements For N+1 configuration, you need 2N+1 IP addresses. For example, if you have a three-node HA cluster, you need seven IP addresses. All nodes must be in the same subnetwork. Else, HA does not work. All installations must have the same database password. Example of setting Forged Transmits for the virtual switch Procedure 1. Log in to the vsphere client. 2. In the inventory pane, click the vsphere distributed switch. 3. Click the Configuration tab. 4. In the Hardware section, click Networking. 5. Click Properties. 6. In the Ports tab, select vswitch, and click Edit. 7. In the Security tab, in the Forged Transmits field, select Accept. 8. Click OK. 9. Click Close. Configuring HA during the Presence Services installation Procedure 1. On the Installation Mode page, select HA Installation. July 2014 Deploying Avaya Aura Presence Services on VMware 41

42 Deploying the Avaya Aura Presence Services OVA 2. In the Please choose either install as primary or backup field, select backup or primary. 3. Click Next. 4. On the Presence Services Configuration screen, type the values for the following parameters: Backup Server IP Address: The physical IP address of the system on which the backup server is running. High Availability Node ID: A unique number from 1 to 255. Note: If two nodes try to use the same number, HA does not work. Service IP Address: The virtual IP address on which the primary server is running. July 2014 Deploying Avaya Aura Presence Services on VMware 42

43 High Availability The system prompts for the HA password. July 2014 Deploying Avaya Aura Presence Services on VMware 43

44 Deploying the Avaya Aura Presence Services OVA 5. In the High Availability Password field, type the password. 6. Click Next to continue with the installation. Next steps After the installation, Presence Services runs using the physical IP and not the service IP. Therefore, clients cannot connect. To ensure that Presence Services runs using the service IP, restart Presence Services by running the stop.sh and the start.ps commands. For cluster configuration, you must configure R2R connections on HA to point to service IP addresses or virtual IP addresses of other nodes. You must configure these IP addresses in the Component IP field. Upgrading Presence Services to support HA Before you begin 1. Upgrade the Presence Services nodes to Release Ensure that all presence users have Communication Profile. For more information, see Assigning Presence Profile by using the Presence Communication Profile Migrating tool. July 2014 Deploying Avaya Aura Presence Services on VMware 44

45 High Availability Procedure Perform one or more of the following steps: To convert a Presence Services server to a primary server, run the following script: /opt/ Avaya/Presence/presence/bin/convert_to_ha.sh <HA Node ID> <Service IP> <Backup Server IP>. To convert a Presence Services server of an earlier release to an HA backup server, run the following script: /opt/avaya/presence/presence/bin/convert_to_ha_backup.sh <HA Group Name> <Node Id> <HA Password>. If the Presence Services server is running, the server stops. and you must restart the server. Next steps After upgrading to HA, you must update the R2R configuration to use the Service IP. You must also update the SIP Entity IP address of Presence Services to a service IP address. Starting or stopping the Presence Services server Procedure 1. Log on to the Presence Services server. 2. At the command prompt, perform one of the following steps: a. To start the Presence Services server, type /opt/avaya/presence/ presence/bin/start.sh, and press Enter. You must start the backup server in the end. b. To stop the Presence Services server, type /opt/avaya/presence/ presence/bin/stop.sh, and press Enter. Viewing the status of HA Procedure 1. Log on to the Presence Services server. 2. At the command prompt, type the presstatus or hastatus command. 3. Press Enter. The system displays one of the following outputs: For a standalone configuration: === HA Information === HA is not enabled For an active HA primary server: === HA Information === HA is enabled July 2014 Deploying Avaya Aura Presence Services on VMware 45

46 Deploying the Avaya Aura Presence Services OVA Group Name: group-ming Server Type: primary Server Status: Active Service IP: Backup Server IP: Node ID: 255 DB Replication: Running Last DB Replication: Feb 03 11:44:36,149 GMT For a failover HA primary server: === HA Information === HA is enabled Group Name: group-ming Server Type: backup Server Status: Standby Service IP= NodeID=2 Monitored=yes Transfered at: :49:17 (ok) Service IP= NodeID=255 Monitored=yes Transfered at: :49:18 (ok) For a standby HA backup server: === HA Information === HA is enabled Group Name: group-ming Server Type: backup Server Status: Standby Service IP= NodeID=2 Monitored=yes Transfered at: :49:17 (ok) Service IP= NodeID=255 Monitored=yes Transfered at: :49:18 (ok) For an active or a takeover HA backup server: Last Config File Last Config File Last Config File Last Config File === HA Information === HA is enabled Group Name: group-ming Server Type: backup Server Status: Active (Node 255) Service IP= NodeID=2 Monitored=no Service IP= NodeID=255 Monitored=yes Last Config File Transfered at: :05:02 (ok) For a stopped HA backup server: === HA Information === HA is enabled Group Name: group-ming Server Type: backup Server Status: Stopped Service IP= NodeID=2 Monitored=no Service IP= NodeID=255 Monitored=no You can also check the HA status by running the monit summary command on the primary and backup server. Failover and failback Failover is handled automatically by the backup server when the server detects that the primary server is offline. The backup server stops monitoring the other primary servers. After the backup July 2014 Deploying Avaya Aura Presence Services on VMware 46

47 High Availability server is online, it can take a few minutes for processes to fully stabilize. Users must log out and log in again in order to get the presence. Failback is a manual operation to prevent flipping back and forth due to unstable network conditions. With this operation, you can fully control when a failback occurs. To failback to the primary server once a backup has become active, you must run: 1. stop.sh on the backup server. This command triggers the backup server to create a sync file(s) and transfer it to the primary server. 2. hafailback.sh on the primary server. This command recovers the active data that was running on the backup server. To ignore backup server data during failover, run hafailbackremove.sh on the primary server, and then run start.sh on the primary server. 3. start.sh on backup server. Scripts for HA Script Syntax Description convert_to_ha.sh convert_to_ha_backup.sh convert_to_ha.sh <HA Node ID> <Service IP> <Backup Server IP> convert_to_ha_backup.sh <Group Name><Group ID> <HA Password> To convert a standalone Presence Services server to an HA primary server. To convert a standalone Presence Services server to an HA backup server. hastatus hastatus To display the status of an HA server. changehaparams.sh changevip.sh [-g <Group Name>] [-i --id <Member ID>] [-p --pwd <HA password>] [-v --vip <Service IP>] [-b -- backupip <Backup Server IP> To modify the HA-related parameters. You can select one or more parameters. For example, the following commands are valid: changehaparams.sh -g <Group Name> changehaparams.sh -v <Service IP> b <Backup Server IP> Table continues July 2014 Deploying Avaya Aura Presence Services on VMware 47

48 Deploying the Avaya Aura Presence Services OVA Script Syntax Description changeip.sh changeip.sh <old IP> <new IP> Note: The following parameters are only applicable to the primary server: <Member ID> <Service IP> <Backup Server IP> The <HA password> parameter is only applicable to the backup server. The <Group Name> parameters applies to both the primary and the backup server. To reregister to System Manager with the new RTS attribute. hafailback.sh hafailback.sh To start the primary server using the data from the active backup server. hafailbackremove.sh hafailbackremove.sh To remove the backup data from the primary server. The primary server starts without importing the latest data from the active backup server. Modifying Presence Services virtual machine properties About this task Important: Do not modify the resource settings other than the Avaya recommended settings, for example, removing the resources altogether. Modifying the recommended virtual machine values can affect the performance, capacity, and stability of the Presence Services virtual machine. To run the Presence Services virtual machine at full capacity, you must meet the recommended resource size requirements; removing or greatly downsizing reservations could put the resource size requirement at risk. Any deviation from the requirement is at your own risk. Procedure 1. Right-click the virtual machine and select Edit Settings. The system displays the Virtual Machine Properties dialog box. July 2014 Deploying Avaya Aura Presence Services on VMware 48

49 Modifying Presence Services virtual machine properties 2. Click the Resources tab. The system displays the details for CPU, memory, disk advanced CPU, and advanced memory in the left pane. 3. Select CPU. 4. In the Resource Allocation area, in the Reservation field, perform one of the following to start the virtual machine: Adjust the slider to the appropriate position. Enter the exact value. July 2014 Deploying Avaya Aura Presence Services on VMware 49

50 Chapter 6: Configuration Configuring the virtual machine automatic start and stop settings Configure the virtual machine to start automatically after a power failure or a restart of the hypervisor. The default is set to no. In high availability (HA) clusters, the VMware HA software ignores the Startup selections. Note: You can skip the this procedure, if you have enable the High Availability option for cluster. 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 under Automatic Startup. 8. Click OK. Example The following is an example of the Virtual Machine Startup/Shutdown screen. July 2014 Deploying Avaya Aura Presence Services on VMware 50

51 Downloading and running the Presence Services Service Pack installation script Next steps For more information on the Presence Services VM Installation script using an X11 forwarding feature, see the Deploying Avaya Aura Presence Services guide on the Avaya support website. Downloading and running the Presence Services Service Pack installation script Before you begin Ensure that Presence Services is successfully installed. Procedure 1. From PLDS, download the latest service pack file. For example, PS-xx.xx.xx.xx.zip. For more information on service packs, see 2. Log in to the Presence server as a cust user. 3. Gain root access by using the following command, su root. July 2014 Deploying Avaya Aura Presence Services on VMware 51

52 Configuration 4. At the command prompt, create a directory for the service pack. For example, enter mkdir /opt/ps_install/spx, where x stands for the service pack version. 5. To change the location of the directory, enter cd /opt/ps_install/spx. 6. Copy the SPx file to the Avaya Aura Presence server to, directory /opt/ps_install/spx. 7. Unzip the file. For example, enter unzip PS-xx.xx.xx.xx.zip, where xx.xx.xx.xx is the release number. 8. Stop Avaya Aura Presence Services by using the /opt/avaya/presence/ presence/bin/stop.sh command. Note: It is important to verify that Presence Services has stopped before you proceed with the installation of the service pack. Use monit summary command to verify. The output of the command should show a not monitored status for processes except for System that appears as running. Do not install Presence Services service pack untill you stop all the processes. 9. Run the Avaya Aura Presence Services SPx installation script from the /opt/ps_install/spx directory. a. Enter./PS-xx.xx.xx.xx.sh ci autoinstall_presence_services.properties b. Wait for the Service Pack to be installed. c. On the successful completion, the system displays the Completed installation message. 10. Restart Presence Services by using the /opt/avaya/presence/presence/bin/ start.sh command. 11. Check that Avaya Aura Presence Services has started successfully. For more information, see Verifying the Avaya Aura Presence Services VM status. July 2014 Deploying Avaya Aura Presence Services on VMware 52

53 Supporting up to 10,000 users Supporting up to 10,000 users Before you begin If you have already installed Presence Services then you must uninstall Presence Services. Procedure 1. Install the Presence Services OVA file. For more information, see the Deploying the Avaya Aura Presence ServicesOVA chapter. 2. Log in to the Presence server as a root user and in the /etc/profile file, change the value for ENABLE_LOW_SPEC_PS from 1 to 0. To support up to 10,000 users in a Virtualized environment, set the ENABLE_LOW_SPEC_PS environment parameter to 0. The system, by default, sets the value for the ENABLE_LOW_SPEC_PS environment parameter to 1, which supports 2500 user. 3. Log out and log in to the Presence server again for the changes to take effect. 4. Install Presence Services. For more information, see the Deploying the Avaya Aura Presence Services OVA chapter. 5. Restart Presence Services. July 2014 Deploying Avaya Aura Presence Services on VMware 53

54 Chapter 7: Post-installation verification Verifying the Presence Services VM status Procedure 1. Log in to the Presence Services VM as a cust user to use a console or an SSH session. 2. Gain access as root. 3. Run the following command, monit summary and ensure that all the processes are running. 4. Check the state of already configured Presence Services components by running the following command: /opt/avaya/presence/presence/bin/presstatus. July 2014 Deploying Avaya Aura Presence Services on VMware 54

55 Checking the synchronization of Presence Services with System Manager 5. On your browser, enter the IP address of the Presence Services Web interface to confirm if the Web interface is reachable. Checking the synchronization of Presence Services with System Manager Procedure 1. Log in to System Manager Web Console on which you have configured the target Avaya Aura Presence Services VM. 2. On System Manager Dashboard, click Services > Replication. 3. On the Replica Groups page, ensure that the target Presence Services VM is Synchronized with System Manager. July 2014 Deploying Avaya Aura Presence Services on VMware 55

56 Post-installation verification Verifying user end points About this task Using this task, you can verify if the configured end points are displaying presence information. Procedure 1. Log in to System Manager Web Console. 2. Verify the following: a. On System Manager Dashboard, click Users > User Management > Manage Users. b. Select a user, and click Edit. The system displays the User Profile Edit page. c. Click the Identity tab, verify the Login Name field value, <user>@global.<domain>. value must match with the value defined for the Domain Susbtitution From field. d. To verify the Domain Susbtitution From field, on System Manager Dashboard, click Elements > Presence > Configuration. The system displays Presence Configuration Properties. July 2014 Deploying Avaya Aura Presence Services on VMware 56

57 Verifying user end points 3. On System Manager Dashboard, click Users > User Management > Manage Users. 4. Select a user and click Edit. 5. On the Communication Profile tab, verify the following information for a user profile: Type: Avaya SIP Handle:<user> Domain:<domain> Note: The system automatically adds the Avaya XMPP value in the Type field after you save the user. This value must match with the Domain Substitution To field. 6. Configure and verify end points for Presence Services. For example, if you have configured Avaya one-x Communicator as an end point, do the following: On Avaya one-x Communicator, see General Settings > Accounts > IM and Presence. July 2014 Deploying Avaya Aura Presence Services on VMware 57

58 Post-installation verification Note: The value in the Server field is the configured IP Address for the Avaya Aura Presence Services VM. 7. When you log in to Avaya one-x Communicator, check your presence status. 8. Verify the presence information of another configured online user on Avaya one-x Communicator July 2014 Deploying Avaya Aura Presence Services on VMware 58

59 Verifying user end points 9. Verify that the Presence changes when you make a call. July 2014 Deploying Avaya Aura Presence Services on VMware 59

60 Chapter 8: Maintenance Updates/patches Avaya Aura Presence Services VM updates You must follow the standard official procedure for applying Service Packs and /or Patches for Presence Servers. Before applying any Service Packs and/or Patches, you must take a snapshot of Presence Services. For more information on service packs and patches, see the Avaya Aura Presence Services Service Pack Release Notes. Upgrades Overview Use the native upgrade procedure for Presence Services to upgrade the Presence Services VM. Before upgrading, you must take a snapshot of the Presence Services VM. For more information about snapshots, see VMware snapshots. For more information about upgrading Presence Services, see Deploying Avaya Aura Presence Services. Backup and restore Native backup and restore Use the native methods of backup and restore of Avaya Aura Presence Services data for longterm backup and recovery when running on VMware. Presence Services data exists both internally on the VM itself and on Avaya Aura System Manager. To take a full backup of the Presence Services data, do the following: Take a backup of the Avaya Aura Presence Services data on the VM using native scripts. July 2014 Deploying Avaya Aura Presence Services on VMware 60

61 Upgrades Note: This affects the service. Take a backup of the Avaya Aura System Manager data using native methods. Related links Backing up the Presence Services VM on page 61 Restoring the Avaya Aura Presence Services VM on page 62 Backing up the Presence Services VM Procedure 1. At the command prompt, stop Presence Services XCP process(es) using the monit stop jabberd command. 2. You must also stop the cm process using the monit stop cm command. 3. At the command prompt, take a backup using the native script, /opt/avaya/presence/ presence/bin/backup.sh. Note: The system stores a local backup copy at the following location, /var/presence/ backup/archive/<backup_*.tgz> 4. Copy the backup file for remote storage. Linux: Use the Linux scp command to copy the files to a remote server. For example: scp user@ps_vm _Ipor_name:/directory/filename to_remote_system_location Windows: Use the WinSCP utility to copy the files to a remote server. See Transferring files using WinSCP on page Restart Presence Services XCP process(es) using the monit start jabberd command. 6. Restart the cm process using the monit start cm command. July 2014 Deploying Avaya Aura Presence Services on VMware 61

62 Maintenance 7. Wait untill all the processes show a running status. Related links Native backup and restore on page 60 Restoring the Avaya Aura Presence Services VM Procedure 1. If you store the Avaya Aura Presence Services (PS) backup archive remotely, copy the Avaya Aura Presence Services (PS) backup archive onto the Presence Services server. 2. At the command prompt, stop the Presence Services XCP process(es) using the monit stop jabberd command. 3. Take a backup using the native script, /opt/avaya/presence/presence/bin/ restore.sh -f <backup archive file, backup_*.tgz>. Note: The system stores a local backup archive at the following location, /var/presence/ backup/archive/<backup_*.tgz>. 4. Restart Presence Services XCP process(es) using the monit start jabberd command. 5. Wait untill all the processes show a running status. Related links Native backup and restore on page 60 VMware snapshots VMware Snapshots should not be relied upon as a robust backup and recovery method. Instead they are better suited to short-term point-in-time copies of the running system before major upgrades or before patching the system. This is due to the potential for losing the snapshot files along with the files containing the virtual machine data as well as the negative performance impacts that result from using snapshots for long periods of time. If snapshots are to be used over a long July 2014 Deploying Avaya Aura Presence Services on VMware 62

63 Upgrades period of time then they should be regularly consolidated. However, this has associated risk if the consolidation fails. In addition, taking Snapshots of Avaya Aura Presence Services VM can be service effecting. It is therefore recommended that before taking a Snapshot or Reverting to a previous Snapshot, you must stop Presence Services using the following command, /opt/avaya/presence/ presence/bin/stop.sh. Note: It is important to verify that Presence Services has stopped before proceeding with the Snapshot. This can be done using the following command, monit summary. Related links Backing up a snapshot on page 63 Restoring a snapshot on page 64 Consolidating snapshots on page 64 Backing up a snapshot Before you begin Ensure the target Presence Services is stopped. If not, use the following command to stop Presence Services, /opt/avaya/presence/presence/bin/stop.sh. About this task Using the VMware vsphere Client: Procedure 1. Select the target Presence Services VM, right-click and select Snapshot. 2. Click Take Snapshot. 3. Enter a Name and Description for the Snapshot. 4. Set the following Snapshot options: Uncheck the Snapshot the virtual machine s memory option. Check the Select Quiesce guest file system (Needs VMware Tools installed) option. Note: 5. Click OK. Quiescing indicates pausing or altering the state of running processes, particularly those that might modify information stored on disk during a backup, to guarantee a consistent and usable backup. 6. Check in the Recent Tasks window for the Status of the Create virtual machine snapshot task and wait until this shows a Completed state. 7. Start Presence Services using the /opt/avaya/presence/presence/bin/start.sh command. July 2014 Deploying Avaya Aura Presence Services on VMware 63

64 Maintenance Related links VMware snapshots on page 62 Restoring a snapshot Before you begin Ensure the target Presence Services is stopped. If not, use the following command to stop Presence Services, /opt/avaya/presence/presence/bin/stop.sh. About this task Using the VMware vsphere Client: Procedure 1. Select the target Presence Services VM, right-click and select Snapshot. 2. Open Snapshot Manager. 3. Select Snapshot to which you want to revert to. 4. Click Goto. 5. Check the Recent Tasks window for the status of the Revert snapshot task and wait until this shows a Completed state. 6. Start Presence Services using the /opt/avaya/presence/presence/bin/start.sh command. Related links VMware snapshots on page 62 Consolidating snapshots Before you begin Ensure the target Presence Services is stopped. If not, use the following command to stop Presence Services, /opt/avaya/presence/presence/bin/stop.sh. About this task You must consolidate snapshots on a regular basis in order to improve performance and reduce disk usage. In order to merge the snapshot delta disks back into the VM s base disk, you must delete the stored snapshots. Note: The actual Consolidate option allows end-users, in the event of a consolidate failure, to do the consolidate operation for themselves without opening a Service Request with VMware. If a commit / delete operation is not able to merge the snapshot delta disks into the base disk of the VM, the system displays a warning message in the user interface. Using the VMware vsphere Client: Procedure 1. Select the target Presence Services VM, right-click and select Snapshot. July 2014 Deploying Avaya Aura Presence Services on VMware 64

65 Migration 2. Open Snapshot Manager. 3. Select a snapshot that you want to delete and then click Delete. 4. Check the Recent Tasks window for the status of the Revert snapshot task and wait until this shows a Completed state. 5. Start Presence Services using the /opt/avaya/presence/presence/bin/start.sh command. Related links VMware snapshots on page 62 Migration Migration data Before migrating from an earlier release of Presence Services to Release 6.2, record the Presence Services configuration information. You must record the Presence Services configuration information in the data collection worksheet. For more information, see Deploying Avaya Aura Presence Services. 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. 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/. July 2014 Deploying Avaya Aura Presence Services on VMware 65

66 Maintenance 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. Migrating Presence Services installed on System Platform You can migrate a Presence server installed on System Platform in the following ways: Performing a fresh installation. For information on fresh installation, see the Deploying the Avaya Aura Presence Services OVA chapter. Duplicating an existing set up. Related links Duplicating an existing server on page 66 Duplicating an existing server Procedure 1. Manually record the existing configuration data from your existing Presence server. To do so, perform the following: a. Log in to the Presence server. b. Locate the autoinstall_ps.properties file, which resides in the directory from where you launch Presence Services originally, for example, /opt/avaya/, and record the configuration data. For more information, see Customer configuration data on page Manually record configuration settings from the XCP Controller Web interface. For more information, see Backup and restore. 3. Stop the Presence server using the /opt/avaya/presence/presence/bin/stop.sh command. 4. Re-image the physical host server, Dom0, with a new ESX operating system. For more information, see the VMware Best Practices for performance chapter. 5. Install VMware infrastructure (ESX server, VSphere client) on the server. For more information, see the Planning and configuration and VMware Best Practices for performance chapter. Skip the re-imaging the physical host sever and installing VMware infrastructure steps, if you do not have an existing infrastructure. Else, proceed to deploying the Presence Services OVA file step. July 2014 Deploying Avaya Aura Presence Services on VMware 66

67 Changing Presence Services Network Identity 6. Deploy the Presence Services OVA file. During the deployment, enter the values that you recorded earlier from the autoinstall_ps.properties file. For more information, see the Deploying the Avaya Aura Presence Services OVA chapter. 7. Log in to the XCP Controller Web interface and modify the values that you recorded earlier from the XCP Controller Web interface. For more information, see Backup and restore. Related links Migrating Presence Services installed on System Platform on page 66 Changing Presence Services Network Identity Changing the Presence Services hostname About this task Note: Presence Services has the following limitations with network identity : hostname IP address Changing the hostname of Presence Services requires a re-install of Presence Services. For more information Presence Services hostname, see Administering Avaya Aura Presence Services on the Avaya support website. changeip.sh tool About this task Using this tool, you can change the IP address stored in the Presence Services configuration files. You must execute the command as a root user. Change the IP address of the server (network interface) manually. The changeip.sh script only changes the IP addresses within the Presence Services product. Procedure 1. Log in to the Presence server as a root user. 2. Stop Presence Services by using the /opt/avaya/presence/presence/bin/stop.sh command. July 2014 Deploying Avaya Aura Presence Services on VMware 67

68 Maintenance Warning: Before you proceed, verify that Presence Services has been stopped. To verify, use the monit summary command. 3. Change the IP address of the server manually by using the vi /etc/sysconfig/ network-scripts/ifcfg-eth0 command. 4. Modify the IPADDR field with the new IP address and then save the file. 5. Restart network service by using the service network restart command. If you are using a remote shell session, you will lose the session on this IP. 6. Using a remote shell session, restart another session with the new IP. 7. Go to the bin folder. For example: cd /opt/avaya/presence/presence/bin. 8. At the command prompt, type./changeip.sh<old IP address><new IP address>. Presence Services starts automatically after you make the changes. For more information, see Quick reference commands. 9. Log in to Presence Services Web Controller and verify that all the services are in a running state. July 2014 Deploying Avaya Aura Presence Services on VMware 68

69 Chapter 9: Troubleshooting Viewing the status of the Presence Services components presstatus The presstatus script is installed in the folder /opt/avaya/presence/presence/bin. The presstatus is a stand-alone command line tool to generate the current state of the Presence Services components. This enables you to know the current state of Presence Services components. You can run the presstatus in the interactive and the command line modes. Interactive mode Use System Manager to view the status of Presence Services components. Command line mode Run command line arguments to view the status of Presence Services components. Viewing monit using a CLI About this task Using the Presence server CLI, you can view a summary list of the status of all the monitored processes. Using the CLI, you can also display more detailed information about individual monitored processes. Procedure 1. To display a summary, type monit summary. 2. To display details, type monit status. July 2014 Deploying Avaya Aura Presence Services on VMware 69

70 Troubleshooting Presence Services logging Overview Warning: You must configure logging levels under the supervision of an Avaya Support personnel. You can configure logging for specific components using the Presence Services log4j.xml configuration file (/opt/avaya/presence/presence/lib/path/log4j.xml). Log4j.xml defines two types of appenders, SPIRIT_FILE and LOCAL_FILE. The SPIRIT_FILE (/var/log/presence/presence-container-1.presence.log) is for the exclusive use of the SAL Agent. So it conforms to the Avaya Common Logging Format (CLF) and is limited to INFO logging and above. The LOCAL_FILE (/var/log/presence/presence-container-1.presence_local.log) on the other hand is for Presence Services administrative users. It is easily readable and contains log messages at all levels. All Operational Logging from Presence components use loggers with the events.operational prefix. <logger name="events.operational.com.avaya.presence.server.licensing"> <level value="warn#com.avaya.common.logging.client.loglevel"/> </logger> In the example above: events.operational indicates that this is Operational Logging. com.avaya.presence.server indicates the Presence Product. Licensing indicates the name of the component. WARN indicates the level of logging you require for this component. The rest of the loggers (including the root logger) are for debugging only. Contact the support engineers for debugging. You could effectively disable debug logging. The section below shows you how to allow logging of only FATAL debug messages. <! - - Debug logging - goes to LOCAL_FILE - -> <root> <level value="fatal#com.avaya.common.logging.client.loglevel"/> <appender-ref ref="local_file"/> </root> Note: The logging levels are: FATAL, ERROR, WARN, INFO, FINE, FINER, FINEST. July 2014 Deploying Avaya Aura Presence Services on VMware 70

71 Presence Services logging Changing the default logging level Procedure 1. Log in to the Presence server. 2. Make changes to the /opt/avaya/presence/presence/lib/path/log4j.xml file. 3. Enable the relevant section and change the level as required. <logger name="events.operational"> <level value="warn#com.avaya.common.logging.client.loglevel"/ > </logger> to, for example, <logger name="events.operational"> <level value="info#com.avaya.common.logging.client.loglevel"/ > </logger> Note: The system generates more log records if you set a level lower. Do not set a low level for a long period of time. If you do, you will have to navigate through unwieldy log files. Set a lower log level for individual components as opposed to changing the default for the whole Presence server. If the log level of a component is increased to the DEBUG level then you must change it back to the ERROR level as soon as the required debug logs are collected for debugging. Viewing logs on System Manager About this task Note: Presence Services integrates with SAL to send log files to System Manager. Procedure 1. Log in to System Manager Web Console by entering the System Manager virtual machine IP address in a Web browser, as follows: Manager IP address>/ SMGR 2. On System Manager Dashboard, click Services > Events > Logs > Log Viewer. You can view the logs and export them to another application as a comma separated values (.csv) file. For more information on logs, see Troubleshooting Avaya Aura Presence Services on the Avaya support website. July 2014 Deploying Avaya Aura Presence Services on VMware 71

72 Appendix A: Best Practices for VMware performance and features 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 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. July 2014 Deploying Avaya Aura Presence Services on VMware 72

73 BIOS Note: 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. 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. 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. 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. 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. July 2014 Deploying Avaya Aura Presence Services on VMware 73

74 Best Practices for VMware performance and features 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. Timekeeping For accurate timekeeping, use the Network Time Protocol (NTP) as a time source instead of the ESXi hypervisor. 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. July 2014 Deploying Avaya Aura Presence Services on VMware 74

75 VMware networking best practices 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. 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. July 2014 Deploying Avaya Aura Presence Services on VMware 75

76 Best Practices for VMware performance and features Connect all physical NICs that are connected to the same distributed switch to the same physical network. Configure all VMkernal vnics to be the same IP Maximum Transmission Unit (MTU). 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. July 2014 Deploying Avaya Aura Presence Services on VMware 76

77 VMware networking best practices 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 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. July 2014 Deploying Avaya Aura Presence Services on VMware 77

78 Best Practices for VMware performance and features 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. July 2014 Deploying Avaya Aura Presence Services on VMware 78