Deploying WebLM in Virtualized Environment R81x Issue2 Dec2019

Deploying standalone Avaya WebLM in
Virtualized Environment
Release 8.1.x
Issue 2
July 2018
© 2018, Avaya Inc. YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU
All Rights Reserved. MUST NOT ACCESS OR USE THE HOSTED SERVICE OR
AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED
Notice SERVICE.
While reasonable efforts have been made to ensure that the Licenses
information in this document is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
the right to make changes and corrections to the information in this WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO,
document without the obligation to notify any person or organization UNDER THE LINK “AVAYA SOFTWARE LICENSE TERMS (Avaya
of such changes. Products)” OR SUCH SUCCESSOR SITE AS DESIGNATED BY
AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS,
Documentation disclaimer USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED
“Documentation” means information published in varying mediums FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA
which may include product information, operating instructions and CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL
performance specifications that are generally made available to users AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER.
of products. Documentation does not include marketing materials. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING,
Avaya shall not be responsible for any modifications, additions, or AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE
deletions to the original published version of Documentation unless WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA
such modifications, additions, or deletions were performed by or on AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA
the express behalf of Avaya. End User agrees to indemnify and hold RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU
harmless Avaya, Avaya's agents, servants and employees against all AND ANYONE ELSE USING OR SELLING THE SOFTWARE
claims, lawsuits, demands and judgments arising out of, or in WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR
connection with, subsequent modifications, additions or deletions to USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,
this documentation, to the extent made by End User. YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM
YOU ARE INSTALLING, DOWNLOADING OR USING THE
Link disclaimer SOFTWARE (HEREINAFTER REFERRED TO
Avaya is not responsible for the contents or reliability of any linked INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO
websites referenced within this site or Documentation provided by THESE TERMS AND CONDITIONS AND CREATE A BINDING
Avaya. Avaya is not responsible for the accuracy of any information, CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
statement or content provided on these sites and does not APPLICABLE AVAYA AFFILIATE (“AVAYA”).
necessarily endorse the products, services, or information described Avaya grants You a license within the scope of the license types
or offered within them. Avaya does not guarantee that these links will described below, with the exception of Heritage Nortel Software, for
work all the time and has no control over the availability of the linked which the scope of the license is detailed below. Where the order
pages. documentation does not expressly identify a license type, the
Warranty applicable license will be a Designated System License as set forth
below in the Designated System(s) License (DS) section as
Avaya provides a limited warranty on Avaya hardware and software. applicable. The applicable number of licenses and units of capacity
Refer to your sales agreement to establish the terms of the limited for which the license is granted will be one (1), unless a different
warranty. In addition, Avaya’s standard warranty language, as well as number of licenses or units of capacity is specified in the
information regarding support for this product while under warranty is documentation or other materials available to You. “Software” means
available to Avaya customers and other parties through the Avaya computer programs in object code, provided by Avaya or an Avaya
Support website: https://support.avaya.com/helpcenter/ Channel Partner, whether as stand-alone products, pre-installed on
getGenericDetails?detailId=C20091120112456651010 under the link hardware products, and any upgrades, updates, patches, bug fixes,
“Warranty & Product Lifecycle” or such successor site as designated or modified versions thereto. “Designated Processor” means a single
by Avaya. Please note that if You acquired the product(s) from an stand-alone computing device. “Server” means a set of Designated
authorized Avaya Channel Partner outside of the United States and Processors that hosts (physically or virtually) a software application
Canada, the warranty is provided to You by said Avaya Channel to be accessed by multiple users. “Instance” means a single copy of
Partner and not by Avaya. the Software executing at a particular time: (i) on one physical
“Hosted Service” means an Avaya hosted service subscription that machine; or (ii) on one deployed software virtual machine (“VM”) or
You acquire from either Avaya or an authorized Avaya Channel similar deployment.
Partner (as applicable) and which is described further in Hosted SAS License types
or other service description documentation regarding the applicable
hosted service. If You purchase a Hosted Service subscription, the Designated System(s) License (DS). End User may install and use
foregoing limited warranty may not apply but You may be entitled to each copy or an Instance of the Software only: 1) on a number of
support services in connection with the Hosted Service as described Designated Processors up to the number indicated in the order; or 2)
further in your service description documents for the applicable up to the number of Instances of the Software as indicated in the
Hosted Service. Contact Avaya or Avaya Channel Partner (as order, Documentation, or as authorized by Avaya in writing. Avaya
applicable) for more information. may require the Designated Processor(s) to be identified in the order
by type, serial number, feature key, Instance, location or other
Hosted Service specific designation, or to be provided by End User to Avaya through
THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA electronic means established by Avaya specifically for this purpose.
HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA Heritage Nortel Software
CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE
FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA “Heritage Nortel Software” means the software that was acquired by
WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO UNDER Avaya as part of its purchase of the Nortel Enterprise Solutions
THE LINK “Avaya Terms of Use for Hosted Services” OR SUCH Business in December 2009. The Heritage Nortel Software is the
SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE software contained within the list of Heritage Nortel Products located
APPLICABLE TO ANYONE WHO ACCESSES OR USES THE at https://support.avaya.com/LicenseInfo under the link “Heritage
HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED Nortel Products” or such successor site as designated by Avaya. For
SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON Heritage Nortel Software, Avaya grants Customer a license to use
BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE Heritage Nortel Software provided hereunder solely to the extent of
DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY the authorized activation or authorized usage level, solely for the
AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF purpose specified in the Documentation, and solely as embedded in,
YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A for execution on, or for communication with Avaya equipment.
COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT Charges for Heritage Nortel Software may be based on extent of
YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE activation or use authorized as specified in an order or invoice.
TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF
Copyright PARTNER ACKNOWLEDGES AND AGREES THE AVAYA
CHANNEL PARTNER IS RESPONSIBLE FOR ANY AND ALL
Except where expressly stated otherwise, no use should be made of RELATED FEES AND/OR ROYALTIES. THE H.264 (AVC) CODEC
materials on this site, the Documentation, Software, Hosted Service, IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE
or hardware provided by Avaya. All content on this site, the FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES
documentation, Hosted Service, and the product provided by Avaya IN WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I)
including the selection, arrangement and design of the content is ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD
owned either by Avaya or its licensors and is protected by copyright (“AVC VIDEO”) AND/OR (II) DECODE AVC VIDEO THAT WAS
and other intellectual property laws including the sui generis rights ENCODED BY A CONSUMER ENGAGED IN A PERSONAL
relating to the protection of databases. You may not modify, copy, ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER
reproduce, republish, upload, post, transmit or distribute in any way LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED
any content, in whole or in part, including any code and software OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL
unless expressly authorized by Avaya. Unauthorized reproduction, INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS
transmission, dissemination, storage, and or use without the express MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://
written consent of Avaya can be a criminal, as well as a civil offense
WWW.MPEGLA.COM.
under the applicable law.
Compliance with Laws
Virtualization
You acknowledge and agree that it is Your responsibility for
The following applies if the product is deployed on a virtual machine.
complying with any applicable laws and regulations, including, but not
Each product has its own ordering code and license types. Unless
limited to laws and regulations related to call recording, data privacy,
otherwise stated, each Instance of a product must be separately
intellectual property, trade secret, fraud, and music performance
licensed and ordered. For example, if the end user customer or
rights, in the country or territory where the Avaya product is used.
Avaya Channel Partner would like to install two Instances of the
same type of products, then two products of that type must be Preventing Toll Fraud
ordered.
“Toll Fraud” is the unauthorized use of your telecommunications
Third Party Components system by an unauthorized party (for example, a person who is not a
corporate employee, agent, subcontractor, or is not working on your
“Third Party Components” mean certain software programs or
company's behalf). Be aware that there can be a risk of Toll Fraud
portions thereof included in the Software or Hosted Service may
associated with your system and that, if Toll Fraud occurs, it can
contain software (including open source software) distributed under
result in substantial additional charges for your telecommunications
third party agreements (“Third Party Components”), which contain
services.
terms regarding the rights to use certain portions of the Software
(“Third Party Terms”). As required, information regarding distributed Avaya Toll Fraud intervention
Linux OS source code (for those products that have distributed Linux
OS source code) and identifying the copyright holders of the Third If You suspect that You are being victimized by Toll Fraud and You
Party Components and the Third Party Terms that apply is available need technical assistance or support, call Technical Service Center
in the products, Documentation or on Avaya’s website at: https:// Toll Fraud Intervention Hotline at +1-800-643-2353 for the United
support.avaya.com/Copyright or such successor site as designated States and Canada. For additional support telephone numbers, see
by Avaya. The open source software license terms provided as Third the Avaya Support website: https://support.avaya.com or such
successor site as designated by Avaya.
Party Terms are consistent with the license rights granted in these
Software License Terms, and may contain additional rights benefiting Security Vulnerabilities
You, such as modification and distribution of the open source
software. The Third Party Terms shall take precedence over these Information about Avaya’s security support policies can be found in
Software License Terms, solely with respect to the applicable Third the Security Policies and Support section of https://
Party Components to the extent that these Software License Terms support.avaya.com/security.
impose greater restrictions on You than the applicable Third Party Suspected Avaya product security vulnerabilities are handled per the
Terms. Avaya Product Security Support Flow (https://
The following applies only if the H.264 (AVC) codec is distributed with support.avaya.com/css/P8/documents/100161515).
the product. THIS PRODUCT IS LICENSED UNDER THE AVC Downloading Documentation
PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A
CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE For the most current versions of Documentation, see the Avaya
REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH Support website: https://support.avaya.com, or such successor site
THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC as designated by Avaya.
VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A Contact Avaya Support
PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO
PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS See the Avaya Support website: https://support.avaya.com for
GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. product or Hosted Service notices and articles, or to report a problem
ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA, with your Avaya product or Hosted Service. For a list of support
L.L.C. SEE HTTP://WWW.MPEGLA.COM. telephone numbers and contact addresses, go to the Avaya Support
website: https://support.avaya.com (or such successor site as
Service Provider designated by Avaya), scroll to the bottom of the page, and select
THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’S Contact Avaya Support.
HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT Trademarks
OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS
SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE The trademarks, logos and service marks (“Marks”) displayed in this
PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY FROM site, the Documentation, Hosted Service(s), and product(s) provided
THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL PARTNER’S by Avaya are the registered or unregistered Marks of Avaya, its
HOSTING OF AVAYA PRODUCTS MUST BE AUTHORIZED IN affiliates, its licensors, its suppliers, or other third parties. Users are
WRITING BY AVAYA AND IF THOSE HOSTED PRODUCTS USE not permitted to use such Marks without prior written consent from
OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING Avaya or such third party which may own the Mark. Nothing
BUT NOT LIMITED TO MICROSOFT SOFTWARE OR CODECS, contained in this site, the Documentation, Hosted Service(s) and
THE AVAYA CHANNEL PARTNER IS REQUIRED TO product(s) should be construed as granting, by implication, estoppel,
INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE or otherwise, any license or right in and to the Marks without the
AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’S EXPENSE, express written permission of Avaya or the applicable third party.
DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER. Avaya is a registered trademark of Avaya Inc.
WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL
PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED
THE H.264 CODEC OR H.265 CODEC, THE AVAYA CHANNEL
All non-Avaya trademarks are the property of their respective owners.
Linux® is the registered trademark of Linus Torvalds in the U.S. and
other countries.
Contents
Chapter 1: Introduction............................................................................................................ 9
Purpose.................................................................................................................................. 9
Prerequisites........................................................................................................................... 9
Change history...................................................................................................................... 10
Chapter 2: Virtualized Environment overview...................................................................... 11
®
Avaya Aura Virtualized Environment overview........................................................................ 11
Kernel-based Virtual Machine overview................................................................................... 11
Supported applications in Virtualized Environment................................................................... 12
Virtualized Environment components...................................................................................... 12
Chapter 3: Planning and configuration................................................................................. 13
Hardware support.................................................................................................................. 13
Supported hardware for VMware...................................................................................... 13
Supported hardware for KVM........................................................................................... 13
Configuration tools and utilities............................................................................................... 13
Supported tools for deploying the KVM OVA...................................................................... 14
Supported footprints for WebLM Server .................................................................................. 14
Software details of WebLM..................................................................................................... 14
Downloading software from PLDS.......................................................................................... 14
Site preparation checklist for KVM.......................................................................................... 15
Customer configuration data for WebLM.................................................................................. 16
Deployment guidelines........................................................................................................... 17
SAL Gateway........................................................................................................................ 17
Chapter 4: Deploying WebLM on VMware............................................................................ 18
®
Checklist for deploying WebLM on VMware ........................................................................... 18
Deploying the WebLM OVA by using vSphere Web Client......................................................... 19
Deploying the application OVA using vSphere Web Client by accessing the host directly............ 21
Deployment of cloned and copied OVAs.................................................................................. 22
Installing a WebLM patch, feature pack, or service pack........................................................... 23
Starting the WebLM server virtual machine.............................................................................. 23
Chapter 5: Deploying WebLM on Kernel-based Virtual Machine....................................... 25
Extracting KVM OVA.............................................................................................................. 25
Deploying KVM OVA by using Virt Manager............................................................................. 25
Deploying WebLM KVM OVA from CLI by using virsh............................................................... 26
Deploying application by using OpenStack.............................................................................. 27
Connecting to OpenStack Dashboard............................................................................... 27
Uploading the qcow2 image............................................................................................. 27
Flavors........................................................................................................................... 28
Creating a security group................................................................................................. 28
Adding rules to a security group........................................................................................ 29
July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 5

Comments on this document? infodev@avaya.com
Contents
Deploying application by using OpenStack........................................................................ 29

