Deploying Avaya IP Office Servers as Virtual Machines

Deploying Avaya IP Office Servers as

Virtual Machines

Release 12.1

Issue 24

October 2024

2020-2024, Avaya LLC

Notice

While reasonable efforts have been made to ensure that the

information in this document is complete and accurate at the time

of printing,

Avaya assumes no liability for any errors. Avaya reserves

the right to make changes and corrections to the information in this

document without the obligation to notify any person or organization

of such changes.

Documentation disclaimer

“Documentation” means information published in varying media

which may include product information, subscription or service

descriptions, operating instructions and performance specifications

that are generally made available to users of products.

Documentation does not include marketing materials.

Avaya shall

not be responsible for any modifications, additions, or deletions

to the original published version of Documentation unless such

modifications, additions, or deletions were performed by or on the

express behalf of

Avaya. End user agrees to indemnify and hold

harmless Avaya, Avaya's agents, servants and employees against

all claims, lawsuits, demands and judgments arising out of, or in

connection with, subsequent modifications, additions or deletions to

this documentation, to the extent made by End user.

Link disclaimer

Avaya is not responsible for the contents or reliability of any linked

websites referenced within this site or Documentation provided by

Avaya. Avaya is not responsible for the accuracy of any information,

statement or content provided on these sites and does not

necessarily endorse the products, services, or information described

or offered within them.

Avaya does not guarantee that these links will

work all the time and has no control over the availability of the linked

pages.

Warranty

Avaya provides a limited warranty on Avaya hardware and software.

Please refer to your agreement with Avaya to establish the terms of

the limited warranty. In addition, Avaya’s standard warranty language

as well as information regarding support for this product while under

warranty is available to

Avaya customers and other parties through

the Avaya Support website: https://support.avaya.com/helpcenter/

getGenericDetails?detailId=C20091120112456651010 under the link

“Warranty & Product Lifecycle” or such successor site as designated

Avaya. Please note that if the product(s) was purchased from an

authorized Avaya channel partner outside of the United States and

Canada, the warranty is provided by said Avaya Channel Partner and

not by Avaya.

“Hosted Service” means an Avaya hosted service subscription that

You acquire from either Avaya or an authorized Avaya Channel

Partner (as applicable) and which is described further in Hosted SAS

or other service description documentation regarding the applicable

hosted service. If You purchase a Hosted Service subscription,

the foregoing limited warranty may not apply but You may be

entitled to support services in connection with the Hosted Service

as described further in your service description documents for the

applicable Hosted Service. Contact

Avaya or Avaya Channel Partner

(as applicable) for more information.

Hosted Service

THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN

AVAYA HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR

AN AVAYA CHANNEL PARTNER (AS APPLICABLE), THE TERMS

OF USE FOR HOSTED SERVICES ARE AVAILABLE ON THE

AVAYA WEBSITE,

HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO

UNDER THE LINK “Avaya Terms of Use for Hosted Services”

OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND

ARE APPLICABLE TO ANYONE WHO ACCESSES OR USES THE

HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED

SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON

BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE

DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY

“YOU” AND “END USER”), AGREE TO THE TERMS OF USE.

IF YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A

COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT

YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE

OR IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF

USE, YOU MUST NOT ACCESS OR USE THE HOSTED SERVICE

OR AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED

SERVICE.

Licenses

The Global Software License Terms (“Software License Terms”)

are available on the following website https://www.avaya.com/en/

legal-license-terms/ or any successor site as designated by Avaya.

These Software License Terms are applicable to anyone who

installs, downloads, and/or uses Software and/or Documentation. By

installing, downloading or using the Software, or authorizing others to

do so, the end user agrees that the Software License Terms create

a binding contract between them and

Avaya. In case the end user is

accepting these Software License Terms on behalf of a company or

other legal entity, the end user represents that it has the authority to

bind such entity to these Software License Terms.

Except where expressly stated otherwise, no use should be made

of materials on this site, the Documentation, Software, Hosted

Service, or hardware provided by

Avaya. All content on this site, the

documentation, Hosted Service, and the product provided by Avaya

including the selection, arrangement and design of the content is

owned either by Avaya or its licensors and is protected by copyright

and other intellectual property laws including the sui generis rights

relating to the protection of databases. You may not modify, copy,

reproduce, republish, upload, post, transmit or distribute in any way

any content, in whole or in part, including any code and software

unless expressly authorized by

Avaya. Unauthorized reproduction,

transmission, dissemination, storage, or use without the express

written consent of Avaya can be a criminal, as well as a civil offense

under the applicable law.

Virtualization

The following applies if the product is deployed on a virtual machine.

Each product has its own ordering code and license types. Unless

otherwise stated, each Instance of a product must be separately

licensed and ordered. For example, if the end user customer or

Avaya Channel Partner would like to install two Instances of the

same type of products, then two products of that type must be

ordered.

Third Party Components

The following applies only if the H.264 (AVC) codec is distributed

with the product. THIS PRODUCT IS LICENSED UNDER THE AVC

PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A

CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE

REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH

THE AVC STANDARD (

“AVC VIDEO”) AND/OR (ii) DECODE AVC

VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A

PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO

PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE

IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.

ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA,

L.L.C. SEE

HTTP://WWW.MPEGLA.COM.

Service Provider

WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL

PARTNER IS HOSTING ANY PRODUCTS THAT USE OR

EMBED THE H.264 CODEC OR H.265 CODEC, THE AVAYA

CHANNEL PARTNER ACKNOWLEDGES AND AGREES THE

AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY AND

ALL RELATED FEES AND/OR ROYALTIES. THE H.264 (AVC)

CODEC IS LICENSED UNDER THE AVC PATENT PORTFOLIO

LICENSE FOR THE PERSONAL USE OF A CONSUMER

OR OTHER USES IN WHICH IT DOES NOT RECEIVE

REMUNERATION TO: (i) ENCODE VIDEO IN COMPLIANCE WITH

THE AVC STANDARD (

“AVC VIDEO”) AND/OR (ii) DECODE AVC

VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A

PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO

PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE

IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.

ADDITIONAL INFORMATION FOR H.264 (AVC) AND H.265 (HEVC)

CODECS MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://

WWW.MPEGLA.COM.

Compliance with Laws

You acknowledge and agree that it is Your responsibility to comply

with any applicable laws and regulations, including, but not limited

to laws and regulations related to call recording, data privacy,

intellectual property, trade secret, fraud, and music performance

rights, in the country or territory where the Avaya product is used.

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, please contact your Avaya

Sales Representative.

Security Vulnerabilities

Information about Avaya’s security support policies can be

found in the Security Policies and Support section of https://

support.avaya.com/security.

Suspected Avaya product security vulnerabilities are handled

per the

Avaya Product Security Support Flow (https://

support.avaya.com/css/P8/documents/100161515).

Trademarks

The trademarks, logos and service marks (“Marks”) displayed in this

site, the Documentation, Hosted Service(s), and product(s) provided

Avaya are the registered or unregistered Marks of Avaya, its

affiliates, its licensors, its suppliers, 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 LLC.

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: https://support.avaya.com, or such successor site

as designated by Avaya.

Contact Avaya Support

See the Avaya Support website: https://support.avaya.com for

Product or Cloud Service notices and articles, or to report a

problem with your

Avaya Product or Cloud Service. For a list of

support telephone numbers and contact addresses, go to the Avaya

Support website: https://support.avaya.com (or such successor site

as designated by Avaya), scroll to the bottom of the page, and select

Contact Avaya Support.

Contents

Part 1: IP Office Virtual Servers...................................................................................... 8

Chapter 1: IP Office Virtual Servers.................................................................................. 9

Duplicate IP address issue............................................................................................... 10

IP Office Anywhere.......................................................................................................... 10

Related Documentation................................................................................................... 10

Downloading documents............................................................................................ 11

Chapter 2: Virtual server licensing.................................................................................. 12

Nodal PLDS Host ID Restrictions...................................................................................... 13

Nodal License Grace Period............................................................................................. 13

Chapter 3: Differences in operation................................................................................ 14

Original RPM files not installed......................................................................................... 14

No USB support.............................................................................................................. 15

VMware tools.................................................................................................................. 15

Media Manager archiving................................................................................................. 15

Primary cannot upgrade other servers............................................................................... 15

Chapter 4: Profiling........................................................................................................... 17

Profiling considerations.................................................................................................... 17

Default virtual machine.................................................................................................... 18

Primary and secondary servers........................................................................................ 19

Server Edition Expansion Server (L)................................................................................. 20

Server Edition Application Server...................................................................................... 20

IP Office Application Server.............................................................................................. 21

Part 2: VMware.................................................................................................................... 22

Chapter 5: VMware Features............................................................................................ 23

Hardware, software and virtual machine requirements........................................................ 24

vMotion requirements...................................................................................................... 25

Disk IOPS requirements................................................................................................... 25

Alarms............................................................................................................................ 26

High availability............................................................................................................... 27

Chapter 6: VMware deployment...................................................................................... 28

Confirm the system settings............................................................................................. 28

Downloading software for VMware.................................................................................... 29

Adding the IP Office OVA Build Certificate......................................................................... 30

Deploying the VMware OVA file (vSphere web client)......................................................... 31

Adding an additional VMware hard disk (vSphere web client).............................................. 32

Deploying the VMware OVA file (vSphere desktop client)................................................... 32

Adding an additional VMware hard disk (vSphere desktop client)........................................ 33

Chapter 7: Virtual machine profiling............................................................................... 35

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 4

Comments on this document?

Adjusting the VMware RAM memory................................................................................. 36

Adjusting the VMware RAM memory (vSphere web client)............................................ 37

Adjusting the VMware RAM memory (vSphere desktop client)...................................... 37

Adjusting the VMware CPU Cores.................................................................................... 38

Adjusting the VMware CPU Cores (vSphere web client)............................................... 39

Adjusting the VMware CPU Cores (vSphere desktop client).......................................... 39

Adjusting the VMware CPU Cycles................................................................................... 40

Adjusting the VMware CPU Cycles (vSphere web client).............................................. 40

Adjusting the VMware CPU Cycles (vSphere desktop client)......................................... 41

Adjusting the VMware disk space..................................................................................... 41

Adjusting the VMware disk space (vSphere web client)................................................ 42

Adjusting the VMware disk space (vSphere desktop client)........................................... 42

Adjusting the VMware IOPS limits..................................................................................... 43

Adjusting the VMware IOPS limits (vSphere web client)................................................ 44

Adjusting the VMware IOPS limits (vSphere desktop client).......................................... 44

Powering On a VMware virtual machine............................................................................ 45

Part 3: Microsoft Hyper-V................................................................................................ 46

Chapter 8: Hyper-V deployment...................................................................................... 47

Confirm the system settings............................................................................................. 47

Downloading the software................................................................................................ 48

Copying and renaming the disk image file......................................................................... 49

Expanding the file hard disk size....................................................................................... 49

Creating a new Hyper-V virtual machine............................................................................ 50

Adding an additional hard disk.......................................................................................... 51

Hyper-V virtual machine profiling...................................................................................... 52

Adjusting the virtual machine's RAM memory settings.................................................. 53

Adjusting the virtual machine's processors.................................................................. 54

Starting the virtual machine.............................................................................................. 55

Part 4: Amazon Web Services....................................................................................... 56

Chapter 9: Amazon deployment...................................................................................... 57

AWS profiling.................................................................................................................. 58

Creating security groups.................................................................................................. 58

Launching a new instance................................................................................................ 59

Changing the security group............................................................................................. 61

Changing the machine instance........................................................................................ 61

Part 5: Microsoft Azure.................................................................................................... 62

Chapter 10: Azure virtual machine deployment............................................................. 63

Downloading the Software............................................................................................... 63

Logging in to Azure.......................................................................................................... 64

Creating a Resource Group.............................................................................................. 65

Creating a virtual network................................................................................................. 65

Uploading the VHD file to Azure....................................................................................... 66

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 5

Comments on this document?

Creating a new Azure virtual machine............................................................................... 67

Adding an Additional Disk for Media Manager.................................................................... 68

Starting an Azure Virtual Machine..................................................................................... 69

Creating a copy of an Azure VHD file................................................................................ 69

Part 6: KVM on Red Hat Linux....................................................................................... 71

Chapter 11: KVM Virtual machine deployment on Red Hat Enterprise Linux 8.10..... 72

Setting-up virtual machine support on Red Hat Enterprise Linux.......................................... 72

Setting-up Web Console on Red Hat Enterprise Linux........................................................ 74

Downloading the Software............................................................................................... 75

Copying the IP Office KVM file.......................................................................................... 76

Adding a KVM virtual machine.......................................................................................... 76

Adding an Additional Disk for Media Manager.................................................................... 77

KVM virtual machine profiling........................................................................................... 78

Adjusting the virtual machine's processors.................................................................. 79

Adjusting the virtual machine's RAM memory settings.................................................. 79

Starting the virtual machine.............................................................................................. 80

Part 7: Server Configuration.......................................................................................... 81

Chapter 12: Initial server configuration.......................................................................... 82

Connecting to the uninitialized virtual machine................................................................... 82

Setting the virtual machine's IP address............................................................................ 83

Performing server ignition................................................................................................ 84

Adding a certificate to the browser.................................................................................... 89

Adding a certificate to Firefox..................................................................................... 89

Adding a certificate to Google Chrome........................................................................ 90

Adding a certificate to Windows Edge......................................................................... 91

Adding a certificate to Mac Safari................................................................................ 91

IP Office initial configuration............................................................................................. 91

Configuring the server applications................................................................................... 92

Disabling a network port................................................................................................... 92

Disabling a network port............................................................................................. 93

Enabling a network port............................................................................................. 93

Chapter 13: Adding TTS languages................................................................................ 95

Checking the TTS languages installed.............................................................................. 95

Downloading the TTS languages...................................................................................... 96

Adding a new language................................................................................................... 96

Part 8: Upgrading............................................................................................................... 98

Chapter 14: Upgrading a virtual machine....................................................................... 99

Downloading the software.............................................................................................. 100

Backing up applications................................................................................................. 100

Transferring the ISO File................................................................................................ 101

Chapter 15: Transfer from a Remote File Server......................................................... 102

Configuring a remote file server source........................................................................... 102

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 6

Comments on this document?

Transferring the ISO from a remote server path .............................................................. 102

Upgrading using the Transferred ISO file......................................................................... 103

Chapter 16: Transfer from a primary server path........................................................ 105

Uploading an ISO file using SSH/SFTP........................................................................... 105

Transferring the ISO from a primary server path............................................................... 106

Upgrading using the Transferred ISO file......................................................................... 106

Chapter 17: Upgrade by Transfer from Your Client PC............................................... 108

Transfer the ISO from the IP Office Web Manager client PC............................................. 108

Upgrading using the Transferred ISO file......................................................................... 109

Chapter 18: Transfer from a virtual machine DVD....................................................... 110

Connect to an ISO File on the client PCs hard disk........................................................... 111

Mapping the virtual machine's DVD to a local PC ISO file (vSphere desktop client)....... 111

Mapping the virtual machine's DVD to a local PC ISO file (vSphere web client)............. 111

Connect to the client PCs DVD drive............................................................................... 112

Mapping the virtual machine’s DVD to the local PC drive (vSphere desktop client)........ 112

Mapping the virtual machine's DVD to local PC drive (vSphere web client)................... 113

Connect to an ISO File in the virtual server datastore....................................................... 113

Uploading an ISO file to the datastore (vSphere desktop client)................................... 114

Uploading an ISO file to the datastore (vSphere web client)........................................ 114

Mapping the virtual machine DVD to an ISO file in the datastore (vSphere desktop

client)..................................................................................................................... 115

Mapping the virtual machine DVD to an ISO file in the datastore (vSphere web client).. 115

Connect to the host server's DVD drive........................................................................... 116

Mapping the virtual machine DVD to the host DVD drive (vSphere desktop client)........ 116

Mapping the virtual machine DVD to the host DVD drive (vSphere web client).............. 117

Downloading the ISO from the primary DVD.................................................................... 118

Upgrading using the Transferred ISO file......................................................................... 118

Part 9: Further Help......................................................................................................... 120

Chapter 19: Additional Help and Documentation........................................................ 121

Additional Manuals and User Guides.............................................................................. 121

Getting Help.................................................................................................................. 121

Finding an Avaya Business Partner................................................................................ 122

Additional IP Office resources......................................................................................... 122

Training........................................................................................................................ 123

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 7

Comments on this document?

Part 1: IP Office Virtual Servers

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 8

Comments on this document?

Chapter 1: IP Office Virtual Servers

Avaya supports the installation of its Linux-based IP Office servers as virtualized servers. Using a

virtual software platform allows the customer's IT staff flexibility to maximize the use of the platform's

hardware to meet the individual needs of each virtual machines it hosts. It also provides them with

access to various tools that ease maintenance and monitoring processes.

• For IP Office R12.1, IP Office is supported on the following virtual server platforms:

- VMware

- Microsoft Hyper-V

- Amazon Web Services (AWS)

- Microsoft Azure

- KVM on Red Hat Enterprise Linux 8.10.

• For IP Office R12.1, the following changes to the IP Office platform affect the installation and

support on virtual server platforms:

- The Linux OS used is 64-bit only.

- UEFI booting is supported where also supported by the virtual server host platform. Where

used:

• You must configure IP Office virtual machines as Generation 2.

• You must not enable Secure Boot or equivalent features on the IP Office virtual machines.

• The IP Office virtual machines will use SCSI virtual hard drives rather than IDE.

• Avaya does not provide or support the virtual server software and hardware chosen by the

customer.

• This document outlines the steps required to deploy an IP Office server as a virtual machine.

If deploying multiple virtual machines, follow the order of deployment and configuration in the

Deploying IP Office Server Edition manual.

• Avaya only supports IP Office virtual machines created using the virtualized server images

supplied by Avaya.

• Avaya does not support IP Office virtual machines created from an IP Office ISO file.

• In addition to certified IP Office training, the installer and system maintainer must have certified

training on the specific virtual platform type or supported by someone who has the required

certification.

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 9

Comments on this document?

Related links

Duplicate IP address issue on page 10

IP Office Anywhere on page 10

Related links

IP Office Virtual Servers on page 9

IP Office Anywhere

IP Office Anywhere is a special version of the Linux-based IP Office service intended for product

demonstrations and evaluation. It includes a pre-built and pre-licensed IP Office configuration.

Anywhere can be installed on a physical server or any of the virtual platforms listed above, it is

also supported on VMware Player and Oracle VirtualBox virtual server platforms. See

Installing

the IP Office Anywhere Demonstration Software manual for installation procedure.

Related links

IP Office Virtual Servers on page 9

Related links

IP Office Virtual Servers on page 9

Downloading documents on page 11

Downloading documents

Procedure

1. Browse to http://support.avaya.com and log in.

2. Select Downloads & Documents.

3. In the Enter Your Product Here box, type IP Office.

4. Use the Choose Release drop-down to select the required IP Office release.

5. Select the content type you want included in the list of documents.

6. Click Enter.

Related links

Nodal PLDS Host ID Restrictions on page 13

Nodal License Grace Period on page 13

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 12

Comments on this document?

Nodal PLDS Host ID Restrictions

If the server is hosting its own licenses, then Avaya validates each license against the server's

unique PLDS Host ID. For an IP Office virtual machine, the IP Office generates the PLDS Host ID

based on the following factors:

• Deployment Specific Factors:

The PLDS Host ID is partially based on several factors relating to the particular virtual

machine's deployment. Redeploying the virtual machine changes its PLDS Host ID, thus

existing licenses in

IP Office configuration becomes invalid. To move to another virtual server

platform without requiring new licenses, use vMotion.

• Configuration Specific Factors:

The PLDS Host ID is also partial based on the following parameters of the virtual machine.

Changing any of these parameters changes the virtual machine's

PLDS Host ID:

- Host Name

- LAN1 IP Address

- LAN2 IP Address

- Timezone

- DHCP Mode

Related links

Virtual server licensing on page 12

Nodal License Grace Period

If the virtual machine already contains nodal licenses and the PLDS Host ID changes, the

licenses remain valid for a 30-day grace period. During those 30 days, if you make more than

five further changes to the configuration parameters existing licenses become invalid immediately.

Therefore, it is recommend that you finalize all these parameters before acquiring any licenses

from

Avaya

Related links

Virtual server licensing on page 12

Nodal PLDS Host ID Restrictions

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 13

Comments on this document?

Chapter 3: Differences in operation

The operations of the virtual IP Office servers largely matches that of the physical IP Office servers.

However, this section details known differences.

Related links

Original RPM files not installed on page 14

No USB support on page 15

VMware tools on page 15

Media Manager archiving on page 15

Primary cannot upgrade other servers on page 15

Original RPM files not installed

The installation of a non-virtual machine includes copying the original RPM files used for each

component's installation onto the server. Go to Updates menu and click Uninstall to uninstall the

component before reinstalling. The presence of the copied original RPM files allows reinstallation

on a non-virtual machine.

In order to reduce the size of the Avaya OVA file, by not including the original RPM files has the

following effects:

• You cannot reinstall the uninstalled components: You cannot reinstall a component if you

delete the

RPM file it from the server's Updates menu. Instead you need to transfer the

appropriate

RPM files to the server first.

• You cannot upgrade other servers from the Primary: If the server is a Primary Server, it

cannot be used to upgrade any Secondary Server or Expansion System (L) servers to match

its software level. However, it can be used to upgrade Expansion System (V2) servers.

You can resolve the issues by: Following the server upgrade process to upload an ISO image

to the server. This involves transferring a copy of the full ISO to the server, that automatically

unpacks a full set of RPM files necessary to upgrade both Primary and other servers.

