Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Release 7.0
Issue 1
January 2016
which the scope of the license is detailed below. Where the order
documentation does not expressly identify a license type, the
applicable license will be a Designated System License. The
applicable number of licenses and units of capacity for which the
license is granted will be one (1), unless a different number of
licenses or units of capacity is specified in the documentation or other
materials available to You. Software means computer programs in
object code, provided by Avaya or an Avaya Channel Partner,
whether as stand-alone products, pre-installed on hardware products,
and any upgrades, updates, patches, bug fixes, or modified versions
thereto. Designated Processor means a single stand-alone
computing device. Server means a Designated Processor that
hosts a software application to be accessed by multiple users.
Instance means a single copy of the Software executing at a
particular time: (i) on one physical machine; or (ii) on one deployed
software virtual machine (VM) or similar deployment.
License type(s)
Designated System(s) License (DS). End User may install and use
each copy or an Instance of the Software only on a number of
Designated Processors up to the number indicated in the order.
Avaya may require the Designated Processor(s) to be identified in
the order by type, serial number, feature key, Instance, location or
other specific designation, or to be provided by End User to Avaya
through electronic means established by Avaya specifically for this
purpose.
Concurrent User License (CU). End User may install and use the
Software on multiple Designated Processors or one or more Servers,
so long as only the licensed number of Units are accessing and using
the Software at any given time. A Unit means the unit on which
Avaya, at its sole discretion, bases the pricing of its licenses and can
be, without limitation, an agent, port or user, an e-mail or voice mail
account in the name of a person or corporate function (e.g.,
webmaster or helpdesk), or a directory entry in the administrative
database utilized by the Software that permits one user to interface
with the Software. Units may be linked to a specific, identified Server
or an Instance of the Software.
Database License (DL). End User may install and use each copy or
an Instance of the Software on one Server or on multiple Servers
provided that each of the Servers on which the Software is installed
communicates with no more than one Instance of the same
database.
CPU License (CP). End User may install and use each copy or
Instance of the Software on a number of Servers up to the number
indicated in the order provided that the performance capacity of the
Server(s) does not exceed the performance capacity specified for the
Software. End User may not re-install or operate the Software on
Server(s) with a larger performance capacity without Avayas prior
consent and payment of an upgrade fee.
Named User License (NU). You may: (i) install and use each copy or
Instance of the Software on a single Designated Processor or Server
per authorized Named User (defined below); or (ii) install and use
each copy or Instance of the Software on a Server so long as only
authorized Named Users access and use the Software. Named
User, means a user or device that has been expressly authorized by
Avaya to access and use the Software. At Avayas sole discretion, a
Named User may be, without limitation, designated by name,
corporate function (e.g., webmaster or helpdesk), an e-mail or voice
mail account in the name of a person or corporate function, or a
directory entry in the administrative database utilized by the Software
that permits one user to interface with the Software.
Shrinkwrap License (SR). You may install and use the Software in
accordance with the terms and conditions of the applicable license
agreements, such as shrinkwrap or clickthrough license
accompanying or applicable to the Software (Shrinkwrap License).
Copyright
Except where expressly stated otherwise, no use should be made of
materials on this site, the Documentation, Software, Hosted Service,
or hardware provided by Avaya. All content on this site, the
documentation, Hosted Service, and the product provided by Avaya
including the selection, arrangement and design of the content is
owned either by Avaya or its licensors and is protected by copyright
and other intellectual property laws including the sui generis rights
relating to the protection of databases. You may not modify, copy,
reproduce, republish, upload, post, transmit or distribute in any way
Contents
Chapter 1: Introduction............................................................................................................ 7
Purpose..................................................................................................................................7
Intended audience...................................................................................................................7
Related resources................................................................................................................... 7
Documentation..................................................................................................................7
Training............................................................................................................................ 8
Viewing Avaya Mentor videos.............................................................................................8
Support.................................................................................................................................. 9
Warranty.................................................................................................................................9
Document changes since last issue........................................................................................ 10
Chapter 2: Architecture overview..........................................................................................11
Appliance Virtualization Platform overview...............................................................................11
January 2016
Contents
January 2016
Contents
January 2016
Chapter 1: Introduction
Purpose
This document provides procedures for deploying the Avaya Aura Application Enablement
Services virtual application in the Avaya Aura Virtualized Environment.
The Avaya virtualization offer is presented in two variants:
Avaya Aura Virtualized Environment (VE) - customer-provided VMware infrastructure, and
Avaya Aura Virtualized Appliance (VA) - Avaya provided server and VMware hypervisor, also
known as Appliance Virtualization Platform.
The information provided in this document includes installation, configuration, initial administration,
troubleshooting, and basic maintenance checklists and procedures.
Intended audience
The primary audience for this document is anyone who is involved with installing, configuring, and
verifying AE Services on Avaya provided server pre-installed with Avaya Virtualization Platform, and
customer-provided virtualized environment at a customer site. The audience includes and is not
limited to implementation engineers, field technicians, business partners, solution providers, and
customers.
Related resources
Documentation
The following documents supplement the information in this guide.
Title
Description
Audience
Design
Table continues
January 2016
Introduction
Title
Description
Audience
Sales Engineers
Sales Engineers,
Solution Architects,
Implementation
Engineers, Support
Personnel
Administration
Avaya Aura Application Enablement Provides a common reference for basic
Services Administration and
Application Enablement Services (AE
Maintenance Guide, Release 7.0
Services) administrative tasks.
Administrators,
Implementation
Engineers, Support
Personnel
Training
The following courses are available on the Avaya Learning website at http://www.avayalearning.com. After logging in to the website, enter the course code or the course title in the Search
field and click Go to search for the course.
Course code
Course title
ATI02595AEN
AVA00962WEN
1U00223O
1U00222O
3U00127O
10U00030E
4100
9Z04481V
January 2016
Support
Procedure
To find videos on the Avaya Support website, go to http://support.avaya.com and perform one
of the following actions:
- In Search, type Avaya Mentor Videos to see a list of the available videos.
- In Search, type the product name. On the Search Results page, select Video in the
Content Type column on the left.
To find the Avaya Mentor videos on YouTube, go to www.youtube.com/AvayaMentor and
perform one of the following actions:
- Enter a key word or key words in the Search Channel to search for a specific product or
topic.
- Scroll down Playlists, and click the name of a topic to see the available list of videos posted
on the website.
Note:
Videos are not available for all products.
Support
Go to the Avaya Support website at http://support.avaya.com for the most up-to-date
documentation, product notices, and knowledge articles. You can also search for release notes,
downloads, and resolutions to issues. Use the online service request system to create a service
request. Chat with live agents to get answers to questions, or request an agent to connect you to a
support team if an issue requires additional expertise.
Warranty
Avaya provides a 90-day limited warranty on Application Enablement Services. To understand the
terms of the limited warranty, see the sales agreement or other applicable documentation. In
addition, the standard warranty of Avaya and the details regarding support for Application
Enablement Services in the warranty period is available on the Avaya Support website at https://
support.avaya.com/ under Help & Policies > Policies & Legal > Warranty & Product Lifecycle.
See also Help & Policies > Policies & Legal > License Terms.
January 2016
Introduction
January 2016
10
January 2016
11
Architecture overview
January 2016
12
Software delivery
The software is delivered as one or more pre-packaged Open Virtualization Appliance (OVA) files
that are posted on the Avaya Product Licensing and Download System (PLDS) and the Avaya
support site. Each OVA contains the following components:
The application software and operating system.
Preinstalled VMware tools.
Preset configuration details for:
- RAM and CPU reservations and storage requirements
- Network Interface Card (NIC)
Note:
The customer provides the servers and the VMware infrastructure, that includes VMware
licenses.
Deployment considerations
Deployment into the blade, cluster, and server is managed as follows:
Avaya Appliance Virtualization Platform from System Manager Solution Deployment Manager
or the Solution Deployment Manager client
January 2016
13
Architecture overview
January 2016
14
With Solution Deployment Manager, you can perform the following operations in Virtualized
Environment and Avaya appliance models.
Deploy Avaya Aura applications
Upgrade and migrate Avaya Aura applications
Download Avaya Aura applications
Install service packs, feature packs, and software patches for the following Avaya Aura
applications:
- Communication Manager and associated devices, such as gateways, media modules, and
TN boards.
- Session Manager
- Branch Session Manager
- Utility Services
- Appliance Virtualization Platform. The ESXi host running on Avaya-provided appliance.
The upgrade process involves the following key tasks:
Discover the Avaya Aura application.
Analyze and download the necessary software components.
Run the preupgrade check to ensure successful upgrade environment.
Upgrade the Avaya Aura application.
January 2016
15
Architecture overview
January 2016
16
Related links
Installing the Solution Deployment Manager client on your computer on page 17
Accessing the Solution Deployment Manager client dashboard on page 19
Solution Deployment Manager client capabilities on page 20
January 2016
17
Architecture overview
Tip:
From the system tray, open the application service monitor, select the application server
that you want to stop, and click Stop.
4. Ensure that the firewall allows the ports that are required to install the Solution Deployment
Manager client installation and use the Solution Deployment Manager functionality.
5. Ensure that 443 and 1527 ports are available.
6. Close all applications that are running on your computer.
7. Do not set CATALINA_HOME as environment variable on the computer where you install the
Solution Deployment Manager client.
Tip:
On Computer, right-click properties, and perform the following:
a. In the left navigation pane, click Advanced system settings.
b. On the System Properties dialog box, click Advanced tab, and click Environment
Variables.
c. Verify the system variables.
8. Ensure that the computer on which the Solution Deployment Manager client is running is
connected to the network.
Any operation that you perform might fail if the computer is not connected to the network.
Procedure
1. Download the Avaya_SDMClient_win64_7.0.0.0.16688_116.zip file from the Avaya
PLDS website at https://plds.avaya.com/.
On the Avaya PLDS website, you can provide the application name as System Manager,
and version as 7.0.
2. Copy the zip file, and extract to a location on your computer by using the WinZip application.
3. Using the Run as administrator option, run the
Avaya_SDMClient_win64_7.0.0.0.16688_116.exe file.
The system displays the Avaya Solution Deployment Manager screen.
4. On the Welcome page, click Next.
5. On the License Agreement page, click I accept the terms of the license agreement and
click Next.
6. On the Install Location page, perform one of the following:
To install the Solution Deployment Manager client in the system-defined folder, click
Restore Default Folder.
To specify a different location for installation, click Choose and browse to an empty folder.
7. Click Next.
8. On the Preinstallation Summary page, review the information, and click Next.
January 2016
18
Next steps
To enable the Solution Deployment Manager client to communicate with the services port of
Appliance Virtualization Platform, set the following on the technician computer:
IP address: 192.168.13.5
Netmask: 255.255.248
Gateway: 192.168.13.1
Related links
Solution Deployment Manager client on page 16
January 2016
19
Architecture overview
Procedure
To start the Solution Deployment Manager client, perform one of the following:
Click Start > All Programs > Avaya, and click SDM Client > Avaya SDM Client.
Click
Related links
Solution Deployment Manager client on page 16
January 2016
20
Related links
Solution Deployment Manager client on page 16
January 2016
21
Architecture overview
January 2016
22
VMware components
VMware components
VMware software component
Description
ESXi Host
ESXi Hypervisor
vSphere Client
vCenter Server
Deployment guidelines
The high-level deployment steps are:
1. Deploy the OVA or OVAs.
2. Configure the application.
3. Verify the installation.
The deployment guidelines for the virtual appliances are:
Deploy as many virtual appliances on the same host as possible.
Deploy the virtual appliances on the same cluster if the cluster goes beyond the host boundary.
Segment redundant elements on a different cluster, or ensure that the redundant elements are
not on the same host.
Plan for rainy day scenarios or conditions. Do not configure resources only for traffic or
performance on an average day.
Do not oversubscribe resources. Oversubscribing affects performance.
Monitor the server, host, and virtual appliance performance.
Important:
The values for performance, occupancy, and usage can vary greatly. The blade server
might run at 5% occupancy, but a virtual machine might run at 50% occupancy. Note that a
virtual machine behaves differently when the CPU usage is higher.
January 2016
23
January 2016
24
Related links
AE Services license requirements on page 78
Example Value
aesserver1
example.com
Note:
If you leave this
value blank,
modify or add the
line search <dns
search path> in
the file etc/
resolv.conf
after you deploy
the AE Services
VM successfully.
Default gateway
address for the AE
Services VM
123.45.67.254
123.45.1.2
123.45.67.89
255.255.255.0
123.45.67.90
255.255.255.0
Table continues
January 2016
25
Example Value
Note:
DHCP will not take effect until you configure it from the command line after initial
deployment.
Do not expect AE Services to initiate DHCP on first boot.
Avaya recommends that you do not use DHCP with AE Services.
Value
Virtual CPUs
2 GB / 2200 MHz
2 GB / 4400 MHz
1 CPU
4 GB / 8800 MHz
2 CPU
4 CPU
Memory
2 GB
Storage requirement
20 GB
IOPS
Network usage
75 Kbps
Note:
AE Services has been tested using a SAN-based datastore only. All other disk configurations
are untested.
You may deploy AE Services on a host that does not have the resources to allocate to the VM for
power up. There are CPU reservations assigned to the virtual appliance, built into the OVA, that are
specified for a specific server speed. For more information about hardware resources to support
Virtualized Environment footprint flexibility, see Reconfiguring hardware resources to support VE
flexible footprint on page 94
January 2016
26
Software requirements
Software requirements
Avaya Aura AE Services uses the current software release 7.0 as its standard release.
January 2016
27
January 2016
28
Supported servers
In the Avaya-appliance model, System Manager supports the following servers for deployments and
upgrades to Release 7.0:
Dell PowerEdge R610 2CPU MID2
HP ProLiant DL360 G7 2CPU MID4
Dell PowerEdge R620 1CPU MID3
HP ProLiant DL360p G8
If you must change the server, use Dell PowerEdge R620 or HP ProLiant DL360p G8 to install
Appliance Virtualization Platform and System Manager Release 7.0.
Related links
Network interfaces for the server on page 28
January 2016
29
Related links
Network interfaces for the server on page 28
January 2016
30
SAL Gateway
A Secure Access Link (SAL) Gateway is required for remote access and alarming.
Through SAL, support personnel or tools can gain remote access to managed devices to
troubleshoot and debug problems.
A SAL Gateway:
1. Receives alarms from Avaya products in the customer network.
2. Reformats the alarms.
3. Forwards the alarms to the Avaya support center or a customer-managed Network
Management System.
You can deploy the SAL Gateway OVA using vCenter through a vSphere client. You can also
deploy the SAL Gateway OVA directly to the ESXi server through a vSphere client.
For more information about the SAL Gateway, see the Secure Access Link documentation on the
Avaya Support website at http://support.avaya.com .
January 2016
31
Pre-deployment checklist
Perform the following procedures before deploying the AE Services OVA.
#
Action
Link/Notes
January 2016
32
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. Select View Downloads.
5. Click on the search icon (magnifying glass) for Company Name.
6. In the %Name field, enter Avaya or the Partner company name.
7. Click Search Companies.
8. Locate the correct entry and click the Select link.
9. Enter the Download Pub ID.
10. Click Search Downloads.
11. Scroll down to the entry for the download file and click the Download link.
12. In the Download Manager box, click the appropriate download link.
Note:
The first link, Click to download your file now, uses the Download Manager to
download the file. The Download Manager provides features to manage the download
(stop, resume, auto checksum). The click here link uses your standard browser
download and does not provide the download integrity features.
January 2016
33
13. (Internet Explorer only) If you receive an error message, click on the install ActiveX
message at the top of the page and continue with the download.
14. Select a location where you want to save the file and click Save.
15. If you used the Download Manager, click Details to view the download progress.
Procedure
1. Enter md5sum filename, where filename is the name of the OVA. Include the .ova file
extension in the filename.
2. Compare the md5 checksum of the OVA to be used for installation with the md5 checksum
that is displayed for the OVA on the PLDS Web site.
3. Ensure that both checksums are the same.
4. If the numbers are different, download the OVA again and reverify the md5 checksum.
Procedure
1. Download a tool to compute md5 checksums from one of the following Web sites:
http://www.md5summer.org/
http://zero-sys.net/portal/index.php?kat=70
http://code.kliu.org/hashcheck/
January 2016
34
Note:
Avaya has no control over the content published on these external sites. Use the content
only as reference.
2. Run the tool on the downloaded OVA and note the md5 checksum.
3. Compare the md5 checksum of the OVA to be used for installation with the md5 checksum
that is displayed for the OVA on the PLDS Web site.
4. Ensure that both numbers are the same.
5. If the numbers are different, download the OVA again and reverify the md5 checksum.
Procedure
1. Using your web browser, go to https://support.avaya.com.
2. Click Support by Product > Documents from the drop-down menu.
3. In the Enter Your Product Here box on the Documents page, start typing Application
Enablement Services, and select Application Enablement Services from the drop-down list.
4. From the Choose Release box, select 7.0.
5. In the Filters area, click Release & Software Update Notes and press Enter.
6. Click the title of the release notes.
Your browser displays the release notes as a .PDF document.
7. Optionally, save the .PDF document to your computer.
January 2016
35
Deployment checklist
You can set up Geographic Redundancy on the system after you install the System Manager file.
For more information, see the Geographic Redundancy configuration section.
Use the following checklist to deploy AE Services Release 7.0 virtual application by using the
following checklist:
#
Action
Download the OVA files for Utility Services from the Avaya Support Web site at http://
support.avaya.com
Keep a copy of the license files for the Avaya Aura products so you can replicate with the
new Host ID after the OVA file installation. Ensure that the license file copies are
accessible.
Ensure that the network configuration data such as naming conventions, IP address,
netmask, and gateway is accessible.
AE Services 7.0 can be deployed by either using System Manager or SDM client.
Install the Avaya_SDMClient_win64_7.0.0.0.16688_116.exe file.
For System Manager SDM, install the System Manager OVA file and provide network
parameters for System Manager. For more information on System Manager deployment,
see Deploying Avaya Aura System Manager in Virtualized Environment.
Table continues
January 2016
36
Action
Install Utility Services OVA, and select the footprint size to default footprint, and select
the service mode.
Procedure
1. Go to SMGR Solution Deployment Manager > VM Management for deploying AE
Services using SMGR SDM.
Note:
See the Deployment Checklist before deploying AE Services using SDM Client.
2. Click on Location > Host > Virtual Machines
3. Click on New to create Virtual Machine
4. On the VM Name Field, enter the Host Name of AE Services.
Note:
Make sure you are installing AE Services on the correct Location and Host.
5. Select the Data Store
6. On the Deploy OVA section, deploy AE Services OVA.
Important:
Before deploying AE Services OVA from SMGR SDM or SDM client, see Upgrading Avaya
Aura applications to Release 7.0 for the following:
Downloading the AE Services OVA.
Deploying the AE Services OVA.
7. Select the software library.
8. Select the OVA File.
9. Select the Foot Print.
January 2016
37
10. In the Configuration Parameters Section, enter the AE Services Network Configuration
information.
11. In the Network Parameters field, assign the NICs to the private port.
12. Accept the EULA Acceptance.
13. Verify the AE Services Deployment Status steps by clicking the Status Details Link in the
AE Services Entry of the Virtual Machine list.
14. AE Services OVA deployment is successful. Verify the AE Services deployment status
clicking the status link.
For more information, see Deploying Avaya Aura applications from Avaya Aura System
Manager.
Procedure
1. Using the vSphere Client, log into the target vCenter.
2. In the vSphere Client window, select File > Deploy OVF Template.
3. On the Source section, click Browse.
4. In the Open dialog box, select the OVA you want to deploy.
5. Click Open.
6. On the Source section, click Next.
7. On the OVF Template Details section, click Next.
8. On the End User License Agreement section, read the license agreement.
9. Click Accept to accept the terms of the license agreement, then click Next.
10. In the Name box on the Name and Location section, enter the name for the AE Services VM,
for example AES-6.3.1. The default is Application Enablement Services.
11. Click Next.
12. Select the AE Services profile under the Deployment Configuration section. Click Next.
13. On the Host/Cluster section, select the host or cluster on which you want to run the AE
Services template.
January 2016
38
Note:
If you selected the host before performing Step 2, the Disk Format section appears. Go
to Step 19.
14. Click Next.
15. On the Specify a Specific Host section, select the specific host within the cluster on which
you want to run the AE Services template.
16. Click Next.
If the host has more than one datastore, the Storage section appears. Go to Step 17.
If the host has only one datastore, the Disk Format section appears. Go to Step 19.
17. On the Storage section, select the appropriate datastore to deploy the AE Services Virtual
Machine.
18. Click Next.
The Disk Format section appears.
19. On the Disk Format section, select Thick Provision Lazy Zeroed.
20. Click Next.
The Network Mapping section appears.
21. On the Network Mapping section, select the appropriate network.
22. Click Next.
23. On the Properties section, perform the following steps:
a. Under Application settings, enter the hostname or fully-qualified domain name for the
AE Services VM in the Hostname box.
Note:
The hostname may contain only the ASCII letters a through z (case sensitive), the
digits 0 through 9, and the hyphen (-).
The hostname cannot begin with or end with a hyphen (-).
The entire hostname (including the delimiting dots) may consist of up to 255
characters.
The hostname cannot exceed 15 characters.
b. In the DNS Search Path box, enter the domain name of the AE Services VM.
Note:
If you leave the DNS Search Path box blank, you must modify the file /etc/
resolv.conf after you power up the system.
c. Under System Time settings, select the Timezone and NTP server(s) as applicable.
d. Under Networking Properties settings, enter the default gateway address for the VM. in
the Default Gateway box.
January 2016
39
Note:
If you leave the Default Gateway box blank, you must configure this setting after
deployment.
e. In the DNS box, enter the domain name servers for this VM. Use a comma to separate
multiple servers.
Note:
If you leave the DNS box blank, you must configure this setting after completing the
deployment.
f. In the Public IP Address box, enter the IP Address. Enter the Public Netmask in the
Public Netmask box.
g. In the Private IP Address box, enter the IP Address. Enter the Private Netmask in the
Private Netmask box. This substep is optional.
h. In the Out of Band Management IP Address box, enter the Out of Band Management
IP Address. Enter the Out of Band Management Netmask in the Out of Band
Management Netmask box. This substep is optional.
Note:
Out of Band Management cannot be enabled after AE Services deployment.
24. Click Next.
25. On the Ready to Complete section, verify the settings displayed. If you need to modify any of
the settings, click Back.
26. Click Finish to deploy the OVF.
The Deploying Application Enablement Services message box appears showing
the status of the deployment.
When deployment is complete, the Deployment Completed Successfully message
box appears.
27. On the Deployment Completed Successfully message box, click Close.
Next steps
Go to Starting the Application Enablement Services virtual machine on page 75.
January 2016
40
Procedure
1. Using the vSphere Client, log into the ESXi host server.
2. In the vSphere Client window, select File > Deploy OVF Template.
3. On the Source page, click Browse.
4. In the Open dialog box, select the OVA you want to deploy.
5. Click Open.
6. On the Source page, click Next.
7. On the OVF Template Details page, verify the information, and then click Next.
8. On the End User License Agreement page, read the license agreement.
9. Click Accept to accept the terms of the license agreement.
10. Click Next.
11. In the Name box on the Name and Location page, enter the name for the AE Services VM
(for example, AES-6.3.1). The default is Application Enablement Services.
12. Click Next.
If the host has more than one datastore, the Storage page appears. Go to Step 13.
If the host has only one datastore, the Disk Format page appears. Go to Step 15.
13. On the Storage page, select the appropriate datastore to deploy the AES Virtual Machine.
14. Click Next.
The Disk Format page appears.
15. On the Disk Format page, select Thick Provision Lazy Zeroed.
16. Click Next.
The Network Mapping page appears.
17. On the Network Mapping page, select the appropriate network.
18. Click Next.
19. On the Ready to Complete page, verify the settings displayed. If you need to modify any of
the settings, use the Back button.
20. When you are ready to deploy the OVF, click Finish.
The Deploying Application Enablement Services message box appears showing the status
of the deployment.
When the deployment is complete, the Deployment Completed Successfully message box
appears.
21. In the Deployment Completed Successfully message box, click Close.
January 2016
41
Next steps
Go to Starting the Application Enablement Services virtual machine on page 75.
Procedure
1. In the vSphere Client window, select View > Inventory > Virtual Machines and Templates.
2. Right-click the Virtual Machine, and select Edit Settings.
3. In the Virtual Machine Properties window, click the Resources tab.
4. In the Settings list, click CPU.
5. In the Resources Allocation area, perform one of the following steps:
Move the Reservation slider to specify the appropriate number.
Enter the appropriate number in the Reservation box.
Note:
Since the AE Services Virtual Machine requires four virtual CPUs, multiply by four the
CPU speed displayed under the host's summary tab.
6. Click OK.
January 2016
42
Procedure
Perform one of the following:
If System Manager is not already deployed, double-click the Solution Deployment Manager client.
If System Manager is available, on the web console, click Services > Solution Deployment
Manager.
January 2016
43
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
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. Perform one of the following:
For System Manager Solution Deployment Manager, on the web console, click
Services > Solution Deployment Manager, and then click VM Management.
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
2. On the Location tab, in the Locations section, select a location that you want to edit.
3. Click Edit.
4. In the Edit Location section, make the required changes.
5. Click Save.
January 2016
44
Related links
New and Edit location field descriptions on page 48
Deleting a location
Procedure
1. Perform one of the following:
For System Manager Solution Deployment Manager, on the web console, click
Services > Solution Deployment Manager, and then click VM Management.
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
2. On the Location tab, in the Locations section, select one or more locations that you want to
delete.
3. Click Delete.
4. On the Delete confirmation dialog box, click Yes.
The system does not delete the virtual machines that are running on the host, and moves the
host to Unknown location host mapping > Unknown location.
Description
Location Name
City
Country
Button
Description
New
Edit
Delete
Hosts
Name
Description
Host Name
January 2016
45
Name
Description
Host IP
Host FQDN
Current Action
Last Action
Data Store
License Status
ESXi Version
AVP
Button
Description
Add
Edit
Remove
Change Password
Update
Refresh
Virtual Machines
Name
Description
VM Name
VM IP
VM FQDN
VM App Name
January 2016
46
Name
Description
VM App Version
VM State
Last Action
Host Name
Trust Status
Data Store
Button
Description
New
Edit
Delete
Start
Stop
Restart
Refresh VM
Show Selected
January 2016
47
Button
Description
When the connection between System Manager and
the virtual machine establishes, the Trust Status
changes to Success.
Description
Name
Avaya Sold-To #
Address
City
State/Province/Region
ZIP/PostalCode
Country
Time Zone
Description
Default Gateway
DNS Server 1
DNS Server 2
NetMask
NTP Server
January 2016
48
Button
Description
Save
Edit
Delete
Cancel
Procedure
1. Perform one of the following:
For System Manager Solution Deployment Manager, on the web console, click
Services > Solution Deployment Manager, and then click VM Management.
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
January 2016
49
Important:
When you change the IP address or FQDN of the Appliance Virtualization Platform host
from local inventory, you require Utility Services. To get the Utility Services application
name during the IP address or FQDN change, refresh Utility Services to ensure that
Utility Services is available.
Related links
New and Edit host field descriptions on page 53
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
January 2016
50
Procedure
1. Perform one of the following:
For System Manager Solution Deployment Manager, on the web console, click
Services > Solution Deployment Manager, and then click VM Management.
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
Procedure
1. Perform one of the following:
For System Manager Solution Deployment Manager, on the web console, click
Services > Solution Deployment Manager, and then click VM Management.
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
January 2016
51
3. On the Host tab, in the Host for Selected Location <location name> section, select an ESXi
host and click Change Network Params.
4. In the Network Parameters section, change the IP address, subnetmask, and other
parameters as appropriate.
5. To change the gateway IP address, perform the following:
a. Click Change Gateway.
The Gateway field becomes available for providing the IP address.
b. In Gateway, change the IP address.
c. Click Save Gateway.
6. Click Save.
The system updates the Appliance Virtualization Platform host information.
Related links
Change Network Parameters field descriptions on page 54
Procedure
1. Perform one of the following:
For System Manager Solution Deployment Manager, on the web console, click
Services > Solution Deployment Manager, and then click VM Management.
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
January 2016
52
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
2. On the Host tab, in the Host for Selected Location <location name> section, select one or
more hosts that you want to delete.
3. Click Delete.
4. On the Delete confirmation page, click Yes.
Procedure
1. Perform one of the following:
For System Manager Solution Deployment Manager, on the web console, click
Services > Solution Deployment Manager, and then click VM Management.
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
2. In the left navigation pane, click the Unknown location host mapping link.
3. In the Host Location Mapping section, select an ESXi host and click Edit.
The system displays the Host Information page.
4. Select a location to which you want to map the ESXi host.
5. Click Submit.
The system displays the ESXi host in the selected location.
Description
Location
January 2016
53
Name
Description
Host Name
Host FQDN or IP
User Name
Password
Button
Description
Save
Description
Name
IP
Subnet Mask
Host Name
Domain Name
Gateway
January 2016
54
Button
Description
Change Gateway
Save Gateway
Button
Description
Save
Description
Current Password
New Password
Button
Description
Change Password
Description
Patch location
Button
Description
Update Host
January 2016
55
Procedure
1. Download the OVA file on your computer.
2. On the System Manager web console, click Services > Solution Deployment Manager.
3. In the navigation pane, click Download Management.
4. On the Download Management page, perform the following:
a. In the Select Files Download Details section, in the Source field, select My Computer.
b. Click Download.
The system displays the Upload File page.
5. In the Software Library field, select a local System Manager software library.
6. Complete the details for the product family, device type, and the software type.
7. Click Browse and select the OVA file from the location on the system.
This system uploads the OVA file from local computer to the designated software library on
System Manager.
January 2016
56
For information about the Deployment checklist, see Deploying Avaya Aura applications from
Avaya Aura System Manager.
Add a location.
Add Appliance Virtualization Platform or an ESXi host to a location.
Download the required OVA files to System Manager.
Procedure
1. Perform one of the following:
For System Manager Solution Deployment Manager, on the web console, click
Services > Solution Deployment Manager, and then click VM Management.
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
January 2016
57
Procedure
1. Perform one of the following:
For System Manager Solution Deployment Manager, on the web console, click
Services > Solution Deployment Manager, and then click VM Management.
January 2016
58
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
January 2016
59
Note:
The Manage Elements page in the inventory does not display the user credentials. You
must manually update the user credentials.
11. To view details, click the Status Details link.
Related links
VM Deployment field descriptions on page 62
Downloading the OVA file to System Manager on page 56
Procedure
1. Perform one of the following:
For System Manager Solution Deployment Manager, on the web console, click
Services > Solution Deployment Manager, and then click VM Management.
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
January 2016
60
The Update IPFQDN in Local Inventory option updates the IP address or FQDN only
in the local database in System Manager. The actual IP address or FQDN of the host
does not change. Use Update Network Params in the Host tab to update the IP
address or FQDN of the host.
b. Click Update VM IP/FQDN.
c. Provide the IP address and FQDN of the virtual machine.
Update IPFQDN in Local Inventory updates the IP address or FQDN only in the local
database in System Manager. The actual IP address or FQDN of the host does not
change. Use Update Network Params in the Host tab to update the IP address or
FQDN of the host.
6. Click Save.
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
2. From the virtual management tree, select a host to which you added virtual machines.
3. On the Virtual Machines tab, select one or more virtual machines that you want to start.
4. Click Start.
In VM State, the system displays Started.
Procedure
1. Perform one of the following:
For System Manager Solution Deployment Manager, on the web console, click
Services > Solution Deployment Manager, and then click VM Management.
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
2. From the virtual management tree, select a ESXi or vCentre host to which you added virtual
machines.
3. On the Virtual Machines tab, select one or more virtual machines that you want to stop.
January 2016
61
4. Click Stop.
In VM State, the system displays Stopped.
Procedure
1. Perform one of the following:
For System Manager Solution Deployment Manager, on the web console, click
Services > Solution Deployment Manager, and then click VM Management.
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
2. From the virtual management tree, select a host to which you added virtual machines.
3. On the Virtual Machines tab, select one or more virtual machines that you want to restart.
4. Click Restart.
In VM State, the system displays Stopped and then Started.
Description
Select Location
Select Host
Host FQDN
VM Name
ME Deployment
Description
Resource Pool
January 2016
62
Button
Description
Datacentre/Cluster
AVP host
Model
Data Store
Capacity Details
The system displays the CPU and memory details of the host in this section. The fields are readonly.
Name
Description
Name
The name
Full Capacity
Free Capacity
Reserved Capacity
Status
The status
Deploy OVA
Name
Description
Submit
January 2016
63
Name
Description
Select OVAs
Configuration Parameters
The system populates most of the fields depending on the OVA file.
Note:
For configuration parameter fields, for Communication Manager Messaging and Utility Services,
see VM Deployment Configuration and Network Parameters field descriptions on page 66.
Table 1: Configuration Parameters for Communication Manager simplex OVA deployment
Name
Description
CM IPv4 Address
CM IPv4 Netmask
CM IPv4 Gateway
CM Hostname
NTP Servers
DNS Servers
January 2016
64
Name
Description
The login name for the privileged administrator. You can change
the value at any point of time.
Confirm Password
Network Parameters
Name
Description
Public
Services
Duplication Link
Button
Description
Deploy
Cancel
Related links
VM Deployment Configuration and Network Parameters field descriptions on page 66
January 2016
65
Description
Messaging Hostname
NTP Servers
DNS Server(s)
Confirm Password
Description
Configuration Parameters
Communication Manager IP
January 2016
66
Name
Description
Note:
A unique Communication Manager IP address is required for
each Utility Services. If you are not associated with a
Communication Manager server, specify a static IP that is in
your network range.
Hostname
TImezone setting
The selected timezone setting for the Utility Services virtual machine.
NTP Server IP
The mode in which you want to deploy Utility Services. The options
are:
Services Port Only: Deploys Services Port only. Use when the
customer already has Utility Services running on another virtual
machine and providing the services.
With the services port feature, through a laptop connected to the
services port of Appliance Virtualization Platform, you can gain
access to Avaya virtual machines and the hypervisor that are
deployed.
Utility Servers Only: Use to disable routing. Set this mode only for
Virtualized Environment. If you set this mode for an Avaya
appliance, the services port becomes non-operational.
Full Functionality: Utility Services and services port enabled. The
default mode for Appliance Virtualization Platform.
You can set the mode only during the deployment. You cannot
change the mode after the virtual machine is deployed.
Note:
For the Solution Deployment Manager client to connect to the
services port features of Utility Services, change the IP address
to 192.11.13.5 on the computer of the technician
Table continues
January 2016
67
Name
Description
Utility Services can gain access to the hypervisor and all virtual
machines. Utility Services provides application routing between
the physical port and virtual applications.
Enrollment Password
Confirmation password
Network Parameters
Default Gateway
DNS
The IP address of domain name servers for the Utility Services virtual
machine. Separate each IP address by a comma.
Required field unless you use DHCP.
Public IP address
Public Netmask
Description
VM Name
VM IP/FQDN
The VM IP/FQDN
Utility Services IP
Button
Description
Update
Description
Action to be performed
January 2016
68
Name
Description
Commit: Displays the software patches that you
can commit.
Rollback: Displays the software patches that you
can rollback.
VM Name
VM IP
Patch Name
Patch Type
Patch Version
Patch State
Patch Status
Button
Description
Commit
Rollback
Description
VM Name
VM IP
VM FQDN
Host Name
January 2016
69
Button
Description
Install
Description
VM Name
VM IP/FQDN
User Name
Password
The password
Button
Description
Reestablish Connection
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
January 2016
70
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
Managing vCenter
Adding an ESXi host in vCenter
About this task
System Manager Solution Deployment Manager supports virtual machine management in vCenter
5.0, 5.1, and 5.5. 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,
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.
Procedure
1. Perform one of the following:
For System Manager Solution Deployment Manager, on the web console, click
Services > Solution Deployment Manager, and then click VM Management.
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
January 2016
71
In the Managed Hosts section, the system displays the ESXi hosts that this vCenter
manages.
Related links
Editing the ESXi host in vCenter on page 72
Map vCenter field descriptions on page 73
New vCentre and Edit vCentre field descriptions on page 73
Procedure
1. Perform one of the following:
For System Manager Solution Deployment Manager, on the web console, click
Services > Solution Deployment Manager, and then click VM Management.
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
),
Procedure
1. Perform one of the following:
For System Manager Solution Deployment Manager, on the web console, click
Services > Solution Deployment Manager, and then click VM Management.
For the Solution Deployment Manager client, on the desktop, click the SDM icon (
and then click VM Management.
January 2016
),
72
Description
Name
IP
FQDN
License
Status
Button
Description
New
Edit
Delete
Refresh
Description
vCenter IP/FQDN
User Name
Password
Button
Description
Commit
Refresh
Managed Hosts
Name
Description
Host IP/FQDN
Host Name
Location
Edit
January 2016
73
Name
Description
Bulk Update
Update
Commit
Unmanaged Hosts
Name
Description
Host IP/FQDN
ESXi Version
January 2016
74
Chapter 6: Configuration
Configuration checklist
Use the following checklist for configuring the AE Services virtual appliance.
#
Action
Link/Notes
January 2016
75
Configuration
Procedure
1. In the vSphere Client inventory, select the host where the virtual machine is located.
2. Click the Configuration tab.
3. In the Software section, click Virtual Machine Startup/Shutdown.
4. Click Properties in the upper-right corner of the screen.
5. In the System Settings section, select Allow virtual machines to start and stop
automatically with the system.
6. In the Manual Startup section, select the virtual machine.
7. Use the Move up button to move the virtual machine to the Automatic Startup section.
8. Click OK.
Procedure
1. In the vSphere Client window, select View > Inventory > VMs and Templates.
2. Right-click the AE Services VM, and select Open Console.
January 2016
76
January 2016
77
Configuration
AE Services licensing
AE Services license requirements
To get the full functionality for AE Services you must install the AE Services product license. The
product license specifies the features you are permitted to use. For more information about licensed
features, see the Avaya Aura Application Enablement Services Overview Guide, 02-300360.
Overview of licensing
Use this overview to learn about the licensing cycle and when licensing events take place.
Obtain the license from the Avaya Product Licensing and Delivery System (PLDS) Web site.
See Downloading software from PLDS on page 33 for more information.
After you install the AE Services software, log in to the AE Services Management Console to
access the Avaya Web License Manager (WebLM).
Note:
You must connect to a remote WebLM. You are running AE Services on the VMware
deployment which uses a remote WebLM.
Use WebLM to install the license.
After you install the license file, you must reboot the AE server.
When the license file is installed, you have access to the AE Services software.
Procedure
1. From your browser, log in to AE Services Management Console. See Logging into the
Management Console on page 84.
2. From the main menu, select Licensing > WebLM Server Address.
3. In the WebLM IP Address field, enter the IPv4 address of the remote WebLM server.
Note:
WebLM does not support IPv6.
January 2016
78
AE Services licensing
4. Use the SSL check box to specify the appropriate setting for SSL. The default setting is
enabled (that is, the SSL check box is checked).
5. In the WebLM Port field, enter the port number of the WebLM server.
Procedure
1. In the address bar of your browser, type https://fully-qualified domain name or
IP address of the AE Services server and press ENTER.
2. From the Application Enablement Services welcome page, click Continue to Login.
3. From the Application Enablement Services Management Console log in page, type your user
name and password, and click Login.
Important:
You cannot log in to the Application Enablement Services Management Console as the
root user. Avaya service technicians should log in as craft. Customers should log in as
cust.
Your browser displays the Application Enablement Services Management Console. The
main menu is in the left pane and the welcome page is in the right pane.
4. From the main menu, select Licensing > WebLM Server Access.
5. Follow these steps to complete the Web License Manager Logon screen.
a. In the User Name field, type admin, the default WebLM User name.
b. In the Password field, type weblmadmin, the default WebLM password.
c. Click the arrow.
The first time you log in to WebLM, the server displays the Change Password page.
6. Complete the fields on the Change Password page and click Submit.
Your browser displays the login page again.
7. Log in as admin with the password you just created.
January 2016
79
Configuration
Procedure
1. From the main menu of the AE Services Management Console, click Licensing > WebLM
Server Access.
2. From the Web License Manager Logon screen, type your WebLM user name and password,
and click the arrow.
3. From the WebLM Install License page, click Browse.
4. Locate the AE Services license file, and select it.
5. With the license file name displaying in the text box, click Install.
WebLM uploads the license file to the WebLM server. When the process is complete, the
server displays the message License file installed successfully.
Note:
If you do not receive this message, see Troubleshooting licensing error messages on
page 82.
6. Verify that the license settings are correct for this customer.
a. Click Licensed Products > Application_Enablement.
b. Verify that the correct license settings are enabled.
7. From the main menu, click Logout.
8. Restart AE Services.
See Restarting AE Services from the AE Services Management Console on page 81 or
Restarting AE Services from the Linux command line on page 81.
January 2016
80
AE Services licensing
Procedure
1. Open an ssh session to the AE Services server, using either of the following methods.
Customers using the Avaya Services package: Log in as cust, and access the root
account by using the su - root command.
Avaya service technicians: Log in as craft, and access the root account by using the su sroot command.
2. Restart AE Services using the following command: /sbin/service aesvcs restart.
Result
The restart command stops AE Services, configures them, and then starts the services. The
restart process takes from 3 to 10 minutes.
Procedure
1. From your browser, log in to the AE Services Management Console. See Logging into the
Management Console on page 84 for more information.
2. From the AE Services Management Console main menu, click Maintenance > Service
Controller.
3. On the Service Controller page, click Restart AE Server.
4. On the Restart AE Server page, click Restart.
After a pause, the server returns to the Service Controller page. A restart can take several
minutes.
5. Verify that all the correct licensed services are running.
January 2016
81
Configuration
Explanation
January 2016
82
Reinstalling or replacing the Avaya Access Security Gateway default authentication file
Procedure
1. Log in to WebLM using an appropriate user name and password. See Logging in to WebLM
and creating a WebLM password on page 79.
2. On the WebLM Home page, click Server properties.
3. On the Server Properties page, locate the value for Primary Host ID.
Procedure
1. Log in to WebLM using an appropriate user name and password.
See Logging in to WebLM and creating a WebLM password on page 79.
2. From the main menu, click Uninstall License.
3. From the Uninstall License page, select the check box for the Application_Enablement
license, and click Uninstall.
Your browser displays a message asking if you want to continue.
4. Click OK.
January 2016
83
Configuration
Note:
Performing this procedure will remove the current authentication file. If you want to maintain a
copy of the current authentication file on the server, you must make a copy of this authentication
file before performing this procedure.
Procedure
1. Open an ssh session to the AE Services server, and log in as the system administrator.
2. From the command line as the root user, type loadauth f l authFileName where
authFileName is the path and file name of the authentication file you want to use. The path
and file name for the default authentication file is /opt/mvap/asg/AESvcs-defaultasg-auth.xml.
3. Press Enter.
The system displays Loading file <name of the authentication file>.
Note:
The loadauth command removed the account password for the root user. If you want
to maintain access via a password for root, perform the following command from the
command line: passwd root.
4. On another machine or in another window, log into the AE Services server as craft.
The system displays a challenge on the screen.
5. Enter the appropriate ASG response.
You are logged into the system.
6. At the command line, type su - root and press Enter to promote the craft account to
the root account.
The system displays a challenge on the screen.
7. Enter the appropriate ASG response.
You are logged into the system.
8. Log out of root.
January 2016
84
Procedure
1. In the address bar of your browser, type the fully qualified domain name or IP address of the
AE Services server (for example https://aserver.example.com).
The first time you try to access the AE Services server, your browser presents a security
alert for an SSL certificate. If the SSL certificate is not presented, verify that the address bar
on your browser displays https and the fully qualified domain name or IP address of the AE
Services server.
2. From the security alert window, click Yes to accept the certificate.
3. From the Application Enablement Services welcome page, click Continue To Login.
4. In the Username box on the Application Enablement Services Management Console log in
page, type your login ID.
5. Click Continue.
6. In the Password box, enter your password.
Note:
If the Access Security Gateway (ASG) is present, your login ID is challenged by ASG.
You must enter a proper response in the Response box to log in successfully.
7. Click Login.
Your browser displays the Application Enablement Services Management Console. The
main menu is in the left pane and the welcome page is in the right pane.
Note:
If this is the first time you are logging in, the End User License Agreement page will be
displayed.
January 2016
85
January 2016
86
Procedure
1. From the AE Services Management Console, back up the server database before you install
an update. See Backing up the AE Services database on page 91.
2. Open an ssh session to the AE Server and access an account with root privileges. See
Opening an ssh session to AE Services on page 88.
3. Copy the patch file via SCP to the AE Services system.
4. Using vSphere Client, take a snap shot of the AE Services system.
Note:
Taking a snap shot of the AE Services system may be service affecting.
5. Run the command update -u --force <patch file>, where <patch file> is the
name of the AE Services patch file.
The update may take up to 10 minutes.
6. After the update is complete, log off.
7. Remove the snap shot.
Procedure
1. Open an ssh session to the AE Services server and access an account with root privileges.
See Opening an ssh session to AE Services on page 88 for more information.
2. From the command prompt, type swversion -a to find the number of the update or patch you
want to remove.
January 2016
87
Updating AE Services
3. At the command prompt, type update -e patchnumber. The screen displays a list of all the
RPMs to be uninstalled. The system prompts you for confirmation before it uninstalls these
RPMs.
If you enter y, the system uninstalls the updates or patches. The system:
- stops AE Services, Tomcat service, and DBService.
- rolls back the RPMs specified in patchnumber.txt to the previous version.
- restarts AE Services, Tomcat service, and DBService.
If you enter n, the update script exits.
Related links
Installing AE Services updates and patches on page 86
Procedure
1. Start your ssh client, and complete the information in the dialog box that it presents to open a
session. For example, specify the following information to open a session to the AE Services
server.
Host Name (or IP address) - enter the host name or IP address of your AE Services
server, for example, aeserver.example.com.
Port - enter 22.
Connection type - enter SSH.
Click Open.
Note:
The server displays the PuTTY Security Alert window the first time you connect to the
SAMP. If you see this window, click Yes to accept the servers host key.
The system displays the PuTTY window.
2. If you are an Avaya service technician or Business Partner, log in as follows:
a. At the login as: prompt, type craft.
b. At the prompt, type the challenge/password.
c. At the command prompt, type su - sroot.
d. At the prompt, type the challenge/password.
January 2016
88
January 2016
89
Migration checklist
Migrate to AE Services for Virtualized Environment from one of the following AE Services offers:
AE Services Software Only offer.
AE Services Bundled Server offer.
AE Services on System Platform offer.
AE Services on VMware offer.
Use the following checklist for upgrading the AE Services virtual appliance:
Note:
If you have AE Services 6.3, 6.3.1, 6.3.3 installed and you want to upgrade to AE Services 7.0,
go to Using RPM patch for installing AE Services 7.0 on page 91. Apply the pre-upgrade
patch on the server where the backup needs to be taken. It is the server that will be migrated to
AE Services for Virtualized Environment.
#
Action
Shut down the AE Services VM, and rename the current AE Services VM.
Install the target AE Services OVA with the same configuration as the AE Services VM you
want to upgrade using System Manager or SDM client.
Restore the AE Services database that you backed up in Step 1 to the AE Services VM you
created in Step 3.
Note:
This beta patch applies to Build 9 of AE Services only, and not for Build 10. In case of
Build 10, After restore, the 7.0 upgrade script has to be applied. During the data
restore operation on the virtual machine, verify that the maximum load capacity does
not exceed the load defined in the capability and scalability matrix.
After the restore is complete, verify that the AE Services application is operational.
Optionally, if you do not require the AE Services VM you renamed in Step 2, you can delete
that VM.
January 2016
90
Procedure
1. From the AE Services Management Console, back up the server data before you install the
feature pack. See Backing up the AE Services server data on page 91.
2. Open an ssh session to the AE Services server and access an account with root privileges.
3. Download the AE Services 7.0 to the current directory.
4. From the command line, type update -u --force xxxx.zip where xxxx is the name of
the downloaded AE Services 7.0 zip file.
The system displays the feature pack ID and the RPMs contained in the package. The
system then prompts you to confirm the installation of the RPMs.
If you enter y, the installation of the feature pack proceeds. The system:
- stops AE Services, Tomcat service, and DBService.
- installs the RPMs contained in the feature pack.
- restarts AE Services, Tomcat service, and DBService.
If you enter n, the installation of the feature pack terminates.
Procedure
1. From your browser, log in to the AE Services Management Console with the appropriate
user account and password.
2. From the AE Services Console main menu, select Maintenance > Server Data > Backup.
3. If you do not want to encrypt the backup file, click Continue.
January 2016
91
Migrating AE Services
4. If you want to encrypt the backup file, perform the following steps:
a. Click the Encrypt Backup File check box, and then click Continue.
b. In the Password box, enter the password you want to use for the encrypted backup file.
The password must consist of 15 to 256 characters. This password cannot contain the
following characters: ` (single quotation), (double quotation), (apostrophe) , \ (back
slash), and % (percent).
c. Click Continue.
5. Click the Here link to download the file.
The File Download dialog box appears. You can specify the location where you want to save
the backup file. Be sure to save the backup file to a safe location that the upgrade will not
affect. For example, save the file to your local computer or another computer used for storing
backups.
The backup file is named
ServerName_AESReleaseVersion_aesvcsdbDDMMYYYY.tar.gz.enc where DDMMYYYY is
a date stamp, and enc indicates that the file is encrypted. If the file is not encrypted, enc will
not appear in the file name.
An example of an encrypted backup file is acme_r6
-2-0-11-0_aesvcsdb18062012.tar.gz.enc.
An example of an unencrypted backup file is acme_r6 -2-0-11-0_aesvcsdb18062012.tar.gz.
6. Click Save.
Note:
The tar file MD5 checksum is displayed on the web page. Use this checksum to verify
the file was downloaded correctly.
Procedure
1. From your browser, log in to AE Services Management Console.
2. From the main menu, select Maintenance > Server Data > Restore.
3. From the Restore Database Configuration page, click Browse .
January 2016
92
Upgrading the standby and active servers when Geographical Redundancy High Availability feature is enabled
Procedure
1. Using the AE Services Management Console, remove High Availability on the active server.
2. Perform a backup of the AE Services server data for the active server.
3. Delete the active and standby AE Services servers from VMware.
4. Install the new active and standby AE Services servers on VMware.
5. Restore the data for the active AE Services server.
6. Using the AE Services Management Console, configure and start High Availability on the
active server.
Note:
When the Memory/CPU of three AE Services profiles with similar CPU and Memory size
are changed, GRHA configuration is not possible. This is because GRHA cannot be
configured on profiles with differing CPU and Memory size values.
January 2016
93
January 2016
94
TSAPI, DLG,
CVLAN
Footprint
Maximum
number of
users or
agents
Maximum
BHCC
Maximum
number of
users or
agents
Maximum
BHCC
Maximum
Messages per
second (MPS)
Rate
1 CPU and 2
GB RAM
1K
20K BHCC
1K
9K BHCC
1K MPS
10K
6K BHCC
2 CPU and 2
GB RAM
2.5K
50K BHCC
2.4K
18K BHCC
1K MPS
12K
12K BHCC
4 CPU and 4
GB RAM
5K
100K BHCC
8K
36K BHCC
2K MPS
20K
24K BHCC
Procedure
1. Connect to the host or cluster using the VMware vSphere client.
2. Log in using the admin login and password.
3. Power off the virtual machine:
a. Right-click on the virtual machine name.
b. Select Power > Shut Down Guest.
c. Click Yes in the Shutdown Confirmation dialog box.
4. Right-click on the virtual machine name and select Edit Settings.
5. Change the Memory Configuration:
a. Click on the Hardware tab.
b. Click Memory.
c. Change the Memory Size to the appropriate limit.
d. (Optional) Click on the Resources tab.
e. (Optional) Select Memory,
f. (Optional) Verify the Reservation is set correctly.
g. (Optional) Uncheck the Unlimited checkbox.
h. (Optional) Verify the Limit slide is set to the same value as the Reservation.
6. Change the CPU configuration:
a. Click the Hardware tab.
b. Select CPUs.
January 2016
95
January 2016
96
Procedure
1. Open an ssh session to AE Services.
2. As the root user, type passwd root and press the ENTER key.
3. At the prompt, type the new password you are assigning.
The default Linux password policy, which is based on a US standard keyboard and the
default password limits for PAM Module Configuration, calls for a minimum of 8 characters,
with at least 1 uppercase character, 1 lowercase character, 1 alphanumeric character, and 1
special character. The following characters are not permitted: $ (dollar sign), (apostrophe),
" (quotation mark), \ (backslash), the space character, and any ASCII control-character.
4. Press the ENTER key.
5. At the prompt, type the new password again and press the ENTER key.
January 2016
97
Linux group
Linux group ID
System_Administrator
susers
555
Security_Administrator
securityadmin
505
UserSvc_Admin
usrsvc_admin
508
January 2016
98
AE Services administrative roles and access privileges (role based access control - RBAC)
Role
Linux group
Linux group ID
Auditor
users
100
Backup_Restore
backuprestore
507
Avaya_Maintenance
avayamaint
506
January 2016
99
Role
Linux group
Linux group ID
Linux Group
craft
suserssecurityadmi
nusrsvc_admin
AE Services
Available on:
AE Services using
VMware in the Virtualized
Environment
Maintenance
Networking
Status
Utilities
User Management (AE Services sets up the craft
account with access to Security)
cust
(customer account)
suserssecurityadmi
nusrsvc_admin
Available on:
January 2016
100
Linux Group
AE Services using
VMware in the Virtualized
Environment
Status
User Management (AE Services sets up the craft
account with access to Security)
Utilities
avaya
Not applicable
(customer account)
Available on:
AE Services SoftwareOnly Server only if you
installed the Avaya
Services package (csservice)
AE Services using
VMware in the Virtualized
Environment
Linux Group
craft
Access privileges
January 2016
101
Linux Group
cust
Access privileges
avaya
Not applicable
Procedure
1. Deploy the Application Enablement Services OVA.
2. Before booting the virtual machine, reduce reservations:
a. Right-click the Application Enablement Services virtual machine and select Edit
Settings.
b. In the Settings window, select the Hardware tab.
c. In the left pane, under Hardware, select Memory.
January 2016
102
d. In the right pane, change the Memory Size value from the existing value to the desired
value.
e. In the left pane, select CPUs.
f. In the right pane, adjust the Number of virtual sockets from the existing value to the
desired value.
January 2016
103
k. In the right pane, click in the MB box and change the number from the existing value to
the desired value.
January 2016
104
Procedure
1. Type http://plds.avaya.com in your web browser to go to the Avaya PLDS website.
2. Enter your Login ID and password to log on to the PLDS website.
3. In the LAC(s) field of the Quick Activation section, enter the LAC that you received in an
email message.
Note:
If you do not have an email message with your LAC, see Searching for entitlements
and make a note of the appropriate LAC from the LAC column.
Note:
The Quick Activation automatically activates all license entitlements on LAC. However,
you can remove line items or specify the number of licenses to activate from the
available licenses.
4. Enter the License Host information.
You can create a new license host or use an existing license host.
5. Click Next to validate the registration detail.
6. Enter the License Host Information.
7. Type the number of licenses that you want to activate.
January 2016
105
Procedure
1. Type http://plds.avaya.com in your web browser to go to the Avaya PLDS website.
2. Enter your Login ID and password to log on to the PLDS website.
3. Click Assets > View Entitlements.
The system displays Search Entitlements page.
4. To search license entitlements by company name, type the company name in the
%Company: field. To see a complete list of companies before you search for their
corresponding entitlements, do the following:
a. Click the magnifying glass icon.
b. Type the name or several characters of the name and a wildcard (%) character.
c. Click Search Companies.
January 2016
106
Result
The system displays all corresponding entitlement records at the bottom of the page.
January 2016
107
Note:
If you move a specified number of activated license entitlements from one host to another by
using the Rehost/Move transaction in PLDS, two new license files are generated:
One license file reduces the number of license entitlements on the License Host from
which you are moving license entitlements.
One license file increases the number of license entitlements on the License Host to which
you are moving license entitlements.
Install each of these license files on the appropriate server.
If you move all activated license entitlements, only one license file is generated. Install this new
license file on the License Host to which you are moving license entitlements. Remove the
license file from the License Host from which you are moving all license entitlements.
Procedure
1. Type http://plds.avaya.com in your web browser to go to the Avaya PLDS website.
2. Enter your Login ID and password to log on to the PLDS website.
3. Click Activation > Rehost/Move from the Home page.
4. Click View Activation Record information to find and select licenses to rehost or move.
You can search the activation records by the Company name, license host, Group name or
ID using the Search Activation Records functionality.
Note:
If you are an Avaya associate or Avaya Partner, enter the search criteria and click
Search Activation Records.
5. Select Rehost/Move for the License Host from which you are moving license entitlements.
6. In the Search License Hosts field, enter the License Host to which you are moving license
entitlements.
Alternatively, you can click Add a License Host to select an existing License Host.
7. Validate the Registration Detail, and click Next.
8. Enter the License Host Information.
9. Enter the number of Licenses to move in the QTY column field and click Next.
10. Accept the Avaya Legal Agreement.
You can search the activation records by the Company name, license host, Group name or
ID using the Search Activation Records functionality.
11. Perform the following steps to send an activation notification email message:
a. In the E-mail to field, enter the email addresses of the additional activation notification
recipients.
b. Enter the comments or special instructions in the Comments field.
January 2016
108
c. Click Finish.
12. Click View Activation Record.
The Overview tab displays a summary of the license activation information.
The Ownership tab displays the registration information.
The License/Key tab displays the license files resulting from the license activation. In
general, a single license file will be generated for each application.
January 2016
109
Related links
BIOS on page 110
VMware Tools on page 112
Timekeeping on page 112
VMware networking best practices on page 113
Storage on page 117
Thin vs. thick deployments on page 118
BIOS
For optimal performance, turn off power saving server options. See the technical data provided by
the manufacturer for your particular server regarding power saving options.
For information about how to use BIOS settings to improve the environment for latency-sensitive
workloads for an application, see the technical white paper at http://www.vmware.com/files/pdf/
techpaper/VMW-Tuning-Latency-Sensitive-Workloads.pdf.
The following sections describe the recommended BIOS settings for:
Intel Virtualization Technology
Dell PowerEdge Servers
HP ProLiant Servers
Related links
Best Practices for VMware performance and features on page 110
Intel Virtualization Technology on page 111
Dell PowerEdge Server on page 111
HP ProLiant Servers on page 112
January 2016
110
BIOS
January 2016
111
HP ProLiant Servers
The following are the recommended BIOS settings for the HP ProLiant servers:
Set the Power Regulator Mode to Static High Mode.
Disable Processor C-State Support.
Disable Processor C1E Support.
Disable QPI Power Management.
Enable Intel Turbo Boost.
Related links
BIOS on page 110
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.
Related links
Best Practices for VMware performance and features on page 110
Timekeeping
For accurate timekeeping, use the Network Time Protocol (NTP) as a time source instead of the
ESXi hypervisor.
January 2016
112
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.
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.
Related links
Best Practices for VMware performance and features on page 110
January 2016
113
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 VMkernal vNICs to be the same IP Maximum Transmission Unit (MTU).
January 2016
114
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
January 2016
115
communicate without entering the physical network. Virtual networks benefit from faster
communication speeds and lower management overhead.
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.
January 2016
116
Storage
References
Title
Link
https://downloads.avaya.com/css/P8/documents/
100154621
http://www.vmware.com/pdf/
Perf_Best_Practices_vSphere5.5.pdf
https://www.vmware.com/support/pubs/vsphere-esxivcenter-server-pubs.html
https://www.vmware.com/support/pubs/
Related links
Best Practices for VMware performance and features on page 110
Storage
The Avaya Aura AE Services virtual machine does not have a large disk footprint, nor is it
particularly disk input/output intensive. AE Services generates a fair amount of log information. As a
general rule, if a failure occurs at any of the hypervisor, network, or network-attached storage levels,
it is possible for AE Services to lose some of its logging information.
When deploying AE Services in a VMware environment, follow these storage recommendations:
Always deploy AE Services with a thickly provisioned disk. The choice between eager and lazy
zeroed makes no difference for the AE Services VM.
For best performance, use AE Services only on disks local to the ESXi host or SAN storage
devices. Do not store AE Services on an NFS storage system.
Related links
Best Practices for VMware performance and features on page 110
January 2016
117
January 2016
118
Related resources
Title
Link
January 2016
119
Related links
Best Practices for VMware performance and features on page 110
VMware vMotion
VMware uses the vMotion technology to migrate a running virtual machine from one physical server
to another physical server without incurring downtime. 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 under-performing 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.
Ensure that you have identical vSwitches. You must enable vMotion on these vSwitches.
Ensure the Port Groups are identical for vMotion.
Use a dedicated NIC to ensure the best performance.
January 2016
120
Related links
Best Practices for VMware performance and features on page 110
January 2016
121
Glossary
AFS
Authentication File System. AFS is an Avaya Web system that allows you
to create Authentication Files for secure Avaya Global Services logins for
supported non-Communication Manager Systems.
Application
Avaya Appliance
Blade
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
MAC
OVA
PLDS
Reservation
January 2016
122
RFA
RFA
Remote Feature Activation. RFA is an Avaya Web system that you use to
create Avaya License Files. These files are used to activate software
including features, capacities, releases, and offer categories. RFA also
creates Authentication Files for secure Avaya Global Services logins for
Communication Manager Systems.
SAN
Snapshot
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
virtual appliance
VM
vMotion
VMware HA
vSphere Client
January 2016
123
Index
Numerics
BIOS settings
for Dell servers ........................................................... 111
7.0
installing ........................................................................91
A
Access Security Gateway
reinstalling the default authentication file ......................83
replacing the default authentication file ........................ 83
access Solution Deployment Manager ................................ 42
access Solution Deployment Manager client .......................19
activating license entitlements ........................................... 105
active server ........................................................................ 93
add
Appliance Virtualization Platform host .......................... 49
AVP host .......................................................................49
ESXi host ................................................................49, 71
location ......................................................................... 44
virtual machine ....................................................... 62, 66
add ESXi host ...................................................................... 49
add ESXi host in vCenter .....................................................71
add location ......................................................................... 44
add location to host ..............................................................72
add virtual machine ........................................................62, 66
AE Services 7.0 using RPM patch
installing ........................................................................91
AES server
hostname ................................................................82, 83
AES software
licensed services .......................................................... 80
restarting .......................................................................81
updating ........................................................................86
Appliance Virtualization Platform host password
change ..........................................................................52
Appliance Virtualization Platform network parameters ........ 51
Appliance Virtualization Platform overview ..........................11
automatic restart
virtual machine ............................................................. 76
Avaya appliance offer .......................................................... 11
Avaya Aura application
deploy ........................................................................... 21
upgrade ........................................................................ 21
Avaya virtualization platform ................................................11
B
Backup Database page ....................................................... 91
best practices
performance and features .......................................... 110
VMware networking .................................................... 113
BIOS .................................................................................. 110
BIOS for HP servers .......................................................... 112
January 2016
C
capabilities
Solution Deployment Manager client ............................20
centralized Solution Deployment Manager .......................... 15
change
ESXi host IP address ....................................................51
change ESXi host password ................................................52
Change Gateway ................................................................. 54
change IP address for ESXi host .........................................51
Change IP FQDN .................................................................60
change Netmask for Appliance Virtualization Platform host 51
Change Network Params .....................................................51
Change Password page in WebLM ..................................... 79
changing the Virtual Machine properties ............................. 42
checklist
configuration procedures .............................................. 75
pre-deployment procedures ..........................................32
System Manager deployment .......................................36
upgrade procedures ..................................................... 90
Client ....................................................................................37
client application computer
requirements .................................................................27
client Solution Deployment Manager ................................... 14
clones
deployment ................................................................... 36
Communication Manager
requirements ...........................................................28, 30
components ......................................................................... 23
VMware ........................................................................ 23
computer requirements ........................................................27
configuration ........................................................................ 76
configuration data
customer .......................................................................25
Configuration Parameters ....................................................66
configuration procedures
checklist ........................................................................75
configure .............................................................................. 76
configuring
virtual machine automatic restart ..................................76
configuring the network settings .......................................... 76
create
virtual machine ............................................................. 58
crossover cable ....................................................................81
CTI link requirements ...........................................................30
CTI OAM home page
Maintenance page .................................................. 81, 91
customer configuration data ................................................ 25
customer VMware ................................................................13
124
Index
D
database
back up ......................................................................... 91
delays on communications channel .....................................30
delete
ESXi host ................................................................53, 72
location ......................................................................... 45
delete ESXi host .................................................................. 53
delete ESXi host in vCenter .................................................72
delete location ......................................................................45
deploy
Branch Session Manager ............................................. 58
Communication Manager ............................................. 58
Session Manager ..........................................................58
System Manager .......................................................... 58
Utility Services .............................................................. 58
deploy application ................................................................ 43
deploy Avaya Aura 7.0 application ...................................... 58
Deploying an OVA file
utility services ............................................................... 56
deploying copies .................................................................. 36
deployment .................................................................... 37, 76
thick ............................................................................ 118
thin ..............................................................................118
deployment guidelines ......................................................... 23
deploy OVA ..........................................................................58
deploy System Manager ...................................................... 36
documentation ....................................................................... 7
downloading software
using PLDS ...................................................................33
download software ...............................................................56
Dual NIC configuration guidelines ....................................... 29
duplex settings for AES ....................................................... 30
DVD
new installation ............................................................. 24
E
edit
ESXi host ................................................................50, 72
location ......................................................................... 44
virtual machine ............................................................. 60
edit ESXi host ...................................................................... 50
edit ESXi host in vCenter .....................................................72
Edit Host .............................................................................. 53
edit location ..........................................................................44
Edit Location ........................................................................ 48
Edit vCenter ......................................................................... 73
edit virtual machine ..............................................................60
error messages
WebLM ......................................................................... 82
ESXi host
add ................................................................................49
add location .................................................................. 72
delete ............................................................................53
edit ................................................................................50
January 2016
manage .........................................................................72
nonmanage ...................................................................72
remove location ............................................................ 72
ESXi host Gateway
change ..........................................................................51
edit ................................................................................51
ESXi host in vCenter
add ................................................................................71
delete ............................................................................72
edit ................................................................................72
remove ..........................................................................72
ESXi host IP address
change ..........................................................................51
edit ................................................................................51
ESXi host map to unknown location .................................... 53
ESXi host password
change ..........................................................................52
Ethernet interfaces
on SAMP ...................................................................... 81
F
features best practices .......................................................110
field descriptions
change password ......................................................... 55
Edit Host ....................................................................... 53
Edit Location .................................................................48
Hosts ............................................................................ 45
Locations ...................................................................... 45
Map vCenter ................................................................. 73
New Host ...................................................................... 53
New Location ................................................................48
Virtual Machines ........................................................... 45
VM Deployment ...................................................... 62, 66
file deployment .....................................................................37
flexible footprint ....................................................................94
configuring hardware resources ................................... 94
footprint flexibility ................................................................. 94
G
GRHA .................................................................................. 93
guidelines
deployment ................................................................... 23
H
hardware resources
configuring for flexible footprint .....................................94
hardware supported
System Manager
supported servers ..................................................29
High Availability ................................................................. 120
host
monitoring .....................................................................70
Host
125
Index
Host (continued)
update ...........................................................................55
Hosts ....................................................................................45
I
install
Application Enablement Services ................................. 17
Avaya Aura applications ............................................... 17
Avaya Aura Media Server .............................................17
Branch Session Manager ............................................. 17
Communication Manager ............................................. 17
Engagement Deployment Platform ...............................17
SAL ...............................................................................17
SDM ..............................................................................17
Session Manager ..........................................................17
Solution Deployment manager client ............................17
System Manager .......................................................... 17
WebLM ......................................................................... 17
installation
license file .....................................................................80
updates and patches .................................................... 86
Installed Patches field descriptions ......................................68
installing AE Services 7.0 using RPM patch ........................91
installing AES virtual appliance OVA without vCenter ......... 40
installing AES virtual appliance OVA with vCenter .............. 38
Install System Manager patch ............................................. 69
Intel Virtualization Technology ...........................................111
intended audience ................................................................. 7
interface speed for AES .......................................................30
L
laptop computer
connecting to server ..................................................... 81
licensed features
specific features
product license ...................................................... 78
Licensed Products page for Application Enablement .......... 80
license entitlements
activating .................................................................... 105
searching for ...............................................................106
license file for AES
installing ........................................................................80
removing an existing file ............................................... 79
verify settings ................................................................80
licenses
AE Services .................................................................. 80
Life cycle management ........................................................43
limited warranty
standard warranty ...........................................................9
Linux commands
swversion ......................................................................86
location
add ................................................................................44
delete ............................................................................45
edit ................................................................................44
January 2016
view .............................................................................. 43
Locations ............................................................................. 45
log in
as user with root privileges ........................................... 81
to OAM ................................................................... 79, 84
to WebLM ..................................................................... 82
WebLM ......................................................................... 83
M
map ESXi host to unknown location .................................... 53
Map vCenter .................................................................. 71, 73
Map vCentre ........................................................................ 73
media server requirements ............................................ 28, 30
monitoring
host ...............................................................................70
virtual machine ............................................................. 70
VM ................................................................................ 70
N
network
interface speed and duplex settings ............................. 30
latency requirements .................................................... 30
Network interfaces ............................................................... 28
Network interfaces, required settings .................................. 30
network parameters
change ..........................................................................54
network settings ...................................................................76
New Host ............................................................................. 53
New Location ....................................................................... 48
New vCenter ........................................................................ 73
NIC
Ethernet interface for technician ...................................81
NIC, recommended settings ................................................ 30
NTP time source ................................................................ 112
O
OAM
home page ........................................................79, 81, 84
restarting AE Services .................................................. 81
opening an ssh session ....................................................... 88
OVA ..................................................................................... 37
verifying on Linux-based computer ...............................34
verifying on Windows-based computer .........................34
overview ...............................................................................13
P
packet delivery time ............................................................. 30
password
change ..........................................................................55
password change
Appliance Virtualization Platform host .......................... 52
ESXi host ......................................................................52
126
Index
Password policy
Linux ............................................................................. 97
patches for software, see updates .......................................86
performance best practices ............................................... 110
periodic spiked delays ......................................................... 30
ping, measure round-trip packet delivery time .....................30
PLDS ................................................................................... 32
downloading software ...................................................33
pre-deployment procedures
checklist ........................................................................32
prerequisites
installation .....................................................................24
upgrades .......................................................................91
purposeinstallationconfigurationadministrationtroubleshooting
maintenance .......................................................................... 7
R
reducing reservations
Communication Manager ........................................... 102
reestablish
connection .................................................................... 70
Reestablish Connection .......................................................45
regenerating a license file ..................................................109
registering ............................................................................ 32
rehosting ............................................................................ 107
related documentation ........................................................... 7
remove ESXi host ................................................................ 72
remove location from host ................................................... 72
removing an existing license file .......................................... 79
Removing the AE Services license file ................................ 83
requirements
client application computer ........................................... 27
license file .....................................................................80
media server ...........................................................28, 30
software ........................................................................ 27
virtual machine storage .............................................. 117
VM resources ............................................................... 26
reservations
reducing for Communication Manager ....................... 102
resource requirements .........................................................26
resources
server ............................................................................24
restart
virtual machine ............................................................. 62
restarting AE Services ......................................................... 81
restart virtual machine from SDM ........................................ 62
restoring the database ......................................................... 92
RPMs
installed on server ........................................................ 86
location ......................................................................... 86
S
SAL Gateway .......................................................................31
SDM ...............................................................................10, 37
installation .....................................................................17
January 2016
T
technician
installation prerequisites ............................................... 24
reserved interface .........................................................81
thick deployment ................................................................118
thin deployment ................................................................. 118
timekeeping ....................................................................... 112
training ................................................................................... 8
127
Index
W
WebLM
error messages .............................................................82
logging in ................................................................ 82, 83
WebLM server
connecting .................................................................... 78
V
vCentre ................................................................................ 73
add ................................................................................73
edit ................................................................................73
videos .................................................................................... 8
view
location ......................................................................... 43
view location ........................................................................ 43
Virtualized Environment .......................................................13
virtual machine
automatic restart configuration ..................................... 76
create ............................................................................58
edit ................................................................................60
monitoring .....................................................................70
restart ........................................................................... 62
start ...............................................................................61
stop ...............................................................................61
Virtual machine management .............................................. 43
Virtual Machine properies
changing ....................................................................... 42
Virtualized Environment ................................................42
Virtual Machines .................................................................. 45
virtual machine storage ......................................................117
VM connection reestablish ...................................................70
VM Deployment ............................................................. 62, 66
vMotion .............................................................................. 120
VM resource requirements .................................................. 26
VMware ..............................................................................120
VMware networking
best practices ............................................................. 113
VMware software
supported ......................................................................27
VMware Tools ....................................................................112
January 2016
128