Use this procedure to deploy and prepare Avaya Aura® Web Gateway Release 10.2.x virtual machines for the migration. To improve efficiency, you can perform many steps simultaneously across all the nodes in the cluster.
Before you begin
Create system backups and gather the required server information by completing the migration preparation procedure. For more information, see Preparing for migration.
For OVA-based deployments, ensure that you have the latest Avaya Aura® Web Gateway Release 10.2.x installer and OVA.
For software-only deployments, ensure that you have the latest Avaya Aura® Web Gateway Release 10.2.x software-only installation package.
Procedure
Deploy Avaya Aura® Web Gateway Release 10.2.x virtual machines using the server configuration information gathered for the Release 3.11 system and then start the virtual machines.
For more information about the deployment procedures, see the Initial setup for VMware and AWS deployments chapter in Deploying the Avaya Aura® Web Gateway for your deployment type.
Attach the new virtual machine to the network recorded for the node in Preparing for migration.
For OVA-based deployments, if you have an installer that is newer than the one staged in /opt/Avaya/ within the virtual machine, for each node in the cluster, copy the installer to the administrative user's home directory suing a file transfer program, such as SFTP or SCP.
If FIPS was enabled on your Release 3.11 system or if you want to use FIPS, perform Enabling FIPS mode.
Important:
You must enable FIPS if FIPS was enabled on your Release 3.11 system. You cannot use backups from a FIPS system to deploy a non-FIPS system. If FIPS was not enabled on your Release 3.11 system, you can enable FIPS as required.
If additional STIG hardening was enabled on your Release 3.11 or if you want to enable additional STIG hardening, perform Enabling additional STIG hardening.
Important:
You must enable additional STIG hardening if it was enabled on your Release 3.11 system. You cannot use backups from a system where additional STIGs are enabled to deploy a system where additional STIGs are disabled. If additional STIG hardening was not enabled on your Release 3.11 system, you can enable it as required.
