Environment
GWAVA (Secure Messaging Gateway) 7
Situation
During the migration from SMG on Ubuntu appliance to SMG on SLES appliance, it is designed to change the IP address on both servers. It will give the new SMG on SLES appliance the IP of the SMG on Ubuntu server. The reason for this, is to make it easier after the migration, so mail will start routing to it immediately. How can this be prevented?
Resolution
To break out of the IP address change, during the migration, do the following:
Note: In this example the SMG on Ubuntu (the server being replaced) server's IP Address is 151.155.211.198. The new SMG on SLES (replacement server) server's IP Address is 151.155.211.199.1) During the required portion of the "Replace existing SMG server" process, (On the server being replaced (SMG on Ubuntu server), instructions state to go to the /opt/gwava/replace directory and execute: sudo ./replace_server.sh) At the end of this step you will see the following screen:2) Instead of pressing [SPACE], press Ctrl-C. This will stop the script from shutting down the SMG on Ubuntu server. At this point the network configuration file has been updated to use the 151.155.211.198 IP Address. To reset it to it's original value (151.155.211.199) execute the following command: sudo ./reset_address.sh3) At this point the configuration file has been reset and the SMG on Ubuntu server is set back to using the original IP Address (in this example 151.155.211.199). Hit Ctrl-C again, to prevent the script from shutting down the server and just continue to run. The SMG on Ubuntu server will continue running at it's original IP address and the network configuration file will be correct so that in the future if the server is restarted it will still be using the original IP Address. (If it's desired to have the SMG on Ubuntu to continue scanning mail the SMG service will need to be started back up by typing: sudo /etc/init.d/gwava7 start).
The required portion of the "Replace existing server" migration has been performed (by copying all the required data to the new server) without replacing the server.