Use this procedure to record server information and back up your Avaya Aura® Web Gateway Release 3.11 system. This information and backup files are required when you deploy new Avaya Aura® Web Gateway Release 10.2.x virtual machines.
If you use Avaya Solutions Platform 120 or Avaya Solutions Platform 130 Release 4 or below, you must upgrade the platform to ASP 130 Release 5. For more information about the upgrade process, see Upgrading Avaya Solutions Platform from Release 4.0 to 5.0.
Note:
Avaya Solutions Platform 120 is synonymous with Avaya Converged Platform 120 and Appliance Virtualization Platform (AVP).
If you use VMWare ESXi 6.0 or 6.5, you must upgrade it to VMware ESXi 6.7 or later.
In cluster deployments, perform steps 2 to 5 on the seed node first and then on all non-seed nodes.
Log in to Avaya Aura® Web Gateway as an administrator.
Run the following command to collect the current system logs:
app collectlogs collect
Avaya Aura® Web Gateway creates a .zip file containing the logs in the /var/log/Avaya/collected-logs directory.
Support teams can resolve issues that might occur on the new system by comparing the collected logs to the logs on the new system.
Do the following to record server information and then save the output in a safe location:
To obtain the fully qualified host name, run the following command:
hostname -f
To obtain the IP address and the network mask, run the following command:
ifconfig -a | grep inet | grep -v 127.0.0.1
To obtain the IP address of the default gateway, run the following command:
netstat -nrv | grep '^0.0.0.0'
To obtain the DNS search list and DNS server IP address, run the following command:
cat /etc/resolv.conf
To obtain the NTP server IP address, run the following command:
cat /etc/ntp.conf | grep "^server"
Log in as the administrator and run the following commands to display the user name and primary group for the administrative account:
id --user --name
id --group --name
If you want to use the same keystore password, obtain the existing keystore password by referencing notes from the original installation.
If you do not want to use the same keystore password, record a new keystore password.
Record the current System Manager enrollment password by referencing notes from the original installation.
Copy the following files to an off-board storage location using a file transfer program, such as SFTP or SCP:
The .zip archive containing the logs.
Any other desired content from the /home directory.
Repeat steps 2 to 5 for all remaining nodes in the cluster.
On each node, run the following command to stop Avaya Aura® Web Gateway and verify that services are stopped:
svc csa stop
svc csa status
On each node, run the following commands to shut down the Avaya Aura® Web Gateway Release 3.11 virtual machine and turn off the power:
sudo shutdown -hP now
If the virtual machine stays powered on, shut down the virtual machine from the virtual machine host interface.
For OVA-based deployments, for each virtual machine in the cluster, use the original installation notes to record the OVA profile used while deploying the original OVA.
Next Steps
Deploy Avaya Aura® Web Gateway Release 10.2.x virtual machines.
