HP 3000 Manuals HP 3000 Manuals
Diagnostic Utilities
This section describes the following diagnostic utilities:
* EVENTLOG
--enable and disable event logs.
* SETCLASS,
--enable and disable component errors by class.
* ARCHIVE
--enable and disable MTA message tracing. If enabled, messages
are copied to the directory /usr/spool/x400/tq.
* RTVIEW
--view the current MTA routing tables.
* QUEVIEW
--view X.400 queues and messages.
* LOOP
--run a loopback test to trouble shoot a Sendmail connection.
* MSGTRACK
--track X.400 messages.
* BUILDIFF
--send a test message to troubleshoot an HP X.400/HP Desk Node.
* BIT
--test basic interoperability.
Each of these utilities can be performed by either typing the appropriate
command at the HP-UX prompt, or by using the X.400 Configuration program
(x4admin) which provides a menu interface.
In some cases, direct use of the HP-UX utilities provides access to
additional functionality not available through the menu interface. For
example, the x4logview
command allows you to specify a time range. This allows you to see
selected messages within a particular time period. It is a good idea to
look at Appendix B to gain familiarity with the capabilities for each
utility and command.
Accessing the Utilities
To access the diagnostic utilities:
* Select DIAGNOSTICS on the X.400 Main Menu
![[]](../../pic3k/M011856/FFN203c50.gif)
Figure 4-2. X.400 Main Menu
This displays the Execute X.400 Diagnostics
Menu.
The menu displays all the utilities you may perform. Select the utility
you wish to execute.
![[]](../../pic3k/M011856/FFN213c50.gif)
Figure 4-3. Execute X.400 Diagnostics Menu
Enabling/Disabling Event Logging.
The EVENTLOG utility enables or disables event logging for the components
you specify.
To use this utility,
* Select EVENTLOG from the X.400 Diagnostics Menu.
This displays the Enable/Disable Event Logging window.
![[]](../../pic3k/M011856/FFN223c50.gif)
Figure 4-4. Enable/Disable Event Logging Window
The fields
on the window are:
Enable or Disable event logging?
MTA? (e or d)
Enter e to enable or d to disable the MTA event
logging.
RTS? (e or d)
Enter e to enable or d to disable the RTS event
logging.
X4MAILER? (e or d)
Only if the Sendmail connection is configured,
enter e to enable or d to disable x4mailer.
ENCODER? (e or d)
Only if an HP X.400/HP Desk Node is configured,
enter e to enable or d to disable encoder event
logging.
DECODER? (e or d)
Only if an HP X.400/HP Desk Node is configured,
enter e to enable or d to disable decoder event
logging.
X4XFER? (e or d)
Only if an HP X.400/HP Desk Node is configured,
enter e to enable or d to disable x4xfer event
logging.
______________________________________________
NOTE When HP X.400 is first installed, the
default is e for all components. If a
field is left blank, event logging for
this component remains unchanged from its
previous state. For example, if MTA
event logging was previously disabled and
the MTA field is left blank, MTA logging
remains disabled.
______________________________________________
To execute event logging
,
* Press the Perform Task key.
To cancel event logging
and remove the window,
* Press the Exit Task key.
NOTE Do not remove event log files when X.400 is running. If more disk
space is needed, use x4agelog
to age the event log files; and then remove the aged files.
See the x4eventlog
command in Appendix B to run this operation from the HP-UX prompt.
Enabling/Disabling Error Logging.
The SETCLASS utility keeps a log of errors for the components you
specify.
To use this utility,
* Select SETCLASS from the X.400 Diagnostics Menu.
This displays the Enable/Disable Error Logging window
.
![[]](../../pic3k/M011856/FFN233c50.gif)
Figure 4-5. Enable/Disable Error Logging Window
The fields
on the window are:
Enable or Disable error logging?
X4XFER? (e or d)
Only if an HP X.400/HP Desk Node is configured,
enter e to enable or d to disable x4xfer error
logging.
ENCODER? (e or d)
Only if an HP X.400/HP Desk Node is configured,
enter e to enable or d to disable encoder error
logging.
DECODER? (e or d)
Only if an HP X.400/HP Desk Node is configured,
enter e to enable or d to disable decoder error
logging.
MTA? (e or d)
Enter e to enable or d to disable the MTA error
logging for the specified error class.
RTS? (e or d)
Enter e to enable or d to disable the RTS error
logging for the specified error class.
Error class?
Default: n. Enter n to display non-critical
errors or p to display procedure tracing.
______________________________________________
NOTE When HP X.400 is first installed,
critical error logging is enabled for all
components, and non-critical error
logging and procedure tracing are
disabled for all components. If a field
is left blank, error logging for this
component remains unchanged from its
previous state. For example, if MTA
error logging was previously disabled and
the MTA field is left blank, MTA logging
is still disabled.
Critical error logging
for all components is always enabled.
You cannot disable critical error
logging.
______________________________________________
To execute
the SETCLASS utility,
* Press the Perform Task key.
To cancel
the SETCLASS utility and remove the window from the screen,
* Press the Exit Task key.
See the x4setclass
command in Appendix B to run this operation from the HP-UX prompt.
Enabling/Disabling MTA Archiving.
TheARCHIVE utility causes the MTA to copy messages into the
/usr/spool/x400/tq directory.
To use this utility,
* Select ARCHIVE from the X.400 Diagnostics Menu.
This displays the Enable/Disable MTA Archiving window
.
![[]](../../pic3k/M011856/FFN243c50.gif)
Figure 4-6. Enable/Disable MTA Archiving Window
The field
on the window is:
Enable or Disable MTA
Archiving? (e or d)
Enter e to enable or d to disable MTA
archiving.
______________________________________________
NOTE MTA archiving uses large amounts of disk
space because each message passing
through the MTA is copied and saved on
the disk. Enable message archiving only
during problem diagnosis for short
periods of time
.
______________________________________________
To execute
the ARCHIVE utility,
* Press the Perform Task key.
To cancel
the ARCHIVE utility and remove the window from the screen,
* Press the Exit Task key.
See the x4archive
command in Appendix B to run this operation from the HP-UX prompt.
Viewing Routes.
The RTVIEW utility allows you to view the MTA routing
table
.
To use this utility,
* Select RTVIEW from the X.400 Diagnostics Menu.
The following is displayed:
Command:
1) Enter standard attributes
2) Enter domain defined attributes
3) Enter postal attributes
4) Find routes for entered O/R address
q) Exit
>
If this address does not use DDAs or postal addressing,
* Enter 1 at the prompt.
If this address uses DDAs,
* Enter 2 at the prompt.
If this address uses the physical delivery fields,
* Enter 3 at the prompt.
To view the list of adjacent MTA numbers and names for a particular O/R
address,
* Enter 4 at the command menu.
To exit
from the route viewer,
* Enter q at the command menu.
See the x4rtview command in Appendix B to run this operation from the
HP-UX prompt.
Viewing Queues.
QUEVIEW allows viewing and removal of X.400 messages in system queues.
It decodes and displays X.400 messages in a readable text format. Users
should be familiar with the X.400 standards.
QUEVIEW deletes X.400 messages. X.400 messages in the UQ and TQ can be
deleted at any time. X.400 messages in the IQ and OQs can be deleted
only when X.400 is not running.
The output uses the ASN.1 PDU format. For more information on ASN.1 PDU,
refer to the CCITT X.400 Red Book.
To use this utility,
* Select QUEVIEW from the Execute X.400 Diagnostics Menu.
The following menu appears
:
![[]](../../pic3k/M011856/FFN253c50.gif)
Figure 4-7. X.400 MHS Utility Menu
To display X.400 header information and message contents
for all messages in a specified message queue,
* Enter 1 at the prompt.
To display only the X.400 message contents
of a specified message,
* Enter 2 at the prompt.
To delete an X.400 message,
* Enter 3 at the prompt.
To exit the X.400 MHS Utility Menu,
* Enter 4 at the prompt.
See the x4queview command in Appendix B to run this operation from the
HP-UX prompt and for sample output.
Executing Loop Back.
The LOOP utility verifies that the X.400 components on your system are
working properly. LOOP sends a test message
from a specified layer down the stack and back up.
To use this utility,
* Select LOOP from the Execute X.400 Diagnostics Menu.
If the Sendmail connection is not configured, the rts test is executed
automatically.
If the Sendmail connection is configured, this displays the Execute Loop
Back Utility window.
![[]](../../pic3k/M011856/FFN263c50.gif)
Figure 4-8. Execute Loop Back Utility Window
The fields
on the window are:
Type of loop back test Enter mailx to perform a mailx loopback test,
to be executed: elm to perform an elm test, or rts to perform
an RTS loopback test.
If you enter mailx or elm,
you are prompted to enter the filename of the test message to send. If
you enter rts, you are prompted to enter either lan or x25.
The mailx and elm tests send a test message to the x400 user. However,
running x4loop mailx/elm from the command line sends a test message to
the user currently logged in. This message does not go to the RTS. The
MTA routes this message back to the user.
For the rts test, you are prompted for the following:
Do you want to run the Enter lan to run the loopback test over 802.3,
test over LAN, X.25, or x25 to run the loopback test over X.25, or fddi
FDDI [lan/x25/fddi]?
to run the loopback test over FDDI.
The rts test loops an automatically generated message from the MTA/RTS
interface through OTS, to the 802.3, X.25 network, or FDDI interface.
The message is generated with the local host's address and is returned by
the 802.3 LANIC or the X.25 switch. The message then progresses back
through the OSI Transport and RTS to the RTS/MTA interface where it is
checked against the original. If the two messages are identical, the
following message is displayed:
RTS LOOPBACK TEST COMPLETED SUCCESSFULLY!
If the two messages are different, the following message is displayed:
RTS LOOPBACK TEST FAILED - sent and received messages differ
If one of the lower layers is not running or the message cannot be sent
within a specified period of time, the following message is displayed:
RTS LOOPBACK TEST FAILED - cannot send message
If the loopback test fails, check the last event logged on the screen.
There is an event log number attached (for example, x4event ###). Using
x4solve, look up this error number to get the error message, cause, and
action. After completing the action, run the loopback test again. If
the problem still exists, refer to the "Troubleshooting" chapter in the
OSI Planning and Troubleshooting Guide.
NOTE If you are using the X.25 interface card, an X.25 switch is
required for the RTS
loopback test.
Executing Message Tracking.
The MSGTRACK utility tracks X.400 messages by searching the X.400 event
logs and prints out the events logged for the specified message.
The MSGTRACK utility cannot track X.400 messages if
* the event log files are aged (MSGTRACK only checks the *.evnt
files).
* the process has not produced any events in a log file.
* the event logged does not contain the message file name.
To use this utility,
* Select MSGTRACK from the X.400 Diagnostics Menu
The following menu appears:
![[]](../../pic3k/M011856/FFN273c50.gif)
Figure 4-9. X4MSGTRACK Main Menu
To display all message files sent from HP Desk,
* Enter 2 at the prompt.
To display all message files sent from Sendmail,
* Enter 3 at the prompt.
To display all message files sent from the HP X.400 API,
* Enter 4 at the prompt.
* Enter the name of the file defined by the API programmer as the
log file at the next prompt.
To display all message files sent to and from the MTA,
* Enter 5 at the prompt.
See the x4msgtrack command in Appendix B to run this operation from the
HP-UX prompt.
Sending a Test Message.
The BUILDIFF utility builds an X.400 message in IFF format and submits it
to the encoder. BUILDIFF tests the functionality of X.400 with HP Desk.
Use this utility to send a message to a user on an adjacent MTA.
NOTE Use this utility only if you are using X.400 with HP Desk.
To use this utility,
* Select BUILDIFF on the X.400 Diagnostics Menu.
You will be prompted for the Originator name, Recipient name, subject,
text file to send and whether a delivery report is required.
Executing BIT Testing.
The BIT utility test basic interoperability of HP's X.400 with other
vendors' X.400 implementations. BIT tests the functionality of X.400
with Sendmail. Use this utility to send a message to a user on an
adjacent MTA using mailx.
NOTE Use this utility only if you are using X.400 with elm or mailx.
To use this utility,
* Select BIT from the X.400 Diagnostics Menu.
The BIT utility completes three tests:
1. Test primary recipient and subject.
You should check that the remote system receives a message with
the subject Test1 and content Test case #1.
2. Test Cc:, Bcc:, and delivery notification.
You should check that the remote system receives a message with
subject Test2. You should also check that the Cc: and Bcc:
recipients receive a message, the Bcc: recipient name does not
appear in the To: and Cc: message, and the originator receives a
delivery notification from the To:, Cc:, and Bcc: recipients.
3. Test nondelivery notification.
You should check that the local system originator receives a
nondelivery notification that includes X.400 diagnostic code and
if the local To: recipient receives the message.
See the x4bit command in Appendix B to run this operation from the HP-UX
prompt.