OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-5
Interconnection Problems With Other MTAs
checkpoint and window sizes. When it responds to MTA 1, the RTS process
returns, as the values of checkpoint and window size, either its own preferred
values or those of MTA 1, whichever are lower. The RTS process also checks the
abstract syntax ID to ensure that the abstract syntax can be supported. After
checking these parameters, the RTS process passes the bind request to the MR
process.
7. The MR process checks the remaining parameters in the bind request: if password
exchange is required (REM-LOGON-VALIDATION is ON), the password in the
request must match either the value of REMOTE-THEIR-PASSWD for adjacent
MTA 1 (as defined in MTA 2) or the value provided by an MTA bind password
server if one is in use. The MTA name must match the value of REMOTE-MTA-
NAME for adjacent MTA 1 (as defined in MTA 2), and the calling address
parameters in the request must match an address specified for adjacent MTA 1 in
the configuration of MTA 2. The calling address can match any set of remote
address values specified for MTA 1. The responder does not look at its own local
address values (LOC-SELECTORs) in performing the validation.
8. If the bind request is acceptable to MTA 2, MTA 2 responds to MTA 1 through the
RTS process and the underlying OSI services. If password exchange is required,
the MTA passes the value of REM-OUR-PASSWD-RSP in the response.
9. In MTA 1, the MR group that initiated the association waits for a response. The
MR group receives the response through its RTS process and underlying OSI
services. If password exchange is required, the MR process compares the
password in the response with the value of REM-THEIR-PASSWD-RSP or, if a
password server is in use, requests that the password server perform validation of
the password.
There are several other MR group attributes that affect association establishment:
•
ASSOC-OPEN-TIME. This attribute specifies how long the MR process waits for
the RTS process to make one attempt to open an association. If this value is too
low, association attempts fail.
•
LINK-RETRY-DELAY. This attribute specifies how long the MR process waits, after
having tried all the links to an MTA without success, before trying them all again.
•
LINK-RETRY-TIME. This attribute specifies how long, from the time the first link
was tried, the MR process waits before requesting that the RTS process establish
an association on an alternate route.
•
xxx-ROUTE-RETRY-DELAY and xxx-ROUTE-RETRY-GROW (xxx is either
URGENT, NORMAL, NONURGENT, or REPORT). These attributes specify how
long the MR process waits, after all links on all routes have been tried without
success, before starting again with the first link on the first route.
•
xxx-ROUTE-RETRY-TIME. This attribute specifies how long, from the time a
message arrived in the management domain, the MR process waits before
sending a nondelivery notification. This notification means that OSI/MHS could not
route or deliver the message to its intended recipient. (If the message was a