Configuring application instance....................................................................................... 30
Deploying application by using Nutanix................................................................................... 31
Logging on to the Nutanix Web console............................................................................ 31
Transferring the files by using the WinSCP utility............................................................... 31
Uploading the qcow2 image............................................................................................. 31
Creating the virtual machine by using Nutanix.................................................................... 32
Starting a virtual machine................................................................................................. 34
Configuring the virtual machine........................................................................................ 34
Deploying application by using Red Hat Virtualization Manager................................................. 35
Logging on to the Red Hat Virtualization Manager Web console.......................................... 35
Uploading the disk........................................................................................................... 35
Creating the virtual machine by using Red Hat Virtualization Manager................................. 36
Starting a virtual machine................................................................................................. 37
Configuring the virtual machine........................................................................................ 37
Chapter 6: Managing the ESXi host by using SDM............................................................. 38
Adding a location................................................................................................................... 38
Adding an Appliance Virtualization Platform or ESXi host......................................................... 38
Adding a software-only platform.............................................................................................. 39
Managing vCenter................................................................................................................. 40
Creating a role for a user................................................................................................. 40
Adding a vCenter to Solution Deployment Manager........................................................... 41
Editing vCenter............................................................................................................... 43
Deleting vCenter from Solution Deployment Manager......................................................... 43
Map vCenter field descriptions.......................................................................................... 43
New vCenter and Edit vCenter field descriptions................................................................ 44
Chapter 7: Configuration........................................................................................................ 47
Application Deployment field descriptions................................................................................ 47
Updating the WebLM server memory...................................................................................... 50
Updating network parameters for cloned WebLM..................................................................... 50
Chapter 8: Post-deployment and upgrade verifications..................................................... 52
Post-upgrade checklist........................................................................................................... 52
Logging on to the WebLM web console................................................................................... 52
Rehosting license files........................................................................................................... 53
Verifying the WebLM software version..................................................................................... 53
Upgrade job status................................................................................................................ 54
Upgrade job status.......................................................................................................... 54
Viewing the Upgrade job status........................................................................................ 54
Editing an upgrade job..................................................................................................... 55
Deleting the Upgrade jobs................................................................................................ 55
Upgrade Job Status field descriptions............................................................................... 56
Rollback process................................................................................................................... 56
Upgrade rollback............................................................................................................. 56

Contents
Rolling back an upgrade.................................................................................................. 57

Enhanced Access Security Gateway overview......................................................................... 57
Enhanced Access Security Gateway (EASG) overview....................................................... 57
Chapter 9: Maintenance......................................................................................................... 60
Maintenance......................................................................................................................... 60
Changing the IP, FQDN, DNS, Gateway, or Netmask addresses......................................... 60
Configuring multiple DNS IP addresses............................................................................. 61
Configuring the time zone................................................................................................ 62
Configuring the NTP server.............................................................................................. 62
Resetting the WebLM password through CLI..................................................................... 62
Performing WebLM backup.............................................................................................. 63
Performing WebLM restore.............................................................................................. 63
Creating a snapshot backup............................................................................................. 64
Creating a snapshot restore............................................................................................. 64
WebLM CLI operations.................................................................................................... 65
Viewing the job history of virtual machine operations.......................................................... 66
Monitoring a host and virtual machine............................................................................... 67
Chapter 10: Resources........................................................................................................... 69
Avaya WebLM documentation................................................................................................ 69
Finding documents on the Avaya Support website............................................................. 69
Accessing the port matrix document.................................................................................. 70
Avaya Documentation Portal navigation............................................................................ 70
Training................................................................................................................................ 71
Viewing Avaya Mentor videos................................................................................................. 71
Support................................................................................................................................ 72
Using the Avaya InSite Knowledge Base........................................................................... 72
Appendix A: Best practices for VM performance and features.......................................... 74
BIOS.................................................................................................................................... 74
Intel Virtualization Technology.......................................................................................... 74
Dell PowerEdge Server ................................................................................................... 75
HP ProLiant G8 and G9 Servers....................................................................................... 75
VMware Tools....................................................................................................................... 76
Timekeeping......................................................................................................................... 76
VMware networking best practices.......................................................................................... 77
Storage................................................................................................................................ 80
Thin vs. thick deployments..................................................................................................... 80
VMware Snapshots............................................................................................................... 81
VMware vMotion................................................................................................................... 82
VMware cloning.................................................................................................................... 83
VMware high availability......................................................................................................... 83
Appendix B: PCN and PSN notifications.............................................................................. 84
PCN and PSN notifications..................................................................................................... 84
Viewing PCNs and PSNs....................................................................................................... 84

Contents
Signing up for PCNs and PSNs.............................................................................................. 85

Glossary................................................................................................................................... 86

Chapter 1: Introduction
Purpose
This document provides procedures for deploying the Avaya WebLM virtual application on
VMware customer-provided Virtualized Environment and Kernel-based Virtual Machine(KVM). The
document includes installation, configuration, installation verification, troubleshooting, and basic
maintenance checklists and procedures.
The primary audience for this document is anyone who is involved with installing, configuring, and
verifying WebLM at a customer site. The audience includes and is not limited to implementation
engineers, field technicians, business partners, solution providers, and customers.
This document does not include optional or customized aspects of a configuration.
Prerequisites
Before deploying the Avaya WebLM OVA, ensure that you have the following knowledge, skills
and tools.
Knowledge
• For KVM: KVM hypervisor installation and set up
• For VMware: VMware® vSphere™ virtualized environment
• Linux® Operating System
• WebLM
Skills
To administer:
• VMware® vSphere™ virtualized environment
• KVM hypervisor
Tools
For information about tools and utilities, see “Configuration tools and utilities”.

Introduction
Change history
The following changes have been made to this document since the last issue:
Issue Date Summary of changes
2 October 2019 For Release 8.1.1, updated the following sections:
• Software details of WebLM on page 14
• Supported footprints for WebLM Server on page 14
• Verifying the WebLM software version on page 53
1 June 2019 Release 8.1 document.

Chapter 2: Virtualized Environment
overview
You can deploy the Avaya Aura® applications in one of the following Virtualized Environment:
• VMware in customer-provided Virtualized Environment
• Kernel-based Virtual Machine Virtualized Environment
Avaya Aura® Virtualized Environment overview

Avaya Aura® Virtualized Environment integrates real-time Avaya Aura® applications with VMware®
and Kernel-based Virtual Machine (KVM).
Kernel-based Virtual Machine overview

Kernel-based Virtual Machine (KVM) is a virtualization infrastructure for the Linux kernel that turns
the Linux kernel into a hypervisor. You can remotely access the hypervisor to deploy applications
on the KVM host.
KVM virtualization solution is:
• Cost effective for the customers.
• Performance reliable and highly scalable.
• Secure as it uses the advanced security features of SELinux.
• Open source software that can be customized as per the changing business requirements of
the customers.

Virtualized Environment overview
Supported applications in Virtualized Environment

Application Release VMware KVM
®
Avaya Aura System Manager Release 8.1.1 Y Y
Avaya WebLM Release 8.1.1 Y Y
®
Avaya Aura Session Manager Release 8.1.1 Y Y
®
Avaya Aura Communication Manager Release 8.1.1 Y Y
Avaya Aura® AVP Utilities Release 8.1.1 — —
®
Avaya Aura Application Enablement Services Release 8.1.1 Y Y
®
Avaya Aura Media Server (Software only) Release 8.0 Y Y
For information about other Avaya product compatibility information, go to https://

support.avaya.com/CompatibilityMatrix/Index.aspx.
Virtualized Environment components

Virtualized component Description
Open Virtualization Appliance The virtualized OS and application packaged in a single file that is used
(OVA) to deploy a virtual machine.
VMware
ESXi Host The physical machine running the ESXi Hypervisor software.
ESXi Hypervisor A platform that runs multiple operating systems on a host computer at
the same time.
vSphere Web Client Using a Web browser, vSphere Web Client connects to a vCenter
server or directly to an ESXi host if a vCenter Server is not used.
vSphere Client (HTML5) vSphere Client (HTML5) is available in vSphere 6.5. Using a Web
browser, it connects to a vCenter server or directly to an ESXi host if a
vCenter Server is not used. This is the only vSphere client
administration tool after the next vSphere release.
vCenter Server 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.
KVM
KVM hypervisor A platform that runs multiple operating systems on a host computer at
the same time.

Chapter 3: Planning and configuration
Hardware support
Supported hardware for VMware

VMware offers compatibility guides that list servers, system, I/O, storage, and backup compatibility
with VMware infrastructure. For more information about VMware-certified compatibility guides and
product interoperability matrices, see http://www.vmware.com/resources/guides.html.
Supported hardware for KVM

To deploy the Avaya Aura® application KVM OVA on a customer-provided server, the server must
be on the Red Hat supported server list for Red Hat Enterprise Linux 7.6.
Configuration tools and utilities

You must have the following tools and utilities for deploying and configuring standalone Avaya
WebLM open virtual application (OVA) on customer-provided Virtualized Environment on VMware
and KVM:
• For VMware: A remote computer running the VMware vSphere Client
• For KVM: A remote computer running the KVM host
• A browser for accessing the Avaya WebLM web interface
• An SFTP client for Windows, for example WinSCP
• An SSH client, for example, PuTTY and PuTTYgen

Planning and configuration
Supported tools for deploying the KVM OVA

You need one of the following tool to deploy KVM OVA.
• Virt Manager GUI
• virsh command line interface
Supported footprints for WebLM Server

These footprints are common for Appliance Virtualization Platform, VMware, and KVM.
Resource Profile 1 Profile 2
vCPU 1 1
CPU reservation • Appliance Virtualization Platform • Appliance Virtualization Platform
and VMware: 2185 MHz and VMware: 2185 MHz
• KVM: 2185 MHz • KVM: 2185 MHz
Memory reservation 1GB 2GB
Storage reservation 40GB 40GB
Shared NICs 1 1
Note:
If you use the WebLM server to acquire licenses for more than 5000 clients, use Profile 2.
Software details of WebLM

For Avaya Aura® application software build details of OVA, ISO, service patch, Data migration
Utility, or Solution Deployment Manager Client, see Avaya Aura® Release Notes on the
AvayaSupport website at http://support.avaya.com/
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 email notification to you. The email 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.

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

Use the following checklist to know the set up required to deploy the KVM OVA.

Planning and configuration
No. Task Description
1 Install the KVM hypervisor.

2 Install the MobaXterm and To remotely access the KVM hypervisor,
Xming softwares on your the Virt Manager GUI, and virsh
laptop/computer. command line interface.
Customer configuration data for WebLM

The following table identifies the key customer configuration information that you must provide
throughout the deployment and configuration process.
Required data Description Example value for the system
IP address The IP address of the For IPv4: 192.168.x.x

WebLM interface.
For IPv6: 2001:0db8::a
Netmask The network address mask. 255.255.0.0
Default Gateway The default network traffic For IPv4: 172.16.x.x
gateway.
For IPv6: 2001:0db8::1
DNS IP Address The IP address of the For IPv4: 172.16.x.x
primary DNS server.
For IPv6: 2001:0db8::5
Domain Name The domain name which abc.mydomain.com
must be a fully qualified
domain name.
Short HostName - weblm
Default Search List The domain name string that abc.mydomain.com
is used for default search.
NTP Server The IP address of the NTP For IPv4: 172.16.x.x
server.
For IPv6: 2001:0db8::b
Time Zone The time zone you want to America/Denver
choose.
CLI User details The command line interface abcd
user details.
Admin UI The admin UI password.
password
EASG Enhanced Access Security
Gateway
Customer root The customer root account
account details details.

Deployment guidelines
Deployment guidelines
• Deploy maximum number of virtualized environment on the same host.
• Deploy the virtualized environment 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.
• 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 virtualized environment performance.
SAL Gateway
You require a Secure Access Link (SAL) Gateway 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.
For more information about SAL Gateway and its deployment, see the Secure Access Link
documentation on the Avaya Support website at http://support.avaya.com.

Chapter 4: Deploying WebLM on VMware
Checklist for deploying WebLM on VMware®

Note:
Deployment of the WebLM OVA using vSphere Web Client by accessing the ESXi host 6.7
directly might fail. Therefore, to deploy the WebLM OVA, use vCenter 6.7 (flex) or Solution
Deployment Manager Client.
No. Task Links/Notes
1. Download the WebLM OVA file from the Avaya Downloading software from
Product Licensing and Delivery System (PLDS) PLDS on page 14
website at https://plds.avaya.com/
2. Install the vSphere client 6.0, 6.5, or 6.7.
3. Keep a copy of license files of Avaya Aura®
products handy so you can replicate with the new
Host ID after the OVA file installation.
4. Keep the network configuration data handy. Customer configuration data on
page 16
5. Deploy the WebLM OVA file. Deploying the WebLM OVA by
using vSphere Web Client on
page 19
6. Start the WebLM virtual machine. Starting the WebLM server virtual
machine on page 23
7. Verify the installation of the WebLM virtual
machine.
8. Install the WebLM 8.1.1 feature pack file. Installing a WebLM patch, feature
pack, or service pack on page 23
9. Restart the WebLM virtual machine from CLI to
get the updated kernel running in memory.

Deploying the WebLM OVA by using vSphere Web Client
Deploying the WebLM OVA by using vSphere Web Client

Before you begin
• Access vCenter Server by using vSphere Web Client.
• Download the Client Integration Plug-in.
Procedure
1. On the web browser, type the following URL: https://<vCenter FQDN or IP
Address>/vsphere-client/.
2. To log in to vCenter Server, do the following:
a. In User name, type the user name of vCenter Server.
b. In Password, type the password of vCenter Server.
3. Right-click the ESXi host and select Deploy OVF Template.
The system displays the Deploy OVF Template dialog box.
4. On the Select template page, perform one of the following steps:
• To download the WebLM OVA from a web location, select URL, and provide the
complete path of the OVA file.
• To access the WebLM OVA from the local computer, select Locate file, click Browse,
and navigate to the OVA file.
5. Click Next.
6. On the Select name and location page, do the following:
a. In Name, type a name for the virtual machine.
b. In Browse, select a datacenter.
7. Click Next.
8. On the Select a resource page, select a host, and click Next.
9. On the Review details page, verify the OVA details, and click Next.
10. To accept the End User License Agreement, on the Accept license agreements page, click
Accept.
11. Click Next.
12. On the Select configuration page, from Configuration, select the WebLM profile.
13. Click Next.
14. On the Select storage page, in Select virtual disk format, click the required disk format.
15. Click Next.
16. On the Select networks page, select the destination network for each source network.
17. Click Next.

