DeployingSystemManageronVMwareinVirtualizedEnvironment
DeployingSystemManageronVMwareinVirtualizedEnvironment
Release 6.3
January 2015
© 2014 Avaya Inc. applicable number of licenses and units of capacity for which the
license is granted will be one (1), unless a different number of
All Rights Reserved. licenses or units of capacity is specified in the documentation or other
Notice materials available to you. “Software” means Avaya’s computer
programs in object code, provided by Avaya or an Avaya Channel
While reasonable efforts have been made to ensure that the Partner, whether as stand-alone products, pre-installed , or remotely
information in this document is complete and accurate at the time of accessed on hardware products, and any upgrades, updates, bug
printing, Avaya assumes no liability for any errors. Avaya reserves fixes, or modified versions thereto. “Designated Processor” means a
the right to make changes and corrections to the information in this single stand-alone computing device. “Server” means a Designated
document without the obligation to notify any person or organization Processor that hosts a software application to be accessed by
of such changes. multiple users. “Instance” means a single copy of the Software
Documentation disclaimer executing at a particular time: (i) on one physical machine; or (ii) on
one deployed software virtual machine (“VM”) or similar deployment.
“Documentation” means information published by Avaya in varying
mediums which may include product information, operating License types
instructions and performance specifications that Avaya may generally Designated System(s) License (DS). End User may install and use
make available to users of its products and Hosted Services. each copy or an Instance of the Software only on a number of
Documentation does not include marketing materials. Avaya shall not Designated Processors up to the number indicated in the order.
be responsible for any modifications, additions, or deletions to the Avaya may require the Designated Processor(s) to be identified in
original published version of documentation unless such the order by type, serial number, feature key, Instance, location or
modifications, additions, or deletions were performed by Avaya. End other specific designation, or to be provided by End User to Avaya
User agrees to indemnify and hold harmless Avaya, Avaya's agents, through electronic means established by Avaya specifically for this
servants and employees against all claims, lawsuits, demands and purpose.
judgments arising out of, or in connection with, subsequent
modifications, additions or deletions to this documentation, to the Heritage Nortel Software
extent made by End User. “Heritage Nortel Software” means the software that was acquired by
Link disclaimer Avaya as part of its purchase of the Nortel Enterprise Solutions
Business in December 2009. The Heritage Nortel Software currently
Avaya is not responsible for the contents or reliability of any linked available for license from Avaya is the software contained within the
websites referenced within this site or documentation provided by list of Heritage Nortel Products located at http://support.avaya.com/
Avaya. Avaya is not responsible for the accuracy of any information, LicenseInfo/ under the link “Heritage Nortel Products”, or such
statement or content provided on these sites and does not successor site as designated by Avaya. For Heritage Nortel
necessarily endorse the products, services, or information described Software, Avaya grants Customer a license to use Heritage Nortel
or offered within them. Avaya does not guarantee that these links will Software provided hereunder solely to the extent of the authorized
work all the time and has no control over the availability of the linked activation or authorized usage level, solely for the purpose specified
pages. in the Documentation, and solely as embedded in, for execution on,
Warranty or (in the event the applicable Documentation permits installation on
non-Avaya equipment) for communication with Avaya equipment.
Avaya provides a limited warranty on Avaya hardware and software. Charges for Heritage Nortel Software may be based on extent of
Refer to your sales agreement to establish the terms of the limited activation or use authorized as specified in an order or invoice.
warranty. In addition, Avaya’s standard warranty language, as well as
information regarding support for this product while under warranty is Copyright
available to Avaya customers and other parties through the Avaya Except where expressly stated otherwise, no use should be made of
Support website: http://support.avaya.com or such successor site as materials on this site, the Documentation, Software, Hosted Service,
designated by Avaya. Please note that if you acquired the product(s) or hardware provided by Avaya. All content on this site, the
from an authorized Avaya Channel Partner outside of the United documentation, Hosted Service, and the Product provided by Avaya
States and Canada, the warranty is provided to you by said Avaya including the selection, arrangement and design of the content is
Channel Partner and not by Avaya. owned either by Avaya or its licensors and is protected by copyright
Licenses and other intellectual property laws including the sui generis rights
relating to the protection of databases. You may not modify, copy,
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA reproduce, republish, upload, post, transmit or distribute in any way
WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO OR any content, in whole or in part, including any code and software
SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE unless expressly authorized by Avaya. Unauthorized reproduction,
APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR transmission, dissemination, storage, and or use without the express
INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., written consent of Avaya can be a criminal, as well as a civil offense
ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS under the applicable law.
APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH
AVAYA OR AN AVAYA CHANNEL PARTNER. UNLESS Virtualization
OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES Each product has its own ordering code and license types. Note that
NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS each Instance of a product must be separately licensed and ordered.
OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA For example, if the end user customer or Avaya Channel Partner
AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA would like to install two Instances of the same type of products, then
RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU two products of that type must be ordered.
AND ANYONE ELSE USING OR SELLING THE SOFTWARE
WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR Third Party Components
USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,
“Third Party Components” mean certain software programs or
YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM
portions thereof included in the Software or Hosted Service may
YOU ARE INSTALLING, DOWNLOADING OR USING THE
contain software (including open source software) distributed under
SOFTWARE (HEREINAFTER REFERRED TO
third party agreements (“Third Party Components”), which contain
INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO
terms regarding the rights to use certain portions of the Software
THESE TERMS AND CONDITIONS AND CREATE A BINDING
(“Third Party Terms”). As required, information regarding distributed
CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
Linux OS source code (for those Products that have distributed Linux
APPLICABLE AVAYA AFFILIATE (“AVAYA”).
OS source code) and identifying the copyright holders of the Third
Avaya grants you a license within the scope of the license types Party Components and the Third Party Terms that apply is available
described below, with the exception of Heritage Nortel Software, for in the Documentation or on Avaya’s website at: http://
which the scope of the license is detailed below. Where the order support.avaya.com/Copyright or such successor site as designated
documentation does not expressly identify a license type, the by Avaya. You agree to the Third Party Terms for any such Third
applicable license will be a Designated System License. The 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 or such
successor site as designated by Avaya. Suspected security
vulnerabilities with Avaya products should be reported to Avaya by
sending mail to: [email protected].
Trademarks
The trademarks, logos and service marks (“Marks”) displayed in this
site, the Documentation, Hosted Service(s), 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, Hosted Service(s) 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.
Linux® is the registered trademark of Linus Torvalds in the U.S. and
other countries.
Downloading Documentation
For the most current versions of Documentation, see the Avaya
Support website: http://support.avaya.com, or such successor site as
designated by Avaya.
Contact Avaya Support
See the Avaya Support website: http://support.avaya.com for Product
or Hosted Service notices and articles, or to report a problem with
your Avaya Product or Hosted Service. For a list of support telephone
numbers and contact addresses, go to the Avaya Support website:
http://support.avaya.com (or such successor site as designated by
Avaya), scroll to the bottom of the page, and select Contact Avaya
Support.
Contents
Chapter 1: Introduction............................................................................................................ 7
Purpose.................................................................................................................................. 7
Intended audience................................................................................................................... 7
Document changes since last issue.......................................................................................... 7
Related resources................................................................................................................... 8
Documentation.................................................................................................................. 8
Training............................................................................................................................ 8
Viewing Avaya Mentor videos............................................................................................. 9
Support................................................................................................................................ 10
Warranty............................................................................................................................... 10
Chapter 2: Architecture overview.......................................................................................... 11
®
Avaya Aura Virtualized Environment Overview....................................................................... 11
Topology.............................................................................................................................. 12
VMware components............................................................................................................. 14
OVA deployment order.......................................................................................................... 14
Deployment guidelines........................................................................................................... 14
Chapter 3: Planning and configuration................................................................................. 16
Server hardware and resources.............................................................................................. 16
Configuration tools and utilities............................................................................................... 16
Customer configuration data.................................................................................................. 16
System Manager virtual machine resource requirements.......................................................... 17
Adjusting the System Manager virtual machine properties........................................................ 18
VMware software requirements.............................................................................................. 19
Chapter 4: Installing the System Manager OVA file............................................................ 20
Deployment of cloned and copied OVAs................................................................................. 20
Methods of System Manager OVA file deployment .................................................................. 20
Installing the System Manager OVA file by using vSphere Client............................................... 20
Deployment checklist....................................................................................................... 20
Downloading the authentication file................................................................................... 22
Deploying the System Manager OVA file by using vSphere................................................ 22
Configuring the network parameters from the vSphere console........................................... 24
Backup Definition parameters........................................................................................... 25
Installing the authentication file on System Manager.......................................................... 27
Installing the System Manager Release 6.3.13 bin file........................................................ 28
Installing the System Manager OVA file by using vCenter......................................................... 29
Deployment checklist....................................................................................................... 29
Deploying the System Manager OVA file using vCenter...................................................... 30
Starting the System Manager virtual machine.......................................................................... 33
Chapter 5: Postinstallation verification................................................................................ 34
Purpose
This document provides procedures for deploying the Avaya Aura® System Manager virtual
application in Avaya Aura® Virtualized Environment. This document includes installation,
configuration, initial administration, troubleshooting, upgrading, and basic maintenance checklists
and procedures.
Intended audience
The primary audience for this document is anyone who is involved with installing, configuring,
upgrading, and verifying System Manager on VMware® vSphere™ 5.0, 5.1, or 5.5 Virtualized
Environment. The audience includes and is not limited to implementation engineers, field
technicians, business partners, solution providers, and customers.
This document does not include optional or customized aspects of a configuration.
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
Avaya Aura® Virtualized Environment Describes the Virtualized Environment Sales engineers
Solution Description 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® System Manager Describes product characteristics and Sales engineers,
Overview and Specification capabilities, including product overview and Solution architects,
feature descriptions, interoperability, Implementation
performance specifications, security, and engineers, Support
licensing requirements for Avaya Aura® personnel
System Manager.
Administration
Administering Avaya Aura® System Describes the procedures to configure Implementation
Manager System Manager and the managed engineers, Support
elements that System Manager supports. personnel
Maintenance and Troubleshooting
Upgrading Avaya Aura® System Describes the procedures to upgrade Avaya Implementation
Manager on VMware in Virtualized Aura® System Manager on VMware in engineers, Support
Environment Virtualized Environment. personnel
Troubleshooting Avaya Aura® Describes the procedures to troubleshoot Implementation
System Manager Avaya Aura® System Manager. engineers, Support
personnel
Training
The following courses are available on the Avaya Learning website at http://www.avaya-
learning.com. After logging into the website, enter the course code or the course title in the Search
field and click Go to search for the course.
Course Course title Type
code
1A00234E Avaya Aura® Fundamental Technology AvayaLive™ Engage Theory
Table continues…
Note:
Videos are not available for all products.
Support
Go to the Avaya Support website at http://support.avaya.com for the most up-to-date
documentation, product notices, and knowledge articles. You can also search for release notes,
downloads, and resolutions to issues. Use the online service request system to create a service
request. Chat with live agents to get answers to questions, or request an agent to connect you to a
support team if an issue requires additional expertise.
Warranty
Avaya provides a 90-day limited warranty on the System Manager software. For detailed terms and
conditions, see the sales agreement or other applicable documentation. Additionally, for the
standard warranty description of Avaya and the details of support, see Help & Policies > Policies
& Legal > Maintenance and Warranty Information on the Avaya Support website at http://
support.avaya.com. For additional information, see Help & Policies > Policies & Legal > License
Terms.
For more details on the hardware maintenance for supported products, see http://portal.avaya.com/
ptlWeb/services/SV0452.
Software delivery
The software is delivered as one or more pre-packaged Open Virtualization Appliance (OVA) files
that are posted on the Avaya Product Licensing and Download System (PLDS) and the Avaya
support site. Each OVA contains the following components:
• the application software and operating system.
• pre-installed VMware tools.
• preset configuration details for
- RAM and CPU reservations and storage requirements
- Network Interface Card (NIC)
Patches and upgrades
A minimum patch level can be required for each supported application. For more information
regarding the application patch requirements, see the compatibility matrix tool at http://
support.avaya.com/CompatibilityMatrix/Index.aspx.
Important:
Do not upgrade the VMware tools software that is packaged with each OVA unless instructed to
do so by Avaya. The supplied version is the supported release and has been thoroughly tested.
Performance and capacities
The OVA template is built with configuration values which optimize performance and follow
recommended Best Practices.
Caution:
Modifying these values can have a direct impact on the performance, capacity, and stability of
the virtual machine. It is the responsibility of the customer to understand the aforementioned
impacts when changing configuration values. Avaya Global Support Services (GSS) may not be
able to assist in fully resolving a problem if the virtual hardware or resource allocation has been
changed to unsupported values for a virtual application. Avaya GSS could require the customer
to reset the values to the optimized values before starting to investigate the issue.
Topology
The following is an example of a deployment infrastructure for System Manager VMware.
VMware components
VMware software component Description
ESXi Host The physical machine running the ESXi Hypervisor software.
ESXi Hypervisor A platform that runs multiple operating systems on a host computer at
the same time.
vSphere Client vSphere Client is an application that installs and manages virtual
machines. vSphere Client connects to a vCenter server or directly to an
ESXi host if a vCenter Server is not used. The application is installed on
a personal computer or accessible through a web interface.
vCenter Server vCenter Server provides centralized control and visibility at every level of
the virtual infrastructure. vCenter Server provides VMware features such
as High Availability and vMotion.
Deployment guidelines
The high-level deployment steps are:
1. Deploy the OVA or OVAs.
2. Configure the application.
3. Verify the installation.
The deployment guidelines for the virtual appliances are:
• Deploy as many virtual appliances on the same host as possible.
• Deploy the virtual appliances on the same cluster if the cluster goes beyond the host boundary.
• Segment redundant elements on a different cluster, or ensure that the redundant elements are
not on the same host.
• Create a tiered or segmented cluster infrastructure that isolates critical applications, such as
Avaya Aura® applications, from other virtual machines.
• Plan for rainy day scenarios or conditions. Do not configure resources only for traffic or
performance on an average day.
• Do not oversubscribe resources. Oversubscribing affects performance.
• Monitor the server, host, and virtual appliance performance.
Important:
The values for performance, occupancy, and usage can vary greatly. The blade server
might run at 5% occupancy, but a virtual machine might run at 50% occupancy. Note that a
virtual machine behaves differently when the CPU usage is higher.
Related Links
Backup Definition parameters on page 25
If the host does not have the minimum resources to allocate to the virtual machine, the system does
not start the System Manager virtual machine.
Related Links
Adjusting the System Manager virtual machine properties on page 18
4. In the Resource Allocation area, in the Reservation field, perform one of the following to
start the virtual machine:
• Adjust the slider to the appropriate position.
• Enter the exact value.
Deployment checklist
You can set up Geographic Redundancy on the system after the installation of the
System_Manager_6.3.13_r5003336.bin file. For more information, see the Geographic
Redundancy configuration section.
Note:
If the System Manager virtual machine is already on Release 6.3 or later, install the
System_Manager_6.3.13_r5003336.bin file to upgrade the system to Release 6.3.13.
Use the following checklist to deploy the System Manager vAppliance by using vSphere.
# Action Link/Notes
# Action Link/Notes
4. In the Deploy OVF Template dialog box, perform one of the following steps:
• In the Deploy from a file or URL field, enter the path to the .ova file.
• Click Browse and navigate to the .ova file from the local computer, network share, CD-
ROM, or DVD.
5. On the OVF Template Details page, verify the details, and click Next.
6. On the End User License Agreement page, click Accept.
7. Click Next.
8. (Optional) On the Name and Location page, in the Name field, change the name for the
virtual machine.
9. Click Next.
10. On the Host page, select the required data store and then click Next.
11. On the Disk Format page, click Thick Provision Lazy Zeroed.
The system displays the data store that you selected and the available space.
12. On the Network Mapping page, for each network that you specified in the OVA Template
Details page, in the Destination Network column, select a host network from the list.
For example, click VM Network 2.
13. Click Next.
14. Review the settings and click Finish.
Wait until the system deploys the OVA file successfully.
15. To start the System Manager virtual machine, perform one of the following steps:
• Right-click the virtual machine, and click Power > Power On.
• On the Inventory menu, click Virtual Machine > Power > Power On.
The system starts the System Manager virtual machine.
Next steps
• When the system starts for the first time, configure the parameters for System Manager. For
instructions, see Configuring the network parameters from CLI.
From the time you power on the system, the deployment process takes about 30–40 minutes to
complete. Do not reboot the system until the configuration is complete. You can monitor the
post deployment configuration from the /var/log/Avaya/PostDeployLogs/
post_install_sp.log file.
• Verify the deployment of the System Manager OVA file.
• Install the System_Manager_6.3.13_r5003336.bin file.
Related Links
Configuring the network parameters from the vSphere console on page 24
Installing the System Manager Release 6.3.13 bin file on page 28
Verifying the installation of System Manager on page 34
Note:
You can skip the configuration of the backup definition parameters to schedule the backup jobs
later.
The backup time must be 6 hours later than the System Manager installation time.
If you set the Backup Start Month field to 5, Backup Start Day field to 24, and Repeat Type field
to Weekly, the system executes the backup job every Friday if May 24th is a Friday.
Name Description
Schedule Backup? • Yes: To schedule the backup jobs during
the System Manager installation.
• No: To schedule the backup jobs later.
Note:
If you select No, the system does
not display the remaining fields.
Backup Server IP The IP address of the remote backup
server.
Note:
The IP address of the backup server
must be different from the System
Manager IP address.
Backup Server Login Id The login ID of the backup server to log in
through CLI.
Backup Server Login Password The password to log in to the backup
server through CLI.
Re-Type Backup Server Login Password The password that you re-enter to log in to
the backup server through CLI.
Backup Directory Location The location on the remote backup server.
Repeat Type The type of the backup. The possible
values are:
• Hourly
• Daily
• Weekly
• Monthly
Backup Frequency The frequency of the backup taken for the
selected backup type.
Backup Start Year The year in which the backup must start.
The value must be greater than or equal to
the current year.
Table continues…
Name Description
Backup Start Month The month in which the backup must start.
The value must be greater than or equal to
the current month.
Backup Start Day The day on which the backup must start.
The value must be greater than or equal to
the current day.
Backup Start Hour The hour in which the backup must start.
The value must be 6 hours later than the
current hour.
Backup Start Minutes The minute when the backup must start.
The value must be a valid minute.
Backup Start Seconds The second when the backup must start.
The value must be a valid second.
Related Links
Downloading the authentication file on page 22
Next steps
1. Verify the patch installation.
• If the patch installation is successful, log off from the system, and remove the snapshot.
Note:
Snapshots occupy the system memory and degrades the performance of the virtual
application. Therefore, delete the snapshot after you verify the patch installation or the
system upgrade.
• If the patch installation fails, use the snapshot to restore the system to the original state.
2. Shut down the System Manager virtual machine.
3. Turn on the System Manager virtual machine.
System Manager takes about 15 minutes to start.
Related Links
Verifying the installation of System Manager on page 34
Starting the System Manager virtual machine on page 33
Deployment checklist
You can set up Geographic Redundancy on the system after the installation of the
System_Manager_6.3.13_r5003336.bin file. For more information, see the Geographic
Redundancy configuration section.
If the System Manager virtual machine is already on Release 6.3 or later, install the
System_Manager_6.3.13_r5003336.bin file to upgrade the system to Release 6.3.13.
Use the following checklist for deploying the System Manager vAppliance using vCenter.
# Action Link/Notes
# Action Link/Notes
• NTP Server IP or FQDN. The IP address or FQDN of the NTP server. Separate IP
addresses or FQDNs with commas (,).
• Time Zone. The time zone. Select a time zone from the list.
• Virtual FQDN for the System Manager virtual machine.
- Virtual short hostname. For example, grsmgr.
- Virtual domain. For example, dev.com.
• The VFQDN value must be unique and different from the FQDN value of
System Manager and the elements.
• VFQDN is a mandatory field.
• Do not add VFQDN entries in the DNS configuration.
• Do not add VFQDN in the /etc/hosts file on System Manager. Adding
VFQDN in the /etc/hosts file might cause failures.
• In Geographic Redundancy, the primary and secondary System Manager must
use the same VFQDN.
• After the System Manager installation, you cannot change the VFQDN unless
you reinstall System Manager.
b. Configure the following SNMPv3 parameters:
• User Name Prefix. For example, global.
• User Authentication Protocol Password. For example, globalpass.
• User Privacy Protocol Password. For example, globalpass.
c. (Optional) Select the Schedule SMGR backup check box to schedule the System
Manager backup and configure the backup definition input parameters. For information,
see Backup Definition parameters.
Note:
• If you do not provide the details in the mandatory fields, you cannot power on the
virtual machine even if the deployment is successful.
• During the startup, the system validates the inputs that you provide. If the inputs
are invalid, the system prompts you to provide the inputs again on the console of
the virtual machine.
• The system does not validate the backup definition data that you provide. If the
data is invalid, the system does not schedule the backup.
16. Click Next.
17. Review the settings and click Finish.
Wait until the system deploys the OVA file successfully.
From the time you power on the system, the deployment process takes about 30–40 minutes
to complete. Do not reboot the system until the configuration is complete. You can monitor
Postinstallation steps
Procedure
Recreate all licenses with the new host ID format, and install the new license files.
System Manager on VMware uses a new host ID format for Avaya WebLM server. Therefore, all
licenses previously installed becomes invalid. For instructions to install the license file, see
Managing licenses in Administering Avaya Aura® System Manager.
SAL Gateway
A Secure Access Link (SAL) Gateway is required for remote access and alarming.
Through SAL, support personnel or tools can gain remote access to managed devices to
troubleshoot and debug problems.
A SAL Gateway:
1. Receives alarms from Avaya products in the customer network.
2. Reformats the alarms.
3. Forwards the alarms to the Avaya support center or a customer-managed Network
Management System.
You can deploy the SAL Gateway OVA using vCenter through a vSphere client. You can also
deploy the SAL Gateway OVA directly to the ESXi server through a vSphere client.
For more information about the SAL Gateway, see the Secure Access Link documentation on the
Avaya Support website at http://support.avaya.com .
For more information, see System Manager Virtualized Environment footprint hardware
resource matrix.
7. Click on the Resources tab.
8. Select Memory and verify the Reservation is set correctly.
9. Clear the unlimited check box and verify the Limit slide is set to the same value as the
Reservation.
10. Click the Hardware tab.
11. Select CPUs and change the Number of sockets according to the limit requirement.
For more information, see System Manager Virtualized Environment footprint hardware
resource matrix.
12. Click the Resources tab.
13. Select CPUs and verify that the Reservation is set correctly.
14. Clear the unlimited check box and verify that the Limit slide is set to the same value as the
Reservation field.
15. Click OK and wait until the virtual machine completes the reconfiguration process.
16. Power on the virtual machine.
Related Links
Installing the System Manager Release 6.3.13 bin file on page 28
System Manager Virtualized Environment footprint hardware resource matrix on page 38
Capability and scalability specification on page 38
primary and the secondary System Manager server. After you complete the bulk activity,
enable the Geographic Redundancy replication if the replication is disabled.
• Disable the Geographic Redundancy replication between the two servers.
Disable the Geographic Redundancy replication before you start the maintenance activities
such as upgrades, installation of software patches or hot fixes. If the primary and the
secondary System Manager servers disconnect from each other for more than the threshold
period, the system automatically disables the Geographic Redundancy replication. The default
threshold period is 5 minutes.
• Activate the secondary System Manager server.
Activate the secondary System Manager server in the following scenarios:
- The primary System Manager becomes nonoperational.
- The enterprise network splits.
• Deactivate the secondary System Manager server.
Deactivate the secondary System Manager server in the following situations:
- The primary System Manager server becomes available.
- The element network restores from the split.
• Restore the primary System Manager server.
After you activate the secondary System Manager server, to return to the active-standby mode,
you must restore the primary System Manager server. You can choose to restore from the
primary System Manager or the secondary System Manager server.
Note:
The system does not merge the data from the primary and secondary server.
• Reconfigure Geographic Redundancy.
You can reconfigure Geographic Redundancy when the secondary System Manager is in the
standby mode or active mode. The reconfiguration process copies the data from the primary
System Manager server to the secondary System Manager server.
• Convert the primary System Manager server to the standalone server.
Perform this procedure to convert the primary System Manager server in the Geographic
Redundancy-enabled system to a standalone server or if you have to configure a new
secondary server.
For detailed instructions to complete each task, see the relevant section in this document.
2. To view the status of the Geographic Redundancy configuration during the restart of the two
application servers, perform one of the following:
• Log on to the web console of the primary System Manager server and perform the
following steps:
a. On the System Manager web console, click Services > Geographic Redundancy.
b. Refresh the GR Health page.
If Enable is available, the configuration is complete.
Note:
Log off and log on to the primary System Manager server to view the updated
status of GR Health.
• Log in to the secondary System Manager server as system administrator by using the
command line interface and perform the following steps:
a. Type tail –f /home/ucmdeploy/quantum/autoReconfig.log.
The system displays the progress during the restart of the two application servers.
When the second application server restart completes, the system displays the
following messages:
SMGR :: operationStatus=success
that the system maintenance activities such as backup, restore, and shutdown are not in
progress.
Procedure
1. On the System Manager web console, click Services > Geographic Redundancy.
2. Click Enable Replication.
The system displays the progress information in the Enable GR Status section.
Note:
As the server becomes unavailable, you cannot gain access to the web console. Wait
until the process is complete before you continue with the next step.
If the enabling process is successful, the system displays the Geographic Redundancy
replication status as Enabled. If the process fails, the system displays an error message
with the replication status as Failed on the primary the System Manager web console. The
primary server remains in the failed state while the secondary server rolls back to the
previous state. Verify if the system has raised an alarm for a temporary network connectivity
failure. Retry when the network connectivity is restored. If the problem persists, contact
Avaya service personnel.
Related Links
Disabling the Geographic Redundancy replication on page 45
Geographic Redundancy field descriptions on page 50
Note:
As the server becomes unavailable, you cannot gain access to the web console. Wait
until the process is complete before you continue with the next step.
Related Links
Deactivating the secondary System Manager server on page 47
Geographic Redundancy field descriptions on page 50
Enable the Geographic Redundancy replication to synchronize the primary and secondary System
Manager servers.
Related Links
Enabling the Geographic Redundancy replication on page 44
Deactivating the secondary System Manager server on page 47
Geographic Redundancy field descriptions on page 50
Name Description
Convert to Standalone Converts to a standalone server.
The system displays the Convert to Standalone
button only when the replication is disabled.
Configure Configures Geographic Redundancy.
The system displays the Configure button only on
the standalone System Manager server.
Reconfigure Configures Geographic Redundancy.
The system displays the Reconfigure button only on
the secondary System Manager server.
Button Description
Enable Replication Continuously replicates the data between the
primary and the secondary System Manager server.
The system displays the Enable Replication button
after the following events:
• State of Geographic Redundancy is Disable.
• Geographic Redundancy configuration.
• Restoration of the primary Geographic
Redundancy server is complete.
Disable Replication Stops replicating the data between the primary and
the secondary System Manager server.
The system displays the Disable Replication button
when the state of Geographic Redundancy is
Enable.
Restore Data Recovers the server after the failback.
The system displays the Restore Data button when
the secondary System Manager server is
deactivated.
Note:
• The system displays Activate Secondary
Server only on the secondary System
Manager server.
• The system displays the Activate Secondary
Server or the Deactivate Secondary Server
button on the page.
Deactivate Secondary Server Click to make the primary System Manager resume
operation. You use this option when the primary
System Manager server restores operation or
recovers from a network failure.
Note:
The system displays Deactivate Secondary
Server only on the secondary System Manager
server.
Table continues…
Name Description
Service Name Displays the name of the service for which the
system provides the status of the health.
View Detail Click View Graph.
• For database and directory replication, the system
displays the graph for default interval. If no graph is
present for the default interval, using the calendar,
you can set the period for which you require to
check the health status, and click Generate to view
health details in a graph.
For database replication, the system displays
graphs for time lag and the size lag. For directory
replication, the system displays graph for time lag
only.
• For file replication, the system displays the last
replication time and the size of the lag.
HeartBeat status
Click View Heartbeat Status to view the details. The system displays the GR Heartbeat page.
Name Description
Service Name The name of the monitored service. The services
are:
• System Health: The heartbeat status indicates if
the primary or the secondary System Manager
server can communicate with the peer System
Manager server over the network.
• Database Replication: The heartbeat status
indicates if the data stored in the System Manager
database is getting replicated between the primary
and the secondary System Manager server.
• Application System Health: The heartbeat status
indicates if the application server of primary or
secondary System Manager can query the
application server of the peer System Manager.
• File Replication: The heartbeat status indicates if
the configuration files are getting replicated
between the primary and the secondary System
Manager server.
• Directory Replication: The heartbeat status
indicates if the data stored in the internal LDAP
server is getting replicated in the respective
System Manager server.
Table continues…
Name Description
Last Successful Heartbeat Time The last time the heartbeat was successful for the
monitored service.
Last Missed Heartbeat Time The last time when the monitored service missed the
heartbeat.
View Details The View Graph link to view the health status of the
monitored service over a period of time. To configure
the time period, click Edit Dates. The graph displays
the status in 0 and 1.
• 0 indicates that the monitored service is either
stopped or failed at that point of time
• 1 indicates that the monitored service is running at
that point of time.
Important:
To use the Use Default option, provide the remote server IP, user name, password,
and name and path of the backup file, and remote server port on the SMGR Element
Manager page. For Use Default, on the SMGR Element Manager page, you can click
Services > Configurationsand navigate to Settings > SMGR > SMGR Element
Manager.
5. In the Backup List, view the list of the remote backups that are created by using the SFTP
and SCP protocols.
If the location of a backup file is modified, in the Parameterized Restore tab, specify the
correct location of the backup file in the File Name field. You can select only one file at a
time.
6. Click Restore. On the Restore Confirmation page, the system displays the following
message:
The Restore operation will terminate all sessions and no services
will be available until the operation completes. So, the System
Manager console will not be available for approximately 45 minutes
but this time may vary based on Database size. Click on Continue to
go ahead with the Restore operation or click on Cancel to abort the
operation.
7. Click Continue.
The system logs you out of the System Manager web console and then shuts down.
Result
After the restore is complete on System Manager that is configured for Geographic Redundancy, the
system automatically restarts with the Geographic Redundancy replication status as disabled.
Related Links
Backup and Restore field descriptions on page 58
Name Description
Operation Specifies the type of operation. The values are:
• Backup
• Restore
File Name • For the backup operation, specifies the name of
the backup file.
• For the restore operation, specifies the name of the
file you want to restore.
Table continues…
Name Description
Path • For the backup operation, specifies the path of the
backup file.
• For the restore operation, specifies the path of the
file you want to restore.
Status Indicates the status of the backup or restore
operation. The values are:
• SUCCESS
• FAILED
• PLANNED
• RUNNING
Status Description Displays the error details of the backup or restore
operation that has failed.
Operation Time Specifies the time of the backup or restore operation.
Operation Type Defines whether the backup or restore operation is
local or remote.
User Displays the user who performed the operation.
Button Description
Backup Opens the Backup page. Use this page to back up
data on a specified local or remote location.
Restore Opens the Restore page. Use this page to restore
data to a specified local or remote location.
If you do not enter the name of the patch or the service pack, the console displays menu items.
Provide the absolute path to the patch or the service pack that you want to install for System
Manager.
Related Links
System Manager command line interface operations on page 62
For instructions to install a license file, see Managing Licenses in Administering Avaya Aura®
System Manager.
Related Links
changeIPFQDN command on page 61
System Manager command line interface operations on page 62
changeIPFQDN command
Use the changeIPFQDN command to change the IP address, FQDN, DNS address, Gateway,
Netmask address for System Manager, and the search list for the DNS address.
Syntax
changeIPFQDN -IP < > –FQDN < > -GATEWAY < >-NETMASK < > -DNS < > -SEARCH < >
Example
You can provide options in any combination that the system supports:
changeIPFQDN -IP 10.11.y.z -FQDN a.domain.weblm.com -GATEWAY 10.11.1.1 -NETMASK
255.255.255.0 -DNS 10.11.1.2 -SEARCH platform.avaya.com
changeIPFQDN -FQDN a.domain.weblm.com -GATEWAY 10.11.1.1
changeIPFQDN -IP 10.11.y.z
Note:
Copy the System
Manager service
pack or patches that
you must install to /
home/admin/.
4 update <absolute path to the Updates the ASG XML file. updateASG <absolute
ASG ASG XML file> path to the ASG XML
file>
5 config Time zone that you Configures the time zone with configureTimeZone
ureTim select the value that you select.
Select a time zone.
eZone
For example,
America/Denver
5 config <IP address of NTP Configures the NTP server configureNTP <IP
ureNTP server> details. address of NTP
server>
Separate IP addresses or
hostnames of NTP servers
with commas (,).
Test alarms
You can generate a test alarm and a clear event corresponding to the generated test alarm. The
severity level of the test alarm is minor. The clear event generated has no definite severity level. The
clear event updates the status of the test alarms from Raised to Cleared. If Secure Access Link
(SAL) Enterprise is configured to forward alarms to Avaya Data Center (ADC), the system also
forwards the test alarm and the clear event for the test alarm to the ADC.
Test Alarm Event
Test Alarm property Value
Alarm.Message Test alarm
Alarm.Severity Minor
Alarm.Status Raised
Alarm.Log.ProcessName TESTALARM
Alarm.Log.EventCode TEST_ALARM_GEN_0001
Related Links
Generating the test alarm from the web console on page 64
Generating the test alarm from CLI on page 65
3. In the Agent List section, select one or more agents for which you want to generate alarms.
4. Click Generate Test Alarm.
The system generates the alarm.
5. To view the alarm, click Events > Alarms.
To view the details of the alarm, wait until the system displays the alarms on the Alarming
page.
Note:
If the system displays SPIRIT Agent is not running, then start SAL Agent.
b. To start SAL Agent, type service spiritAgent start and press Enter.
The utils directory contains SAL Agent command line utilities.
3. To navigate to the utils directory, at the prompt, type cd $SPIRIT_HOME/scripts/
utils/and press Enter.
4. Perform one of the following:
• To generate the test alarm for System Manager, type sh generateTestAlarm.sh, and
press Enter.
• To generate the clear alarm for System Manager, type sh generateTestAlarm.sh -
c, and press Enter.
5. Perform one of the following:
• To generate the test alarm for a different product, type sh generateTestAlarm.sh -l
LOG_LOCATION -p PRODUCT_TYPE, and press Enter.
• To generate the clear alarm for a different product, type sh generateTestAlarm.sh -
c -l LOG_LOCATION -p PRODUCT_TYPE, and press Enter.
Here, LOG_LOCATION is one of the log files that the SAL agent tails for this product, and
PRODUCT_TYPE is the log product type that you configured for this product in the SAL
agent.
BIOS
For optimal performance, turn off power saving server options. See the technical data provided by
the manufacturer for your particular server regarding power saving options.
For information about how to use BIOS settings to improve the environment for latency-sensitive
workloads for an application, see the technical white paper at http://www.vmware.com/files/pdf/
techpaper/VMW-Tuning-Latency-Sensitive-Workloads.pdf.
The following sections describe the recommended BIOS settings for:
• Intel Virtualization Technology
• Dell PowerEdge Servers
• HP ProLiant Servers
Note:
The VT setting is locked as either On or Off when the server starts. After enabling VT in the
system BIOS, save your changes to the BIOS settings and exit. The BIOS changes take effect
after the host server reboots.
Other suggested BIOS settings
Servers with Intel Nehalem class and newer Intel Xeon CPUs offer two more power management
options: C-states and Intel Turbo Boost.
• Disabling C-states lowers latencies to activate the CPUs from halt or idle states to a fully active
state.
• Intel Turbo Boost steps up the internal frequency of the processor if the workload requires
more power. The default for this option is enabled. Do not change the default.
These settings depend on the OEM make and model of the server. The BIOS parameter
terminology for current Dell and HP servers are described in the following sections. Other server
models might use other terminology for the same BIOS controls.
HP ProLiant Servers
The following are the recommended BIOS settings for the HP ProLiant servers:
• Set the Power Regulator Mode to Static High Mode.
• Disable Processor C-State Support.
• Disable Processor C1E Support.
• Disable QPI Power Management.
• Enable Intel Turbo Boost.
VMware Tools
The VMware Tools utility suite is built into the application OVA. The tools enhance the performance
of the guest operating system on the virtual machine and improve the management of the virtual
machine.
VMware tools provide:
• VMware Network acceleration
• Host to Guest time synchronization
• Disk sizing
For more information about VMware tools, see Overview of VMware Tools at http://
kb.vmware.com/kb/340.
Important:
Do not upgrade the VMware tools software that is packaged with each OVA unless instructed to
do so by Avaya. The supplied version is the supported release and has been thoroughly tested.
Timekeeping
For accurate timekeeping, use the Network Time Protocol (NTP) as a time source instead of the
ESXi hypervisor.
The NTP servers can be local or over the Internet. If the NTP servers are on the Internet, the
corporate firewall must open UDP port 123 so that the NTP service can communicate with the
external NTP servers.
The VMware tools time synchronization method is disabled at application deployment time to avoid
dueling clock masters. You must configure the NTP service first because the applications are not
receiving clock updates from the hypervisor. To verify that VMware Tools Timesync is disabled, run
the command /usr/bin/vmware-toolbox-cmd timesync status.
In certain situations, the ESXi hypervisor pushes an updated view of its clock into a virtual machine.
These situations include starting the virtual machine and resuming a suspended virtual machine, If
this view differs more than 1000 seconds from the view that is received over the network, the NTP
service might shutdown. In this situation, the guest OS administrator must manually set the guest
clock to be the same or as close as possible to the network time source clock. To keep the NTP
service active, the clock on the ESXi host must also use an accurate clock source, such as the
same network time source that is used by the guest operating system. The VMware
recommendation is to add tinker panic 0 to the first line of the ntp.conf file so that the NTP can
adjust to the network time even with large differences.
If you use the names of the time servers instead of the IP address, you must configure the Domain
Name Service in the guest OS before you administer the NTP service. Otherwise, the NTP service
cannot locate the time servers. If you administer the NTP service first, you must restart the NTP
service after administering the DNS service.
After you administer the NTP service in the application, run the ntpstat or /usr/sbin/ntpq -p
command from a command window. The results from these commands:
• Verify if the NTP service is getting time from a network time source.
• Indicate which network time source is in use.
• Display how closely the guest OS matches the network time.
• Display how often the guest OS checks the time.
The guest OS polls the time source every 65 to 1024 seconds. Larger time intervals indicate that the
guest clock is tracking the network time source closely. If the time source is local, then the NTP
service is not using a network time source and a problem exists.
If the clock value is consistently wrong, look through the system log for entries regarding ntpd. The
NTP service writes the activities it performs to the log, including when the NTP service loses
synchronization with a network time source.
For more information, see Timekeeping best practices for Linux guests at http://kb.vmware.com/kb/
1006427. The article presents best practices for Linux timekeeping to achieve best timekeeping
results. The article includes:
• specifics on the particular kernel command line options to use for the Linux operating system of
interest.
• recommended settings and usage for NTP time sync, configuration of VMware Tools time
synchronization, and Virtual Hardware Clock configuration.
The date and time of the System Manager virtual machine synchronizes with the NTP
server.
6. Select the Restart NTP service to apply changes check box.
7. Click OK.
The Time Configuration page displays the date and time, NTP Servers, and the status of the
NTP client.
This configuration describes a simple version of networking Avaya applications within the same
ESXi host. Highlights to note:
• Separation of networks: VMware Management, VMware vMotion, iSCSI (SAN traffic), and
virtual machine networks are segregated to separate physical NICs.
• Teamed network interfaces: vSwitch 3 in Example 1 displays use of a load-balanced NIC team
for the Virtual Machines Network. Load balancing provides additional bandwidth for the Virtual
Machines Network, while also providing network connectivity for the virtual machines in the
case of a single NIC failure.
• Communication Manager Duplex link: Communication Manager software duplication must be
separated from all other network traffic. Example 1 displays one method of separating
Communication Manager Duplex with a port group combined with a VLAN. The
Communication Manager software duplication link must meet specific network requirements.
for more information, see Avaya PSN003556u at PSN003556u. The following are the minimum
requirements of the Communication Manager software duplex connectivity:
- The total capacity must be 1 Gbps or greater. Reserve 50 Mbps of bandwidth for duplication
data.
- The round-trip delay must be 8 ms or less.
- The round-trip packet loss must be 0.1% or less.
- Both servers duplication ports must be on the same IP subnet.
- You must disable duplication link encryption for busy-hour call rates that result in greater
than 40% CPU occupancy. You can view the CPU occupancy using the list
measurements occupancy command and looking at the results under the Static + CPU
occupancy heading.
- The system must maintain CPU occupancy on the active server (Static + CPU) at less than
65% to provide memory refresh from the active to standby server.
• Session Manager vNIC mapping: Session Manager OVA defines four separate virtual NICs
within the VM. However, Example 1 shows all interfaces networked through a single virtual
machine network, which is supported. If the Session Manager Management and Session
Manager Asset networks are separated by subnets, you can create a VLAN for the appropriate
network.
• Virtual networking: The network connectivity between virtual machines that connect to the
same vSwitch is entirely virtual. In Example 2, the virtual machine network of vSwitch3 can
communicate without entering the physical network. Virtual networks benefit from faster
communication speeds and lower management overhead.
This configuration shows a complex situation using multiple physical network interface cards. The
key differences between Example 1 and Example 2 are:
• VMware Management Network redundancy: Example 2 includes a second VMkernel Port at
vSwitch2 to handle VMware Management Network traffic. In the event of a failure of vmnic0,
VMware Management Network operations can continue on this redundant management
network.
• Removal of Teaming for Virtual Machines Network: Example 2 removes the teamed physical
NICs on vSwitch3. vSwitch3 was providing more bandwidth and tolerance of a single NIC
failure instead of reallocating this NIC to other workloads.
• Communication Manager Duplex Link: vSwitch4 is dedicated to Communication Manager
Software Duplication. The physical NIC given to vSwitch4 is on a separate physical network
that follows the requirements described in PSN003556u at PSN003556u.
• Session Manager Management Network: Example 2 shows the Session Manager Management
network separated onto its own vSwitch. The vSwitch has a dedicated physical NIC that
physically segregates the Session Manager Management network from other network traffic.
References
Title Link
Product Support Notice PSN003556u https://downloads.avaya.com/css/P8/documents/
100154621
Performance Best Practices for VMware vSphere™ Performance Best Practices for VMware vSphere™
5.0 5.0
Performance Best Practices for VMware vSphere™ http://www.vmware.com/pdf/
5.5 Perf_Best_Practices_vSphere5.5.pdf
VMware vSphere 5.0 Basics VMware vSphere Basics - ESXi 5.0
VMware vSphere 5.5 Documentation https://www.vmware.com/support/pubs/vsphere-esxi-
vcenter-server-pubs.html
VMware Documentation Sets https://www.vmware.com/support/pubs/
Storage
When you deploy Avaya Aura® System Manager in Virtualized Environment, observe the following
set of storage recommendations:
• Always deploy System Manager with a thickly provisioned disk.
• For best performance, use System Manager only on disks local to the ESXi Host, or Storage
Area Network (SAN) storage devices. Do not store System Manager on an NFS storage
system.
• By implementing thin provisioned disks, you are able to over-allocate storage. If storage is
over-allocated, thin virtual disks can grow to fill an entire datastore if left unchecked.
• If a guest operating system needs to make use of a virtual disk, the guest operating system
must first partition and format the disk to a file system it can recognize. Depending on the type
of format selected within the guest operating system, the format may cause the thin
provisioned disk to grow to full size. For example, if you present a thin provisioned disk to a
Microsoft Windows operating system and format the disk, unless you explicitly select the Quick
Format option, the Microsoft Windows format tool writes information to all of the sectors on the
disk, which in turn inflates the thin provisioned disk to full size.
Thin provisioned disks can over-allocate storage. If the storage is over-allocated, thin virtual disks
can grow to fill an entire datastore if left unchecked. You can use thin provisioned disks, but you
must use strict control and monitoring to maintain adequate performance and ensure that storage is
not completely consumed. If operational procedures are in place to mitigate the risk of performance
and storage depletion, then thin disks are a viable option.
VMware Snapshots
A snapshot preserves the state and data of a virtual machine at a specific point in time. You can
create a snapshot before upgrading or installing a patch.
The best time to take a snapshot is when no applications in the virtual machine are communicating
with other computers. The potential for problems is greatest if the virtual machine is communicating
with another computer. For example, if you take a snapshot while the virtual machine is
downloading a file from a server on the network, the virtual machine continues downloading the file
and communicating its progress to the server. If you revert to the snapshot, communications
between the virtual machine and the server are confused and the file transfer fails.
Caution:
Snapshot operations can adversely affect service. Before performing a snapshot
operation, you must stop the application that is running on the virtual machine or place
the application out-of-service. When the snapshot operation is complete, start or bring
the application back into service.
Snapshots can:
• Consume large amounts of data resources.
• Increase CPU loads on the host.
• Affect performance.
• Affect service.
To prevent adverse behaviors, consider the following recommendations when using the Snapshot
feature:
• Do not rely on VMware snapshots as a robust backup and recovery method. Snapshots are not
backups. The snapshot file is only a change log of the original virtual disk.
• Do not run a virtual machine off of a snapshot. Do not use a single snapshot for more than 24
to 72 hours.
• Take the snapshot, make the changes to the virtual machine, and delete or commit the
snapshot after you verify the virtual machine is working properly. These actions prevent
snapshots from growing so large as to cause issues when deleting or committing the
snapshots to the original virtual machine disks.
• When taking a snapshot, do not save the memory of the virtual machine. The time that the host
takes to write the memory to the disk is relative to the amount of memory that the virtual
machine is configured to use. Saving the memory can add several minutes to the time taken to
complete the operation. If the snapshot is active, saving memory can make calls appear to be
active or in progress and can cause confusion to the user. To create a clean snapshot image
from which to boot, do the following when you create a snapshot:
- In the Take Virtual Machine Snapshot window, clear the Snapshot the virtual machine’s
memory check box.
- Select the Quiesce guest file system (Needs VMware Tools installed) check box to
ensure that all write instructions to the disks are complete. You have a better chance of
creating a clean snapshot image from which to boot.
• If you are going to use snapshots for a long time, you must consolidate the snapshot files
regularly to improve performance and reduce disk usage. Before merging the snapshot delta
disks back into the base disk of the virtual machine, you must first delete stored snapshots.
Note:
If a consolidation failure occurs, end-users can use the actual Consolidate option without
opening a service request with VMware. If a commit or delete operation does not merge
the snapshot deltas into the base disk of the virtual machine, a warning is displayed in the
UI.
Related resources
Title Link
Best practices for virtual machine snapshots in the Best Practices for virtual machine snapshots in the
VMware environment VMware environment
Understanding virtual machine snapshots in VMware Understanding virtual machine snapshots in VMware
ESXi and ESX ESXi and ESX
Working with snapshots Working with snapshots
Configuring VMware vCenter Server to send alarms Send alarms when virtual machines are running from
when virtual machines are running from snapshots snapshots
Consolidating snapshots in vSphere 5.x Consolidating snapshots in vSphere 5.x
VMware Cloning
System Manager does not support VMware Cloning.
VMware vMotion
VMware uses the vMotion technology to migrate a running virtual machine from one physical server
to another physical server without incurring downtime. The migration process, also known as a hot
migration, migrates running virtual machines with zero downtime, continuous service availability,
and complete transaction integrity.
With vMotion, you can:
• Schedule migration to occur at predetermined times and without the presence of an
administrator.
• Perform hardware maintenance without scheduled downtime.
• Migrate virtual machines away from failing or underperforming servers.
Before using vMotion, you must:
• Ensure that each host that migrates virtual machines to or from the host uses a licensed
vMotion application and the vMotion is enabled.
• Ensure that you have identical vSwitches. You must enable vMotion on these vSwitches.
• Ensure that the Port Groups are identical for vMotion.
• Use a dedicated NIC to ensure the best performance.
Note:
If System Manager WebLM is being used as a master WebLM server in an enterprise licensing
deployment for a product, after migration of virtual machine to another physical server by using
vMotion, validate connectivity with added local WebLM servers. This is to ensure that the
master WebLM server can communicate with local WebLM servers.
AFS Authentication File System. AFS is an Avaya Web system that allows you
to create Authentication Files for secure Avaya Global Services logins for
supported non-Communication Manager Systems.
Avaya Appliance A physical server sold by Avaya running a VMware hypervisor that has
several virtual machines, each with its virtualized applications. The servers
can be staged with the operating system and application software already
installed. Some of the servers are sold as just the server with DVD or
software downloads.
ESXi A virtualization layer that runs directly on the server hardware. Also known
as a bare-metal hypervisor. Provides processor, memory, storage, and
networking resources on multiple virtual machines.
PLDS Product Licensing and Download System. The Avaya PLDS provides
product licensing and electronic software download distribution.
RFA Remote Feature Activation. RFA is an Avaya Web system that you use to
create Avaya License Files. These files are used to activate software
including features, capacities, releases, and offer categories. RFA also
creates Authentication Files for secure Avaya Global Services logins for
Communication Manager Systems.
SAN Storage Area Network. A SAN is a dedicated network that provides access
to consolidated data storage. SANs are primarily used to make storage
devices, such as disk arrays, accessible to servers so that the devices
appear as locally attached devices to the operating system.
Storage vMotion A VMware feature that migrates virtual machine disk files from one data
storage location to another with limited impact to end users.
vCenter Server An administrative interface from VMware for the entire virtual infrastructure
or data center, including VMs, ESXi hosts, deployment profiles, distributed
virtual networking, and hardware monitoring.
vMotion A VMware feature that migrates a running virtual machine from one
physical server to another with minimal downtime or impact to end users.
vMotion cannot be used to move virtual machines from one data center to
another.
vSphere Client The vSphere Client is a downloadable interface for administering vCenter
Server and ESXi.
F L
features best practices .........................................................67 license file
flexible footprint ....................................................................37 Avaya Aura products .................................................... 16
configuring hardware resources ................................... 37 load matrix ........................................................................... 38
footprint flexibility ................................................................. 37
footprint hardware matrix ..................................................... 38
FQDN ...................................................................................60
N
changeIPFQDN ............................................................ 61 network management systems destination ..........................66
Network Management Systems Destinations ...................... 66
G network parameters ............................................................. 24
new license file .................................................................... 34
generate test alarm ..............................................................65 NMS destination; add .......................................................... 66
generate test alarms ............................................................ 64 NMS destinations .................................................................66
generating test alarms ......................................................... 64 NTP server
Geographical Redundancy .................................................. 42 configure .......................................................................62
Geographic Redundancy ................................... 40, 47, 50, 52 NTP time ..............................................................................70
disable .......................................................................... 45 NTP time source .................................................................. 69
enable ...........................................................................44
Geographic Redundancy field descriptions ......................... 50
Geographic Redundancy key tasks ..................................... 41
O
Geo Redundancy .................................................................46 OVA deployment order ........................................................ 14
GR Health field descriptions ................................................ 52 ova file ................................................................................. 20
guidelines OVA file
deployment ................................................................... 14 deploy ..................................................................... 22, 30
overview ...............................................................................11
H
HA ........................................................................................78
P
hardware and software prerequisites on the primary and parameters
secondary servers ............................................................... 40 backup definition ...........................................................25
hardware resources patch file
configuring for flexible footprint .....................................37 install ............................................................................ 28
High Availability ................................................................... 78 performance best practices ................................................. 67
perform the System Manager tests ......................................34
I postinstall
steps ............................................................................. 34
install power on System Manager VM ........................................... 33
patch from CLI .............................................................. 62 prerequisites .................................................................. 40, 41
service pack from CLI ...................................................62
System Manager patch .................................................28
System Manager service pack from CLI .......................59
R
install authentication file .......................................................27 related documentation ........................................................... 8
install new license files ........................................................ 34 requirements
install patch from CLI ........................................................... 62 virtual machine resources .............................................17
install service pack from CLI ................................................62 resource requirements .........................................................17
install System Manager OVA file using vCenter .................. 30 resources
Intel Virtualization Technology .............................................67 server ............................................................................16
IP address ............................................................................60 restore
primary System Manager ............................................. 47
K restoring a backup from a remote server .............................56
restoring a system backup from a local server .................... 57
key tasks restoring backup; remote server .......................................... 56
Geographic Redundancy ..............................................41 restoring data backup .......................................................... 57
T
test alarm from CLI
generate ....................................................................... 65
test alarms from web console
generate ....................................................................... 64
thick deployment ..................................................................75
thin deployment ................................................................... 75
timekeeping ......................................................................... 69
time zone
configure .......................................................................62
tools and utilities .................................................................. 16
topology ............................................................................... 12
training ................................................................................... 8
U
unconfigure
Geographic Redundancy ..............................................50
updateASG .................................................................... 27, 62
upgrade
System Manager .......................................................... 62
V
verify
System Manager installation ........................................ 34
videos .................................................................................... 9
virtual machine ...............................................................22, 30
automatic restart configuration ..................................... 35
virtual machine resource requirements ................................17
vMotion ................................................................................ 78
VM properties
adjust ............................................................................ 18