OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-12
Problem Examples
Figure 9-3 shows MTA2.
In this example, a message has been submitted to MTA1 from a Transfer PS Mail
client to be delivered to the adjacent MTA2. In this case, MTA1 is the initiator of the
association and MTA2 is the responder. Event message 35 is enabled.
When the connection problem occurs, OSI/MHS reports the following event message:
94-12-02 12:20:46 \CS7.$RK11 TANDEM.MHS.D20 000035
RTS Outgoing Association Rejected; id(0); Reason: Validation
Failure;
Remote:
NSAP=52
TSEL=52
SSEL=4B5353454C3241
PSEL=
Local:
NSAP=51
TSEL=51
SSEL=4B5353454C3141
PSEL=
This event message shows that outgoing association requests are being rejected
because of a validation failure. A connection is being established between two OSI
end systems, but not between MTAs. This fact is reflected in an increase in the
statistics counters for Out-assocs-rej as displayed by the STATS PROCESS command.
(An OSI connection has been established between the two end systems; otherwise, an
MTA could not have made an association request.)
Figure 9-3. MTA2 Configuration
Note. Sometimes the operator or system manager chooses not to enable accounting event
messages for performance reasons.
092VST .VSD
MTA2
MR 1
MR 2 MR 3
X.25
OSI/AS
OSI/TS
X25AM
MTA1 MTA3