Sun Microsystems SunLink SNA 9.1 PU2.1, Configuration Manual

Page: 230 / 298

B-4 SunLink SNA 9.1 PU2.1 Server Configuration Guide—August 1997
B
•
Resource selection - The client specifies the name of the physical unit (PU),
logical unit (LU), or LU pool it wants to access. The Sun Name Server
directs the client to the system that contains the resource.
For example, the following figure illustrates a company,
acme
, that has built
a gateway and configured a subdomain,
sna
, to administer the Sun PU2.1
SNA Server name space. The resources include an LU (
LU010A
) and an LU
pool (
TSOPOOL
).
Figure B-2 Sun SNA Subdomain
If a client in the
acme
domain wants to connect to
LU010A
, the client specifies
the name
LU010A.sna
. If the client wants to connect to an LU in
TSOPOOL
,
the client specifies the name
TSOPOOL.sna
. Note that if a client in the
widget
domain specifies the name
TSOPOOL.sna
, the
corp
DNS will fail to resolve
the name request and will refer the request to its parent domain,
acme
.
•
User mapping
- The client specifies its user name. The Sun Name Server
maps the user by name to the default resource defined in the user
configuration and directs the client to the system that contains that resource.
User mapping allows users to indicate who they are rather than what
resource they want to access. For example, if a user specifies
jdaniels.sna
,
the Sun Name Server maps the user to the configured default resource.
Whether the client uses resource selection or user mapping, the Sun Name
Server resolves the name request, selects a host to service the connection, and
then sends the IP address of the host to the client. When the client receives the
name resolution, the client sends its open request to the resolved address.
root
com
acme
sna
corp
widget
sna resources