You are on page 1of 64

Avaya Secure Access Link Gateway

using VMware® in the Virtualized
Environment Deployment Guide

Issue 2
April 2013

© 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.

Licence types

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://support.avaya.com. 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.
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”).

2

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.

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.
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.

SAL Gateway in the Virtualized Environment Deployment Guide
Comments? infodev@avaya.com

April 2013

Copyright

Contact Avaya Support

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.

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.

Virtualization
Each vAppliance will have its own ordering code. Note that each
instance of a vAppliance must be separately ordered. If the end user
customer or Business Partner would like to install 2 of the same type
of vAppliances, then 2 vAppliances of that type must be ordered.
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/Copyright. You agree to the Third Party Terms for
any such Third Party Components.
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://support.avaya.com. 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 Documentation
For the most current versions of Documentation, see the Avaya
Support website: http://support.avaya.com.

SAL Gateway in the Virtualized Environment Deployment Guide

April 2013

3

com April 2013 .4 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya.

................................................................. 25 VMware High Availability....................................................................................................................................................................................................................................................... 7 Purpose............................................................................................................................................................................................................... 18 Chapter 4: VMware best practices for performance.................................................................................................................................................................................................................................................................................. 27 Chapter 5: Initial setup and pre-deployment................................................................................................................... 29 Registering the SAL Gateway virtual machine........................................................................................................................................................................ 15 SAL Gateway virtual machine resource requirements........................................................ 9 Chapter 2: Architecture overview...................................................................... 11 Avaya Aura® Virtualized Environment overview.................................................................................. 26 VMware vMotion........................................................................................................................................................... 21 Configuring timing........................................................................................ 24 Best practices for VMware features.......................... 25 VMware Snapshots................................................. 15 Planning.................................................................. 22 VMware networking best practices....................................................................................................................................... 17 VMware software requirements.......... 18 Capacity of SALGateway in a virtualization environment................................................................................................. 20 HP ProLiant Servers — BIOS settings................................................. 13 Deployment guidelines......................................................................................................................................................... 19 Intel Virtualization Technology support..................................................................................................................................................................................................................................... 29 Downloading the SAL Gateway OVA.......................................................................................................................................................................................... 11 VMware components...................................................................................................................................................................................................... 7 Related resources........................................................................................................................................................................................................................................................................................................................................... 15 Server hardware and resources.............................................................................. 19 Dell PowerEdge Servers — BIOS settings................................................................................................. 16 Editing the virtual machine resources......................Contents Chapter 1: Introduction.......................... 21 Time keeping............................... 8 Avaya Mentor videos.............................................................................................................................................................................................................................................................................................................. 29 Registering for PLDS................... 7 Intended audience.................................................................... 8 Documentation............................................................................................. 7 Document changes since last issue.................................... 23 Thin vs.. 27 Hyperthreading.................................... 17 Specifications of bundled software in the OVA.......................................................................... 20 VMware Tools.......................................................................................................................................................................... 17 Software requirements... 29 Downloading software from PLDS......................................... 30 Chapter 6: Deploying the SAL Gateway OVA............................... 19 BIOS....................................... thick deployments........................................................................................................................................................................................................................... 9 Support.................................................................. 33 SAL Gateway in the Virtualized Environment Deployment Guide April 2013 5 ....................................................................................................................................................... 33 SAL Gateway OVA deployment overview........................................... 13 Chapter 3: Planning and configuration... 8 Training.....................................................................................................................................................

.......................................................................................................................................................................................................... 59 Signing up for PCNs and PSNs...................... 45 Chapter 8: Validation of the SAL Gateway implementation.............. 47 Testing the alarming service of SAL Gateway.................................. 50 Chapter 10: Backing up and restoring the virtual machine............ Properties field descriptions........................................................................................................................................................................................................................... 52 Chapter 11: Upgrading the SAL Gateway OVA................................................. 59 PCN and PSN notifications..................................................... 51 Backup and restore overview................ 53 Upgrading the SAL Gateway vAppliance........................................................... 48 Chapter 9: Reconfiguration of the virtual machine.................................. 55 FAQ........................................................... Deploying the SAL Gateway OVA to vCenter............................................................................................................................................................................................................................................................................................................................................ 43 Starting the SAL Gateway virtual machine..................... 33 34 36 40 41 Chapter 7: Initial configuration.............................................................................................................................................................. 54 Chapter 12: Troubleshooting..................................................................................................................................................................................................................... 43 Configuring the virtual machine automatic start and stop settings.............................................................................................. 60 Glossary................................. Deployment of cloned and copied OVAs.................... 59 Viewing PCNs and PSNs..................................................................... 61 Index......... 51 Restoring a virtual machine............................................................................................................................................................................................................................................................................................................. 43 Configuring the SAL Gateway and the network parameters........................................... 53 Validating an upgrade operation................................. 63 6 SAL Gateway in the Virtualized Environment Deployment Guide April 2013 ................................................................................................................................ 47 Testing the SAL Watchdog service.......................................................... 49 Reconfiguring the virtual machine deployed through vCenter..................... 47 Testing the remote access service of SAL Gateway............................................... 55 Appendix A: PCN and PSN notifications......... 51 Backing up the virtual machine.......................................................................................................................................................................................................................................................................................................................................................................Deployment checklist....................................... 49 Reconfiguring the virtual machine deployed directly on an ESXi server................................... 48 Testing the Gateway UI.......... Deploying the SAL Gateway OVA directly to the ESXi server........................................................................................................................................................................................................................................

configuration. and basic maintenance checklists and procedures. initial administration. SAL Gateway in the Virtualized Environment Deployment Guide April 2013 7 . The audience includes and is not limited to implementation engineers. • Added the Deployment of cloned and copied OVAs section. Intended audience The primary audience for this document is anyone who installs. Document changes since last issue The following changes have been made to this document since the last issue: • Added VMware ESXi 5. This document does not include optional or customized aspects of a configuration. configures. troubleshooting. business partners.1 virtualization environment at a customer site. solution providers.0 or 5. and customers. The document includes installation. • Added the details of the application software and the operating system in the Specifications of bundled software in the OVA section.1 support information for SAL Gateway virtual application in the VMware software requirements section. field technicians. and verifies SAL Gateway on a VMware® vSphere™ 5.Chapter 1: Introduction Purpose This document provides procedures for deploying the Secure Access Link (SAL) Gateway virtual application in the Avaya Aura® Virtualized Environment.

Introduction

Related resources
Documentation
The following table lists the documents related to this product. Download the documents from
the Avaya Support website at http://support.avaya.com
Title

Description

Audience

Design
Describes the Virtualized
Sales engineers
Environment solution from a
functional view. Includes a high-level
description of the solution as well as
topology diagrams, customer
requirements, and design
considerations.

Avaya Aura® Virtualized
Environment Solution
Description

Implementation and administration
Implementing Secure Access
Link Gateway

Describes the implementation
requirements and procedures for
standalone SAL Gateway. Provides
information about configuring and
administering SAL Gateway for
remote servicing of Avaya products at
a customer site.

Solution
architects,
implementation
engineers,
support personnel

Training
The following courses are available on the Avaya Learning website at http://www.avayalearning.com. To search for the course, log on to Avaya Learning Center, enter the course
code in the Search field, and click Go.
Course code
1A00232V

8

Course title
®

Avaya Aura Essentials

SAL Gateway in the Virtualized Environment Deployment Guide
Comments? infodev@avaya.com

April 2013

Support

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 the Avaya Mentor Videos website at http://www.youtube.com/AvayaMentor and enter
virtual appliance in the Search channel field to view the list of available videos.
You can also enter the application product name to view videos that are available for a
particular product.

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 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.

SAL Gateway in the Virtualized Environment Deployment Guide

April 2013

9

Introduction

10

SAL Gateway in the Virtualized Environment Deployment Guide
Comments? infodev@avaya.com

April 2013

Avaya Aura® Virtualized Environment provides a hardware-efficient simplified solution for upgrading to the latest Avaya Aura® release and adding the latest Avaya Aura® capabilities. • enables business to scale rapidly to accommodate growth and to respond to changing business requirements. • enables capital equipment cost savings. and at times. For customers who need to add more capacity or application interfaces. • uses standard operating procedures for both Avaya and non-Avaya products. Avaya Aura® Virtualized Environment integrates real-time Avaya Aura® applications with VMware® virtualized server architecture. uses the terms interchangeably. • requires fewer servers and racks which reduces the footprint. • satisfies customer demand for Avaya products in a virtualized environment on customerspecified servers and hardware. For customers who want to migrate to the latest collaboration solutions. Avaya Aura® has been sold and installed as an individual appliance within customer networks to offer collaboration capabilities and business advantages.Chapter 2: Architecture overview Avaya Aura® Virtualized Environment overview Traditionally. For existing customers who have a VMware IT infrastructure. Avaya Aura® applications on VMware offer flexible solutions to expansion. Avaya Aura® Virtualized Environment provides an opportunity to upgrade to the next release level of collaboration using their own VMware infrastructure. • lowers power consumption and cooling requirements. SAL Gateway in the Virtualized Environment Deployment Guide April 2013 11 . Note: This document uses the following terms. • lowers operational expenses. Virtualized Environment is inclusive of the Avaya Aura® portfolio. Virtualized Environment provides the following benefits: • simplifies IT management by providing common software administration and maintenance. The Virtualized Environment project is only for VMware and is not intended to include any other industry hypervisor.

