OSI/MHS Configuration and Management Manual

OSI Address Configuration in OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
D-16
Adjacent MTA Address Configuration
loc-nsap-1 3233343232333530303136313031, &
rem-applic-context MTS-TRANSFER
== ***** Add OSI address entries for OUT(D) and IN(S) ******
== In this example the entries defined for IN(D) in "Local
== MR Group Address Configuration" are reused for OUT(S).
ADD ENTRY $zosi.#TSEL.4D4853415431
ADD ENTRY $zosi.#NSAP.333131303432313030303931323036, &
L3PROFILE $zosi.#L3.Carl1, &
L4PROFILE $zosi.#L4.PRFTP0, NETADDR-MODE X25-1980
== The following command also defines <out-s-port>
ADD PROFILE $zosi.#L3.Carl1, &
X25DESTADDR "311042100091206" , X25PORT 01
In this example the ADD MTA command defines local and remote Transport selectors
and NSAPs for the connection to the adjacent MTA. The local addresses define the
value of OUT(S), and the remote addresses define the values of OUT(D) and IN(S).
Local TSEL
In this example, the #TSEL entry for the LOC-TSELECTOR-1 parameter of the ADD
MTA command has already been defined in the local configuration commands, so in
this case, the Transport selector for OUT(S) is the same as for IN(D).
Local NSAP
The #NSAP entry for the LOC-NSAP-1 parameter has also already been defined in the
local address configuration (by the MR-NSAP parameter). This entry defines the
physical network connection which will be used to initiate connections to the adjacent
MTA.
Normally, the LOC-NSAP-n parameter is configured as a hexadecimal representation
of the local X.25 NUA. However, when X.25 1980 is used, this is only a convention,
since LOC-NSAP-n is not used for validation of incoming connections. It can therefore
be configured to any unique value. The configured value has only local significance for
selecting the correct SNPA on outgoing connections.
Remote TSEL
The #TSEL entry for the REM-TSELECTOR-1 parameter of the ADD MTA command is
used only to define this TSEL to the OSI manager. This defines the values of both <in-
s-tsel> and <out-d-tsel>, and no further parameters are required.
Note that <in-s-tsel> is validated against the configured values, and a validation failure
occurs if no match is found.