Please enable JavaScript to view this site.

R11.1 Linux-Based System Upgrade Notes

The upgrade process in detail is:

 

Action

Description

1.

Upgrade to the latest R11.0.4 service pack

The server should first be upgraded to R11.0.4.5 using the standard ISO transfer methods.

This is absolutely essential. R11.0.4.5 contains changes which are used by the process of upgrading to R11.1 SP2.

Attempting to upgrade to R11.1 SP2 or higher from any earlier pre-R11.0 release will fail and may cause the lose of data.

2.

Verify Correct Operation

Once upgraded to R11.0.4.5, verify the operation of all services (local and remote phones, voicemail, one-X Portal for IP Office, Media Manager, etc).

! WARNING: Even if the customer no longer uses Media Manager, if there are any stored call recordings on the server's additional hard disk, then the service needs to be running correctly on R11.0.4.5 before the server is upgraded to R11.1 SP2. Once the server is upgraded to R11.1 SP2, the Media Manager service can be stopped again.

3.

Backup the Servers

Once satisfied with operation at R11.0.4.5, take a full backup of all servers. The backup is not used as part of the R11.1 SP2 upgrade processes in this document but is recommended for system recovery should that become necessary.

4.

Upgrade from R11.0.4 to R11.1 or R11.1 FP1

Finally, proceed with the upgrade from R11.0.4.5 to R11.1 SP2 (for Hyper-V, only an upgrade to R11.1 FP1 is available). The upgrade process varies depending on the type of server:

Unified Communications Module
This process uses a 32GB USB memory key created using Avaya USB Creator and the 11.1 SP2 ISO file. The Unified Communications Module is rebooted from the USB memory key. The USB memory key then runs the upgrade process and is used to temporarily store existing data during the module's upgrade.

Physical Linux-based IP Office Servers (including IP Office Application Server)
This process use a 256GB USB memory key created using Rufus and the 11.1 SP2 ISO file. The USB memory key is used to run the upgrade process and to temporarily store existing data during the modules upgrade.

VVMware Virtual Machines
This process uses a virtual machine hard-disk (VMDK) file downloaded from Avaya. The virtual hard-disk is mounted onto the existing server and the server then rebooted using that disk. The upgrade hard-disk runs the upgrade process and is used to temporarily store data during the server's upgrade.

Hyper-V Virtual Machines
This process uses a virtual machine hard-disk (VHD) file downloaded from Avaya. The virtual hard-disk is mounted onto the existing server and the server then rebooted using that disk. The upgrade hard-disk runs the upgrade process and is used to temporarily store data during the server's upgrade.

Hyper-V virtual machines can only be upgraded to R11.1 FP1. There is no Hyper-V upgrade file for R11.1 service packs.

AWS Virtual Machines
This process is similar to the VMware virtual machine process above. However, extra steps are required in order to convert the VMDK file into a hard-disk volume that can be used to boot AWS instances.

 

 

Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments at its own discretion. The publication of information in this document does not imply freedom from patent or any other protective rights of Avaya or others. All trademarks identified by ™, ® or © are registered trademarks or trademarks respectively are the property of their respective owners.

© 2021 AVAYA
Issue 03.b.-
Friday, November 5, 2021