Related links

Differences in operation on page 14

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 14

Comments on this document?

No USB support

Avaya does not support features that require access to the virtual machine's USB port. This

includes using the USB port for upgrades and for external music on hold.

Related links

Differences in operation on page 14

VMware tools

VMware tools is used by the virtual machine management software such as the vSphere client

and vCenter to complete requested administrative tasks.

Avaya packages a specific version of VMware Tools as part of the IP Office OVA. This version is

tailored for the IP Office operating system.

You should not upgrade the IP Office virtual machine version of VMware Tools except when

advised by Avaya. Doing so could destabilize operation of the virtual machine and affect its

performance.

Related links

Differences in operation on page 14

Media Manager archiving

When the Media Manager application's disk partition reaches full capacity, its starts using older

recordings archived onto a separate storage and deletes local recordings. A variety of archive

destinations are supported.

For virtual server installations, the Blu-Ray-R and DVD+RW archiving options are not supported.

Instead, the Network Attached Storage (NAS) or cloud based storage archive options must be

used. Refer to the

Administering Avaya IP Office

™

Platform Media Manager.

Related links

Differences in operation on page 14

Primary cannot upgrade other servers

In a Server Edition network, the Primary Server can upgrade its connected Secondary Server and

Expansion System (L) servers to the same software level as itself. However, this does not work if

the Primary Server is a newly installed virtual machine.

No USB support

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 15

Comments on this document?

This issue is related to the fact the OVA deployment does not include a set of the original RPM files

required for reinstallation of

IP Office components. See Original RPM files not installed on page 14

The solution is to first upgrade the Primary Server using any of the documented methods, see

Transferring the ISO File on page 101. The upgrade process includes loading all the original RPM

files onto the server which it can then use to upgrade other servers.

Related links

Differences in operation on page 14

Differences in operation

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 16

Comments on this document?

Chapter 4: Profiling

The standard IP Office virtual machine image assumes four CPUs, 3072 MB RAM and a 100 GB

hard disk (see Default virtual machine on page 18). However, you must adjust the resources

allocated to meet the intended role of the virtual machine and to optimize the use of the virtual

server platform's available resources, especially if it is supporting multiple virtual machines.

The IP Office virtual machine requirements are outlined in the following tables. Depending on the

type of virtual server, the stage at which these can be adjusted may vary.

Related links

Profiling considerations on page 17

Default virtual machine on page 18

Primary and secondary servers on page 19

Server Edition Expansion Server (L) on page 20

Server Edition Application Server on page 20

IP Office Application Server on page 21

Profiling considerations

Special factors to consider for profiling are:

• Network Ports:

You must configure all IP Office virtual machines with two Ethernet ports. If you are

using vMotion, additional network port requirement will apply, see vMotion requirements on

page 25.

• Hard disk:

Regardless of the IP Office virtual machine's role, it requires a minimum of 100 GB of

allocated hard drive space. However, if required additional hard disk space can be added.

See

Adjusting the VMware disk space on page 41.

- If it is planned to run the Media Manager service on the virtual server, the requirement for

an additional hard disk for Media Manager still applies.

• Disk Storage IOPS Requirements:

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 17

Comments on this document?

To maintain acceptable performance, the number of virtual machines using the same disk

storage and the total throughput of those machines must be within the capacity of that

storage. See Disk IOPS requirements on page 25.

• Profiling Other Virtual Machines:

It is good practice to monitor the resource utilization of all the virtual machines running in their

infrastructure. Profile all virtual machines running on the virtual server platform to fine-tune

the hardware resources allocated and used. This will improve performance by allocating

resources where needed and optimize the use of the virtual infrastructure.

• Multiple IP Office Servers:

If deploying servers with the intention of using resiliency, then the hardware resources and

profiling applied to each server must include allowance for the scenarios where users re-

there is a mix of non-virtualized and virtualized machines, then the assignment of resources

to the virtual machine must match the hardware resources available in the non-virtualized

machine.

Related links

Profiling on page 17

Default virtual machine

The IP Office virtual images install a default virtual machine that matches the profiling values for a

typical 200 user Primary Server.

Hardware

configuration

Resource Allocation Memory Hard Disk

• vCPU: 4

• RAM: 3072MB

• HDD: 1x 100 GB

• CPU: 5 GHz

• Shares: High

• Reservation: 8000 Mhz

• Limit: Unlimited

• Shares: High

• Reservation: 2765 MB

• Limit: Unlimited

• Shares: High

• Limit: Unlimited

After deployment of a virtual machine, you should optimize the resources allocated to meet the

actual requirements of the virtual machine. See Profiling on page 17. For example, if the virtual

machine supports only 50 users, you can reduce the allocated processors and RAM memory. This

allows for the best use of the overall resources provided by the virtual server platform.

Related links

Profiling on page 17

Profiling

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 18

Comments on this document?

Primary and secondary servers

The following table displays the minimum supported profile values for different IP Office virtual

machine roles in primary and secondary servers:

Server Type Primary and Secondary servers

Users

[1]

20 100 20 50 100 200 500 1000 2000 3000

one-X Portal Users

[1]

- 5 16 20 40 88 175 351 703 1500

Voicemail Channels

[1]

2 12 3 7 12 24 49 98 196 248

[2]

RAM (MB) Allocated 768 2048 2684

[5]

2684

[5]

3072 3072 4096 5120 6144 10240 14336

Reserved 625 1551 2416

[5]

2416

[5]

2624 2765 3358 4198 5376 8192 11909

CPUs 1 2–3 2–3 2–3 2–4 3–5 3–5 4–7 5–8 7–10 11-14

CPU Cycles

(GHz)

Limit 3 5 4 5 7 10 10 14 18 20 25

Reserved 3 4 3 4 6 8 8 12 15 17 21

Hard Disk (GB)

[7,8]

100 100 100 100 100 100 130 140 150 160 160

IOPS

[6]

15 31 17 18 26 41 71 129 248 338 346

AWS Machine Instance

[9]

m5.large m5.xlarge m5.2xlarge m5.4xlarge

1. If there is any profile misalignment between the user and channel quantities, use the

highest-profile that meets all requirements.

2. More than 250 recording channels with Media Manager requires approximately 12 vCPU

or 30 GHz CPU cycles in total.

3. Each one-X Portal client connection counts as one load.

4. The CPU values shown apply to all virtualization platforms. However, for Hyper-V the CPU

values should be increased by 20%.

5. If Media Manager is enabled, add 250MB RAM and increase the typical IOPS values.

6. Typical IOPS is the average HDD I/O transactions per second during normal operation.

When backup, intense logging or Media Manager are in use, more IOPS are required; 40

to 200 IOPS depending on backup data size, logging rate or recording channels.

7. Voicemail Pro requires 0.5 MB per minute for messages, prompts and announcements.

Each user and group mailbox is limited to up to 30 MB (1 hour).

8. Media Manager requires 60 KB per minute for non-authenticated VRL files and 120 KB per

minute for authenticated VRLA files. Media Manager also reserves 1 GB of space for the

call details database and other operations. Note that more than 250 channels of recording

requires at least 12 vCPUs and 30 GHz CPU cycles.

9. The quoted AWS machines instances are recommendations only. The range of machine

instances and the capabilities of existing instances change frequently. Therefore, other

instances can be used so long as their capabilities match the profiling resource

requirements.

Related links

Profiling on page 17

Primary and secondary servers

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 19

Comments on this document?

Server Edition Expansion Server (L)

Server Type Server Edition Expansion Server (L)

Users 10 50 100 200 500 750

RAM Allocated 1024 1024 1024 1024 1024 1024

Reserved 887 896 900 900 903 906

CPUs 2–3 2–3 2–3 2–3 2–3 2–3

CPU Cycles (GHz) Limit 3 3 5 5 5 6

Reserved 2 2 4 4 4 5

Hard Disk (GB) 100 100 100 100 100 100

IOPS

[1]

Typical 5 5 6 7 9 11

Notes

1. Typical IOPS is the average HDD I/O transactions per second during normal operation.

When backup, intense logging or Media Manager are in use, more IOPS are required; 40

to 200 IOPS depending on backup data size, logging rate or recording channels.

Related links

Profiling on page 17

Server Edition Application Server

These profiling values are for an IP Office Application server being used to provide one–X Portal

service support to a Server Edition/Select server that has had its own portal service switched-off in

order to increase its supportable user capacity.

Server Type Server Edition Application Server

one-X Portal Users

[1]

50 100 200 500 1000 2000 3000

RAM (MB) Allocated 3072 3072 3072 4096 6144 10240 14336

Reserved 2703 2703 2703 3548 5386 8555 12272

CPUs 2–3 2–3 2–4 3–5 4–6 4–6 4–6

CPU Cycles (GHz) Limit 6 6 7 10 11 11 11

Reserved 5 5 6 8 9 9 9

Hard Disk (GB) 100 100 100 100 100 100 100

IOPS

[2]

10 10 11 16 18 20 21

Notes

1. If there is any profile misalignment between the user and channel quantities, use the

highest-profile that meets all requirements.

Profiling

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 20

Comments on this document?

2. Typical IOPS is the average HDD I/O transactions per second during normal operation.

When backup, intense logging or Media Manager are in use, more IOPS are required; 40

to 200 IOPS depending on backup data size, logging rate or recording channels.

Related links

Profiling on page 17

IP Office Application Server

These profiling values are for an IP Office Application Server being used provide services to an

IP500 V2 running in IP Office Preferred Edition mode. This can be used to provide Voicemail Pro,

Media Manager and or one-X Portal support to the IP500 V2.

Server Type IP Office Application servers

one-X Portal Users

[1]

50 100 200 750

Voicemail Channels

[1]

20 50 100 150

RAM (MB) Allocated 3072 3072 4096 7168

Reserved 2739 2739 3420 6144

CPUs 2–3 2–3 3–5 4–7

CPU Cycles (GHz) Limit 5 5 9 13

Reserved 4 4 7 11

Hard Disk (GB)

[3, 4]

100 100 100 100

IOPS

[5]

34 49 162 318

Notes

1. If there is any profile misalignment between the user and channel quantities, use the

highest-profile that meets all requirements.

2. Each one-X Portal client connection counts as one load.

3. Voicemail Pro requires 0.5 MB per minute for messages, prompts and announcements.

Each user and group mailbox is limited to up to 30 MB (1 hour).

4. Media Manager requires 60 KB per minute for non-authenticated VRL files and 120 KB per

minute for authenticated VRLA files. Media Manager also reserves 1 GB of space for the

call details database and other operations. Note that more than 250 channels of recording

requires at least 12 vCPUs and 30 GHz CPU cycles.

5. Typical IOPS is the average HDD I/O transactions per second during normal operation.

When backup, intense logging or Media Manager are in use, more IOPS are required; 40

to 200 IOPS depending on backup data size, logging rate or recording channels.

Related links

Profiling on page 17

IP Office Application Server

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 21

Comments on this document?

Part 2: VMware

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 22

Comments on this document?

Chapter 5: VMware Features

The following VMware features are supported.

Supported Virtual Servers

Avaya supports the IP Office virtual machine on the following virtual server platforms:

• VMware vSphere: The vSphere support is:

- Supported with VMware vSphere ESXi 7.0 and 8.0.

- Support includes the Standard, Enterprise and Enterprise Plus variants. Also support for

Essentials Kit and Essentials Plus Kit variants where available.

Supported VMware Virtual Server Features

• vCenter: VMware vCenter server, is the centralized management tool for the vSphere suite.

It allows the management of multiple host servers and virtual machines on different hosts

through a single console application.

• vMotion: vMotion allows you to move an existing virtual machine from one virtual server

platform to another with minimal interruption to the operation of the virtual machine. For

example, this may be necessary if the existing server platform resources become exhausted.

see

vMotion requirements on page 25.

• Snapshot: The virtual machine must be powered off before taking or deleting a snapshot. Note

that running a virtual machine with snapshots degrades its performance. Similarly, deleting

snapshots can take some time to complete and can impact performance.

The virtual machines disk size cannot be changed if any snapshot is taken from the virtual

machine. Any existing snapshots must be deleted first.

• OVA Deployment

• Soft Power Off

• High Availability: Enables the automatic re-establishment of the virtual machine on a new

host server during a failure on or of the original host. See

High availability on page 27.

• VMware Tools: Note however that an IP Office specific version of VMware tools is included as

part of the IP Office OVA. See VMware tools on page 15.

vSphere Clients

Traditional host management used the vSphere desktop client installed on a client PC. For vSphere

5.0 onwards, VMware introduced the vSphere web client. The vSphere desktop client is still

supported, however new features released with vSphere 5.1 and higher are only managed using

the vSphere web client.

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 23

Comments on this document?

Also, using vSphere desktop client to connect to the ESXi 5.5 host and deploy the OVA will fail.

When the 5.x ESXi host version is managed by a virtual center, the vSphere desktop client's

management capabilities are restricted.

Related links

Hardware, software and virtual machine requirements on page 24

vMotion requirements on page 25

Disk IOPS requirements on page 25

Alarms on page 26

High availability on page 27

Hardware, software and virtual machine requirements

Refer to the following:

• For a searchable list of hardware platforms, refer to VMware Compatibility Guide. The

platform must support at least 2 Ethernet interfaces.

• ESXi Hardware Requirements.

• VMware Lifecycle Product Matrix for current supported VMware software.

Avaya provides IP Office virtualization software in an OVA format. The following are high-level

software and hardware requirements:

• Latest VMware vSphere software. See VMware Features on page 23.

• VMware vSphere desktop client software. vCenter is supported but not required unless using

vSphere web client.

• VMware compatible hardware platform.

• Intel-based CPUs from the Xeon family with 2 GHz clock speed or better. 2.4 GHz

recommended.

• The RAM size must satisfy the ESXi requirements in addition to the specific RAM

requirements of the virtual machines deployed. The profiling section lists the requirements

for IP Office virtual machines. 6 GB and higher is recommended.

• 2 Ethernet interfaces (more recommended if using vMotion)

To determine the required virtual server platform:

• Refer to the Default virtual machine on page 18 section to assess the total requirements for

the IP Office virtual machines.

• Add in the requirements for any other virtual machines.

• Add in the underlying requirements for the virtual server software itself.

• Note the minimum requirements above.

• Note the requirements for vMotion. See vMotion requirements on page 25.

VMware Features

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 24

Comments on this document?

• Assess the compatibility of potential server platforms using the VMware site.

Related links

VMware Features on page 23

vMotion requirements

vMotion allows you to move an existing virtual machine from one virtual server platform to another

with minimal interruption to the operation of the virtual machine. For example, this may be

necessary if the existing server platform resources become exhausted.

For IP Office virtual machines, using vMotion allows you to move the virtual machine without

changing its System Identification and requiring new IP Office licenses. If the virtual machine is

running one-X Portal, any existing sessions may have to log in again after the move.

To use vMotion:

• Each server platform requires 2 Gigabit Ethernet ports with one port dedicated to vMotion

traffic.

• The server platform CPUs must be similar, that is, from the same manufacturer and using

similar processor architectures.

• The Ethernet switch connecting the two servers must be minimum 10Gbps.

• vMotion imposes specific storage requirements. Several options exist including iSCSI and

local storage, among others. See VMware vMotion documentation for detailed requirements.

• To decrease chances of one-X Portal connectivity interruptions, it is recommended that

vMotion operation is done at times of low IP Office use.

Related links

VMware Features on page 23

Disk IOPS requirements

Input/Output Operations Per Second (IOPS) is a measurement of the traffic between a virtual

machine and the disk storage it is using. The following factors should be considered when

assessing the IOPS aspect of the virtual platform:

• The number of virtual machines running on an ESXi host should not exceed the IOPS of

the disk storage divided by 30. For example, a datastore with an IOPS of 150 should only

support up to 5 virtual machines.

• The total maximum IOPS of all the virtual machines must be within the IOPS capacity of the

datastore. To compute how many IOPS the storage supports, you need to know the hard

disk type, RAID configuration, number of drives, connection method, and so on. See Poor

performance and high disk latency with some storage configurations

vMotion requirements

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 25

Comments on this document?

• By default, no IOPS limit is set for each virtual machine disk. If limits are set, it is important

to understand how the limits are used for all virtual machines using the same datastore. The

limits are aggregated to set an overall limit for the datastore as follows:

- Example: 4 virtual machine disks using the same datastore, each disk set to 100 IOPS.

• As each disk is limited to 100, the total IOPS for the datastore is 400. If disks 1, 2 and 3

are currently using 10 IOPS each, disk 4 could use 370 IOPS without being restricted.

- Example: One disk set to Unlimited (the default), all other disks are set to 100 IOPS.

• As one of the disks is set to unlimited, the potential IOPS for the virtual machine disks

using that datastore are also unlimited.

Exceeding the IOPS capacity of the datastore will lead to unpredictable results for virtual machine

applications using that storage. Whilst a maximum IOPS limit can be applied to each virtual

machine disk, that approach is not recommended for

IP Office virtual machines as once again it

will lead to unpredictable behavior.

Related links

VMware Features on page 23

Alarms

The vSphere clients Performance tab displays performance information for individual virtual

machines and for the whole ESXi server. vCenter further extends the capabilities of monitoring

this performance on long term basis.

In addition to the above performance monitors for any virtual machines, for IP Office virtual

machines a number of specific alarms are available that can be output to other applications. The

alarms are warning alarms, critical alarms and OK alarms for when usage returns to below the

alarm threshold.

Alarm Alarm Threshold

Warning Alarm Critical Alarm

CPU Clock Cycles 90% 95%

RAM Memory 85% 97%

Hard Disk Input/Output 15% 25%

Network 15% 25%

You can view and or receive the alarms in a number of ways:

• They appear in the alarms shown by the server's web control menus. see Server Edition

documentation.

• Within the configuration of the IP Office application on the virtual machine, you can select to

output alarms to SNMP, Syslog and or email. IP Office Manager manual.

VMware Features

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 26

Comments on this document?

• System Status Application displays the alarms when connected to the virtual machine.

Related links

VMware Features on page 23

High availability

VMware High Availability (HA) allows a virtual machine to be automatically re-established on

another host machine if its normal host fails or detects a potential failure. For example:

• Host failures include power failure and ESXi kernel panic.

• A Linux operating system crash on the host server.

Backup is started up after a failure has been detected and takes a approximately 10 minutes to

complete. During the switch any unsaved data and active calls are lost.

Use of this feature is only supported for IP Office Select systems. It requires the customer data

center to include multiple host servers and for those hosts to have access to the same separate

datastore.

HA cannot be combined with IP Office resiliency as the two mechanisms conflict. For example, if

HA is enabled for a Primary Server, no primary resources (phones, hunt groups, voicemail server)

can be supported using

IP Office resilience fallback to a Secondary Server.

Related links

VMware Features on page 23

High availability

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 27

Comments on this document?

Chapter 6: VMware deployment

This document outlines the steps required to deploy an IP Office server as a virtual machine.

If deploying multiple virtual machines, follow the order of deployment and configuration in the

Deploying IP Office Server Edition manual.

• In addition to certified IP Office training, the installer and system maintainer must have certified

training on the specific virtual platform type or supported by someone who has the required

certification.

• During deployment, you must ensure that the deployment of each IP Office virtual machine

is completed, including setting the required LAN1 and LAN2 IP addresses, before starting the

deployment of another IP Office virtual machine.

Related links

Confirm the system settings on page 28

Downloading software for VMware on page 29

Adding the IP Office OVA Build Certificate on page 30

Deploying the VMware OVA file (vSphere web client) on page 31

Adding an additional VMware hard disk (vSphere web client) on page 32

Deploying the VMware OVA file (vSphere desktop client) on page 32

Adding an additional VMware hard disk (vSphere desktop client) on page 33

Confirm the system settings

Any duplication of IP addresses, even the temporary default IP addresses, causes the IP Office

application to not start and any existing IP Office service to stop.

If using local nodal licensing (see Virtual server licensing on page 12), the virtual server bases the

PLDS Host ID its uses for license validation on several server configuration settings. Hence,

before deploying the virtual machine and obtaining any licenses, you must confirm with the

customer the final values for the following:

• Host Name

• LAN1 IP Address

• LAN2 IP Address

• Timezone

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 28

Comments on this document?

• DHCP Mode

This does not apply if using WebLM centralized licensing.

Related links

VMware deployment on page 28

Hyper-V deployment on page 47

Downloading software for VMware

About this task

Avaya make a number of different file available for each IP Office release. For a VMware

deployment, select the following files:

• Avaya IP Office OVA Certificate:

You must install this certificate (AvayaIPOffice-2023-OVA-CertChain.crt) in VMware

before deploying any IP Office .ova file. VMware uses the certificate to verify the build

certificate of the

IP Office .ova files.

• OVA file:

You use this type of file for the initial deployment of a VMware virtual machine. The file is an

full machine image.

• TTS ISO:

The images used to deploy new virtual machines do not include text-to-speech (TTS)

prompts. To add TTS languages, you need to download and install the additional ISO files for

TTS languages. These are provided as 3

.iso files:

- Note: TTS files from pre-12.1 releases are not compatible with R12.1.

- DVD 1: English, Spanish, French, German, Italian.

- DVD 2: Swedish, Norwegian, Finnish, Dutch, Danish, Portuguese, Greek.

- DVD 3: Chinese, Polish, Russian.

Procedure

1. Browse to http://support.avaya.com and log in.

2. Click Support by Product and select Downloads.

3. In the Enter Product Name box, enter IP Office and select the displayed match.

4. Use the Choose Release drop-down to select the required release.

5. From the listed Downloads, select the version of release required. There are multiple

versions depending on the number of service packs and feature packs available.

6. Click on the required files and follow any further instructions shown by the website and

your browser.

