Upgrading an AWS instance to R12.0.x

Last Updated : Apr 18, 2024 |

About this task

This process boots the virtual machine from the copied vmdk upgrade file. The boot process backs up the server data, upgrades it to R12.0.x, and then restores the server data.

Before you begin

  • You must upgrade the server to IP Office R11.1.3.x.

  • After upgrading to IP Office R11.1.3.x, back up all the servers and services before upgrading to R12.0.x. See Creating an IP Office backup.

Procedure

  1. Shut down the server using the following method:
    1. Connect to the server's platform view/web control menus using port 7071.
    2. Click Shutdown and click Yes. Wait approximately 90 seconds, after which on the connected monitor you will see services shutting down.
    warning
    • 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 which the upgrade process uses.

  2. Check that the server has completed its shutdown:
    1. In EC2, select Instances and select the instance.
    2. Select Actions > Instance State > Stop and confirm the action.
  3. The Description > Block devices section shows links for the instance's virtual disks:
    • /dev/sda1 = The IP Office drive.

    • /dev/sdb = The optional Media Manager drive.

  4. Click on the /dev/sda1 link and then the EBS ID link:
    1. Note the Volume ID. Click the Name field and give the volume a distinctive name if not already done.
    2. Click and then select Actions > Detach.
  5. If also present, click on the /dev/sdb link. Note the Volume ID and then select Actions > Detach.
  6. Attach the upgrade volume as the drive from which the instance boots:
    1. Select Elastic Block Storage > Volumes.
    2. Select Actions > Attach Volume.
    3. In the Instance field, select the matching instance.
    4. For the Device, enter /dev/sda1.
    5. Repeat the process to reattach the original IP Office volume but the Device now set to /dev/sdb.
    6. You do not need to reattach the Media Manager volume at this stage.
  7. Restart the instance:
    1. Select Instances and select the instance.
    2. Select Actions > Instance State > Start and confirm the action.
  8. The instance boots from the upgrade volume and starts the upgrade process.
  9. When the upgrade has finished, the instance automatically switches off.
    1. Select Instances.
    2. Locate the instance and verify the Status Checks column shows "Stopped".
  10. Detach the upgrade volume and the original IP Office volume.
  11. Reattach the original IP Office volume as /dev/sda1.
  12. If present, reattach the Media Manager volume as /dev/sdb.
  13. Restart the instance.
  14. Wait 10 minutes. During this time, the upgrade process will complete additional steps and reboot the server again.
  15. When the server has restarted:
    1. Check that the version shown is R12.0.x. If not, see Failure to upgrade.
    2. Cancel any Consolidate Configuration Entries menu shown in IP Office Manager or IP Office Web Manager. The menu disappears after you have upgraded all IP Office servers in a network to R12.0.x.
    3. Ignore any Upgrade Available prompts shown in IP Office Web Manager. You must only upgrade other IP Office servers using the processes in this document.
    4. Following the upgrade, test and verify the operation of all services. If you find any issues, see Known upgrade issues.
  16. If the server is part of a network, continue with the next server. See Upgrading a network of IP Office servers.
    • You can reuse the upgrade image to upgrade multiple servers in sequence. However, you must only use an upgrade image to upgrade one server at a time.

  17. When satisfied with the operation of the upgraded servers, you can delete the copies of the upgrade disk.
    • Only do this after when you are satisfied with the upgrade. The upgrade disk contains log files relating to the upgrade, see Upgrade logs. You need those log files to report upgrade issues.