Using Cloud Load Balancers with RackConnect


To configure RackConnect to allow Cloud Load Balancer traffic to your Cloud Servers, a “Dedicated to Cloud” RackConnect Network Policy will need to be created to allow your Cloud Load Balancer resources to communicate with your Cloud Servers. You can use Cloud Load Balancers with RackConnect by following these steps:

1.  Create a “Dedicated to Cloud” Network Policy.

2.  Set the “Source Type” to Network.

3.  Use the appropriate 10.xxx.xxx.xxx/xx Network listed below as the “Source Server Network”:

  • For the DFW region, use:

    10.183.248.0/22
    10.189.254.0/23

  • For the IAD region, use:

    10.189.254.0/23

  • For the ORD region, use:

    10.183.250.0/23
    10.183.252.0/23
    10.183.254.0/23
    10.189.245.0/24
    10.189.246.0/23

  • For the LON region, use:

    10.189.246.0/23
    10.190.254.0/23

  • For the SYD region, use:

    10.189.254.0/23

  • For the HKG region, use:

    10.189.254.0/23

4.  Set the “Destination Type”, “Destination Protocol”, and “Destination Port or Port Range” to specify the resources that the Cloud Load Balancer will access.

Further details about using Cloud Load Balancers with RackConnect

Cloud Load Balancers works best when all servers to be load balanced reside in the Cloud. If Dedicated Servers need to be load balanced, or Cloud and Dedicated Servers are to be load balanced ''together”, then you should deploy RackConnect with a F5 load balancer. The firewall used with RackConnect serves to further isolate and protect the customers dedicated servers.

Here is a normal use case for using Cloud Load Balancers with RackConnect (Image below):

  • Use Cloud Load Balancers to balance web traffic between Cloud Servers
  • Use RackConnect to provide back-end connectivity to Dedicated Database Servers from your Cloud Servers


In this example, a Cloud Load Balancer balances traffic between Cloud web servers, while RackConnect provides connectivity from the web servers to the Dedicated DB servers.  Note that when using CLB with RackConnect, all internet traffic comes and goes through the Cloud, and the customer will pay for all outbound bandwidth at the standard CLB rate. This bandwidth is not included in the “included” bandwidth that comes with each dedicated server.

IMPORTANT NOTE: When using Cloud Load Balancers and RackConnect together, you will normally have two points of entry into your environment from the Internet: one on your Dedicated side protected by your Dedicated Edge Network Device (ASA or F5), and another on your Cloud side via your Cloud Load Balancer (Virtual IP accessible on the Public Internet). In this scenario, your Dedicated Edge Network Device will be unable to protect your Cloud Load Balancer connections. If this is a concern, then you can deploy RackConnect with a F5 load balancer.


To clarify, RackConnect can NOT be used to balance traffic between Cloud and Dedicated servers, or to protect your CLB Inbound Internet connections:

 


Using Dedicated Load Balancers with RackConnect <---Previous | Next ---> RackConnect Compatibility with First-Gen Cloud Server Images



Was this content helpful?




© 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


See license specifics and DISCLAIMER