OSI/FTAM Configuration and Management Manual

Introduction to Tandem FTAM
OSI/FTAM Configuration and Management Manual—421944-001
1-13
Subsystem Interdependencies
Subsystem Interdependencies
For Tandem FTAM to communicate across an OSI network, the following entities must
be fully configured and running:
•
OSI manager process and MIB
•
TLAM (or PAM for G-series) or X25AM subsystem, or both
•
OSI/TS subsystem
•
OSI/AS subsystem
•
APLMGR subsystem
•
FTAM subsystem
To communicate with remote computer systems, your APLMGR subsystem
configuration must specify the Guardian name of the OSI manager process managing
the OSI/AS, OSI/TS, and TLAM (or PAM), X25AM, or TCP/IP subsystems that will
provide the underlying services for your Tandem FTAM processes. In addition, your
OSI/AS subsystem configuration must include the common names and/or addresses
used to configure local FTAM initiator and responder processes, and also the common
names and/or addresses of remote responders with which your Tandem FTAM
applications communicate. For more information on this procedure, see Section 3,
Planning, Installing, and Configuring Tandem FTAM.
Tandem Hardware and Software Environment
This subsection discusses the Tandem hardware and software environments necessary to
configure Tandem FTAM on a Tandem computer system. For a detailed description of
the hardware and software necessary to configure OSI/AS, OSI/TS, TLAM (or PAM),
and X25AM, see the OSI/AS Configuration and Management Manual. For a detailed
description of the hardware and software necessary to configure NonStop TCP/IP, see
the TCP/IP Configuration and Management Manual.
Hardware Requirements
The Tandem FTAM software runs on Tandem systems that use the Tandem NonStop
Kernel operating system. Tandem FTAM requires one or more hardware
communications-controller boards to control physical lines into communications
subnetworks. Tandem FTAM uses standard Tandem communications controllers through
OSI/AS, OSI/TS, and TLAM (or PAM), X25AM, or TCP/IP to implement subnetwork
protocols. Table 1-1 on page 1-14 lists the communications controllers required for each
protocol/interface, where xx indicates the appropriate controller in a family of
controllers (3600, 5700, 6100, or 6200).
Note. All processes within each Tandem FTAM system (APLMGR processes and FTAM
initiator and responder processes), the user applications for that Tandem FTAM system, and
the related OSI/AS subsystem must run on the same Expand node. Each Expand node may
have a Tandem FTAM system. A responder process can access files only on its local node.