Implementing and Administering

Services-VM on Avaya Aura® System

Platform

Release 4.0
Issue 2
February 2018
© 2013-2018, Avaya Inc.
All Rights Reserved.
Notice
While reasonable efforts have been made to ensure that the
information in this document is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves
the right to make changes and corrections to the information in this
document without the obligation to notify any person or organization
of such changes.
Documentation disclaimer
“Documentation” means information published in varying mediums
which may include product information, operating instructions and
performance specifications that are generally made available to users
of products. Documentation does not include marketing materials.
Avaya shall not be responsible for any modifications, additions, or
deletions to the original published version of Documentation unless
such modifications, additions, or deletions were performed by or on
the express behalf of Avaya. End User agrees to indemnify and hold
harmless Avaya, Avaya's agents, servants and employees against all
claims, lawsuits, demands and judgments arising out of, or in
connection with, subsequent modifications, additions or deletions to
this documentation, to the extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked
websites referenced within this site or Documentation provided by
Avaya. Avaya is not responsible for the accuracy of any information,
statement or content provided on these sites and does not
necessarily endorse the products, services, or information described
or offered within them. Avaya does not guarantee that these links will
work all the time and has no control over the availability of the linked
pages.
Warranty
Avaya provides a limited warranty on Avaya hardware and software.
Refer to your sales agreement to establish the terms of the limited
warranty. In addition, Avaya’s standard warranty language, as well as
information regarding support for this product while under warranty is
available to Avaya customers and other parties through the Avaya
Support website: https://support.avaya.com/helpcenter/
getGenericDetails?detailId=C20091120112456651010 under the link
“Warranty & Product Lifecycle” or such successor site as designated
by Avaya. Please note that if You acquired the product(s) from an
authorized Avaya Channel Partner outside of the United States and
Canada, the warranty is provided to You by said Avaya Channel
Partner and not by Avaya.
“Hosted Service” means an Avaya hosted service subscription that
You acquire from either Avaya or an authorized Avaya Channel
Partner (as applicable) and which is described further in Hosted SAS
or other service description documentation regarding the applicable
hosted service. If You purchase a Hosted Service subscription, the
foregoing limited warranty may not apply but You may be entitled to
support services in connection with the Hosted Service as described
further in your service description documents for the applicable
Hosted Service. Contact Avaya or Avaya Channel Partner (as
applicable) for more information.
Hosted Service
THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA
HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA
CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE
FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA
WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO UNDER
THE LINK “Avaya Terms of Use for Hosted Services” OR SUCH
SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE
APPLICABLE TO ANYONE WHO ACCESSES OR USES THE
HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED
SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON
BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE
DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY
AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF
YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A
COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT
YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE
TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF
YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU
MUST NOT ACCESS OR USE THE HOSTED SERVICE OR
AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED
SERVICE.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO,
UNDER THE LINK “AVAYA SOFTWARE LICENSE TERMS (Avaya
Products)” OR SUCH SUCCESSOR SITE AS DESIGNATED BY
AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS,
USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED
FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA
CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL
AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER.
UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING,
AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE
WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA
AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA
RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU
AND ANYONE ELSE USING OR SELLING THE SOFTWARE
WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR
USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,
YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM
YOU ARE INSTALLING, DOWNLOADING OR USING THE
SOFTWARE (HEREINAFTER REFERRED TO
INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO
THESE TERMS AND CONDITIONS AND CREATE A BINDING
CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
APPLICABLE AVAYA AFFILIATE (“AVAYA”).
Avaya grants You a license within the scope of the license types
described below, with the exception of Heritage Nortel Software, for
which the scope of the license is detailed below. Where the order
documentation does not expressly identify a license type, the
applicable license will be a Designated System License as set forth
below in the Designated System(s) License (DS) section as
applicable. 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 set of Designated
Processors that hosts (physically or virtually) a software application
to be accessed by multiple users. “Instance” means a single copy of
the Software executing at a particular time: (i) on one physical
machine; or (ii) on one deployed software virtual machine (“VM”) or
similar deployment.
License types
Designated System(s) License (DS). End User may install and use
each copy or an Instance of the Software only: 1) on a number of
Designated Processors up to the number indicated in the order; or 2)
up to the number of Instances of the Software as indicated in the
order, Documentation, or as authorized by Avaya in writing. 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.
Cluster License (CL). End User may install and use each copy or an
Instance of the Software only up to the number of Clusters as
indicated on the order with a default of one (1) Cluster if not stated.
“Cluster” means a group of Servers and other resources that act as a
single system.
Enterprise License (EN). End User may install and use each copy or THE AVAYA CHANNEL PARTNER IS REQUIRED TO
an Instance of the Software only for enterprise-wide use of an INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE
unlimited number of Instances of the Software as indicated on the AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’S EXPENSE,
order or as authorized by Avaya in writing. DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER.
CPU License (CP). End User may install and use each copy or Preventing Toll Fraud
Instance of the Software on a number of Servers up to the number
“Toll Fraud” is the unauthorized use of your telecommunications
indicated in the order provided that the performance capacity of the
system by an unauthorized party (for example, a person who is not a
Server(s) does not exceed the performance capacity specified for the
corporate employee, agent, subcontractor, or is not working on your
Software. End User may not re-install or operate the Software on
company's behalf). Be aware that there can be a risk of Toll Fraud
Server(s) with a larger performance capacity without Avaya’s prior
associated with your system and that, if Toll Fraud occurs, it can
consent and payment of an upgrade fee.
result in substantial additional charges for your telecommunications
Named User License (NU). You may: (i) install and use each copy or services.
Instance of the Software on a single Designated Processor or Server
Avaya Toll Fraud intervention
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 If You suspect that You are being victimized by Toll Fraud and You
authorized Named Users access and use the Software. “Named need technical assistance or support, call Technical Service Center
User”, means a user or device that has been expressly authorized by Toll Fraud Intervention Hotline at +1-800-643-2353 for the United
Avaya to access and use the Software. At Avaya’s sole discretion, a States and Canada. For additional support telephone numbers, see
“Named User” may be, without limitation, designated by name, the Avaya Support website: https://support.avaya.com or such
corporate function (e.g., webmaster or helpdesk), an e-mail or voice successor site as designated by Avaya.
mail account in the name of a person or corporate function, or a
directory entry in the administrative database utilized by the Software Trademarks
that permits one user to interface with the Software. The trademarks, logos and service marks (“Marks”) displayed in this
Shrinkwrap License (SR). You may install and use the Software in site, the Documentation, Hosted Service(s), and product(s) provided
accordance with the terms and conditions of the applicable license by Avaya are the registered or unregistered Marks of Avaya, its
agreements, such as “shrinkwrap” or “clickthrough” license affiliates, its licensors, its suppliers, or other third parties. Users are
accompanying or applicable to the Software (“Shrinkwrap License”). not permitted to use such Marks without prior written consent from
Avaya or such third party which may own the Mark. Nothing
Copyright contained in this site, the Documentation, Hosted Service(s) and
Except where expressly stated otherwise, no use should be made of product(s) should be construed as granting, by implication, estoppel,
materials on this site, the Documentation, Software, Hosted Service, or otherwise, any license or right in and to the Marks without the
or hardware provided by Avaya. All content on this site, the express written permission of Avaya or the applicable third party.
documentation, Hosted Service, and the product provided by Avaya Avaya is a registered trademark of Avaya Inc.
including the selection, arrangement and design of the content is
owned either by Avaya or its licensors and is protected by copyright All non-Avaya trademarks are the property of their respective owners.
and other intellectual property laws including the sui generis rights Linux® is the registered trademark of Linus Torvalds in the U.S. and
relating to the protection of databases. You may not modify, copy, other countries.
reproduce, republish, upload, post, transmit or distribute in any way Downloading Documentation
any content, in whole or in part, including any code and software
unless expressly authorized by Avaya. Unauthorized reproduction, For the most current versions of Documentation, see the Avaya
transmission, dissemination, storage, and or use without the express Support website: https://support.avaya.com, or such successor site
written consent of Avaya can be a criminal, as well as a civil offense as designated by Avaya.
under the applicable law. Contact Avaya Support
Third Party Components See the Avaya Support website: https://support.avaya.com for
“Third Party Components” mean certain software programs or product or Hosted Service notices and articles, or to report a problem
portions thereof included in the Software or Hosted Service may with your Avaya product or Hosted Service. For a list of support
contain software (including open source software) distributed under telephone numbers and contact addresses, go to the Avaya Support
third party agreements (“Third Party Components”), which contain website: https://support.avaya.com (or such successor site as
terms regarding the rights to use certain portions of the Software designated by Avaya), scroll to the bottom of the page, and select
(“Third Party Terms”). As required, information regarding distributed Contact Avaya Support.
Linux OS source code (for those products that have distributed Linux
OS source code) and identifying the copyright holders of the Third
Party Components and the Third Party Terms that apply is available
in the products, Documentation or on Avaya’s website at: https://
support.avaya.com/Copyright or such successor site as designated
by Avaya. The open source software license terms provided as Third
Party Terms are consistent with the license rights granted in these
Software License Terms, and may contain additional rights benefiting
You, such as modification and distribution of the open source
software. The Third Party Terms shall take precedence over these
Software License Terms, solely with respect to the applicable Third
Party Components to the extent that these Software License Terms
impose greater restrictions on You than the applicable Third Party
Terms.
Service Provider
THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’S
HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT
OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS
SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE
PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY FROM
THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL PARTNER’S
HOSTING OF AVAYA PRODUCTS MUST BE AUTHORIZED IN
WRITING BY AVAYA AND IF THOSE HOSTED PRODUCTS USE
OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING
BUT NOT LIMITED TO MICROSOFT SOFTWARE OR CODECS,
 Contents

