SNAX/APC Configuration and Management Manual

Configuring Network Resources for SNAX/APC
SNAX/APC Configuration and Management Manual—138787
4-27
Configuring a Partner LU
A Single-Session LU
Upon receipt of an unsolicited BIND request, a PTNR-LU and a PTNR-MODE objects
will be added to the local LU with the following attribute values:
PTNR-LU
Object name = $<apc-process>.<local-LU>.PLU-name
SNANAME = fully qualified PLU name
Peripheral-Node = NO
Parallel-Session-LU = NO
PTNR-MODE
Object name = $<apc-process>.<local-LU>.<PLU-name>.Mode-name
ModeName = mode name extracted from the BIND image
DefaultMaxSession = 1
DefaultMinConWinner = 1
DefaultMinConLoser = 0
MaxAutoact = 0
RcvWindow = 3
SendWindow = 3
DefaultMaxInRUSize = process MAXINRUSIZE
DefaultMaxOutRUSize = process MAXOUTRUSIZE
Both of these objects will be brought up to the STARTED state, and the BIND request
will then be processed. These two objects will be automatically brought down to the
STOPPED state and deleted from the local LU’s configuration after the session is
terminated.
A Parallel-Session LU
Upon receipt of an unsolicited BIND request, the SNAX/APC process will first perform
a validation on the mode name specified in the BIND image.
Because SNASVCMG sessions have to be established for CNOS operation before any
other PTNR-MODEs can start initiating sessions, the first unsolicited BIND request
ought to be coming from the SNASVCMG of the remote LU. Therefore, if the mode
name specified in the BIND image is not SNASVCMG, the BIND request will be
rejected with a sense data indicating session limit exceeded (x08050000). If the mode
name matches SNASVCMG, the following dynamic objects will be automatically added
to the local LU:
PTNR-LU
Object name = $<apc-process>.<local-LU>.PLU-name
SNANAME = fully qualified PLU name
Peripheral-Node = YES
Parallel-Session-LU = YES
In addition, all of the SNA-defined PTNR-MODEs discussed in SNA-defined Mode
Names on page 4-19 will be added to the PTNR-LU.