Upgrading a VMware virtual machine to R11.1.3

Last Updated : Aug 09, 2024 |
Prolog information
This process boots the virtual machine from the copied VMDK upgrade file. The boot process backs up the server and then upgrades its components to R11.1.3 before restoring the server data.
Other:
  • Do not use any other method to shut down the server. Doing so will cause the loss of data and settings. This method creates files used by the upgrade process.
Before you begin
  • You must upgrade the server to IP Office R11.0.4.8.
  • After upgrading to IP Office R11.0.4.8, back up all the servers and services before upgrading to R11.1.3. See Creating an IP Office backup.
  1. Shut down the server using the following method:
    1. Connect to the server's platform view/web control menus using port 7071.
    2. On the System tab, click Show optional services.
    3. If the Media Manager service is running, deselect the service's auto-start checkbox and then stop the service.
    4. Click Shutdown and click Yes. Wait approximately 90 seconds, after which you will 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:
    1. Select the virtual machine and click Edit virtual machine settings.
    2. On the Virtual Hardware tab, at the bottom set New device to Existing Hard Disk and click Add.
    3. Browse to the copy of the upgrade vmdk file and select that file.
      ADDITIONAL INFORMATION:
      Important:
      • 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.
    4. Click Next >. Check the settings and click OK.
  4. Adjust the boot order of the virtual machine's hard disks so that it reboots using the upgrade vmdk file:
    1. Expand the settings of the hard disk.
    2. 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.
    3. Click OK. and repeat the process for the other drives present.
    4. When completed, the upgrade vmdk drive is 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 automatically switches off.
  8. Remove the upgrade vmdk file from the virtual machine and reset the drive boot order:
    1. Select the virtual machine and click Edit virtual machine settings.
    2. Move the cursor to the right of the upgrade hard disk entry. Click the x icon.
    3. Repeat the process in step 4 to return the remaining drives back to their original boot order. Put the original IP Office drive back to SCSI(0:0) and, if present, the Media Manager drive to SCSI(0:1).
  9. Restart the virtual server by clicking Power on the virtual machine.
  10. When the server has restarted:
    1. Check that the version shown is R11.1.3. If not, see Failure to upgrade.
    2. Following the upgrade, test and verify the operation of all services:
      ADDITIONAL INFORMATION:
      • Incoming and outgoing calls.
      • Voicemail services.
      • Avaya one-X® Portal for IP Office if used.
  11. If the server hosts Media Manager:
    1. Connect to the server's platform view/web control menus using port 7071.
    2. On the System tab, click Show optional services.
    3. For the Local Media Manager service, select the service's auto-start checkbox and then start the service. This starts the Media Manager database encryption process:
      ADDITIONAL INFORMATION:
      • You must let Media Manager complete this one-time encryption process. The time required depends on the number of recordings and the server resources and can take several hours.
      • Interrupting the encryption process, for example restarting the Media Manager service or the IP Office server, can cause issues.
      • When completed, you can check recordings using the Media Manager menus.
  12. If the server is part of a network, continue with the next server.
  13. When satisfied with the operation of the upgraded servers, you can delete the copies of the vmdk file.