Sun Microsystems SunLink SNA 9.1 PU2.1, Configuration Manual

Page: 260 / 298

E-2 SunLink SNA 9.1 PU2.1 Server Configuration Guide—August 1997
E
E.2.1 Normal Load Balancing Description
Normal load balancing is simpler to configure and implement than
geographical load balancing and is useful if all clients are in the same
geographical location. However, it requires that each client knows the name of
the resource it wants to connect to or that a unique user record has been
defined for each client. In addition, if the LUs are geographically dispersed, a
client may connect to an LU at a remote location.
An extended TN3270E or sun3270 client can specify both a hostname/port ID
pair and the name of the a resource or user record for connection parameters.
If the client specifies a user record, the server checks the preferred default
resource for available LUs. If none are available, the server sequentially checks
the alternate default resources until it finds an available LU.
A traditional TN3270 client can specify only a hostname/port ID pair for
connection parameters. The server looks for a user record with either an IP
Address parameter or IP Hostname parameter that matches the IP address or
IP hostname of the client. The server checks the preferred default resource
specified in the user record for available LUs. If none are available, the server
sequentially checks the alternate default resources until it finds an available
LU.
E.2.2 Normal Load Balancing Example
The example described in this section assumes that each desktop is configured
so that all TN3270E client connections use the following connection
parameters:
•
Hostname:
foo.sna.sun.com
•
Connection Resource:
foo
The user record specifies the following:
•
Name:
foo
•
Default Resource:
POOL-1 PUBLIC
Refer to the following figure as you follow the procedure.