OSI/FTAM Configuration and Management Manual

Planning, Installing, and Configuring Tandem FTAM
OSI/FTAM Configuration and Management Manual—421944-001
3-10
Configuration Information in the OSI Manager MIB
Addressing of Tandem Responders
All FTAM associations with a particular responder process use the common name or
OSI address configured for that responder through its VFS profile. VFS profiles, which
can be shared by several responders, allow multiple responders to share the same
common name (that is, the same OSI address).
One advantage of sharing profiles is load distribution. When OSI/AS receives a request
from a remote system, it receives an OSI address from that system. If there is only one
responder corresponding to that address, OSI/AS sends the request to the responder, and
any additional requests using that OSI address are kept pending until the responder can
take on new requests. If there are multiple responders associated with one OSI address,
OSI/AS distributes the connection requests sequentially among the available responders;
requests are matched with the first available attach for any responder. In this way, the
association requests are shared among the responders that share the profile. Responder
capacity at one OSI address can be increased by adding more responders that have the
same profile.
PROCESS and ENTRY Objects
The OSI manager MIB contains PROCESS objects that specify the characteristics of
TAPS, TSP, and NSP server processes, and ENTRY objects that tie components of a
local OSI address to specific processes. A local TSEL ENTRY object associates a TSEL
with a TAPS process; a local NSAP ENTRY object associates an NSAP with a TSP
process and a subnetwork point of attachment (SNPA), and a local SNPA ENTRY object
associates an SNPA with an NSP process. When a local application requests an FTAM
association, the OSI manager process uses these ENTRY objects to select the TAPS
process, TSP process, and NSP process to service all requests over that association. Any
combination of an NSP process, a TSP process, and a TAPS process within one OSI/AS
subsystem can be bound together in this way to service an association.
SERVICE and PROFILE Objects
The OSI manager MIB also contains SERVICE objects and, optionally, PROFILE
objects that specify characteristics of the connections to be used for outgoing requests at
the various OSI layers. PROFILE objects are tied to specific OSI address components.
SERVICE objects provide default values to be used at a given layer when no PROFILE
object is configured for the specified address. For example, you can use the Layer 3
SERVICE object or a Layer 3 PROFILE object to select the X.25 PVC channel (port)
number, and the Layer 4 SERVICE object or a Layer 4 PROFILE object to select the
transport protocol class. SERVICE objects are provided for ACSE, Layer 6, Layer 5,
Layer 4, and Layer 3. You can specify PROFILE objects for Layers 5, 4, and 3.