Implementing and Administering Services-VM 2.0

Implementing and Administering
Services-VM
on Avaya Aura® System Platform
Release 2.0
January 2013
Issue 1
© 2013 Avaya Inc. All Rights Reserved.
Notice
While reasonable efforts have been made to ensure that the information in this
document is complete and accurate at the time of printing, Avaya assumes no
liability for any errors. Avaya reserves the right to make changes and
corrections to the information in this document without the obligation to notify
any person or organization of such changes.
Documentation disclaimer
“Documentation” means information published by Avaya in varying mediums
which may include product information, operating instructions and performance
specifications that Avaya generally makes available to users of its 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 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 its hardware and Software (“Product(s)”).
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:
http://www.avaya.com/support
Please note that if you acquired the Product(s) from an authorized Avaya
reseller outside of the United States and Canada, the warranty is provided to
you by said Avaya reseller and not by Avaya. “Software” means computer
programs in object code, provided by Avaya or an Avaya Channel Partner,
whether as stand-alone products or pre-installed on hardware products, and
any upgrades, updates, bug fixes, or modified versions thereto.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE,
http://support.avaya.com/LicenseInfo/ ARE APPLICABLE TO ANYONE WHO
DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE,
PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN
AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A
COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA
RESELLER. 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 AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT
TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR
SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING,
DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS
TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR
WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE
SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS
“YOU” AND “END USER”), AGREE TO THESE TERMS AND CONDITIONS
AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR
THE APPLICABLE AVAYA AFFILIATE ( “AVAYA”).
Avaya grants you a license within the scope of the license types described
below, with the exception of Heritage Nortel Software, for which the scope of
the license is detailed below. Where the order documentation does not
expressly identify a license type, the applicable license will be a Designated
System License. The applicable number of licenses and units of capacity for
which the license is granted will be one (1), unless a different number of
licenses or units of capacity is specified in the documentation or other materials
available to you. “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.
License type(s)
Designated System(s) License (DS). End User may install and use each
copy 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, 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.
Database License (DL). End User may install and use each copy 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 a
single instance of the same database.
CPU License (CP). End User may install and use each copy of the Software
on a number of Servers up to the number indicated in the order provided that
the performance capacity of the Server(s) does not exceed the performance
capacity specified for the Software. End User may not re-install or operate the
Software on Server(s) with a larger performance capacity without Avaya’s prior
consent and payment of an upgrade fee.
Named User License (NU). You may: (i) install and use the Software on a
single Designated Processor or Server per authorized Named User (defined
below); or (ii) install and use the Software on a Server so long as only
authorized Named Users access and use the Software. “Named User”, means
a user or device that has been expressly authorized by Avaya to access and
use the Software. At Avaya’s sole discretion, a “Named User” may be, without
limitation, designated by name, corporate function (e.g., webmaster or
helpdesk), an 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”).
Heritage Nortel Software
“Heritage Nortel Software” means the software that was acquired by Avaya as
part of its purchase of the Nortel Enterprise Solutions Business in December
2009. The Heritage Nortel Software currently available for license from Avaya
is the software contained within the list of Heritage Nortel Products located at
http://support.avaya.com/LicenseInfo/ under the link “Heritage Nortel
Products”. For Heritage Nortel Software, Avaya grants Customer a license to
use Heritage Nortel Software provided hereunder solely to the extent of the
authorized activation or authorized usage level, solely for the purpose specified
in the Documentation, and solely as embedded in, for execution on, or (in the
event the applicable Documentation permits installation on non-Avaya
equipment) for communication with Avaya equipment. Charges for Heritage
Nortel Software may be based on extent of activation or use authorized as
specified in an order or invoice.
Copyright
Except where expressly stated otherwise, no use should be made of materials
on this site, the Documentation, Software, or hardware provided by Avaya. All
content on this site, the documentation and the Product provided by Avaya
including the selection, arrangement and design of the content is owned either
by Avaya or its licensors and is protected by copyright and other intellectual
property laws including the sui generis rights relating to the protection of
databases. You may not modify, copy, reproduce, republish, upload, post,
transmit or distribute in any way any content, in whole or in part, including any
code and software unless expressly authorized by Avaya. Unauthorized
reproduction, transmission, dissemination, storage, and or use without the
express written consent of Avaya can be a criminal, as well as a civil offense
under the applicable law.
Third-party components
“Third Party Components” mean certain software programs or portions thereof
included in the Software that may contain software (including open source
software) distributed under third party agreements (“Third Party Components”),
which contain terms regarding the rights to use certain portions of the Software
(“Third Party Terms”). Information regarding distributed Linux OS source code
(for those Products that have distributed Linux OS source code) and identifying
the copyright holders of the Third Party Components and the Third Party Terms
that apply is available in the Documentation or on Avaya’s website at:
http://support.avaya.com/ThirdPartyLicense/. You agree to the Third Party
Terms for any such Third Party Components.
Note to Service Provider
The Product may use Third Party Components that have Third Party Terms
that do not allow hosting and may need to be independently licensed for such
purpose.
Preventing Toll Fraud
“Toll Fraud” is the unauthorized use of your telecommunications system by an
unauthorized party (for example, a person who is not a corporate employee,
agent, subcontractor, or is not working on your company's behalf). Be aware
that there can be a risk of Toll Fraud associated with your system and that, if
Toll Fraud occurs, it can result in substantial additional charges for your
telecommunications services.
Avaya Toll Fraud intervention
If you suspect that you are being victimized by Toll Fraud and you need
technical assistance or support, call Technical Service Center Toll Fraud
Intervention Hotline at +1-800-643-2353 for the United States and Canada. For
additional support telephone numbers, see the Avaya Support website:
http://www.avaya.com/support.Suspected security vulnerabilities with Avaya
products should be reported to Avaya by sending mail to:
securityalerts@avaya.com.
Trademarks
The trademarks, logos and service marks (“Marks”) displayed in this site, the
Documentation and Product(s) provided by Avaya are the registered or
unregistered Marks of Avaya, its affiliates, or other third parties. Users are not
permitted to use such Marks without prior written consent from Avaya or such
third party which may own the Mark. Nothing contained in this site, the
Documentation and Product(s) should be construed as granting, by implication,
estoppel, or otherwise, any license or right in and to the Marks without the
express written permission of Avaya or the applicable third party.
Avaya is a registered trademark of Avaya Inc.
All non-Avaya trademarks are the property of their respective owners, and
“Linux” is a registered trademark of Linus Torvalds.
Downloading documents
For the most current versions of documentation, see the Avaya Support
website:
http://www.avaya.com/support
Contact Avaya Support
See the Avaya Support website: http://support.avaya.com for product notices
and articles, or to report a problem with your Avaya product.
For a list of support telephone numbers and contact addresses, go to the
Avaya Support website: http://support.avaya.com, scroll to the bottom of the
page, and select Contact Avaya Support.
Contents
Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
Purpose of the document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
Prerequisites for using the document . . . . . . . . . . . . . . . . . . . . . . . .
7
Services-VM overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8
Usage of SAL Gateway on Services-VM . . . . . . . . . . . . . . . . . . . . . . .
9
Services-VM resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
Supported load for SAL Gateway on Services-VM . . . . . . . . . . . . . . . . .
10
New in this release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
Related resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Avaya Mentor videos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
11
12
Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
Chapter 2: Implementing Services-VM . . . . . . . . . . . . . . . . . . .
13
Services-VM 2.0 implementation process . . . . . . . . . . . . . . . . . . . . . .
13
Services-VM installation through a fresh installation of System Platform 6.3. . .
14
Services-VM installation through upgrading from System Platform 6.0.3 to 6.3 .
15
Upgrading Services-VM on System Platform . . . . . . . . . . . . . . . . . . . .
18
Verifying Services-VM installation and upgrade. . . . . . . . . . . . . . . . . . .
20
Chapter 3: Configuring SNMP . . . . . . . . . . . . . . . . . . . . . . .
21
SNMP configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
Configuring SNMP for Services-VM . . . . . . . . . . . . . . . . . . . . . . . . .
21
Chapter 4: Administering Services-VM through the System Platform Web Console
23
Services-VM administration overview . . . . . . . . . . . . . . . . . . . . . . . .
23
Modifying Services-VM configuration . . . . . . . . . . . . . . . . . . . . . . . .
23
Enabling Services-VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25
Disabling Services-VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25
Checking application states . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26
Checking version information for Services-VM . . . . . . . . . . . . . . . . . . .
27
Rebooting Services-VM from the System Platform Web Console . . . . . . . . .
28
Managing Services-VM patches . . . . . . . . . . . . . . . . . . . . . . . . . . .
28
Chapter 5: Managing SAL Gateway through the System Platform Web Console29
SAL Gateway management on the System Platform Web Console overview . . .
Implementing and Administering Services-VM
29
January 2013
5
Contents
Enabling SAL Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
Disabling SAL Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30
Launching the SAL Gateway UI from System Platform . . . . . . . . . . . . . . .
31
Implementing and Administering Services-VM
January 2013
6
Chapter 1: Introduction
Purpose of the document
This document provides information about the following:
●
Introduction to Services-VM
●
Implementation of Services-VM on Avaya Aura® System Platform
●
Services-VM upgrade on System Platform
●
Administration of Services-VM on 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 Secure Access Link (SAL)
Gateway management through the System Platform Web Console, the document is not a
reference point for implementation and administration of System Platform and SAL Gateway.
Always use the appropriate product documentation to obtain information about System Platform
and SAL Gateway.
The screenshots used in the document are representative examples of the application user
interface (UI) and might change in future releases of System Platform.
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 the 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.
Implementing and Administering Services-VM
January 2013
7
Introduction
Services-VM overview
In Avaya Aura® System Platform 6.0 and earlier releases, SAL Gateway was a coresident
application on the Console Domain (cdom). From System Platform 6.2 onwards, SAL Gateway
is hosted on an independent virtual machine, Services Virtual Machine (Services-VM), on
System Platform. This new SAL Gateway deployment model eases SAL Gateway upgrades on
System Platform and provides users with faster access to the benefits from enhancements and
maintenance releases.
Services-VM is an independent virtual machine on System Platform 6.2 onwards. Services-VM
provides a platform to host tools and applications that provide the customer a better service
experience.
Services-VM is bundled with the installer of System Platform 6.2 and later. However, you can
upgrade Services-VM independent of System Platform.
Note:
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
like a solution template.
Figure 1: Structure of Services-VM on System Platform
8
Implementing and Administering Services-VM
January 2013
Usage of SAL Gateway on Services-VM
Usage of SAL Gateway on Services-VM
You can use SAL Gateway residing in Services-VM to remotely monitor and remotely access
multiple devices, also known as managed elements. SAL Gateway can service managed
elements that are on the same server as SAL Gateway and managed elements that are not on
the same server.
Use of SAL Gateway on Services-VM is restricted to the following three scenarios:
●
For the solution template applications deployed on the same server as the embedded SAL
Gateway.
●
For the System Manager versions approved for System Platform 6.2 or later, plus remote
access and alarming to a maximum of ten Session Managers.
●
For solution templates including Communication Manager (that is, all Communication
Manager and Solution for Midsize Enterprise templates approved for System Platform 6.2
or later) that can support a maximum of four Avaya Branch Gateways, such as G250,
G350, G430, and G450. Alarming from a Branch Gateway is reported through the
Communication Manager Server, which forwards the alarms to Avaya.
Any configuration that exceeds the usage given in the three scenarios stated earlier must have
a standalone SAL Gateway for use.
The limits stated are based upon normal alarm frequency and network conditions.
Note:
Note:
You can find notifications about updates to the usage of SAL Gateway on System
Platform in PSN003058u on the Avaya Support website at http://
support.avaya.com. You can use the following direct link to view the notification:
https://downloads.avaya.com/css/P8/documents/100124860.
Services-VM resources
For this release of Services-VM, System Platform allocates the following resources to
Services-VM. This section is for informational purposes only. The values are set by Avaya and
are not user configurable.
Resource
Value
Virtual CPU core
1
CPU speed
2 GHz
Implementing and Administering Services-VM
January 2013
9
Introduction
Note:
Resource
Value
Total memory
512 MB
Total disk space
4 GB
Virtual NIC
1
Note:
Future releases of Services-VM might have more than 512 MB of memory, which
will enable the onboard SAL Gateway to support higher number of managed
elements. Specifications of other resources might also change in future releases.
Supported load for SAL Gateway on Services-VM
SAL Gateway running on Services-VM supports maximum 15 managed elements.
!
Important:
To ensure stable and predictable performance, do not exceed the limit of 15
managed elements for SAL Gateway that is hosted on Services-VM. To support
more than 15 managed elements, you must implement a standalone SAL
Gateway.
!
Important:
Do not add SLA Mon Server as a managed element with the OIS_SLA_MON
model to SAL Gateway that is running on Services-VM in System Platform 6.2 or
later.
Important:
Important:
New in this release
Services-VM Release 2.0 is built on its previous release and has the following new features and
enhancements.
Operating system upgrade to CentOS 5.8
In Services-VM Release 2.0, the operating system is upgraded from CentOS version 5.5 to
version 5.8.
10
Implementing and Administering Services-VM
January 2013
Related resources
SAL Gateway upgrade to Release 2.2
In Services-VM Release 2.0, SAL Gateway is upgraded to Release 2.2.
For more information about SAL Gateway 2.2, see the documentation for release 2.2 available
on the Avaya Support website at http://support.avaya.com.
Local root access
In Release 2.0, Services-VM provides you with a local root access. The root login comes with a
default password, root01. For security reasons, change the password immediately after
upgrading to Release 2.0.
Simpler SNMP v2c and v3 configuration
Services-VM Release 2.0 simplifies the configuration of the Net-SNMP Master agent for v2c or
v3.
Security enhancements
Release 2.0 has the following security enhancements:
●
Network and firewall related security fixes.
●
OS related security fixes.
●
Security patches for packages.
Related 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
●
Secure Access Link Gateway Implementation Guide
Always use the appropriate version of the document to obtain information about System
Platform and SAL Gateway. You can download these documents from the Avaya Support
website at http://support.avaya.com.
Implementing and Administering Services-VM
January 2013
11
Introduction
Also check the Avaya Support website for the latest updates and information before you install
or upgrade Avaya products.
Avaya Mentor videos
Avaya Mentor is an Avaya-run channel on YouTube that includes technical content on how to
install, configure, and troubleshoot Avaya products.
Visit http://www.youtube.com/AvayaMentor and do one of the following:
●
Enter a key word or key words in the Search channel to search for a specific product or
topic.
●
Click the name of a playlist to scroll though the posted videos.
Support
Visit 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 notices,
release notes, downloads, user guides, and resolutions to issues. Use the Web service request
system to create a service request. Chat with live agents to get answers to questions. If an
issue requires additional expertise, agents can quickly connect you to a support team.
12
Implementing and Administering Services-VM
January 2013
Chapter 2: Implementing Services-VM
Services-VM 2.0 implementation process
You can implement Services-VM 2.0 through a fresh installation of System Platform 6.3.
If you already have System Platform installed in your environment, the following upgrade paths
to Services-VM 2.0 are available:
Release
Upgrade path
System Platform 6.0.3.x.x
Direct platform upgrade to System Platform 6.3,
which comes with the integrated Services-VM
Release 2.0.
System Platform 6.2.0.x.x
Template upgrade to Services-VM 2.0 >
(Optional) Platform upgrade to System Platform 6.3.
Platform upgrade to System Platform 6.3 (the
upgrade does not affect the Services-VM version,
which remains as 1.0) > Template upgrade to
Services-VM 2.0.
After the first time implementation of Services-VM, future upgrades to System Platform do not
affect Services-VM. For example, a platform upgrade from System Platform 6.2 to 6.3 does not
upgrade the Services-VM version.
Note:
Note:
After the first time implementation of Services-VM, you must maintain
Services-VM like a solution template. If you already have Services-VM on your
System Platform, You can implement any later releases of Services-VM through
the template upgrade process. For more information about upgrading the
Services-VM version, see Upgrading Services-VM on System Platform on
page 18.
!
Important:
Important:
Before proceeding with a platform upgrade from System Platform 6.0 to 6.3, read
the Services-VM Installation Application Note to ensure that communication
between the existing integrated SAL Gateway and Avaya Data Center is not
severed during the upgrade process. Retain the shared Console Domain IP
address for the integrated Services-VM and assign the new IP address to the
Console Domain prior to the upgrade.
Implementing and Administering Services-VM
January 2013
13
Implementing Services-VM
Note:
Note:
If the embedded SAL Gateway on System Platform 6.0.3 is in use, ensure that
you enable Services-VM during the platform upgrade from System Platform 6.0.3
to 6.2 or 6.3. Disabling Services-VM during platform upgrade results in the SAL
Gateway configuration not being migrated to the new SAL Gateway on
Services-VM.
Services-VM installation through a fresh installation of
System Platform 6.3
When you perform a fresh installation of System Platform 6.3.0.x.x, the system installs
Services-VM 2.0 as part of the installation process. During the installation of System Platform
6.3.0.x.x, the installer prompts you for the Services-VM configuration parameters. See Figure 2.
For more information about installing System Platform, see Installing and Configuring Avaya
Aura® System Platform.
Figure 2: Services-VM configuration page during System Platform installation
14
Implementing and Administering Services-VM
January 2013
Services-VM installation through upgrading from System Platform 6.0.3 to 6.3
During the installation of System Platform 6.3, the installer prompts for the following
Services-VM configuration parameters:
Note:
●
Enable Services VM: Select this option if this System Platform solution needs to be
supported by the SAL Gateway residing in Services-VM. Do not select this option if a
centralized standalone SAL Gateway is used to support System Platform and possibly
other products residing in System Platform.
●
Hostname: Provide a hostname for Services-VM.
●
Static IP: Provide a static IPv4 address for Services-VM. This field is always mandatory.
●
IPv6 Address and IPv6 Prefix: Provide an IPv6 address and prefix respectively. These
fields are optional, and you can leave the fields blank if you do not require IPv6. These
fields are available if you selected Enable IPv6 in the previous screens during the System
Platform installation.
Note:
For a fresh installation of System Platform 6.3, the SAL Gateway on Services-VM
is not enabled by default. To enable SAL Gateway after installation, see Enabling
SAL Gateway on page 29.
Services-VM installation through upgrading from System
Platform 6.0.3 to 6.3
Services-VM 2.0 is installed as part of the platform upgrade from System Platform version
6.0.3.x.x to version 6.3.0.x.x. After System Platform installs Services-VM for the first time, you
must maintain Services-VM like a solution template. Future upgrades to System Platform do not
affect Services-VM.
Note:
Note:
In case of a platform upgrade from System Platform version 6.0.3.x.x to version
6.3.0.x.x, you might require to install a service pack, patch, or both before running
the upgrade process. Before proceeding with the platform upgrade, check the
relevant release notes for the System Platform version and adhere to upgrade
paths and instructions in the release notes for the version from which you are
upgrading. See the release notes for the System Platform version 6.3.0.x.x on the
Avaya Support website at http://support.avaya.com.
Implementing and Administering Services-VM
January 2013
15
Implementing Services-VM
!
Important:
Important:
Before proceeding with a System Platform upgrade to version 6.3.0.x.x from
version 6.0.3.x.x, you must read the instructions in "Reassigning Cdom and
Services VM IP addresses," in "Prerequisites for System Platform upgrades" of
Upgrading Avaya Aura System Platform to ensure that communication between
the existing integrated SAL Gateway and Avaya Data Center is not severed
during the upgrade process. Using the instructions in the procedure, you can
re-assign the shared Console Domain and SAL Gateway IP address to
Services-VM and assign a new IP address to the Console Domain prior to the
upgrade. When you assign the former Console Domain IP address to
Services-VM, the managed devices do not need re-administration because SAL
Gateway will have the same IP address after the upgrade.
During the platform upgrade, the System Platform Web Console displays a Web page where
you must provide the Services-VM configuration parameters. See Figure 3.
For more information about platform upgrade, see Upgrading Avaya Aura System Platform.
Figure 3: Platform Upgrade page
During the platform upgrade from System Platform version 6.0.3.x.x to 6.3.0.x.x, you must set
up the following Services-VM configuration parameters:
16
Implementing and Administering Services-VM
January 2013
Services-VM installation through upgrading from System Platform 6.0.3 to 6.3
●
Enable Services VM: Select this option if this System Platform solution needs to be
supported by the SAL Gateway residing in Services-VM. Do not select this option if a
centralized standalone SAL Gateway is used to support System Platform and possibly
other products residing in System Platform.
!
Important:
●
Services VM Hostname: Provide a hostname for Services-VM.
●
Preferred IP address Type: Select the IP address type as IPv4 or IPv6. The system uses
the selected address type to configure the applications that run on Services-VM, such as
SAL Gateway.
●
Services VM IPv4 Address: Enter an IPv4 address for Services-VM in this field. This field
is always mandatory even if the preferred IP address type is IPv6.
●
Services VM IPv6 Address: Enter an IPv6 address for Services-VM in this field. This field
is mandatory only if you have selected the Preferred IP address Type value as IPv6.
!
Important:
If you did not follow the instructions in "Reassigning Cdom and Services VM IP
addresses," in "Prerequisites for System Platform upgrades" of Upgrading Avaya
Aura System Platform to reassign the original Console Domain IP address to
Services-VM, then you must modify the SNMP trap destinations for all managed
devices that send their alarms to SAL Gateway. Specifically, you must set the trap
destinations to the new IP address of Services-VM instead of the previously
shared IP address of Console Domain so that alarms from managed devices can
reach the SAL Gateway hosted on Services-VM. Refer to product-specific
documentation for information about configuring trap destinations.
!
Important:
If you did not follow the instructions in "Reassigning Cdom and Services VM IP
addresses," in "Prerequisites for System Platform upgrades" of Upgrading Avaya
Aura System Platform, then you must ensure that appropriate network
modifications are made and firewall rules are updated or removed to allow the
new Services-VM IP address to communicate with the Avaya SAL Concentrator
Servers.
Important:
Important:
Important:
If the embedded SAL Gateway on System Platform 6.0.3 is in use, ensure that
you enable Services-VM during the platform upgrade from System Platform 6.0.3
to 6.2 or 6.3. Disabling Services-VM during platform upgrade results in the SAL
Gateway configuration not being migrated to the new SAL Gateway on
Services-VM.
Implementing and Administering Services-VM
January 2013
17
Implementing Services-VM
Upgrading Services-VM on System Platform
Services-VM 2.0 supports upgrade from version 1.0.x.
After System Platform installs Services-VM for the first time, you must maintain Services-VM
like a solution template. Services-VM follows the same methodology for the announcement,
distribution, and installation like a solution template. You must apply the Services-VM upgrades
only through the System Platform Web Console similar to all other solution templates.
About this task
The Services-VM upgrade procedure is similar to the upgrade procedure for other solution
templates on System Platform. This section mainly describes the steps that you need to do
differently for Services-VM from a template upgrade.
For more information about upgrading a solution template, see Upgrading Avaya Aura System
Platform.
Procedure
1. Log on to the System Platform Web Console as an administrator.
2. In the left navigation pane, click Virtual Machine Management > Templates.
The Search Local and Remote Template page displays the Services-VM version installed
on System Platform. The page also displays the solutions templates that are currently
installed on System Platform.
3. Click Upgrade that is beside the Services-VM version installed.
4. Select the template for Service-VM upgrade by following the same steps as you do to
search and select a template for upgrade in System Platform.
The Template Details page displays the version and additional information for the current
and the new template for Services-VM.
5. If not selected already, 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.
6. Click Save.
The Template Details page displays the default settings for Services-VM.
7. If required, modify the default settings.
8. Click Install.
At this stage, the upgrade process starts and the Template Installation page displays the
progress of the upgrade process.
18
Implementing and Administering Services-VM
January 2013
Upgrading Services-VM on System Platform
Note:
As part of the upgrade process, the system terminates Services-VM at this stage
that 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 may result in alarms being missed. If you are
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 will continue in the background until all
the tasks in the upgrade process are complete.
Note:
Note:
The first task in the process, downloading the disk image for Services-VM, might
take varied amount of time to complete depending on the location of the server
from which the template is downloaded and the network quality such as
bandwidth. The rest of the tasks take approximately 20 minutes to complete.
Note:
9. Log on to the System Platform Web Console to check the progress of the upgrade
process.
After the completion of the upgrade tasks, the Template Installation page displays two
buttons, Commit Installation and Rollback Installation.
10. Verify the upgrade and do one of the following:
●
Click Commit Installation to commit the newly upgraded Services-VM.
●
Click Rollback Installation to cancel the upgrade process and go back to the
previous version of Services-VM.
!
Important:
If you do not log on to the Web Console within 4 hours (240 minutes) from the
completion of the upgrade tasks and commit the upgrade process, the system
cancels the upgrade process and automatically rolls back to the previous version
of Services-VM.
Important:
Note:
Note:
For information on post-upgrade verifications, see Verifying Services-VM
installation and upgrade on page 20.
!
Important:
Important:
Never directly upgrade SAL Gateway that is running on Services-VM. You must
upgrade SAL Gateway on Services-VM only through the Services-VM upgrade
process.
Implementing and Administering Services-VM
January 2013
19
Implementing Services-VM
Verifying Services-VM installation and upgrade
After installing or upgrading Services-VM, you can perform the following steps to verify whether
the system 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:
●
Verify that services_vm is displayed in the list of virtual machines.
●
Verify that the state for services_vm is Running.
●
If SAL Gateway is enabled on Services-VM, verify that the application state for
services_vm is Running.
3. If SAL Gateway is disabled, enable SAL Gateway from the System Platform Web Console.
Note:
Note:
If SAL Gateway was disabled on Services-VM before the upgrade, SAL Gateway
remains disabled after the upgrade. You cannot launch the SAL Gateway UI
unless you enable SAL Gateway on Services-VM. See Enabling SAL Gateway on
page 29.
4. Perform the following to verify that all SAL Gateway services are running:
a. Log in to the SAL Gateway UI.
b. Click Administration > Service Control & Status.
c. On the Gateway Service Control page, click Check Health for the Gateway.
d. When the health check completes, verify that all services listed under Gateway
Services are depicted as running by a green check mark.
Note:
20
Note:
For more information, see "Checking the status of SAL Gateway" and
"Troubleshooting for SAL Gateway diagnostics" in Secure Access Link 2.2
Gateway Implementation Guide.
Implementing and Administering Services-VM
January 2013
Chapter 3: Configuring SNMP
SNMP configuration overview
Services-VM can support either SNMP v2c or v3 for SAL Gateway. In case of a fresh installation
of Services-VM, Services-VM supports SNMP v3 by default. You can change the configuration
to support the required SNMP version.
After you upgrade Services-VM from 1.0 to 2.0, Services-VM supports the SNMP version that
was configured on Services-VM 1.0.
Services-VM contains two files, snmpv2c.conf and snmpv3.conf, for SNMP v2c
configuration 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 default values that you must modify with actual values after a consultation 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
You can use this procedure to update the SNMP configuration of Service-VM to support either
v2c or v3.
Implementing and Administering Services-VM
January 2013
21
Configuring SNMP
Procedure
1. Connect to Services-VM over Secure Shell (SSH) using the default login for System
Platform, admin.
2. Use the su command to change the user to root.
3. Change directory to /etc/snmp.
4. In the directory, locate the snmpd.conf file, and check where the snmpd.conf soft link is
pointing.
Sample ls command output:
[root@puvvspsvm01 snmp]# ls -l
total 32
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 snmpd.conf:
rm -f snmpd.conf
8. Do one of the following to create a soft link to the SNMP version you want to support:
●
To configure SNMP v3 support in Services-VM, run the following command:
ln -s snmpv3.conf snmd.conf
●
To configure SNMP v2c support in Services-VM, run the following command:
ln -s snmpv2c.conf snmpd.conf
9. Start the snmd 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.
22
Implementing and Administering Services-VM
January 2013
Chapter 4: Administering Services-VM
through the System Platform
Web Console
Services-VM administration overview
After System Platform installs Services-VM, you can administer Services-VM like 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. For more information, see Chapter 5:
Managing SAL Gateway through the System Platform Web Console.
●
Checking the status of Services-VM.
●
Managing patches for Services-VM.
●
Rebooting Services-VM.
Modifying Services-VM configuration
Using the System Platform Web Console, you can modify the network configuration of
Services-VM.
Implementing and Administering Services-VM
January 2013
23
Administering Services-VM through the System Platform Web Console
!
CAUTION:
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.
CAUTION:
CAUTION:
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 4: Network Configuration page - the Solution Template - ServicesVM section
4. As required, make changes to the following fields to modify the network configuration:
●
24
Services VM Hostname
Implementing and Administering Services-VM
January 2013
Enabling Services-VM
●
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:
Note:
For information about other fields on the Network Configuration page, see
Administering Avaya Aura System Platform.
Enabling Services-VM
To avail the SAL alarming and remote access services through the SAL Gateway residing in
Services-VM, you must enable Services-VM. If you did not enable Services-VM during a
platform upgrade or a fresh installation of System Platform, you can enable Services-VM using
the System Platform Web Console.
!
CAUTION:
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
Using the System Platform Web Console, you can disable Services-VM if you do not require the
services of the SAL Gateway or any other applications running on Services-VM.
Implementing and Administering Services-VM
January 2013
25
Administering Services-VM through the System Platform Web Console
!
CAUTION:
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, clear the Enable Services VM check
box.
5. Click Save.
Checking application states
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:
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.
26
Implementing and Administering Services-VM
January 2013
Checking version information for Services-VM
4. Check the value of the Application State field to know the current status of the application
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.
●
Timeout: Application has missed a heartbeat, signifying a problem and can result in
the System Platform rebooting the virtual machine to clear the problem.
Checking version information for Services-VM
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, SAL Gateway, SAL models, and patches.
Implementing and Administering Services-VM
January 2013
27
Administering Services-VM through the System Platform Web Console
Rebooting Services-VM from the System Platform Web
Console
As part of troubleshooting activities, sometimes you might need to reboot Services-VM. Using
this procedure, you can reboot Services-VM from the System Platform Web Console.
!
CAUTION:
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.
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:
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. In
addition, apply all service packs or patches for Services-VM through the System
Platform Web Console only.
To install service packs and patches for Services-VM and the SAL Gateway on Services-VM,
follow the patch management procedures in Administering Avaya Aura System Platform.
28
Implementing and Administering Services-VM
January 2013
Chapter 5: Managing SAL Gateway
through the System Platform
Web Console
SAL Gateway management on the System Platform Web
Console overview
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 UI.
For SAL Gateway administration information, see Secure Access Link 2.2 Gateway
Implementation Guide.
Enabling SAL Gateway
Using the System Platform Web Console, you can enable the SAL Gateway hosted on
Services-VM.
When System Platform installs Services-VM for the first time, the SAL Gateway residing in
Services-VM is not enabled by default. To avail the SAL alarming and remote access services
through the SAL Gateway on Services-VM, you must enable SAL Gateway.
!
Important:
Important:
To enable the SAL Gateway services, ensure that Services-VM is already
enabled on System Platform. See Enabling Services-VM on page 25.
Procedure
1. Log on to the System Platform Web Console as an administrator.
2. In the navigation pane, click Server Management > SAL Gateway Management.
Implementing and Administering Services-VM
January 2013
29
Managing SAL Gateway through the System Platform Web Console
Figure 5: SAL Gateway Management page
3. On the SAL Gateway Management page, click Enable SAL Gateway.
Note:
Note:
If you have already enabled SAL Gateway, the SAL Gateway Management page
displays the Disable SAL Gateway button.
Disabling SAL Gateway
Using the System Platform Web Console, you can disable the SAL Gateway residing in
Services-VM.
For example, if you are using a centralized standalone SAL Gateway to support System
Platform and other products residing in System Platform and do not require the services of the
SAL Gateway residing in Services-VM, you might want to disable the SAL Gateway on
Services-VM.
Procedure
1. Log on to the System Platform Web Console as an administrator.
2. In the navigation pane, click Server Management > SAL Gateway Management.
30
Implementing and Administering Services-VM
January 2013
Launching the SAL Gateway UI from System Platform
Figure 6: SAL Gateway Management page
3. On the SAL Gateway Management page, click Disable SAL Gateway.
Note:
Note:
If you have already disabled SAL Gateway, the SAL Gateway Management page
displays the Enable SAL Gateway button.
Launching the SAL Gateway UI from System Platform
Use this procedure to launch the SAL Gateway UI from the System Platform Web Console.
You can use the SAL Gateway UI to administer SAL Gateway. The SAL Gateway UI provides a
means to configure and monitor the SAL Gateway as well as the associated Secure Access
Concentrator Servers for alarming and remote access. For more information, see Secure
Access Link 2.2 Gateway Implementation Guide.
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. When the portal displays its Log On page, enter your user name and password for the
System Platform Console Domain.
5. Configure the SAL Gateway as appropriate.
Implementing and Administering Services-VM
January 2013
31
Managing SAL Gateway through the System Platform Web Console
Note:
32
Note:
An alternative method of accessing the SAL Gateway UI is to open the following
URL on a Web browser:
https://<Services-VM_address>:7443/, where
<Services-VM_address> is the hostname 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.
Implementing and Administering Services-VM
January 2013