HP 3000 Manuals

Managing HP X.400 Administrator's Guide

Problem Isolation 

The first task in diagnosing a problem is to isolate it to one of the
major components.  For instance, if a message is not being transferred to
an adjacent MTA, the problem could be in routing, in queuing, or in the
network.  If a message from the HP X.400/HP Desk Node is not received by
the MTA, the problem could be with the encoder or EIQ. If a message from
Sendmail is not received by the MTA, the problem could be with x4mailer.
A general knowledge of the X.400 system and the Error and Event logs will
help you isolate the problem.

The following is a list of components and related problems.  Figure 8-1
shows the major components of HP X.400.

   *   MTA 
       --problems with routing, encoding or decoding, or the MTA's IQ 

   *   RTS 
       --problems with the network or RTS queues

   *   encoder 
       --problems with outgoing messages to X.400 from HP Desk

   *   decoder/x4xfer 
       --problems with messages destined for HP X.400/HP Desk Node

   *   x4mailer 
       --problems with messages being transferred between Sendmail and
       the MTA


          Figure 4-1.  HP X.400 Major Componants 

Use the following guidelines 
to isolate the problem:

   1.  Check if X.400 is running by using the x4stat 
       command or using x4admin. 

       If you use x4admin, select STATUS from the X.400 Main Menu.  The
       Monitor X.400 Status Menu displays.  Select PROCESS. The current
       status information for OTS and X.400 displays.

   2.  Check event or error messages relating to the message, file, or
       adjacent MTA. The message may often describe the problem exactly.
       For example, an MTA event log message may include a reason of:
       Message Discarded -- No route.  This isolates the problem to
       routing.  You then want to isolate the problem further, that is,
       to either an incorrect O/R address specification or an incorrect
       entry in the routing table.

       To display an event log 
       , run x4admin and select STATUS from the X.400 Main Menu.  The
       Monitor X.400 Status Menu is displayed.  Select EVENTS. The
       Display Events window appears and you may select a component to
       view.  The event log file you have chosen is displayed.

       To format and display an error log file, select STATUS from the
       X.400 Main Menu to get to the Monitor X.400 Status Menu.  Select
       FMTERRS to display the Format and Display Errors window.  Select a
       component to view.  The error log file you have chosen is
       displayed. 

   3.   

       Trace a message using event logs or x4msgtrack.  You can determine
       which components handled a message and its route.  For instance,
       if the MTA event log lists a message as being routed to an HP
       X.400/HP Desk Node, but that message does not appear in the
       decoder event log, the message should be in one of the MTA to
       decoder OQs.  The MTA event log lists a message as being routed to
       x4mailer, but that message does not appear in the 
       x4min.evnt log file, the message should be in
       /usr/spool/x400/oq/oq253.  The previous step explains how to
       display an event log.

   4.  Use the diagnostic utilities 
       if the log files do not provide enough information.  If the
       problem is reproducible, enable the diagnostics to track the
       problem.  The diagnostics utilities are located in the next
       section of this chapter.

Once you isolate the problem to a specific component, check the
configuration information of that area.  Many problems arise due to
incorrect configuration. 
If the problem is not due to incorrect configuration and no other cause
is apparent, use the diagnostic utilities to examine the system before
the problem occurs again.

MPE/iX 5.0 Documentation