There are several methods to access your RackConnect Cloud Servers. Following, is an overview of these methods.
If the automation feature Provision public IP address is enabled, RackConnect automatically assigns a new public IP address from one of your Dedicated IP blocks to each of your Cloud Servers and adds the appropriate translation (NAT) to your Edge Network Device. After the IP address is assigned, you can view it by querying the Cloud Servers API or looking up the Cloud Server in the MyRackspace Portal.
The following screenshot shows the IP address information of a RackConnect Cloud Server in the RackConnect Management Interface section of the MyRackspace Portal.
Note: Disregard the initial public IP address assigned to your Cloud Server when it was built. When the RackConnect automation completes, that initial public IP address is no longer used.
You must explicitly create one or more network policies to allow direct access to your RackConnect Cloud Servers from the Internet via their Public IP address. By default, network policies do not allow inbound access from the Internet to your Cloud Servers, even if you applied the Basic Access Network Policy Template. (The one exception to this would be any existing rules on the outside/external access list of your Edge Network Device that allow requests destined for any public IP address through any ports or protocols).
Other than the direct access method detailed in the preceding section, following are some alternative methods of connecting to your RackConnect Cloud Servers:
IMPORTANT NOTE: When connecting between your Cloud and Dedicated environments with RackConnect, you should always use the private IP addresses of your Dedicated and Cloud Servers.
© 2011-2013 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License