Accessing RackConnect cloud servers
Previous section: Managing RackConnect v2.0 network policies
Applies to: RackConnect v3.0 and RackConnect v2.0
You can use several methods to access your RackConnect cloud servers. This article provides an overview of some of these methods.
Direct access to RackConnect cloud servers via their public IP address
With RackConnect v2.0, if the automation feature to provision public IP addresses is enabled on your RackConnect Cloud account, then the RackConnect automation systems automatically assigns new public IP addresses to your newly built cloud servers. With RackConnect v3.0, automation features are no longer available, but you can still provision public IP addresses to your cloud servers by using the RackConnect v3.0 API. In either case, the public IP addresses assigned to your cloud servers are allocated out of one of your dedicated public IP address blocks. A NAT (network address translation) entry is then configured on your RackConnect edge network device, which is a one-to-one association from the allocated dedicated public IP address to the cloud server’s ServiceNet IP address, in the case of RackConnect v2.0, or to its cloud network IP address, in the case of RackConnect v3.0.
You can use these dedicated public IP addresses to use SSH or RDP to directly access your cloud servers, as long as access is allowed. Access might be allowed via network policies with RackConnect v2.0. With RackConnect v3.0, access might be allowed via firewall access list entries created by the Network Security Team or via the Firewall Manager feature available within the MyRackspace portal.
You can view the IP addresses assigned to your cloud servers by querying the Cloud Servers API or by looking up the cloud server’s details in the MyRackspace portal or the Cloud Control Panel. For example, the following image shows the dedicated IP address, named RackConnect, for a fully deployed RackConnect cloud server in the MyRackspace portal.
Note: Disregard the initial public IP address assigned to your cloud servers when they are built. With RackConnect v2.0, the automation processes deactivates the initial public IP address.
Alternative methods of connecting to your RackConnect cloud servers
If you have not provisioned dedicated public IP addresses to your RackConnect cloud servers, you might be able to use one of these alternative methods for connecting to these cloud servers:
You can connect to one of your dedicated servers, and then from that dedicated server, you can connect to one of your RackConnect cloud servers by using its ServiceNet IP address with RackConnect v2.0 cloud servers, or by using its cloud network’s IP address with RackConnect v3.0 cloud servers. With RackConnect v2.0, this method requires that you have an appropriate Dedicated to Cloud Servers network policy deployed. With RackConnect v3.0, this method requires that you have an appropriate access list entry that allows this access.
Connect directly to the console of the cloud server by using the console option available within the Cloud Control Panel.
If you are using a Cisco ASA as your RackConnect edge network device, it might be feasible to use a site-to-site VPN or client VPN solution to allow direct access to your cloud servers. With RackConnect v2.0, this option also requires that you have an appropriate Dedicated to Cloud Servers network policy deployed to allow your VPN network to access your cloud servers. With RackConnect v3.0, this option requires access list entries be created to allow your VPN network to access your cloud servers. If you are interested in setting up a VPN solution with your RackConnect environment, contact support.
Important: When connecting between cloud and dedicated environments with RackConnect, always use the private IP addresses of the dedicated and cloud servers to avoid bandwidth charges.
If you have any questions, reach out to us. Our contact information is available on the Contact Us page.
Continue the conversation in the Rackspace Community.
©2016 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License