HP 3000 Manuals HP 3000 Manuals
x4loop
Initiate the loopback utility for X.400.
Syntax
________________________________________________________________________
| |
|x4loop {mailx filename} [-N NSAP] |
| {elm filename } |
| |
|{rts {x25}} |
|{{lan } } |
|{{fddi} } |
________________________________________________________________________
Parameters
mailx filename Initiate a loopback test for mailx using the
specified file name.
elm filename Initiate a loopback test for elm using the specified
file name.
rts Initiate a loopback test for the Reliable Transfer
Server (RTS).
x25 If rts is selected, run test over X.25.
lan If rts is selected, run test over LAN.
fddi If rts is selected, run test over FDDI.
-N NSAP Specify the local NSAP value used for the local RTS
loopback test.
Description
The x4loop command verifies that the X.400 components on your system are
working properly. With either the mailx or elm option specified, x4loop
sends a test message from mailx or elm to the MTA and back to the user.
With the rts option specified, x4loop sends a test message from a
specified layer down the stack and back up.
The mailx and elm tests send a test message using the specified filename
to the user currently logged in. After initiating x4loop, you should
receive a message whose body contents are the specified file.
The RTS loopback test runs over X.25, LAN or FDDI. If your system has
more than one of these items configured, you need sequential tests for
each item.
The rts test loops an automatically generated message from the MTA/RTS
interface through the OSI Transport and X.25/LAN/FDDI interface. The
message is configured with the local host's address and is returned by
the X.25 switch or LAN card depending on the test. 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
NOTE The rts loopback test over X.25 requires an X.25 switch.
You must supply an NSAP the first time you run x4loop. This NSAP becomes
the default when running x4loop without the -N <NSAP> parameter until
changed by specifying and saving a new NSAP while executing x4loop.
While the RTS loopback test runs, x4loop displays the contents of the RTS
event log (either loop.evnt or loopl.evnt).
Files
/usr/lib/x400/loop.conf
RTS local loopback configuration file for X.25.
/usr/lib/x400/loop1.conf
RTS local loopback configuration file for LAN.
/usr/lib/x400/loopf.conf
RTS local loopback configuration file for FDDI
/usr/spool/x400/loopiq
Input queue for the loopback diagnostics.
/usr/spool/x400/loopoq
Output queue for the X.25 loopback diagnostics.
/usr/spool/x400/looplanoq
Output queue for the LAN loopback diagnostics.
/usr/spool/x400/loopfddioq
Output queue for the FDDI loopack diagnostics.