Downloading software for VMware

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 29

Comments on this document?

7. Also download and read any documents shown under Related Documents

Next steps

• If not previously done, add the AvayaIPOffice-2023-OVA-CertChain.crt certificate

file to VMware (see Adding the IP Office OVA Build Certificate on page 30).

• Otherwise, proceed to deploying the new virtual machine using the VMware desktop client

(see Deploying the VMware OVA file (vSphere desktop client) on page 32) or web client

(see

Deploying the VMware OVA file (vSphere web client) on page 31).

Related links

VMware deployment on page 28

Adding the IP Office OVA Build Certificate

About this task

The latest versions of VMware ESXi 7.0/8.0 perform security checks on the build certificates

.ova and .ovf files before allowing you to use those files. See https://kb.vmware.com/s/article/

84240.

• For IP Office .ova files, you must upload the AvayaIPOffice-2023-OVA-

CertChain.crt file to VMware. You only need to perform this process once.

Before you begin

• Download the AvayaIPOffice-2023-OVA-CertChain.crt file. See Downloading

software for VMware on page 29.

Procedure

1. Login to vCenter as administrator.

2. From the drop-down menu, select Administration > Certificates > Certificate

Management.

3. Click ADD next to Trusted Roots Certificates.

4. Browse and select the AvayaIPOffice-2023-OVA-CertChain.crt certificate.

Next steps

• Proceed to deploying the new virtual machine:

- Using the VMware desktop client, see Deploying the VMware OVA file (vSphere desktop

client) on page 32.

- Using the VMware web client, see Deploying the VMware OVA file (vSphere web client) on

page 31.

Related links

VMware deployment on page 28

VMware deployment

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 30

Comments on this document?

Deploying the VMware OVA file (vSphere web client)

About this task

Deploying the OVA file to the virtual server platform creates a new virtual machine. Note that,

depending on the speed of the link between the client PC and the virtual server host, this process

can take several hours.

Procedure

1. Using the vSphere Web Client, connect to the host server onto which you want to deploy

the OVA.

2. Select Action > All vCenter Actions > Deploy OVF Template.

3. Enter the location of the OVA file. If on your PC, click Browse, select the OVA image file

and click Open and then click Next.

4. A summary of the OVA is displayed. Click Next.

5. The installer displays the license agreement. Click Accept and then click Next.

6. Enter a name for the virtual machine. This name appears in the VMware server inventory

of virtual machines it is hosting. Click Next.

7. Set the type of disk space usage to Thick Provision Eager Zeroed. Also select the

datastore that the virtual machine should use. Click

Next.

8. Select the network connections for the virtual machine. The virtual interfaces should not be

on the same LAN. Click Next.

9. Set the network addresses for the network interfaces. Click Next.

10. The install wizard displays a summary of the deployment settings. Do not select Power on

after deployment check box.

11. Click Finish.

Next steps

After the deployment is complete, the new virtual machine appears in the inventory of virtual

machines.

• If deploying a virtual machine to run Media Manager, you now need to add an additional hard

disk. See

Adding an additional VMware hard disk (vSphere web client) on page 32.

• Otherwise, you can now adjust the resource allocation of the virtual machine. See Virtual

machine profiling on page 35.

Related links

VMware deployment on page 28

Deploying the VMware OVA file (vSphere web client)

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 31

Comments on this document?

Adding an additional VMware hard disk (vSphere web

client)

About this task

To run Media Manager, you must provide the IP Office server running Voicemail Pro with an

additional hard disk. Avaya recommend that you add the additional disk before the IP Office server

initial configuration.

• The minimum supported size is 30 GB. The recommended size is 300 GB or larger.

• Media Manager requires 60 KB per minute for non-authenticated files and 120 KB per minute

for authenticated files.

• Media Manager also reserves 1 GB of space for the call details database and other

operations.

• If you need to add the additional disk after initial configuration, refer to the Administering

Avaya IP Office

™

Platform Media Manager manual for details of initializing the new disk.

Procedure

1. Using the vSphere web client, select the virtual machine. For example, select vCenter

Management and in the navigation tree on the left select the virtual machine.

2. Right-click a virtual machine in the inventory and select Edit Settings.

3. On the Virtual Hardware tab, from the New device drop-down select New Hard Disk and

click Add. The hard disk appears in the virtual hardware devices list.

4. Expand New hard disk.

5. Set the hard disk size and select the units (MB or GB) from the drop-down menu.

6. Select the datastore location where you want to store the virtual machine files.

7. For the format select Thick Provision Eager Zeroed and click Next.

Next steps

• You should now adjust the resource allocation of the virtual machine. See Virtual machine

profiling on page 35.

Related links

VMware deployment on page 28

Deploying the VMware OVA file (vSphere desktop client)

About this task

Deploying the OVA file to the virtual server platform creates a new virtual machine. Note that,

depending on the speed of the link between the client PC and the virtual server host, this process

can take several hours.

VMware deployment

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 32

Comments on this document?

Procedure

1. Using the VMware vSphere Client, connection go virtual server.

2. Select File and then select Deploy OVF TemplateDeploy OVF Template.

3. Click Browse and select the OVA image file and click Open and click Next.

4. The installer displays the license agreement. Click Accept and then click Next.

5. Enter a name for the virtual machine. This name appears in the VMware server inventory

of virtual machines it is hosting. Click Next.

6. Set the type of disk space usage to Thick Provision Eager Zeroed. Also select the

datastore that the virtual machine should use. Click Next.

7. Select the network connections for the virtual machine. The virtual interfaces should not be

on the same LAN. Click Next.

8. Set the network addresses for the network interfaces. Click Next.

9. The install wizard displays a summary of the deployment settings. Do not select Power on

after deployment check box.

10. Click Finish.

Next steps

After deployment is complete, the new virtual machine appears in the inventory of virtual

machines.

• If deploying a virtual machine to run Media Manager, you now need to add an additional hard

disk. See

Adding an additional VMware hard disk (vSphere desktop client) on page 33.

• Otherwise, you can now adjust the resource allocation of the virtual machine. See Virtual

machine profiling on page 35.

Related links

VMware deployment on page 28

Adding an additional VMware hard disk (vSphere desktop

client)

About this task

To run Media Manager, you must provide the IP Office server running Voicemail Pro with an

additional hard disk. Avaya recommend that you add the additional disk before the IP Office server

initial configuration.

• The minimum supported size is 30 GB. The recommended size is 300 GB or larger.

• Media Manager requires 60 KB per minute for non-authenticated files and 120 KB per minute

for authenticated files.

Adding an additional VMware hard disk (vSphere desktop client)

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 33

Comments on this document?

• Media Manager also reserves 1 GB of space for the call details database and other

operations.

• If you need to add the additional disk after initial configuration, refer to the Administering

Avaya IP Office

™

Platform Media Manager manual for details of initializing the new disk.

Procedure

1. Using the vSphere desktop client, select the Inventory view.

2. Locate the required virtual machine in the inventory navigation tree on the left. If not

shown, select

View > Show VMs in Inventory.

3. Click on the virtual machine.

4. Right-click on the virtual machine and select Edit Settings.

5. On the Virtual Hardware tab, click on Add and select Hard Disk and click Next

6. Select Create a new virtual disk and click Next.

7. Set the Disk Size.

8. Set the Disk Provisioning to Thick Provision Eager Zeroed.

9. Select the Datastore to use. This can be the same datastore or a different one from that

used during the OVA deployment.

10. Click Next.

11. Check the settings are as required. Click Finish.

Next steps

• You should now adjust the resource allocation of the virtual machine. See Virtual machine

profiling on page 35.

Related links

VMware deployment on page 28

VMware deployment

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 34

Comments on this document?

Chapter 7: Virtual machine profiling

After deploying a virtual machine, you must optimize its allocated resources to meet the

requirements of the virtual machine’s role, see Profiling on page 17. This allows for the best use of

the overall resources provided by the virtual server platform.

• For example, if the virtual machine will only support 50 users, you can reduce the allocated

processors and RAM memory.

Attribute Description

Memory You can set the maximum amount of RAM memory that the virtual machine can use. You can

also set how much of that RAM memory the platform guarantees for the virtual machine.

• See Adjusting the VMware RAM memory on page 36

CPU You can configure multiple virtual processor (vCPUs) for a virtual machine. A virtual machine

cannot have more vCPUs than the maximum number of logical CPUs on the host virtual server

platform. The number of logical CPUs is the number of physical processor cores.

• See Adjusting the VMware CPU Cores on page 38

CPU Clock

Cycles

You can set the maximum number of CPU clock cycles that the virtual machine can use. You

can also set the number of CPU clock cycles guaranteed for the virtual machine. Multiply the

clock cycle of the CPU with the number of allocated virtual CPU processors to determine the

aggregate value and compare it with recommended profiling values.

• See Adjusting the VMware CPU Cycles on page 40

Hard Disk By default the virtual machine is allocated a 100 GB virtual disk. However, this can be

increased if required. Note however that the size cannot be decreased at a later stage.

• See Adjusting the VMware disk space on page 41.

IOPS Input/Output Operations Per Second (IOPS) is a measurement of the traffic between a virtual

machine and the disk storage it is using.

• See Disk IOPS requirements on page 25

Network

Ports

The IP Office virtual machine deploys with two network interfaces. By default these configure

as LAN1 (192.168.42.1/255.255.255.0) and LAN2 (192.168.43.1/255.255.255.0) when the

virtual machine starts. If the LAN2 port is not required, it can be disabled, see Disabling a

network port on page 92. This reduces the chances of IP address duplication which causes

the IP Office application to not start, see Duplicate IP address issue on page 10.

After profiling, you can power on the virtual machine. See Powering On a VMware virtual

machine on page 45.

• Profiling Other Virtual Machines:

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 35

Comments on this document?

It is good practice to monitor the resource utilization of all the virtual machines running in their

infrastructure. Profile all virtual machines running on the virtual server platform to fine-tune the

hardware resources allocated and used. This will improve performance by allocating resources

where needed and optimize the use of the virtual infrastructure.

• Multiple IP Office Servers:

If deploying servers with the intention of using resiliency, then the hardware resources and

profiling applied to each server must include allowance for the scenarios where users re-

there is a mix of non-virtualized and virtualized machines, then the assignment of resources

to the virtual machine must match the hardware resources available in the non-virtualized

machine.

Related links

Adjusting the VMware RAM memory on page 36

Adjusting the VMware CPU Cores on page 38

Adjusting the VMware CPU Cycles on page 40

Adjusting the VMware disk space on page 41

Adjusting the VMware IOPS limits on page 43

Powering On a VMware virtual machine on page 45

Adjusting the VMware RAM memory

You can set the maximum amount of RAM memory that the virtual machine can use. You can also

set how much of that RAM memory the platform guarantees for the virtual machine. Set these

values to match the virtual server’s profile requirements. See Profiling on page 17.

Warning:

• The following processes can be used on a new virtual machine that has not been

powered on/started.

• To perform the same actions on an existing virtual machine, it must first be powered

off/stopped before making the adjusting and then powered on/started again. That will

interrupt all services provided by the virtual machine.

Related links

Virtual machine profiling on page 35

Adjusting the VMware RAM memory (vSphere web client) on page 37

Adjusting the VMware RAM memory (vSphere desktop client) on page 37

Virtual machine profiling

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 36

Comments on this document?

Adjusting the VMware RAM memory (vSphere web client)

Procedure

1. Using the vSphere web client, select the virtual machine. For example, select vCenter

Management and in the navigation tree on the left select the virtual machine.

2. Right-click a virtual machine in the inventory and select Edit Settings.

3. Expand the Memory.

4. In the RAM text box, type the amount of RAM to assign to the virtual machine. See

Profiling on page 17. Select whether the memory is specified in MB or GB.

5. Select the required values for reservations and shares:

• Reservation – This value sets the guaranteed minimum available RAM for the virtual

machine. You cannot set the reservation higher than the maximum memory value. For

IP Office virtual machines, the recommended value is 75-80% of the maximum.

• Shares – Select the virtual machine's relative priority for sharing the server platform

memory. The values are

Low, Normal, High and Custom. The more shares a virtual

machine has, the more often it gets a time slice of a memory when there is no

memory idle time. Shares represent a relative priority for the allocation of memory

capacity between virtual machines. For more information about share values, refer to

the VMware Resource Management Guide.

Select Normal only if the IP Office virtual machine has exclusive use of the ESXi host.

However, if other virtual machines utilizing the share mechanism present on the host,

it is imperative that

IP Office virtual machine is set to High. IP Office is a real-time

telecommunication software that requires immediate access to hardware resources.

6. Click OK.

Next steps

• If doing as part of installing a new virtual machine, continue with any further profiling required.

When completed, start the virtual machine (see

Powering On a VMware virtual machine on

page 45).

Related links

Adjusting the VMware RAM memory on page 36

Adjusting the VMware RAM memory (vSphere desktop client)

Procedure

1. Using the vSphere desktop client, select the Inventory view.

2. Locate the required virtual machine in the inventory navigation tree on the left. If not

shown, select View > Show VMs in Inventory.

3. Click on the virtual machine.

4. Right-click on the virtual machine and select Edit Settings.

5. Select Memory.

Adjusting the VMware RAM memory

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 37

Comments on this document?

6. Adjust the maximum memory size for the virtual machine. See Profiling on page 17.

7. Click the Resources tab and select Memory. Allocate the RAM for the virtual machine.

See Profiling on page 17.

• Reservation – This value sets the guaranteed minimum available RAM for the virtual

machine. You cannot set the reservation higher than the maximum memory value. For

IP Office virtual machines, the recommended value is 75-80% of the maximum.

• Shares – Select the virtual machine's relative priority for sharing the server platform

memory. The values are Low, Normal, High and Custom. The more shares a virtual

machine has, the more often it gets a time slice of a memory when there is no

memory idle time. Shares represent a relative priority for the allocation of memory

capacity between virtual machines. For more information about share values, refer to

the VMware Resource Management Guide.

Select Normal only if the IP Office virtual machine has exclusive use of the ESXi host.

However, if other virtual machines utilizing the share mechanism present on the host,

it is imperative that IP Office virtual machine is set to High. IP Office is a real-time

telecommunication software that requires immediate access to hardware resources.

8. Click OK.

Next steps

• If doing as part of installing a new virtual machine, continue with any further profiling required.

When completed, start the virtual machine (see Powering On a VMware virtual machine on

page 45).

Related links

Adjusting the VMware RAM memory on page 36

Adjusting the VMware CPU Cores

You can configure multiple virtual processor (vCPUs) for a virtual machine. A virtual machine

cannot have more vCPUs than the maximum number of logical CPUs on the host virtual server

platform. The number of logical CPUs is the number of physical processor cores.

Note that the CPU core clock speed affects the range selection. When the CPU is at the low end

toward 2 GHz, use the higher number of CPUs. When the CPU speed is higher, for example 3.6

GHz, use the lower number of CPUs.

The CPU core clock speed multiplied by the number of cores, must meet the aggregate CPU cycle

requirements of the virtual machine. See Profiling on page 17.

Related links

Virtual machine profiling on page 35

Adjusting the VMware CPU Cores (vSphere web client) on page 39

Adjusting the VMware CPU Cores (vSphere desktop client) on page 39

Virtual machine profiling

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 38

Comments on this document?

Adjusting the VMware CPU Cores (vSphere web client)

Procedure

1. Using the vSphere web client, select the virtual machine. For example, select vCenter

Management and in the navigation tree on the left select the virtual machine.

2. Right-click a virtual machine in the inventory and select Edit Settings.

3. Expand the CPU.

4. Select the number of virtual processors for the virtual machine. See Profiling on page 17

5. Click OK.

Next steps

• If doing as part of installing a new virtual machine, continue with any further profiling required.

When completed, start the virtual machine (see Powering On a VMware virtual machine on

page 45).

Related links

Adjusting the VMware CPU Cores on page 38

Adjusting the VMware CPU Cores (vSphere desktop client)

Procedure

1. Using the vSphere desktop client, select the Inventory view.

2. Locate the required virtual machine in the inventory navigation tree on the left. If not

shown, select

View > Show VMs in Inventory.

3. Click on the virtual machine.

4. Right-click on the virtual machine and select Edit Settings.

5. Click the Hardware tab and select CPU.

6. Select the number of virtual processors for the virtual machine. See Profiling on page 17

7. Click OK.

Next steps

• If doing as part of installing a new virtual machine, continue with any further profiling required.

When completed, start the virtual machine (see Powering On a VMware virtual machine on

page 45).

Related links

Adjusting the VMware CPU Cores on page 38

Adjusting the VMware CPU Cores

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 39

Comments on this document?

Adjusting the VMware CPU Cycles

You can set the maximum number of CPU clock cycles that the virtual machine can use. You can

also set the number of CPU clock cycles guaranteed for the virtual machine.

Multiply the clock cycle of the CPU with the number of allocated virtual CPU processors

to determine the aggregate value and compare it with recommended profiling values. See

Profiling on page 17.

Related links

Virtual machine profiling on page 35

Adjusting the VMware CPU Cycles (vSphere web client) on page 40

Adjusting the VMware CPU Cycles (vSphere desktop client) on page 41

Adjusting the VMware CPU Cycles (vSphere web client)

Procedure

1. Using the vSphere web client, select the virtual machine. For example, select vCenter

Management and in the navigation tree on the left select the virtual machine.

2. Right-click a virtual machine in the inventory and select Edit Settings.

3. On the Virtual Hardware tab, expand CPU.

4. Allocate the CPU cycles for the virtual machine's vCPUs. See Profiling on page 17

• Reservation – This value sets the guaranteed minimum available RAM for the virtual

machine. You cannot set the reservation higher than the maximum memory value. For

IP Office virtual machines, the recommended value is 75-80% of the maximum.

• Shares – The more shares a virtual machine has, the more often it gets a time slice

of a CPU when there is no CPU idle time. Shares represent a relative priority for the

allocation of memory capacity between virtual machines. For more information about

share values, refer to the

VMware Resource Management Guide.

- Select Normal only if the IP Office virtual machine has exclusive use of the ESXi

host. However, if other virtual machines utilizing the share mechanism present on

the host, it is imperative that IP Office virtual machine is set to High. IP Office is

a real-time telecommunication software that requires immediate access to hardware

resources.

5. Click OK.

Next steps

• If doing as part of installing a new virtual machine, continue with any further profiling required.

When completed, start the virtual machine (see

Powering On a VMware virtual machine on

page 45).

Related links

Adjusting the VMware CPU Cycles on page 40

Virtual machine profiling

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 40

Comments on this document?

Adjusting the VMware CPU Cycles (vSphere desktop client)

Procedure

1. Using the vSphere desktop client, select the Inventory view.

2. Locate the required virtual machine in the inventory navigation tree on the left. If not

shown, select

View > Show VMs in Inventory.

3. Click on the virtual machine.

4. Right-click on the virtual machine and select Edit Settings.

5. Click the Resources tab and select CPU.

6. Allocate the CPU cycles for the virtual machine's vCPUs. See Profiling on page 17

• Reservation – This value sets the guaranteed minimum available RAM for the virtual

machine. You cannot set the reservation higher than the maximum memory value. For

IP Office virtual machines, the recommended value is 75-80% of the maximum.

• Shares – The more shares a virtual machine has, the more often it gets a time slice

of a CPU when there is no CPU idle time. Shares represent a relative priority for the

allocation of memory capacity between virtual machines. For more information about

share values, refer to the VMware Resource Management Guide.

- Select Normal only if the IP Office virtual machine has exclusive use of the ESXi

host. However, if other virtual machines utilizing the share mechanism present on

the host, it is imperative that

IP Office virtual machine is set to High. IP Office is

a real-time telecommunication software that requires immediate access to hardware

resources.

7. Click OK.

Next steps

• If doing as part of installing a new virtual machine, continue with any further profiling required.

When completed, start the virtual machine (see

Powering On a VMware virtual machine on

page 45).

Related links

Adjusting the VMware CPU Cycles on page 40

Adjusting the VMware disk space

By default the virtual machine is allocated a 100 GB virtual disk. However, this can be increased to

meet the virtual server’s profiling requirements. See Profiling on page 17.

Note however:

• The disk size cannot be decreased at a later stage.

• The virtual machines disk size cannot be changed if any snapshot have been taken of the

virtual machine. Any existing snapshots must first be deleted.

Adjusting the VMware disk space

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 41

Comments on this document?

The process for increasing the disk size takes two parts:

• Using a vSphere client, increase the virtual machine's disk size and then restart the virtual

machine.

• Using the server's IP Office web management menus, indicate to use the additional space

and restart the server.

Related links

Virtual machine profiling on page 35

Adjusting the VMware disk space (vSphere web client) on page 42

Adjusting the VMware disk space (vSphere desktop client) on page 42

Adjusting the VMware disk space (vSphere web client)

Procedure

1. Using the vSphere web client, select the virtual machine. For example, select vCenter

Management and in the navigation tree on the left select the virtual machine.

2. Right-click a virtual machine in the inventory and select Edit Settings.

3. Click the Hardware tab and select the hard disk to modify.

4. Select a Virtual Device Node type from the drop-down menu.

5. To change the size of the disk, enter a new value in the Provisioned Size text box. See

Profiling on page 17.

6. Click OK.

7. Right-click on the virtual machine and select Power > Power Off.

Next steps

• If doing as part of installing a new virtual machine, continue with any further profiling required.

When completed, start the virtual machine (see Powering On a VMware virtual machine on

page 45).

Related links

Adjusting the VMware disk space on page 41

Adjusting the VMware disk space (vSphere desktop client)

Procedure

1. Using the vSphere desktop client, select the Inventory view.

2. Locate the required virtual machine in the inventory navigation tree on the left. If not

