OSI/MHS Configuration and Management Manual

OSI Address Configuration in OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
D-9
Configuring the Remote Addresses
The example below illustrates some of the commands needed to define IN(D). An
example of a complete set of commands appears in Putting It All Together on
page D-11. This list is only an indication of the main commands that are used:
ADD GROUP #MR.<mr-group-name>, ... &
MR-T-SELECTOR <in-d-tsel>, &
MR-NSAP <in-d-nsap>
ADD ENTRY #TSEL.<in-d-tsel>, PROFILE ..., SERVER ...
ADD ENTRY #NSAP.<in-d-nsap>, L4PROFILE ..., SERVER ...,&
SNPA ...
The second local address, OUT(S), is configured in the ADD MTA command. It defines
the source address that will be used in outgoing associations from our local MTA.
The configuration of OUT(S) has an additional complication compared to IN(D). It is
defined in the LOC- address parameters of the ADD MTA command and the
associated OSI stack commands. In some cases, the REM-NSAP parameter of the
ADD MTA command and its associated stack commands also contribute to the
address, as described below. Here are the main commands and parameters used to
define OUT(S):
ADD MTA #<mta-name>, ... &
LOC-TSELECTOR1 <out-s-tsel>, &
LOC-NSAP1 <out-s-nsap>, &
REM-NSAP1 <out-d-nsap>
ADD ENTRY #TSEL.<out-s-tsel>, PROFILE ...
ADD ENTRY #NSAP.<out-s-nsap>, L4PROFILE ..., SNPA ...
ADD ENTRY #NSAP.<out-d-nsap>, L4PROFILE ..., L3PROFILE ...
Additional OUT(S) addresses can be configured using LOC-TSELECTOR2, and so on.
In many cases, <out-s-tsel> will be the same as <in-d-tsel>, and <out-s-nsap> will be
the same as <in-d-nsap>. The first two ADD ENTRY commands in the list above will
then be the same as those used to define IN(D) and should therefore not be repeated.
<out-d-nsap> is involved in the production of OUT(S) if the underlying connection uses
the 1980 version of X.25. The reason is that, when the NSAP address is mapped to
the X.25 NUA, the calling address in an outgoing X.25 call request packet contains a
subaddress defined by the X25PORT parameter of the #L3 profile for that call.
Because the #L3 profile is defined by the REM-NSAP for the connection, together with
its associated #NSAP entry, it follows that the calling subaddress is defined by the
REM-NSAP for the MTA. If this fact is not understood, it can result in configuration
problems that cause associations to be rejected because of validation failures.
Configuring the Remote Addresses
The remote addresses consist of the OUT(D) and IN(S) addresses. (OUT(R) is not
validated and so does not have to be configured.)