OSI/FTAM Configuration and Management Manual

Planning, Installing, and Configuring Tandem FTAM
OSI/FTAM Configuration and Management Manual—421944-001
3-18
How Configured Information Is Used in Making
FTAM Associations
8. The OSI manager then sends an internal ADD SU request to the local TAPS server
process, using the TAPS subdevice name chosen in step 6. This ADD SU request
includes the name of the TSP process.
The TAPS subdevice corresponds to the responder’s attach and will be displayed as
a responder subdevice in response to SCF commands sent to the responder. (Note
that a responder subdevice is actually a TAPS subdevice.)
9. The TAPS process adds the subdevice and responds to the OSI manager.
10. The OSI manager returns the subdevice name and the OSI address to the responder’s
OSI/AS API.
11. The OSI/AS API, on behalf of the responder, opens the TAPS subdevice and sends a
message, including the OSI address, to perform an attach through that subdevice.
12. TAPS sends an attach register request to the TSP process.
Steps 13 through 15 take place when an F-INITIALIZE indication, specifying the
responder’s configured OSI address as the remote address, comes in from a remote
FTAM system.
13. The indication is sent up from the network through the configured NSP, TSP, and
TAPS processes to the responder. At each layer, it satisfies one of the pending
attaches.
14. The responder verifies the indication and returns a response to the remote system
through the TAPS, TSP, and NSP processes.
15. Unless the ALLOWSU attribute has been set to OFF for this responder, the
responder issues another register request to the OSI manager process to replace the
SU now being used.
Note that if the responder’s TAPS process is restarted for any reason, there will be a
five-minute delay before the responder reissues its attaches and is able to make any
associations. Any attempt to establish an association with the responder within this
five-minute interval will fail, and the responder will issue EMS event message
(operator message) #8, reporting a subdevice access failure:
The status value 2 indicates that the error is not immediately retryable. The error
code -126 indicates that the OSI/AS API failed to establish the association because
of an error detected by the OSI manager process. The error subcode 109 indicates
that the TAPS process was not available.
TANDEM.OSIFTAM.D40 000008
process-name Subdevice Access Failed:
APS Reports: Status=2, Error=-126
Subcode=109