OSI/FTAM Configuration and Management Manual

Planning, Installing, and Configuring Tandem FTAM
OSI/FTAM Configuration and Management Manual—421944-001
3-14
How Configured Information Is Used in Making
FTAM Associations
9. The OSI manager retrieves information from its MIB, as shown in the following
table:
10. The OSI manager chooses a TAPS subdevice name and sends an internal ADD SU
request to the local TSP server process using this subdevice name. This ADD SU
request includes the name of the local NSP server process.
11. The TSP process builds a TSP subdevice name from the TAPS subdevice name,
adds the TSP subdevice, and responds to the OSI manager.
12. The OSI manager then sends an internal ADD SU request to the local TAPS server
process using the TAPS subdevice name chosen in step 11. This ADD SU request
includes the name of the TSP process.
13. The TAPS process adds the subdevice and responds to the OSI manager.
14. The OSI manager returns the subdevice name and the local and remote OSI
addresses to the initiator’s OSI/AS API.
Using This Item...
The OSI Manager Process
Selects This MIB Entry...
And Extracts This
Information...
Local common name from
application’s initialize
request or from APLMGR
MIB (if present)
1
Local APPL ENTRY Local OSI address (PSEL,
SSEL, TSEL, and NSAP)
Local TSEL Local TSEL ENTRY Local TAPS server process
and
Layer 5 profile
2
Local NSAP Local NSAP ENTRY Local TSP server process,
local SNPA, and Layer 4
profile
2
Local SNPA Local SNPA ENTRY Local NSP server process
and Layer 3 profile
2
Remote common name from
APLMGR MIB (if present)
1
Remote APPL ENTRY Remote OSI address (PSEL,
SSEL, TSEL, and NSAP)
3
1 If any OSI address components are specified instead of or in addition to a common name, the specified
address components are used directly; no lookup is performed, and any specified common name is ignored.
2 If no profile is present, the attribute values from that layer’s SERVICE object are used on the connection.
3 Remote TSEL, NSAP, and SNPA entries can also be present to specify remote Layer 5, 4, and 3 profiles. If
remote profiles are defined, their attributes take precedence over the attributes in local profiles or SERVICE
objects.