OSI/FTAM Configuration and Management Manual

Planning, Installing, and Configuring Tandem FTAM
OSI/FTAM Configuration and Management Manual—421944-001
3-17
How Configured Information Is Used in Making
FTAM Associations
The following steps occur when Tandem FTAM is started:
1. A system operator or command file sends the APLMGR process an SCF START
command to start the responder.
2. The APLMGR process retrieves information from its MIB as follows
3. The APLMGR process starts the responder and sends it the retrieved information.
4. The responder issues n attach register requests to the OSI manager process named in
the PROFILE configuration, where n is the configured MAXATTACH value for the
responder. After issuing each attach, the responder adds a subdevice to service the
attach.
Steps 5 through 12 are then performed once for each attach:
5. The OSI manager retrieves information from its MIB as follows
6. 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.
7. The TSP process builds a TSP subdevice name from the TAPS subdevice name,
adds the TSP subdevice, and responds to the OSI manager.
Using This Item...
The APLMGR Process
Selects This MIB Entry... and Extracts This Information...
Internal responder
name in START
command
PROCESS NAME (Guardian process name),
PROFILE (VFS profile name),
MAXATTACH, and other attributes
PROFILE attribute PROFILE OSI manager process name, and
common name and/or OSI address
(PSEL, SSEL, TSEL, and NSAP)
Using This
Item...
The OSI Manager Process
Selects This MIB Entry... And Extracts This Information...
COMNAME
from APLMGR
MIB (if
present)
∗
APPL ENTRY OSI address (PSEL, SSEL, TSEL, and
NSAP)
TSEL TSEL ENTRY TAPS server process
NSAP NSAP ENTRY TSP server process and SNPA
SNPA SNPA ENTRY NSP server process
* 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.