OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-23
Problem Reporting
number 9) is 51. To correct this problem, alter the MTA object with the correct REM-
NSAP-1 value:
-> assume mta $zk2.#mta1
-> alter, rem-nsap-1 51
-> info mta,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....... 51
*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
The change in the value of REM-NSAP-1 takes effect immediately.
Connection problems can also occur when an invalid password or application context
is used. If the password is invalid, the subsystem rejects the association and
generates an event message. You can use the INFO MTA command with the DETAIL
option to display the password for an adjacent MTA, as shown above. If the initiating
and responding MTAs specify different application contexts (MTA attribute APPLICN-
CONTEXT), the association is likewise rejected.
Problem Reporting
If you are sure that the problem is not a configuration error and you wish to report a
connection problem, provide the following information to your HP representative:
•
Description of the environment: in particular, the connection attributes dialogue
mode, checkpoint size, OSI addresses (both remote and local), and the type of
network services used (OSI/AS and OSI/TS; TLAM or PAM, or X25AM; TCP/IP
running over TLAM or X25AM).
•
RTS traces with MHSRTS trace records
•
STATS PROCESS on RTS display from SCF