OSI/FTAM Configuration and Management Manual

Planning, Installing, and Configuring Tandem FTAM
OSI/FTAM Configuration and Management Manual—421944-001
3-43
Installing the Basic Components
Configuring the OSI/AS Subsystem for FTAM
Once the OSI/AS, OSI/TS, and TLAM, X25AM, PAM, or TCP/IP subsystems are
running, configure the OSI/AS subsystem to communicate with Tandem FTAM. The
OSI/AS Configuration and Management Manual explains how to configure OSI/AS.
However, a valid OSI/AS configuration must meet some additional requirements to
work properly with Tandem FTAM:
•
The OSI manager process name specified in the OSI/AS configuration must be the
same as the OSI manager process name (OMGRNAME attribute value) configured
for the Tandem FTAM subsystem by using the ALTER SUBSYS command.
•
Define an OSI address in the OSI manager MIB for each FTAM common name that
will be used by local initiator or responder processes. You do this by adding an
APPL ENTRY object to your OSI/AS configuration for each address, as follows:
°
Define an OSI/AS application name (through an APPL ENTRY object) to match
each FTAM common name that your application specifies in the local-appl
parameter to an FTM_INITIALIZE_REQ_ procedure call.
°
Define an OSI/AS application name (through an APPL ENTRY object) to match
the FTAM common name configured for each initiator. (The configured
common name is used, by default, whenever the application does not specify a
common name or address in the FTM_INITIALIZE_REQ_ call.)
°
Define an OSI/AS application name (through an APPL ENTRY object) to match
the FTAM common name in each VFS profile used by one or more responders.
Similarly, if you choose to use OSI addresses instead of common names (this is not
recommended), you must define these to match the initiator and responder addresses
defined to FTAM.
Further, for every local APPL ENTRY object, OSI/AS also requires you to define
underlying entries in the OSI manager MIB. You must define the NSAP and TSEL
entries referenced in each APPL ENTRY object and the SNPA ENTRY object
referenced in each NSAP ENTRY object. (Alternatively, you can specify the NSAP and
TSEL address components directly in the APPL ENTRY objects; however, you must
always specify the SNPA in an SNPA ENTRY object.)
In addition, if the remote entity requires SSEL or PSEL address components, you must
specify these in each APPL ENTRY object. You must also define all Layer 3, Layer 4,
and Layer 5 profiles referenced in ENTRY objects.
•
Define an OSI address in the OSI manager MIB for each remote responder with
which your local initiator processes communicate. If you use common names or if
the remote entity requires specification of PSELs or SSELs, you must do this
through an APPL ENTRY object.
For remote APPL ENTRY objects, you do not need to define underlying ENTRY
objects.
•
The Layer 5 SERVICE object or the Layer 5 profiles you use must specify use of
session version 2, with session version 1 off. (Tandem FTAM requires the use of
session version 2.)