Please enable JavaScript to view this site.

R11.1 Linux-Based System Upgrade Notes

This process boots the virtual machine from the copied VMDK upgrade file. The boot process backups the server and then upgrades its components to R11.1 SP2 before restoring the server data.


1.Upgrade the server to R11.0.4.5 using the standard ISO upgrade process. Test and verify correct operation of all services on R11.0.4.5 before upgrading to R11.1 SP2/FP1.

It is especially important to verify Media Manager is running if the server has stored call recordings. Media Manager must be running during the upgrade process for correct migration to R11.1 SP2/FP1.

2.Ensure that you have a full backup in order to be able to recover from any upgrade issues. See Creating a Back Up.

3.Upload and prepare the VMDK file. See Preparing the AWS Upgrade Volume.


1.Shutdown the server using the System | Shutdown in its port 7071 web control menus:

! Warning: Do not use any other method to shutdown the server. Doing so will lead to the loss of data and settings. This method creates backup files for some services that are then used for the upgrade.

a.Connect to the server's web control menus using port :7071.

b.On the System menu, click Shutdown and click Yes. Wait approximately 90 seconds after which you should see the services shutting down.

2.Check that the server has completed its shutdown:

a.In EC2, select Instances and select the instance.

b.Select Actions | Instance State | Stop and confirm the action.

3.With the instance selected, in the Description tab, the Block devices section provides links for the virtual disks being used: the current IP Office drive (/dev/sda1) and possibly a Media Manager drive (/dev/sdb).

4.Click on the /dev/sda1 link and then the EBS ID link:

a.Note the Volume ID. Click Name field and give the volume a distinctive name if not already done.

b.Click and then select Actions | Detach.

5.If also present, click on the /dev/sdb link. Again note the Volume ID and then select Actions | Detach.

6.Attach the upgrade volume as the drive from which the instance should boot:

a.Select Elastic Block Storage | Volumes.

b.Select Actions | Attach Volume.

c.In the Instance field, select the matching instance.

d.For the Device, enter /dev/sda1.

e.Repeat the process to reattach the original IP Office volume but with its Device now set to /dev/sdb. It is not necessary to reattach the Media Manager volume at this stage.

7.Restart the instance:

a.Select Instances and select the instance.

b.Select Actions | Instance State | Start and confirm the action.

8.Wait until the status of the instance indicates that it has been powered off:

a.Select Instances. Locate the instance and verify the status is shown as "Stopped" in the Status Checks column.  

9.Detach all the current volumes again (the upgrade volume and the original IP Office volume).

10.Reattach the original IP Office volume as /dev/sda1 and, if present, the Media Manager volume as /dev/sdb.

11.Restart the instance.  

a.Check the version of the server is now shown as R11.1 SP2. If not, see Failed to Upgrade.

b.Check the operation of the services (calls, voicemail, one-X Portal for IP Office, etc). See Known Upgrade Issues for a number of known issues that affect some upgrades.

c.If part of a network, continue with the next server. See Upgrading a Network of Servers.

12.Once completed and satisfied with the operation of the upgraded instance(s), delete the upgrade volume.

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