com April 2013 .Network Interface Card (NIC) .1 (PS) • Avaya Aura® Session Manager Release 6. The supplied version is the supported release and has been thoroughly tested. the hardware. The OVA contains the following components: • the application software and operating system.2 (ACE) • Avaya Aura® Application Enablement Services Release 6. and server is managed by vCenter or vSphere.1. The customer provides the servers. and the VMware infrastructure including the VMware licenses.Architecture overview • server and host • reservations and configuration values Virtualized Environment applications The Virtualized Environment supports the following Avaya products: • Avaya Aura® Communication Manager Release 6.2 (US) Customer deployment Deployment into the blade.RAM and CPU reservations and storage requirements .0 and ESXi 5.other settings Patches and upgrades A minimum patch level can be required for each supported application. cluster.2 (AES) • WebLM Standalone Release 6. See the Compatibility Matrix at Compatibility Matrix for more information regarding the application patch requirements.2 (SM) • Avaya Aura® Utility Services Release 6. the virtual appliances.2 (SMGR) • Avaya Aura® Presence Services Release 6.2 (SAL) • Avaya Aura® System Manager Release 6.2 (WebLM) • Secure Access Link Release 2. Software delivery The software is delivered as a pre-packaged Open Virtualization Application (OVA) file posted on the Avaya Product Licensing and Download System (PLDS).2 (Simplex & Duplex) • Avaya Agile Communication Environment™ Release 6. • pre-installed VMware tools for deployment on VMware ESXi 5. 12 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya. • preset configuration details for . Important: Do not update the VMware tools software which is packaged with each OVA unless instructed to do so by Avaya.

Deployment guidelines The high-level steps are: 1. Configuration procedures. Caution: Modifying these values can have a direct impact on the performance. Enables the installation and management of virtual machines.VMware components Performance and capacities The OVA template is built with configuration values which optimize performance and follow recommended Best Practices. VMware components VMware Software Component Description ESXi Host The physical machine running the ESXi Hypervisor software. vSphere Client The client application that is installed on a personal computer or accessible through a Web interface. capacity. Deployment of the . ESXi Hypervisor A platform that runs multiple operating systems on a host computer at the same time. vCenter Server vCenter Server provides centralized control and visibility at every level of the virtual infrastructure. SAL Gateway in the Virtualized Environment Deployment Guide April 2013 13 . Verification of the installation. Avaya GSS could require the customer to reset the values to the optimized values before starting to investigate the issue. Avaya Global Support Services (GSS) may not be able to assist in fully resolving a problem if the resource allocation has been changed for a virtual application. It connects to a vCenter server or directly to an ESXi host in the case where vCenter Server is not used. 3. 2. and stability of the virtual machine.ova. Virtual machines are managed through vSphere Client software which provides alarming and performance monitoring of ESXi hosts and virtual machines. It is the responsibility of the customer to understand the aforementioned impacts when changing configuration values. vCenter Server provides VMware features such as High Availability and vMotion.

The blade may be running at 5% occupancy. from other VMs. depending on host size and VMs. • Ensure that you have enough resources for rainy day scenarios or conditions. Resources may only be configured for traffic or performance on an average day. • Deploy the virtual appliances on the same cluster if it goes beyond the host boundary. 14 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya. Communication Manager duplication pair. and virtual appliance performance. such as Avaya Aura®.com April 2013 . Note that some VMs will behave differently at a higher CPU usage. For example. occupancy. • Do not over-subscribe resources. and use can vary greatly. • Monitor the blade. Important: The values for performance. but a VM may be running at 50%.Architecture overview The following are deployment guidelines for the virtual machines: • Deploy the virtual appliances on the same host as possible. • Create a tiered or segmented cluster infrastructure that isolates critical applications. • Segment redundant elements on a different cluster. host. Over-subscribing causes performance problems.

Chapter 3: Planning and configuration Planning As an Avaya customer.0 and any of its updates. See Registering for PLDS on page 29. which is associated with the Sold-To number that identifies the location where you want to install SAL Gateway. To log on to the PLDS website. See Server hardware and resources on page 15. 3 Ensure that you have all the required hardware for the VMware environment. The VMware-certified servers must be running ESXi 5.1 and any of its updates.com/resources/guides. I/O. Server hardware and resources VMware offers certified compatibility guides which list System. 2 Download the SAL Gateway OVA file from PLDS.html to view the VMware certified Compatibility Guides and the Product Interoperability Matrixes. or ESXi 5. 4 Ensure that you plan the staging and verification activities and the virtualization environment has enough resources to be assigned for the SAL Gateway vAppliance.avaya.com. SAL Gateway in the Virtualized Environment Deployment Guide April 2013 15 . ensure that you complete the following before deploying the SAL Gateway open virtual application (OVA): # Action Notes 1 Register for the Avaya Product Licensing and Delivery System (PLDS) website at https:// plds. See SAL Gateway virtual machine resource requirements on page 16. use your Avaya Single Sign On (SSO) login.vmware. Storage/SAN and Backup compatibility with VMware Infrastructure See http://www.

In case of CPU resource limitations. and stability of the SAL Gateway virtual machine. Modifying these allocated resources could have a direct impact on the performance. CPU reservations are assigned to the vAppliance through the OVA.com April 2013 . Important: Do not modify any other resource settings. the deployed virtual machine may not boot correctly. the virtual machine must meet these resource size requirements. you can adjust the virtual machine properties. for example. capacity.Planning and configuration Important: You must configure the time and NTP settings on each ESXi server before you deploy and configure the OVA. Removing or downsizing reservations could put this requirement at risk. VMware Resource Value vCPU 2 CPU speed 2 GHz Memory 2 GB Storage reservation 40 GB Shared NIC 1 @ 1000 Mbps You might deploy the SAL Gateway vAppliance on a host that does not have the resources to allocate to the virtual machine for starting the virtual machine. and you might have to lower the CPU speed more. For SAL Gateway to perform at maximum capacity. These resources are specified in the SAL Gateway OVA. To run at full capacity. Avaya recommends that you adjust the resource allocation for the virtual machine to have 2 vCPUs with CPU speed of 2 GHz or higher. the CPU adjustments might not correct the start-up conditions. For a specific server speed. You can adjust other virtual machine resources as required. the system displays the Insufficient capacity on each physical CPU. Otherwise. SAL Gateway virtual machine resource requirements The SAL Gateway virtual machine requires the following minimal set of resources to be available on the ESXi host for deployment. Related topics: Editing the virtual machine resources on page 17 16 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya. To correct this limitation. or some similar message after the start-up request. In some cases. downsizing of allocated resources.

1. The SAL Gateway VMware virtualization environment is packaged as a vAppliance ready for deployment on VMware-certified hardware.1.1.0 or ESXi 5. Procedure 1. Right click the virtual machine. ESXi 5.0 or ESXi 5.0 and vCenter Server 5. 2.php to view compatibility with other solution releases.vmware. See VMware Product Interoperability Matrixes at http://partnerweb. including CPU.0 or 5. For CPU limitations. On the Virtual Machine Properties window.com/comp_guide2/sim/interop_matrix. SAL Gateway vAppliance currently does not support VMware vSphere 4. VMware software requirements For optimal results. as required. and select Edit Settings. 4. Adjust the other resource allocations. Software requirements SAL Gateway uses the current release. use the following VMware software versions: • VMware vSphere Client ESXi 5.1.2. Disk. Alternatively. 3. SAL Gateway in the Virtualized Environment Deployment Guide April 2013 17 . The tab displays the virtual machine resources. enter the exact number into the Reservations field.1 • VMware vCenter Server ESXi 5. of software as the standard release of SAL Gateway vAppliance on VMware vSphere 5. and Advanced CPU.1 ESXi 5. Memory. However. 2.0 can be added under vCenter Server 5. Click OK. select the Resources tab.1 can be added only under vCenter Server 5. select CPU from the left pane and adjust the CPU reservation to an appropriate number so that the virtual machine can function properly. 5.VMware software requirements Editing the virtual machine resources About this task Use this procedure to adjust the virtual machine resources if the host does not have enough resources to allocate according to the reservations that are specified in the OVA.

0. build 860230 VMware ESXi Host 5. and other required software components.0.0.0. the alarm flow.0.0. build 799733 VMware Tools 8.0.6. build 426873 Specifications of bundled software in the OVA The SAL Gateway OVA contains the application software. To run at full capacity. operating system.0_33 Application software SAL Gateway 2. and network conditions must the normal.0.1. For the capacity matrix of a standalone SAL Gateway.2. build 623860 5.24 Capacity of SALGateway in a virtualization environment The capacity of SAL Gateway VMware virtualization environment is the same as the capacity of a standalone SAL Gateway.6. the virtual machine must meet the required specifications and the resource allocation.8. Also.2.0. build 880146 VMware vSphere Client 5.com April 2013 . see Implementing Secure Access Link Gateway 2. remote sessions.0.Planning and configuration The following table lists the required software and the supported versions for the SAL Gateway VMware virtualization environment. Operating system CentOS 5. Equipment Software versions VMware vCenter Server 5.0. along with preinstalled VMware tools.1.1. build 623373 5. The following are the specifications of the software components included as part of the SAL Gateway OVA.0. 64-bit Java Oracle JRE 1. build 623373 5. 18 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya.6261.

