Migrating Appliance Virtualization Platform deployed on Common Server 1, 2, or 3 with Communication Manager to Avaya Solutions Platform 130 Release 5.x

Last Updated : Jan 17, 2024 |
Prolog information
Metadata
Keywords:
Use the following procedure to migrate Appliance Virtualization Platform that is deployed on Avaya Common Server 1, 2, or 3 to Avaya Solutions Platform 130 Release 5.x with Communication Manager deployed on it.
Note:
Common Server R1, R2, and R3 (HP DL360 G7/G8/G9 and Dell R610/R620/R630) do not support Avaya Aura® Release 10.1. The last supported release for these servers is Avaya Aura® 8.1.3.x. You must place an order for the new Avaya Solutions Platform 130 R5.x. The Avaya Solutions Platform 130 R5.x installer needs the current Appliance Virtualization Platform and Communication Manager IP and naming information. The installer also needs the Communication Manager server backup details like the user name, password, and directory path.
Note:
If multiple applications are on the same server, follow the upgrade order.
Before you begin
Important:
This should be a like to like migration from application perspective. So only migrate the existing applications first and do not deploy any additional application. Once all the applications are migrated successfully, then use the Avaya One Source (A1S) Configurator tool to determine if any additional applications can be deployed on Avaya Solutions Platform 130.
  1. Take the backup of Communication Manager and keep it on remote servers.
    ADDITIONAL INFORMATION:
    For information about creating a data backup on a remote server, see Creating a full backup and Restoring backup.
  2. To do the graceful shutdown of the application, log in to the host UI through vSphere Web Client, and do the following:
    1. Select the application, right-click, and then click Guest OSShut down.
      STEP RESULT:
      The system displays the following message:
      Are you sure you want to shut down <virtual_machine_name>.
    2. To proceed, click Yes.
    ADDITIONAL INFORMATION:
    Note:
    • If you have a virtual machine on the host, Avaya recommends to do the graceful shutdown of the virtual machine.
    • Ensure that no calls are running on the system.
  3. Shut down the Appliance Virtualization Platform host using the command line interface.
    ADDITIONAL INFORMATION:
    For information, see Shutting down Appliance Virtualization Platform host from CLI.
  4. The CSR1/R2/R3 is now offline. If there are issues with the Avaya Solutions Platform 130 R5.x deployment, you can bring back the CSR1/R2/R3 server on-line.
  5. Optional: If a rollback is required, you can bring back the CSR1/R2/R3 server on-line.
  6. Deploy Avaya Solutions Platform 130 Release 5.x.
    ADDITIONAL INFORMATION:
    For information about deploying Avaya Solutions Platform 130, see Installing the Avaya Solutions Platform 130 Series.
  7. Deploy Communication Manager Release 10.1 on Avaya Solutions Platform 130 Release 5.x.
    ADDITIONAL INFORMATION:
    For information, see Deploying Avaya Aura® Communication Manager in Virtualized Environment.
  8. Restore the backup taken and ensure everything is working fine.
    ADDITIONAL INFORMATION:
    For information about creating a data backup on a remote server, see Creating a full backup and Restoring backup.