Release 6.3
Issue 3
October 2013
Avaya grants you a license within the scope of the license types
described below, for which the scope of the license is detailed below.
Where the order documentation does not expressly identify a license
type, the applicable license will be a Designated System License. The
applicable number of licenses and units of capacity for which the
license is granted will be one (1), unless a different number of licenses
or units of capacity is specified in the documentation or other materials
available to you. Designated Processor means a single stand-alone
computing device. Server means a Designated Processor that hosts
a software application to be accessed by multiple users.
License types
Designated System(s) License (DS). End User may install and
use each copy of the Software only on a number of Designated
Processors up to the number indicated in the order. Avaya may
require the Designated Processor(s) to be identified in the order
by type, serial number, feature key, location or other specific
designation, or to be provided by End User to Avaya through
electronic means established by Avaya specifically for this
purpose.
Concurrent User License (CU). End User may install and use
the Software on multiple Designated Processors or one or more
Servers, so long as only the licensed number of Units are
accessing and using the Software at any given time. A Unit
means the unit on which Avaya, at its sole discretion, bases the
pricing of its licenses and can be, without limitation, an agent,
port or user, an e-mail or voice mail account in the name of a
person or corporate function (e.g., webmaster or helpdesk), or
a directory entry in the administrative database utilized by the
Software that permits one user to interface with the Software.
Units may be linked to a specific, identified Server.
Database License (DL). End User may install and use each copy
of the Software on one Server or on multiple Servers provided
that each of the Servers on which the Software is installed
communicates with no more than a single instance of the same
database.
CPU License (CP). End User may install and use each copy of
the Software on a number of Servers up to the number indicated
in the order provided that the performance capacity of the
Server(s) does not exceed the performance capacity specified
for the Software. End User may not re-install or operate the
Software on Server(s) with a larger performance capacity
without Avayas 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 Avayas sole discretion, a
Named User may be, without limitation, designated by name,
corporate function (e.g., webmaster or helpdesk), an e-mail or
voice mail account in the name of a person or corporate function,
or a directory entry in the administrative database utilized by the
Software that permits one user to interface with the Software.
Shrinkwrap License (SR). You may install and use the Software
in accordance with the terms and conditions of the applicable
license agreements, such as shrinkwrap or clickthrough
license accompanying or applicable to the Software
(Shrinkwrap License).
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/
October 2013
Copyright
Avaya and Avaya Aura are trademarks of Avaya Inc. All non-Avaya
trademarks are the property of their respective owners.
Linux is the registered trademark of Linus Torvalds.
Downloading Documentation
Virtualization
Each virtual appliance has its own ordering code. Note that each
instance of a virtual appliance must be ordered separately. If the enduser customer or Business Partner wants to install two of the same type
of virtual appliances, then two virtual appliances 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 Avayas 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(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 and product(s) should
be construed as granting, by implication, estoppel, or otherwise, any
October 2013
October 2013
Contents
Chapter 1: Introduction...................................................................................................... 7
Purpose..................................................................................................................................................... 7
Intended audience.................................................................................................................................... 7
Document changes since last issue.......................................................................................................... 7
Related resources..................................................................................................................................... 7
Avaya Mentor videos........................................................................................................................ 7
Documentation................................................................................................................................. 8
Support...................................................................................................................................................... 10
Chapter 2: Architecture overview...................................................................................... 11
Avaya Aura Virtualized Environment Overview...................................................................................... 11
Avaya Collaboration Pod for Avaya Aura Virtualized Environment........................................................ 13
VMware components................................................................................................................................ 14
Deployment guidelines.............................................................................................................................. 14
Chapter 3: Planning and configuration............................................................................. 17
Planning.................................................................................................................................................... 17
Downloading software from PLDS............................................................................................................ 18
Server hardware and resources................................................................................................................ 19
Utility Services virtual machine resource requirements............................................................................ 19
Software requirements.............................................................................................................................. 20
VMware software requirements................................................................................................................ 20
Chapter 4: Deploying and configuring Utility Services Open Virtual Application........ 21
Deployment of cloned and copied OVAs.................................................................................................. 21
Deployment and configuration on the ESXi host through the vSphere client........................................... 21
Deploying the Utility Services OVA.................................................................................................. 21
Configuring the Utility Services OVA................................................................................................ 22
Properties field descriptions............................................................................................................. 23
Deployment and configuration on vCenter through the vSphere client..................................................... 23
Deploying the Utility Services OVA.................................................................................................. 23
Configuring the Utility Services OVA................................................................................................ 25
Properties field descriptions............................................................................................................. 26
Installation of the RFA Authentication file on Utility Services.................................................................... 27
Installing the RFA Authentication file through the vSphere client..................................................... 27
Installing the RFA Authentication file through the Utility Services Web page.................................. 28
Viewing the status of the NTP server........................................................................................................ 28
Chapter 5: Configuration.................................................................................................... 31
Configuring the virtual machine automatic startup settings...................................................................... 31
Post deployment reconfiguration.............................................................................................................. 32
Reconfiguring the Utility Services OVA through the ESXi host........................................................ 33
Reconfiguring the Utility Services OVA through vCenter................................................................. 34
Chapter 6: Maintenance...................................................................................................... 37
Upgrading the Utility Services virtual machine.......................................................................................... 37
Updating patches and service packs........................................................................................................ 38
Backup and restore................................................................................................................................... 38
Include/Exclude IP Firmware option................................................................................................. 38
October 2013
Disaster Recovery............................................................................................................................
Creating a backup of Utility Services................................................................................................
Restoring a backup of Utility Services..............................................................................................
Transferring files using WinSCP...............................................................................................................
39
39
39
40
Appendix A: VMware Best Practices for performance.................................................... 41
BIOS.......................................................................................................................................................... 41
Intel Virtualization Technology support............................................................................................ 41
Dell PowerEdge Servers BIOS settings....................................................................................... 42
HP ProLiant Servers BIOS settings............................................................................................. 42
VMware Tools........................................................................................................................................... 43
Time keeping............................................................................................................................................. 43
VMware networking best practices........................................................................................................... 44
Thin vs. thick deployments........................................................................................................................ 49
VMware Features...................................................................................................................................... 50
VMware Snapshots.......................................................................................................................... 50
VMware Cloning............................................................................................................................... 51
VMware High Availability.................................................................................................................. 52
VMware vMotion............................................................................................................................... 52
VMware Storage vMotion................................................................................................................. 53
Appendix B: PCN and PSN notifications.......................................................................... 55
PCN and PSN notifications....................................................................................................................... 55
Viewing PCNs and PSNs.......................................................................................................................... 55
Signing up for PCNs and PSNs................................................................................................................ 56
Glossary............................................................................................................................... 57
Index..................................................................................................................................... 59
October 2013
Chapter 1: Introduction
Purpose
This document provides deployment checklists and procedures for installing and configuring
a reference configuration. It also describes initial administration and basic maintenance
checklists and procedures.
Intended audience
This document is intended for personnel who deploy a verified reference configuration at a
customer site.
Related resources
Avaya Mentor videos
Avaya Mentor videos are available to provide technical content on how to install, configure,
and troubleshoot Avaya products.
Videos are available on the Avaya support site, listed under the video document type, and on
the Avaya-run channel on YouTube.
October 2013
Introduction
To find videos on the Avaya support site, select the product name, and check the videos
checkbox to see a list of available videos.
Note:
Videos are not available for all products.
To find the Avaya Mentor videos on YouTube, go to http://www.youtube.com/AvayaMentor
and perform one of the following actions:
Enter a key word or key words in the Search Channel to search for a specific product
or topic.
Scroll down Playlists, and click the name of a topic to see the available list of videos
posted on the site.
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 Solution
Description
Sales Engineers,
Solution
Architects,
Implementation
Engineers,
Support
Personnel
Sales Engineers,
Solution
Architects,
Implementation
Engineers,
October 2013
Related resources
Title
Description
Audience
Support
Personnel
Sales Engineers,
Solution
Architects,
Implementation
Engineers,
Support
Personnel
Sales Engineers,
Solution
Architects,
Implementation
Engineers,
Support
Personnel
Sales Engineers,
Solution
Architects,
Implementation
Engineers,
Support
Personnel
Sales Engineers,
Solution
Architects,
Implementation
Engineers,
Support
Personnel
VMware vMotion
October 2013
Introduction
Title
VMware vSphere
Description
Audience
Architects,
Implementation
Engineers,
Support
Personnel
Sales Engineers,
Solution
Architects,
Implementation
Engineers,
Support
Personnel
Sales Engineers,
Solution
Architects,
Implementation
Engineers,
Support
Personnel
Administration
Accessing and Managing
Avaya Aura Utility Services
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.
10
October 2013
October 2013
11
Architecture overview
Customer deployment
Deployment into the blade, cluster, and server is managed by vCenter Server and vSphere
Client.
The customer provides the servers and the VMware infrastructure including the VMware
licenses.
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)
12
October 2013
Documentation
The following table lists the Avaya Collaboration Pod for Avaya Aura Virtualized Environment
documents. These documents are available on the Avaya support website at http://
support.avaya.com.
Title
Avaya Collaboration Pod for Avaya Aura
Virtualized Environment Technical
Solutions Guide
Description
Provides an overview of the solution,
specifications, and components that Avaya
Collaboration Pod for Avaya Aura
Virtualized Environment integrates.
October 2013
13
Architecture overview
VMware components
VMware Software
Component
Description
ESXi Host
ESXi Hypervisor
vSphere Client
vCenter Server
Deployment guidelines
The high-level deployment steps are:
1. Deploy the OVA or OVAs.
2. Configure the application/system.
3. Verify the installation.
The following are deployment guidelines for the virtual appliances:
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 the redundant elements
will not be on the same host.
Create a tiered or segmented cluster infrastructure that isolates critical applications, such
as Avaya Aura applications, from other virtual machines.
14
October 2013
Deployment guidelines
Ensure that you have enough resources 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
may be running at 5% occupancy, but a virtual machine may be running at 50%
occupancy. Note that a virtual machine will behave differently if the CPU usage is
higher.
October 2013
15
Architecture overview
16
October 2013
Planning
You must ensure that the customer has completed the following steps before deploying the
virtual appliance:
#
Action
Notes
October 2013
17
Procedure
1. Enter http://plds.avaya.com in your Web browser to access the Avaya PLDS
website.
2. Enter your login ID and password.
3. On the PLDS home page, select Assets.
4. Select View Downloads.
5. Click on the search icon (magnifying glass) for Company Name.
6. In the %Name field, enter Avaya or the Partner company name.
7. Click Search Companies.
8. Locate the correct entry and click the Select link.
9. Enter the Download Pub ID.
10. Click Search Downloads.
11. Scroll down to the entry for the download file and click the Download link.
12. In the Download Manager box, click the appropriate download link.
Note:
The first link, Click to download your file now, uses the Download Manager to
download the file. The Download Manager provides features to manage the
download (stop, resume, auto checksum). The click here link uses your standard
browser download and does not provide the download integrity features.
13. (Internet Explorer only) If you receive an error message, click on the install
ActiveX message at the top of the page and continue with the download.
18
October 2013
14. Select a location where you want to save the file and click Save.
15. If you used the Download Manager, click Details to view the download progress.
Value
CPU core
2.4 GHZ
CPU Reservation
n/a
Memory
1 GB
Memory reservation
n/a
Storage reservation
20 GB
Shared NICs
Network Utilization
5 Mbps
IOPS
60
Note:
In the customer environment, performance of Utility Services might vary from the average
results.
October 2013
19
Software requirements
Utility Services Release 6.2 and later can be deployed on VMware vSphere Release 5.0 or
VMware vSphere Release 5.1.VMware vSphere Release 4.1 does not support Utility Services.
The Utility Services VMware virtualization environment is packaged as a virtual appliance
ready for deployment on the VMware-certified hardware. The following table lists the software
requirements:
Equipment
Software Release
VMware Studio
2.6.0.0, 631426
VMware Tools
9.0.0.15210, 782409
6.3.0.0
20
October 2013
October 2013
21
If the OVA file is downloaded at a location accessible from your computer, click
Browse and select the file. Click Next.
If the OVA file is located on an HTTP server, enter the URL in the Deploy from
a file or URL field. Click Next.
5. Verify the template details, and click Next.
6. Accept the End User License Agreement (EULA). Click Next.
7. In the Name field, assign a name of maximum 80 characters to the new virtual
machine. Click Next.
8. Select the location to store the virtual machine files. Click Next.
9. Select Thick Provision Lazy Zeroed as the virtual disk format. Click Next.
For more information about virtual disks, see Thin vs. thick deployments.
10. Verify the deployment settings and click Finish.
Related topics:
Thin vs. thick deployments on page 49
Default Gateway
Hostname
DNS
IP address allocation for eth0
For more information about the fields, see Properties field descriptions.
9. To configure the timezone settings, select the region and the local area.
22
October 2013
10. Enter the IP address of Communication Manager used for the Utility Services virtual
machine.
11. Enter the IP address of the primary NTP server to be used for the Utility Services
virtual machine.
12. The system installs the default authentication file. You must replace the file with the
authentication file that you downloaded from RFA. For more information, see
Installation of the RFA Authentication file on Utility Services.
Related topics:
Properties field descriptions on page 23
Installation of the RFA Authentication file on Utility Services on page 27
Description
Default Gateway
Hostname
DNS
October 2013
23
24
October 2013
14. On the Ready to Complete screen, verify the deployment settings and click
Finish.
Related topics:
Viewing the status of the NTP server on page 28
Thin vs. thick deployments on page 49
October 2013
25
For more information, see Installation of the RFA Authentication file on Utility
Services.
Related topics:
Properties field descriptions on page 26
Installation of the RFA Authentication file on Utility Services on page 27
Viewing the status of the NTP server on page 28
Description
Communication Manager IP
Hostname
Timezone
NTP Server IP
Default Gateway
DNS
Network 1 IP Address
Network 1 Netmask
Related topics:
Viewing the status of the NTP server on page 28
26
October 2013
Related topics:
Transferring files using WinSCP on page 40
October 2013
27
28
October 2013
October 2013
29
30
October 2013
Chapter 5: Configuration
Procedure
1. In the vSphere Client inventory, select the host where the virtual machine is
located.
2. Click the Configuration tab.
3. In the Software section, click Virtual Machine Startup/Shutdown.
4. Click Properties in the upper right corner of the screen.
5. In the System Settings section, select Allow virtual machines to start and stop
automatically with the system.
6. In the Manual Startup section, select the virtual machine.
7. Use the Move up button to move the virtual machine under Automatic Startup.
8. Click OK.
Example
The following is an example of the Virtual Machine Startup/Shutdown screen.
October 2013
31
Configuration
32
October 2013
Procedure
1. In the vSphere Client, select the Utility Services virtual machine.
2. Click the Getting Started tab.
3. Click Power on the virtual machine.
4. Click the Console tab.
5. Log in to an account with administrative privileges.
6. Run the /opt/vsp/VMware_conf.sh command.
7. When the system prompts to continue, enter y.
8. Enter the values for the following network entities:
a.
b.
c.
d.
Default Gateway
Hostname
DNS
IP address allocation for eth0
For more information about the fields, see Properties field descriptions.
9. To configure the timezone settings, select the region and the local area.
10. Enter the IP address of Communication Manager used for the Utility Services virtual
machine.
11. Enter the IP address of the primary NTP server to be used for the Utility Services
virtual machine.
12. The system installs the default authentication file. You must replace the file with the
authentication file that you downloaded from RFA. For more information, see
Installation of the RFA Authentication file on Utility Services.
Related topics:
Properties field descriptions on page 23
Installation of the RFA Authentication file on Utility Services on page 27
October 2013
33
Configuration
Procedure
1. In the vSphere Client, select the Utility Services virtual machine.
2. Click the Getting Started tab.
3. Click Power on the virtual machine.
4. Click Edit Virtual Machine Settings. The system displays a new window containing
the details of the Utility Services virtual machine.
5. Click the Options tab.
6. Click Properties.
7. On the Properties screen, complete the following fields:
a. In the Application section, complete the following fields:
Communication Manager IP
Hostname
Timezone
NTP Server IP
b. In the Networking section, complete the following fields:
Default Gateway
DNS
Network 1 IP Address
Network 1 Netmask
For more information about the fields, see Properties field descriptions.
8. Click OK.
9. The system installs the default authentication file. You must replace the default
authentication file with the authentication file that you have downloaded from RFA.
For more information, see Installation of the RFA Authentication file on Utility
Services.
34
October 2013
Related topics:
Properties field descriptions on page 26
Installation of the RFA Authentication file on Utility Services on page 27
October 2013
35
Configuration
36
October 2013
Chapter 6: Maintenance
Related topics:
Deploying and configuring Utility Services Open Virtual Application on page 21
Creating a backup of Utility Services on page 39
Restoring a backup of Utility Services on page 39
October 2013
37
Maintenance
38
October 2013
Disaster Recovery
If the Utility Services virtual machine fails completely, you can redeploy the OVA with the same
settings used originally and restore a full backup to regain full functionality.
October 2013
39
Maintenance
4. Click Browse and select the backup file that you want to restore from the local
machine.
5. Click Upload Backup.
The system restores the backup file.
6. Click Continue.
Procedure
1. Use WinSCP to connect to the virtual machine.
2. Enter the credentials for SCP access.
3. Click OK or Continue as necessary in the warning dialogue boxes.
4. Change the file transfer protocol from SFTP to SCP.
5. Click Browse to locate and select the file.
6. In the WinSCP destination machine window, browse to /home/.
7. Select /home/customerloginname as the destination location for the file transfer.
This is likely to be the first destination when WinSCP opens.
8. Click and drag the file from the WinSCP source window to /home/
customerloginname in the WinSCP destination window.
9. Click the WinSCP Copy button to start the file transfer.
10. When the copy completes, close the WinSCP window and click OK.
40
October 2013
BIOS
For details on BIOS settings to improve the environment for latency-sensitive workloads for an
application, see the Best Practices for Performance Tuning of Latency-Sensitive Workloads in
vSphere VMs technical white paper at http://www.vmware.com/files/pdf/techpaper/VMWTuning-Latency-Sensitive-Workloads.pdf.
The following are the best performance BIOS settings for a few specific servers from the
VMware-certified server list. In general, turn off power-saving server options for optimal
performance. Consult the manufacturer technical data for your particular server.
Related topics:
Intel Virtualization Technology support on page 41
Dell PowerEdge Servers BIOS settings on page 42
HP ProLiant Servers BIOS settings on page 42
October 2013
41
Note:
The VT setting is locked (either on or off) at boot time. After enabling VT in the system BIOS,
save your changes to the BIOS settings and exit. The host server will reboot, and the BIOS
changes will take effect.
42
October 2013
VMware Tools
VMware Tools
The VMware Tools utility suite is included as part of 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.
The tools provide:
VMware Network acceleration
Host to Guest time synchronization
Disk sizing
Startup/Shutdown
See Overview of VMware Tools at http://kb.vmware.com/kb/340 for more information regarding
VMware tools.
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.
Time keeping
For accurate time keeping, use the Network Time Protocol (NTP) as a time source instead of
the ESXi hypervisor.
The NTP servers can be local to the LAN or over the Internet. If the NTP servers are on the
Internet, the corporate firewall must open UDP port 123 so that NTP service can communicate
with the external NTP servers.
VMware tools time synchronization 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 VMware Tools Timesync is Disabled,
run the command /usr/bin/vmware-toolbox-cmd timesync status.
In special situations, such as powering up the virtual machine, after vMotion, and after
resuming a suspended virtual machine, the ESXi hypervisor will push an updated view of its
clock into a virtual machine. If this view is very different from that received over the network
(over 1000 seconds), the NTP service might not adjust to the network time and shutdown. In
this situation, the guest 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
October 2013
43
on the ESXi host must also use an accurate clock source, 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.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 in setting the NTP
configuration, you must configure the Domain Name Service in the guest before administering
the NTP service. Otherwise, the NTP service will not be able to locate the time servers. If the
NTP service is administered 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 to verify the NTP service is getting time from a network
time source. The results indicate which network time source is being used, how close the guest
is to the network time, and how often the guest checks the time. The guest polls the time source
between every 65 and 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 seems to be consistently wrong, look through the system log for entries
regarding ntpd. The NTP service writes the activities it performs to the log, including when it
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. These
recommendations include specifics on the particular kernel command line options to use for
the Linux operating system of interest. There is also a description of the recommended settings
and usage for NTP time sync, configuration of VMware Tools time synchronization, and Virtual
Hardware Clock configuration to achieve best timekeeping results.
44
October 2013
October 2013
45
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
VM 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 VMs Network. Load balancing provides additional bandwidth for the VMs
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. There are several methods of doing this,
but Example 1 displays separating Communication Manager Duplex with a port group
combined with a VLAN. The Communication Manager software duplication link must meet
46
October 2013
October 2013
47
This configuration shows a more complicated situation of using more available physical
network interface cards. Highlights which differ from Example 1 include:
VMware Management Network redundancy: In this example, a second VMkernel Port has
been added to 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 VMs Network: This example removes the teamed physical NICs
on vSwitch3, which was providing more bandwidth and tolerance of a single NIC failure
in favor of reallocating this NIC to other workloads.
Communication Manager Duplex Link: vSwitch4 has been dedicated to Communication
Manager Software Duplication. The physical NIC given to vSwitch4 is on a separate
48
October 2013
References
Title
Link
PSN003556u
http://pubs.vmware.com/vsphere-51/
index.jsp
October 2013
49
VMware Features
VMware Snapshots
A snapshot preserves the state and data of a virtual machine at a specific point in time. The
snapshot is a short-term copy of the running system that is created before a major upgrade or
a patch installation.
Snapshots can:
consume large amounts of data resources.
increase CPU loads on the host.
affect performance.
affect service.
Verify that the patch installation or upgrade is successful, and ensure that the virtual application
is functional. You can then delete the snapshot
Caution:
Snapshot operations can adversely affect service. The application that is running on
the virtual machine must be stopped or set to out-of-service before you perform a
snapshot operation. When the snapshot operation has completed, the application can
then be restarted or brought back into service.
Due to the 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-72 hours. The recommended actions are to take the snapshot, make the changes
to the virtual machine, and delete or commit the snapshot as soon as the virtual machine
is verified to be working properly. 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.
When taking a snapshot, do not save the memory of the virtual machine. 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. If the snapshot is activated, saving memory will make calls
50
October 2013
VMware Features
appear to be active or in progress and can cause confusion to the user. When creating a
snapshot, make sure that you:
- uncheck the Snapshot the virtual machines memory check box in the Take
Virtual Machine Snapshot window.
- select the Quiesce guest file system (Needs VMware Tools installed) check box
to make sure all writes to the disks have completed. It gives a better chance of
creating a clean snapshot image from which to boot.
If you are going to use snapshots over a long period of time, you must consolidate the
snapshot files on a regular basis 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:
In the event of a consolidate failure, 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
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
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.x
VMware Cloning
Installing a guest operating system and applications can be time consuming. With clones, you
can make many copies of a virtual machine from a single installation and configuration process.
However, if making a clone of the Avaya Aura Utility Services, do not perform any Guest
Customization. Select Do not customize as this option is not currently supported.
October 2013
51
VMware vMotion
VMware uses the vMotion technology to migrate a running virtual machine from one physical
server to another physical server without incurring downtime. The migration process, also
known as a hot-migration, migrates running virtual machines with zero downtime, continuous
service availability, and complete transaction integrity.
With vMotion, you can
schedule migration to occur at predetermined times and without the presence of an
administrator.
perform hardware maintenance without scheduled downtime.
migrate virtual machines away from failing or under-performing servers.
Before using vMotion, you must:
ensure that each host that migrates virtual machines to or from the host uses a licensed
vMotion application and the vMotion is enabled.
ensure that you have identical vSwitches. You must enable vMotion on these
vSwitches.
ensure the Port Groups are identical for vMotion.
use a dedicated NIC to ensure the best performance.
52
October 2013
VMware Features
October 2013
53
54
October 2013
Procedure
1. Go to the Avaya Support website at http://support.avaya.com.
Note:
If the Avaya Support website displays the login page, enter your SSO login
credentials.
2. On the top of the page, click DOWNLOADS & DOCUMENTS.
3. On the Downloads & Documents page, in the Enter Your Product Here field, enter
the name of the product.
4. In the Choose Release field, select the specific release from the drop-down list.
5. Select Documents as the content type.
6. Select the appropriate filters as per your search requirement. For example, if you
select Product Support Notices, the system displays only PSNs in the documents
list.
October 2013
55
Note:
You can apply multiple filters to search for the required documents.
Procedure
1. Go to the Avaya Support Web Tips and Troubleshooting: eNotifications
Management page at https://support.avaya.com/ext/index?
page=content&id=PRCS100274#.
2. Set up e-notifications.
For detailed information, see the How to set up your E-Notifications procedure.
56
October 2013
Glossary
AFS
Application
Avaya Appliance
Blade
ESXi
Hypervisor
MAC
OVA
PLDS
Reservation
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
October 2013
57
SAN
creates Authentication Files for secure Avaya Global Services logins for
Communication Manager Systems.
SAN
Snapshot
Storage vMotion
A VMware feature that migrates virtual machine disk files from one data
storage location to another with limited impact to end users.
vCenter Server
virtual appliance
VM
vMotion
VMware HA
vSphere Client
58
October 2013
Index
deployment .......................................................... 14
A
automatic restart .........................................................31
virtual machine ..................................................... 31
B
Backup and restore .................................................... 38
best practices ........................................................41, 44
networking ............................................................44
performance ......................................................... 41
BIOS ........................................................................... 41
BIOS for Dell servers ..................................................42
BIOS for HP servers ................................................... 42
C
checklist ......................................................................17
planning procedures ............................................ 17
clones ......................................................................... 21
deployment .......................................................... 21
Collaboration Pod ....................................................... 13
components ................................................................ 14
VMware ................................................................ 14
configuring .................................................................. 31
VM automatic restart ............................................ 31
Configuring the Utility Services OVA .................... 22, 25
Creating a backup of Utility Services .......................... 39
D
Deploying and configuring Utility Services Open Virtual
Application ..................................................... 21
deploying copies .........................................................21
Deploying the Utility Services OVA ....................... 21, 23
deployment ................................................................. 49
thick ......................................................................49
thin ....................................................................... 49
deployment guidelines ................................................14
Disaster Recovery ...................................................... 39
document changes ....................................................... 7
downloading software .................................................18
using PLDS .......................................................... 18
G
guidelines ................................................................... 14
I
Include/Exclude IP Firmware option ........................... 38
Installation of the RFA Authentication file on Utility
Services ......................................................... 27
Installing the RFA Authentication File on Utility
Services ......................................................... 27
Installing the RFA Authentication file through the Utility
Services Web page ....................................... 28
Intel VT support .......................................................... 41
L
legal notice ................................................................... 2
N
networking best practices ........................................... 44
O
overview ..................................................................... 11
P
PCN ............................................................................ 55
PCN notification ..........................................................55
PCNs .......................................................................... 55
performance best practices ........................................ 41
planning procedures ................................................... 17
checklist ............................................................... 17
PLDS .......................................................................... 18
downloading software .......................................... 18
Post deployment reconfiguration ................................ 32
Properties field descriptions ..................................23, 26
PSN ............................................................................ 55
PSN notification .......................................................... 55
PSNs .......................................................................... 55
R
Reconfiguring the Utility Services OVA through the ESXi
host ................................................................ 33
October 2013
59
S
server hardware and resources ..................................19
signing up ................................................................... 56
PCNs and PSNs .................................................. 56
snapshots ................................................................... 50
software requirements ................................................ 20
support ....................................................................... 10
contact ................................................................. 10
supported versions ..................................................... 20
VMware ................................................................ 20
T
thick deployment ........................................................ 49
60
U
Updating patches and service packs ..........................38
Upgrading the Utility Services virtual machine ........... 37
Utility Services backup ............................................... 39
V
videos ........................................................................... 8
Viewing the status of the NTP server ......................... 28
virtual machine ........................................................... 31
automatic restart .................................................. 31
Virtual Machine resource requirements ...................... 19
vMotion ....................................................................... 52
VMware Cloning ......................................................... 51
VMware High Availability ............................................ 52
VMware software ........................................................20
supported ............................................................. 20
VMware Storage vMotion ........................................... 53
VMware Tools ............................................................ 43
VT support .................................................................. 41
W
WinSCP ...................................................................... 40
using .................................................................... 40
October 2013