see the Best Practices for Performance Tuning of Latency-Sensitive Workloads in vSphere VMs technical white paper at http://www. see Performance Best Practices for VMware vSphere 5.Chapter 4: VMware best practices for performance The following sections define the required best practices for the SAL Gateway virtualization environment.com/files/pdf/techpaper/VMWTuning-Latency-Sensitive-Workloads. The following are the best performance BIOS settings for a few specific servers from the VMware-certified server list.1. For standard virtualization best practices for VMware vSphere 5. For standard virtualization best practices for VMware vSphere 5. Consult the manufacturer technical data for your particular server. Related topics: Intel Virtualization Technology support on page 19 Dell PowerEdge Servers — BIOS settings on page 20 HP ProLiant Servers — BIOS settings on page 20 Intel Virtualization Technology support Intel CPUs require EM64T and Virtualization Technology (VT) support in the chip and in the BIOS to run 64–bit virtual machines. turn off power-saving server options for optimal performance. BIOS For details on BIOS settings to improve the environment for latency-sensitive workloads for an application.vmware.0.1. see Performance Best Practices for VMware vSphere 5.pdf. In general. All Intel Xeon processors feature: • Intel Virtualization Technology • Intel Extended Memory 64 Technology • Execute Disable Bit SAL Gateway in the Virtualized Environment Deployment Guide April 2013 19 .0.

com April 2013 . Virtualization Technology. The host server will reboot. These settings depend on the OEM make and model of the server. set C States to disabled. After enabling VT in the system BIOS. Do not change the default. • Disable Processor C-State Support. you select F2 to display the system setup options. The feature may be called VT. Note: The VT setting is locked (either on or off) at boot time. • Enable Intel Turbo Boost. Dell PowerEdge Servers — BIOS settings When the Dell server starts. set Turbo Mode to enable. Vanderpool Technology. • Disable QPI Power Management. • Disable Processor C1E Support. • Intel Turbo Boost steps up the internal frequency of the processor if the workload requires more power. • Disabling C-states lowers latencies to activate the CPUs from halt or idle states to full power on. • Under Processor Settings. The BIOS parameter terminology for current Dell and HP servers are described in the following sections. and the BIOS changes will take effect. Other server make and models may have other terminology but equivalent BIOS controls. • Under Processor Settings. 20 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya. or Virtual Machine Extensions.VMware best practices for performance Ensure that VT is enabled in the host system BIOS. The following are the recommended BIOS settings for the Dell PowerEdge servers: • Set the Power Management Mode to Maximum Performance. save your changes to the BIOS settings and exit. HP ProLiant Servers — BIOS settings The following are the recommended BIOS settings for the HP ProLiant servers: • Set the Power Regulator Mode to Static High Mode. Other suggested BIOS settings Servers with Intel Nehalem class and newer Intel Xeon CPUs also offer two power management options: C-states and Intel Turbo Boost. VMX. The default for this option is enabled. • Set the CPU Power and Performance Management Mode to Maximum Performance.

The tools provide: • VMware Network acceleration • Host to Guest time synchronization • Disk sizing • Startup/Shutdown For more information. the guest administrator must manually set the guest clock to be the same or as close as possible to the network time source clock. after vMotion. If this view is very different from that received over the network (over 1000 seconds). run the command /usr/bin/vmware-toolbox-cmd timesync status. The NTP servers can be local to the LAN or over the Internet. You must configure the NTP service first because the applications are not receiving clock updates from the hypervisor. the corporate firewall must open UDP port 123 so that NTP service can communicate with the external NTP servers. use the Network Time Protocol (NTP) as a time source instead of the ESXi hypervisor.vmware. In special situations. VMware tools time synchronization is disabled at application deployment time to avoid dueling clock masters. To keep the NTP service active. the ESXi hypervisor will push an updated view of its clock into a virtual machine. If the NTP servers are on the Internet. The supplied version is the supported release and has been thoroughly tested. To verify VMware Tools Timesync is Disabled. the clock SAL Gateway in the Virtualized Environment Deployment Guide April 2013 21 .com/kb/340. Important: Do not update the VMware tools software which is packaged with each OVA unless instructed to do so by Avaya. In this situation. The tools are a suite of utilities that enhances the performance of the guest operating system on the virtual machine and improves the management of the virtual machine. the NTP service might not adjust to the network time and shutdown.VMware Tools VMware Tools VMware Tools are included as part of the application OVA. see Overview of VMware Tools at http://kb. such as powering up the virtual machine. Time keeping For accurate time keeping. and after resuming a suspended virtual machine.

The SAL Gateway virtual machine has an NTP service running that you can configure to synchronize with an external NTP server. configuration of VMware Tools time synchronization. and Virtual Hardware Clock configuration to achieve best timekeeping results. If the time source is local. you must configure the Domain Name Service in the guest before administering the NTP service. For more information.conf file so that the NTP can adjust to the network time even with large differences. Important: To maintain the system time of the SAL Gateway virtual machine. These recommendations include specifics on the particular kernel command line options to use for the Linux operating system of interest. 22 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya. and how often the guest checks the time. The NTP service writes the activities it performs to the log. you must configure NTP on the SAL virtualized environment. see Timekeeping best practices for Linux guests at http:// kb.com/kb/1006427. look through the system log for entries regarding ntpd. including when it loses synchronization with a network time source. Timekeeping is also important for managing and isolating alarms that SAL Gateway forwards. Related topics: Configuring timing on page 22 Configuring timing The SAL Gateway virtual machine relies on NTP for timekeeping. The results indicate which network time source is being used.com April 2013 .VMware best practices for performance on the ESXi host must also use an accurate clock source. Otherwise. such as the same network time source that is used by the guest. The VMware recommendation is to add tinker panic 0 to the first line of the ntp. then the NTP service is not using a network time source and a problem exists. If the clock value seems to be consistently wrong. The guest polls the time source between every 65 and 1024 seconds. About this task Use this procedure to configure the NTP service on the SAL Gateway virtual machine. you must restart the NTP service after administering the DNS service. the NTP service will not be able to locate the time servers.vmware. After you administer the NTP service in the application. run the ntpstat or /usr/sbin/ntpq -p command from a command window to verify the NTP service is getting time from a network time source. The article presents best practices for Linux timekeeping. Larger time intervals indicate that the guest clock is tracking the network time source closely. There is also a description of the recommended settings and usage for NTP time sync. If you use the names of the time servers instead of the IP address in setting the NTP configuration. If the NTP service is administered first. how close the guest is to the network time.

org 1. 5. Open the /etc/ntp. comment out the following lines: server server server 0.127.ntp.pool.centos.ntp.0 # local clock fudge 127. add the NTP servers for time synchronization as the following: server <IP/hostname> server <IP/hostname> 8.1. After those lines.1. 10. Save and close the /etc/ntp. VMware networking best practices You can have many different configurations for networking in a VMware environment.VMware networking best practices Procedure 1.pool. Log in as admin. Run the following command to stop the NTP service: service ntpd stop 4. 3.conf file in a text editor.0 stratum 10 9.conf file. Add the following line at the top of the file: tinker panic 0 6.127. This section is not a substitute for the actual VMware documentation. you must review the VMware networking best practices before deploying any applications on an ESXi host.centos. you must configure the corporate firewall to open the UDP port 123 so that the NTP service can communicate with the external NTP servers. If you do not have experience with VMware networking. Connect to the virtual machine through an SSH client. Run the following command to start the NTP service: service ntpd start Next steps If the NTP servers are on the Internet. The information in this section includes a number of best practices and recommendations from the perspective of Avaya. The following are the suggested best practices for configuring a network that supports applications deployed on VMware hosts: SAL Gateway in the Virtualized Environment Deployment Guide April 2013 23 .centos. If you do not want to use the CentOS NTP servers.org 2. Comment out the following two lines: server 127. and switch to the root user. 2.pool.ntp.org 7.

thin virtual disks can grow to fill an entire datastore if left unchecked.ova files are built using vmxnet3 by default. • To protect sensitive VMs.com April 2013 . You can use thin provisioned disks. thick deployments The general recommendation is to deploy thick disks which are lazy-zeroed. it is not uncommon for the deployment operation to time out and fail. • Connect all physical NICs that are connected to the same vSphere standard or distributed switch to the same physical network.jsp?topic= %2Fcom.1 VMware vSphere Basics http://pubs. • Configure the vMotion connection in such as way that the connection is located on a separate network that is devoted to vMotion.com/vsphere-50/index. 24 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya.VMware best practices for performance • Create a vSphere standard or distributed switch with dedicated NICs for each service to achieve greater security and performance.introduction. If separate switches are not possible. but each block is zeroed only on the first write.vmware.doc_50%2FGUI D-F7A7E6C0-FA25-4806-8921-0438F1B2AEAE. If the storage is over-allocated.vmware.html Thin vs.0 Performance Best Practices for http://www. • has a longer disk creation time.pdf VMware vSphere™ 5. Avaya . Some configurations require eager-zeroed thick disks.0. A lazy-zeroed thick disk has all of the space allocated at the time of creation.com/pdf/ Perf_Best_Practices_vSphere5. Thin provisioned disks can over-allocate storage. deploy firewalls in the VM that route between virtual networks with uplinks to physical networks and pure virtual networks with no uplinks to physical networks.vmware.vmware. An eager-zeroed thick disk • has all space allocated and zeroed out at the time of creation.com/pdf/ ® Perf_Best_Practices_vSphere5. even on the first write to each block. use port groups with different VLAN IDs. The result is a shorter creation time but reduced performance the first time a block is written.pdf VMware vSphere 5. • Configure all VMkernal vNICs to the same IP Maximum Transmission Unit (MTU). References Title Link Performance Best Practices for http://www. • Specify VM NIC hardware type vmxnet3 for best performance.vsphere. • results in the best performance. Because of the extra time required to deploy an eager zero disk.1.

