Notes on batch setup of systems (when controlling the load balancer)

Smart Composer functionality sets only the basic settings (such as virtual server or a real server definition, binding between virtual server port and real server port) of the load balancer. When you set up the system, this information is used as a base for creating a virtual server or a real server in the load balancer. After completing the batch setup of systems, manually perform settings to support a specific network configuration.

For details on APIs and the CLI commands of the load balancer executed by the Smart Composer functionality, see Appendix K CLI commands or APIs of the load balancer executed by the Smart Composer functionality.

Notes on sharing the load balancer

When sharing a single load balancer among different Web systems, you must divide virtual server of the load balancer used in each Web system.

You must take precautions regarding the following definitions in Easy Setup definition file.

• Load balancer definition
  Set the same IP address for the load balancer on each Web system.
  
• Virtual server definition (load balancer definition)
  Set unique virtual server name, virtual server IP address, and port number for each Web system.
  

For ACOS, you must also perform the settings (using Auto Translation functionality) for automatically converting the ports with any of the following 2 configuration conditions are fulfilled.

1. If the port number set to the virtual server or real server is greater than 1023 (when it is not well-known)
2. If the port number of the real server and that of the corresponding virtual server are different
   (Example) If the port number of the virtual server is 80, while that of the casting destination is 8081.
   

Set the auto translation functionality for the load balancer in advance. For details on settings, see the ACOS documentation.

Notes on the load balancer redundancy

In a configuration with redundant load balancers, you must perform settings for connecting to each of the load balancers. Perform the connection settings required for connecting to each of the two load balancers in the lb.properties file. The lb.connect_type of each load balancer must be the same.

The following example illustrates the setting example of lb.properties in case of the configuration with redundant load balancers (AX2000, BS320) used for direct connection using the telnet. In this example, load balancers LB1 and LB2 are used, with the management IPs as "192.168.1.100" and "192.168.1.101" respectively.

lb.list=192.168.1.100,192.168.1.101
 
# Settings for the load balancer LB1 having redundant configuration
lb.enable_passwd.192.168.1.100=adminpw
lb.connect_type.192.168.1.100=telnet
lb.telnet.user.192.168.1.100=user01
lb.telnet.passwd.192.168.1.100=user01pw
lb.telnet.user_prompt.192.168.1.100="AX login: "
lb.telnet.passwd_prompt.192.168.1.100="Password: "
lb.telnet.login_prompt.192.168.1.100=>
 
# Settings for the load balancer LB2 having redundant configuration
lb.enable_passwd.192.168.1.101=adminpw
lb.connect_type.192.168.1.101=telnet
lb.telnet.user.192.168.1.101=user01
lb.telnet.passwd.192.168.1.101=user01pw
lb.telnet.user_prompt.192.168.1.101="AX login: "
lb.telnet.passwd_prompt.192.168.1.101="Password: "
lb.telnet.login_prompt.192.168.1.101=>
 

Note: Set the same value for the portion in bold.

Reference note

When sharing the redundant load balancer among multiple Web systems, set the same IP address in the management-host tag and the redundant-management-host tag in the definition of the load balancer of each Web system.