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

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

SNA Concepts C-7
C
as IBM Token Ring and Ethernet. PU2.1 nodes can interconnect LUType 6.2-
based applications running on the same system. This is known as an intranode
session.
The following figure illustrates the connection of two PU2.1 nodes over an
SNA transport network. Applications on either the AS/400 or the System/36
can communicate either with applications on the other (peer) machine or with
applications resident on the same (local) machine.
Figure C-3 Peer-to-Peer SNA Physical Components
SNA PU2.1 end node devices connect to a peer-to-peer SNA network through
a data link connection to either another PU2.1 device or to a PU4 or PU5
device. Like hierarchical SNA, peer-to-peer SNA supports data link
connections over telecommunications lines using SDLC, over X.25 PSDNs
using QLLC, and over IBM Token Ring or Ethernet local area networks. Over
SDLC and QLLC, a PU2.1 node acts as a primary, secondary, or negotiable link
station. Over IBM Token Ring or Ethernet, a PU2.1 node acts as a negotiable
link station.
Note – Unlike traditional hierarchical SNA, peer-to-peer connectivity does not
require subordinate operation under a host. However, peer-to-peer
connectivity with a host is defined.
C.2.2 Logical Components
Like hierarchical SNA, logical components of a peer-to-peer SNA network are
NAUs. Each NAU has a unique name in an SNA network. The following figure
illustrates the relationship between the logical components of a peer-to-peer
SNA network.
AS/400
SNA transport
network
System/36