Please enable JavaScript to view this site.

R11.1 Linux-Based System Upgrade Notes

> Upgrading VMware Virtual Machines

Upgrading a VMware Virtual Machine

Scroll Prev Up Next More

This process boots the virtual machine from the copied VMDK upgrade file. The boot process backups the data on the server's existing drive, upgrades its components to R11.1 SP2 and then restores the server data.

Pre-Requisites

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 Uploading the VMDK File.

Process

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.Login to the VMware platform hosting the virtual machine.

3.Mount the upgrade VMDK files as a new hard disk for the virtual machine:

a.Select the virtual machine and click Edit virtual machine settings.

b.On the Virtual Hardware tab, at the bottom set New device to Existing Hard Disk and click Add.

c.Browse to the copy of the upgrade VMDK file and select that file.

Do not use the originally uploaded VMDK file. It must be a copy of that file. If upgrading a network of servers, each server can use the same VMDK copy but not simultaneously.  

d.Click Next >. Check the settings and click OK.  

4.Adjust the hard drive boot order of the virtual machine's hard disks so that it reboots using the upgrade VMDK file. This is done by adjusting the SCSI node setting of each drive:

a.Expand the settings of the hard disk.

b.Next to Virtual Device Node, click on the SCSI setting and select the drive's position in the boot order. SCSI(0:0) is the first drive and the one from which the server boots, SCSI(0:1) the second and so on.

c.Click OK. and repeat the process for the other drives present.

d.When completed, the upgrade VMDK drive should be SCSI(0:0), the virtual machine's original drive SCSI(0:1), and if present, the Media Manager drive SCSI(0:2).

5.Click Power on the virtual machine.

6.Click Summary and then click on the screen image.

7.Monitor the upgrade process from the console. When completed, the server is automatically powered off.

8.Remove the upgrade VMDK file from the virtual machine:

a.Select the virtual machine and click Edit virtual machine settings.

b.Move the cursor to the right of the upgrade hard disk entry. Click the x icon that appears.

c.Repeat the process in step 4 to return the remaining drives back to their original boot order. That is, put the original IP Office drive back to SCSI(0:0), and if present, the Media Manager drive SCSI(0:1).

9.Restart the virtual server by clicking Power on the virtual machine. Once the server has restarted:

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.

10.Once satisfied with the operation of the upgraded servers, delete the copies of the VMDK file.  

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.

Use of this site indicates acceptance of its cookies and analytics, and acceptance of the Avaya privacy policy.

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