do not save the memory of the virtual machine.Best practices for VMware features but you must use strict control and monitoring to maintain adequate performance and ensure that storage is not completely consumed. • Do not run a virtual machine off of a snapshot. the application can then be restarted or brought back into service. If operational procedures are in place to mitigate the risk of performance and storage depletion. Following the recommended actions prevents snapshots from growing so large as to cause issues when deleting or committing the snapshots to the original virtual machine disks. Snapshots are not backups. A snapshot is useful as a short-term fallback for patching and upgrading the system. and delete or commit the snapshot as soon as the virtual machine is verified to be working properly. When the snapshot operation has completed. The application that is running on the virtual machine must be stopped or set to out-of-service before you perform a snapshot operation. • affect service. The length of time the host takes to write the memory onto the disk is relative to the amount of memory the virtual machine is configured to use and can add several minutes to the time it takes to complete the operation. • affect performance. The snapshot file is only a change log of the original virtual disk. consider the following recommendations when using the Snapshot feature. then thin disks are a viable option. Caution: Snapshot operations can adversely affect service. • When taking a snapshot. The recommended actions are to take the snapshot. Due to the adverse behaviors. make the changes to the virtual machine. Snapshots can: • consume large amounts of data resources. Do not use a single snapshot for more than 24-72 hours. • Do not rely on VMware snapshots as a robust backup and recovery method. • cause increased CPU loads on the host. saving memory will make calls SAL Gateway in the Virtualized Environment Deployment Guide April 2013 25 . Best practices for VMware features VMware Snapshots A snapshot preserves the state and data of a virtual machine at a specific point in time. If the snapshot is activated.

If you have configured VMware HA on the ESXi host on which a SAL Gateway virtual machine is installed.VMware best practices for performance appear to be active or in progress and can cause confusion to the user.x Consolidating snapshots in vSphere 5.uncheck the Snapshot the virtual machine’s memory check box in the Take Virtual Machine Snapshot window. 26 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya. you must first delete stored snapshots. a warning is displayed in the UI. make sure that you: . Related resources Title Web page Best practices for virtual machine snapshots Best Practices for virtual machine snapshots in the VMware environment in the VMware environment Understanding virtual machine snapshots in Understanding virtual machine snapshots in VMware ESXi and ESX VMware ESXi and ESX Working with snapshots Working with snapshots Configuring VMware vCenter Server to send Send alarms when virtual machines are alarms when virtual machines are running running from snapshots from snapshots Consolidating snapshots in vSphere 5. failure of this ESXi host results in SAL Gateway vAppliance being moved to a standby ESXi host. Before merging the snapshot delta disks back into the base disk of the virtual machine. When creating a snapshot. end-users can use the actual Consolidate option without opening a service request with VMware. you must consolidate the snapshot files on a regular basis to improve performance and reduce disk usage. Note: In the event of a consolidate failure. . • If you are going to use snapshots over a long period of time. SAL Gateway resumes to provide all the usual features and services.x VMware High Availability VMware High Availability (HA) is a viable option for SAL recovery in the VMware environment.com April 2013 . If a commit or delete operation does not merge the snapshot deltas into the base disk of the virtual machine. After the cold boot of SAL Gateway on the standby ESXi host is complete. It gives a better chance of creating a clean snapshot image from which to boot.select the Quiesce guest file system (Needs VMware Tools installed) check box to make sure all writes to the disks have completed.

VMware vMotion VMware uses the vMotion technology to migrate a running virtual machine from one physical server to another physical server without incurring downtime. you can • schedule migration to occur at predetermined times and without the presence of an administrator. iSCSI SAN. • Ensure identical Port Groups for vMotion. also known as a hot-migration. and complete transaction integrity. see the VMware® ESXi host documentation. the console network must have redundant network paths. • Ensure that you have identical vSwitches. With vMotion. You must enable vMotion on these vSwitches. • perform hardware maintenance without scheduled downtime. The migration process. • Use a dedicated NIC to ensure the best performance.Best practices for VMware features Keep the following points in mind while configuring to use VMware HA: • All virtual machines and the configuration files of the virtual machine must be on a shared storage. • VMware HA uses the virtual machine priority to decide the order of restart. SAL Gateway in the Virtualized Environment Deployment Guide April 2013 27 . enables the live migration of running virtual machines with zero downtime. continuous service availability. • To have reliable failure detection for HA clusters. such as Fibre Channel SAN. note the following: • Ensure that each host that migrates virtual machines to or from the host uses a licensed vMotion application and the vMotion is enabled. Before using vMotion. For the procedure to enable hyperthreading. • migrate virtual machines away from failing or under-performing servers. Hyperthreading VMware® recommends that you enable hyperthreading on the ESXi host as hyperthreading can enhance the processor performance. Hyperthreading is enabled by default on the ESXi host. or SAN iSCI NAS. The reason is that VMware HA monitors the heartbeat between hosts on the console network for failure detection.

VMware best practices for performance 28 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya.com April 2013 .

Avaya will send you the PLDS access confirmation within one business day. If you are registering: • as an Avaya Partner. 3.com also.Ship-To number . The PLDS registration page is displayed.avaya. send an e-mail to prmadmin@avaya. Click Submit.Company Sold-To .com. • as a customer. 2.Chapter 5: Initial setup and pre-deployment Downloading the SAL Gateway OVA Registering for PLDS Procedure 1. Downloading software from PLDS About this task Note: You can download product software from http://support.avaya. Log in to SSO with your SSO ID and password. The PLDS Web site redirects you to the Avaya single sign-on (SSO) Web page. SAL Gateway in the Virtualized Environment Deployment Guide April 2013 29 .License authorization code (LAC) 4. Go to the Avaya Product Licensing and Delivery System (PLDS) Web site at https:// plds. enter the Partner Link ID. enter one of the following: . If you do not know your Partner Link ID.com.

Initial setup and pre-deployment Procedure 1. Click the download icon from the appropriate download. PLDS displays the downloads again with a checkmark next to the downloads that are completed successfully. you must notify Avaya Registration Team and provide the appropriate product information. install Active X. 2. 3.com in your Web browser to go to the Avaya PLDS website. 30 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya. When the system displays the security warning. When the system displays the confirmation box. You require these identifiers to install the SAL Gateway virtual machine software. When the installation is complete. Select View Downloads. Type http://plds. Registering the SAL Gateway virtual machine Registering a product with Avaya is a process that uniquely identifies the product so that Avaya can provide service to the product.avaya. If you receive an error message. click Install. select Assets. 5. select Click to download your file now. About this task Use this procedure to register a SAL Gateway virtual machine with Avaya and to obtain the unique identifiers prior to the SAL Gateway virtual machine implementation. click on the message. On the Home page. 9.com April 2013 . When you register a new SAL Gateway. Using these IDs. Avaya assigns a Solution Element ID (SEID) and a Product ID to the SAL Gateway. 4. Avaya can uniquely identify the SAL Gateway at your location. To register a product. Search for the available downloads using one of the following methods: • By actual download name • By selecting an application type from the drop-down list • By download type • By clicking Search Downloads 6. 8. and continue with the download. 7. Enter your Login ID and password to log on to the PLDS Web site.

SAL Gateway in the Virtualized Environment Deployment Guide April 2013 31 . If you completed Step 2 of the registration form. 3. Avaya sends you an email message with the following information: • The SEID and the Product ID of the new SAL Gateway. • Submit the registration form after completing Step 2 for the added managed devices. complete Step 1 of the form. Next steps • Implement the SAL Gateway virtual machine. On the form. • Customer contact information. • Add managed devices to your SAL Gateway using the SEIDs provided to you in Step 1 and Step 2 of the registration form. enter the following information: • Customer name. • A list of other FLs for your company. You require these identifiers to install SAL Gateway. Send the registration form to salreg@avaya.com using the link provided on the form.Registering the SAL Gateway virtual machine Procedure 1. Avaya sends you a list of SEIDs and Product IDs of the devices installed in the locations you selected. • A list of Avaya devices currently registered at the same location. complete Step 2 of the registration form. so that Avaya can contact you for sending the IDs or for any queries. • Avaya Sold-To number or customer functional location (FL) number that identifies the location where you want to install SAL Gateway. When the registration is complete. Using the Secure Access Link Registration Form that is available with the software download. 2. (Optional) To obtain SEIDs of registered devices from other functional locations. Result Avaya uses this information to register the new SAL Gateway.

com April 2013 .Initial setup and pre-deployment 32 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya.

Chapter 6: Deploying the SAL Gateway OVA SAL Gateway OVA deployment overview The SAL Gateway OVA supports two models of deployment on a VMware vSphere 5. # Action Link/Notes 1 Ensure that the ESXi host server is ready. You receive these IDs after you register SAL Gateway with Avaya. 3 Deploy the OVA.1 environment: • vCenter deployment through a vSphere client • Direct deployment to the ESXi server through a vSphere client Based on the VMware environment you have. See Deploying the SAL Gateway OVA directly to the ESXi server on page 40 or Deploying the SAL Gateway OVA to vCenter on page 34. SAL Gateway in the Virtualized Environment Deployment Guide April 2013 33 . Deployment checklist Use the following checklist for deploying the SAL Gateway vAppliance. For more information.0 or 5. 2 Ensure that you have the Solution Element ID and the Product ID for SAL Gateway. select one of the two methods of deployment. see Registering the SAL Gateway virtual machine on page 30.

