OSI/FTAM Configuration and Management Manual

Planning, Installing, and Configuring Tandem FTAM

OSI/FTAM Configuration and Management Manual—421944-001

3-6

Configuration Information in the OSI Manager MIB

This subsection provides basic information on configuring OSI addresses, processes,

and protocols in the OSI manager MIB for use by Tandem FTAM initiators and

responders. The configuration of OSI/AS subsystem objects in the OSI manager MIB,

through OSI/AS SCF commands, takes care of the following functions:

•

Setting up OSI addressing relationships

•

Configuring the architecture of the OSI/AS subsystem and underlying subsystems

(TAPS, TSP, and NSP processes)

•

Setting protocol attributes for the underlying OSI layers

The types of OSI/AS objects configured in the OSI manager MIB are ENTRY,

PROCESS, PROFILE, and SERVICE objects.

OSI Addresses

A Tandem FTAM initiator communicates with a remote FTAM responder by referring to

its own local OSI address and to the remote OSI address of the responder. A remote

FTAM initiator communicates with a local Tandem FTAM responder by referring to the

also must be configured in the APLMGR MIB.

In the Tandem OSI architecture, the components of the local addresses allow the OSI/AS

subsystem to identify particular underlying TAPS, TSP, and NSP processes for servicing

requests, and to identify the protocol characteristics of the underlying connections at the

various OSI layers.

An OSI address consists of four components: presentation selector (PSEL), session

selector (SSEL), transport selector (TSEL), and network service access point (NSAP).

Since TAPS processes provide ACSE, session, and presentation services, the local PSEL

and SSEL address components can usually be chosen arbitrarily. Each local TSEL is

associated with a particular TAPS process, and each local NSAP is associated with a

particular TSP process.

Note. Tandem FTAM does not cross-check the validity or consistency of the addressing

information in your FTAM and OSI/AS configurations. Many OSI/AS configuration errors cannot

be detected by the software until an FTAM association is attempted using the affected

addresses. Check your OSI/AS configuration carefully.