Chapter 1: Introduction............................................................................................................ 5
Purpose of the document......................................................................................................... 5
Prerequisites for using the document........................................................................................ 5
Change history........................................................................................................................ 6
New in this release.................................................................................................................. 6
Chapter 2: Services-VM overview........................................................................................... 7
Services-VM resources............................................................................................................ 8
Use of SAL Gateway on Services-VM....................................................................................... 9
Supported load for SAL Gateway on Services-VM...................................................................... 9
Chapter 3: Implementing Services-VM................................................................................. 10
Services-VM 4.0 implementation process................................................................................ 10
Upgrading Services-VM on System Platform............................................................................ 11
Chapter 4: Postupgrade verification and configuration...................................................... 15
Postupgrade tasks checklist................................................................................................... 15
Verifying the Services-VM implementation............................................................................... 17
Password complexity rules..................................................................................................... 18
Chapter 5: Administering Services-VM through the System Platform web console........ 19
Services-VM administration overview...................................................................................... 19
Modifying Services-VM configuration...................................................................................... 19
Enabling Services-VM........................................................................................................... 21
Disabling Services-VM........................................................................................................... 21
Checking application states.................................................................................................... 22
Checking version information for Services-VM......................................................................... 23
Rebooting Services-VM from the System Platform web console................................................ 23
Managing Services-VM patches............................................................................................. 24
Performing backup and restore of Services-VM....................................................................... 24
Chapter 6: Managing SAL Gateway through the System Platform web console............. 26
SAL Gateway management through the System Platform web console...................................... 26
Enabling SAL Gateway.......................................................................................................... 26
Disabling SAL Gateway......................................................................................................... 27
Launching the SAL Gateway user interface through System Platform........................................ 28
Chapter 7: Configuring SNMP............................................................................................... 30
SNMP configuration overview................................................................................................. 30
Configuring SNMP for Services-VM........................................................................................ 30
Chapter 8: Resources............................................................................................................. 32
Documentation...................................................................................................................... 32
Finding documents on the Avaya Support website............................................................. 32
Viewing Avaya Mentor videos................................................................................................. 33
Support................................................................................................................................ 33

February 2018 Implementing and Administering Services-VM 4

Comments on this document? infodev@avaya.com
Chapter 1: Introduction

Purpose of the document

This document provides information about the following:
• Introduction to Services Virtual Machine (Services-VM)
• Upgrade to Services-VM 4.0 on Avaya Aura® System Platform
• Basic administration of Services-VM on Avaya Aura® System Platform
The scope of this document is limited to describing the implementation and administration of
Services-VM. Although the document refers to System Platform and Avaya Diagnostic Server with
the SAL Gateway component, the document is not a reference point for implementation and
administration of System Platform, Avaya Diagnostic Server, or SAL Gateway. Always use the
appropriate product documentation to get information about System Platform and SAL Gateway.
This document is intended for people who implement and maintain Services-VM on System
Platform.
Note:
The screen shots used in the document are representative examples of the System Platform
user interface and might change in future releases.