Deploying WebLM on VMware
18. On the Customize template page, enter the configuration and network parameters.
For information about the configuration and network parameters, see Configuring the
network parameters fields and descriptions on page 47.
Note:
• If you do not provide the details in the mandatory fields, you cannot power on the
virtual machine even if the deployment is successful.
• During the startup, the system validates the inputs that you provide. If the inputs are
invalid, the system prompts you to provide the inputs again on the console of the
virtual machine.
19. Click Next.
20. On the Ready to complete page, review the settings, and click Finish.
Wait until the system deploys the OVA file successfully.
21. To start the WebLM virtual machine, if WebLM is not already powered on perform one of
the following steps:
• Click VM radio button, and click Actions > Power > Power On.
• Right-click the virtual machine, and click Power > Power On.
• On the Inventory menu, click VirtualMachine > Power > Power On.
The system starts the WebLM virtual machine.
When the system starts for the first time, configure the parameters for WebLM. For
instructions, see Configuring the network parameters fields and descriptions on page 47.
22. Click the Console tab and verify that the system startup is successful.
Next steps
Note:
Modifying the network or management configuration is not recommended before the patch
deployment.
Related links
Deploying the application OVA using vSphere Web Client by accessing the host directly on
page 21
Application Deployment field descriptions on page 47

Deploying the application OVA using vSphere Web Client by accessing the host directly
Deploying the application OVA using vSphere Web Client

by accessing the host directly
About this task
Use this procedure for deploying application OVA on ACP 130 and equivalent server. This same
procedure is applicable for ESXi 6.5 u2 onwards.
Before you begin
• Access vCenter Server by using vSphere Web Client.
• Download the Client Integration Plug-in.
Procedure
1. On the Web browser, type the host URL: https://<Host FQDN or IP Address>/ui.
2. Enter login and password.
3. Right-click an ESXi host and select Create/Register VM.
The system displays the New virtual machine dialog box.
4. On the Select creation type page, select Deploy a virtual machine from an OVF or OVA
file.
5. Click Next.
6. On the Select OVF and VMDK file page, do the following:
a. Type a name for the virtual machine.
b. Click to select files or drag and drop the OVA file from your local computer.
7. Click Next.
8. On the Select storage page, select a datastore, and click Next.
9. To accept the End User License Agreement, on the License agreements page, click I
Agree.
10. Click Next.
11. On the Deployment options page, perform the following:
a. From Network mappings, select the required network.
b. From Disk provisioning, select Thick provision lazy zeroed.
c. From Deployment type, select profile.
For more information about supported footprints, see “Supported footprints of
Communication Manager on VMware”.
d. Uncheck Power on automatically.
12. Click Next.
13. On the Additional settings page, click Next.

14. On the Ready to complete page, review the settings, and click Finish.
Wait until the system deploys the OVA file successfully.
15. To edit the virtual machine settings, click VM radio option and perform the following:
• Click Actions > Edit Settings to edit the required parameters.
• Click Save.
Note:
Ensure that the virtual machine is powered down to edit the settings.
16. To ensure that the virtual machine automatically starts after a hypervisor reboot, click VM
radio option, and click Actions > Autostart > Enable.
Note:
If you do not enable autostart, you must manually start the virtual machine after the
hypervisor reboot. Autostart must be enabled on the Host for the virtual machine
autostart to function.
17. To start the virtual machine, if application is not already powered on perform one of the
following steps:
• Click VM radio option, and click Actions > Power > Power On.
• Right-click the virtual machine, and click Power > Power On.
• On the Inventory menu, click Virtual Machine > Power > Power On.
The system starts the application virtual machine.
When the system starts for the first time, configure the parameters for application.
18. Click Actions > Console, select the open console type, verify that the system startup is
successful, then input the application configuration parameters.
Related links
Deploying the WebLM OVA by using vSphere Web Client on page 19
Application Deployment field descriptions on page 47
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.

Installing a WebLM patch, feature pack, or service pack
Installing a WebLM patch, feature pack, or service pack

Before you begin
• Create backup of WebLM.
• Copy the patch file, feature pack file, or the service pack file to the WebLM server.
• Verify the installed WebLM version.
Procedure
1. Log in to the WebLM command line interface with administrator privilege CLI user
credentials.
2. Verify the MD5 checksum of the patch file that you want to install.
3. Type WebLMPatchdeploy <absolute path to the WebLM feature pack
file>.
For example, WebLMPatchdeploy /home/avaya/VEWebLM_8.1.x.0_xxx.bin.
The system installs the patch file.
4. To accept the license terms, read the End User License Agreement carefully, and type Y.
The patch installation takes about 10–15 minutes to complete. You can view to monitor the
WebLM patch progress status from the /var/log/Avaya/WebLM_Patch.log file.
If the installation is successful, the system displays a warning message on the dashboard
and on the command line interface to restart WebLM if kernel is updated.
5. After patch installation is successful, relogin to CLI to check if the updated kernel is
running.
6. Restart the standalone WebLM.
Next steps
If the patch or service pack installation fails, perform a snapshot restore to go to the previous
version of WebLM.
Note:
Modifying the network or management configuration is not recommended before the patch
deployment.
Starting the WebLM server virtual machine

Procedure
1. From the list of virtual machines for the target host, select the WebLM server machine that
you have deployed.
2. Click Power On.

3. If you have deployed WebLM through vSphere, at the system prompt, enter the network
parameters.
4. Confirm the network parameters. Press n to reenter the values.
The WebLM boot-up sequence continues and WebLM configuration starts.
5. Right-click the deployed WebLM server virtual machine, and select Open Console.
The WebLM server virtual machine starts.
Note:
You must re-host all the required licenses after upgrading WebLM. For a fresh
installation, you need not re-host the licenses.

Chapter 5: Deploying WebLM on Kernel-
based Virtual Machine
Extracting KVM OVA

Procedure
1. Create a folder on the KVM host and copy the application KVM OVA in the created folder.
2. Type the command tar -xvf <application_KVM.ova>.
The system extracts the files from the application KVM OVA.
Deploying KVM OVA by using Virt Manager

Before you begin
• Create a folder on the KVM host and copy the KVM OVA in the created folder.
• Access the KVM host remotely.
• Extract the KVM OVA files.
Procedure
1. On the terminal, run the command: virt-manager.
2. On the Virtual Machine Manager window, click File > New Virtual Machine, and select
Import existing disk image.
3. On the Create a new virtual machine Step 1 of 4 window, select Import existing disk
image.
4. Click Forward.
5. On the Create a new virtual machine Step 2 of 4 window, perform the following:
a. In Provide the existing storage path, click Browse, and select the qcow2 image of
application on the KVM host.
b. In OS type, select Linux.
c. In Version, select Red Hat Linux Enterprise 7.6.
d. Click Forward.

Deploying WebLM on Kernel-based Virtual Machine
a. In Memory (RAM), enter the required memory.
b. In CPU, enter the number of CPUs for the virtual machine based on the application
profile.
c. Click Forward.
a. In Name, type the name of the virtual machine.
b. Select the Customize Configuration before Install check box.
c. Check Network selection and verify the required network interface.
d. Click Finish.
8. In the left navigation pane, click Disk 1. In the Advanced options section, perform the
following:
a. In Disk bus, select SCSI.
b. In Storage format, type qcow2.
c. Click Apply.
9. In the left navigation pane, click Boot Options and perform the following:
a. In Boot device order, click Hard Disk.
b. Click Apply.
10. Click Begin Installation.
The system creates a new virtual machine.
Next steps
On first boot of the virtual machine, provide the configuration and networking parameters.
Deploying WebLM KVM OVA from CLI by using virsh

Before you begin
• Create a folder on the KVM host and copy the KVM OVA in the created folder.
• Access the KVM host remotely.
• Extract the KVM OVA files.
Procedure
On the KVM host CLI, perform the following:
a. Navigate to the WebLM KVM OVA directory.

Deploying application by using OpenStack
b. Run the WebLM installation utility, type the command: sh WEBLM-installer.sh

WebLM-7.1.0.0.11-27074-kvm-10.ovf.
c. When the system prompts, select the required WebLM profile.
d. In VM name, type a name of the virtual machine.
e. In Drive storage location, type storage location of the virtual machine.
f. In Network, select the network.
The system displays the command to deploy the image.
g. To continue, type Y.
The system displays the message: Deploying image.
Next steps
On the KVM host, run the command: virt-manager. On first boot of the virtual machine, provide
the WebLM configuration and networking parameters.
Connecting to OpenStack Dashboard

Before you begin
• Create an OpenStack account.
• Acquire adequate permission to upload and deploy the KVM ova.
Procedure
1. In your web browser, type the OpenStack URL.
For example, http://<openstack.xyz.com>/horizon.
2. In Domain, type the domain name.
3. In User Name, type the user name.
4. Click Connect.
The system displays the Instance Overview - OpenStack Dashboard page.
Uploading the qcow2 image

Procedure
1. Connect to OpenStack Dashboard.

2. In the left navigation pane, click Project > Compute > Images.
3. On the Images page, click Create Image.
The system displays the Create An Image dialog box.
4. In Name, type the name of the image.
5. In Description, type the description of the image.
6. In Image Source, click Image Location or Image File, and perform one of the following:
• In Image Location, type the exact URL of the qcow2 image.
• In Image File, click Browse. In the Choose File to Upload dialog box, select the qcow2
image from your local system, and click Open.
7. In Format, click QCOW2 - QEMU Emulator.
8. Click Create Image.
The system displays the created image on the Images page.
Flavors
Flavors are footprints of an application. The administrator must create flavors for each application.
For information about the footprints, see the profiles and footprints information for the application.
Creating a security group

About this task
Security groups are sets of IP filter rules. Each user must create security groups to specify the
network settings for the application.
Procedure
2. In the left navigation pane, click Project > Compute > Access & Security.
3. On the Access & Security page, click Create Security Group.
The system displays the Create Security Group dialog box.
4. In Name, type the name of the security group.
5. In Description, type the description of the security group.
6. Click Create Security Group.
The system displays the created security group on the Access & Security page.
Next steps
Add rules to security group.

Adding rules to a security group

Before you begin
Create a security group.
Procedure
1. On the Access & Security page, click Manage Rules that is corresponding to the created
security group.
2. On the Access & Security / Manage Security Group Rules page, click Add Rule.
The system displays the Add Rule dialog box.
3. In Rule, click a rule
The system displays the fields that are associated with the selected rule.
4. Enter the appropriate values in the fields.
5. Click Add.
The system displays the created rule on the Access & Security / Manage Security Group
Rules page.

Before you begin
• Create flavors.
• Create a security group.
Procedure
2. In the left navigation pane, click Project > Compute > Instances.
3. On the Instance page, click Launch Instance.
The system displays the Launch Instance dialog box.
4. In Details, perform the following:
a. In Instance Name, type a name of the instance.
b. In Availability zone, select the availability zone of the instance.
c. Click Next.
5. In Source, perform the following:
a. In the Available section, select a check box corresponding to an instance image.
The system displays the selected image in the Allocated section.

b. Click Next.
6. In Flavors, perform the following:
a. In the Available section, select a check box corresponding to a flavor name.
The system displays the selected flavor in the Allocated section.
b. Click Next.
7. In Networks, perform the following:
a. In the Available section, select a check box corresponding to a network name.
The system displays the selected network in the Allocated section.
b. Click Next.
8. In Network Ports, leave the default settings, and click Next.
9. In Security Groups, perform the following:
a. In the Available section, select a check box corresponding to a security group name.
The system displays the selected security group in the Allocated section.
b. Click Next.
10. In Key Pair, leave the default settings, and click Next.
11. In Configuration, leave the default settings, and click Next.
12. In Metadata, leave the default settings.
13. Click Launch Instance.
The system displays the created instance on the Instances page. The Status column
displays: Spawning. When the system creates the application instance, the Status
column displays: Active.
The system displays the static IP Address of the application in the IP Address column.
Next steps
Configure the application instance. Use the static IP Address to configure the application instance.
Configuring application instance

Procedure
1. On the Instances page, in the INSTANCE NAME column, click the application instance
name.
2. On the Instances / <Instance Name> page, click Console.
3. On the Instance Console page, go to console, and follow the prompt to configure the
application instance.

Deploying application by using Nutanix
Logging on to the Nutanix Web console

Procedure
1. To log on to the Nutanix Web console, in your web browser, type the PRISM URL.
For example, http://<PRISM_IPAddress>/.
2. In username, type the user name.
3. In password, type the password.
4. Press Enter.
The system displays the Home page.
Transferring the files by using the WinSCP utility

About this task
Use the following procedure to transfer the files from a remote system to a Nutanix container by
using the WinSCP utility.
Procedure
1. Use WinSCP or a similar file transfer utility to connect to the Nutanix container.
2. In File protocol, click SCP.
3. Enter the credentials to gain access to SCP.
4. Click Login.
5. Click OK or Continue as necessary in the warning dialog boxes.
6. In the WinSCP destination machine pane, browse to /home/<Container_Name> as the
destination location for the file transfer.
7. Click and drag the qcow2 image from the WinSCP source window to /home/
<Container_Name> in the WinSCP destination window.
8. Click the WinSCP Copy button to transfer the file.
9. When the copy completes, close the WinSCP window (x icon) and click OK.
Uploading the qcow2 image

Procedure
1. Log on to the Nutanix Web console.

2.
Click Settings icon ( ) > Image Configuration.
The system displays the Image Configuration dialog box.
3. Click + Upload Image.
The system displays the Create Image dialog box.
4. In NAME, type the name of the image.
5. In ANNOTATION, type the description of the image.
6. In IMAGE TYPE, click DISK.
7. In STORAGE CONTAINER, click the storage container of the image.
8. In IMAGE SOURCE, perform one of the following:
• Select From URL, type the exact URL of the qcow2 image. For example: nfs://
<127.0.0.1>/<Storage Container Name>/<Image Name>
• Select Upload a file, click Browse. In the Choose File to Upload dialog box, select the
qcow2 image from your local system, and click Open.
9. Click Save.
The system displays the created image on Image Configuration.
Creating the virtual machine by using Nutanix

Before you begin
• Upload the qcow2 image.
• Configure the network.
Procedure
1. Log on to the Nutanix Web console.
2. Click Home > VM.
3. Click + Create VM.
The system displays the Create VM dialog box.
4. In the General Configuration section, perform the following:
a. In NAME, type the name of the virtual machine.
b. In DESCRIPTION, type the description of the virtual machine.
5. In the Compute Details section, perform the following:
a. In VCPU(S), type the number of virtual CPUs required for the virtual machine.
b. In NUMBER OF CORES PER VCPU, type the number of core virtual CPUs required
for the virtual machine.