and click Next. enter the full URL in the Deploy from a file or URL field. Click Next. In the vCenter deployment. and click Next. • If the OVA file is located on an HTTP server. If the host or cluster has resource pools.Deploying the SAL Gateway OVA Deploying the SAL Gateway OVA to vCenter If you have a vCenter server to administer your VMware infrastructure. b. 2. Perform the following to specify the location for the deployment: a. and click Next: • If the OVA file is downloaded at a location accessible from your computer. select the inventory location to deploy the virtual machine. and click Next. select the data store location to store the virtual machine files. Click Next. Select the resource pool you want to use. 3. 7. In the OVF Template Details window. Select the host or cluster where you want to deploy the virtual machine. e. type a unique name for the new virtual machine. in the Name field. d. 6. the wizard displays the Host/Cluster window. Connect to the vCenter server through the vSphere client. and click Accept.com April 2013 . c. In the Name and Location window. 34 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya. Procedure 1. In the Storage window. 8. verify the details about the SAL Gateway OVA template. you get the options to provide the SAL Gateway configuration information through the deployment wizard windows. From the Inventory Location field. Select File > Deploy OVF Template. read the license agreement. 4. In the Deploy OVF Template window. use this procedure to deploy the SAL Gateway OVA to your VMware infrastructure. 5. If you did not select a host when you started the deployment process. the wizard displays the Resource Pool window. In the End User License Agreement window. perform one of the following to select the OVA file. and click Next. click Browse to select the location.

In the Network Properties section of the Properties window. In the Disk Format window. Thick Provision Lazy Zeroed. accept the default disk format. which allocates the required 40-GB disk space for the SAL Gateway virtual machine. complete the following fields according to your network settings: • Default Gateway SAL Gateway in the Virtualized Environment Deployment Guide April 2013 35 . In the Properties window. complete the following fields for configuring the SAL Gateway parameters: • Timezone setting • Hostname • Solution Element ID • Alarm ID • Platform Qualifier • Primary Destination Core • Port • Secondary Destination Core • Port • Primary Destination Remote • Port • Secondary Destination Remote • Port • (Optional) Proxy Type • (Optional) Proxy Hostname • (Optional) Proxy Port • (Optional) Proxy User • (Optional) Proxy Password • (Optional) Policy Server Hostname • (Optional) Policy Server Port • Master Agent Hostname • Master AgentX Port • Role b. perform the following to configure the SAL Gateway specifications: a. In the Application section of the Properties window. 10. see Thin vs. and click Next.Deploying the SAL Gateway OVA to vCenter 9. thick deployments on page 24. For information about virtual disk.

the deployment process might take more time. where n is a digit from 0 through 9. 13. select the Power on after deployment check box to automatically start the virtual machine after the deployment. SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya. Related topics: Starting the SAL Gateway virtual machine on page 43 Properties field descriptions The following table provides the descriptions of the fields available in the Application section of the Properties page. see Properties field descriptions on page 36. 11. (Optional) In the Ready to Complete window. Avaya Services or Avaya Partners can uniquely identify and connect to this SAL Gateway. verify the deployment properties settings. Hostname The host name of the SAL Gateway virtual machine. Name 36 Description Timezone setting The appropriate time zone for the location where you deploy the SAL Gateway virtual machine. and click Finish. Next steps If you did not select the option to start the virtual machine automatically. 12. The deployment process takes about 10 to 12 minutes to complete.com April 2013 . Click Next. Using this ID.Deploying the SAL Gateway OVA • DNS • Network 1 IP Address • Network 1 Netmask For more information about the fields. start the virtual machine. If you do not select this check box. you can manually start the virtual machine after the deployment. You must replace the default value with the Solution Element ID you receive from Avaya. Solution Element ID A unique identifier in the format (nnn)nnn-nnnn. If the OVA file location is an HTTP server. In the Ready to Complete window.

the remote access and product alarm functionalities through SAL Gateway are affected. The default value is secure. the remote access and product alarm functionalities through SAL Gateway are affected. Otherwise. The Product ID is included in alarms that are sent to alarm receivers from the managed device. If you have a local Concentrator Core Server or one at a partner location. which is used to communicate with the Concentrator Core Server located at Avaya. you must retain the default value to communicate with Avaya. this SAL Gateway.alarming. assigned to a device. you must enter the value as 8443.Properties field descriptions Name Description Otherwise. For the Avaya Concentrator Core Server. Do not change the default value unless you receive instructions to do so. The default platform qualifier is Enterpriseproduction. Alarm ID A unique 10-character ID. For a local Concentrator Core Server. You can modify the Solution Element ID and the Product ID information later through the SAL Gateway user interface (UI). Primary Destination Core The host name of the Concentrator Core Server that SAL Gateway first contacts. for example. Port The port number for the primary Concentrator Core Server. The default port is 443. you must enter the host name or the IP address of that server.avaya. you must retain the default value. Note: Register your SAL Gateway before you perform the deployment so that you have the Solution Element ID and Product ID ready for the deployment. Platform Qualifier An alphanumeric string to establish a channel for communication between SAL Gateway and Secure Access Concentrator Core Server. Otherwise. Avaya uses the Alarm ID to identify the device that generated the alarm. You receive this ID after you register SAL Gateway with Avaya. also called Product ID. You must replace the default value with the Product ID you receive from Avaya. SAL Gateway in the Virtualized Environment Deployment Guide April 2013 37 . You receive this ID after you register SAL Gateway with Avaya.com.

Port The port number of the secondary destination.com. Primary Destination Remote The host name or IP address of the primary Secure Access Concentrator Remote Server that requests and facilitates remote access for service personnel. The default value for this field is secure. 38 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya.avaya. Port The port number of the primary Secure Access Concentrator Remote Server. accept the default value. The options are: • HTTP: For an HTTP proxy without authentication. The default value is 443.com. The default value is 443. where sl1 has a lower case letter L and then the number 1 following the letter s. Note: If you do not have a secondary server. This field is required only if you use a proxy server for Internet access outside the firewall of your network. Note: If you do not have a secondary server. • SOCKS: For a SOCKS proxy without authentication. • Authenticated HTTP: For an HTTP proxy with authentication.avaya. Port The port number for the secondary Concentrator Core Server. accept the default value.avaya.sal.sal.alarming. Secondary Destination Remote The host name or IP address of the secondary Concentrator Remote Server.Deploying the SAL Gateway OVA Name Description Secondary Destination Core The host name of the secondary Concentrator Core Server.com April 2013 . Proxy Type (Optional) The type of channel that the SAL Gateway virtual machine uses to communicate with the servers outside your network. The default value is sl1.com. The default value is sl1. The default value for this field is 443.

If you have not configured an SNMP master agent before the OVA deployment. You can add the Policy Server information later through the SAL Gateway user interface (UI). Proxy Port (Optional) The port number of the proxy server. • Deny: Without access to the SAL Gateway UI. Role The role or permission level of the Avaya support personnel to the SAL Gateway UI. For information about SNMP master agent configuration.Properties field descriptions Name Description Proxy Hostname (Optional) The host name or IP address of the proxy server. Policy Server Port (Optional) The port number that Policy Server uses for communication with SAL Gateway. Master Agent Hostname The host name or IP address of the SNMP master agent to which the SNMP subagent must connect. This field is required only if the proxy type is authenticated HTTP.1. This field is required only if the proxy type is authenticated HTTP. you must update the SNMP master agent information on the SAL Gateway UI after you complete OVA deployment. Proxy Password (Optional) The password for the authenticated HTTP proxy. Master AgentX Port The AgentX listener port number of the SNMP master agent. see Implementing Secure Access Link Gateway. The following table provides the descriptions of the fields available in the Network Properties section of the Properties page. • Browse: With the read-only access to all pages.0. The use of Policy Server is optional. This field is required only if you have a proxy server for Internet access outside your network. The default value is 127.0. Proxy User (Optional) The user name for the authenticated HTTP proxy. SAL Gateway in the Virtualized Environment Deployment Guide April 2013 39 . Avaya support personnel can have one of the following roles: • Administrator: With full permissions to all the SAL Gateway UI pages except a few. Policy Server Hostname (Optional) The host name or the IP address of Policy Server installed on your network.

DNS The comma-separated addresses of the Domain Name Servers (DNS) for the virtual machine. verify the details about the SAL Gateway OVA template. 40 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya. Network 1 Netmask The netmask or prefix for the network interface. and click Next. During this direct deployment. You can leave this field blank if you plan to use DHCP. You can leave this field blank if you plan to use Dynamic Host Configuration Protocol (DHCP). On the OVF Template Details window. Select File > Deploy OVF Template. you cannot configure the SAL Gateway parameters. the console displays a series of prompts to set the SAL Gateway parameters.com April 2013 . Connect to the ESXi host server through the vSphere client. click Browse to select the location. After the deployment. Procedure 1. 5. • If the OVA file is located on an http server. Network 1 IP Address The IP address of the network interface. Click Next. 2. 3. You can leave this field blank if you plan to use DHCP. when you start the SAL Gateway virtual machine console for the first time. enter the full URL in the Deploy from a file or URL field. 4. You can leave this field blank if you plan to use DHCP. perform one of the following to select the OVA file: • If the OVA file is downloaded at a location accessible from your computer. Deploying the SAL Gateway OVA directly to the ESXi server Use this procedure to deploy the SAL Gateway OVA directly to the ESXi server through a vSphere client.Deploying the SAL Gateway OVA Name Description Default Gateway The IP address of the default gateway on your network. On the Deploy OVF Template window.