Prerequisites for using the document

You must be familiar with the System Platform web console as this document refers to the System
Platform web console for administering Services-VM. For more information about the System
Platform web console, see Administering Avaya Aura® System Platform.
Ensure that you have a valid user ID with administrator-level or advanced administrator-level
permission to log on to the System Platform web console. To know about user roles and access
restrictions, see Administering Avaya Aura® System Platform.

February 2018 Implementing and Administering Services-VM 5

Comments on this document? infodev@avaya.com
Introduction

Change history

Issue Date Summary of changes

Release 3.0, July 2017 The first issue of the document in this release.
Issue 1
Release 3.0, February 2018 Updated the topics: New in this release on page 6 and Managing
Issue 2 Services-VM patches on page 24.

New in this release

Services-VM Release 4.0 is built on the previous release and has the following new features and
enhancements.
Avaya Diagnostic Server 3.0
Services-VM Release 4.0 comes with Avaya Diagnostic Server Release 3.0. Avaya Diagnostic
Server 3.0 on Services-VM 4.0 provides only the SAL Gateway component. Services-VM 4.0 does
not contain the SLA Mon™ Server component of Avaya Diagnostic Server.
For more information about Avaya Diagnostic Server 3.0, see the Avaya Diagnostic Server
documentation for Release 3.0 available on the Avaya Support website at http://
support.avaya.com/.

Upgrade support from all earlier Services-VM releases

• Services-VM Release 4.0 supports a direct template upgrade from all earlier releases. You
can upgrade to Services-VM 4.0 on System Platform 6.2 and later releases.
• On your first login after the upgrade, the system prompts you to change the default root
password.
• After you change the root password, the system might prompt you to enable or disable the
automatic software upgrade feature.
• On your first login after the upgrade, the system might prompt you to update the SMTP
details, if they are not already configured. Also update the administrator email ID on SMTP
Configuration page of the SAL Gateway.
Operating system upgrade
In Release 4.0, the operating system is upgraded to 64-bit CentOS version 6.9.
OpenJDK JRE support
In Release 4.0, Services-VM supports OpenJDK JRE version 1.8.

February 2018 Implementing and Administering Services-VM 6

Comments on this document? infodev@avaya.com
Chapter 2: Services-VM overview

In Avaya Aura® System Platform 6.0 and earlier releases, SAL Gateway was a coresident software
on the Console Domain (cdom). In System Platform 6.2 and later releases, an independent virtual
machine, Services Virtual Machine (Services-VM), on System Platform hosts SAL Gateway. This
deployment model eases upgrades of SAL Gateway on System Platform and provides users with
faster access to the benefits from enhancements and maintenance releases.
Services-VM provides a platform to host tools and applications that provide the customer a better
service experience.
Services-VM 4.0 comes with Avaya Diagnostic Server 3.0 that provides the remote access
capabilities of SAL Gateway.
Note:
Services-VM is not a solution template and is separate from a solution template installed on
System Platform. Services-VM is an independent domain on System Platform, similar to
Console Domain. However, you must maintain Services-VM in the same way as a solution
template.

February 2018 Implementing and Administering Services-VM 7

Comments on this document? infodev@avaya.com
Services-VM overview

Figure 1: Structure of Services-VM on System Platform

Related links
Services-VM resources on page 8
Use of SAL Gateway on Services-VM on page 9
Supported load for SAL Gateway on Services-VM on page 9

Services-VM resources
This Services-VM release supports two configurations, small and medium. System Platform
allocates the following resources to Services-VM based on the supported configuration. This
section is for your information only. You cannot configure or change the values.
Resource Small Medium
Virtual CPU core 1 1
CPU speed 2.3 GHz 2.3 GHz
Total memory 512 MB 1 GB
Total disk space 4 GB 10 GB
Table continues…

February 2018 Implementing and Administering Services-VM 8

Comments on this document? infodev@avaya.com
 Use of SAL Gateway on Services-VM

Resource Small Medium

Virtual NIC 1 1
Supported hardware • Avaya Common Server R1 Avaya Common Server R2 and
R3
• S8300D, S8300E, S8510, and
S8800

Related links
Services-VM overview on page 7

Use of SAL Gateway on Services-VM

You can use SAL Gateway residing on Services-VM to remotely monitor and gain access to
multiple devices, also known as managed elements. SAL Gateway can service managed
elements irrespective of whether the managed elements are located on the same server as SAL
Gateway.
Limit the use of the integrated SAL Gateway to support a maximum of 15 managed elements. To
exceed this guideline, you must implement a standalone SAL Gateway to support the overage.
The limit of 15 managed elements is based on normal alarm frequency and network conditions.
Note:
For more information about SAL Gateway, see Administering Avaya Diagnostic Server SAL
Gateway.
Related links
Services-VM overview on page 7

Supported load for SAL Gateway on Services-VM

Maximum supported managed elements 15
Maximum simultaneous remote connections 6
Maximum alarms per minute 20

Important:
To ensure stable and predictable performance, do not exceed the limit of 15 managed
elements. To support more than 15 managed elements, you must implement a standalone
SAL Gateway.
Related links
Services-VM overview on page 7

February 2018 Implementing and Administering Services-VM 9

Comments on this document? infodev@avaya.com
Chapter 3: Implementing Services-VM

Services-VM 4.0 implementation process

You can do a direct template upgrade to Services-VM 4.0 from all earlier Services-VM releases.
System Platform 6.2 and later releases support upgrade to Services-VM 4.0.
The following upgrade paths to Services-VM 4.0 are available:
Hardware type Upgrade path
Avaya Common Server Release 3 Template upgrade to Services-VM 4.0 from:
• Services-VM 2.0.0.9
• Services-VM 3.0
Avaya Common Server Release 3 supports the medium
configuration of Services-VM 4.0.
Avaya Common Server Release 2 Template upgrade to Services-VM 4.0 from:
• Services-VM 2.0
• Services-VM 2.0.0.9
• Services-VM 3.0
Avaya Common Server Release 2 supports the medium
configuration of Services-VM 4.0.
Avaya Common Server Release 1, S8300D, Template upgrade to Services-VM 4.0 from:
S8300E, S8510, and S8800
• Services-VM 1.0
• Services-VM 2.0
• Services-VM 3.0
Avaya Common Server Release 1 and other hardware
mentioned here support the small configuration of
Services-VM 4.0.

