OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-17
Problem Examples
Initiator : 1 Turn : 0 Checkpoint size : 1 Window size : 3
Safe store window : 2 Application Protocol : 88 Abstract syntax id : 0
Dialogue mode : 0
Local MTA name : 4D544131
Local Password : 4D544132
Remote MTA name :
Remote Password :
Recovery time : 600 Recovery expiry : 0 Delay time : 60 Delay expiry
: 0 PCD List size : 0 PCID : 0
Current session connection id
User ref : 040751515A4B312030 Common ref :
170D3933303630323139323034355A Add ref : 140135
Activity id :
Initial session connection id :
User reference : Common ref : Add ref :
Activity id :
Activity number : 0
Original session connection id
User reference : 040751515A4B312030 Common ref :
170D3933303630323139323034355A Add ref : 140135
SpTx : 0 SpRx : 0 SpAckTx : 0 SpAckRx : 0
PDU Id= 0 0-0-0-0-0
Offset : 0 Transfer time : 0 Transfer Expiry : 0 Size : 0
Completed flag : 0
Roll back index : 0 Roll back overflow : 0
Trace record number 1 (RT-OPreq) shows that connection establishment has been
attempted. This trace record shows all addresses and RTS-specific information such
as passwords, MTA name, protocol, and connection mode. Trace record number 13
shows that the connection has been rejected. The refusal reason is 2. The context
value (in this case 1129240) shows that the records pertain to the same association.
The refusal reasons for inbound requests are the CCITT RTS refusal reason codes,
listed in Table 9-4.
In the current example, the connection fails because the RT-OPreq request is refused
by the adjacent MTA. To solve this problem, we must examine the adjacent MTA
(using SCF if that MTA is an OSI/MHS subsystem) and determine why it rejects the
open request.
The trace records show all the connection parameters that are used. Check to be sure
the parameters used are the same as the parameters expected by the adjacent MTA.
Table 9-4. CCITT RTS Refusal Reason Codes
Refusal Reason Code Description
0 RTS busy The accepting RTS, or the responder, is so loaded that it
cannot support a new association. The requesting RTS
should retry the request.
1 cannot recover This value is used only by the accepting RTS in the
association recover procedure if it is unable to accomplish
an attempted association recovery.
2 validation failure The responder does not recognize the requestor’s
credentials as being valid for the proposed association.
3 unacceptable dialogue mode The responder does not accept the type of dialogue mode
proposed for the association.