shown, select View > Show VMs in Inventory.

3. Click on the virtual machine.

4. Right-click on the virtual machine and select Edit Settings.

5. Click the Hardware tab and select the hard disk to modify.

Virtual machine profiling

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 42

Comments on this document?

6. Select a Virtual Device Node type from the drop-down menu.

7. To change the size of the disk, enter a new value in the Provisioned Size text box. See

Profiling on page 17.

8. Click OK.

9. Right-click on the virtual machine and select Power > Power Off.

Next steps

• If doing as part of installing a new virtual machine, continue with any further profiling required.

When completed, start the virtual machine (see

Powering On a VMware virtual machine on

page 45).

Related links

Adjusting the VMware disk space on page 41

Adjusting the VMware IOPS limits

Input/Output Operations Per Second (IOPS) is a measurement of the traffic between a virtual

machine and the disk storage it is using.

The following factors should be considered when assessing the IOPS aspect of the virtual

platform:

• The number of virtual machines running on an ESXi host should not exceed the IOPS of

the disk storage divided by 30. For example, a datastore with an IOPS of 150 should only

support up to 5 virtual machines.

• The total maximum IOPS of all the virtual machines must be within the IOPS capacity of the

datastore. To compute how many IOPS the storage supports, you need to know the hard

disk type, RAID configuration, number of drives, connection method, and so on. See VMware

Knowledge Base.

• By default no IOPS limit is set for each virtual machine disk. However, an IOPS limit can

be set. If limits are set, it is important to understand how the limits are used for all virtual

machines using the same datastore. The limits are aggregated to set an overall limit for the

datastore as follows:

- Example: 4 virtual machine disks using the same datastore and each disk set to 100 IOPS

As each disk is limited to 100, the total IOPS for the datastore is 400. If disks 1, 2 and 3

are currently using 10 IOPS each, disk 4 could use 370 IOPS without being restricted.

- Example: One disk set to Unlimited (the default), all other disks are set to 100 IOPS As

one of the disks is set to unlimited, the potential IOPS for the virtual machine disks using

that datastore are also unlimited.

Exceeding the IOPS capacity of the datastore will lead to unpredictable results for virtual machine

applications using that storage. Whilst a maximum IOPS limit can be applied to each virtual

machine disk, that approach is not recommended for IP Office virtual machines as once again it

will lead to unpredictable behavior.

Adjusting the VMware IOPS limits

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 43

Comments on this document?

Warning:

• The following processes can be used on a new virtual machine that has not been

powered on/started.

• To perform the same actions on an existing virtual machine, it must first be powered

off/stopped before making the adjusting and then powered on/started again. That will

interrupt all services provided by the virtual machine.

Related links

Virtual machine profiling on page 35

Adjusting the VMware IOPS limits (vSphere web client) on page 44

Adjusting the VMware IOPS limits (vSphere desktop client) on page 44

Adjusting the VMware IOPS limits (vSphere web client)

Procedure

1. Using the vSphere web client, select the virtual machine. For example, select vCenter

Management and in the navigation tree on the left select the virtual machine.

2. Right-click a virtual machine in the inventory and select Edit Settings.

3. Click the Virtual Hardware tab and expand Hard Disk.

4. Select a virtual hard disk from the list.

5. Under Shares, click the drop-down menu and select the relative amount of shares to

allocate to the virtual machine (

Low, Normal or High). You can select Custom to enter a

user-defined shares value. Higher shares allow a virtual machine to keep more concurrent

I/O operations pending at the storage device or datastore compared to a virtual machine

with lower shares.

6. Under Limit — IOPS, click the drop-down menu and enter the upper limit of storage

resources to allocate to the virtual machine. By default, IOPS are unlimited. You can

selectLow (500), Normal (1000), or High (2000), or you can select Custom to enter a

user-defined number of shares.

7. Click OK.

Next steps

• If doing as part of installing a new virtual machine, continue with any further profiling required.

When completed, start the virtual machine (see Powering On a VMware virtual machine on

page 45).

Related links

Adjusting the VMware IOPS limits on page 43

Adjusting the VMware IOPS limits (vSphere desktop client)

Procedure

1. Using the vSphere desktop client, select the Inventory view.

Virtual machine profiling

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 44

Comments on this document?

2. Locate the required virtual machine in the inventory navigation tree on the left. If not

shown, select View > Show VMs in Inventory.

3. Click on the virtual machine.

4. Click the Resources tab.

5. Select Hard Disk.

6. In Limit — IOPS set the required IOPS limit for each disk the virtual machine uses. See

Profiling on page 17. By default, the limits are set to Unlimited.

7. Click OK.

Next steps

• If doing as part of installing a new virtual machine, continue with any further profiling required.

When completed, start the virtual machine (see Powering On a VMware virtual machine on

page 45).

Related links

Adjusting the VMware IOPS limits on page 43

Powering On a VMware virtual machine

About this task

Following profiling of the virtual machine, you can power on the virtual server.

Procedure

1. Right-click on the virtual machine.

2. Select Power > Power On.

Next steps

• You can now use a web browser to access the virtual machine. See Connecting to the

uninitialized virtual machine on page 82.

• As part of the deployment of a new virtual machine, you now need to complete the initial

server configuration processes.

Related links

Virtual machine profiling on page 35

Powering On a VMware virtual machine

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 45

Comments on this document?

Part 3: Microsoft Hyper-V

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 46

Comments on this document?

Chapter 8: Hyper-V deployment

IP Office server's are supported as Hyper-V virtual machines.

• Supported virtual machine platforms are Hyper-V running on Windows 2016, Windows 2019

and Windows 2022 servers and on Microsoft Hyper-V Server 2016, 2019 and 2022.

• The installation is performed using a Hyper-V disk image file (VHDX) downloaded from the

Avaya support website.

• Virtual Server Edition/IP Office Select servers require Virtualized Server licenses. See Virtual

server licensing on page 12.

• This document outlines the steps required to deploy an IP Office server as a virtual machine.

If deploying multiple virtual machines, follow the order of deployment and configuration in the

Deploying IP Office Server Edition manual.

• In addition to certified IP Office training, the installer and system maintainer must have certified

training on the specific virtual platform type or supported by someone who has the required

certification.

• During deployment, you must ensure that the deployment of each IP Office virtual machine

is completed, including setting the required LAN1 and LAN2 IP addresses, before starting the

deployment of another

IP Office virtual machine.

Related links

Confirm the system settings on page 28

Downloading the software on page 48

Copying and renaming the disk image file on page 49

Expanding the file hard disk size on page 49

Creating a new Hyper-V virtual machine on page 50

Adding an additional hard disk on page 51

Hyper-V virtual machine profiling on page 52

Starting the virtual machine on page 55

Confirm the system settings

Any duplication of IP addresses, even the temporary default IP addresses, causes the IP Office

application to not start and any existing IP Office service to stop.

If using local nodal licensing (see Virtual server licensing on page 12), the virtual server bases the

PLDS Host ID its uses for license validation on several server configuration settings. Hence,

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 47

Comments on this document?

before deploying the virtual machine and obtaining any licenses, you must confirm with the

customer the final values for the following:

• Host Name

• LAN1 IP Address

• LAN2 IP Address

• Timezone

• DHCP Mode

This does not apply if using WebLM centralized licensing.

Related links

VMware deployment on page 28

Hyper-V deployment on page 47

Downloading the software

About this task

Avaya make a number of different file available for each IP Office release. For a Hypervisor

deployment, select the following files:

• VHDX file: (Hypervisor)

The downloaded is a .zip file from which you can extract the .vhdx file. The file is a hard

disk image. In the process of creating a new virtual machine, the file becomes the virtual

machine's hard disk.

• TTS ISO:

The images used to deploy new virtual machines do not include text-to-speech (TTS)

prompts. To add TTS languages, you need to download and install the additional ISO files for

TTS languages. These are provided as 3

.iso files:

- Note: TTS files from pre-12.1 releases are not compatible with R12.1.

- DVD 1: English, Spanish, French, German, Italian.

- DVD 2: Swedish, Norwegian, Finnish, Dutch, Danish, Portuguese, Greek.

- DVD 3: Chinese, Polish, Russian.

Procedure

1. Browse to http://support.avaya.com and log in.

2. Click Support by Product and select Downloads.

3. In the Enter Product Name box, enter IP Office and select the displayed match.

4. Use the Choose Release drop-down to select the required release.

Hyper-V deployment

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 48

Comments on this document?

5. From the listed Downloads, select the version of release required. There are multiple

versions depending on the number of service packs and feature packs available.

6. Click on the required files and follow any further instructions shown by the website and

your browser.

7. Also download and read any documents shown under Related Documents

Next steps

• Copy and rename the VHDX file. See Copying and renaming the disk image file on page 49.

Related links

Hyper-V deployment on page 47

Copying and renaming the disk image file

About this task

The file used when creating a new virtual machine becomes the hard disk of that virtual machine.

It cannot then be used to create another new virtual machine. Therefore, it is important to use a

copy of the downloaded file, especially if you are planning to create several virtual machines.

Procedure

1. Download the zipped file for the required software release. See Downloading software for

VMware on page 29.

2. Unzip the VHDX file and copy the file to a personal folder. Keep this file as your master

copy for that software release.

3. Save a copy of the file and rename it.

4. Move the renamed file to the folder on the Hyper-V server used to store virtual

machine disks. By default it is C:\Users\Public\Documents\Hyper-V\Virtual

Hard Disks.

Next steps

• Now adjust the disk size. See Expanding the file hard disk size on page 49.

Related links

Hyper-V deployment on page 47

Expanding the file hard disk size

About this task

The default hard disk size set in the downloaded file is 100 GB. This may need to be expanded

depending on planned role of the virtual machine. See Profiling on page 17.

Copying and renaming the disk image file

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 49

Comments on this document?

Procedure

1. In Hyper-V Manager, select Action > Edit Disk.

2. In the Locate Disk menu, enter the file path of the VHDX file or browse to the file and click

Next.

3. In the Choose Action menu select Expand and click Next.

4. In the Configure Disk menu set the new size required and click Next.

5. In the Summary menu check the settings. If okay click Finish.

Next steps

• You can now proceed with using the file to create a new virtual machine. See Creating a new

Hyper-V virtual machine on page 50.

Related links

Hyper-V deployment on page 47

Creating a new Hyper-V virtual machine

About this task

After preparing a new VHDX file for the virtual machine, you can use it to create a new virtual

machine.

Before you begin

• Copy and rename and the download VHDX file, see Copying and renaming the disk image

file on page 49. The copy becomes the hard disk of the new virtual machine. Therefore, you

cannot use it for other virtual machines.

Procedure

1. From the Hyper-V Manager menu bar, select Action > New > Virtual Machine.

Alternatively, you can go to Actions panel, and select New > Virtual Machine.

2. Click Next.

3. Rename the virtual machine you are creating and click Next.

4. On the Specify Generation page, select Generation 2. Click Next.

5. In Assign Memory menu, you can set the memory to match the recommend settings for

the server's planned role, see Profiling on page 17. However, you can accept the default

and adjust the memory later during the virtual machine profiling stage. Click Next.

6. In Configure Networking menu, select the network connection that the new virtual

machine should use. Note that the IP Office image expects to obtain an initial IP address

from that network using DHCP. You can change the address after starting the virtual

machine. Click Next.

7. In the Connect Virtual Hard Disk menu, select Use an existing virtual hard disk.

Hyper-V deployment

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 50

Comments on this document?

8. Browse to and select the VHDX file that you prepared for this new virtual machine and click

Next.

Warning:

• Use the copy of the VHDX file for the installation. Do not use the original file

downloaded for the Avaya support site or any copy already used for another virtual

machine. The copy you use becomes the hard disk of the new virtual machine.

9. In the Summary menu, click Finish. The new virtual machine should now appear in the list

of virtual machines.

10. Do not start the virtual machine at this stage.

11. Right-click on the new virtual machine and select Settings.

12. Select Security. Check that Enable Secure Boot is not selected. Click OK.

Next steps

• Do not start the virtual machine at this stage:

- If intending to support Media Manager, see Adding an additional hard disk on page 51.

- Otherwise, perform virtual machine profiling, see Virtual machine profiling on page 35.

Related links

Hyper-V deployment on page 47

Adding an additional hard disk

About this task

To run Media Manager, you must provide the IP Office server running Voicemail Pro with an

additional hard disk. Avaya recommend that you add the additional disk before the IP Office server

initial configuration.

• The minimum supported size is 30 GB. The recommended size is 300 GB or larger.

• Media Manager requires 60 KB per minute for non-authenticated files and 120 KB per minute

for authenticated files.

• Media Manager also reserves 1 GB of space for the call details database and other

operations.

• If you need to add the additional disk after initial configuration, refer to the Administering

Avaya IP Office

™

Platform Media Manager manual for details of initializing the new disk.

Procedure

1. In the list of virtual machines, select the required virtual machine.

2. Right-click and select Connect.

3. If the virtual machine is already running, stop it by clicking the . This stops the services

provided by the virtual machine.

Adding an additional hard disk

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 51

Comments on this document?

4. In the virtual machine connection window, select File > Settings.

5. Select SCSI Controller.

6. Select Hard Drive and click Add.

7. Select Virtual hard disk and click New.

8. Click Next.

9. In the Choose Disk Format menu, select VHDX. Click Next.

10. In the Choose Disk Type menu, select how you want the disk file to behave. Click Next.

11. In the Specify Name and Location menu, enter the name and location for the new virtual

hard disk file. Click Next.

12. Set the size for the new disk. Click Next.

13. In the Summary menu check the settings. If okay, click Finish.

14. Click Apply and then click OK.

Next steps

• Do not start the virtual machine. Instead, perform any required virtual machine profiling, see

Virtual machine profiling on page 35.

Related links

Hyper-V deployment on page 47

Hyper-V virtual machine profiling

After deploying a virtual machine, you must optimize its allocated resources to meet the

requirements of the virtual machine’s role, see Profiling on page 17. This allows for the best

use of the overall resources provided by the virtual server platform.

Attribute Description

Memory You can set the maximum amount of RAM memory that the virtual machine can use. You can

also set how much of that RAM memory the platform guarantees for the virtual machine.

See Adjusting the virtual machine's RAM memory settings on page 53.

Processors You can configure multiple virtual processor (vCPUs) for a virtual machine. A virtual machine

cannot have more vCPUs than the maximum number of logical CPUs on the host virtual server

platform. The number of logical CPUs is the number of physical processor cores.

See Adjusting the virtual machine's processors on page 54.

After profiling, you can start the virtual machine.

• Profiling Other Virtual Machines:

It is good practice to monitor the resource utilization of all the virtual machines running in their

infrastructure. Profile all virtual machines running on the virtual server platform to fine-tune

Hyper-V deployment

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 52

Comments on this document?

the hardware resources allocated and used. This will improve performance by allocating

resources where needed and optimize the use of the virtual infrastructure.

• Multiple IP Office Servers:

If deploying servers with the intention of using resiliency, then the hardware resources and

profiling applied to each server must include allowance for the scenarios where users re-

there is a mix of non-virtualized and virtualized machines, then the assignment of resources

to the virtual machine must match the hardware resources available in the non-virtualized

machine.

Related links

Hyper-V deployment on page 47

Adjusting the virtual machine's RAM memory settings on page 53

Adjusting the virtual machine's processors on page 54

Adjusting the virtual machine's RAM memory settings

About this task

You can set the maximum amount of RAM memory that the virtual machine can use. You can also

set how much of that RAM memory the platform guarantees for the virtual machine. Set these

values to match the virtual server’s profile requirements. See

Profiling on page 17.

Before you begin

• The following processes can be used on a new virtual machine that has not been powered

on/started.

• To perform the same actions on an existing virtual machine, it must first be powered off/

stopped before making the adjusting and then powered on/started again. That will interrupt all

services provided by the virtual machine.

Procedure

1. In the list of virtual machines, select the required virtual machine.

2. Right-click and select Connect.

3. If the virtual machine is already running, stop it by clicking the . This stops the services

provided by the virtual machine.

4. In the virtual machine connection window, select File > Settings.

5. Select Memory.

6. Adjust the memory settings to match the recommended settings for the server role. See

Profiling on page 17

7. Click Apply.

Next steps

• If doing as part of installing a new virtual machine, continue with any further profiling required.

When completed, start the virtual machine (see

Starting the virtual machine on page 55).

Hyper-V virtual machine profiling

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 53

Comments on this document?

Related links

Hyper-V virtual machine profiling on page 52

Adjusting the virtual machine's processors

About this task

You can configure multiple virtual processor (vCPUs) for a virtual machine. A virtual machine

cannot have more vCPUs than the maximum number of logical CPUs on the host virtual server

platform. The number of logical CPUs is the number of physical processor cores.

Note that the CPU core clock speed affects the range selection. When the CPU is at the low end

toward 2 GHz, use the higher number of CPUs. When the CPU speed is higher, for example 3.6

GHz, use the lower number of CPUs.

The CPU core clock speed multiplied by the number of cores, must meet the aggregate CPU cycle

requirements of the virtual machine. See Profiling on page 17.

Before you begin

• The following processes can be used on a new virtual machine that has not been powered

on/started.

• To perform the same actions on an existing virtual machine, it must first be powered off/

stopped before making the adjusting and then powered on/started again. That will interrupt all

services provided by the virtual machine.

Procedure

1. In the list of virtual machines, select the required virtual machine.

2. Right-click and select Connect.

3. If the virtual machine is already running, stop it by clicking the . This stops the services

provided by the virtual machine.

4. In the virtual machine connection window, select File > Settings.

5. Select Processor.

6. Adjust the settings to match the recommended settings for the server role. See Profiling on

page 17.

7. Click Apply.

Next steps

• If doing as part of installing a new virtual machine, continue with any further profiling required.

When completed, start the virtual machine (see Starting the virtual machine on page 55).

Related links

Hyper-V virtual machine profiling on page 52

Hyper-V deployment

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 54

Comments on this document?

Starting the virtual machine

About this task

Having installed and profiled the new virtual machine, it can be started. This will boot it from the

virtual hard disk file after which the initial IP Office server configuration can be started. See Initial

server configuration on page 82.

Procedure

1. In the list of virtual machines, select the required virtual machine.

2. Right-click and select Connect.

3. In the virtual machine connection window click on the icon or alternatively select

Action > Start to start the virtual machine.

• For a new virtual machine, the virtual machine now goes through start up processes

such as partition resizing. This can take up to 15 minutes to complete.

• The server displays the address details for further configuration of the server.

Next steps

• Use the address shown to start the initial server configuration process. See Initial server

configuration on page 82.

Related links

Hyper-V deployment on page 47

Starting the virtual machine

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 55

Comments on this document?

Part 4: Amazon Web Services

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 56

Comments on this document?

Chapter 9: Amazon deployment

IP Office server's are supported as AWS virtual machines, referred to as 'instances'. Each AWS

instance is created using a combination of parts:

• Machine Instance:

This defines the processor and memory and other factors of the platform on which

the virtual machine is run. AWS provide a range of different machine instances (https://

aws.amazon.com/ec2/instance-types). The machine instance selected should match the

profiling requirements of the server's intended IP Office role. See AWS profiling on page 58.

• Disk Storage:

Storage can be associated with the virtual machine. AWS supports several different types of

storage, however for

IP Office it is assumed that a drive or drives using EBS (Elastic Block

Storage) are used.

• Amazon Machine Image (AMI):

This file contains the initial image for an IP Office virtual machine.

- The name of the file indicates the release of IP Office software.

- The same image is used to create different types of IP Office server. The server type is

selected during initial server configuration.

• Virtual Private Cloud (VPC):

This is the customer's private network within an AWS cloud. It defines the private IP addresses

you can use for the instances launched in the network and provides a range of features for

controlling the traffic between the VPC and the public internet; route tables, internet gateways,

public IP addresses, and so on. This documentation does not cover the configuration of the

customer's VPC.

• Security Group:

A security group controls external internet access to virtual machines. Each security group

consists of a set of rules defining the allowed access based on protocol, port and source

address. You can define multiple security groups and then select which one is used by each

particular virtual machine.

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 57

Comments on this document?

The process of combining the instances to create a new virtual IP Office server is referred to as

'launching an instance'. During that process, the AWS menus request details of the components to

use and the settings to be applied to those components.

• This document outlines the steps required to deploy an IP Office server as a virtual machine.

If deploying multiple virtual machines, follow the order of deployment and configuration in the

Deploying IP Office Server Edition manual.

• In addition to certified IP Office training, the installer and system maintainer must have certified

training on the specific virtual platform type or supported by someone who has the required

certification.

• During deployment, you must ensure that the deployment of each IP Office virtual machine

is completed, including setting the required LAN1 and LAN2 IP addresses, before starting the

deployment of another IP Office virtual machine.

Related links

AWS profiling on page 58

Creating security groups on page 58

Launching a new instance on page 59

Changing the security group on page 61

Changing the machine instance on page 61

AWS profiling

The AWS machine instance https://aws.amazon.com/ec2/instance-types and storage specified

when launching a new instance should match the requirements of the virtual server's intended

role. See Profiling on page 17.

Related links

Amazon deployment on page 57

Creating security groups

Prior to launching any IP Office instances you should create several security groups. A security

group consists of a set of rules for what access is allowed based on a set of selected protocols,

ports and source address settings. When launching a new instance, you can select the security

group that it should use.

• When launching a new instance you should use a highly restricted security group you have

created that allow access from as few hosts and protocols as possible. For example, one that

only allows access from your IP address and using HTTPS access to ports 7070/7071. This

is necessary since the new instance boots with default passwords until initial configuration is

completed.

Amazon deployment

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 58

Comments on this document?

