Working With Virtual Clusters; Adding A Virtual Cluster - Coyote Point Systems Equalizer Installation And Administration Manual

High-performance load-balancing appliance
Table of Contents

Advertisement

Chapter 5: Administering Virtual Clusters

Working with Virtual Clusters

A virtual cluster acts as the network-visible service for a group of servers. You use the
Equalizer Administration Interface to add, configure, and remove virtual clusters.

Adding a Virtual Cluster

To add a new virtual cluster:
1.
Log into the Equalizer Administration interface with edit access.
2.
Select Add Cluster from the Add menu in the main menu bar. The Add Cluster dialog
is displayed in the right frame. You can also display this dialog by viewing the
Equalizer Parameters and selecting Add Cluster from the local menu.
Figure 45 Adding a virtual cluster
3.
Enter the Cluster Name and Address:
Cluster Name
Cluster Address
4.
Select the protocol type for the cluster:
62
The logical name for the cluster. Each cluster must have a unique name that
begins with an alphabetical character, not a numeral. For example, CPImages.
The dotted decimal IP address of the cluster or its fully-qualified domain name
(FQDN). The IP address of the cluster is the external address that clients will use
to connect to the cluster. For example, 199.146.85.0. Specifying cluster
addresses by FQDNs instead of IP addresses enables you to manage changes
to the IP addresses through your locally administered DNS. However, if your
local DNS is down when you start up your Equalizer, your clusters won't be
configured properly.
HTTP—the cluster handles web server requests and can route requests to
particular servers based on the content of the request and various load-balancing
criteria. (Supports Layer 7 load balancing.)
HTTPS—the cluster handles secure web server requests and can route requests to
particular servers based on the content of the request and various load-balancing
criteria. (Supports Layer 7 load balancing.)
Generic TCP—the cluster handles TCP-based requests and can route requests
based on configured load balancing criteria and the IP address and TCP port
number. Load balancing based on the generic connection protocols can be more
efficient, but routing decisions cannot take into account the content of the
request. (Supports Layer 4 load balancing.)
Generic UDP—the cluster handles TCP-based requests and can route requests
based on configured load balancing criteria and the IP address and UDP port
number. Load balancing based on the generic connection protocols can be more
Equalizer Installation and Administration Guide

Advertisement

Table of Contents
loading

Table of Contents