On the Ready to Complete window.Deployment of cloned and copied OVAs 6. select Do not customize. If you are making a clone of an Avaya application. do not perform any Guest Customization. type a unique name for the new virtual machine. which allocates the required 40-GB disk space for the SAL Gateway virtual machine. On the Disk Format window. However. accept the default disk format. 9. deploy a new OVA. If the OVA file location is an http server. and click Next. and click Next. start the virtual machine. The deployment process takes about 10 to 12 minutes to complete. and click Next. you can create a copy of the virtual machine or clone the virtual machine. Thick Provision Lazy Zeroed. If you do not select this check box. thick deployments on page 24. if you are making a clone of an Avaya application. and configure the SAL Gateway parameters. With cloning. 8. select the Power on after deployment check box to automatically start the virtual machine after the deployment. To avoid any complexities and unexpected behavior. 10. Next steps If you did not select the option to start the virtual machine automatically. (Optional) On the Ready to Complete window. verify the deployment settings. 7. you can manually start the virtual machine after the deployment. Related topics: Starting the SAL Gateway virtual machine on page 43 Configuring the SAL Gateway and the network parameters on page 45 Deployment of cloned and copied OVAs To re-deploy a virtual machine. Start the SAL Gateway virtual machine console. For information about virtual disk. SAL Gateway in the Virtualized Environment Deployment Guide April 2013 41 . On the Name and Location window. click Accept. Installing a guest operating system and applications can be time consuming. On the End User License Agreement window. and click Finish. These processes have subtle technical details that require a thorough understanding of the effects of these approaches. see Thin vs. read the license agreement. in the Name field. the deployment process might take more time. you can make several copies of a virtual machine from a single installation and configuration process.

Deploying the SAL Gateway OVA 42 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya.com April 2013 .

SAL Gateway in the Virtualized Environment Deployment Guide April 2013 43 . The system starts the system services and the SAL Gateway services. the system displays a message to log in to the virtual machine. In the vSphere client. and click Open Console. right-click the virtual machine.Chapter 7: Initial configuration Starting the SAL Gateway virtual machine Use this procedure to start the virtual machine. the VMware HA software ignores the Startup selections. select the host where the virtual machine is located. In the vSphere Client inventory. In the Software section. 2. click Virtual Machine Startup/Shutdown. In high availability (HA) clusters. 2. After the startup process is complete. the system displays messages to set the SAL Gateway parameters and the network parameters whenever you start the virtual machine. Procedure 1. The default is set to no. In the vSphere client. Click the Configuration tab. Procedure 1. right click the virtual machine. and click Power > Power On. Result The console displays the system startup messages. If you deploy the virtual machine directly on the ESXi host server. Configuring the virtual machine automatic start and stop settings Configure the virtual machine to start automatically after a power failure or a restart of the hypervisor. 3.

44 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya. In the System Settings section. Click OK. Use the Move up button to move the virtual machine under Automatic Startup. Click Properties in the upper right corner of the screen. Example The following is an example of the Virtual Machine Startup/Shutdown screen. select the virtual machine. select Allow virtual machines to start and stop automatically with the system.Initial configuration 4. 5.com April 2013 . 8. 6. 7. In the Manual Startup section.

If required. you get the options to reconfigure the virtual machine. You can either proceed with the configuration or skip the configuration. As a part of the startup. At the appropriate system prompts. 2. At the system prompt. open the virtual machine console. Note: Set the IP address and netmask before entering the default gateway information for the virtual machine. 3. • The hostname of the virtual machine. To accept the default values.Configuring the SAL Gateway and the network parameters Configuring the SAL Gateway and the network parameters If you deploy the SAL Gateway virtual machine directly on an ESXi host server. the system prompts you to configure the SAL Gateway vAppliance. complete the following SAL Gateway parameters. After you start the virtual machine for the first time. • The proxy server information. select the time zone for the SAL Gateway virtual machine. you must configure the network and the SAL Gateway parameters when you start the virtual machine for the first time. 4. • The IP address allocated to the virtual machine. Procedure 1. • The domain name server (DNS) information. select the appropriate option in the configuration wizard to change the following network settings: • The IP address of the default gateway on your network. press Enter at each prompt: • SAL Gateway Solution Element ID • SAL Gateway Alarm ID • Platform Qualifier • Primary Destination Core Server • Primary Destination Core Server Port • Secondary Destination Core Server • Secondary Destination Core Server Port SAL Gateway in the Virtualized Environment Deployment Guide April 2013 45 . At each subsequent restart of the virtual machine that was deployed directly on an ESXi host.

46 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya. select the role to be assigned to Avaya service personnel. see Properties field descriptions on page 36. the system starts the SAL Gateway services and prompts you to log on to the virtual machine. Result After the SAL Gateway configuration is complete.com April 2013 .Initial configuration • Primary Destination Remote Server • Primary Destination Remote Server Port • Secondary Destination Remote Server • Secondary Destination Remote Server Port • (Optional) Proxy Type • (Optional) Proxy Server Hostname • (Optional) Proxy Server Port • (Optional) Policy Server Hostname • (Optional) Policy Server Port • Master Agent Hostname • Master Agent Port For more information about the fields. The system configures SAL Gateway according to the settings you entered. 6. Confirm the configuration changes. When the system prompts. 5.

remote access. Testing the remote access service of SAL Gateway About this task Use the following procedure to test whether the remote access service of SAL Gateway is running properly. Run the following command. and check the outcome of the command: service axedaAgent status 3. If the service is not running. Testing the alarming service of SAL Gateway Procedure 1. SAL Watchdog. and switch to the root user. are running properly.Chapter 8: Validation of the SAL Gateway implementation You can run a number of tests to validate whether the SAL Gateway implementation is successful. run the following command to start the service: service spiritAgent start 4. 2. Procedure 1. Run the following command. Log on to the SAL Gateway virtual machine as admin. run the following command to start the service: SAL Gateway in the Virtualized Environment Deployment Guide April 2013 47 . Log on to the SAL Gateway virtual machine as admin. The validation involves ensuring that the SAL Gateway services. Check the status again to verify that the service is running properly. 2. If the service is not running. and SAL Gateway UI. and switch to the root user. and check the outcome of the command: service spiritAgent status 3. which include alarming.

In the address bar. Check the status again to verify that the service is running properly. If the service is not running. Testing the Gateway UI About this task You can browse to the SAL Gateway Web interface using a Web browser. run the following command to start the service: service salWatchdog start 4. Check the status again to verify that the service is running properly. Run the following command. From another terminal on the network where SAL Gateway is deployed. type the following URL: https://<IP address of the SAL Gateway virtual machine>:7443 You can replace the host IP with the DNS host name if the host server is registered under DNS.com April 2013 . and check the outcome of the command: service salWatchdog status 3. Testing the SAL Watchdog service Procedure 1. The browser must display the SAL Gateway login page. Log on to the SAL Gateway virtual machine as admin. 2. and switch to the root user. 2.Validation of the SAL Gateway implementation service axedaAgent start 4. Procedure 1. 48 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya. open a Web browser.

the netmask. Modify the properties according to your requirements. On the Edit Settings window. 3. Note: On the Edit Settings window. Power on the virtual machine. 6. Connect to the vCenter server through the vSphere client. To change any SAL Gateway-specific parameters. you can reconfigure the virtual machine at any time. SAL Gateway in the Virtualized Environment Deployment Guide April 2013 49 . the IP Address. Result When the virtual machine boots up. you can modify the time zone and the network settings. 7. select the Options tab. 5.Chapter 9: Reconfiguration of the virtual machine After you deploy the SAL Gateway virtual machine. and click Properties. and the default gateway. the DNS. Shut down the virtual machine. which include the hostname. all the settings are applied automatically. Click OK. and click Edit Settings. Procedure 1. 2. Reconfiguring the virtual machine deployed through vCenter About this task Use this procedure to reconfigure the virtual machine deployed using vCenter. Right click the virtual machine. The reconfiguration procedures differ based on the type of deployment. which can be vCenter deployment or direct ESXi deployment. 4. use the SAL Gateway Web interface.

Connect to the ESXi host server through the vSphere client. you can modify the time zone and the network settings. As part of the startup. use the SAL Gateway Web Interface. To change any SAL Gateway-specific parameters. see Configuring the SAL Gateway and the network parameters on page 45. For more information about the network parameters.com April 2013 . IP Address. you can reconfigure the virtual machine. By following the interactive messages from the script. DNS. a script runs during the boot up process that waits for user inputs. The script waits for your input for 30 seconds before proceeding with the normal boot process. which include hostname. the script skips the reconfiguration of the virtual machine and proceeds with the normal boot process. 2. 4. Note: Using this procedure. If you do not provide any input within 30 seconds. Shut down the virtual machine. 50 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya. and open the virtual machine console. 3. netmask. and default gateway. Start the virtual machine. Follow the interactive messages that the system displays to reconfigure the virtual machine. then at every reboot.Reconfiguration of the virtual machine Reconfiguring the virtual machine deployed directly on an ESXi server If you deploy the SAL Gateway virtual machine directly on an ESXi host. Procedure 1. About this task Use this procedure only when you need to reconfigure the virtual machine deployed directly on an ESXi host server. the system prompts you to configure the virtual machine.

Chapter 10: Backing up and restoring the virtual machine Backup and restore overview You can use the backup and restore capabilities of the SAL Gateway virtual machine for the long-term backup and recovery of the SAL Gateway virtual machine that runs on VMware. you have the responsibility to run the backup at periodic intervals. Copy the backup archive to an external host to prevent loss of data in the event of a system failure. You can find the latest backup archive file at the /vm-data/backup/ archives/ directory. Alternatively. 2. 4. Procedure 1. To copy the file to a remote server. and switch to the root user. or connect to the virtual machine using an SSH client. Open a virtual machine console. Log in as admin. you can schedule a job to run the backup at a periodic interval and copy the backup archive to an external system for preserving the data in the event of a system failure. As the customer. you can use the Linux scp command: SAL Gateway in the Virtualized Environment Deployment Guide April 2013 51 . Backing up the virtual machine About this task Use this procedure to back up the SAL Gateway virtual machine. The archive file is saved with a file name similar to vmbackup_xxxxxxxx. 3. Run the following command: backup The system displays the directory location where the backup archive is saved.gz.tar.