Important:
Services-VM 4.0 comes with only the SAL Gateway component of Avaya Diagnostic Server
3.0. If you have Services-VM 3.0 with the SLA Mon server, a template upgrade to Services-
VM 4.0 does not retain the SLA Mon data. To prevent data loss, take a backup of the Avaya
Diagnostic Server components before the template upgrade.

February 2018 Implementing and Administering Services-VM 10

Comments on this document? infodev@avaya.com
 Upgrading Services-VM on System Platform

Upgrading Services-VM on System Platform

About this task
Services-VM 4.0 supports direct template upgrade from all earlier releases.
The Services-VM upgrade procedure is similar to the upgrade procedure of other solution
templates on System Platform. For more information about upgrading a solution template, see
Upgrading Avaya Aura® System Platform. This procedure only describes the steps that you must
do differently for Services-VM from a template upgrade.
Before you begin
• As a safety measure, take a backup of the Avaya Diagnostic Server components on
Services-VM. Consider one of the following options:
- Use the integrated backup and restore features on the System Platform web console for
backup.
- Use the backup features of Avaya Diagnostic Server components, and save the backup
archives on a remote server. The template upgrade does not retain the backup archives
that you save locally on Services-VM.
- At the minimum, through the SAL Gateway user interface, export the managed element
data to a csv file.
Note:
If you have SLA Mon server on Services-VM 3.0, a template upgrade to Services-VM 4.0
does not retain the SLA Mon server component and its data.
• Ensure that the existing SAL Gateway version on Services-VM is not using Policy Server.
Otherwise, upgrade to Services-VM 4.0 is rolled back. Through the SAL Gateway user
interface, disable the use of Policy Server.
Procedure
1. Log on to the System Platform web console as an administrator.
2. If you have an ISO image for the Services-VM upgrade and have physical access to the
System Platform server, write the ISO image to a DVD, and insert the DVD in the server
CD-ROM or DVD drive. Proceed to Step 4.
Important:
The preferred method for upgrading Services-VM is to write the ISO image to a DVD
and then choosing the CD/DVD option to install the template.
3. If you have an ISO image but do not have physical access to the server, do the following:
a. Transfer the Services-VM image file to the cdom virtual machine.
You can use the scp command to copy the file from a Linux system to the remote
virtual machine. To copy the file from a Windows system, you can use WinSCP or a
similar file transfer tool.
b. Establish an SSH session to cdom as the root user.

February 2018 Implementing and Administering Services-VM 11

Comments on this document? infodev@avaya.com
Implementing Services-VM

c. Create the mount directory for the image file of Services-VM.

For example:
mkdir /mnt/Services_VM
d. Change the directory to the location where you copied the image file.
e. Mount the image file on the mount directory that you created earlier.
For example:
mount -o loop Services_VM-4.0.0.0.X.iso /mnt/Services_VM
f. Copy the folder where you mounted the ISO image to the /vsp-template folder.
For example:
cp -r /mnt/Services_VM /vsp-template/
g. List the files in the /vsp-template/Services_VM folder to check that the copy
operation is successful.
The following is a sample output of the ls command for the /vsp-template/
Services_VM/ folder:
ls -l /vsp-template/Services_VM/
total 839000
-r-------- 1 tomcat tomcat 5811 Aug 27 18:20 backup_sdom.sh
-r-------- 1 tomcat tomcat 2507 Aug 27 18:20 index.html
-r-------- 1 tomcat tomcat 12090 Aug 27 18:20 patch_sdom.sh
-r-------- 1 tomcat tomcat 4084 Aug 27 18:20 resizeVM.sh
-r-------- 1 tomcat tomcat 858218207 Aug 27 18:21 services_vm.gz
-r-------- 1 tomcat tomcat 12316 Aug 27 18:21 Services_VM_Medium.ovf
-r-------- 1 tomcat tomcat 522 Aug 27 18:21 Services_VM.mf
-r-------- 1 tomcat tomcat 12270 Aug 27 18:21 Services_VM_Small.ovf
-r-------- 1 tomcat tomcat 4448 Aug 27 18:21 srvcs-vm-srvc-control.sh
-r-------- 1 tomcat tomcat 2673 Aug 27 18:21 versioninfo_sdom.sh

h. Unmount the image file.

For example:
umount /mnt/Services_VM
i. Remove the folder that you created for mounting the ISO image.
For example:
rm -rf /mnt/Services_VM
4. In the left navigation pane of the System Platform web console, click Virtual Machine
Management > Templates.
The Search Local and Remote Template page displays the Services-VM version and the
solutions templates installed on System Platform.
5. Click Upgrade next to the installed Services-VM version.

February 2018 Implementing and Administering Services-VM 12

Comments on this document? infodev@avaya.com
 Upgrading Services-VM on System Platform

6. In the Install Template From field, select the location from where the system must install
the Services-VM upgrade. Follow the same steps as you do to search and select a
template for upgrade in System Platform.
If you copied the ISO image file for Services-VM to the server, select SP Server.
If you wrote the ISO image to a DVD and inserted the DVD to the server CD or DVD drive,
select SP CD/DVD.
7. Select the appropriate Open Virtualization Format (OVF) file for Services-VM from the
following according to the hardware type:

Hardware type OVF file

Avaya Common Server R1, S8300D, S8300E, S8510, and Services_VM_Small.ovf
S8800
Avaya Common Server R2 Services_VM_Medium.ovf
Avaya Common Server R3 Services_VM_Medium.ovf