c. In Memory, type the memory required for the virtual machine.

The value must be in GiB.
You must select the CPU and Memory according to the application footprint profile.
6. In the Disk section, perform the following:
a. Click + Add New Disk.
The system displays the Add Disk dialog box.
b. In TYPE, click DISK.
c. In OPERATION, click Clone from Image Service.
d. In IMAGE, click the application image.
e. In BUS TYPE, click IDE.
f. Click Add.
The system displays the added disk in the Disk section.
7. In the Disk section, select a boot device.
8. In the Network Adopters (NIC) section, perform the following:
a. Click Add New NIC.
The system displays the Create NIC dialog box.
b. In VLAN NAME, click the appropriate NIC.
The system displays VLAN ID, VLAN UUID, and NETWORK ADDRESS / PREFIX for
the selected NIC.
c. Click Add.
The system displays the added NIC in the Network Adopters (NIC) section.
You must select the number of NIC according to the application footprint profile.
If you are configuring Out of Band Management, select one more NIC.
9. In the VM Host Affinity section, perform the following:
a. Click Set Affinity.
The system displays the Set VM Host Affinity dialog box.
b. Select one or more host to deploy the virtual machine.
c. Click Save.
The system displays the added hosts in the VM Host Affinity section.
10. Click Save.
The system displays the message: Received operation to create VM <name of
the VM>.

After the operation is successful, the system displays the created virtual machine on the
VM page.
Next steps
Start the virtual machine.
Starting a virtual machine

Before you begin
Create the virtual machine.
Procedure
1. Click Home > VM.
2. On the VM page, click Table.
3. Select the virtual machine.
4. At the bottom of the table, click Power On.
The system starts the virtual machine.
Next steps
Launch the console. On the first boot of the virtual machine, provide the configuration and
networking parameters.
Configuring the virtual machine

Procedure
1. Click Home > VM.
2. On the VM page, click Table.
3. Select the virtual machine.
4. At the bottom of the table, click Launch Console.
5. Follow the prompt to configure the virtual machine.

Deploying application by using Red Hat Virtualization Manager
Deploying application by using Red Hat Virtualization

Manager
Logging on to the Red Hat Virtualization Manager Web console

Procedure
1. In your web browser, type the Red Hat Virtualization Manager URL.
For example, https://<RedHatVirtualizationManager_IPAddress>/ovirt-engine/.
2. To log in, click Not Logged In > Login.
The system displays the Red Hat Virtualization Manager Log In page.
3. In Username, type the user name.
4. In Password, type the password.
5. In Profile, click the appropriate profile.
6. Click Log In.
The system displays the Red Hat Virtualization Manager Web Administration page.
Uploading the disk

Before you begin
You must import the ovirt-engine certificate into your browser by accessing the http://
<engine_url>/ovirt-engine/services/pki-resource?resource=ca-
certificate&format=X509-PEM-CA link to get the certificate. Establish the trust for the new
Certificate Authority (CA) with the website.
Procedure
1. Log on to the Red Hat Virtualization Manager Web console.
2. In the left navigation pane, click System.
3. On the Disks tab, click Upload > Start.
The system displays the Upload Image dialog box.
4. Click Browse.
5. In the Choose File to Upload dialog box, select the qcow2 disk image from your local
system, and click Open.
6. In Size(GB), type the size of the disk.
7. In Alias, type the name of the disk.

8. In Description, type the description of the disk.

9. In Data Center, click the data center to store the disk.
10. In Storage Domain, click the storage domain of the disk.
11. In Disk Profile, click disk profile.
12. In Use Host, click the host of the disk.
13. Click OK.
The system displays the uploaded image on the Disks tab. Once the disk image is
successfully uploaded, the Status column displays OK.
Creating the virtual machine by using Red Hat Virtualization

Manager
Before you begin
• Upload the qcow2 disk image.
• Create an instance type.
• Configure the network.
Procedure
1. Log on to the Red Hat Virtualization Manager Web console.
2. In the left navigation pane, click System.
3. On the Virtual Machines tab, click New VM.
The system displays the New Virtual Machine dialog box.
4. In Operating System, click Linux.
5. In Instance Type, click an instance type.
You must select the instance type according to the application footprint profile.
6. In Optimized for, click Server.
7. In Name, type the name of the virtual machine.
8. In Description, type the description of the virtual machine.
9. In the Instance Images section, perform the following:
a. Click Attach.
The system displays the Attach Virtual Disks dialog box.
b. In Interface, click IDE.
c. Click OK.
The system displays the added disk in the Instance Images section.

Deploying application by using Red Hat Virtualization Manager
10. In nic1, click a vNIC profile.

If you are configuring Out of Band Management, select one more NIC.
11. Click OK.
After the operation is successful, the system displays the created virtual machine on the
Virtual Machines tab.
Next steps
Start the virtual machine.
Starting a virtual machine

Before you begin
Create the virtual machine.
Procedure
Right-click the virtual machine and click Run.
When the system starts the virtual machine, the system displays a green upward arrow key ( )
corresponding to the virtual machine name.
Next steps
Launch the console. On the first boot of the virtual machine, provide the configuration and
networking parameters
Configuring the virtual machine

Before you begin
• Start the virtual machine.
• Install the virt-viewer installer to access console.
Procedure
1. Right-click the virtual machine and click Console.
2. Follow the prompt to configure the virtual machine.

Chapter 6: Managing the ESXi host by
using SDM
Adding a location
About this task
You can define the physical location of the host and configure the location specific information.
You can update the information later.
Procedure
1. On the Locations tab, in the Locations section, click New.
2. In the New Location section, perform the following:
a. In the Required Location Information section, type the location information.
b. In the Optional Location Information section, type the network parameters for the
virtual machine.
3. Click Save.
The system displays the new location in the Application Management Tree section.
Adding an Appliance Virtualization Platform or ESXi host

About this task
Use the procedure to add an Appliance Virtualization Platform or ESXi host. You can associate an
ESXi host with an existing location.
If you are adding a standalone ESXi host to System Manager Solution Deployment Manager or to
the Solution Deployment Manager client, add the standalone ESXi host using its FQDN only.
Solution Deployment Manager only supports the Avaya Aura® Appliance Virtualization Platform
and VMware ESXi hosts. If you try to add another host , the system displays the following error
message:
Retrieving host certificate info is failed: Unable to communicate with
host. Connection timed out: connect. Solution Deployment Manager only
supports host management of VMware-based hosts and Avaya Appliance
Virtualization Platform (AVP).

Adding a software-only platform
Before you begin

Add a location.
Procedure
1. Click Application Management.
2. In Application Management Tree, select a location.
3. On the Platforms tab, in the Platforms for Selected Location <location name> section,
click Add.
4. In the New Platform section, do the following:
a. Provide details of Platform name, Platform FQDN or IP address, user name, and
password.
For Appliance Virtualization Platform and VMware ESXi deployment, you can also
provide the root user name.
b. In Platform Type, select AVP/ESXi.
c. If you are connected through the services port, set the Platform IP address of
Appliance Virtualization Platform to 192.168.13.6.
5. Click Save.
6. In the Certificate dialog box, click Accept Certificate.
The system generates the certificate and adds the Appliance Virtualization Platform host.
For the ESXi host, you can only accept the certificate. If the certificate is invalid, Solution
Deployment Manager displays the error. To generate certificate, see VMware
documentation.
In the Application Management Tree section, the system displays the new host in the
specified location. The system also discovers applications.
Next steps
1. In Application Management Tree, establish trust for all the virtual machines that are
deployed on the host.
2. Ensure that the system populates the Application Name and Application Version for
each virtual machine.
Adding a software-only platform

About this task
Use this procedure to add an operating system on Solution Deployment Manager. In Release
8.1.1, the system supports the Red Hat Enterprise Linux Release 7.6 64-bit operating system.
Before you begin
Add a location.

Managing the ESXi host by using SDM
Procedure
1. On the Platforms tab, click Add.
2. In Platform Name, type the name of the platform.
3. In Platform FQDN or IP, type the FQDN or IP address of the base operating system.
4. In User Name, type the user name of the base operating system.
For a software-only deployment, the user name must be a direct access admin user. If the
software-only application is already deployed, provide the application cli user credentials.
5. In Password, type the password of the base operating system.
6. In Platform Type, select OS.
7. Click Save.
If the platform has some applications running, the system automatically discovers those
applications and displays the applications in the Applications tab.
• If Solution Deployment Manager is unable to establish trust, the system displays the
application as Unknown.
• If you are adding OS, only Add and Remove operations are available on the Platforms
tab. You cannot perform any other operations. On the Applications tab, the system
enables the New option. If the application is System Manager, the system enables
Update App on Solution Deployment Manager Client
The system displays the added base operating system on the Platforms tab.
Managing vCenter
Creating a role for a user

About this task
To manage a vCenter or ESXi in Solution Deployment Manager, you must provide complete
administrative-level privileges to the user.
Use the following procedure to create a role with administrative-level privileges for the user.
Procedure
1. Log in to vCenter Server.
2. On the Home page, click Administration > Roles.
The system displays the Create Role dialog box.
3. In Role name, type a role name for the user.

Managing vCenter
4. To provide complete administrative-level privileges, select the All Privileges check box.
5. (Optional) To provide minimum mandatory privileges, do the following.
a. In All Privileges, select the following check boxes:
• Datastore
• Datastore cluster
• Distributed switch
• Folder
• Host profile
• Network
• Resource
• Tasks
• Virtual machine
• vApp
Note:
You must select all the subprivileges under the list of main set of privileges. For
example, when you select the Distributed switch check box, ensure that you
select all the related subprivileges. This is applicable for all the main privileges
mentioned above. If you do not select all the subprivileges, the system might not
work properly.
b. In All Privileges, expand Host, and select the Configuration check box.
Note:
You must select all the subprivileges under Configuration.
6. Click OK to save the privileges.
Next steps
Assign this role to the user for mapping vCenter in Solution Deployment Manager. To assign the
role to the user, see the VMware documentation.
Adding a vCenter to Solution Deployment Manager

About this task
System Manager Solution Deployment Manager supports virtual machine management in vCenter
6.0, 6.5, and 6.7. When you add vCenter, System Manager discovers the ESXi hosts that this
vCenter manages, adds to the repository, and displays in the Managed Hosts section. Also,
System Manager discovers virtual machines running on the ESXi host and adds to the repository.
System Manager displays vCenter, ESXi host, and virtual machines on the Manage Elements
page.

Before you begin

Ensure that you have the required permissions.
Procedure
1. In the lower pane, click Map vCenter.
2. On the Map vCenter page, click Add.
3. In the New vCenter section, provide the following vCenter information:
a. In vCenter FQDN, type FQDN of vCenter.
• For increased security when using a vCenter with Solution Deployment Manager,
use an FQDN for the vCenter. vCenter does not put IP addresses in its certificates.
Therefore, you need FQDN to confirm the server identity through the certificate in
Solution Deployment Manager.
• The FQDN value must match with the value of the SAN field of the vCenter
certificate. The FQDN value is case sensitive.
b. In User Name, type the user name to log in to vCenter.
c. In Password, type the password to log in to vCenter.
d. In Authentication Type, select SSO or LOCAL as the authentication type.
If you select the authentication type as SSO, the system displays the Is SSO
managed by Platform Service Controller (PSC) field.
e. (Optional) If PSC is configured to facilitate the SSO service, select Is SSO managed
by Platform Service Controller (PSC).
PSC must have a valid certificate.
The system enables PSC IP or FQDN and you must provide the IP or FQDN of PSC.
f. (Optional) In PSC IP or FQDN, type the IP or FQDN of PSC.
4. Click Save.
5. On the certificate dialog box, click Accept Certificate.
The system generates the certificate and adds vCenter.
In the Managed Hosts section, the system displays the ESXi hosts that this vCenter
manages.
Related links
Editing vCenter on page 43
Map vCenter field descriptions on page 43
New vCenter and Edit vCenter field descriptions on page 44

Managing vCenter
Editing vCenter
Before you begin
Procedure
2. On the Map vCenter page, select a vCenter server and click Edit.
3. In the Edit vCenter section, change the vCenter information as appropriate.
4. If vCenter is migrated from an earlier release, on the Certificate page, click Save, and then
click Accept Certificate.
5. To edit the location of ESXi hosts, in the Managed Hosts section, do one of the following:
• Select an ESXi host and click the edit icon ( ).
• Select one or more ESXi hosts, select the location, click Bulk Update > Update.
6. Click Commit to get an updated list of managed and unmanaged hosts.
If you do not click Commit after you move the host from Managed Hosts to Unmanaged
Hosts or vice versa, and you refresh the table, the page displays the same host in both the
tables.
Deleting vCenter from Solution Deployment Manager

Before you begin
Procedure
2. On the Map vCenter page, select one or more vCenter servers and click Delete.
3. Click Yes to confirm the deletion of servers.
The system deletes the vCenter from the inventory.
Map vCenter field descriptions

Name Description
Name The name of the vCenter server.
Table continues…

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

Name Description
vCenter FQDN FQDN of vCenter.
User Name The user name to log in to vCenter.
Table continues…

Managing vCenter
Name Description
Password The password that you use to log in to vCenter.
Authentication Type The authentication type that defines how Solution
Deployment Manager performs user authentication.
The options are:
• SSO: Global username used to log in to vCenter
to authenticate to an external Active Directory
authentication server.
• LOCAL: User created in vCenter
If you select the authentication type as SSO, the
system displays the Is SSO managed by Platform
Service Controller (PSC) field.
Is SSO managed by Platform Service Controller The check box to specify if PSC manages SSO
(PSC) service. When you select the check box, the system
enables PSC IP or FQDN.
PSC IP or FQDN The IP or FQDN of PSC.
Button Description
Save Saves any changes you make to FQDN, username,
and authentication type of vCenter.
Refresh Refreshes the vCenter details.
Managed Hosts
Name Description
Host IP/FQDN The name of the ESXi host.
Host Name The IP address of the ESXi host.
Location The physical location of the ESXi host.
IPv6 The IPv6 address of the ESXi host.
Edit The option to edit the location and host.
Bulk Update Provides an option to change the location of more
than one ESXi hosts.
Note:
You must select a location before you click
Bulk Update.
Update Saves the changes that you make to the location or
hostname of the ESXi host.
Commit Commits the changes that you make to the ESXi
host with location that is managed by vCenter.

