OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-67
Problem Reporting
Problem Reporting
If you are sure that an LO or RS process interface problem was caused neither by a
configuration error nor by an operator action (like stopping an APPL object), and you
wish to report an LO or RS process interface problem for investigation, provide the
following information to your HP representative:
•
EMS logs, including accounting events
•
Complete traces of LO or RS process
•
Detailed description of the problem
•
Description of the environment (products and product versions)
•
Configuration details (SCF displays, configuration files)
•
Description of the RUA or user application
•
Any other relevant material
Effects on the System
There is minimal effect on the subsystem when connection errors occur with the LO
and RS processes.
Recovery Checklist
Consider the following items if problems arise within the LO or RS processes and their
interfaces:
•
O/R names that have attributes defined in the APPL object
•
OSI addresses
•
Status of the APPL objects
•
Status of the MS group and MR groups
•
Number of associations available per LO and RS group
Summary
This section described troubleshooting examples and guidelines for interconnection
problems with other MTAs or gateways, unroutable messages and nondelivery reports,
and LO and RS process interface problems. It also discussed message tracking using
accounting event messages.