Create a load balancing configuration

When you create a load balancing version, you set the load balancing type and configure data centers and liveness tests.

How to

  1. Go to > CDN > Edge logic Cloudlets.
  2. On the main Cloudlets Policy Manager screen, select the Manage Load Balancing Setup tab.
  3. Click Create New Load Balancing Setup.
  4. Enter a unique load balancing ID using alphanumeric characters and underscores, and add a note describing the configuration.
  5. Click Create Load Balancing Setup.
    Version 1 of the load balancing configuration displays on the Load Balancing Version Details screen.
  6. Complete these fields:
    Field Entry
    Version Notes Enter a description of how this particular configuration version differs from others.
    Balancing Type Select the type of load balancing to use, which is either Weighted or Performance.

    Weighted load balancing routes requests to live data centers exactly in the proportion configured.

    Performance load balancing dynamically determines which route to use based on real-time load feedback and the shortest geographic route to the origin data center.

    Note: If a data center fails, the system automatically fails over to another data center.
    Enable Liveness Test Select to enable liveness testing for your load balancing configuration
  7. Click Add Data Center and select a data center from the dropdown.
  8. Complete the following data center fields:
    Field Entry
    Percent Traffic Enter the percent of traffic that will be sent to the data center. The total for all data centers listed must equal 100%.

    The total for all data centers is automatically set to 100%.

    For example, if you add a data center and assign it 80% of the traffic, the next data center you add will automatically be set to 20%. If you then add a third data center, it will automatically be set to 0%. You will have to manually adjust this field across all data centers to get your desired traffic percentages.

    Is a Cloud Service If selected, caching for the data center is updated at a certain interval. This is how caching works for cloud-based services, like AWS.

    If enabled, caching will occur at shortened intervals, as IP addresses used with cloud services can change.

    Data Center Location Start typing the country and city where your data center is located. Once you select the country and city, the system autopopulates the latitude and longitude.

    If your city doesn't appear in the dropdown after typing it, manually add the latitude and longitude.

    Liveness Servers If you enable liveness tests, enter the IP addresses or hostnames that are pinged by the liveness checks.
  9. Add and configure additional data centers until they're all configured.
  10. If you enabled the liveness test, complete these fields:
    Field Entry
    Protocol The protocol or scheme for the database, either HTTP or HTTPS.
    Port The port for the test object. The default port is 80 which is standard for HTTP. For HTTPS, enter 443.
    Test Interval (sec) How often the liveness test occurs in seconds. The default is 60 seconds, and a minimum of 10 seconds is required.
    Timeout (sec) The number of seconds the system waits before failing the liveness test. The default is 25 seconds.
    Path The path to the test object used for liveness testing. The test object resides on your origin.
    Host Header The value of the Host header needed to support liveness tests. The Host header is the domain name without the protocol/scheme.
    Redirects (3XX) Enable to mark the liveness test as failed when the request returns a 3xx (redirection) status code.
    Client Error (4XX) Enable to mark the liveness test as failed when the request returns a 4xx (client error) status code.
    Server Error (5XX) Enable to mark the liveness test as failed when the request returns a 5xx (server error) status code.
  11. Click Save Load Balancing Version.