The Template Details page displays the version and additional information about the
current and the new template for Services-VM.
8. Select the check box next to the Normal configuration, and click Install.
The Template Network Configuration page displays the general network settings for
Services-VM.
9. Click Save.
The Template Details page displays the default values for Services-VM.
10. If required, change the default values.
11. Click Install.
The upgrade process starts and the Template Installation page displays the progress of the
upgrade.
Note:
As part of the upgrade process, the system stops Services-VM at this stage, which
results in termination of the SAL Gateway services running on Services-VM. The
temporary termination of the services causes termination of all established connections
to SAL Gateway and might result in product alarms being missed. If you have
connected to the System Platform web console remotely through the SAL Gateway
that is on board, the system logs you off from the web console at this stage. The
Services-VM upgrade process continues in the background until all tasks in the
upgrade process are complete.
Note:
The first task in the process, downloading the disk image for Services-VM, might take
varied amount of time to complete. The completion time depends on the location of the

February 2018 Implementing and Administering Services-VM 13

Comments on this document? infodev@avaya.com
Implementing Services-VM

server from which you download the template and the network quality, such as
bandwidth and traffic. The other tasks take approximately 20 minutes to complete.
12. Log on to the System Platform web console to check the progress of the upgrade.
After the completion of the upgrade tasks, the Template Installation page displays two
buttons, Commit Installation and Rollback Installation.
13. Verify the upgrade, and perform one of the following actions:
• Click Commit Installation to apply the newly upgraded Services-VM.
• Click Rollback Installation to cancel the upgrade process and return to the previous
version of Services-VM.
Important:
You must log on to the web console within 4 hours of the completion of the upgrade
tasks and commit the upgrade process. Otherwise, the system cancels the upgrade
process and automatically rolls back to the previous version of Services-VM.
Related links
Verifying the Services-VM implementation on page 17

February 2018 Implementing and Administering Services-VM 14

Comments on this document? infodev@avaya.com
Chapter 4: Postupgrade verification and
configuration
Postupgrade tasks checklist
After a template upgrade, complete the following tasks to ensure that upgraded Services-VM is
functional.
No. Task
1 Verify that the Services-VM upgrade
operation is successful.
2 If SAL Gateway is disabled or the
application state is not Running,
enable SAL Gateway through the
System Platform web console.
3 Log on to Services-VM through an
SSH session as root, and when the
system prompts, change the root
password.
February 2018 Implementing and Administering Services-VM
Comments on this document? infodev@avaya.com
Description
See Verifying the Services-VM
implementation on page 17.
See Enabling SAL Gateway on page 26.
On your first login after the upgrade, the system
prompts you to change the default root
password.
Adhere to the password complexity rules while
you set up a new password. See Password
complexity rules on page 18.
Note:
On System Platform 6.4, the default root
password on Services-VM is the same as
that on CDOM. On System Platform
version earlier than 6.4, the root password
on the upgraded Services-VM is the
default password for Services-VM. The
default password is available in the
description section of Services-VM on
PLDS.
Note:
The Services-VM root password expires
after every 90 days. Remember to set up a
Table continues…
15
Postupgrade verification and configuration

No. Task Description

new password before the existing

4 On your first login, if the system
prompts you, enable or disable the
automatic software upgrade feature.
5 When you upgrade Services-VM from
1.0 or 2.0.0.9 to 4.0, update the
administrator email ID on SAL
Gateway.
password expires.
After you change the default root password, the
system might prompt you to enable or disable
the automatic software upgrade feature on SAL
Gateway. The system prompts this question
only if the automatic software feature is
currently disabled on SAL Gateway.
If you enable the feature, SAL Gateway
automatically downloads software updates,
including major, minor, and service pack
releases, and installs the downloaded software
packages after a grace period. If you keep the
feature disabled, SAL Gateway still downloads
the updates. However, you must install the
software updates manually.
Type one of the following responses at the
system prompt:
• y: To enable the feature.
• n: To disable the feature.
This is a one time question. By default, the
answer is Yes.
On the SMTP Configuration page of the SAL
Gateway web interface, update the
administrator email ID. Also ensure that values
in other required fields on the page are
accurate.

Note:
If you are upgrading Services-VM from 2.0
or 3.0, ensure that all details on the SMTP
Configuration page on are accurate.

Note:
An upgrade to Services-VM 4.0 does not retain the base Services-VM system configuration.
For example, if a user account is added on the base Services-VM version, that account will
not be available in Services-VM 4.0. The upgrade operation carries forward only the SAL
Gateway configuration data from the base Services-VM version.

February 2018 Implementing and Administering Services-VM 16

Comments on this document? infodev@avaya.com
 Verifying the Services-VM implementation

Verifying the Services-VM implementation

About this task
After upgrading Services-VM, use the following procedure to ensure that Services-VM is
functional.
Procedure
1. On the System Platform web console, click Virtual Machine Management > Manage.
2. On the Virtual Machine List page, verify the following:
• services_vm is present in the list of virtual machines.
• The state for services_vm is Running.
• If SAL Gateway is enabled on Services-VM, the application state for services_vm is
Running.
Note:
After a template upgrade from Services-VM 2.0.0.9 to 4.0, SAL Gateway remains in
the disabled state and the application state for services_vm remains Stopped.
3. If SAL Gateway is disabled or the application state is not Running, enable SAL Gateway
through the System Platform web console.
If SAL Gateway was disabled on Services-VM before the upgrade, SAL Gateway remains
disabled after the upgrade. You cannot open the SAL Gateway user interface unless you
enable SAL Gateway on Services-VM.
4. Perform the following steps to verify that all SAL Gateway services are running:
a. Log on to the SAL Gateway user interface.
b. Click Administration > Service Control & Status.
c. On the Gateway Service Control page, click Check Health for the Gateway.
d. When the system completes the check, verify that all services listed under Gateway
Services are running as indicated by a green check mark.
For more information, see Checking the status of SAL Gateway and Troubleshooting for
SAL Gateway diagnostics in Administering Avaya Diagnostic Server SAL Gateway.
Related links
Enabling SAL Gateway on page 26

February 2018 Implementing and Administering Services-VM 17

Comments on this document? infodev@avaya.com
Postupgrade verification and configuration

Password complexity rules

Password rules
You must adhere to the following rules while creating a root user password:
• The password must be minimum eight characters long.
• The password must contain minimum one English upper case letter.
• The password must contain minimum one English lower case character.
• The password must contain minimum one numeric character.
• The password must contain minimum one non-alphanumeric special character, such as ! @ #
&.
• The password must contain minimum four characters that are different from the previous
password.