• Once the instance is ignited and initial configuration utility completed, you can then switch

the virtual machine's security group to one you have created for operational systems. For

example, one that allows access from customer addresses using the ports/protocols of the IP

Office services that have been configured on the server. See Changing the security group on

page 61.

Related links

Amazon deployment on page 57

Launching a new instance

About this task

The following is a general example for launching a new virtual instance. The exact process can

vary depending on the customer network requirements.

Procedure

1. Sign in to your AWS account. Click Services and select EC2.

2. From the top-right corner, select the zone appropriate to the customer location.

3. Click Launch Instance and select Community AMIs and enter Avaya as the search

string.

4. Locate the IP Office AMI and click Select.

• The name of the file indicates the release of IP Office software.

• The same image is used to create different types of IP Office server. The server type is

selected during initial server configuration.

5. Select a machine instance that matches the profiling requirements of the virtual machine's

intended role. See

AWS profiling on page 58.

6. Click Next.

a. In Configure Instance Details page, select the customer's VPC and the subnet in

which the virtual machine should operate.

b. To support eth1, under Network interfaces, click Add Device.

• If you use this option, AWS will not automatically assign IP addresses to the ports.

After launching the instance, you must obtain the eth0 interface ID and assign a

Elastic IP public IP address.

7. Click Next.

8. In Add Storage page, set the size of the disk to match the profiling requirements of the

virtual machine's intended role. See AWS profiling on page 58.

• Note: Adjusting the disk size following server ignition is not supported.

• If the server will support Media Manager, you must add an additional separate storage

volume. To add this, click Add New Volume and specify the size required.

Launching a new instance

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 59

Comments on this document?

9. Click Next.

10. In Add Tags page, enter any tags that you want associated with this instance.

• AWS uses tags in other EC2 menus to display, sort and group matching resources.

Each tag consists of name and value pair. For example, you may find it useful to have

tags that indicate the server type, the location it serves and the customer

11. Click Next.

12. In Configure Security Group page, select the system installer's security group you

created. See Creating security groups on page 58.

Important:

• When launching a new instance, you should use a highly restricted security group

that allows access from as few hosts and protocols as possible. For example,

one that allows access from your IP address and using HTTPS access to ports

7070/7071 only. This is necessary since the new instance boots with default

passwords until initial configuration is completed. Following server ignition, you can

assign a different security group that allows the access required for normal

IP Office

operation.

• If you do not select a group, the install process automatically creates a launch

wizard group which allows SSH access on port 22 only.

13. Click Review and Launch. Check that the details shown match the requirements for the

server being created. If so, click Launch.

14. Create a new key pair or choose an existing key pair. This provides a security certificate for

secure SSH access to the virtual machine.

15. If creating a new key pair, click Download Key Pair and ensure that you store the

downloaded PEM certificate file in a safe place.

16. Click Launch Instances.

17. If no problems are reported, scroll down the summary form and click View Instances. The

list of your instances displays the new virtual machine.

• Alternatively, select Services > EC2 and from the navigation tree select Instances >

Instances.

18. The machine starts by performing initial formatting and partitioning of the storage. This

takes approximately 15 minutes to complete.

Next steps

• Proceed with the initial server configuration process. See Initial server configuration on

page 82.

Related links

Amazon deployment on page 57

Amazon deployment

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 60

Comments on this document?

Changing the security group

About this task

You can change the security group assigned to an instance. This allows you to maintain a set of

security groups for different purposes and to flexible switch which security group an instance is

currently using. See Changing the security group on page 61.

Procedure

1. Sign in to your AWS account. Click Services and select EC2.

2. In the navigation tree on the left select Instances > Instances.

3. Select the instance for which you want to change the security group.

4. Click Actions and select Networking > Change Security Groups.

5. Select the security group that you want the virtual machine to use and click Assign

Security Groups.

Related links

Amazon deployment on page 57

Changing the machine instance

About this task

If necessary, you can change the machine instance on which the virtual machine is running.

Important:

This processes requires the server to be stopped and restarted and so ends any calls and

operations currently in progress.

Procedure

1. Sign in to your AWS account. Click Services and select EC2.

2. In the navigation tree on the left select Instances > Instances.

3. Select the instance for which you want to change the machine instance it uses.

4. Click Actions and select Instance State > Stop|. When prompted, select Yes, Stop.

5. Wait until the Instance State has changed to stopped.

6. Click Actions and select Instance Settings > Change Instance Type.

7. Select the type of machine instance required and click Apply.

8. Click Actions and select Instance State > Start. Click Yes, Start.

Related links

Amazon deployment on page 57

Changing the security group

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 61

Comments on this document?

Part 5: Microsoft Azure

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 62

Comments on this document?

Chapter 10: Azure virtual machine

deployment

IP Office server's are supported as virtual machines within Microsoft's Azure environment.

• This document outlines the steps required to deploy an IP Office server as a virtual machine.

If deploying multiple virtual machines, follow the order of deployment and configuration in the

Deploying IP Office Server Edition manual.

• In addition to certified IP Office training, the installer and system maintainer must have certified

training on the specific virtual platform type or supported by someone who has the required

certification.

• During deployment, you must ensure that the deployment of each IP Office virtual machine

is completed, including setting the required LAN1 and LAN2 IP addresses, before starting the

deployment of another IP Office virtual machine.

Related links

Downloading the Software on page 63

Logging in to Azure on page 64

Creating a Resource Group on page 65

Creating a virtual network on page 65

Uploading the VHD file to Azure on page 66

Creating a new Azure virtual machine on page 67

Adding an Additional Disk for Media Manager on page 68

Starting an Azure Virtual Machine on page 69

Creating a copy of an Azure VHD file on page 69

Downloading the Software

About this task

Avaya make a number of different file available for each IP Office release. For a Azure

deployment, select the following files:

• VHD file: (Azure)

The download is a .zip file from which you can extract the .vhd file.

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 63

Comments on this document?

• TTS ISO:

The images used to deploy new virtual machines do not include text-to-speech (TTS)

prompts. To add TTS languages, you need to download and install the additional ISO files for

TTS languages. These are provided as 3

.iso files:

- Note: TTS files from pre-12.1 releases are not compatible with R12.1.

- DVD 1: English, Spanish, French, German, Italian.

- DVD 2: Swedish, Norwegian, Finnish, Dutch, Danish, Portuguese, Greek.

- DVD 3: Chinese, Polish, Russian.

Procedure

1. Browse to http://support.avaya.com and log in.

2. Click Support by Product and select Downloads.

3. In the Enter Product Name box, enter IP Office and select the displayed match.

4. Use the Choose Release drop-down to select the required release.

5. From the listed Downloads, select the version of release required. There are multiple

versions depending on the number of service packs and feature packs available.

6. Click on the required files and follow any further instructions shown by the website and

your browser.

7. Also download and read any documents shown under Related Documents

Next steps

• Create a resource group for the IP Office virtual machines. See Creating a Resource

Group on page 65.

Related links

Azure virtual machine deployment on page 63

Logging in to Azure

About this task

For information on Microsoft Azure, see https://docs.microsoft.com/en-us/azure.

Procedure

1. In your web browser, enter https://portal.azure.com.

2. In the Email, Phone and Skype fields, enter your the registered email.

3. In the Password field, type your password.

4. Click Sign In. The web browser displays the Microsoft Azure portal.

Related links

Azure virtual machine deployment on page 63

Azure virtual machine deployment

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 64

Comments on this document?

Creating a Resource Group

About this task

A resource group is used to group related servers and services. In this case, that can be set of IP

Office virtual servers.

Procedure

1. In the Azure portal, click the icon.

2. Select Resource groups.

3. Click Create.

4. Complete the required details.

5. Click Review + create.

6. Click Create.

Next steps

• Having created a resource group, define the virtual network used by the group. See Creating

a virtual network on page 65.

Related links

Azure virtual machine deployment on page 63

Creating a virtual network

About this task

Once a resource group has been created for the virtual IP Office servers, a virtual network can

also be created.

Before you begin

• Create a resource group for the IP Office virtual machines. See Creating a Resource

Group on page 65.

Procedure

1. In the Azure portal, click the icon.

2. Select Virtual networks.

3. Click Create.

4. In the Basics settings:

a. Select your Subscription and Resource group.

b. Enter a Virtual network name.

c. Select your Region.

Creating a Resource Group

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 65

Comments on this document?

d. Click Next.

5. In the Security settings:

a. Select any additional security services required.

b. Click Next.

6. In the IP addresses settings:

a. Configure your virtual network address space with the IPv4 and IPv6 address subnets

you will need.

b. Click Next.

7. Click Review + create.

8. Click Create.

Next steps

• Upload the IP Office .vhd file. See Uploading the VHD file to Azure on page 66.

Related links

Azure virtual machine deployment on page 63

Uploading the VHD file to Azure

Before you begin

• Define the virtual network for use by servers in the resource group. See Creating a virtual

network on page 65.

Procedure

1. In the Azure portal, click the icon.

2. Select Storage accounts.

3. Select the storage account to which you want to upload the .vhd file.

• If you do not have a storage account, click Create to create one.

• Note that the selected storage location dictate where subsequent image can be created

and deployed.

4. Click Data storage and select Containers.

5. Select the container to which you want to upload the .vhd file.

• If you do not have a storage container, click + Container to create one.

6. Click Upload.

a. Select the .vhd file to upload.

b. Click Advanced.

Azure virtual machine deployment

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 66

Comments on this document?

c. Set the Blob type to Page Blob.

d. Click Upload.

Next steps

• You can use the uploaded file to create virtual machines. See Creating a new Azure virtual

machine on page 67.

Related links

Azure virtual machine deployment on page 63

Creating a new Azure virtual machine

About this task

Follow this procedure to create a new virtual machine from the .vhd file.

Before you begin

• Upload the IP Office .vhd file. See Uploading the VHD file to Azure on page 66.

Procedure

1. In the Azure portal, click the icon.

2. In the search box enter managed disks.

3. Select Managed Disks from the results.

a. Select your Subscription and Resource group.

b. Enter the disk name in Disk name.

c. Select your Region.

d. Set the Source type to Storage blob.

e. Next to Source blob, click Browse.

f. Browse to the uploaded .vhd file. Select the file and click Select.

g. Set the OS type to Linux.

h. Set the Security type to Standard. Do not select Confidential or Trusted launch.

i. Set the VM generation to Generation 2.

j. Click Change size and select the require disk size and type.

k. Click Review + create.

l. Click Create.

4. In the Azure portal, click the icon.

5. Select Home.

Creating a new Azure virtual machine

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 67

Comments on this document?

6. Select Disks:

a. Click on the disk created in the previous steps.

b. Click Create VM.

c. Select the Resource group.

d. Enter a name in Virtual machine name.

e. In the Image text box, browse and select the uploaded iposerver file.

f. Select the required virtual machine size.

g. In the Authentication type, select Password.

h. Verify the network subnets.

i. Click Review + create.

j. Click Create.

Next steps

• If intending to support Media Manager, see Adding an Additional Disk for Media Manager on

page 68.

• Otherwise, start the server. See Starting an Azure Virtual Machine on page 69.

Related links

Azure virtual machine deployment on page 63

Adding an Additional Disk for Media Manager

About this task

To run Media Manager, you must provide the IP Office server running Voicemail Pro with an

additional hard disk. Avaya recommend that you add the additional disk before the IP Office server

initial configuration.

• The minimum supported size is 30 GB. The recommended size is 300 GB or larger.

• Media Manager requires 60 KB per minute for non-authenticated files and 120 KB per minute

for authenticated files.

• Media Manager also reserves 1 GB of space for the call details database and other

operations.

• If you need to add the additional disk after initial configuration, refer to the Administering

Avaya IP Office

™

Platform Media Manager manual for details of initializing the new disk.

Procedure

1. In the Azure portal, click the icon.

2. Select Virtual machines.

Azure virtual machine deployment

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 68

Comments on this document?

3. Select the virtual machine from the list.

4. Select Settings > Disks .

5. Click Create and attach a new disk.

6. Configure the new disk as required and click Apply.

Next steps

• Start the server. See Starting an Azure Virtual Machine on page 69.

Related links

Azure virtual machine deployment on page 63

Starting an Azure Virtual Machine

Procedure

1. In the Azure portal, click Virtual machines.

2. Select the virtual machine(s) to be started.

3. Click Start.

Next steps

• If this is a new server, proceed to initial server configuration. See Initial server

configuration on page 82.

Related links

Azure virtual machine deployment on page 63

Creating a copy of an Azure VHD file

About this task

Microsoft recommend that number of concurrent virtual machines deployed using the any

particular snapshot or .vhd file is limited to 20.

If more than 20 virtual machines are required, an additional disk can be created for the additional

virtual machines.

Procedure

1. In the Azure portal, select All Services.

2. In the All Services search box, enter disks and then select Disks to display the list of

available disks.

3. Select the disk that you would like to use. The page for that disk appears.

Starting an Azure Virtual Machine

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 69

Comments on this document?

4. From the menu at the top, select Create snapshot.

5. Enter a Name for the snapshot.

6. Choose a Resource group for the snapshot. You can use either an existing resource

group or create a new one.

7. For Account type, choose Standard (HDD) or Premium (SSD) storage.

8. When done, select Create to create the snapshot.

9. After the snapshot has been created, select Create a resource in the left menu.

10. In the search box, enter managed disk and select Managed Disks from the list.

11. On the Managed Disks page, select Create.

12. Enter a Name for the disk.

13. Choose a Resource group for the disk. You can use either an existing resource group or

create a new one. This selection will also be used as the resource group where you create

the virtual machines from the disk.

14. For Account type, choose Standard (HDD) or Premium (SSD) storage.

15. In Source type, select Snapshot.

16. In the Source snapshot drop-down, select the snapshot created earlier.

17. Make any other adjustments as needed and then select Create to create the disk.

Related links

Azure virtual machine deployment on page 63

Azure virtual machine deployment

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 70

Comments on this document?

Part 6: KVM on Red Hat Linux

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 71

Comments on this document?

Chapter 11: KVM Virtual machine

deployment on

Red Hat

Enterprise Linux 8.10

This is rough first draft only. Release of R12.1 with IPv6 takes priority. KVM support will be in

a done and tested in an R12.1 service pack.

For IP Office R12.1, Avaya supports the deployment of IP Office virtual machines using KVM on

Red Hat Enterprise Linux 8.10 using the Avaya ASP130 server hardware.

• Whilst you can install and manage virtual machines from the Linux command line, this

document assumes that you will use Web Console wherever possible. The Web Console

allows browser based access to view and manage the Linux server and services, including

virtual machines running on the Linux server.

• For the Red Hat Enterprise Linux documentation, see https://docs.redhat.com/en/

documentation/red_hat_enterprise_linux/8/html/configuring_and_managing_virtualization/index

Related links

Setting-up virtual machine support on Red Hat Enterprise Linux on page 72

Setting-up Web Console on Red Hat Enterprise Linux on page 74

Downloading the Software on page 75

Copying the IP Office KVM file on page 76

Adding a KVM virtual machine on page 76

Adding an Additional Disk for Media Manager on page 77

KVM virtual machine profiling on page 78

Starting the virtual machine on page 80

Setting-up virtual machine support on Red Hat Enterprise

Linux

About this task

The following is a general outline of the steps required to configure virtual machine support on

Red Hat Enterprise Linux 8.10.

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 72

Comments on this document?

Procedure

1. Use either of the following commands to check that the PC hardware supports

virtualization.

• For Intel processors: grep -e 'vmx' /proc/cpuinfo

• For AMD processors: grep -e 'svm' /proc/cpuinfo

The output should show vmx or svm highlighted several times. If there is no response, then

the server CPU does not have virtualization support enabled.

2. Use the following command to check that Linux has the KVM modules available:

lsmod | grep kvm

The server will respond will something like the following:

kvm_intel 348160 0

kvm 970752 1 kvm_intel

irqbypass 16384 1 kvm

3. Use the following commands to install the Linux virtualization modules. If prompted, enter

a. yum module install virt

b. yum install virt-install virt-viewer

4. Use the following commands to start the libvirtd daemon and set it to auto-start. This

service supports and manages virtual machines.

a. systemctl start libvirtd.service

b. systemctl enable libvirtd.service

5. Enter the command systemctl status libvirtd.service and check that the status

shows

active (running). To return to the command line, press Ctrl+C.

6. Enter the command virt-host-validate command and check that the report shows

PASS for each option.

a. Take any actions the report requests. Note that actions such as adding cmdline

arguments, will require you to restart the server for the new setting to take effect.

b. Enter virt-host-validate again.

Next steps

• Add support for Web Console access. See Setting-up Web Console on Red Hat Enterprise

Linux on page 74.

Related links

KVM Virtual machine deployment on Red Hat Enterprise Linux 8.10 on page 72

Setting-up virtual machine support on Red Hat Enterprise Linux

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 73

Comments on this document?

Setting-up Web Console on Red Hat Enterprise Linux

About this task

The following is a general outline of the steps required to configure Web Console on Red Hat

Enterprise Linux 8.10. You can then use the Web Console to manage services running on the

server, including virtual machines.

Before you begin

• You must first configure the server to support virtual machines. See Setting-up virtual

machine support on Red Hat Enterprise Linux on page 72.

Procedure

1. Use the following command to install the Web Console service:

a. yum install cockpit cockpit-machines

b. When prompted, press y.

2. Use the following commands to start the Web Console service and set it to auto-start:

a. systemctl start cockpit.socket

b. systemctl enable cockpit.socket

3. Enter the command systemctl status cockpit.socket and check that the status

shows active (listening). To return to the command line, press Ctrl+C.

4. Use the following commands to add the Web Console service to the host server firewall:

a. firewall-cmd --add-service=cockpit --permanent and wait for the

success response.

b. firewall-cmd --reload and wait for the success response.

5. Check that you can access and use Web Console:

a. From another PC, enter https://<server IP or FQDN>:9090

b. Login to Web Console.

6. Check that the Web Console displays the option Virtual machines.

7. In Web Console, add the network bridge settings for virtual machines:

a. Select Networking.

b. Click Add bridge.

c. Give the bridge a name and select the ethernet ports.

d. Click Add.

Related links

KVM Virtual machine deployment on Red Hat Enterprise Linux 8.10 on page 72

KVM Virtual machine deployment on Red Hat Enterprise Linux 8.10

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 74

Comments on this document?

Downloading the Software

About this task

Avaya makes files available for each IP Office release. For a KVM deployment, download the

following files:

• KVM file: (KVM on Red Hat Linux)

The download is a .zip file from which you can extract the .qcow2 file.

• TTS ISO:

The images used to deploy new virtual machines do not include text-to-speech (TTS)

prompts. To add TTS languages, you need to download and install the additional ISO files for

TTS languages. These are provided as 3

.iso files:

- Note: TTS files from pre-12.1 releases are not compatible with R12.1.

- DVD 1: English, Spanish, French, German, Italian.

- DVD 2: Swedish, Norwegian, Finnish, Dutch, Danish, Portuguese, Greek.

- DVD 3: Chinese, Polish, Russian.

Procedure

1. Browse to http://support.avaya.com and log in.

2. Click Support by Product and select Downloads.

3. In the Enter Product Name box, enter IP Office and select the displayed match.

4. Use the Choose Release drop-down to select the required release.

5. From the listed Downloads, select the version of release required. There are multiple

versions depending on the number of service packs and feature packs available.

6. Click on the required files and follow any further instructions shown by the website and

your browser.

7. Also download and read any documents shown under Related Documents

Next steps

• Extract the .qcow2 file. and upload it to a location on the Red Hat Enterprise Linux server.

For example, upload to the /tmp directory.

Related links

KVM Virtual machine deployment on Red Hat Enterprise Linux 8.10 on page 72

Downloading the Software

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 75

Comments on this document?

Copying the IP Office KVM file

About this task

You will create each virtual machines using a separate .qcow2 file as the virtual machines hard

disk. Therefore, you need to create a separate copy of the IP Office .qcow2 file for each virtual IP

Office server. You then need to load the separate files to the Red Hat Enterprise Linux server.

Before you begin

• Download the IP Office .qcow2 file. See Downloading the Software on page 75.

Procedure

1. Extract the IP Office .qcow2 file from the downloaded .zip file.

2. Make a copy of the file and change its name to clearly identify the files intended usage. For

example,

Customer_A_Primary_IP Office.qcow2.

3. Repeat the step above for any other IP Office virtual machine that you want to create.

4. Using an SSH file transfer tool, transfer the copies of the .qcow2 files to the Red Hat

Enterprise Linux server.

Tip:

• We recommend create a new folder for the .qcow2 files that identifies the role of

the files.

Next steps

• See Adding a KVM virtual machine on page 76.

Related links

KVM Virtual machine deployment on Red Hat Enterprise Linux 8.10 on page 72

Adding a KVM virtual machine

About this task

Use this process to use the .qcow2 file as the hard disk of a new IP Office virtual machine.

Procedure

1. Using a browser, login to Web Console on the host server.

2. Click Virtual machines.

3. Click Import VM.

4. Add a Name for the virtual machine that identifies its role.

5. Set the path to the location of the .qcow2 file that you want used as the virtual machines

hard disk.

KVM Virtual machine deployment on Red Hat Enterprise Linux 8.10

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 76

Comments on this document?

6. Set the Operating system to Rocky Linux 9 (Blue Onyx)

7. Set the Memory to match the amount required by the profile for the virtual machines IP

Office role. See Profiling on page 17.

8. Click Import and edit.

9. Click Firmware. Change the setting to UEFI and click Save.

10. For Autostart, select Run when host boots.

11. In the Networking section, check that the virtual machine is associated with the correct

bridge.

Next steps

• Do not start the virtual machine at this stage:

