System StatusPortal Login

Use Cloud Load Balancers with RackConnect

Suggest Edits

Applies to: RackConnect v3.0 and RackConnect v2.0

Because only a highly restricted ServiceNet option is
available for RackConnect v3.0, Cloud Load Balancer traffic is blocked by default. If you do require access to Cloud Load Balancers in your RackConnect v3 environment, contact Rackspace Support, and we can help you enable Cloud Load Balancer use in your RackConnect v3 environment.
For more details about the offerings that are support by RackConnect v3.0 and the differences between RackConnect
v3.0 and v2.0, see the following articles:

Note: The rest of this article applies only to RackConnect v2.0.

Configure RackConnect v2.0 to allow cloud load balancer traffic

To configure RackConnect to allow cloud load balancer traffic to your
cloud servers, you must create a Dedicated to Cloud Servers network policy in
RackConnect.

  1. Log in to RackConnect Management Interface.

  2. On the Network Policies tab, add a new policy.

  3. Set Access Scenario to Dedicated to Cloud Servers.

  4. Set the Source Type to Network.

  5. Use the appropriate 10.nnn.nnn.nnn/nn network as the
    Source Server Network:

    • DFW region:

      10.189.254.0/24
10.189.252.0/24
10.183.248.0/24
10.187.186.0/24
10.187.187.0/26
10.183.250.0/24
10.187.187.0/26

    • IAD region:

      10.187.191.0/24
10.189.255.0/24
10.187.186.0/24
10.189.254.0/24

    • ORD region:

      10.183.253.0/24
10.183.250.0/24
10.189.246.0/24
10.187.187.0/24
10.187.186.0/24
10.183.252.0/24
10.189.245.0/24
10.183.251.0/24

    • LON region:

      10.187.191.0/24
10.190.254.0/24
10.189.246.0/24
10.190.255.0/24
10.187.190.0/24
10.189.247.0/24

    • SYD region:

      10.189.254.0/24

    • HKG region:

      10.189.254.0/23

  6. Set the Destination Type, Destination Protocol, and Destination Port or Port Range to specify the resources that the load balancer will access.

  7. Click Create Rule.

More details about using cloud load balancers with RackConnect

Cloud load balancers work 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 need to be load balanced together, then you
should deploy RackConnect with a F5 load balancer instead. The firewall
used with RackConnect serves to further isolate and protect your
dedicated servers.

Following is a normal use case for using cloud load balancers with
RackConnect:

  • 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, and RackConnect provides connectivity from the web servers
to the dedicated database servers. When you use cloud load balancers
with RackConnect, all internet traffic travels through the cloud, and
you pay for all outbound bandwidth at the standard Cloud Load Balancers
rate. This bandwidth is not included in the bandwidth that comes with
each dedicated server.

Important: When using Cloud Load Balancers and RackConnect together,
you 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 address accessible on the public
Internet). In this scenario, your dedicated edge network device cannot
protect your cloud load balancer connections. If this is a concern, then
you can deploy RackConnect with a F5 load balancer.

To reiterate, RackConnect cannot be used to balance traffic between
cloud and dedicated servers, or to protect your inbound cloud load
balancer Internet connections.

The following image shows some use cases that further illustrate the
limitations of using cloud load balancers:

Updated 4 months ago