February 2018 Implementing and Administering Services-VM 18

Comments on this document? infodev@avaya.com
Chapter 5: Administering Services-VM
through the System Platform
web console

Services-VM administration overview

You can administer Services-VM in the same way as a solution template by accessing the System
Platform web console. Some of the activities that you can perform include:
• Viewing and updating network configuration information of Services-VM.
• Enabling or disabling Services-VM.
• Enabling or disabling SAL Gateway on Services-VM.
• Checking the status of Services-VM.
• Managing patches for Services-VM.
• Rebooting Services-VM.
• Backing up and restoring Services-VM.

Modifying Services-VM configuration

About this task
Using the System Platform web console, you can change the network configuration of Services-
VM.
Warning:
Changes in the network parameters result in restart of applications that run on Services-VM,
including SAL Gateway, which causes termination of established connections.
Caution:
Do not enable or disable Services-VM while making changes to any network settings on the
Network Configuration page. If you want to enable or disable Services-VM, first save the
network configuration changes and then navigate back to the Network Configuration page to
enable or disable Services-VM.

February 2018 Implementing and Administering Services-VM 19

Comments on this document? infodev@avaya.com
Administering Services-VM through the System Platform web console

Procedure
1. Log on to the System Platform web console as an administrator.
2. On the System Platform web console, click Server Management > Network
Configuration.
3. On the Network Configuration page, navigate to the Solution Template - ServicesVM
section, which displays the configuration parameters for Services-VM.

Figure 2: Network Configuration page: The Solution Template – ServicesVM section

4. As required, make changes to the following fields:
• Services VM Hostname
• Preferred IP address Type
• Services VM IPv4 Address (Mandatory)
• Services VM IPv6 Address (If Preferred IP address Type is IPv6, then mandatory)
5. Click Save.
Note:
For information about other fields on the Network Configuration page, see
Administering Avaya Aura System Platform.

February 2018 Implementing and Administering Services-VM 20

Comments on this document? infodev@avaya.com
 Enabling Services-VM

Enabling Services-VM
About this task
To avail the remote access service through the SAL Gateway residing on Services-VM, you must
enable Services-VM. If you did not enable Services-VM during a platform upgrade, you can enable
Services-VM using the System Platform web console.
Caution:
Do not change any network settings on the Network Configuration page while enabling or
disabling Services-VM. If you need to make any network configuration change, first save the
enabling or disabling action and then navigate back to the Network Configuration page to
make further changes.
Procedure
1. Log on to the System Platform web console as an administrator.
2. In the navigation pane, click Server Management > Network Configuration.
3. On the Network Configuration page, navigate to the Solution Template - ServicesVM
section, which displays the configuration parameters for Services-VM.
4. In the Solution Template - ServicesVM section, select the Enable Services VM check
box.
5. Click Save.

Disabling Services-VM
About this task
When you do not require the services of SAL Gateway or any other applications running on
Services-VM, you can disable Services-VM using the System Platform web console.
Caution:
Do not change any network settings on the Network Configuration page while enabling or
disabling Services-VM. If you need to make any network configuration change, first save the
enabling or disabling action and then navigate back to the Network Configuration page to
make further changes.
Procedure
1. Log on to the System Platform web console as an administrator.
2. In the navigation pane, click Server Management > Network Configuration.
3. On the Network Configuration page, navigate to the Solution Template - ServicesVM
section, which displays the configuration parameters for Services-VM.

February 2018 Implementing and Administering Services-VM 21

Comments on this document? infodev@avaya.com
Administering Services-VM through the System Platform web console

4. In the Solution Template - ServicesVM section, clear the Enable Services VM check
box.
5. Click Save.

Checking application states

About this task
After an upgrade or after applying a patch, you might want to check the current status of the virtual
machine and applications running on the virtual machine to verify if the system is in good state.
From the System Platform web console, you can check the status of Services-VM and SAL
Gateway services running on Services-VM.
Note:
For more information about managing virtual machines on the System Platform web console,
see Administering Avaya Aura® System Platform.
Procedure
1. Log on to the System Platform web console as an administrator.
2. In the navigation pane, click Virtual Machine Management > Manage.
The Virtual Machine List page displays a list of all virtual machines that are currently
running on System Platform.
3. To view details of a specific virtual machine, click the virtual machine name.
For example, click services_vm to view details of Services-VM.
The Virtual Machine Detail page displays configuration details for the virtual machine,
including its MAC address, IP address, and operating system. The page also displays the
status of the virtual machine and the application running on the virtual machine.
4. Check the value of the Application State field to know the current status of SAL Gateway
running on the virtual machine.
Possible application statuses on Services-VM are as follows:
• Starting: SAL Gateway is currently starting up and will enter the running state when the
system completes the startup process.
• Running: All SAL Gateway services are running normally.
• Stopped: All SAL Gateway services have stopped. This happens when you disable SAL
Gateway.
• Stopping: SAL Gateway services are shutting down and SAL Gateway will enter the
stopped state when the system completes the shutdown process.
• Partial: Some services of SAL Gateway are running, but not all services.

February 2018 Implementing and Administering Services-VM 22

Comments on this document? infodev@avaya.com
 Checking version information for Services-VM

• Timeout: Application has missed a heartbeat, signifying a problem and can result in
reboot of the virtual machine to clear the problem.

Checking version information for Services-VM

About this task
Knowing the version number helps you in managing a virtual machine, such as selecting an
appropriate upgrade path during an upgrade process and applying appropriate patches or service
packs. Using this procedure, you can check the version information of Services-VM installed on
System Platform.
Procedure
1. Log on to the System Platform web console as an administrator.
2. In the navigation pane, click Virtual Machine Management > Manage.
The Virtual Machine List page displays a list of all virtual machines that are currently
running on System Platform.
3. Click the version number displayed beside services_vm.
The Detailed Version Information for domain page displays the version information for
Services-VM, its operating system, Avaya Diagnostic Server, SAL Gateway, SAL models,
and patches.

Rebooting Services-VM from the System Platform web

console
About this task
As part of troubleshooting activities, sometimes you might need to reboot Services-VM. Using this
procedure to reboot Services-VM from the System Platform web console.
Caution:
Reboot of Services-VM results in restart of applications that run on Services-VM, including
SAL Gateway, which causes termination of established connections. Product alarm flow to
Avaya might also be delayed.
Procedure
1. Log on to the System Platform web console as a user with the Advanced Administrator
role.
2. In the navigation pane, click Virtual Machine Management > Manage.