- If intending to support Media Manager, see Adding an Additional Disk for Media

Manager on page 77.

- Otherwise, perform virtual machine profiling, see KVM virtual machine profiling on

page 78.

Related links

KVM Virtual machine deployment on Red Hat Enterprise Linux 8.10 on page 72

Adding an Additional Disk for Media Manager

About this task

To run Media Manager, you must provide the IP Office server running Voicemail Pro with an

additional hard disk.

Avaya recommend that you add the additional disk before the IP Office server

initial configuration.

• The minimum supported size is 30 GB. The recommended size is 300 GB or larger.

• Media Manager requires 60 KB per minute for non-authenticated files and 120 KB per minute

for authenticated files.

• Media Manager also reserves 1 GB of space for the call details database and other

operations.

• If you need to add the additional disk after initial configuration, refer to the Administering

Avaya IP Office

™

Platform Media Manager manual for details of initializing the new disk.

Procedure

1. Using a browser, login to Web Console on the host server.

2. Click Virtual machines.

3. Click on the name of the virtual machine to display its details.

4. In the Disks section, click Add disk.

a. Select Create new.

Adding an Additional Disk for Media Manager

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 77

Comments on this document?

b. Add a Name that identifies the disks usage.

c. Set the required size of the disk.

d. Click Add.

Related links

KVM Virtual machine deployment on Red Hat Enterprise Linux 8.10 on page 72

KVM virtual machine profiling

After deploying a virtual machine, you must optimize its allocated resources to meet the

requirements of the virtual machine’s role, see

Profiling on page 17. This allows for the best

use of the overall resources provided by the virtual server platform.

Attribute Description

Memory You can set the maximum amount of RAM memory that the virtual machine can use. You can

also set how much of that RAM memory the platform guarantees for the virtual machine.

See Adjusting the virtual machine's RAM memory settings on page 79.

Processors You can configure multiple virtual processor (vCPUs) for a virtual machine. A virtual machine

cannot have more vCPUs than the maximum number of logical CPUs on the host virtual server

platform. The number of logical CPUs is the number of physical processor cores.

See Adjusting the virtual machine's processors on page 79.

After profiling, you can start the virtual machine.

• Profiling Other Virtual Machines:

It is good practice to monitor the resource utilization of all the virtual machines running in their

infrastructure. Profile all virtual machines running on the virtual server platform to fine-tune

the hardware resources allocated and used. This will improve performance by allocating

resources where needed and optimize the use of the virtual infrastructure.

• Multiple IP Office Servers:

If deploying servers with the intention of using resiliency, then the hardware resources and

profiling applied to each server must include allowance for the scenarios where users re-

there is a mix of non-virtualized and virtualized machines, then the assignment of resources

to the virtual machine must match the hardware resources available in the non-virtualized

machine.

Related links

KVM Virtual machine deployment on Red Hat Enterprise Linux 8.10 on page 72

Adjusting the virtual machine's processors on page 79

Adjusting the virtual machine's RAM memory settings on page 79

KVM Virtual machine deployment on Red Hat Enterprise Linux 8.10

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 78

Comments on this document?

Adjusting the virtual machine's processors

About this task

You can configure multiple virtual processor (vCPUs) for a virtual machine. A virtual machine

cannot have more vCPUs than the maximum number of logical CPUs on the host virtual server

platform. The number of logical CPUs is the number of physical processor cores.

Note that the CPU core clock speed affects the range selection. When the CPU is at the low end

toward 2 GHz, use the higher number of CPUs. When the CPU speed is higher, for example 3.6

GHz, use the lower number of CPUs.

The CPU core clock speed multiplied by the number of cores, must meet the aggregate CPU cycle

requirements of the virtual machine. See

Profiling on page 17.

Before you begin

• To do this on an existing virtual machine, you must first power off/stop the virtual machine

before making the adjustment. That will interrupt all services provided by the virtual machine.

Procedure

1. Using a browser, login to Web Console on the host server.

2. Click Virtual machines.

3. Click on the name of the virtual machine to display its details.

4. Click on the edit option next to CPU.

5. Adjust the settings to match the recommended settings for the server role. See Profiling on

page 17.

6. Click Apply.

Next steps

• If doing as part of installing a new virtual machine, continue with any further profiling required.

When completed, start the virtual machine (see

Starting the virtual machine on page 80).

Related links

KVM virtual machine profiling on page 78

Adjusting the virtual machine's RAM memory settings

About this task

You can set the maximum amount of RAM memory that the virtual machine can use. Set these

values to match the virtual server’s profile requirements. See Profiling on page 17.

Before you begin

• To do this on an existing virtual machine, you must first power off/stop the virtual machine

before making the adjustment. That will interrupt all services provided by the virtual machine.

Procedure

1. Using a browser, login to Web Console on the host server.

KVM virtual machine profiling

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 79

Comments on this document?

2. Click Virtual machines.

3. Click on the name of the virtual machine to display its details.

4. Click on the edit option next to Memory.

5. Adjust the settings to match the recommended settings for the server role. See Profiling on

page 17.

6. Click Save.

Next steps

• If doing as part of installing a new virtual machine, continue with any further profiling required.

When completed, start the virtual machine (see Starting the virtual machine on page 80).

Related links

KVM virtual machine profiling on page 78

Starting the virtual machine

About this task

Having installed and profiled the new virtual machine, you can start it. This will boot it from the

virtual hard disk (the

.qcow2 file) after which you can start the initial IP Office server configuration.

Procedure

1. Using a browser, login to Web Console on the host server.

2. Click Virtual machines.

3. Click on the name of the virtual machine to display its details.

4. Click on Run.

5. Watch the Console and wait for it to display IP Office Server Edition login menu.

Next steps

• Start the initial server configuration process. See Initial server configuration on page 82.

Related links

KVM Virtual machine deployment on Red Hat Enterprise Linux 8.10 on page 72

KVM Virtual machine deployment on Red Hat Enterprise Linux 8.10

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 80

Comments on this document?

Part 7: Server Configuration

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 81

Comments on this document?

Chapter 12: Initial server configuration

Once a new virtual machine has been started, it requires initial configuration to set the servers’

role and complete other key configuration settings. Once these have been complete, it should be

possible to license, configure and manage the virtual machine in the same way as a normal physical

IP Office server.

Related links

Connecting to the uninitialized virtual machine on page 82

Setting the virtual machine's IP address on page 83

Performing server ignition on page 84

Adding a certificate to the browser on page 89

IP Office initial configuration on page 91

Configuring the server applications on page 92

Disabling a network port on page 92

Connecting to the uninitialized virtual machine

About this task

Using a browser, use the process below to login and proceed to Performing Server Ignition. See

Performing server ignition on page 84.

Procedure

1. From a client PC, start the browser and enter https:// followed by the IP address of the

server and

:7071. For example https://192.168.42.1:7071

• The virtual machines eth0 IP address is shown in the console window. By default

the IP address for initial configuration is 192.168.42.1/255.255.255.0. If you

cannot connect to the virtual machine using the default IP address, you need to assign

the virtual machine a valid browseable address. See Setting the virtual machine's IP

address on page 83.

2. The login page is displayed. Enter the user name as root and the password

Administrator.

3. Click Login.

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 82

Comments on this document?

Next steps

• Once connected, the server ignition menus are displayed. See Performing server ignition on

page 84.

Related links

Initial server configuration on page 82

Setting the virtual machine's IP address

A newly deployed IP Office virtual machine uses the following default IP settings:

• LAN1 (eth0): 192.168.42.1/24

• LAN2 (eth1): 192.168.43.1/24

If the default IP settings are incompatible with the network on which you are deploying the virtual

machine, you can use the steps described to change them. When the settings are correct and you

can access the virtual machine from the network using a browser, you can proceed to performing

the server ignition.

• Avaya does not support setting IPv6 addresses before IP Office server ignition. For IP Office

administration, you must set and use an IPv4 address. If you require an IPv6 address for the

IP Office, you can set the address during or after IP Office server ignition.

Before you begin

Warning:

• If using local nodal licensing, the virtual machine uses its IP address as part of the

unique PLDS Host ID used for licensing. Changing the IP address can change the host

ID, invalidating any existing licenses. See

Virtual server licensing on page 12. Therefore,

you must ensure that you have confirmed the final IP address settings before setting

these values.

Procedure

1. Within the virtualized platform you are using to host the virtual machine, open a console

window.

2. Log in as the root user:

a. In the console, enter login.

b. Enter username root and password Administrator.

3. Use the Network Manager Tool to view and edit the address settings:

a. Enter nmtui.

b. Select Edit a connection.

c. Select eth0 or eth1.

Setting the virtual machine's IP address

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 83

Comments on this document?

d. Edit the settings to match the customer network requirements.

• Avaya does not support setting IPv6 addresses before IP Office server ignition. For

IP Office administration, you must set and use an IPv4 address. If you require an

IPv6 address for the IP Office, you can set the address during or after IP Office

server ignition.

e. Select OK.

f. Select Back and then select OK again.

4. Restart the ports network connections and check the port status. In this example, port

eth0:

a. Enter nmcli con down eth0 && nmcli con up eth0.

b. Enter nmcli. Check that the address details shown for the port are correct.

5. Restart the virtual machine and check that the network address changes have persisted.

Next steps

• Using a browser, connect to the server using the new address. See Connecting to the

uninitialized virtual machine on page 82.

Related links

Initial server configuration on page 82

Performing server ignition

About this task

Server ignition is used to set the server's role and other key settings.

Procedure

1. Using a browser, connect to the virtual machine. See Connecting to the uninitialized virtual

machine on page 82.

2. If you accept the license, select I Agree and click Next.

Initial server configuration

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 84

Comments on this document?

3. Select the role that the server should perform and click Next. The subsequent menus vary

depending on the chosen server type.

4. If an additional hard disk was added during the virtual server deployment, details of

the additional hardware appear. Otherwise the menu displays No new hardware

available.

For Media Manager support, it is recommended to accept the defaults. These are:

a. Leave Format Hard Drive checked.

b. Create a single partition for the whole disk. You can create up to 3 logical partitions on

the physical disk.

c. Leave the Mount Point name as /additional-hdd#1. The full mount path name

for each partition is automatically configured by the system adding /partition1, /

partition2 and so on, as a suffix.

For example /additional-hdd#1/partition1. Note that it is this partition name,

including /partition1, that should be used for Media Manager settings.

Performing server ignition

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 85

Comments on this document?

d. Select Mount Hardware to have the additional disk automatically mounted.

5. Click Next. Enter the server's network settings.

• Remember that the LAN1 and LAN2 IP addresses and DHCP mode selections affect the

virtual machine's PLDS Host ID used for licensing . Therefore, if using or planing to use

local nodal licensing, we strongly recommended that before obtaining any licenses, you

ensure that these are set to their final values.

• The ignition process allows you to set the IP address for the LAN1 port only. The LAN2

port initially uses the default address 192.168.43.1. To avoid the duplicate IP address

issue you should set the LAN2 address after ignition. This can be done using

IP Office

Manager or IP Office Web Manager.

• For AWS virtual machine these settings affect the private IP address settings of the

instance. They do not alter the public IP address values assigned by AWS.

• Hostname is used as the DNS host name of the server.

- For internal applications, this value must be reachable by DNS within the customer

network. If the server is also supporting external applications, the host name also

needs to be reachable by external DNS. Consult with the customers IT support to

Initial server configuration

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 86

Comments on this document?

ensure that the host name is acceptable and that routing to the host name has been

configured correctly.

6. Click Next.

7. Set the time source for the server.

• Remember that the virtual machine uses the Timezone for licensing. Therefore, we

strongly recommended that this is set to its final value before obtaining any licenses.

• Select to use the time provided by an NTP server.

• For a virtual server, if not using NTP, the server takes its time from the virtual server's

host platform rather than allow manual configuration through the server menus.

• By default, Secondary Server and Expansion System (L) servers automatically get their

time from the Primary Server and you can only change the Timezone.

• Select the companding setting to use. For telephone systems in North American

locations and Japan, select μ-Law (also referred to as U-Law or Mu-Law). For most

other locations, select A-Law.

8. Click Next.

Performing server ignition

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 87

Comments on this document?

9. Enter and confirm a new password.

These are the passwords for various IP Office service accounts and also for the Linux

accounts created on the server. Ensure that you note the passwords set.

10. Click Next.

11. If the selected Server Type was Application Server, select the services provided by the

server.

Unselected services remain installed but not running unless manually started.

12. Click Next.

The menu prompts which security certificate the server should use. This option is not used

for Secondary Server and Expansion System (L) servers.

• If you select Generate CA automatically, you must download the certificate from the

next screen.

• If you select Import CA, click Browse and locate the security certificate file that the

server should use and click Upload.

Initial server configuration

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 88

Comments on this document?

13. Select whether you want the server to be supported by Avaya through their EASG service

and click Next.

14. Check the displayed summary. Use the Previous and Next options to readjust settings if

necessary.

15. Click Apply.

16. The browser menu will attempt to redirect you to the server IP address you configured

during ignition. Click

OK when displayed to access the server's IP Office Web Manager

menus.

AWS: For an AWS virtual machine the browser is redirected to the private IP address of

the server. You need to manually change the browser address back to the instance's public

IP address.

Next steps

• Add the downloaded certificate to our browser, see Adding a certificate to the browser on

page 89. Then proceed to initial configuration, see IP Office initial configuration on

page 91.

Related links

Initial server configuration on page 82

Adding a certificate to the browser

Browser access to the server uses secure access. The browser used therefore needs to have a

copy of the same CA certificate as used to sign the virtualized server's own identity certificate.

• If the server is using its own auto-generated certificate, you can downloaded the certificate

from the Certificates section of the Settings > General menu. Download the DER-encoded

certificate (a CRT file).

• If the server is using an identity certificate generated elsewhere and then uploaded to the

server, obtain a copy of the CA certificate from the same source.

Related links

Initial server configuration on page 82

Adding a certificate to Firefox on page 89

Adding a certificate to Google Chrome on page 90

Adding a certificate to Windows Edge on page 91

Adding a certificate to Mac Safari on page 91

Adding a certificate to Firefox

Procedure

1. Click the icon and select . Alternatively, click on the icon if shown on the browser

home page.

Adding a certificate to the browser

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 89

Comments on this document?

2. Click Advanced and select Certificates.

3. Click View Certificates.

4. Click Authorities.

5. Click Import. Browse to the location of the CRT or PEM file downloaded from the server.

Select the file and click Open.

6. Select all the check boxes to trust the certificate.

7. Click OK twice.

Next steps

• If adding the certificate from a newly initialized server, proceed to initial configuration. See IP

Office initial configuration on page 91.

Related links

Adding a certificate to the browser on page 89

Adding a certificate to Google Chrome

Procedure

1. Click the icon and select Settings.

2. Click Show advanced settings. Scroll to HTTP/SSL and click Manage certificates.

3. Click Import.

4. Click Next and browse to the location of the downloaded certificate. Select it and click

Open.

5. Click Next.

6. Click Place all certificates in the following store.

• If using the server's own generated certificate, select the Trusted Root Certification

Authorities.

• If using a certificate from another source, select Intermediate Certification

Authorities.

7. Click Next and then Finish.

8. Click OK, Close.

Next steps

• If adding the certificate from a newly initialized server, proceed to initial configuration. See IP

Office initial configuration on page 91.

Related links

Adding a certificate to the browser on page 89

Initial server configuration

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 90

Comments on this document?

Adding a certificate to Windows Edge

Procedure

1. From the file browser, open the directory containing the certificate file.

2. Right-click the file and select Install Certificate. You may be prompted for admin

credentials and/or a confirmation prompt.

3. On the first wizard screen, click Next.

4. On the Certificate Store screen select Place all certificates in the following store.

• If using the server's own generated certificate, select the Trusted Root Certification

Authorities.

• If using a certificate from another source, select Intermediate Certification

Authorities.

5. Click OK.

Next steps

• If adding the certificate from a newly initialized server, proceed to initial configuration. See IP

Office initial configuration on page 91.

Related links

Adding a certificate to the browser on page 89

Adding a certificate to Mac Safari

Procedure

1. From the browser, open the directory containing the certificate file.

2. Double-click the certificate.

3. You are prompted to store the certificate in the login keychain or the system keychain.

To make the certificate available to all users of this system, select system keychain.

Next steps

• If adding the certificate from a newly initialized server, proceed to initial configuration. See IP

Office initial configuration on page 91.

Related links

Adding a certificate to the browser on page 89

IP Office initial configuration

About this task

The IP Office service running on the server requires some initial configuration. This is done using

the initial configuration utility (ICU) menu. This menu is automatically shown the first time you login

using either

IP Office Web Manager or IP Office Manager.

IP Office initial configuration

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 91

Comments on this document?

Procedure

1. Log in to IP Office Web Manager.

a. Enter https:// followed by the server address. Click on the IP Office Web Manager

Web Manager link.

b. Enter the user name Administrator and the password that was created for that

user during ignition.

2. Web manager displays the initial configuration menu for the IP Office service. If this does

not appear, click Solution. Most of the settings are automatically completed using the

values you entered during module ignition.

3. Check the values are as expected. If the module is under centralized management from

Avaya System Manager, select the Centralized Management checkbox. Enter the details

required for Avaya System Manager.

4. Click Apply.

The service is restarted using the values set in the menu. After the restart the browser is

redirected to the normal web management menus.

Related links

Initial server configuration on page 82

Configuring the server applications

The services provided by the virtual machine can now be configured in the same way as for

non-virtual installations. Refer to the appropriate documentation for Voicemail Pro, one-X Portal

and Media Manager. See Related Documentation on page 10.

Related links

Initial server configuration on page 82

Disabling a network port

The IP Office virtual machine deploys with two network interfaces. By default these configure

as eth0 (192.168.42.1/255.255.255.0) and eth1 (192.168.43.1/255.255.255.0) when the virtual

machine starts. The

IP Office uses these as LAN1 and LAN2 respectively.

If eth1 (LAN2) is not required, you can disable the port. Doing that reduces the chances of IP

address duplication, which causes the IP Office application to not start. See Duplicate IP address

issue on page 10.

Related links

Initial server configuration on page 82

Initial server configuration

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 92

Comments on this document?

Disabling a network port on page 93

Enabling a network port on page 93

Disabling a network port

About this task

You can use this process to disable a network port.

Procedure

1. Login to the server as root.

2. Enter nmcli to see details of the active ports.

3. Enter nmtui.

4. Select Activate a connection.

5. Highlight the connection you want to disable and select Deactivate.

6. Select Back.

7. Select OK.

8. Enter nmcli to see details of the active ports.

Related links

Disabling a network port on page 92

Enabling a network port

About this task

You can use this process to enable a network port.

Procedure

1. Login to the server as root.

2. Enter nmcli to see details of the active ports.

3. Enter nmtui.

4. Select Activate a connection.

5. Highlight the connection you want to disable and select Activate.

6. Select Back.

7. Select OK.

8. Enter nmcli to see details of the active ports.

Next steps

• If doing as part of installing a new virtual machine, continue with any further profiling required.

When completed, start the virtual machine (see

Powering On a VMware virtual machine on

page 45).

Disabling a network port

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 93

Comments on this document?

Related links

Disabling a network port on page 92

Initial server configuration

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 94

Comments on this document?

Chapter 13: Adding TTS languages

The Voicemail Pro application can use Text-to-speech (TTS). However, the IP Office image file

used to create virtual machines does not include the TTS languages. The TTS languages are

downloadable as three separate DVD's. See Downloading software for VMware on page 29.

To use TTS languages, you need to upload and install the additional languages on the virtual

machines running the Voicemail Pro application. In a Server Edition network, that applies to the

Primary Server and Secondary Server servers.

Warning:

• TTS files from pre-12.1 releases are not compatible with R12.1.

• During this process, the server needs to restart the voicemail service each time it installs a

new TTS language.

Related links

Checking the TTS languages installed on page 95

Downloading the TTS languages on page 96

Adding a new language on page 96

Checking the TTS languages installed

Procedure

1. Access the server's web control/platform view menus.

2. Select Updates.

3. In the list of Services, each TTS language is shown with the prefix TTS.

Related links

Adding TTS languages on page 95

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 95

Comments on this document?

Downloading the TTS languages

About this task

Avaya make a number of different file available for each IP Office release. For TTS, select the

following files:

• TTS ISO:

The images used to deploy new virtual machines do not include text-to-speech (TTS)

prompts. To add TTS languages, you need to download and install the additional ISO files for

TTS languages. These are provided as 3

.iso files:

- Note: TTS files from pre-12.1 releases are not compatible with R12.1.

- DVD 1: English, Spanish, French, German, Italian.

- DVD 2: Swedish, Norwegian, Finnish, Dutch, Danish, Portuguese, Greek.

- DVD 3: Chinese, Polish, Russian.

Procedure

1. Browse to http://support.avaya.com and log in.

2. Click Support by Product and select Downloads.

3. In the Enter Product Name box, enter IP Office and select the displayed match.

4. Use the Choose Release drop-down to select the required release.

5. From the listed Downloads, select the version of release required. There are multiple

versions depending on the number of service packs and feature packs available.

6. Click on the required files and follow any further instructions shown by the website and

your browser.

7. Also download and read any documents shown under Related Documents

Related links

Adding TTS languages on page 95

Adding a new language

About this task

Note that this process causes the voicemail service to restart, ending all calls currently being

handled by the voicemail service.

Procedure

1. Access the server's web control/platform view menus.

2. Select Settings > General.

Adding TTS languages

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 96

Comments on this document?

3. In the Software Repositories section, click on the Browse button for Application.

Browse to and select the RPM file for the required language and click OK.

4. Click Add.

5. Select Updates.

