|
|
|
|
The load on the SNAP-IX server increases as more clients are added to the network in the local branch of the bank. The bank invests in a second SNAP-IX server that runs in parallel to the first, as shown in LAN with Two SNAP-IX Servers. Adding a second server enables local load-balancing across the two servers; the second server also provides a hot-backup capability.
As the local network expands, the two servers enable the network to support increased traffic without duplicating all the resources in the network. Also, the number of additional links required to the host is reduced, because all of the clients share the links between the server and the host.
The local branch achieves scalable load balancing by defining LUs on both servers and assigning all of those LUs to one LU pool. The applications on the clients are configured to use an LU from that pool. If no LUs are available on one server, the client automatically uses an LU that is available on the second server.
As more clients are added to the ever-expanding network and the network traffic continues to increase, the bank can add more SNAP-IX servers, all with LUs that are assigned to the existing LU pool. This configuration enables client applications to start using these new LUs without any additional configuration. In this way, the processing power within the network can be expanded as required, without the need for network downtime or the need to reconfigure clients.
This configuration also provides hot backup capability in the network, by using multiple servers in the client/server configuration. If a communication link fails between one of the servers and the host, the restarted application can automatically use an LU from the pool; the LU can reside on any of the remaining connected servers.
|
|
|
 |
|