| |
|
 |
TriLoad Balancer uses
three forward technologies
to support different network topologies |
|
| |
|
|
| |
Solution
 Direct Routing
| In this configuration, client, Load Balancer and Real Servers are at the same physical network segment, as well as the VIP (Virtual IP). Real Servers run Windows 2000 Server, with IIS listening at port 80. To verify the dispatching result, each real server has a file named ip.txt under web root, containing its real IP address. The Load Balancer will forward all requests from client to real servers using direct routing. |
 |
| Configuration of Load Balancer: |
- Sets real IP address to 192.168.0.100, net mask 255.255.255.0
- Adds virtual IP 192.168.0.10
- Adds Direct Routing service to VIP 192.168.0.10 with port 80
- Adds two real servers 192.168.0.201 and 192.168.0.202 to the service
|
Configuration of Real Server (take 192.168.0.201 as example) |
- Sets real IP address to 192.168.0.201, net mask 255.255.255.0
- Adds MS Loopback Network Interface, sets its address to 192.168.0.10 with net mask 255.255.255.252
|
| To verify the configuration, you can access URL http://192.168.0.10/ip.txt at client machine. Because normal browsers will cache the result, it is better to verify the result using tool telnet. In command line, type telnet 192.168.0.10 80, then GET /ip.txt HTTP/1.0<cr><cr> to simulate the HTTP protocol to get the HTTP response from server. You can also log into TriLoad Admin console at http://192.168.0.100:8080/, in Status page you can check the server statistics. |
Note: You can access http://192.168.0.100:8080 to config your load balancer |
Network Address Translation
| In this configuration, client, Load Balancer and Real Servers are at the same physical network segment, as well as the VIP (Virtual IP). Real Servers are running Windows 2000 Server, with IIS listening at port 80. To verify the dispatcher result, each real server has a file named ip.txt under web root, containing its real IP address. The Load Balancer will forward all requests from client to real servers using Network Address Translation. |
 |
| Configuration of Load Balancer: |
- Sets real IP address to 192.168.0.100, net mask 255.255.255.0
- Adds virtual IP 192.168.0.10
- Adds NAT service to VIP 192.168.0.10 with port 80
- Adds two real servers 192.168.0.201 and 192.168.0.202 to the service
|
Configuration of Real Server (take 192.168.0.201 as example) |
- Sets real IP address to 192.168.0.201, net mask 255.255.255.0
- Adds routing rule to force the real server use Load Balancer for all responses back to clients, even the client is at the same network: route add 192.168.0.0 mask 255.255.255.0 192.168.0.100
|
To verify the configuration, you can access URL http://192.168.0.10/ip.txt at client machine. Because normal browsers will cache the result, it is better to verify the result using tool telnet. In command line, type telnet 192.168.0.10 80, then GET /ip.txt HTTP/1.0<cr><cr> to simulate the HTTP protocol to get the HTTP response from server. You can also log into TriLoad Admin console at http://192.168.0.100:8080/, in Status page you can check the server statistics. |
| Note: You can access http://192.168.0.100:8080 to config your load balancer |
|
|