Unmanaged Hosts
Name Description
Host IP/FQDN The name of the ESXi host.
ESXi Version Displays the versions of the ESXi host linked to
vCenter FQDN.
Note:
For Release 8.1, do not select the 5.0 and 5.1
versions.
IPv6 The IPv6 address of the ESXi host.
Button Description
Commit Saves all changes that you made to vCenter on the
Map vCenter page.

Chapter 7: Configuration
Application Deployment field descriptions

Configuration Parameters
Note:
The master WebLM server and the local WebLM server must be in the same IP mode either
IPv4 or IPv6.
Name Description
IPv4 Address The IPv4 address of the WebLM virtual machine.
Netmask The IPv4 subnetwork mask to assign to the WebLM virtual machine.
IPv4 Default Gateway The gateway IPv4 address to assign to the WebLM virtual machine.
IP Address of DNS Server The DNS IPv4 address to assign to the WebLM virtual machine. Separate
the IP addresses with commas (,).
Short Hostname The short hostname to assign to the WebLM virtual machine.
IPv6 Address The IPv6 address of the WebLM virtual machine.
IPv6 Network Prefix The IPv6 subnetwork mask to assign to the WebLM virtual machine.
IPv6 Gateway The gateway IPv6 address to assign to the WebLM virtual machine.
Domain Name The domain name of the WebLM virtual machine.
Default Search List The short hostname to assign to the WebLM virtual machine.
NTP Server IP/FQDN The IP address or FQDN of the NTP server.
The field is optional. Separate the IP addresses with commas (,).
Timezone The timezone where the WebLM virtual machine is located. A list is
available where you select the name of the continent and the name of the
country.

Configuration
WebLM CLI USER

Name Description
WebLM command line user Specifies the WebLM command line user name.
name
Note:
Do not provide the common user names, such as, admin, csaadmin,
postgres, root, bin, daemon, adm, sync, dbus, vcsa, ntp, saslauth,
sshd, tcpdump, xfs, rpc, rpcuser, nfsnobody, craft, inads, init,
rasaccess, sroot, postgres, smgr, and nortel.
Do not use the user names, such as, admin and csadmin.
WebLM command line user Specifies the WebLM command line user password.
password
Confirm Password Re-type the WebLM command line user password.
WebLM UI Password for User - admin

Name Description
WebLM UI admin user Specifies the WebLM admin user password.
Password
Note:
Do not use the default password for admin.
Confirm Password Re-type the WebLM admin user password.
Enhanced Access Security Gateway (EASG) - EASG User Access

Name Description
Enter 1 to Enable EASG Enables or disables Avaya Logins for Avaya Services to perform the
(Recommended) or 2 to required maintenance tasks.
Disable EASG
The options are:
• 1: To enable EASG.
• 2: To disable EASG.
Avaya recommends to enable EASG.
You can also enable EASG after deploying or upgrading the application
by using the command: EASGManage --enableEASG.

Application Deployment field descriptions
Customer Root Account

Name Description
Enable Customer Root Enables or disables the customer root account for the application.
Account for this Application
Displays the ROOT ACCESS ACCEPTANCE STATEMENT screen. To
accept the root access, click Accept.
When you accept the root access statement, the system displays the
Customer Root Password and Re-enter Customer Root Password
fields.
Customer Root Password The root password for the application
Re-enter Customer Root The root password for the application
Password
Networking Parameters
When you deploy the application on Appliance Virtualization Platform, the system displays the
Automatically Mapped VM Network Interfaces section with the VM Interfaces, Mapped to Host
Network, and Server NIC columns.
Name Description
Public The port number that is mapped to public port group.
You must configure Public network configuration parameters only when
you configure Out of Band Management. Otherwise, Public network
configuration is optional.
Services The port number that is mapped to the services port group when AVP
Utilities is deployed in the solution.
AVP Utilities provides routing from the services port to the virtual
machines and additional functions, such as alarm conversion.
Out of Band Management The port number that is mapped to the out of band management port
group.
When you deploy the application on VMware, the system displays the Select a Network Mapping
for VM Network Interfaces section.
Name Description
Public The port number that is mapped to public port
group.
You must configure Public network configuration
parameter only.
Button Description
Deploy Displays the EULA acceptance screen. To accept EULA and start the
deployment process, click Accept.

Configuration
Updating the WebLM server memory

About this task
To handle more than five thousand license requests at a time, WebLM requires large memory.
Perform the following procedure to update the memory settings of WebLM on VMware.
Procedure
1. Log in to the VMware vSphere Web client, and shut down the WebLM virtual machine.
2. Select the WebLM virtual machine, and right-click.
If you cannot view the WebLM virtual machine, click Home > Inventory > Hosts and
Clusters
3. Click Edit Settings.
4. In the Edit Settings or Virtual Machine Properties dialog box, select the Hardware tab and
edit the Memory Size from 1 GB to 2 GB.
5. In the Resources tab, type 2048 in the text field.
6. Select MB from the drop-down list, and click OK.
7. In the left navigation pane, right-click the WebLM virtual machine.
8. In the context menu, click Power On.
Updating network parameters for cloned WebLM

About this task
If a WebLM virtual machine is cloned or exported to another host by using OVF tool, you cannot
change the IP address of the cloned WebLM virtual machine instance by using the
changeIPFQDN command immediately after cloning because the network interface is unavailable.
Use the following procedure to update network parameters for cloned WebLM.
Before you begin
Deploy WebLM OVA on ESXi.
Procedure
1. Log on to the WebLM web interface and CLI, and ensure that the login is successful.
2. Power off the WebLM that you deployed.
3. Clone WebLM by using the following:
a. Select the WebLM virtual machine.
b. Right-click and select Clone.
c. Ensure that the cloning is successful.

Updating network parameters for cloned WebLM
4. Power on the cloned WebLM virtual machine.

5. Perform the following to check the MAC address:
a. Right-click the cloned WebLM virtual machine.
b. Click Edit Settings > Network Adapter 1 > MAC Address, and note the MAC
address.
6. On the Console tab of VMware client, perform the following steps:
a. Type the MAC address that you noted in the earlier step in the /etc/sysconfig/
network-scripts/ifcfg-eth0.
b. Update the required network parameters.
7. Power off the WebLM virtual machine.
On the WebLM virtual machine, the eth0 turns on with the old IP address from the cloned
WebLM virtual machine.
8. Restart the network services by using /etc/init.d/network restart utility.
9. Log on to the WebLM web interface, and ensure that the system displays the host ID.

Chapter 8: Post-deployment and upgrade
verifications
Post-upgrade checklist
Sr. No. Tasks Links/Notes
1 Log on to the WebLM web console See Logging on to the WebLM web console on
and verify the WebLM page 52.
<version_number>.
2 Rehost the license file that you See Rehosting license files on page 53. For
generated on the WebLM server. more details, refer Administering Avaya
WebLM.
Note:
If you had upgraded the
application by using Solution
Deployment Manager client,
you do not need to rehost the
license file separately.
3 Configure the EASG settings, if See Enhanced Access Security Gateway
required. (EASG) overview on page 57.
4 Rollback the upgrade in case the See Rolling back an upgrade on page 57.
upgrade fails.
5 Delete the virtual machine -
snapshots, if required.
Logging on to the WebLM web console

About this task
The WebLM web console is the main interface of Avaya WebLM. You must log on to the WebLM
web console to perform any task. The WebLM home page displays the navigation menu that
provides access to shared services to perform operations that WebLM supports.

Rehosting license files
Before you begin

Get a user account to log on to the WebLM web console. To create a new account, go to the
Avaya Support website at https://support.avaya.com.
Procedure
1. On a web browser, type the WebLM URL: https://<Fully Qualified Domain
Name>>:52233/WebLM.
2. In the User Name field, type the user name.
3. In the Password field, type the password.
4. Click Log On.
WebLM validates the user name and password with the WebLM user account and displays
the home page with the WebLM <version_number>. If the match fails, WebLM displays an
error message and prompts you to reenter the user name and password.
Rehosting license files

Procedure
1. On the WebLM console, click Server Properties.
2. On the Server Properties page, note the WebLM server host ID.
3. Go to the PLDS website regenerate the license file for your product using the same host
ID.
4. Install the license file that you generated on the WebLM server.
For more information about installing a license file, see Administering Avaya WebLM.
Verifying the WebLM software version

About this task
To verify the WebLM version, perform the following procedure after you deploy or upgrade
WebLM.
• On the WebLM console, do the following:
1. Log on to the WebLM web console with administrator privilege credentials.
2. On the home page, click About.
The system displays the About WebLM window with the build details.
3. Verify the software version of WebLM.

Post-deployment and upgrade verifications
• On the WebLM command line interface, do the following:

credentials.
2. Type swversion.
************************************************
StandAlone WebLM Software Information
************************************************
Standalone WebLM 8.1.x Build Number 8.1.1.xxxx Patch 8.1.x Build
Number 8.1.x.x.xxxxx
Upgrade job status
Upgrade job status

The Upgrade Job Status page displays the status of completion of every upgrade job that you
performed. Every step that you perform to upgrade an application by using Solution Deployment
Manager is an upgrade job. You must complete the following jobs to complete the upgrade:
1. Refresh Element(s): To get the latest data like version data for the applications in the
system.
2. Analyze: To evaluate an application that completed the Refresh Element(s) job.
3. Pre-Upgrade Check: To evaluate an application that completed the Analyze job.
4. Upgrade: To upgrade applications that completed the Pre-upgrade Check job.
5. Commit: To view commit jobs.
6. Rollback: To view rollback jobs.
7. Uninstall: To view uninstall jobs.
Viewing the Upgrade job status

Procedure
1. On the System Manager web console, click Services > Solution Deployment Manager.
2. In the left navigation pane, click Upgrade Job Status.
3. On the Status of Upgrade Management Jobs page, in the Job Type field, click a job type.
4. Select one or more jobs.
5. Click View.
The system displays the Upgrade Job Status page.

Upgrade job status
Editing an upgrade job

Before you begin
You can edit the configuration of an upgrade job that is in pending state.
Procedure
2. In the navigation pane, click Upgrade Job Status.
3. On the Upgrade Job Status page, in the Job Type field, click Upgrade.
4. Select a pending upgrade job that you want to edit.
5. Click Edit Configuration.
The system displays the Upgrade Configuration page.
6. To edit the configuration, see Upgrading Avaya Aura applications.
Deleting the Upgrade jobs

Procedure
2. In the left navigation pane, click Upgrade Job Status.
3. On the Upgrade Job Status page, in the Job Type field, click a job type.
4. Select one or more jobs.
5. Click Delete.
The system updates the Upgrade Job Status page.

Upgrade Job Status field descriptions

Name Description
Job Type The upgrade job type. The options are:
• Refresh Element(s): To view refresh elements jobs.
• Analyze: To view analyze jobs.
• Pre-Upgrade Check: To view preupgrade check jobs.
• Upgrade: To view upgrade jobs.
• Commit: To view commit jobs.
• Rollback: To view rollback jobs.
• Uninstall: To view uninstall jobs.
Job Name The upgrade job name.
Start Time The time when the system started the job.
End Time The time when the system ended the job.
Status The status of the upgrade job. The status can be: SUCCESSFUL,
PENDING_EXECUTION, PARTIAL_FAILURE, FAILED.
% Complete The percentage of completion of the upgrade job.
Element Records The total number of elements in the upgrade job.
Successful Records The total number of times that the upgrade job ran successfully.
Failed Records The total number of times that the upgrade job failed.
Button Description
Delete Deletes the upgrade job.
Re-run Checks Performs the upgrade job again.
Edit Configuration Displays the Upgrade Configuration page where you can change the upgrade
configuration details.
Rollback process
Upgrade rollback
The upgrade rollback is initiated in two cases:
• Upgrade process of an element fails: Administrator need not rollback upgrade of all the
elements. When the element upgrade fails, the system stops the entire upgrade process and

Enhanced Access Security Gateway overview
displays the failure status on the Upgrade Management page. The entire upgrade process
does not roll back. Only the failed element upgrade rolls back.
• Upgrade process of the entire system fails: Admin specifies rollback all when the system
upgrade fails. The system stops the upgrade and rolls back the overall upgrade process.
Rolling back an upgrade

Procedure
2. In the navigation pane, click Upgrade Management.
3. Click the Avaya Aura® application that you want to rollback.
The system selects the parent of the application that you select and all child applications of
the parent. For example, the page displays the message Selected System Platform
or child of System Platform, and System Platform and all child
applications.
4. Click Upgrade Actions > Rollback.
Enhanced Access Security Gateway (EASG) overview

EASG provides a secure method for Avaya services personnel to access the Avaya Aura®
application remotely and onsite. Access is under the control of the customer and can be enabled
or disabled at any time. EASG must be enabled for Avaya Services to perform tasks necessary for
the ongoing support, management and optimization of the solution. EASG is also required to
enable remote proactive support tools such as Avaya Expert Systems® and Avaya Healthcheck.
Managing EASG from CLI

About this task
After deploying or upgrading an Avaya Aura® application, you can enable, disable, or view the
status of EASG.
Before you begin
Log in to the application CLI interface.
Procedure
1. To view the status of EASG, run the command: EASGStatus.

The system displays the status of EASG.

