Sun Microsystems SunLink SNA 9.1 PU2.1, Руководство по настройке

Страница: 38 / 298

1-12 SunLink SNA 9.1 PU2.1 Server Configuration Guide—August 1997
1
•
A group of intermittent users can use limited resources more efficiently. For
example, if 15 users need only intermittent access to five dependent LUs,
you can create an LU pool for these users.
•
By selecting an LU pool, a client or group of clients can ensure that
connections are limited to a known set of dependent LUs.
•
If you want to limit a group of users to a single host and the host is
connected to a particular PU2.1 server, creating an LU pool ensures that any
client software started by these users connects to the correct host.
•
Providing an LU pool separates the resources from the client, allowing
changes to the server without requiring changes to the client configuration.
For more information about creating an LU pool, refer to Section 8.4, “Creating
an LU Pool,” on page 8-9.
1.8 Users and User Groups
The Sun PU2.1 SNA Server allows you to create user records for clients and for
system/network administrators. You can also use a wild-carded fully-qualified
domain name or a masked IP address to specify a group of users (clients or
system/network administrators) that have common requirements without
specifying each user individually.
User records allow you to control the resources to which a client can connect.
You define a list of preferred and alternate default resources in the user record.
If the client does not (or cannot) specify a resource when connecting to the
host, the server tries to connect the client to the preferred default resource. If
the preferred resource is not available, the server sequentially checks the
alternate resources until it finds an available LU. If your LUs are
geographically dispersed, you can use multiple default resources to ensure that
LUs closest to the client are checked first.
You can specify one or more of the following default resources for each client:
•
Dependent LU or independent LU - Allows you to provide a single known
LU for the client connection. In case of problems, you can determine which
LU the client was connected to. For a dependent LU, you can add this user
record to the access list of the LU to restrict the LU to that client connection.
Note –
If you use an LU as the default resource and a system or network
outage occurs, the client may not be connected since the LU is not available.