6. In the Services section, locate the newly added TTS language and click Install.

Related links

Adding TTS languages on page 95

Adding a new language

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 97

Comments on this document?

Part 8: Upgrading

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 98

Comments on this document?

Chapter 14: Upgrading a virtual machine

Server Edition software supports several methods for upgrading. For virtual machines, the

supported method is to upload the new ISO file to the virtual server, using one of the methods

below, and then select upgrade within the IP Office Web Manager menus.

Method Summary

Transfer from a virtual DVD Upload the ISO file from a virtual DVD drive. You can connect an ISO

file to the virtual machine's DVD drive in several ways.

Transfer from a remote file server Upload the ISO file to the server from a file server (http, https, ftp, sftp

or scp).

Transfer via SSH/SFTP to the virtual

machine

Upload the ISO file directly to a folder on the server using SFTP.

Direct transfer Upload the ISO file to the server using the IP Office Web Manager

browser session.

Warning:

• Not Supported for Upgrades from Pre-R12.0:

This method of upgrading is not supported for upgrading from pre-R12.0 releases. For

example, from R11.1 to R12.0.You must upgrade the server using the processes in the

Upgrading Linux-based IP Office Systems to R12.0 manual.

• WARNING: Boot from DVD Upgrades:

For non-virtual IP Office servers, the server can boot from a DVD copy of the ISO. The

menu presented includes an option to upgrade. However, for virtual machines this method

of upgrading is not supported.

In a Server Edition network consisting of several servers, you can use IP Office Web Manager to

first upgrade the primary server. The files on the primary are then used to upgrade its associated

secondary, expansion and application servers. Note that this is not possible from a newly installed

virtual primary server.

The VMware Snapshot feature can be used to provide a more robust upgrade process by providing

a fall back point to the previous instance of the virtual machine. See VMware Features on page 23.

Related links

Downloading the software on page 100

Backing up applications on page 100

Transferring the ISO File on page 101

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 99

Comments on this document?

Downloading the software

About this task

Virtual server upgrades use the same ISO file as used for non-virtual servers.

• ISO file:

You can use this type of file to upgrade an existing virtual machine, see Upgrading a virtual

machine on page 99. Before using an.iso file, you must backup all applications data and

check that you have understood any additional requirements mentioned in the IP Office

Technical Bulletin for the IP Office release. IP Office Technical Bulletins are downloadable

from the same website as the software.

Procedure

1. Browse to http://support.avaya.com and log in.

2. Click Support by Product and select Downloads.

3. In the Enter Product Name box, enter IP Office and select the displayed match.

4. Use the Choose Release drop-down to select the required release.

5. From the listed Downloads, select the version of release required. There are multiple

versions depending on the number of service packs and feature packs available.

6. Click on the required files and follow any further instructions shown by the website and

your browser.

7. Also download and read any documents shown under Related Documents

Next steps

• Backup the existing servers. See Backing up applications on page 100.

Related links

Upgrading a virtual machine on page 99

Backing up applications

You can configure IP Office Web Manager to backup the servers in a Server Edition network to a

another servers. Refer to the Deploying Avaya IP Office Server Edition Manual manual.

Next steps

• Once you have backed up the servers, proceed with transferring the new ISO file to the

server. See

Transferring the ISO File on page 101.

Related links

Upgrading a virtual machine on page 99

Upgrading a virtual machine

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 100

Comments on this document?

Transferring the ISO File

Having backed up the applications, the next stage is to transfer the ISO file to the Primary Server.

As previously stated, there are number of different methods supported for a virtual machine.

• Transfer from the virtual machine DVD:

- For a physical server, this method uses an ISO file burnt to DVD and placed in the server's

DVD drive. For a virtual machine, there are several methods to connect an ISO file to the

virtual machine's DVD drive. See

Transfer from a virtual machine DVD on page 110.

• Transfer from a remote file server:

- Thorough the IP Office Web Manager menus, you can configure the server with the details

of remote file servers from which it can upload an ISO file. See Transfer from a Remote

File Server on page 102.

• Transfer from a primary server path:

- Using SFTP, you can upload the ISO file directly to the server. Within IP Office Web

Manager, you can then use the server file path to download the file. See Transfer from a

primary server path on page 105.

• Transfer from the Web Manage client PC:

- You can transfer an ISO file during a connected IP Office Web Manager session. See

Transfer the ISO from the IP Office Web Manager client PC on page 108.

Related links

Upgrading a virtual machine on page 99

Transferring the ISO File

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 101

Comments on this document?

Chapter 15: Transfer from a Remote File

Server

You can upload an ISO file to the virtual server from a previously configured file server. The process

for this is the same for virtual and non-virtual machines. See

Server Edition documentation for full

details.

Related links

Configuring a remote file server source on page 102

Transferring the ISO from a remote server path on page 102

Upgrading using the Transferred ISO file on page 103

Configuring a remote file server source

Procedure

1. Login to IP Office Web Manager.

2. Click on the Solution Settings drop-down and select Remote Server Options.

3. IP Office Web Manager lists the currently configured remote servers.

4. Click Add Remote Server.

5. Enter details for the remote file server hosting the ISO file. The details required vary

depending on the protocol used by the server.

6. Click OK. The new remote server is now included in the list of remote servers.

7. Click Close.

Related links

Transfer from a Remote File Server on page 102

Transferring the ISO from a remote server path

Procedure

1. Login to IP Office Web Manager.

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 102

Comments on this document?

2. Click Solution.

3. Click on the Actions drop-down and select Transfer ISO.

4. Click Transfer from and select Remote Location.

5. Click Select Remote Server and select the previously configured remote file server from

the list.

6. In the File Path field, enter the path to the ISO file on that server.

7. Click OK. The menu shows the progress of the download.

8. The servers listed in the Solution overview show an icon and Upgrade Available.

Next steps

• Proceed with upgrading from the uploaded file. See Upgrading using the Transferred ISO

file on page 103.

Related links

Transfer from a Remote File Server on page 102

Upgrading using the Transferred ISO file

About this task

Having downloaded an ISO file to the server , IP Office Web Manager indicates those servers

it can upgrade. It does this by showing an

icon and Upgrade Available next to the server's

details on the Solution menu.

Warning:

• Not Supported for Upgrades from Pre-R12.0:

This method of upgrading is not supported for upgrading from pre-R12.0 releases. For

example, from R11.1 to R12.0.You must upgrade the server using the processes in the

Upgrading Linux-based IP Office Systems to R12.0 manual.

Procedure

1. Login to IP Office Web Manager.

2. Select Solution.

3. Select the checkbox next to each server to upgrade. Upgrades require the primary server

upgraded before any other servers.

4. Click on the Actions drop down and select Upgrade.

5. The upgrade process typically requires the IP Office server to restart, ending the current

web browser connection. If this occurs, login to IP Office Web Manager again to check on

the status of the upgrade.

Upgrading using the Transferred ISO file

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 103

Comments on this document?

Next steps

If necessary, repeat the process to upgrade all the servers.

Related links

Transfer from a Remote File Server on page 102

Transfer from a Remote File Server

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 104

Comments on this document?

Chapter 16: Transfer from a primary server

path

SFTP/SSH can be used to upload an ISO file directly to a folder on the virtual machine. The upload

process is typically slow, several hours, but reliable.

Related links

Uploading an ISO file using SSH/SFTP on page 105

Transferring the ISO from a primary server path on page 106

Upgrading using the Transferred ISO file on page 106

Uploading an ISO file using SSH/SFTP

Procedure

1. Start your SFTP or SSH file application and connect to the IP Office Application Server PC.

The exact method depends on the application you are using.

a. Enter the details for the IP Office Application Server:

• The Host Name is the IP address of the IP Office Application Server.

• The User Name is Administrator.

• The Protocol is SFTP/SSH.

• The Port is 22. If this is the first time the application has connected to the server,

accept the trusted key.

b. If this is the first time the application has connected to the IP Office Application Server,

accept the trusted key.

c. When prompted, enter the user password.

2. The default folder displayed after logging in is /home/Administrator.

3. Upload the ISO file to the server.

Related links

Transfer from a primary server path on page 105

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 105

Comments on this document?

Transferring the ISO from a primary server path

Procedure

1. Login to IP Office Web Manager.

2. Click Solution.

3. Click on the Actions drop-down and select Transfer ISO.

4. Click Transfer from and select Primary Server Path.

5. In the File Path field, enter the path to the previously uploaded ISO file. For example, /

home/Administrator/Downloads/abe-11.1.1-209_el6.iso.

6. Click OK. The menu shows the progress of the download.

7. The servers listed in the Solution overview show an icon and Upgrade Available.

Next steps

• Proceed with upgrading from the uploaded file. See Upgrading using the Transferred ISO

file on page 106.

Related links

Transfer from a primary server path on page 105

Upgrading using the Transferred ISO file

About this task

Having downloaded an ISO file to the server , IP Office Web Manager indicates those servers

it can upgrade. It does this by showing an

icon and Upgrade Available next to the server's

details on the Solution menu.

Warning:

• Not Supported for Upgrades from Pre-R12.0:

This method of upgrading is not supported for upgrading from pre-R12.0 releases. For

example, from R11.1 to R12.0.You must upgrade the server using the processes in the

Upgrading Linux-based IP Office Systems to R12.0 manual.

Procedure

1. Login to IP Office Web Manager.

2. Select Solution.

3. Select the checkbox next to each server to upgrade. Upgrades require the primary server

upgraded before any other servers.

4. Click on the Actions drop down and select Upgrade.

Transfer from a primary server path

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 106

Comments on this document?

5. The upgrade process typically requires the IP Office server to restart, ending the current

web browser connection. If this occurs, login to IP Office Web Manager again to check on

the status of the upgrade.

Next steps

If necessary, repeat the process to upgrade all the servers.

Related links

Transfer from a primary server path on page 105

Upgrading using the Transferred ISO file

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 107

Comments on this document?

Chapter 17: Upgrade by Transfer from Your

Client PC

This method of upgrade uses an .iso file transferred directly from your PC through the browser.

Related links

Transfer the ISO from the IP Office Web Manager client PC on page 108

Upgrading using the Transferred ISO file on page 109

Transfer the ISO from the IP Office Web Manager client PC

We do not recommend this method of uploading an ISO file to the server for remote maintenance

of servers not located on the same local network as the PC. The file transfer is slow and does

not continue or automatically resume if the IP Office Web Manager session disconnects during the

transfer.

Procedure

1. Login to IP Office Web Manager.

2. Click Solution.

3. Click on the Actions drop-down and select Transfer ISO.

4. Click Transfer from and select Client Machine.

5. For the Select ISO field, click Browse. Locate and select the ISO file and click Open.

6. Click OK. The menu shows the progress of the download.

7. The servers listed in the Solution overview show an icon and Upgrade Available.

Next steps

• Proceed to upgrading from a downloaded ISO. See Upgrading using the Transferred ISO

file on page 109.

Related links

Upgrade by Transfer from Your Client PC on page 108

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 108

Comments on this document?

Upgrading using the Transferred ISO file

About this task

Having downloaded an ISO file to the server , IP Office Web Manager indicates those servers

it can upgrade. It does this by showing an icon and Upgrade Available next to the server's

details on the Solution menu.

Warning:

• Not Supported for Upgrades from Pre-R12.0:

This method of upgrading is not supported for upgrading from pre-R12.0 releases. For

example, from R11.1 to R12.0.You must upgrade the server using the processes in the

Upgrading Linux-based IP Office Systems to R12.0 manual.

Procedure

1. Login to IP Office Web Manager.

2. Select Solution.

3. Select the checkbox next to each server to upgrade. Upgrades require the primary server

upgraded before any other servers.

4. Click on the Actions drop down and select Upgrade.

5. The upgrade process typically requires the IP Office server to restart, ending the current

web browser connection. If this occurs, login to IP Office Web Manager again to check on

the status of the upgrade.

Next steps

If necessary, repeat the process to upgrade all the servers.

Related links

Upgrade by Transfer from Your Client PC on page 108

Upgrading using the Transferred ISO file

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 109

Comments on this document?

Chapter 18: Transfer from a virtual machine

DVD

One of the options for downloading an ISO image used by IP Office Web Manager is to download

the ISO file from the primary server's DVD drive. To use this option for a virtual machine, you must

first connect the virtual machine's DVD drive to the ISO file.

The VMware client supports the following options for connecting the virtual machine's DVD drive

to a source. This section lists the different methods in order of preference based on speed and

reliability:

• Connect to an ISO file on the client PCs hard disk – This method connects the virtual

machine's DVD drive to an ISO file on the hard disk of the VMware client PC. The time to

complete the upgrade depends on the speed between the vSphere host and the client PC. See

Connect to an ISO File on the client PCs hard disk on page 111.

• Connect to the client PC DVD drive – This method connects the virtual machine's DVD drive

to the DVD drive of the PC running the VMware client PC. The time to complete the upgrade

depends on the speed between the vSphere host and the client PC. See

Connect to the client

PCs DVD drive on page 112.

• Connect to an ISO file in the virtual server datastore – This method connects the virtual

machine's DVD drive to an

ISO file previously uploaded to the virtual server datastore. For

remote upgrades, this method is the most reliable. In addition, if multiple virtual machines use

the same datastore, they can access the same ISO file. See Connect to an ISO File in the

virtual server datastore on page 113.

• Connect to the VMware server's DVD drive – This method connects the virtual machine's

DVD drive to a DVD drive on the VMware server PC. This method requires physical access to

a DVD drive on the VMware server. See

Connect to the host server's DVD drive on page 116.

Related links

Connect to an ISO File on the client PCs hard disk on page 111

Connect to the client PCs DVD drive on page 112

Connect to an ISO File in the virtual server datastore on page 113

Connect to the host server's DVD drive on page 116

Downloading the ISO from the primary DVD on page 118

Upgrading using the Transferred ISO file on page 118

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 110

Comments on this document?

Connect to an ISO File on the client PCs hard disk

This method maps the DVD drive of the virtual machine to an ISO file on the PC running the

VMware client.

Related links

Transfer from a virtual machine DVD on page 110

Mapping the virtual machine's DVD to a local PC ISO file (vSphere desktop client) on page 111

Mapping the virtual machine's DVD to a local PC ISO file (vSphere web client) on page 111

Mapping the virtual machine's DVD to a local PC ISO file (vSphere

desktop client)

Procedure

1. Place the ISO file in a folder on your client PC.

2. Using the vSphere client, select the Inventory view.

3. Locate the required virtual machine in the inventory navigation tree on the left. If not

shown, select View > Show VMs in Inventory

4. Click on the virtual machine.

5. Click on the Connect/disconnect the CD/DVD device of the virtual machine icon in

the toolbar.

• If already connected to a source, the details are shown and the option to disconnect.

Select disconnect and then click the icon again.

6. From the drop-down, select CD/DVD drive 1 and then select Connect to ISO image on

local disk.

7. Select the ISO file and click Open.

Next steps

• You can now download the ISO to the virtual server using the DVD Primary Server option

in the IP Office Web Manager menus. See Downloading the ISO from the primary DVD on

page 118.

Related links

Connect to an ISO File on the client PCs hard disk on page 111

Mapping the virtual machine's DVD to a local PC ISO file (vSphere

web client)

Procedure

1. Place the ISO file in a folder on your client PC.

2. Using the vSphere web client, select the virtual machine. For example, select vCenter

Management and in the navigation tree on the left select the virtual machine.

Connect to an ISO File on the client PCs hard disk

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 111

Comments on this document?

3. Click on the icon in the toolbar.

4. From the CD/DVD drive drop-down, select CD/DVD drive 1 and then select Connect to

ISO image on local disk.

5. Select the ISO file and click Open.

6. You can now download the ISO to the virtual server using the DVD Primary Server option

in the IP Office Web Manager menus.

Next steps

• You can now download the ISO to the virtual server using the DVD Primary Server option

in the IP Office Web Manager menus. See Downloading the ISO from the primary DVD on

page 118.

Related links

Connect to an ISO File on the client PCs hard disk on page 111

Connect to the client PCs DVD drive

This method maps the DVD drive of the virtual machine to the DVD drive of the PC running the

VMware client.

On some Windows operating systems, access to the client PC DVD drive requires vSphere to run

with local administrator rights. For details refer to the VMware Knowledge Base.

Related links

Transfer from a virtual machine DVD on page 110

Mapping the virtual machine’s DVD to the local PC drive (vSphere desktop client) on page 112

Mapping the virtual machine's DVD to local PC drive (vSphere web client) on page 113

Mapping the virtual machine’s DVD to the local PC drive (vSphere

desktop client)

Procedure

1. Insert the DVD into the PC's DVD drive.

2. Using the vSphere client, select the Inventory view.

3. Locate the required virtual machine in the inventory navigation tree on the left. If not

shown, select View > Show VMs in Inventory

4. Click on the virtual machine.

5. Click on the Connect/disconnect the CD/DVD device of the virtual machine icon in

the toolbar.

• If already connected to a source, the details are shown and the option to disconnect.

Select disconnect and then click the icon again.

Transfer from a virtual machine DVD

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 112

Comments on this document?

6. From the drop-down, select CD/DVD and then select the appropriate drive letter for the PC

drive containing the DVD.

Next steps

• You can now download the ISO to the virtual server using the DVD Primary Server option

in the

IP Office Web Manager menus. See Downloading the ISO from the primary DVD on

page 118.

Related links

Connect to the client PCs DVD drive on page 112

Mapping the virtual machine's DVD to local PC drive (vSphere

web client)

Procedure

1. Insert the DVD into the PC's DVD drive.

2. Click Virtual Machines and select a virtual machine from the list and click it.

3. Click the Manage tab, and click the CD/DVD connection icon.

4. Select an available drive to connect to, and browse for the CD/DVD media.

5. An Access Control dialog box opens. Click Allow to proceed. To change your selection,

click the connection icon, select Disconnect, and select a different option.

6. Click OK.

Next steps

• You can now download the ISO to the virtual server using the DVD Primary Server option

in the

IP Office Web Manager menus. See Downloading the ISO from the primary DVD on

page 118.

Related links

Connect to the client PCs DVD drive on page 112

Connect to an ISO File in the virtual server datastore

This method uses an ISO file uploaded to the file datastore used by the virtual machine.

Related links

Transfer from a virtual machine DVD on page 110

Uploading an ISO file to the datastore (vSphere desktop client) on page 114

Uploading an ISO file to the datastore (vSphere web client) on page 114

Mapping the virtual machine DVD to an ISO file in the datastore (vSphere desktop client) on

page 115

Mapping the virtual machine DVD to an ISO file in the datastore (vSphere web client) on page 115

Connect to an ISO File in the virtual server datastore

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 113

Comments on this document?

Uploading an ISO file to the datastore (vSphere desktop client)

Procedure

1. Place the ISO file in a folder on your client PC.

2. Using the vSphere client, select the Inventory view.

3. Locate the required virtual machine in the inventory navigation tree on the left. If not

shown, select View > Show VMs in Inventory

4. Click on the virtual machine.

5. Select the Summary tab on the right.

6. In the Resources section, right click on the datastore and select Browse Datastore.

7. Click on the and select Upload File.

8. Browse to the location of the ISO image and click OK.

9. Once the upload has finished, close the Datastore Browser.

Next steps

• You can now map the virtual machine DVD drive to the ISO file. See Mapping the virtual

machine DVD to an ISO file in the datastore (vSphere desktop client) on page 115.

Related links

Connect to an ISO File in the virtual server datastore on page 113

Uploading an ISO file to the datastore (vSphere web client)

Procedure

1. Using the vSphere web client, select the virtual machine. For example, select vCenter

Management and in the navigation tree on the left select the virtual machine.

2. In the inventory, click Datastore and on the Objects tab, select the datastore to which you

will upload the file.

3. Click the icon.

4. Select the folder that you created or select an existing folder, and click the icon.

5. If the Client Integration Access Control dialog box appears, click Allow to allow the

plug-in to access your operating system and proceed with the file upload.

6. On the local computer, find the ISO file and upload it.

7. Once the upload has finished, refresh the datastore file browser to see the uploaded file in

the list.

Next steps

• You can now map the virtual machine DVD drive to the ISO file. See Mapping the virtual

machine DVD to an ISO file in the datastore (vSphere web client) on page 115.

Transfer from a virtual machine DVD

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 114

Comments on this document?

Related links

Connect to an ISO File in the virtual server datastore on page 113

Mapping the virtual machine DVD to an ISO file in the datastore

(vSphere desktop client)

Before you begin

• Upload the ISO file. See Uploading an ISO file to the datastore (vSphere desktop client) on

page 114.

Procedure

1. Use the process above to upload the ISO file to the datastore.

2. Using the vSphere client, select the Inventory view.

3. Locate the required virtual machine in the inventory navigation tree on the left. If not

shown, select View > Show VMs in Inventory

4. Click on the virtual machine.

5. Click on Connect/disconnect the CD/DVD device of the virtual machine in the

toolbar.

• If already connected to a source, the details are shown and the option to disconnect.

Select disconnect and then click the icon again.

6. From the drop-down, select CD/DVD drive 1 and then select Connect to ISO image on

datastore.

7. Select Datastore ISO File and click Browse.

8. Select the ISO file and click OK.

Next steps

• You can now download the ISO to the virtual server using the DVD Primary Server option

in the IP Office Web Manager menus. See Downloading the ISO from the primary DVD on

page 118.

Related links

Connect to an ISO File in the virtual server datastore on page 113

Mapping the virtual machine DVD to an ISO file in the datastore

(vSphere web client)

Before you begin

• Upload the ISO file. See Uploading an ISO file to the datastore (vSphere web client) on

page 114.

Procedure

1. Use the process above to upload the ISO file to the datastore.

