HP 3000 Manuals HP 3000 Manuals
Troubleshooting Procedures When Using X.400 with HP Desk
The following procedures help trace outgoing and incoming messages in
order to determine where the problem is occurring.
Outgoing Message
1. Log on to HP Desk on HP X.400/HP Desk Node.
2. Send a message to a remote X.400 user with priority set to urgent
and acknowledgement set to 3 (ack 3). This forces the remote
X.400 system to generate a delivery acknowledgement and to test
for bidirectional connectivity.
3. Monitor the message by selecting option 3 of the X400UTIL
command. Messages similar to the following display:
08/23 13:17 [E] Extracted msg refno 639749 from HPDESK queue
X400. Filename = P1317261.PUB.HPOFFICE.
08/23 13:17 [E] Processing HPDesk msg in file
P1317261.PUB.HPOFFICE
08/23 13:17 [E] Message P1317261.PUB.HPOFFICE
Sender = David Wood
08/23 13:17 [E] Message P1317261.PUB.HPOFFICE
Subject = Mktg Meeting
08/23 13:17 [E] Message P1317261.PUB.HPOFFICE
passed to Transfer process in file T3547859.X400FILE
This shows the export process, indicated by [E], extracted the
message from the HP Desk data base and transferred it to the
transfer process. If such a message does not display, check if HP
X.400/HP Desk is running by using X400STATUS
. If it is not running, use X400MAILON
to start the HP X.400/HP Desk Node and send a message again.
If the export process logged errors to the log file, refer to
Appendix A in the HP X.400/HP Desk Administrator's Guide for an
explanation of the errors. Make sure that the recipient's
location is configured as an X.400 location.
The transfer process logs messages such as:
09/14 15:29 [T] Transferring T3547859.X400FILE to X.400
as CLIPPER/NE557803
09/14 15:29 [T] File CLIPPER/NE557803 successfully
transferred to X.40
This shows the transport process, indicated by [T], logged the
message. The filename T3547859 is the name of the file that the
export process submitted to the transfer process. If a message
also shows the file was transferred to X.400, continue to step 4.
If the transfer process failed to copy the file to X.400, the
reasons may be:
a. The NS/9000 between the HP X.400/HP Desk Node and X.400 may
not be working. The transfer process is likely to log an
error such as:
10/04 15:55 [T] X400ERR - Unable to connect to target node.
MC:220/3030 LP;t_at
tempt_transfer LC:200 (NSERR 6)
(Transfer) SUP1:0 SUP2:0
Refer to the HP 9000 Series 300 and 800 Computers Network
Services manual for resolving this error.
b. The password configured on the HP X.400/HP Desk Node for
X.400 may be incorrect. The transfer process is likely to
log an error indicating lack of permissions. Run the X.400
Configurator program by typing at the MPE prompt x400config
to access the System Parameters menu to verify that X.400
login password is correct. Also, run x4admin and access
the Configure HP X.400/HP Desk Nodes screen to make sure
that the HP X.400/HP Desk Node is configured on X.400.
c. X.400 or the HP 9000 is not running. Use x4stat
to check that X.400 is running. If it is not running, the
permissions will be set so that the transfer process cannot
copy files to X.400.
d. There is not enough disk space on the HP 9000. There must
be 8 Mb of disk space on the partition containing
/usr/spool/x400 for files to be transferred to the HP 9000.
Use the bdf command to check the disk space.
4. Track the message on the Server in the event log files using the
MSGTRACK utility within x4admin, the x4msgtrack, or x4logcat
command, or the HP-UX commands cat, more, vi, or tail. When using
the message tracking utility, the name of the file transferred
from the HP X.400/HP Desk Node to X.400 is the name of the file
found in the HP X.400/HP Desk log file. You can also track the
message by checking individual event log files.
An example using an HP-UX command is tail
/usr/spool/x400/log/encoder.evnt, which shows the last 10 lines of
the event log file. When the message is copied to X.400,
the encoder processes it. Look in the event log file
/usr/spool/x400/log/encoder.evnt for messages such as:
09/11-17:20:15 Processing (X4EVENT 501)
IFF File [/usr/spool/x400/eiq/CLIPPER/NE557803]
09/11-17:20:16 IFF Submitted to MTA (X4EVENT 502)
IFF File [/usr/spool/x400/eiq/CLIPPER/NE557803]
PDU File [/usr/spool/x400/iq/I0911172015a]
If no messages display, use x4stat
to make sure that X.400 is running.
If the encoder process logs an error in the event log file, use
x4logview
to obtain more information about the error. Refer to Appendix B
for details.
5. The MTA process now processes the message and logs in
/usr/spool/x400/log/mta.evnt messages such as:
09/12-10:23:28 UMPDU 0 ARRIVED in file
/usr/spool/x400/iq/I0911172015a (X4EVENT 2113)
Mpdu-id : US ADMD HPUSA CLIPPER F102253 644370493B
Originator : CNTRY=US ADMD=ADMD PRMD=HPUSA ORG=SALES SUR=WOOD
09/12-10:23:29 UMPDU 1
RELAYED to MTA 3 in file
/usr/spool/x400/oq/oq003/H0912102328a.003. (X4EVENT 2107)
Mpdu-id : US ADMD HPUSA CLIPPER F102253 644370493B
Originator : CNTRY=US ADMD=ADMD PRMD=HPUSA ORG=SALES SUR=WOOD
Recipient : CNTRY=US ADMD=admd PRMD=hp ORG=mktg SUR=cole
Per Recipient Flag : a8(Hex), 168(Decimal)
This shows the MTA routed the message to MTA 3, the adjacent MTA
to which the message is to be sent. The name of the MTA is also
found in the event message.
If the MTA process logs an error in the event log file, use
x4logview
to obtain more information about the error. Refer to Appendix B
for details.
If error "Could not deliver. No route." is in the event log file,
this indicates that the MTA process was not able to find a route
for the recipient O/R address. Do the following:
a. Verify the recipient O/R address was specified correctly.
b. Use x4rtview
to make sure that a route exists for the recipient O/R
address.
c. Use x4admin
to add or modify the route.
6. The RTS process now attempts to send the message to the adjacent
MTA 3 and logs in /usr/spool/x400/log/r003.evnt event messages
such as:
09/12-10:47:17 STARTED OUTBOUND TRANSFER OF 716 BYTES
/usr/spool/x400/oq/oq003/H0912102328a.003 (X4EVENT 3502)
09/12-10:47:20 OUTBOUND TRANSFER SUCCESSFULLY COMPLETED
/usr/spool/x400/oq/oq003/H0912102328a.003 (X4EVENT 3505)
This shows that the file was successfully transferred. If the
recipient still did not receive the message, check and perform the
necessary troubleshooting on the adjacent MTA
.
If the RTS
process cannot communicate with the RTS process of the adjacent
MTA, it logs in the event log file errors such as:
09/12-10:37:12 CONNECT ATTEMPT FAILED - MESSAGE RETURNED TO MTA
/usr/spool/x400/oq/oq002/N0824103723a.002 (X4EVENT 3506)
REASON = Validation failure
This shows that the adjacent MTA refused the connection because of
validation failure. Use x4admin
to access the Add Adjacent MTA screen to check the Adjacent MTA
Mnemonic Name
(this is the outgoing MTA name
) and Outgoing Password fields. Then verify that the name and
password configured on X.400 matches those configured on the
adjacent MTA.
If the RTS process was not able to establish a connection to the
adjacent MTA because of failure at the session or lower layers, it
also logs errors such as:
9/15-15:10:50 RECEIVED S-PROVIDER-ABORT.INDICATION
(X4EVENT 3534)
REASON CODE = f3
PATH ID: 1
09/15-15:10:50 NO CONNECTION YET - RTS BUSY (will try later)
(X4EVENT 3522)
Use x4solve to retrieve the recommended actions for the errors.
Refer to Appendix A for more information on x4solve.
If the RTS process logs other errors, use x4logview
to obtain more details and x4solve to retrieve more information on
the error.
Incoming Message
1. Send a message from an adjacent MTA to an HP Desk user. Make sure
that the O/R address
of the HP Desk user is correct, including the user's HP Desk
location/sublocation codes.
2. Observe the event log file corresponding to the adjacent MTA to
verify that the message is sent correctly to X.400. Refer to
Appendix A in this manual for information on determining the name
of the RTS event log file to examine. For example, look at MTA
3's corresponding file /usr/spool/x400/log/r003.evnt for a message
indicating that the adjacent MTA was able to establish a
connection at the RTS
layer:
09/12-13:06:45 INCOMING TRANSFER STARTED (X4EVENT 3523)
Incoming MTA Name: ``BOBCAT''
Incoming Password: ``express''
If a similar message is in the file, go to the next step. If not
in the file (logged at current time), it is likely that the
adjacent MTA was not able to establish a connection at the session
layer or layers below. Refer to the Installing and Administering
OSI Transport Services manual for further information on
troubleshooting this problem.
If the RTS process logs an error indicating Validation Failure,
the passwords configured for the adjacent MTA may be incorrect.
Use x4admin to access the Configure Local MTA screen to check the
incoming MTA Name
and access the Add Adjacent MTA screen
to check the Incoming Password. Then verify that the name and
password configured on X.400 matches those configured on the
adjacent MTA.
3. When the RTS process accepts the message from the adjacent MTA, it
submits the message to directory /usr/spool/x400/iq. The MTA
process then processes the message. Track the message on X.400 in
the event log files using the MSGTRACK utility within x4admin or
the x4msgtrack command. You can also track the message by
checking individual event log files. Look in the MTA event log
file /usr/spool/x400/log/mta.evnt for messages such as:
09/11-14:07:10 UMPDU 0 ARRIVED in file
/usr/spool/x400/iq/M09111407a.504 (X4EVENT 2113)
Mpdu-id : US ADMD HPUSA CLIPPER NE020018925417141905
Originator: CNTRY=US ADMD=admd PRMD=hp1 SUR=root
Filesize: 543 bytes
Priority: 1
Content Type: 2
09/11-14:07:10 Trace entry 0 from US ADMD HPUSA
Arrived at Sep 11 14:06:54 1989 PDT Action = RELAYED
09/11-14:07:10 Internal Trace entry 0 from CLIPPER
Arrived at Sep 11 14:06:54 1989 PDT Action = RELAYED
09/11-14:07:11 UMPDU 1
RELAYED to MTA 1 named SILVER in file
/usr/spool/x400/oq/oq001/N09111411a.001. (X4EVENT 2107)
Mpdu-id : US ADMD HPUSA CLIPPER NE020018925417141905
Originator: CNTRY=US ADMD=admd PRMD=hp1 SUR=root
Recipient: CNTRY=US ADMD=teledemo PRMD=hp2 SUR=root
Per Recipient Flag: 98(Hex), 168(Decimal)
This shows that the MTA routed the message to MTA 1, which should
correspond to the HP X.400/HP Desk Node.
If the MTA process logs an error, use x4logview
to obtain more details and x4solve to retrieve more information on
the error. Refer to Appendix A for more information on x4solve.
If error "Could not deliver. No route." is in the MTA event log
file, this indicates that the MTA process was not able to find a
route for the recipient O/R address. Do the following:
a. Verify the recipient O/R address was specified correctly.
b. Use x4rtview
to make sure that a route exists for the O/R address of the
HP Desk user.
c. Use x4admin
to add or modify the route.
d. Send the message again after adding or modifying the route.
e. Verify that the message was received by the RTS and then by
the MTA on X.400.
4. If the MTA process correctly routes the message to the HP X.400/HP
Desk Node, the decoder process now processes the message. Look in
the decoder event log file /usr/spool/x400/log/decoder.evnt for
messages such as:
09/11-14:07:15 Decoding (X4EVENT 801)
PDU File [/usr/spool/x400/oq/oq001/N0911140711a.001]
09/11-14:07:16 Submission to X4XFER (X4EVENT 812)
PDU File [/usr/spool/x400/oq/oq001/N09111407111a.001]
IFF File [/usr/spool/x400/doq/oq001/N0911140715a.M]
If the decoder process logs an error, use x4logview to obtain more
details and x4solve to retrieve more information on the error.
Refer to Appendix A for more information on x4solve.
5. The x4xfer process now attempts to copy the file to the HP
X.400/HP Desk Node. Look in /usr/spool/x400/log/x4xfer.evnt for a
message such as:
09/11-14:07:42 X4XFER Copied /usr/spool/x400/doq/oq001
/N0911140715a.M to CLIPPER as MB508537 (X4EVENT 711)
If the x4xfer process failed to copy the file to the HP X.400/HP
Desk Node, an error is logged. Use x4solve to retrieve more
information. The possible reasons for an error may be:
a. The NS/9000 between the HP X.400/HP Desk Node and X.400 may
not be working. Use x4solve to retrieve information on the
error and recommended actions.
Refer to the HP 9000 Series 300 and 800 Computers Network
Services manual for information on NS errors.
b. The password configured for the X400XFER.HPOFFICE,X400XFER
logon on the HP X.400/HP Desk Node may be incorrect. In
this case, the error Could not log on to target node
displays. Use x4admin to correct the password in the
Modify HP X.400/HP Desk Node screen and go to the next
step.
When the x4xfer process failed to copy the files, the result of
the dscopy command is saved in files in /usr/spool/x400/log/dslog.
Look at the file specified in the event log file for more details.
6. When the file is copied to the HP X.400/HP Desk Node, the HP
X.400/HP Desk receive and import processes then process the
message. Monitor the message by selecting option 3 of the
X400UTIL command. Messages display such as:
09/14 15:39 [R] MB508537.X400XFER passed to Import
process as M5755749.X400FILE
09/14 15:29 [I] File M5755749.X400FILE is an ***X.400 MESSAGE***
09/14 15:29 [I] File M5755749.X400FILE Sender = Smith Caroline
09/14 15:29 [I] File M5755749.X400FILE Subject = Schedule
09/14 15:29 [I] File M5755749.X400FILE has 1 HPDesk users on
its distribution list
09/14 15:29 [I] File M5755749.X400FILE successfully submitted
into HPDesk; Ref No = 1448370
This shows the receive process, indicated by [R], or the import
process, indicated by [I], logged the messages.
If no messages display, use X400STATUS
to make sure that all X.400 processes are running.
The import process may also log errors when
a. Recipient O/R address
is incorrect.
b. Location/sublocation specified in the recipient O/R address
is incorrect. The import process will not submit the
message to the HP Desk data base.
To verify the recipient O/R address, run the X.400 Configurator
program by typing at the MPE prompt x400config and access the
Recipient Address Specific Details menu. Then verify the mapping
of the O/R address fields to the location/sublocation fields.