run the following command: restore <Archive_file_path_on_VM> 52 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya. 3.com April 2013 . Start the virtual machine. and switch to the root user. you can use the following: • From a Linux remote system: Use the scp command to copy the file back to the virtual machine. 4. From the virtual machine console. 2. If you are copying the file from a remote system.Backing up and restoring the virtual machine scp <archive_file> <username>@<remote_server_ip>:<directory_path> Restoring a virtual machine About this task Use this procedure to restore a virtual machine from a backup archive. scp <user>@<SAL_VM_IP_or_hostname>:<directorypath_and_filena me_on_remote_system_location> • From a Windows remote system: Use WinSCP or a similar file transfer utility to copy the file back to the virtual machine. Deploy the virtual machine. 5. Procedure 1. Copy the backup archive file to a directory on the virtual machine. Log in to the virtual machine as admin.

4. Next steps Check the network configuration. and copy the backup file to an external host.Chapter 11: Upgrading the SAL Gateway OVA Upgrading the SAL Gateway vAppliance About this task Use this procedure to upgrade to a new version of the SAL Gateway vAppliance. SAL Gateway in the Virtualized Environment Deployment Guide April 2013 53 . and SAL Gateway configuration to validate that the upgrade process is successful. For more information. Start the new SAL Gateway virtual machine. Log in to the new SAL Gateway virtual machine as admin. Shut down the existing SAL Gateway virtual machine. Copy the backup file from the external host to a directory on the new virtual machine. For more information. services. 6. and switch to the root user. 7. see Backing up the virtual machine on page 51. see Restoring a virtual machine on page 52. Take a backup of the existing SAL Gateway virtual machine. You can accept the default values for configuring the virtual machine and the SAL Gateway software as you are going to restore the configuration values from the backup file of the earlier virtual machine. if you have already deployed the Beta version of the SAL Gateway virtual machine. After you validate the upgrade process. Procedure 1. you can remove the earlier virtual machine from the host server. 5. Deploy the new SAL Gateway OVA on an ESXi host server. you can use this procedure to upgrade to the GA version of the SAL Gateway virtual machine. That is. Restore the backup file on the new SAL Gateway virtual machine. 2. 3.

Upgrading the SAL Gateway OVA Related topics: Deploying the SAL Gateway OVA to vCenter on page 34 Deploying the SAL Gateway OVA directly to the ESXi server on page 40 Backing up the virtual machine on page 51 Restoring a virtual machine on page 52 Validating an upgrade operation After you upgrade the SAL Gateway virtual machine by restoring the backup of an earlier virtual machine. including IP address and hostname. About this task Use the following steps to validate that the upgrade process is successful. visit the Avaya Support website at http://support.avaya.2.0. To report a problem with the upgrade operation or to contact Avaya Support for assistance. Procedure 1.0-vApp-1. 54 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya. Additionally.com. Log on to the SAL Gateway Web interface. you must check whether the network configuration and the SAL Gateway configuration are properly restored.0.0. Run the following command to check the version of the new SAL Gateway virtual machine: swversion -v The version number for the GA release of the SAL Gateway vAppliance is SALGateway-2. are restored properly: ifconfig hostname less /etc/host 4. 3.com April 2013 . and check the SAL Gateway configuration. you must check that all the services are running on the new virtual machine. Log on to the SAL Gateway virtual machine as admin. Run the following commands to verify that the SAL Gateway services are up and running: service spiritAgent status service axedaAgent status service gatewayUI status 5. Run the following commands to view and verify that the network configuration parameters. 2. and switch to the root user.0-e50-09.

For information about reconfiguring your virtual machine. Q. Avaya does not recommend using DHCP for the SAL Gateway virtual machine. In absence of a console access. A console access is not necessary while you reboot the SAL Gateway virtual machine. Do I require a console access while rebooting the SAL Gateway virtual machine? A. No. No. Can I use DHCP for the network parameters for the SAL Gateway virtual machine? A. see Reconfiguring the virtual machine deployed through vCenter on page 49 and Reconfiguring the virtual machine deployed directly on an ESXi server on page 50. the script waits for 30 seconds and then continues with the normal boot process. Q. For information about configuring NTP servers on the SAL Gateway virtual machine. SAL Gateway uses the IP address of the SAL Gateway virtual machine. When you reboot a SAL Gateway virtual machine that is deployed directly on an ESXi host. However. For onboarding. you require a console access. How do I manage the system date and time? A. If you use DHCP for configuring the network parameters of SAL Gateway in the Virtualized Environment Deployment Guide April 2013 55 . To be able to utilize the script. having a console access can be useful.Chapter 12: Troubleshooting FAQ Q. Can I use the Ethernet interface other than eth0 for the SAL Gateway virtual machine? A. the script considers that you do not want to reconfigure the virtual machine. The script waits for user input for 30 seconds before proceeding with the normal boot process. which onboards the devices in the customer network. This process is applicable only in the case of direct deployment. Currently the SAL Gateway virtual machine can work only with eth0. The SAL Gateway virtual machine uses NTP to synchronize the system time with an NTP server. If the SAL Gateway virtual machine was deployed through vCenter. Q. depending on the deployment scenario and the user needs. Even though the SAL Gateway virtual machine supports DHCP. a script runs during the boot process that waits for user inputs. then having a console access can help you to reconfigure the virtual machine during the boot process. How do I reconfigure my virtual machine after I have deployed the virtual machine? A. The SAL Gateway virtual machine has SAL Gateway running on the machine. If you do not provide input within 30 seconds. You can utilize the script to reconfigure the virtual machine. If the SAL Gateway virtual machine was deployed directly on an ESXi host using a vSphere client. see Configuring timing on page 22. then you do not require a console access during the rebooting. Q.

Run the following command: /opt/vmware/share/vami/vami_ovf_process -s eth0 4. other processes in the SAL Gateway virtual machine use the iptables modules. 6. How do I change to static configuration? A. 7. Shut down the virtual machine using the vCenter administration. 3. I have installed the SAL Gateway virtual machine using DHCP through vCenter. How do I find the version of the SAL Gateway virtual machine? A. 2. Log in as admin. In such cases. Edit the virtual machine settings. During the first boot. Q. or connect to the virtual machine through an SSH client. Start the virtual machine using the vCenter administration. 3. run the following command: 56 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya.Troubleshooting the SAL Gateway virtual machine. Why do I get an VM communication interface: [FAILED] error on the virtual machine console during the first boot? A. Provide static configuration for the networking parameters in the Properties page. then chances are that the IP address of the SAL Gateway virtual machine might change. To see only the SAL Gateway version. Open a virtual machine console. one by one with the new IP address. During the restore process. Q. Perform the following steps to apply static configuration for networking to the SAL Gateway virtual machine installed using vCenter: 1.com April 2013 . Apart from the SAL Gateway services. which were already onboard. The errors do not occur on subsequent reboots. The restart attempt fails because these shared modules cannot be unloaded while other processes are still running. Configure static parameters for the networking of the SAL Gateway virtual machine so that you do not encounter similar issues. Failure to unload the iptables modules has no service impact. 4. Perform the following steps to find the version of the SAL Gateway virtual machine: 1. Open a virtual machine console. Why do I get an Unloading iptables modules: [FAILED] error during the restore operation? A. or connect to the virtual machine through an SSH client. which causes these errors. These errors have no service impact. 2. Log in as admin. Ignore this error. Run the following command: sudo swversion The system displays a verbose output. Ignore these errors. you must again onboard all the devices. the system recreates the initial ram disk (initrd) to include the VMware Tools modules. Q. 5. Q. the system tries to restart the iptables service. and switch to the root user.

Q. Therefore. If you deployed the SAL Gateway virtual machine directly on an ESXi host. What should I do? A. Running the storage or host vMotion does not affect any service that is currently running on the SAL Gateway virtual machine. Any remote connections created before running the storage or host vMotion continue to work. The script runs in two parts.com to contact Avaya. then every time you boot the virtual machine. SAL Gateway in the Virtualized Environment Deployment Guide April 2013 57 . Through the interactive prompts from the script. a script runs as part of the boot up process that waits for user inputs. In the first part. The script for configuring network parameters for a direct deployment on an ESXi host indicates that pressing Control+C opens the main menu. However. this script runs while the virtual machine is still booting. type n or N when the script prompts for reconfiguration on the virtual machine console. In the second part. Try to run the restore command again. you can configure the network parameters. To see only the version of the SAL Gateway virtual machine. you might not be able to establish new remote connections to the managed devices. If the error persists. If you want to skip the process.avaya. However. Q. you can establish new connections. A. run the following command: sudo swversion -v Q. Q. you can reconfigure the virtual machine. Why pressing Control+C does not work during the configuration of the virtual machine on the virtual machine console? A. Will there be any service outage if I run the storage or host vMotion? A. Why do I have to configure the virtual machine every time I boot up? A. when the storage or host vMotion is in progress. This outage lasts only until the storage or host vMotion is complete. After the storage or host vMotion completes successfully. the Control+C key press sequence does not work.FAQ sudo swversion -s 5. This issue is a known issue. I got an error while running the restore command. visit the Avaya Support website at http://support. you can configure the time zone settings.

com April 2013 .Troubleshooting 58 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya.