Connect to an ISO File in the virtual server datastore

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 115

Comments on this document?

2. Right-click the virtual machine and select Edit Settings.

a. To locate a virtual machine, select a datacenter, folder, cluster, resource pool, host, or

vApp.

b. Click the Related Objects tab and click Virtual Machines.

3. Expand CD/DVD, and select Datastore ISO File from the drop-down menu.

4. Browse to select the file and click OK.

5. Click Edit and select Connected next to the datastore ISO file to connect the device.

6. Click OK.

Next steps

• You can now download the ISO to the virtual server using the DVD Primary Server option

in the IP Office Web Manager menus. See Downloading the ISO from the primary DVD on

page 118.

Related links

Connect to an ISO File in the virtual server datastore on page 113

Connect to the host server's DVD drive

This method uses an ISO file burnt to DVD and then placed into the physical DVD drive of the

VMware server platform. Whilst this method is fast, it requires access to the physical virtual server

platform.

Related links

Transfer from a virtual machine DVD on page 110

Mapping the virtual machine DVD to the host DVD drive (vSphere desktop client) on page 116

Mapping the virtual machine DVD to the host DVD drive (vSphere web client) on page 117

Mapping the virtual machine DVD to the host DVD drive (vSphere

desktop client)

Procedure

1. Insert the DVD into the host server's DVD drive.

2. Using the vSphere client, select the Inventory view.

3. Locate the required virtual machine in the inventory navigation tree on the left. If not

shown, select View > Show VMs in Inventory

4. Click on the virtual machine.

Transfer from a virtual machine DVD

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 116

Comments on this document?

5. Click on the Connect/disconnect the CD/DVD device of the virtual machine icon in

the toolbar.

• If already connected to a source, the details are shown and the option to disconnect.

Select disconnect and then click the icon again.

6. From the drop-down, select CD/DVD and then select Connect to host device.

7. From the drop-down list, select the host device to use. For example, a typical entry for a

CD/DVD drive is

/vmfs/devices/cdrom/mpx.vmhba0:C0T0L0.

8. Click OK.

Next steps

• You can now download the ISO to the virtual server using the DVD Primary Server option

in the

IP Office Web Manager menus. See Downloading the ISO from the primary DVD on

page 118.

Related links

Connect to the host server's DVD drive on page 116

Mapping the virtual machine DVD to the host DVD drive (vSphere

web client)

Procedure

1. Insert the DVD into the host server's DVD drive.

2. Right-click the virtual machine and select Edit Settings.

a. To locate a virtual machine, select a datacenter, folder, cluster, resource pool, host, or

vApp.

b. Click the Related Objects tab and click Virtual Machines.

3. On the Virtual Hardware tab, expand CD/DVD and from the drop-down menu select Host

Device.

4. If more than one type of CD/DVD media is available on the host, select the media.

5. Click OK.

Next steps

• You can now download the ISO to the virtual server using the DVD Primary Server option

in the

IP Office Web Manager menus. See Downloading the ISO from the primary DVD on

page 118.

Related links

Connect to the host server's DVD drive on page 116

Connect to the host server's DVD drive

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 117

Comments on this document?

Downloading the ISO from the primary DVD

About this task

Having connected the virtual server's DVD to an ISO source as above, you can now use IP Office

Web Manager to download that ISO source to the server.

Procedure

1. Login to IP Office Web Manager.

2. Click Solution.

3. Click on the Actions drop-down and select Transfer ISO.

4. Click Transfer from and select DVD Primary Server.

5. Click OK. The menu shows the progress of the download.

6. The servers listed in the Solution overview show an icon and Upgrade Available.

Next steps

• Proceed with upgrading from the uploaded file. See Upgrading using the Transferred ISO

file on page 118.

Related links

Transfer from a virtual machine DVD on page 110

Upgrading using the Transferred ISO file

About this task

Having downloaded an ISO file to the server , IP Office Web Manager indicates those servers

it can upgrade. It does this by showing an icon and Upgrade Available next to the server's

details on the Solution menu.

Warning:

• Not Supported for Upgrades from Pre-R12.0:

This method of upgrading is not supported for upgrading from pre-R12.0 releases. For

example, from R11.1 to R12.0.You must upgrade the server using the processes in the

Upgrading Linux-based IP Office Systems to R12.0 manual.

Procedure

1. Login to IP Office Web Manager.

2. Select Solution.

3. Select the checkbox next to each server to upgrade. Upgrades require the primary server

upgraded before any other servers.

4. Click on the Actions drop down and select Upgrade.

Transfer from a virtual machine DVD

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 118

Comments on this document?

5. The upgrade process typically requires the IP Office server to restart, ending the current

web browser connection. If this occurs, login to IP Office Web Manager again to check on

the status of the upgrade.

Next steps

If necessary, repeat the process to upgrade all the servers.

Related links

Transfer from a virtual machine DVD on page 110

Upgrading using the Transferred ISO file

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 119

Comments on this document?

Part 9: Further Help

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 120

Comments on this document?

Chapter 19: Additional Help and

Documentation

The following pages provide sources for additional help.

Related links

Additional Manuals and User Guides on page 121

Getting Help on page 121

Finding an Avaya Business Partner on page 122

Additional IP Office resources on page 122

Training on page 123

Additional Manuals and User Guides

The Avaya Documentation Center website contains user guides and manuals for Avaya products

including IP Office.

• For a listing of the current IP Office manuals and user guides, look at the Avaya IP Office

™

Platform Manuals and User Guides document.

• The Avaya IP Office Knowledgebase and Avaya Support websites also provide access to the

IP Office technical manuals and users guides.

- Note that where possible these sites redirect users to the version of the document hosted

by the Avaya Documentation Center.

For other types of documents and other resources, visit the various Avaya websites (see

Additional IP Office resources on page 122).

Related links

Additional Help and Documentation on page 121

Getting Help

Avaya sells IP Office through accredited business partners. Those business partners provide

direct support to their customers and can escalate issues to

Avaya when necessary.

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 121

Comments on this document?

If your IP Office system currently does not have an Avaya business partner providing support and

maintenance for it, you can use the Avaya Partner Locator tool to find a business partner. See

Finding an Avaya Business Partner on page 122.

Related links

Additional Help and Documentation on page 121

Finding an Avaya Business Partner

If your IP Office system currently does not have an Avaya business partner providing support and

maintenance for it, you can use the Avaya Partner Locator tool to find a business partner.

Procedure

1. Using a browser, go to the Avaya Website at https://www.avaya.com

2. Select Partners and then Find a Partner.

3. Enter your location information.

4. For IP Office business partners, using the Filter, select Small/Medium Business.

Related links

Additional Help and Documentation on page 121

Additional IP Office resources

In addition to the documentation website (see Additional Manuals and User Guides on page 121),

there are a range of website that provide information about Avaya products and services including

IP Office.

• Avaya Website (https://www.avaya.com)

This is the official Avaya website. The front page also provides access to individual Avaya

websites for different regions and countries.

• Avaya Sales & Partner Portal (https://sales.avaya.com)

This is the official website for all Avaya business partners. The site requires registration for

a user name and password. Once accessed, you can customize the portal to show specific

products and information type that you want to see.

• Avaya IP Office Knowledgebase (https://ipofficekb.avaya.com)

This site provides access to an online, regularly updated version of IP Office user guides and

technical manual.

• Avaya Support (https://support.avaya.com)

Additional Help and Documentation

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 122

Comments on this document?

This site provide access to Avaya product software, documentation and other services for

Avaya product installers and maintainers.

- Avaya Support Forums (https://support.avaya.com/forums/index.php)

This site provides forums for discussing product issues.

• International Avaya User Group (https://www.iuag.org)

This is the organization for Avaya customers. It provides discussion groups and forums.

• Avaya DevConnect (https://www.devconnectprogram.com/)

This site provides details on APIs and SDKs for Avaya products, including IP Office. The site

also provides application notes for third-party non-Avaya products that interoperate with IP

Office using those APIs and SDKs.

• Avaya Learning (https://www.avaya-learning.com/)

This site provides access to training courses and accreditation programs for Avaya products.

Related links

Additional Help and Documentation on page 121

Training

Avaya training and credentials ensure our Business Partners have the capabilities and skills to

successfully sell, implement, and support Avaya solutions and exceed customer expectations. The

following credentials are available:

• Avaya Certified Sales Specialist (APSS)

• Avaya Implementation Professional Specialist (AIPS)

• Avaya Certified Support Specialist (ACSS)

Credential maps are available on the Avaya Learning website.

Related links

Additional Help and Documentation on page 121

Training

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 123

Comments on this document?

Index

A-law ....................................................................................84

activate

network port ..................................................................93

add

browser certificate ........................................................ 89

hard disk Hyper-V .........................................................51

hard disk VMware .........................................................32

TTS language ............................................................... 96

Add

KVM ..............................................................................76

Additional disk

Azure ............................................................................ 68

Hyper-V ........................................................................ 51

KVM ..............................................................................77

VMware ........................................................................ 32

additional hard disk

add Hyper-V ................................................................. 51

add Vmware ................................................................. 32

AWS ..............................................................................59

mount point ...................................................................84

Administrator ......................................................................121

alarm ....................................................................................26

Amazon

machine instance ..........................................................19

profiling ......................................................................... 58

security groups ....................................................... 58, 61

Anywhere .............................................................................10

APIs ................................................................................... 122

Application Notes ...............................................................122

Application Server

profiling ......................................................................... 21

select role ..................................................................... 84

archiving

media manager .............................................................15

AWS

machine instance ....................................................19, 61

profiling ......................................................................... 58

security groups ....................................................... 58, 61

Azure ................................................................................... 63

Additional disk .............................................................. 68

Container ...................................................................... 66

Copy VHD .....................................................................69

Download VHD ............................................................. 63

Network ........................................................................ 65

Resource Group ........................................................... 65

Start virtual machine .....................................................69

Storage Account ........................................................... 66

Upload VHD ..................................................................66

backup ............................................................................... 100

Blob Type .............................................................................66

Blu-Ray ................................................................................ 15

browser

certificate ...................................................................... 89

connect to new server .................................................. 82

connect to server .......................................................... 91

business partner locator .................................................... 122

certificate

Chrome .........................................................................90

Edge ............................................................................. 91

Firefox ...........................................................................89

Google Chrome ............................................................ 90

OVA certificate .............................................................. 30

Safari ............................................................................ 91

change

IP address .............................................................. 83, 84

machine instance ..........................................................61

check

TTS languages ............................................................. 95

Chrome certificate ................................................................90

Cockpit .................................................................................74

companding ......................................................................... 84

configuration ........................................................................ 82

configure

remote file server ........................................................102

server ............................................................................92

connect

new server .................................................................... 82

server ............................................................................91

Container ............................................................................. 66

copy

VHD .............................................................................. 69

copy disk image ................................................................... 49

courses .............................................................................. 122

CPU

adjust (Hyper-V) ........................................................... 54

adjust (KVM) .................................................................79

adjust (VMware) ........................................................... 38

alarm .............................................................................26

Application Server ........................................................ 21

expansion server .......................................................... 20

primary server ...............................................................19

secondary server .......................................................... 19

Server Edition application server ..................................20

CPU cycles

adjust (VMware) ........................................................... 40

create a virtual server

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 124

Comments on this document?

create a virtual server (continued)

AWS ..............................................................................57

Azure ............................................................................ 63

Hyper-V ........................................................................ 47

VMware ........................................................................ 28

critical alarm .........................................................................26

date ......................................................................................84

deactivate

network port ..................................................................93

default

user name and password ............................................. 82

virtual server spec ........................................................ 18

deploy a new server

AWS ..............................................................................57

Azure ............................................................................ 63

Hyper-V ........................................................................ 47

VMware ........................................................................ 28

differences ........................................................................... 14

Media Manager archiving ............................................. 15

RPM files ...................................................................... 14

upgrading ......................................................................15

USB .............................................................................. 15

VMware tools ................................................................15

disable

port ............................................................................... 93

disk image

copy .............................................................................. 49

download ...................................................................... 48

rename ......................................................................... 49

documentation ..................................................................... 10

download .......................................................................11

download

documentation .............................................................. 11

ISO file ........................................................................100

OVA certificate .............................................................. 29

OVA file .........................................................................29

TTS ...............................................................................96

VHDX file ...................................................................... 48

Download

Azure VHD ....................................................................63

KVM ..............................................................................75

TTS .........................................................................63, 75

duplicate IP address ............................................................ 10

DVD+RW archiving ..............................................................15

Edge certificate .................................................................... 91

enable

port ............................................................................... 93

Enterprise ............................................................................ 23

Essentials ............................................................................ 23

ESXi .....................................................................................23

eth1

eth1 (continued)

activate ......................................................................... 93

deactivate ..................................................................... 93

expansion server

profiling ......................................................................... 20

select role ..................................................................... 84

external music ......................................................................15

files

RPM files ...................................................................... 14

Firefox certificate ................................................................. 89

format

additional hard disk .......................................................84

forums ................................................................................122

gateway ............................................................................... 84

Generation 2 .................................................................. 50, 67

Google Chrome certificate ................................................... 90

Grace period ........................................................................ 13

hard disk

add Hyper-V ................................................................. 51

add VMware ................................................................. 32

adjust (Hyper-V) ........................................................... 49

adjust (VMware) ........................................................... 41

alarm .............................................................................26

Application Server ........................................................ 21

expansion server .......................................................... 20

IOPS ............................................................................. 25

mount point ...................................................................84

primary server ...............................................................19

secondary server .......................................................... 19

Server Edition application server ..................................20

hardware requirements ........................................................24

Help ................................................................................... 121

High Availability ....................................................................27

hostname ............................................................................. 84

Hyper-V

Additional disk .............................................................. 51

adjust CPU ................................................................... 54

adjust hard disk ............................................................ 49

adjust RAM ................................................................... 53

power on .......................................................................55

profiling ......................................................................... 52

start ...............................................................................55

ignition ................................................................................. 84

initialization .......................................................................... 82

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 125

Comments on this document?

IOPS .................................................................................... 25

adjust (VMware) ........................................................... 43

alarm .............................................................................26

Application Server ........................................................ 21

expansion server .......................................................... 20

primary server ...............................................................19

secondary server .......................................................... 19

Server Edition application server ..................................20

IP address

change ..........................................................................84

change (console) .......................................................... 83

duplicate issue ..............................................................10

IP Office

documentation .............................................................. 10

IP Office Anywhere .............................................................. 10

ISO file

download .................................................................... 100

transfer to server ........................................................ 101

KVM ..................................................................................... 72

Add virtual machine ...................................................... 76

Additional disk .............................................................. 77

adjust CPU ................................................................... 79

adjust RAM ................................................................... 79

Copy ............................................................................. 76

Download ......................................................................75

power on .......................................................................80

profiling ......................................................................... 78

start ...............................................................................80

launch a new server

AWS ..............................................................................57

Azure ............................................................................ 63

Hyper-V ........................................................................ 47

VMware ........................................................................ 28

license ..................................................................................12

Linux

KVM ..............................................................................72

Local nodal licensing ........................................................... 12

new server .................................................................... 82

server ............................................................................91

Azure ............................................................................ 64

machine instance

application server ................................................... 20, 21

change ..........................................................................61

expansion server .......................................................... 20

primary server ...............................................................19

machine instance (continued)

secondary server .......................................................... 19

Manuals ............................................................................. 121

Media Manager

archiving ....................................................................... 15

Azure disk .....................................................................68

Hyper-V disk ................................................................. 51

KVM disk ...................................................................... 77

VMware disk ................................................................. 32

memory

alarm .............................................................................26

Application Server ........................................................ 21

expansion server .......................................................... 20

primary server ...............................................................19

secondary server .......................................................... 19

Server Edition application server ..................................20

music-on-hold ...................................................................... 15

NAS ..................................................................................... 15

network

alarm .............................................................................26

Azure ............................................................................ 65

network port ......................................................................... 92

disable .......................................................................... 93

enable ...........................................................................93

New machine

Hyper-V ........................................................................ 50

Nodal licensing .................................................................... 12

NTP ......................................................................................84

one-X Portal

documentation .............................................................. 10

users .......................................................................19–21

Oracle VirtualBox .................................................................10

OS Type ...............................................................................67

OVA certificate

download ...................................................................... 29

install ............................................................................ 30

OVA file

deploy ..................................................................... 31, 32

download ...................................................................... 29

Page Blob ............................................................................ 66

password ............................................................................. 84

PLDS Host ID ...................................................................... 12

port

disable .......................................................................... 93

enable ...........................................................................93

power on

Azure ............................................................................ 69

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 126

Comments on this document?

power on (continued)

Hyper-V ........................................................................ 55

KVM ..............................................................................80

VMware ........................................................................ 45

primary server

profiling ......................................................................... 19

select role ..................................................................... 84

profiling ................................................................................ 17

Application Server ........................................................ 21

AWS ..............................................................................58

CPU (Hyper-V) ............................................................. 54

CPU (KVM) ...................................................................79

CPU (VMware) ............................................................. 38

CPU cycles (VMware) .................................................. 40

default server profile ..................................................... 18

expansion server .......................................................... 20

hard disk (Hyper-V) ...................................................... 49

hard disk (VMware) ...................................................... 41

Hyper-V ........................................................................ 52

IOPS (VMware) ............................................................ 43

KVM ..............................................................................78

primary server ...............................................................19

RAM (Hyper-V) ............................................................. 53

RAM (KVM) .................................................................. 79

RAM (VMware) ............................................................. 36

secondary server .......................................................... 19

Server Edition application server ..................................20

VMware ........................................................................ 35

Quick Reference Guides ....................................................121

RAM

adjust (Hyper-V) ........................................................... 53

adjust (KVM) .................................................................79

adjust (VMware) ........................................................... 36

Red Hat Linux ...................................................................... 72

related documentation ......................................................... 10

remote file server ............................................................... 102

rename disk image .............................................................. 49

requirements

vMotion ......................................................................... 25

Reseller ..............................................................................121

resilience ..............................................................................17

High Availability ............................................................ 27

Resource Group .................................................................. 65

role .......................................................................................84

RPM files ............................................................................. 14

Safari certificate ................................................................... 91

sales .................................................................................. 122

SDKs

..................................................................................122

secondary server

profiling ......................................................................... 19

select role ..................................................................... 84

Secure Boot ......................................................................... 50

security groups

change ..........................................................................61

create ............................................................................58

Security Type ....................................................................... 67

server

backup ........................................................................ 100

configue ........................................................................ 92

configuration ................................................................. 82

connect ......................................................................... 91

connect to new ............................................................. 82

ignite new ..................................................................... 84

initialization ................................................................... 82

license .......................................................................... 12

profiling ......................................................................... 17

server type ....................................................................84

transfer ISO file ...........................................................101

upgrade ........................................................................ 99

virtual server differences ...............................................14

setting

IP address .................................................................... 83

Snapshot ..............................................................................23

software requirements ......................................................... 24

Source Blob ......................................................................... 67

Source Type .........................................................................67

start

Hyper-V virtual machine ............................................... 55

KVM ..............................................................................80

Start

Azure ............................................................................ 69

Storage Account .................................................................. 66

support ...............................................................................122

Media Manager archiving ............................................. 15

RPM files ...................................................................... 14

upgrading ......................................................................15

USB .............................................................................. 15

VMware ........................................................................ 23

VMware tools ................................................................15

switch on

Azure ............................................................................ 69

Hyper-V ........................................................................ 55

KVM ..............................................................................80

VMware ........................................................................ 45

system

settings ................................................................... 28, 47

System Administrator .........................................................121

Technical Bulletins ............................................................. 122

time ...................................................................................... 84

timezone .............................................................................. 84

training ....................................................................... 122, 123

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 127

Comments on this document?

transfer ISO

from DVD .................................................................... 110

from remote file server ................................................102

using SSH/SFTP ........................................................ 105

TTS ...................................................................................... 95

add language ................................................................96

check ............................................................................ 95

download ...................................................................... 96

U-law ....................................................................................84

upgrade ................................................................................99

from virtual server .........................................................15

RPM files ...................................................................... 14

transfer ISO file ...........................................................101

upload

VHD .............................................................................. 66

USB ..................................................................................... 15

User Guides .......................................................................121

users

Application Server ........................................................ 21

expansion server .......................................................... 20

one-X Portal ..................................................................20

primary server ...............................................................19

secondary server .......................................................... 19

vCenter ................................................................................ 23

VHD

copy .............................................................................. 69

Download ......................................................................63

upload ...........................................................................66

VHDX file

deploy ........................................................................... 50

download ...................................................................... 48

Virtual machine

Add KVM ...................................................................... 76

Start Azure ....................................................................69

Start Hyper-V ................................................................55

Start KVM ..................................................................... 80

VM Generation .....................................................................67

vMotion .......................................................................... 23, 25

VMware

Additional disk .............................................................. 32

adjust CPU ................................................................... 38

adjust CPU cycles ........................................................ 40

adjust hard disk ............................................................ 41

adjust RAM ................................................................... 36

High Availability ............................................................ 27

IOPS ............................................................................. 43

OVA certificate .............................................................. 30

power on .......................................................................45

profiling ......................................................................... 35

requirements .................................................................24

Snapshot ...................................................................... 23

VMware (continued)

supported features ........................................................23

VMware Player .................................................................... 10

VMware tools ....................................................................... 15

Voicemail Pro

channels ....................................................................... 19

documentation .............................................................. 10

TTS ...............................................................................95

vSphere ............................................................................... 23

warning alarm ...................................................................... 26

Web Console ....................................................................... 74

WebLM centralized licensing ............................................... 12

websites .............................................................................122

October 2024 Deploying Avaya IP Office Servers as Virtual Machines 128

Comments on this document?