OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-22
Problem Examples
The accepting RTS generates a rejection in response to the connection request. It
fails validation. Validation involves the checking of the credentials (passwords) and
other attributes such as the remote OSI address (in particular REM-NSAP-n values).
Compare the MTA attributes of the initiator (MTA 1), as defined to the responder (MTA
2), with the calling address attributes in the association request:
-> info mta $zk2.#mta1,detail
MHS Detailed info MTA MTA1
*Password-server.. OFF
*Logon-validation. ON
*Applicn-context.. MTS-TRANSFER
*Dialogue-mode.... MONOLOGUE
*Max-msg-length... 0
*Local-init....... ON
*Remote-init...... ON
*Rem-P-SELECTOR-1.
*Rem-S-SELECTOR-1. 4B5353454C3141
*Rem-T-SELECTOR-1. 51
*Rem-NSAP-1....... 59
*Loc-P-SELECTOR-1.
*Loc-S-SELECTOR-1. 4B5353454C3241
*Loc-T-SELECTOR-1. 52
*Loc-NSAP-1....... 52
*X121-Country-name
*Country-name.....
*Our-Passw........ MTA1
*Their-Passw...... MTA2
*Our-Passw-Rsp....
*Their-Passw-Rsp..
*Abs-syntax-id.... ID-AS-MTA-RTSE
Rem-MTA-name..... MTA1
ISO-Country-name. US
Remote-ADMD...... POSTMASTER1
Remote-PRMD...... DEVELOPMENT
A comparison of these attributes with the values in the open request shows that the
REM-NSAP-1 address is incorrect. According to the MTA 1 object, the REM-NSAP-1
address is 59, but the value of the calling NSAP address from the RTS trace (record
5 BAD_TURN validation failure Initial turn is not owned by
initiator.
6 NOT_ALLOWED_TO_OPEN rts busy This MTA is not configured for
incoming associations
(REMOTE-INIT off).
7 NO_MORE_ALLOWED rts busy Maximum number of
associations reached for RTS.
8 BUSY rts busy The RTS process has reached
an internal threshold and is
not able to support another
association.
Table 9-5. RTS Refusal Code Mapping (page2of2)
No. Internal Name
CCITT RTSE
(Refuse reason) Meaning