OSI/MHS Configuration and Management Manual

OSI Address Configuration in OSI/MHS
OSI/MHS Configuration and Management Manual424827-003
D-15
Adjacent MTA Address Configuration
networks, the #SNPA entry also defines a #L3 profile, which can be used to specify
various parameters for incoming connections to the X.25 network layer.
The #L3 profile defines a port number, which will be used to listen for incoming X.25
calls. It can also include such parameters as whether packet-size negotiation or
reverse charging are allowed.
These commands together define IN(D) for incoming connections as follows:
IN(D): t-selector = 313131
X.25 NUA = 23422350016101
Note that the value configured for the NSAP address is not significant for 1980 X.25,
because the local NSAP addresses (<in-d-nsap> and <out-s-nsap>) are used only to
link to the values configured for the X.25 SRCADDR and port numbers.
In the example, the value used for <in-d-nsap> is, in fact, a hexadecimal
representation of local-nua concatenated with <in-d-port>. This is merely a convention,
and any unique value of <in-d-nsap> could have been used, because no address
validation is carried out against the values defined in the ADD GROUP #MR command.
The other local addresses, the OUT(S) addresses, have not yet been defined.
Adjacent MTA Address Configuration
An OSI stack is added for an adjacent MTA as follows:
== ***************** Add adjacent MTA ********************
ADD MTA $zmhs.#Carl, &
rem-mta-name TANDEMMTAA, &
rem-dialogue-mode MONOLOGUE, &
iso-country-name US, &
rem-admd ATTMAIL, &
rem-logon-validation ON, &
rem-our-passw MYPW, &
rem-their-passw BOFF, &
rem-prmd TANDEMPRMD, &
rem-local-init ON, &
rem-remote-init ON, &
rem-max-msg-len 2097152, &
rem-pselector-1, &
rem-sselector-1, &
rem-tselector-1 4D4853415431, &
rem-nsap-1 333131303432313030303931323036, &
loc-pselector-1, &
loc-sselector-1, &
loc-tselector-1 313131, &