HP 3000 Manuals HP 3000 Manuals
Worksheet Instructions
This section describes how to use the worksheets located in Appendix A of
this manual.
To configure X.400, determine which of the following items you want to
configure:
1. Local MTA--The MTA from which you send messages. You must
configure your local MTA.
2. Destination(s)--The adjacent MTA, HP X.400/HP Desk Node, Sendmail
connection, HP OpenMail connection, and/or API client to which you
send messages. If you want to send messages outside of your local
MTA, you must configure the appropriate destination.
3. Routes and alternate routes--The path a message may take to reach
its destination. If you configure an adjacent MTA, you must
configure a route to that MTA. Initial routes to the HP X.400/HP
Desk Node, Sendmail connection, HP OpenMail connection, and API
client are automatically configured.
4. User group--A set of O/R addresses that can be given limited X.400
access. If you want to restrict X.400 access for a group of
users, configure a user group.
For each of the items you want to configure, copy the appropriate
worksheets, collect the necessary information, and use the X.400
administration program to configure the information (you can access the
administration program by using either osiadmin or x4admin.
Shaded boxes on a worksheet contain required parameters. Optional
parameters are parameters that accept a blank line as a valid entry.
Default values have been entered on the worksheets if a default value
exists.
For a description of the parameters, refer to the appropriate chapter of
this manual. For example, for a description of the local MTA parameters,
refer to Chapter 5, "Configuring the Local MTA."
Printable String
When you are configuring a menu or screen, you enter a printable string
for certain fields. A printable string consists of the following set of
characters:
"A"..."Z"
"a"..."z"
"0"..."9"
" " (space)
' (apostrophe)
( (left parenthesis)
) (right parenthesis)
, (comma)
+ (plus)
- (hyphen)
. (full stop)
/ (slash)
: (colon)
? (question)
= (equal)
Local MTA Information
This section explains how to obtain management domain names (ADMD and
PRMD), TSAP, SSAP, and NSAP.
Obtaining Management Domain Names.
You need to assign ADMDand/or PRMDnames to your local MTA(see Chapter 2
for more information on ADMDs and PRMDs). If mail is sent from your
local MTA to a public carrier or PTT, the ADMD name assigned to your
local MTAis the ADMD name of the public carrier or PTT. The PRMD name may
be obtained from an assigning authority which may be the ADMD to which
your local MTA is connected.
Obtaining TSAP, SSAP, and NSAP Addresses.
The default TSAP of your local MTA is 0x4D4853 (hexadecimal) or MHS
(ASCII).
The default SSAP of your local MTA is null. You can configure a
different SSAP value for your local MTA if needed, but it is not
recommended.
To obtain the NSAP of your local MTA, refer to the OSI Planning and
Troubleshooting Guide.
NOTE This manual uses the term SAP (SSAP, TSAP) instead of the term
selector (S-selector, T-selector) that is used in other HP
documentation. The terms are synonymous.
Adjacent MTA Information
You must obtain certain information from the Administrator of each MTA.
This includes:
* The address of the adjacent MTA
. You need the SSAP
(optional), TSAP
and NSAP
addresses of the adjacent MTA. The SSAP address is probably null.
* Passwords (optional) used when connections are established. If
you are using passwords, one password is needed when you request
to establish a connection. Another password is needed when the
adjacent MTA requests to establish a connection with your local
MTA. The passwords are case-sensitive and must be exact when
entered.
* Name of the adjacent MTA. If you are using passwords, the name you
use must be the same name used by their MTA.
* The times when mail is to be sent from your local MTA to the
adjacent MTA. The time ranges may vary for low, normal, and high
priority messages.
* The country, ADMD, and PRMDnames associated with the adjacent MTA.
* If the components of the session connection identifier (SCID)used
by the RTSshould be encoded as separate components rather than as
a sequence.
* The profile the adjacent MTA conforms to (CEN/CENELEC 41201,
CEN/CENELEC 41202, NIST 84, NIST 88, or EWOS 88).
* The routing paths to the adjacent MTAs, which are based on O/R
addresses(see Chapter 2 for more information).
This information should be entered on your network map for every adjacent
MTA. Use this map along with the configuration worksheets when
configuring X.400.
HP X.400/HP Desk Node Information
For each HP X.400/HP Desk Node connected to your local MTA, you need to
obtain certain information. This includes:
* NS node name. The NS node name must match the LAN node name
configured in the Systems Parameters Menu of the HP X.400/HP Desk
Node. Refer to Chapter 5, "Configuring the HP Desk Network" of
the HP X.400/HP Desk Node Administrator's Guide for more
information on the Systems Parameters Menu.
* The NS (Network Service/9000)
domain and organization of the node.
* Account, group, and user login passwordsof the node. The account
is hpoffice and the group and user name is x400xfer. The x4xfer
process uses these names and passwords to log on to the HP
X.400/HP Desk Nodes when transferring files. The user password
must match the login password configured in the Systems Parameters
Menu of the HP X.400/HP Desk Node. Refer to Chapter 5,
"Configuring the HP Desk Network" of the HP X.400/HP Desk Node
Administrator's Guide for more information on the Systems
Parameters Menu.
* The country, ADMD, PRMD, organization name, and organization unit
names 1-4 of the HP X.400/HP Desk Node. These parameters must
match the parameters configured on the Addressing Details Menu of
HP X.400/HP Desk Node. Refer to Chapter 5, "Configuring the HP
Desk Network" of the HP X.400/HP Desk Node Administrator's Guide
for more information on the Addressing Details Menu
On the HP X.400/HP Desk Node, you should have configured the following:
1. System parameters--Information about X.400 required by the HP
X.400/HP Desk Node.
2. Addressing details--Information required to create an X.400
address from an HP Desk address.
3. Recipient specific address details--Definition of where the
location code, sublocation code, and FSC address are placed in the
originator's O/R address.
Refer to Chapter 5, "Configuring the HP Desk Network" of the HP X.400/HP
Desk Node Administrator's Guide for more information on HP X.400/HP Desk
Node configuration.