In order to Implement RackConnect, the following are required:
Supported Network Device - The RackConnect automation is compatible with any Cisco ASA firewall (5505 Security+ or better) or F5 Big-IP load balancer. You need at least one of these devices in your managed hosting configuration in order to implement RackConnect. If you already have one, there is no additional charge for RackConnect.
Supported Region - RackConnect is currently available in our Chicago (ORD), Dallas (DFW), and London (LON3) regions. Your dedicated managed hosting environment and Cloud environment must be located in the same region in order to implement RackConnect.
RackConnect connects an available physical interface on your Network Device to the Cloud internal network. Creating a new Cloud Server triggers the RackConnect automation process, which, in cases where all Automation Features are enabled, will:
1. Validate the existence of a Gateway IP address on your RackConnect Connected Device, and add the appropriate Gateway IP address, if it does not exist
2. Provision a public IP address for the Cloud Server and configure a static NAT translation for it on the RackConnect Edge Network Device
3. Connect to the Cloud Server, disable its public interface, and route all traffic through its private interface (a.k.a. ServiceNet, which has the 10.x.x.x IP address) towards your RackConnect Connected Device as the default gateway.
4. The automation then adjusts access lists on the firewall, load balancer (if applicable), and Cloud Server software firewalls based on your pre-defined Network Policies.
Without RackConnect: Traffic is routed out through the Internet when connecting from Dedicated to Cloud.
With RackConnect: Traffic is routed via your Dedicated Network Device to the Cloud. RackConnect automation keeps your dedicated configuration and Cloud Servers secure.
© 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