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

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

Overview 1-21
1
1.11 Peer-to-Peer Operations
The Sun PU2.1 SNA Server supports peer-to-peer operations between a PU2.1
device and either a PU4 or PU5 device or another PU2.1 device, as follows:
•
PU4 or PU5 device - The physical connection between the PU2.1 device and
a PU4 or PU5 device, such as a 3745 communications controller or an
ES/9000 mainframe, can be through any of the supported connection types.
For more information, refer to Section 1.4, “Connection Types,” on page 1-8.
For SDLC and QLLC connections, the local link station can assume a
primary, secondary, or negotiable role. Note that in traditional SNA
networks, only the secondary role is supported.
PU2.1 devices connect directly to VTAM in a PU5 device.
When using the Network Control Program (NCP), peripheral node Type2.1
support is included in Version 4, Release 3. You do not have to define the
traditional NCP parameters, such as
DATMODE
,
MAXDATA
,
MAXOUT
,
MODULO
,
and
PASSLIM
, since this information is conveyed on the XID. You should,
however, set
PUTYPE=2
and
XID=YES
in the NCP PU macro definition.
•
PU2.1 device - No host configuration is necessary. Information about the
device configuration is conveyed between the two devices, using their XID
exchange. The XID contains information about station identification, role,
modulo, outstanding frames, and maximum frame size.
The Sun PU2.1 SNA Server includes the SunLU6.2 security utility, which
provides both LU6.2-based security and UNIX-based security for peer-to-peer
operations.
For each local LUType 6.2, you can define a list of remote LUType 6.2 users
who are allowed to run TPs on the LU. In addition, you can define a list of
users who are allowed to run TPs on any local LU. When conversation-level
security is required, access security parameters in incoming Attach requests are
verified against this LUType 6.2 user information. If the Sun PU2.1 SNA Server
is configured to perform UNIX-level security, you do not have to specify
LUType 6.2 user passwords because users are verified with UNIX password
security. You can restrict TP access to a subset of the defined LUType 6.2 users.
For more information, refer to Appendix G, “LUType 6.2 Security.”