Technical data

Using DNS to Balance Work Load
6.5 Configuring the Load Broker
cluster "www.tcpip.ern.sea.com"
{
dns-ttl 45;
dns-refresh 30;
masters {
9.20.208.53;
};
polling-interval 9;
max-members 3;
members {
9.20.208.100;
9.20.208.53;
9.20.208.54;
9.20.208.80;
9.20.208.129;
9.20.208.130;
};
failover 16.20.208.200;
};
To retain your UCX Version 4.x DNS cluster load-balancing configuration:
1. Enter the CONVERT/CONFIGURATION BIND/CLUSTER command, as
shown in the following example:
TCPIP> CONVERT/CONFIGURATION BIND -
_TCPIP> /CLUSTER=SYS$SYSDEVICE:[TCPIP$LD_BKR]TCPIP$LBROKER.CONF
The output from this command is a TCPIP$LBROKER.CONF file containing
your basic configuration.
2. Edit the TCPIP$LBROKER.CONF file to produce a complete configuration
file.
6.5.1 Enabling the Load Broker
To enable DNS cluster load balancing, complete the following tasks:
1. Ensure that all hosts in the DNS cluster are running TCP/IP Services.
2. Configure the load broker (see Section 6.5).
3. Configure the BIND name server that is authoritative for the DNS cluster to
allow dynamic updates from the host on which the load broker is running.
For how to configure dynamic updates, see Section 5.3.6.
4. Ensure TCP/IP connectivity between the DNS cluster members and the load
broker.
5. Enable the metric server on each member of the DNS cluster:
a. Run the following command procedure:
$ @SYS$MANAGER:TCPIP$CONFIG
b. On the TCPIP$CONFIG Server Components Configuration menu, select
option 8:
8 -- METRIC.
c. On the Metric configuration display, select option 2:
2 -- Start service on this node.
Review the following guidelines:
• DNS cluster hosts and clients are not required to be on the same bridged
LAN.
Using DNS to Balance Work Load 6–7