How To: Configure DynaCenter to migrate servers that do not have a direct connection to the MWS in your Amazon VPC
Reference Number: AA-00395 Views: 1313 Created: 08-29-2016 10:23 Last Updated: 10-18-2016 16:24

Applies To:

DynaCenter 6.5 and later

Background:

By default, when installed from the AWS Marketplace, DynaCenter is configured to migrate servers that have direct access to the private subnet where the MWS is installed. If your data center cannot connect to your VPC because you do not have either AWS Direct Connect or a VPN, you must associate a public IP to the MWS so that your servers can connect to the MWS over the internet. Consider using an elastic IP for the public IP so that the IP will remain associated to the instance if it is ever stopped and then restarted.

Important: When you migrate your source servers using the public IP of the MWS, your server workloads travel over the internet.

More Information:

For information on installing DynaCenter from the AWS Marketplace:

http://docs.racemi.com/Amazon/InstallDynaCenterAWSMarketplace/Default.htm  

Resolution:

To ensure that DynaCenter can migrate servers that do not have a direct connection to your VPC, do the following:

1.   Log in to the MWS server as the ec2-user.

2.   If your MWS does not have a public IP address, associate an elastic IP to your MWS.

3.   Run the following command to register the public network with DynaCenter:

dccmd register external network public https://<MWSPublicIP>

Example:

dccmd register external network public https://54.176.176.75

4.   Run the following command to get the private IP of the MWS server, and note the IP:

curl http://169.254.169.254/latest/meta-data/local-ipv4

5.   Run the following commands to register the public network created in Step 2 with the DynaCenter depots:

dccmd register depot image dav://127.0.0.1/repo/images private=dav://<PrivateIP> public=dav://<PublicIP>

dccmd register depot sync  dav://127.0.0.1/repo/sync private=dav://<PrivateIP> public=dav://<PublicIP>

dccmd register depot park dav://127.0.0.1/repo/parking private=dav://<PrivateIP> public=dav://<PublicIP>

6.   Run the following command to create the DynaCenter agent installation packages:

sudo /opt/race/bin/rpackagedpad public depot://park

7.   Use the following instructions to download and install the agent packages that use the public network:

Installing the DynaCenter Agent

8.   When you configure the migration template to migrate servers that have access to the MWS over the public network, ensure that you select the public network when you configure the Route to Source setting on the General Tab of the template editor.

Reference: Migrating Server Workloads with the DynaCenter Console