2. To enable EASG, do the following:
a. Run the command: EASGManage --enableEASG.
The system displays the following message.
By enabling Avaya Services Logins you are granting Avaya access
to your system. This is required to maximize the performance
and value of your Avaya support entitlements, allowing Avaya to
resolve product issues in a timely manner.
The product must be registered using the Avaya Global
Registration Tool (GRT, see https://grt.avaya.com) to be
eligible for Avaya remote connectivity. Please see the Avaya
support site (https://support.avaya.com/ registration) for
additional information for registering products and
establishing remote access and alarming.
b. When the system prompts, type yes.
The system displays the message: EASG Access is enabled.
3. To disable EASG, do the following:
a. Run the command: EASGManage --disableEASG.
The system displays the following message.
By disabling Avaya Services Logins you are denying Avaya access
to your system. This is not recommended, as it can impact
Avaya's ability to provide support for the product. Unless the
customer is well versed in managing the product themselves,
Avaya Services Logins should not be disabled.
b. When the system prompts, type yes.
The system displays the message: EASG Access is disabled.
Viewing the EASG certificate information

Procedure
Log in to the application CLI interface.
EASG site certificate

EASG site certificates are used by the onsite Avaya technicians who do not have access to the
Avaya network to generate a response to the EASG challenge. The technician will generate and
provide the EASG site certificate to the customer. The customer loads this EASG site certificate on
each server to which the customer has granted the technician access. The EASG site certificate
will only allow access to systems on which it has been installed, and will only allow access to the
given Avaya technician and cannot be used by anyone else to access the system including other
Avaya technicians. Once this is done, the technician logs in with the EASG challenge/response.

Managing site certificates

Before you begin
1. Obtain the site certificate from the Avaya support technician.
2. You must load this site certificate on each server that the technician needs to access. Use
a file transfer tool, such as WinSCP to copy the site certificate to /home/cust directory,
where cust is the login ID. The directory might vary depending on the file transfer tool
used.
3. Note the location of this certificate and use in place of installed_pkcs7_name in the
commands.
4. You must have the following before loading the site certificate:
• Login ID and password
• Secure file transfer tool, such as WinSCP
• Site Authentication Factor
Procedure
1. To install the site certificate:
a. Run the following command: sudo EASGSiteCertManage --add
<installed_pkcs7_name>.
b. Save the Site Authentication Factor to share with the technician once on site.
2. To view information about a particular certificate: run the following command:
• sudo EASGSiteCertManage --list: To list all the site certificates that are currently
installed on the system.
• sudo EASGSiteCertManage --show <installed_pkcs7_name>: To display
detailed information about the specified site certificate.
3. To delete the site certificate, run the following command:
• sudo EASGSiteCertManage --delete <installed_pkcs7_name>: To delete
the specified site certificate.
• sudo EASGSiteCertManage --delete all: To delete all the site certificates that
are currently installed on the system.

Chapter 9: Maintenance
Maintenance
This chapter describes the procedures to change the WebLM IP address, FQDN, and other
parameters from Command Line Interface (CLI). This chapter also provides information about
performing backup and restore of WebLM.
Note:
The existing license files become invalid when you:
• change the WebLM IP address
• perform a WebLM update
• clone a virtual machine
When you redeploy the WebLM, then you must reinstall a new license file to match the new
Host ID generated in the WebLM server.
Changing the IP, FQDN, DNS, Gateway, or Netmask addresses

Before you begin
Log in to the WebLM command line interface with administrator privilege CLI user credentials.
Important:
Ensure that WebLM maintenance is not in progress.
Procedure
1. Type changeIPFQDN —IP <IP Address> —FQDN <FQDN> —GATEWAY <Gateway
address> —NETMASK <Netmask address> —dns <dns address> —SEARCH
<search list for DNS>.
Warning:
Do not change the IP address settings from VMware tools when WebLM is in the
Power Off state.

Maintenance
Note:
After a WebLM IP/FQDN change, the licenses become invalid. You must re-host the
licenses. The license data varies based on the installed license as part of the license
re-host.
2. To add more than one IP address for the DNS server, type changeIPFQDN –dns
primary_DNS_IPaddress, secondary_DNS_IPaddress, DNS_N_IPadress....”
to “changeIPFQDN –dns primary_DNS_IPaddress,
secondary_DNS_IPaddress, ..., DNS_N_IPadress.
You must separate each DNS IP address by a comma (,). For example, changeIPFQDN -
dns 10.14.16.2,14.17.13.5.
The system takes a few seconds to apply the DNS changes to the network.
Note:
The command to configure multiple DNS IP addresses overrides all the previous DNS
IP address entries.
Related links
Rehosting license files on page 53
WebLM CLI operations on page 65
Configuring multiple DNS IP addresses

Before you begin
• Deploy the WebLM OVA file.
• Start the WebLM virtual machine.
When you turn on WebLM for the first time after you deploy the OVA file, the system applies
the network configurations that you provided during the deployment of the WebLM OVA file.
Note:
The command to configure multiple DNS IP addresses overrides all the previous DNS IP
address entries.
Procedure
credentials.
Important:
Ensure that WebLM maintenance is not in progress.
2. Check the existing DNS IP address of WebLM.
3. To add more than one IP address for the DNS server, type changeIPFQDN –dns
primary_DNS_IPaddress, secondary_DNS_IPaddress, DNS_N_IPadress....”

Maintenance
to “changeIPFQDN –dns primary_DNS_IPaddress,

secondary_DNS_IPaddress, ..., DNS_N_IPadress.
You must separate each DNS IP address by a comma (,). For example, changeIPFQDN -
dns 10.14.16.2,14.17.13.5.
The system takes a few seconds to apply the DNS changes to the network.
4. Log on to the WebLM web console with administrator privilege credentials.
5. Ensure that the system displays the multiple DNS IP addresses.
Related links
Configuring the time zone

Procedure
credentials.
2. Type configureTimeZone.
3. Select the time zone from the list.
For example, America/Denver.
Related links
Configuring the NTP server

Procedure
credentials.
2. Type configureNTP <IP address of the NTP server>.
The system configures the NTP server.
Related links
Resetting the WebLM password through CLI

Procedure
credentials.

Maintenance
2. Type the weblm_password <reset|restore> command.

Using password reset you can back up the existing user configuration and apply the
predefined password. By resetting the password, you can restore the backed up
configuration.
Performing WebLM backup

Procedure
credentials.
2. Perform one of the following:
• Type WebLMBackup <backup_location> and provide the backup location as a
parameter.
In this case, the WebLM backup is stored at the location you specify as a parameter.
• Type WebLMBackup.
In this case, the backup location is not provided, and the WebLM backup is stored at the
default location. You can edit the default location using the conf.properties file.
Copy the backup files to a remote computer or to an external storage device.
Performing WebLM restore

Procedure
credentials.
2. Depending on your restore requirement, perform one of the following:
• Type WebLMRestore full <backup_location> to restore all the WebLM files by
picking up the backup file at the specified location.
• Type WebLMRestore full to restore all the WebLM files by picking up the backup file
at the default location specified in conf.properties.
• Type WebLMRestore selective <backup_location> to restore a set of files
necessary for the functionality of the WebLM server from the specified backup location.
• Type WebLMRestore selective to restore a set of files necessary for the
functionality of the WebLM server from the default location specified in conf.properties.
Note:
The conf.properties file is located at /opt/vsp/conf.properties. You can
modify the default location of the backup files through the conf.properties file.

Maintenance
Creating a snapshot backup

About this task
Important:
Do not perform any activity on WebLM until the snapshot backup is complete.
To create the snapshot backup, use the vCenter client or the vSphere client.
Procedure
1. From the list of virtual machines, right-click the required WebLM virtual machine, and
select Snapshot.
2. Click Take Snapshot.
3. In the Name and Description fields, enter a name and the description for the snapshot.
4. Set the following Snapshot options:
a. Enable Snapshot the virtual machine’s memory.
b. Enable Quiesce guest file system (Needs VMware Tools installed).
Note:
Quiescing indicates pausing or altering the state of running processes, particularly the
processes that might modify the information stored on disk during a backup. Quiescing
ensures a consistent and usable backup.
5. Click OK.
6. In the Recent Tasks window, ensure that the status of the Create virtual machine
snapshot task is Completed.
Creating a snapshot restore

About this task
Important:
Do not perform any activity on WebLM until the snapshot restore is complete.
Performing the VMware snapshot restore is not the same as application specific restore.
To restore the snapshot backup, use the vCenter client or the vSphere client.
Procedure
1. From the list of virtual machines, select the deployed WebLM virtual machine, and right-
click and select Snapshot.
2. Open Snapshot Manager.

Maintenance
3. Select the snapshot version that you want to restore.

4. Click Go to.
5. In the Recent Tasks window, verify whether the Status of the Revert snapshot task is
Completed.
WebLM CLI operations

# Command Parameters Description Usage
1. changeIPFQDN • IP < new IP address Updates the IP address, • changeIPFQDN -IP <
for WebLM > FQDN, Gateway, new IP address >
Netmask, DNS, and the
• FQDN < new fully • changeIPFQDN -
search list with the new
qualified domain name FQDN < new fully
value.
of WebLM > qualified domain name
>
• GATEWAY < new
gateway address for • changeIPFQDN -IP <
WebLM > new IP address > -
GATEWAY < new
• NETMASK < new
gateway address for
netmask address for
WebLM > -SEARCH <
WebLM >
new search list for
• dns < new DNS DNS addresses >
address for WebLM >
• SEARCH < new
search list for DNS
addresses >
2. configureNTP < IP address of the NTP Configures the NTP configureNTP < IP
server > server details. address of the NTP
server >
Separate the IP
addresses or the host
names of the NTP
servers with commas (,).
3. configureTim < Time zone that you Configures the time configureTimezone
eZone want to select > zone with the value that Select a time zone. For
you select. example, America/
Denver
Table continues…

Maintenance
# Command Parameters Description Usage

4. WebLMPatchde < absolute path to the Installs the software WebLMPatchdeploy
ploy WebLM service pack, patch, the service pack, <absolute path to home/
feature pack, or the or the feature pack for admin/< WebLM
software patch > WebLM. FeaturepackName >
Note:
Copy the WebLM
feature pack or
patches that you
install to /home/
admin/.
5. weblm_passwo <reset> Reset option backs up weblm_password
rd the existing user reset
<restore>
configuration and
weblm_password
applies the predefined
restore
password.
Restore option restores
the backed-up user
configuration. The utility
also supports the non-
root user, such as
admin.
6. configureTLS <TLSv1.2> Configures the TLS Type one of the
support. following option:
<TLSv1.1>
• enable TLSv1.2
<TLSv1>
• enable TLSv1.2 and
TLSv1.1
• enable TLSv1.2,
TLSv1.1 and TLSv1.0
7. collectLogs Collects the WebLM
logs in the /tmp/
WebLM_Logs_XXXXXXX
XXXXXXXX.zip file.
Viewing the job history of virtual machine operations

Procedure
1. On the System Manager web console, click Services > Solution Deployment Manager >
Application Management.
2.
On the desktop, click the SDM icon ( ), and then click Application Management.
3. In the lower pane, click Job History.

Maintenance
4. On the Job History page, in Operation, select one or more operations.

5. Click Submit.
The page displays the details of jobs that you selected.
Job History field descriptions

Name/Button Description
Operation The operation that is performed on a virtual
machine.
You can select one or more operations that are
performed on a virtual machine, such as host
restart, virtual machine deployment, and patch
installation.
Submit Provides details of jobs that you selected.
History
Name Description
Job ID The unique name of the virtual machine
management job.
IP/FQDN The IP address or host name of the virtual machine
or the host where the operation is performed.
Operation The operation performed on the virtual machine or
host. For example, host refresh, virtual machine
deployment, and patch installation.
Status The status of the job.
Start Time The start time of the job.
End Time The end time of the job.
Monitoring a host and virtual machine

Monitoring a platform
Procedure
1. Click Monitor Platforms.
2. On the Monitor Hosts page, do the following:
a. In Hosts, click a host.
b. Click Generate Graph.
The system displays the graph regarding the CPU/memory usage of the host that you
selected.

Maintenance
Monitoring an application
Procedure
1. Click Monitor Applications.
2. In the Monitor VMs page, do the following:
a. In Hosts, click a host.
b. In Virtual machines, click a virtual machine on the host that you selected.
3. Click Generate Graph.
The system displays the graph regarding the CPU/memory usage of the virtual machine
that you selected.

Chapter 10: Resources
Avaya WebLM documentation

The following table lists the documents related to Avaya WebLM. Download the documents from
the Avaya Support website at http://support.avaya.com.
Title Description Audience
Implementing
Deploying standalone Avaya Deploy the application in virtual appliance Implementation
WebLM in Virtual Appliance environment by using Solution Deployment personnel
Manager
Deploying standalone Avaya Deploy the application in virtualized Implementation
WebLM in Virtualized Environment environment. personnel
Deploying standalone Avaya Deploy the application on cloud services. Implementation
WebLM in Infrastructure as a personnel
Service Environment
Deploying standalone Avaya Deploy the application in software-only Implementation
WebLM in Software-Only environment. personnel
Environment
Upgrading standalone Avaya Upgrade the application. Implementation
WebLM personnel
Administering
Administering standalone Avaya Perform administration tasks System
WebLM administrators
Finding documents on the Avaya Support website

Procedure
1. Go to https://support.avaya.com.
2. At the top of the screen, type your username and password and click Login.
3. Click Support by Product > Documents.
4. In Enter your Product Here, type the product name and then select the product from the
list.
5. In Choose Release, select an appropriate release number.

Resources
6. In the Content Type filter, click a document type, or click Select All to see a list of all
available documents.
For example, for user guides, click User Guides in the Content Type filter. The list
displays the documents only from the selected category.
7. Click Enter.
Accessing the port matrix document

Procedure
1. Go to https://support.avaya.com.
2. Log on to the Avaya website with a valid Avaya user ID and password.
3. On the Avaya Support page, click Support By Product > Documents.
4. In Enter Your Product Here, type the product name, and then select the product from the
list of suggested product names.
5. In Choose Release, select the required release number.
6. In the Content Type filter, select one or more of the following categories:
• Application & Technical Notes
• Design, Development & System Mgt
The list displays the product-specific Port Matrix document.
7. Click Enter.
Avaya Documentation Portal navigation

Customer documentation for some programs is now available on the Avaya Documentation Portal
at https://documentation.avaya.com.
Important:
For documents that are not available on the Avaya Documentation Portal, click Support on
the top menu to open https://support.avaya.com.
Using the Avaya Documentation Portal, you can:
• Search for content in one of the following ways:
- Type a keyword in the Search field.
- Type a keyword in Search, and click Filters to search for content by product, release, and
document type.
- Select a product or solution and then select the appropriate document from the list.
• Find a document from the Publications menu.

Training
• Publish a PDF of the current section in a document, the section and its subsections, or the
entire document.
• Add content to your collection by using My Docs ( ).
Navigate to the My Content > My Docs menu, and do any of the following:
- Create, rename, and delete a collection.
- Add content from various documents to a collection.
- Save a PDF of selected content in a collection and download it to your computer.
- Share content in a collection with others through email.
- Receive content that others have shared with you.
• Add yourself as a watcher by using the Watch icon ( ).
Navigate to the My Content > Watch list menu, and do the following:
- Set how frequently you want to be notified, starting from every day to every 60 days.
- Unwatch selected content, all content in a document, or all content on the Watch list page.
As a watcher, you are notified when content is updated or deleted from a document, or the
document is removed from the portal.
• Share a section on social media platforms, such as Facebook, LinkedIn, and Twitter.
• Send feedback on a section and rate the content.
Note:
Some functionality is only available when you log in to the portal. The available functionality
depends on the role with which you are logged in.
Training
The following courses are available at http://www.avaya-learning.com/. To search for the course,
enter the course code in the Search field and click Go.
Course code Course title
71200V Integrating Avaya Aura® Core Components
Viewing Avaya Mentor videos

Avaya Mentor videos provide technical content on how to install, configure, and troubleshoot
Avaya products.

Resources
About this task

Videos are available on the Avaya Support website, listed under the video document type, and on
the Avaya-run channel on YouTube.
• To find videos on the Avaya Support website, go to https://support.avaya.com/ and do one of
the following:
- In Search, type Avaya Mentor Videos, click Clear All and select Video in the Content
Type.
- In Search, type the product name. On the Search Results page, click Clear All and select
Video in the Content Type.
The Video content type is displayed only when videos are available for that product.
In the right pane, the page displays a list of available videos.
• To find the Avaya Mentor videos on YouTube, go to www.youtube.com/AvayaMentor and do
one of the following:
- Enter a key word or key words in the Search Channel to search for a specific product or
topic.
- Scroll down Playlists, and click a topic name to see the list of videos available for the topic.
For example, Contact Centers.
Note:
Videos are not available for all products.
Support
Go to the Avaya Support website at https://support.avaya.com for the most up-to-date
documentation, product notices, and knowledge articles. You can also search for release notes,
downloads, and resolutions to issues. Use the online service request system to create a service
request. Chat with live agents to get answers to questions, or request an agent to connect you to a
support team if an issue requires additional expertise.
Using the Avaya InSite Knowledge Base

The Avaya InSite Knowledge Base is a web-based search engine that provides:
• Up-to-date troubleshooting procedures and technical tips
• Information about service packs
• Access to customer and technical documentation
• Information about training and certification programs
• Links to other pertinent information

Support
If you are an authorized Avaya Partner or a current Avaya customer with a support contract, you
can access the Knowledge Base without extra cost. You must have a login account and a valid
Sold-To number.
Use the Avaya InSite Knowledge Base for any potential solutions to problems.
1. Go to http://www.avaya.com/support.
2. Log on to the Avaya website with a valid Avaya user ID and password.
The system displays the Avaya Support page.
3. Click Support by Product > Product-specific Support.
4. In Enter Product Name, enter the product, and press Enter.
5. Select the product from the list, and select a release.
6. Click the Technical Solutions tab to see articles.
7. Select relevant articles.

Appendix A: Best practices for VM
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, “Best Practices for Performance
Tuning of Latency-Sensitive Workloads in vSphere VMs” at https://www.vmware.com/.
The following sections describe the recommended BIOS settings for:
• Intel Virtualization Technology
• Dell PowerEdge Servers
• HP ProLiant Servers
Related links
Intel Virtualization Technology on page 74
Dell PowerEdge Server on page 75
HP ProLiant G8 and G9 Servers on page 75
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.

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. These settings depend on the OEM make and model of
the server. The BIOS parameter terminology for current Dell and HP servers are described in the
following sections. Other server models might use other terminology for the same BIOS controls.
• Disabling C-states lowers latencies to activate the CPUs from halt or idle states to a fully
active state.
• Intel Turbo Boost steps up the internal frequency of the processor if the workload requires
more power. The default for this option is enabled. Do not change the default.
Related links
BIOS on page 74
Dell PowerEdge Server

Following are the BIOS recommendations for Dell PowerEdge Servers supported by Avaya SBCE:
When the Dell server starts, press F2 to display the system setup options.
• Set the Power Management Mode to Maximum Performance.
• Set the CPU Power and Performance Management Mode to Maximum Performance.
• In Processor Settings, set:
- Turbo Mode to enable.
- C States to disabled.
Related links
BIOS on page 74
HP ProLiant G8 and G9 Servers

The following are the recommended BIOS settings for the HP ProLiant G8 and G9 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.

Best practices for VM performance and features
Related links
BIOS on page 74
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 http://
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.

VMware networking best practices
If you use the names of the time servers instead of the IP address, you must configure the Domain
Name Service in the guest OS before you administer the NTP service. Otherwise, the NTP service
cannot locate the time servers. If you administer the NTP service first, you must restart the NTP
service after administering the DNS service.
After you administer the NTP service in the application, run the ntpstat or /usr/sbin/ntpq
-p command from a command window. The results from these commands:
• Verify if the NTP service is getting time from a network time source.
• Indicate which network time source is in use.
• Display how closely the guest OS matches the network time.
• Display how often the guest OS checks the time.
The guest OS polls the time source every 65 to 1024 seconds. Larger time intervals indicate that
the guest clock is tracking the network time source closely. If the time source is local, then the
NTP service is not using a network time source and a problem exists.
If the clock value is consistently wrong, look through the system log for entries regarding ntpd.
The NTP service writes the activities it performs to the log, including when the NTP service loses
synchronization with a network time source.

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

• Configure all VMkernel vNICs to be the same IP Maximum Transmission Unit (MTU).
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.
• 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.
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.
• Session Manager Management Network: Example 2 shows the Session Manager
Management network separated onto its own vSwitch. The vSwitch has a dedicated physical
NIC that physically segregates the Session Manager Management network from other
network traffic.
References
Title Link
Product Support Notice PSN003556u Go to http://support.avaya.com and search for
PSN003556u.
Performance Best Practices for VMware vSphere® Go to https://www.vmware.com/support/pubs/ and
6.0 search for Performance Best Practices for VMware
vSphere® 6.0.
VMware vSphere 6.5 Documentation Go to https://www.vmware.com/support/pubs/ and
search for VMware vSphere 6.5 Documentation.
VMware vSphere 6.0 Documentation Go to https://www.vmware.com/support/pubs/ and
search for VMware vSphere 6.0 Documentation.
VMware Documentation Sets https://www.vmware.com/support/pubs/
Storage
For best performance, use WebLM only on disks local to the ESXi Host, or Storage Area Network
(SAN) storage devices. Do not store WebLM on an NFS storage system.
Thin vs. thick deployments

VMware ESXi uses a thick virtual disk by default when it creates a virtual disk file.. The thick disk
preallocates the entire amount of space specified during the creation of the disk. For example, if
you create a 10 megabyte disk, all 10 megabytes are preallocated for that virtual disk.
• Thin-provisioned disks can grow to the full size as specified at the time of virtual disk
creation, but they cannot shrink. Once you allocate the blocks, you cannot deallocate them.
• Thin-provisioned disks run the risk of overallocating storage. If storage is over-allocated, thin
virtual disks can grow to fill an entire datastore if left unchecked.
• If a guest operating system needs to make use of a virtual disk, the guest operating system
must first partition and format the disk to a file system it can recognize. Depending on the
type of format selected within the guest operating system, the formatting process may cause
the thin-provisioned disk to grow to full size. For example, if you present a thin-provisioned
disk to a Microsoft Windows operating system and format the disk, unless you explicitly

VMware Snapshots
select the Quick Format option, the format tool in Microsoft Windows writes information to all
sectors on the disk, which in turn inflates the thin-provisioned disk to full size.
VMware Snapshots
A snapshot preserves the state and data of a virtual machine at a specific point in time. You can
create a snapshot before upgrading or installing a patch.
The best time to take a snapshot is when no applications in the virtual machine are
communicating with other computers. The potential for problems is greatest if the virtual machine
is communicating with another computer. For example, if you take a snapshot while the virtual
machine is downloading a file from a server on the network, the virtual machine continues
downloading the file and communicating its progress to the server. If you revert to the snapshot,
communications between the virtual machine and the server are confused and the file transfer
fails.
Caution:
Snapshot operations can adversely affect service. Before performing a snapshot
operation, you must stop the application that is running on the virtual machine or place
the application out-of-service. When the snapshot operation is complete, start or bring
the application back into service.
Snapshots can:
• Consume large amounts of data resources.
• Increase CPU loads on the host.
• Affect performance.
• Affect service.
To prevent adverse behaviors, consider the following recommendations when using the Snapshot
feature:
• Do not rely on VMware snapshots as a robust backup and recovery method. Snapshots are
not backups. The snapshot file is only a change log of the original virtual disk.
• Do not run a virtual machine from a snapshot. Do not use a single snapshot for more than 24
to 72 hours.
• Take the snapshot, make the changes to the virtual machine, and delete or commit the
snapshot after you verify the virtual machine is working properly. These actions prevent
snapshots from growing so large as to cause issues when deleting or committing the
snapshots to the original virtual machine disks.
• When taking a snapshot, do not save the memory of the virtual machine. The time that the
host takes to write the memory to the disk is relative to the amount of memory that the virtual
machine is configured to use. Saving the memory can add several minutes to the time taken
to complete the operation. If the snapshot is active, saving memory can make calls appear to

be active or in progress and can cause confusion to the user. To create a clean snapshot
image from which to boot, do the following when you create a snapshot:
- In the Take Virtual Machine Snapshot window, clear the Snapshot the virtual
machine’s memory check box.
- Select the Quiesce guest file system (Needs VMware Tools installed) check box to
ensure that all write instructions to the disks are complete. You have a better chance of
creating a clean snapshot image from which to boot.
• If you are going to use snapshots for a long time, you must consolidate the snapshot files
regularly to improve performance and reduce disk usage. Before merging the snapshot delta
disks back into the base disk of the virtual machine, you must first delete stored snapshots.
Note:
If a consolidation failure occurs, end-users can use the actual Consolidate option without
opening a service request with VMware. If a commit or delete operation does not merge
the snapshot deltas into the base disk of the virtual machine, the system displays a
warning on the user interface.
Related resources
Title Link
Best practices for virtual machine snapshots in the Best Practices for virtual machine snapshots in the
VMware environment VMware environment
Understanding virtual machine snapshots in Understanding virtual machine snapshots in
VMware ESXi and ESX VMware ESXi and ESX
Working with snapshots Working with snapshots
Configuring VMware vCenter Server to send alarms Send alarms when virtual machines are running
when virtual machines are running from snapshots from snapshots
VMware vMotion
VMware uses the vMotion technology to migrate a running virtual machine from one physical
server to another physical server without incurring down time. The migration process, also known
as a hot migration, migrates running virtual machines with zero downtime, continuous service
availability, and complete transaction integrity.
With vMotion, you can:
• Schedule migration to occur at predetermined times and without the presence of an
administrator.
• Perform hardware maintenance without scheduled downtime.
• Migrate virtual machines away from failing or underperforming servers.
Before using vMotion, you must:
• Ensure that each host that migrates virtual machines to or from the host uses a licensed
vMotion application and the vMotion is enabled.

VMware cloning
• Ensure that you have identical vSwitches. You must enable vMotion on these vSwitches.
• Ensure that the Port Groups are identical for vMotion.
• Use a dedicated NIC to ensure the best performance.
Note:
If WebLM is being used either as a master WebLM server or a local WebLM server in an
enterprise licensing deployment for a product, after migration of virtual machine to another
physical server using vMotion, validate connectivity from the master WebLM server for all the
added local WebLM servers to ensure that the master WebLM server can communicate with
the local WebLM servers.
VMware cloning
WebLM supports VMware cloning. However, WebLM does not support the Guest Customization
feature. Therefore, do not use the Guest Customization wizard in the VMware cloning wizard while
cloning WebLM.
Note:
Do not perform WebLM cloning. If a clone of a WebLM VMware is created, all existing
licenses become invalid. You must rehost all the licenses.
If WebLM is the master server in an enterprise licensing deployment for a product, after
cloning the master WebLM server, the enterprise license file is invalidated on the clone. You
must then rehost the enterprise license file on the cloned WebLM server and redo the
enterprise configurations. The administrator must add the local WebLM server again and
change allocations for each WebLM server to use the cloned master WebLM server with the
existing local WebLM servers.
If WebLM is the local WebLM server in an enterprise licensing deployment for a product, after
cloning the local WebLM server, the allocation license file on the local WebLM server is
invalidated due to the changed host ID. The administrator must validate the connectivity for
the local WebLM server from the master WebLM server and change allocations to push a new
allocation license file to the local WebLM server with a valid host ID.
VMware high availability

In a virtualized environment, you must use the VMware High Availability (HA) method to recover
WebLM in the event of an ESXi Host failure. For more information, see “High Availability
documentation for VMware”.
Note:
High Availability will not result in HostID change and all the installed licenses are valid.

Appendix B: PCN and PSN notifications
PCN and PSN notifications

Avaya issues a product-change notice (PCN) for any software update. For example, a PCN must
accompany a service pack or an update that must be applied universally. Avaya issues a product-
support notice (PSN) when there is no update, service pack, or release fix, but the business unit or
Avaya Services need to alert Avaya Direct, Business Partners, and customers of a problem or a
change in a product. A PSN can also be used to provide a work around for a known problem,
steps to recover logs, or steps to recover software. Both these notices alert you to important
issues that directly impact Avaya products.
Viewing PCNs and PSNs

About this task
To view PCNs and PSNs, perform the following steps:
Procedure
1. Go to the Avaya Support website at https://support.avaya.com.
If the Avaya Support website displays the login page, enter your SSO login credentials.
2. On the top of the page, click DOCUMENTS.
3. On the Documents page, in the Enter Your Product Here field, type the name of the
product.
4. In the Choose Release field, select the specific release from the drop-down list.
5. Select the appropriate filters as per your search requirement.
For example, if you select Product Support Notices, the system displays only PSNs in the
documents list.
You can apply multiple filters to search for the required documents.

Signing up for PCNs and PSNs
Signing up for PCNs and PSNs

About this task
Manually viewing PCNs and PSNs is helpful, but you can also sign up for receiving notifications of
new PCNs and PSNs. Signing up for notifications alerts you to specific issues you must be aware
of. These notifications also alert you when new product documentation, new product patches, or
new services packs are available. The Avaya Notifications process manages this proactive
notification system.
To sign up for notifications:
Procedure
1. Go to http://support.avaya.com and search for “Avaya Support Web Tips and
Troubleshooting: E-Notifications Management”.
Under the Results section, click Avaya Support Web Tips and Troubleshooting: E-
Notifications Management.
2. Set up e-notifications.
For detailed information, see the How to set up your E-Notifications procedure.

Glossary
Application A software solution development by Avaya that includes a guest operating

system.
Blade A blade server is a stripped-down server computer with a modular design

optimized to minimize the use of physical space and energy. Although
many components are removed from blade servers to save space,
minimize power consumption and other considerations, the blade still has
all of the functional components to be considered a computer.
EASG Enhanced Access Security Gateway. The Avaya Services Logins to

access your system remotely. The product must be registered using the
Avaya Global Registration Tool for enabling the system for Avaya Remote
Connectivity.
ESXi A virtualization layer that runs directly on the server hardware. Also
known as a bare-metal hypervisor. Provides processor, memory, storage,
and networking resources on multiple virtual machines.
Hypervisor A hypervisor is also known as a Virtual Machine Manager (VMM). A

hypervisor is a hardware virtualization technique which runs multiple
operating systems on the same shared physical server.
MAC Media Access Control address. A unique identifier assigned to network

interfaces for communication on the physical network segment.
OVA Open Virtualization Appliance. An OVA contains the virtual machine

description, disk images, and a manifest zipped into a single file. The
OVA follows the Distributed Management Task Force (DMTF)
specification.
PLDS Product Licensing and Download System. The Avaya PLDS provides
product licensing and electronic software download distribution.
Reservation A reservation specifies the guaranteed minimum required amounts of

CPU or memory for a virtual machine.
SAN Storage Area Network. A SAN is a dedicated network that provides

access to consolidated data storage. SANs are primarily used to make

Snapshot
storage devices, such as disk arrays, accessible to servers so that the

devices appear as locally attached devices to the operating system.
Snapshot The state of a virtual appliance configuration at a particular point in time.

Creating a snapshot can affect service. Some Avaya virtual appliances
have limitations and others have specific instructions for creating
snapshots.
Storage vMotion A VMware feature that migrates virtual machine disk files from one data
storage location to another with limited impact to end users.
vCenter Server An administrative interface from VMware for the entire virtual
infrastructure or data center, including VMs, ESXi hosts, deployment
profiles, distributed virtual networking, and hardware monitoring.
virtual appliance A virtual appliance is a single software application bundled with an

operating system.
VM Virtual Machine. Replica of a physical server from an operational

perspective. A VM is a software implementation of a machine (for
example, a computer) that executes programs similar to a physical
machine.
vMotion A VMware feature that migrates a running virtual machine from one
physical server to another with minimal downtime or impact to end users.
vMotion cannot be used to move virtual machines from one data center to
another.
VMware HA VMware High Availability. A VMware feature for supporting virtual

application failover by migrating the application from one ESXi host to
another. Since the entire host fails over, several applications or virtual
machines can be involved. The failover is a reboot recovery level which
can take several minutes.
vSphere Client The vSphere Client is an interface for administering vCenter Server and
ESXi. Downloadable versions are VMware 5.5 and 6.0. A browser-based
Web client version is VMware 6.5 and later.

Index
A configuration and network parameters
WebLM ......................................................................... 47
accessing port matrix ...........................................................70 configure NTP server ...........................................................62
adding configure virtual machine .....................................................37
Appliance Virtualization Platform host .......................... 38 configure VM
AVP host ....................................................................... 38 Launch Console ............................................................34
ESXi host ......................................................................38 configuring
location ......................................................................... 38 application .................................................................... 30
rule ................................................................................29 configuring multiple DNS IP addresses ............................... 61
software-only platform .................................................. 39 configuring time zone ...........................................................62
vCenter to SDM ............................................................ 41 connecting
adding ESXi host ................................................................. 38 OpenStack Dashboard ................................................. 27
adding location .....................................................................38 content
adding location to host .........................................................43 publishing PDF output .................................................. 70
adding vCenter to SDM ....................................................... 41 searching ...................................................................... 70
add rules sharing ..........................................................................70
security group ............................................................... 29 watching for updates .................................................... 70
analyze job status ................................................................ 54 creating
application application virtual machine ..................................... 32, 36
monitoring .....................................................................68 security group ............................................................... 28
Application Deployment creating a role in vCenter .....................................................40
WebLM field descriptions ..............................................47 creating snapshot backup ....................................................64
Avaya support website .........................................................72 creating snapshot restore .................................................... 64
customer configuration data ................................................ 16
customer VMware ................................................................ 11
B
backup through CLI ............................................................. 63 D
best practices
VMware networking ...................................................... 77 deleting
BIOS .................................................................................... 74 upgrade jobs .................................................................55
BIOS for HP servers ............................................................ 75 deleting vCenter ...................................................................43
BIOS settings deploy Communication Manager OVA
for Dell servers ............................................................. 75 direct host ..................................................................... 21
vSphere Web Client ......................................................21
deploying
C application by using OpenStack ................................... 29
changing DNS ......................................................................60 KVM OVA by using Virt Manager ..................................25
changing FQDN ................................................................... 60 WebLM KVM OVA from CLI by using virsh .................. 26
changing IP address ............................................................ 60 deploying copies .................................................................. 22
changing Netmask address ................................................. 60 deployment
changing network parameters from CLI ...............................60 thick .............................................................................. 80
CLI operations thin ................................................................................80
WebLM ......................................................................... 65 deployment guidelines ......................................................... 17
clones deploy System Manager OVA
deployment ................................................................... 22 using vSphere Web Client ............................................ 19
cloning ................................................................................. 83 documentation
collection WebLM ......................................................................... 69
delete ............................................................................70 documentation portal ........................................................... 70
edit name ......................................................................70 finding content .............................................................. 70
generating PDF ............................................................ 70 navigation ..................................................................... 70
sharing content ............................................................. 70 document changes .............................................................. 10
components downloading software
virtualized environment .................................................12 using PLDS ...................................................................14

Index
E KVM OVA deployment tools .................................................14
EASG
certificate information ................................................... 58
L
disabling ....................................................................... 57 license files
enabling ........................................................................ 57 rehost ............................................................................53
status ............................................................................ 57 location
EASG site certificate ............................................................58 adding ...........................................................................38
editing logging on
vCenter ......................................................................... 43 WebLM web console .................................................... 52
editing upgrade configuration .............................................. 55 log on
editing vCenter .....................................................................43 Nutanix Web console ....................................................31
Edit vCenter ......................................................................... 44 Red Hat Virtualization Manager Web console .............. 35
Enhanced Access Security Gateway
EASG overview ............................................................ 57
ESXi host M
adding ...........................................................................38
Map vCenter ............................................................ 41, 43, 44
extracting
monitoring
KVM OVA ......................................................................25
application .................................................................... 68
platform .........................................................................67
F multiple DNS IP addresses ............................................60, 61
My Docs ...............................................................................70
field descriptions
Job History ....................................................................67
Map vCenter ................................................................. 43 N
finding content on documentation portal ..............................70
network restart ..................................................................... 50
finding port matrix ................................................................ 70
New vCenter ........................................................................ 44
flavor .................................................................................... 28
NTP server
configure .......................................................................62
G NTP time source .................................................................. 76
guidelines
deployment ................................................................... 17 O
OVA file
H deploy ..................................................................... 19, 21
overview ............................................................................... 11
high availability
VMware ........................................................................ 83
P
I PCN notification ................................................................... 84
performing WebLM backup ..................................................63
InSite Knowledge Base ........................................................72 performing WebLM restore .................................................. 63
installing a patch .................................................................. 23 platform
installing a service pack .......................................................23 monitoring .....................................................................67
installing WebLM feature pack .............................................23 PLDS
Intel Virtualization Technology ............................................. 74 downloading software ...................................................14
port matrix ............................................................................70
J post-upgrade checklist
WebLM ......................................................................... 52
Job History .....................................................................66, 67 power on VM ........................................................................34
preupgrade job status .......................................................... 54
PSN notification ................................................................... 84
K
Kernel-based Virtual Machine R
overview ........................................................................11
supported hardware ......................................................13 refresh elements job status ..................................................54

Index
rehosting license files .......................................................... 53 timekeeping ......................................................................... 76

related training courses ....................................................... 71 time zone ............................................................................. 62
removing location from host .................................................43 Training ................................................................................ 71
removing vCenter ................................................................ 43 transferring files
resetting the password .........................................................62 using WinSCP .............................................................. 31
resetting the WebLM password ........................................... 62
resources
server ............................................................................13
U
restoring WebLM ..................................................................63 update network parameters ................................................. 50
rollback updating the WebLM server memory ...................................50
upgrade ........................................................................ 56 upgrade
rollback upgrade .................................................................. 57 rollback ......................................................................... 57
run virtual machine .............................................................. 37 upgrade jobs
deleting ......................................................................... 55
S editing ........................................................................... 55
status ............................................................................ 56
SAL Gateway .......................................................................17 upgrade job status ............................................................... 54
searching for content ........................................................... 70 Upgrade job status
sharing content .................................................................... 70 Viewing ......................................................................... 54
signing up upgrade rollback .................................................................. 56
PCNs and PSNs ........................................................... 85 uploading
site certificate qcow2 disk image on Red Hat Virtualization ................ 35
add ................................................................................59 qcow2 image ................................................................ 27
delete ............................................................................59 qcow2 image on Nutanix .............................................. 31
manage .........................................................................59
view .............................................................................. 59
site preparation
V
checklist for KVM ..........................................................15 vCenter
snapshot; backup .................................................................64 add ................................................................................44
snapshot restore .................................................................. 64 adding ...........................................................................41
snapshots ............................................................................ 81 add location .................................................................. 43
software details deleting ......................................................................... 43
Avaya WebLM .............................................................. 14 edit ................................................................................44
starting the WebLM virtual machine .....................................23 editing ........................................................................... 43
starting up the WebLM server ..............................................23 manage .........................................................................43
start VM ............................................................................... 34 remove location ............................................................ 43
status removing .......................................................................43
Analyze .........................................................................56 unmanage .....................................................................43
analyze job ................................................................... 54 vCentre
Preupgrade check ........................................................ 56 field descriptions ...........................................................43
preupgrade check job ................................................... 54 verifying
Refresh elements job ....................................................54 software version ........................................................... 53
upgrade job ...................................................................54 videos .................................................................................. 71
upgrade jobs .................................................................56 viewing
storage .................................................................................80 PCNs ............................................................................ 84
support .................................................................................72 PSNs ............................................................................ 84
supported applications viewing job history ............................................................... 66
VMware and KVM .........................................................12 virtualized environment ........................................................ 11
supported hardware and resources ..................................... 13 Virtualized Environment ....................................................... 11
System Manager virtual machine operations
7.0 .................................................................................54 job history ..................................................................... 66
upgrade ........................................................................ 54 vMotion ................................................................................ 82
VMware cloning ................................................................... 83
T VMware networking
best practices ............................................................... 77
thick deployment ..................................................................80 VMware Tools ...................................................................... 76
thin deployment ................................................................... 80 VT support ........................................................................... 74

Index
W
watch list .............................................................................. 70
WebLM
admin user ....................................................................47
CLI user ........................................................................ 47
deployment checklist .................................................... 18
update network parameters ..........................................50
WebLM; restore ................................................................... 63
WebLM backup ........................................................ 60, 63, 64
WebLM CLI operations ........................................................ 65
WebLM command line interface operations .........................65
WebLM configuration data ................................................... 16
WebLM field descriptions
Application Deployment ................................................47
WebLM memory
update ...........................................................................50
WebLM resource requirements
footprints .......................................................................14
WebLM restore .............................................................. 60, 64
WebLM server; time zone .................................................... 62
WebLM VMware configuration data .....................................16


Deploying WebLM in Virtualized Environment R81x Issue2 Dec2019

Uploaded by

Copyright:

Available Formats

Deploying WebLM in Virtualized Environment R81x Issue2 Dec2019

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Deploying WebLM in Virtualized Environment R81x Issue2 Dec2019

Uploaded by

Copyright:

Available Formats

Deploying standalone Avaya WebLM in

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 5

Deploying application by using OpenStack........................................................................ 29

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 6

Rolling back an upgrade.................................................................................................. 57

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 7

Signing up for PCNs and PSNs.............................................................................................. 85

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 8

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 9

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 10

Avaya Aura® Virtualized Environment overview

Kernel-based Virtual Machine overview

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 11

Supported applications in Virtualized Environment

For information about other Avaya product compatibility information, go to https://

Virtualized Environment components

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 12

Supported hardware for VMware

Supported hardware for KVM

Configuration tools and utilities

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 13

Supported tools for deploying the KVM OVA

Supported footprints for WebLM Server

Software details of WebLM

Downloading software from PLDS

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 14

Site preparation checklist for KVM

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 15

No. Task Description

1 Install the KVM hypervisor.

Customer configuration data for WebLM

IP address The IP address of the For IPv4: 192.168.x.x

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 16

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 17

Checklist for deploying WebLM on VMware®

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 18

Deploying the WebLM OVA by using vSphere Web Client

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 19

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 20

Deploying the application OVA using vSphere Web Client

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 21

Deployment of cloned and copied OVAs

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 22

Installing a WebLM patch, feature pack, or service pack

Starting the WebLM server virtual machine

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 23

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 24

Extracting KVM OVA

Deploying KVM OVA by using Virt Manager

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 25

Deploying WebLM KVM OVA from CLI by using virsh

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 26

b. Run the WebLM installation utility, type the command: sh WEBLM-installer.sh

Deploying application by using OpenStack

Connecting to OpenStack Dashboard

Uploading the qcow2 image

July 2018 Deploying standalone Avaya WebLM in Virtualized Environment 27

Creating a security group