SNAX/XF and SNAX/APN Configuration and Management Manual

Configuring for Token-Ring Support
SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006
9-18
The HP Implementation
The HP Implementation
Configuration of resources for Token-Ring support must be done using SCF or an SPI
application. To define SNAX/APN Token-Ring resources, additional attributes, modified
attributes, or both for the SCF ADD and ALTER LINE, PU, and LU commands must be
supplied. Most of the parameters are optional and default to an acceptable value. All
the relevant SCF commands are detailed in this section.
Configuring SNAX/APN for Token-Ring
Before starting Token-Ring configuration, you should have performed Tasks 1 through 3 of the
Configuration Quick Start
on page 1-1. In the SNAX/APN Token-Ring implementation,
remote PU objects that are added to lines represent the link stations defined by the
Token-Ring architecture. Additional information is supplied by the ADD PU and ALTER
PU commands to properly support the LLC2 protocols.
SAP information is indirectly supplied by information coming from the ADD LINE,
ALTER LINE, ADD PU, and ALTER PU commands. The ADD PU and ALTER PU
commands are used to indicate which local SAP value a PU should use. (Multiple PUs
can have the same local SAP value.)
The MAC component is not configured by SNAX/APN. This level is controlled by the
ServerNet LAN Systems access (SLSA) process that interfaces directly with the Token-
Ring ServerNet adapter (TRSA).
Use of the TRSA requires the definition of line subtype (4) in the SCF ADD DEVICE
command. For details, see Section 13, SCF Commands for SNAX/XF and SNAX/APN.
The Components of Token-Ring Support
Token-Ring support is provided by use of SCF commands to configure SNAX/APN, in
particular to send information to the service manager and line-handler processes.
SNAX/APN in turn sends configuration information about the SAPs to PAM. PAM
provides NonStop systems with an IEEE 802.2-compliant interface for LAN access.
(802.2 is the LLC layer, previously depicted in Figure 9-6
on page 9-10). PAMMAN is
the programmatic interface for configuration and network management of PAM.
After the link stations are configured and started, SNAX/APN sends PIUs (the actual
data to be transmitted) to PAM, which acts as the access method to the ring. The
ServerNet LAN Systems Access (SLSA) subsystem contains software controls and
code for the Token-Ring ServerNet adapter (TRSA).
These relationships are depicted in Figure 9-12
on page 9-19.