February 2018 Implementing and Administering Services-VM 23

Comments on this document? infodev@avaya.com
Administering Services-VM through the System Platform web console

The Virtual Machine List page displays a list of all the virtual machines that are currently
running on System Platform.
3. On the Virtual Machine List page, click services_vm.
4. On the Virtual Machine Detail page, click Reboot.

Managing Services-VM patches

Important:
Before applying any service packs or patches for the SAL Gateway on Services-VM, ensure
that the service pack or patch is certified for Services-VM.
Procedure
To install service packs and patches for Services-VM or SAL Gateway on Services-VM, follow the
procedure given in the corresponding Release Notes.

Performing backup and restore of Services-VM

About this task
Using the System Platform web console, you can backup and restore the configuration information
of System Platform and solution templates, including cdom, Services-VM, and other template
virtual machines. The backup feature of System Platform backs up only the configuration files or
settings. Therefore, the restore operation cannot restore other system files and folders that might
get deleted.
Caution:
You must perform backup and restore operations for SAL Gateway and SLA Mon™ on
Services-VM through the integrated Backup and Restore options on the System Platform web
console. The Services-VM upgrade process does not save the backup archives that you
create locally on Services-VM by using the backup feature of SAL Gateway and SLA Mon™.
In addition, you must create a new backup point from the System Platform web console after a
successful upgrade to Services-VM 4.0. The system might not restore some configurations
when you use earlier backups taken with the earlier version of Services-VM.
Procedure
1. Log on to the System Platform web console as an administrator.
2. To back up configuration data on System Platform, in the navigation pane, click Server
Management > Backup/Restore > Backup.

February 2018 Implementing and Administering Services-VM 24

Comments on this document? infodev@avaya.com
 Performing backup and restore of Services-VM

You can schedule a periodic backup or take the system backup immediately. For more
information about the System Platform backup process, see Administering Avaya Aura®
System Platform.
3. To restore backed up configuration data for System Platform and solution templates, in the
navigation pane, click Server Management > Backup/Restore > Restore.
You can choose the restore point and restore your system to that point. For more
information about the System Platform restore process, see Administering Avaya Aura®
System Platform.

February 2018 Implementing and Administering Services-VM 25

Comments on this document? infodev@avaya.com
Chapter 6: Managing SAL Gateway through
the System Platform web
console

SAL Gateway management through the System Platform

web console
Using the System Platform web console, you can perform some activities around the SAL
Gateway residing on Services-VM. Activities that you can perform include:
• Enabling SAL Gateway
• Disabling SAL Gateway
• Launching the SAL Gateway UI
This chapter does not cover the administration of SAL Gateway through the SAL Gateway web
interface. For SAL Gateway administration information, see Administering Avaya Diagnostic
Server SAL Gateway.

Enabling SAL Gateway

About this task
To avail the alarm transfer and remote access services through the SAL Gateway that resides on
Services-VM, SAL Gateway must be in the enabled state. Using the System Platform web
console, you can enable the SAL Gateway on Services-VM.
Before you begin
Ensure that Services-VM is already enabled on System Platform.
Procedure
1. Log on to the System Platform web console as an administrator.
2. In the navigation pane, click Server Management > SAL Gateway Management.

February 2018 Implementing and Administering Services-VM 26

Comments on this document? infodev@avaya.com
 Disabling SAL Gateway

Figure 3: SAL Gateway Management page

3. On the SAL Gateway Management page, click Enable SAL Gateway.
If you see the Disable SAL Gateway button instead of the Enable SAL Gateway button,
SAL Gateway is already enabled.

Disabling SAL Gateway

About this task
Using the System Platform web console, you can disable the SAL Gateway residing on Services-
VM.
For example, if you are using a centralized standalone SAL Gateway to support System Platform
and other products residing on System Platform and do not require the services of the SAL
Gateway residing on Services-VM, you might want to disable the SAL Gateway on Services-VM.
Note:
SAL Gateway uninstallation is not supported on Services-VM. Instead, you can disable
Services-VM or SAL Gateway through the System Platform web console.
Procedure
1. Log on to the System Platform web console as an administrator.
2. In the navigation pane, click Server Management > SAL Gateway Management.

February 2018 Implementing and Administering Services-VM 27

Comments on this document? infodev@avaya.com
Managing SAL Gateway through the System Platform web console

Figure 4: SAL Gateway Management page

3. On the SAL Gateway Management page, click Disable SAL Gateway.
If SAL Gateway is already disabled, the SAL Gateway Management page displays the
Enable SAL Gateway button instead of the Disable SAL Gateway button.

Launching the SAL Gateway user interface through

System Platform
About this task
Use this procedure to launch the SAL Gateway user interface through the System Platform web
console.
You can use the SAL Gateway UI to administer SAL Gateway. The SAL Gateway user interface
provides a mean to configure and monitor SAL Gateway services used for alarm transfer and
remote access. For more information, see Administering Avaya Diagnostic Server SAL Gateway.
Procedure
1. Log on to the System Platform web console as an administrator.
2. In the navigation pane, click Server Management > SAL Gateway Management.
3. On the SAL Gateway Management page, click Launch SAL Gateway Management
Portal.
4. On the Log On page of the SAL Gateway portal, enter your user name and password for
the System Platform Console Domain.
5. Configure the SAL Gateway as appropriate.

February 2018 Implementing and Administering Services-VM 28

Comments on this document? infodev@avaya.com
 Launching the SAL Gateway user interface through System Platform

Note:
An alternative method of accessing the SAL Gateway user interface is to open the
following URL on a web browser:
https://<Services-VM_address>:7443/
Where, replace <Services-VM_address> with the host name or IP address of Services-
VM. This method can be used to access SAL Gateway if the System Platform web
console is not accessible for some reason.

February 2018 Implementing and Administering Services-VM 29

Comments on this document? infodev@avaya.com
Chapter 7: Configuring SNMP

SNMP configuration overview