Both these notices alert you to important issues that directly impact Avaya products. perform the following steps: Procedure 1. or release fix. A PSN can also be used to provide a workaround for a known problem. 3. Viewing PCNs and PSNs About this task To view PCNs and PSNs. if you select Product Support Notices. click DOWNLOADS & DOCUMENTS. 4. but the business unit or services need to alert Avaya Direct. in the Enter Your Product Here field. Avaya issues product-support notice (PSN) when there is no patch. 2. enter the name of the product. Note: If the Avaya Support website displays the login page. In the Choose Release field. steps to recover logs. Go to the Avaya Support website at http://support. and customers of a problem or a change in a product. or steps to recover software. On the Downloads & Documents page. the system displays only PSNs in the documents list. enter your SSO login credentials.com. Business Partners.Appendix A: PCN and PSN notifications PCN and PSN notifications Avaya issues a product-change notice (PCN) in case of any software update. SAL Gateway in the Virtualized Environment Deployment Guide April 2013 59 . 6. For example. Select the appropriate filters as per your search requirement. Select Documents as the content type. 5. service pack. For example. a PCN must accompany a service pack or a patch that needs to be applied universally. select the specific release from the drop-down list. On the top of the page.avaya.

To sign up for notifications: Procedure 1. For detailed information. 60 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya. The Avaya E-Notifications process manages this proactive notification system . new product patches. These notifications also alert you when new product documentation. 2. or new services packs are available.com/ext/index? page=content&id=PRCS100274#.PCN and PSN notifications Note: You can apply multiple filters to search for the required documents. Go to the Avaya Support Web Tips and Troubleshooting: eNotifications Management page at https://support. Signing up for notifications alerts you to specific issues you must be aware of.com April 2013 . Signing up for PCNs and PSNs About this task Manually viewing PCNs and PSNs is helpful. but you can also sign up for receiving notifications of new PCNs and PSNs.avaya. Set up e-notifications. see the How to set up your ENotifications procedure.

and a manifest zipped into a single file.Glossary AFS Authentication File System. Some of the servers are sold as just the server with DVD or software downloads. OVA Open Virtualization Appliance. MAC Media Access Control address. A unique identifier assigned to network interfaces for communication on the physical network segment. Avaya Services VM A virtual machine that supports Avaya services applications. The SAL Gateway in the Virtualized Environment Deployment Guide April 2013 61 . An OVA contains the virtual machine description. A hypervisor is a hardware virtualization technique which runs multiple operating systems on the same shared physical server. storage. Provides processor. Blade A blade server is a stripped-down server computer with a modular design optimized to minimize the use of physical space and energy. each with its virtualized applications. AFS is an Avaya Web system that allows you to create Authentication Files for secure Avaya Global Services logins for supported non-Communication Manager Systems. memory. several applications or virtual machines can be involved. Also known as a bare-metal hypervisor. Currently the services virtual machine is part of System Platform which uses a nonVMWare hypervisor. disk images. Since the entire host fails over. Although many components are removed from blade servers to save space. and networking resources on multiple virtual machines. Hypervisor A hypervisor is also known as a Virtual Machine Manager (VMM). the blade still has all of the functional components to be considered a computer. Application A software solution development by Avaya that includes a guest operating system. minimize power consumption and other considerations. Avaya Appliance A physical server sold by Avaya running a VMware hypervisor that has several virtual machines. HA High Availability. The failover is a reboot recovery level which can take several minutes. The servers can be staged with the operating system and application software already installed. ESXi A virtualization layer that runs directly on the server hardware. A VMware feature for supporting virtual application failover by migrating the application from one ESXi host to another.

VM Virtual Machine. RFA is an Avaya Web system that you use to create Avaya License Files. RFA also creates Authentication Files for secure Avaya Global Services logins for Communication Manager Systems. Creating a snapshot can affect service. Replica of a physical server from an operational perspective. Some Avaya virtual appliances have limitations and others have specific instructions for creating snapshots. RFA Remote Feature Activation.PLDS OVA follows the Distributed Management Task Force (DMTF) specification. such as disk arrays. vMotion A VMware feature that migrates a running virtual machine from one physical server to another with minimal downtime or impact to end users. accessible to servers so that the devices appear as locally attached devices to the operating system. SANs are primarily used to make storage devices. virtual appliance A virtual appliance is a single software application bundled with an operating system. CPU cycles. releases. vCenter Server An administrative interface from VMware for the entire virtual infrastructure or data center. including VMs. These files are used to activate software including features. deployment profiles. and hardware monitoring. or memory that are reserved for a virtual machine. Reservation A reservation is the amount of physical RAM. and offer categories. PLDS Product Licensing and Download System. The Avaya PLDS provides product licensing and electronic software download distribution. a computer) that executes programs similar to a physical machine. Snapshot Capture a virtual appliance configuration in time. capacities. ESXi hosts. Storage vMotion A VMware feature that migrates virtual machine disk files from one data storage location to another with limited impact to end users. vSphere Client vSphere Client is VMware’s computer cloud virtualization operating system. distributed virtual networking. 62 SAL Gateway in the Virtualized Environment Deployment Guide Comments? infodev@avaya. A SAN is a dedicated network that provides access to consolidated data storage. A VM is a software implementation of a machine (for example. vMotion cannot be used to move virtual machines from one data center to another.com April 2013 . SAN Storage Area Network.

...................................................20 BIOS for HP servers ............ 19 intended audience ...........13 deployment procedures ............................................................................................................. 21 bundled software specifications ............... 7 F FAQ ....................... 45 configuring ............................ 33 deployment procedures .................................................................................................. 23 O overview ................................................36 properties page ........... 33 planning procedures .............................................................................................................. 7 N network parameters ...................................... 36 G guidelines ............ 13 VMware ............................................................... 7 document purpose ................................................................................................................... 51 OVA deployment ..... 34............................................................................... 24 thick .... 45 networking Avaya applications ..................................... 11........24 thin ............................................................................................................ 19 BIOS .................................................... 33 document changes ...............................23 Avaya Mentor videos ....................................................................................... 33 checklist .............................. 51 backup and restore ......................................... 17 virtual machine resources ................................................................................................................................................................................ 40 directly to ESXi ...................................................................................................... 34 deployment .................................. 27 I Intel VT support .......................................................................................45 configure ...........45 network parameters ....................................................................................................................................................... 26 hyperthreading ................................ 13 deployment ............ 41 deployment ......................................................29 Avaya applications ............................................................... 33............................................................... 23 networking .................................................... 15 clones ............................................................................................................................. 18 C capacity of SAL Gateway ............................ 33 P PCN .......................... 24 deployment guidelines ....................... 19 BIOS for Dell servers ...................40 to vCenter ................................................................................................................................41 deploying OVA ........................................................ 59 SAL Gateway in the Virtualized Environment Deployment Guide April 2013 63 ............... 41 components ................................................................................ 55 field descriptions ............................................................................ 17 B best practices .................. 23 networking best practices ..............................................9 E editing ................................... 13 configure ........8 D deploying copies ............Index A downloading software ........................................................................................................................... 19 performance ...................... 18 checklist ............................. 22 timing ............................. 22 courses ........... 15............................................................................................. 13 H high availability ...... 45 SAL Gateway parameters ..................................................

.. 54 upgrading ......................................................................................49 virtual machine ......... 16.................... 59 PSNs .......................... 43 support ................................. 29 downloading software ...................................................... 53 64 test remote access service .................................................................................................................................................................................................... 49 shutdown setting ..... 60 snapshots .............................................................................................................................................................................................. 59 purpose of document .......................................................................... 52 S SAL Gateway ....................................................................8 related resources ......15 server .................................................................. 29...................... 21 VT support ............................................... 17 software ..................................................................................................................................................................... 15 restoring .................................... 9 contact ..................................................................................................43............... 18 SAL Gateway implementation .................................... 47 test the alarming service ................................... 50 at vCenter ......................................................................................................................................................................................... 17 vMotion ................... 49 reconfiguring virtual machine .................................................................................................................... 7 upgrading ................................................................................... 52 virtual machine .....................................PCN notification ............................................................................................................................................................... 30 SAL Gateway capacity .................................................................................................................. 8 U upgrade operation ............................. 47 test remote access service ................................... 50 at ESXi host .............................................. 45 SAL Gateway vAppliance . 48 SAL Watchdog service ..................................................................................................................... 17 T R reconfiguration ........... 16 resource requirements ............. 22 configuring ............................................................................................................................................................17 supported .................................... 19 planning procedures .............................................................................................. 9 supported versions ............................................ 9 Avaya Mentor .............................. 27 VMware software ........................................... 24 time keeping ..... 36 field descriptions ...............15 signing up for PCNs and PSNs ... 47 testing .................................. 43 virtual machine resource requirements ................................................................................................................... 29 properties page ............................................................................................................................ 43 reconfiguration .......................................................................................................................................................................... 49 registering ... 9 requirements ............ 54 upgrade operation ............................................................................................................................... 17 specifications ...... 30 SAL Gateway .......................18 starting virtual machine ...........................................................................................48 thick deployment .............. 17 VMware ................... 54 validating ..... 59 PSN notification ........................ 9 Avaya Mentor videos ............................................. 30 related documentation ................................................................................................................................59 PCNs .............. 59 performance best practices ................ 16 resources ............................................... 47 test alarming services ...................... 30 registering ........ 36 PSN ....................... 15 PLDS .......................... 54 videos ......... 53 V validating ...9 virtual machine .... 53 SAL Gateway vAppliance .......................................................................................... 43 startup setting ............ 47 validation ............................................... 18 bundled software ............................... 47 SAL Gateway parameters ........... 49... 22 training ................................... 49 starting ........ 24 thin deployment .......................... 19 SAL Gateway in the Virtualized Environment Deployment Guide April 2013 ......................................... 17 virtual machine resources ...................... 15 checklist ................ 17 VMware Tools ............................................................................... 17 editing ......................................... 16 virtual machine resources ........................................................................................................................................................................................... 21 timekeeping ....................................................................................................................... 53 server hardware and resources ................................. 25 software requirements ............................. 45 configure .................................................