OSI/MHS Configuration and Management Manual

OSI Address Configuration in OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
D-10
Configuring the Remote Addresses
OUT(D) is defined in the OSI stack commands associated with the REM-address
parameters of the ADD MTA command, as shown in the following list:
ADD MTA #<mta-name>, ... &
REM-TSELECTOR1 <out-d-tsel>, &
REM-NSAP1 <out-d-nsap>
ADD ENTRY #TSEL.<out-d-tsel>
ADD ENTRY #NSAP.<out-d-nsap>, L4PROFILE, L3PROFILE ...
The ADD ENTRY #NSAP command is the same command used in the definition of
OUT(S), above. In this sense, this command is used in the production of both the
outgoing calling NSAP and the outgoing called NSAP (X.25 1980 only).
IN(S) is defined in the REM- address parameters of the ADD MTA command, as
follows:
ADD MTA #<mta-name>, ... &
.. REM-TSELECTOR1 <in-s-tsel>, &
REM-NSAP1 <in-s-nsap>
ADD ENTRY #TSEL.<in-s-tsel>
ADD ENTRY #NSAP.<in-s-nsap>, L4PROFILE, L3PROFILE...
These commands are the same ones that were used for OUT(D) above. It follows that
<out-d-tsel> must have the same value as <in-s-tsel>. The only way to achieve
different values for these two addresses is to configure two REM-TSELECTOR
addresses for the MTA: REM-TSELECTOR1 and REM-TSELECTOR2.
The same consideration applies to the <out-d-nsap> and the <in-s-nsap>, except that if
the 1980 version of X.25 is used, there is a way to define different values for these two
addresses without defining multiple REM-NSAP addresses. This option will be
described later.
Note. IN(S) is used for security checking to validate the identity of the adjacent MTA.
Note. There is no way to prevent OSI/MHS from attempting to use a value configured for <in-
s-tsel> as if it were an <out-d-tsel> address other than to define a separate MTA object for
each address. The parameter REM-LOCAL-INIT, which can prevent OSI/MHS from opening
an association with an adjacent MTA, applies to all links with that MTA object.