Services-VM can support either SNMP v2c or SNMP v3 for SAL Gateway. By default, Services-
VM is configured for SNMP v3. You can change the configuration to support the required SNMP
version.
Services-VM preserves the SNMP configuration, either v2c or v3, from the earlier version of
Services-VM during an upgrade.
Services-VM contains two configuration files, snmpv2c.conf and snmpv3.conf, for SNMP v2c
and SNMP v3 configuration respectively. Based on the SNMP version you want to support, you
must use one of the two files for SNMP configuration. The files contain the following parameters
and default values. For SNMP configuration, you must replace the default values with actual
values after consulting with your network administrator.
File Parameter Default value
snmpv2c.conf Community string avaya123
snmpv3.conf User name initial
Authentication protocol MD5
Authentication password avaya123
Privacy protocol Data Encryption Standard (DES)
Privacy password avaya123

Configuring SNMP for Services-VM

About this task
Use this procedure to update the SNMP configuration of Service-VM to support either SNMP v2c
or SNMP v3.
Procedure
1. Log on to the Services-VM command line interface through an SSH session.
2. Use the su command to change the user to root.
3. Change the directory to /etc/snmp.

February 2018 Implementing and Administering Services-VM 30

Comments on this document? infodev@avaya.com
 Configuring SNMP for Services-VM

4. In the directory, find the snmpd.conf file, and check to where the snmpd.conf softlink is
pointing.
The following is a sample of the ls command output of the /etc/snmp directory:
lrwxrwxrwx 1 root root 11 Jul 19 20:35 snmpd.conf -> snmpv3.conf
-rw-r--r-- 1 root root 18579 May 21 14:30 snmpd.conf.save
-rw-r--r-- 1 root root 77 Jun 28 11:54 snmpv2c.conf
-rw-r--r-- 1 root root 72 Jun 28 11:54 snmpv3.conf

5. If the snmpd service is running, run the following command to stop the service:
service snmpd stop
6. Run the following command to back up the snmpd.conf file:
cp snmpd.conf snmpd.conf.orig
7. Run the following command to remove the snmpd.conf file:
rm -f snmpd.conf
8. Do one of the following to create a softlink to the SNMP version that you want to support:
• To configure the SNMP v3 support on Services-VM, run the following command:
ln -s snmpv3.conf snmpd.conf
• To configure the SNMP v2c support on Services-VM, run the following command:
ln -s snmpv2c.conf snmpd.conf
9. Start the snmpd service:
service snmpd start
10. If the snmpAgent service is already running, restart the service:
service snmpAgent restart
You have completed the SNMP configuration for Services-VM.

February 2018 Implementing and Administering Services-VM 31

Comments on this document? infodev@avaya.com
Chapter 8: Resources

Documentation
Refer the following documents to obtain information about administering and using System
Platform and SAL Gateway:
• Installing and Configuring Avaya Aura® System Platform
• Administering Avaya Aura® System Platform
• Upgrading Avaya Aura® System Platform
• Administering Avaya Diagnostic Server SAL Gateway
Always use the appropriate version of the document to obtain information about System Platform
and Avaya Diagnostic Server. You can download these documents from the Avaya Support
website at http://support.avaya.com/.
Also check the Avaya Support website for the latest updates and information before you install or
upgrade Avaya products.
Related links
Finding documents on the Avaya Support website on page 32

Finding documents on the Avaya Support website

Procedure
1. Navigate to http://support.avaya.com/.
2. At the top of the screen, type your username and password and click Login.
3. Click Support by Product > Documents.
4. In Enter your Product Here, type the product name and then select the product from the
list.
5. In Choose Release, select an appropriate release number.
6. In the Content Type filter, click a document type, or click Select All to see a list of all
available documents.
For example, for user guides, click User Guides in the Content Type filter. The list
displays the documents only from the selected category.

February 2018 Implementing and Administering Services-VM 32

Comments on this document? infodev@avaya.com
 Viewing Avaya Mentor videos

7. Click Enter.
Related links
Documentation on page 32

Viewing Avaya Mentor videos

Avaya Mentor videos provide technical content on how to install, configure, and troubleshoot
Avaya products.
About this task
Videos are available on the Avaya Support website, listed under the video document type, and on
the Avaya-run channel on YouTube.
Procedure
• To find videos on the Avaya Support website, go to 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.

February 2018 Implementing and Administering Services-VM 33

Comments on this document? infodev@avaya.com
Index
A P
administration password rules .....................................................................18
Services-VM ................................................................. 19 postupgrade tasks ............................................................... 15

B R
back up Services-VM ...........................................................24 rebooting Services-VM ........................................................ 23
resources, Services-VM .........................................................8
restore Services-VM ............................................................ 24
C
checking application states ..................................................22 S
checking version information ............................................... 23
checklist SAL Gateway
postupgrade tasks ........................................................ 15 disabling ....................................................................... 27
configuring SNMP ................................................................30 enabling ........................................................................ 26
launching from System Platform ...................................28
SAL Gateway management .................................................26
D SAL Gateway on Services-VM
disabling SAL Gateway ........................................................27 supported load ................................................................9
disabling Services-VM ......................................................... 21 Services-VM
document administration ............................................................... 19
prerequisites ................................................................... 5 backup restore ..............................................................24
purpose ...........................................................................5 checking application states ...........................................22
document changes ................................................................ 6 checking version information ........................................ 23
disabling ....................................................................... 21
documentation .............................................................. 32
E enabling ........................................................................ 21
implementation process ................................................10
enabling Services-VM ..........................................................21
managing patches ........................................................ 24
modify configuration ..................................................... 19
L overview ......................................................................... 7
rebooting from System Platform ................................... 23
launching SAL Gateway user interface ................................28 resources ........................................................................8
upgrading ...................................................................... 11
M use of SAL Gateway .......................................................9
Services-VM upgrade
managing patches ............................................................... 24 verify ............................................................................. 17
modify SNMP configuration .............................................................30
Services-VM configuration ............................................19 support .................................................................................33

N U
network configuration upgrade path ........................................................................10
modify ........................................................................... 19 upgrading
new in the release ..................................................................6 Services-VM ..................................................................11

O V
overview verify
SAL Gateway management ..........................................26 Services-VM upgrade ................................................... 17
Services-VM ................................................................... 7 videos .................................................................................. 33

February 2018 Implementing and Administering Services-VM 34

Comments on this document? infodev@avaya.com