HP 3000 Manuals HP 3000 Manuals
Routes
It is recommended that you understand routing before configuring routes.
Read Chapter 2, Routing and Addressing, for a general understanding of
routing and considerations that should be made when you configure routes.
Routing for X.400 occurs on a store and forwardbasis. Each MTA along the
route of a message determines the next MTA to which the message should be
transferred. Thus, the local MTA on X.400 determines to which
destination it should forward the message.
A route consists of a set of O/R address
attributes and a destination. The destination
must be an adjacent MTA, HP X.400/HP Desk Node,OpenMail connection,
Sendmail connection, or API client. The local MTA determines the
destination by comparing the recipient O/R address within a message to
the O/R address attributes specified for each route. The MTA uses the
destination from the first route it matches.
Wildcards and Null Character
If an attribute in a route is omitted
, this attribute matches any value for that attribute in a received
message. If multiple routes match, the MTA delivers the message to the
route it first encounters. Use x4rtview to determine the destination.
One or more wildcards, asterisks (*),can be inserted into a route
attribute. If an asterisk is entered into the country code, the asterisk
must be the only character entered. The asterisk matches any string of
characters. For example, a route that has an ADMD of HP* matches any
ADMD that begins with HP such as HP, HP-CND, and HP-GND. The asterisk
can be inserted anywhere within an attribute. An ADMD of HP*IND*
matches HP-IND, HP-IND/RND, and HPIND.
An attribute that consists of only an asterisk is the same as omitting
that attribute. The MTA routes a message more quickly if an attribute is
omitted.
A null character (#)can be entered into a route attribute. If the null
character is entered into a route attribute, the null character must be
the only character entered.
The null character matches an attribute that is not present in an O/R
address. For example, if the null character is entered for the ADMD,
then a route would only match the O/R address if it has no ADMD.
Initial Routes Added Automatically
You do not need to configure routes destined for HP X.400/HP Desk Nodes,
the Sendmail connection , the OpenMail connection, or API clients, since
the initial route is automatically configured when the destination is
configured.
However, if you wish to modify this route or add additional routes to HP
X.400/HP Desk Nodes, Sendmail connection, OpenMail connection, or API
clients, you may do so using the Add/Modify Route screens. When
modifying an initial route, only the O/R address attribute values present
on the original screen can be modified. For example, the organization
name and organization unit names of the OpenMail connection are the only
attributes that can be modified since these are the only attributes in
the Configure OpenMail Connection screen.
An initial route cannot be deleted. The route is deleted when the
destination is deleted. An initial route cannot contain T.61 characters.
The initial route for the OpenMail connection can contain wildcards and
null characters only in the organization unit names.
The initial route for the Sendmail connection and the initial routes for
API clients cannot contain wildcards or null characters. If the initial
route for the Sendmail connection or the initial routes for the API
clients are not valid 1984 X.400 standard O/R address forms, a warning
message displays. Refer to the O/R Address Attributes and Forms section
of Chapter 2 for more information on 1984 X.400 standard forms.
Output Queues
An output queue
exists for every adjacent MTA, HP X.400/HP Desk Node, Sendmail
connection, OpenMail connection, or API client that you configure. When
a message is routed to a destination, it is placed in that destination's
Output Queue (OQ).
T.61 Characters in O/R Address Attributes
The 1988 X.400 standard allows T.61 characters as well as printable
string characters in the following O/R address attributes: organization
name, organization unit names, DDAs, and personal name (surname, given
name, initials, generational qualifier, and common name). An O/R address
can contain an attribute that consists of a T.61 character version and a
printable string version. Routes configured in x4admin can contain only
one version of an attribute.
x4admin can configure routes with attributes containing characters from
HP's Roman8 character set (for example, a ). The MTA converts the Roman8
character to its T.61 equivalent. Your terminal must be able to support
the Roman8 character set.
Since the 1984 X.400 standard does not support T.61 characters, 1984
X.400 systems may not be able to generate messages containing T.61
characters. You may want to add another route that is the printable
string equivalent of the route that contains T.61 characters. If you add
a route that contains T.61 characters, a message displays reminding you
to enter a route that is the printable string equivalent.
The MTA matches an attribute from an O/R address in a message to an
attribute of a route if:
* The printable string version of an attribute in a message matches
the printable string version of that attribute in a route, or
* The T.61 character version of an attribute in a message matches
the T.61 character version of that attribute in a route, or
* The T.61 version of an attribute in a message matches the
printable string version of that attribute in a route.
Examples
The following examples show how routing works. Example 1 shows how
routes may overlap when using omitted attributes and the wildcard in the
attributes of the configured routes. When routes overlap, use x4rtview
to determine which route the MTA uses.
For each example, use the following configured routes:
Route 1 Country = US
ADMD = HP* Org
Name = Information Networks
Org Unit 1 = Lab
Org Unit 2 = Engr
Destination = MTA1
Route 2 Country = US
ADMD = #
PRMD = *HP*
Org Name = Information Networks
Org Unit 1 = Marketing
Org Unit 2 = *
Destination = MTA2
Route 3 Country = US
ADMD = Telemail
Destination = MTA3
Route 4 PRMD = HP*
Destination = MTA4
Example 1.
If the recipient O/R address for an incoming message is:
Recipient O/R Address Country = US
ADMD = Telemail
PRMD = HP-PRMD
Org Name = Information Networks
Org Unit 1 = Marketing
Org Unit 2 = Customer Support
Personal Name = John Doe
Routes 3 and 4 may be used to deliver the
message. Route 1 cannot be used because the
ADMDs and organization units do not match.
Route 2 cannot be used because the ADMDs do not
match. Use x4rtview to determine if Route 3 or
Route 4 is used.
Example 2.
If the recipient O/R address for an incoming message is:
Recipient O/R Address Country = US
PRMD = PRMD-HP
Org Name = Information Networks
Org Unit 1 = Marketing
Org Unit 2 = Sales
Personal Name = Elizabeth Jones
Route 2 may be used. Route 1 cannot be used because the ADMDs and
organization units do not match. Route 3 cannot be used because the
ADMDs do not match. Route 4 cannot be used because the PRMDs do not
match.
Example 3.
If the recipient O/R address for an incoming message is:
Recipient O/R Address Country = FR
PRMD = HP-Private
Org Name = Information Networks
Org Unit 1 = Lab
Org Unit 2 = Engr
Personal Name = Jean Li
Route 4 can be used. Route 1 cannot be used because the country names do
not match. Route 2 cannot be used because the country names and
organization unit 1 names do not match. Route 3 cannot be used because
the country names and ADMDs do not match.
Configuring Routes
To configure an X.400 route,
* Select the ROUTES item from the Configure X.400 Menu.
This displays the Configure X.400 Routes screen.
![[]](../../pic3k/M011985/FFN373c50.gif)
Figure 8-1. Configure X.400 Routes Screen
NOTE If you are configuring X.400 for the first time, this screen does
not display a list of routes. If you are reconfiguring, this
screen displays a list of the currently configured routes with the
destination and some of the more commonly supplied O/R address
attributes.
The first route for each HP X.400/HP Desk Node, OpenMail
connection, Sendmail connection, and API client is automatically
generated and is indicated by an * immediately to the right of the
type field.
The fieldson the screen are:
Num
Display. Unique index number temporarily
assigned in ascending order to identify a route
during the X.400 configuration. The number
assigned to a route may change as existing
routes are deleted and new routes are added.
Type
Display. Route destination type that can be an
adjacent MTA (MTA), HP X.400/HP Desk Node
(DSK), OpenMail connection (OM), Sendmail
connection (SM), or API client (CL).
Destination
Display. Route destination that can be the
name of an adjacent MTA, HP X.400/HP Desk Node
, local OpenMail connection, local Sendmail
connection, or API client.
O/R Attributes
Display. A list of the O/R attributes assigned
to this route (for example, country name, ADMD,
PRMD, organization name, and organization
units). All attributes that fit on the screen
are displayed.
If you need to scroll the screen,
* Press the Page Down key to scroll forward for additional entries,
or
* Press the Page Up key to scroll to the previous screen.
To add, modify, or delete a route,
* Press the Action Menu key to display the Action Menu so you can
select Add Route, Modify Route, or Delete Route.
To configure a default destination,
* Press the Action Menu key to display the Action Menu so you can
select Configure Default Destination.
To display all O/R attributes of a route,
* Select the specific route to be viewed.
* Press the Action Menu key. The Configure X.400 Routes Action Menu
displays so you can select the Modify Route item to display the
route attributes.
* To display additional route attributes, press the Action Menu key.
The Modify Route Action Menu displays so you can select the
Terminal Address Fields, Personal Name Fields, Domain Defined
Attributes, or Physical Delivery Fields to display additional
route attributes.
Adding a Route
To add a route,
* Select the Add Route item from the Configure X.400 Routes Action
Menu.
This displays the Add Route screen.
![[]](../../pic3k/M011985/FFN383c50.gif)
Figure 8-2. Add Route Screen
NOTE You must configure an adjacent MTA, HP X.400/HP Desk Node, OpenMail
connection, local Sendmail connection, or API client before you can
configure the routesto them.
You use this screen to enter information for a single route. Since you
define routes based on the recipient's O/R address, a routeis the
combination of different O/R attributes. You can route on any
combination of the following route attributes:
Country
ADMD
PRMD
Organization name
Organization unit names (up to four occurrences)
X.121 address
Telematic terminal identifier
UA unique numeric identifier
Surname
Given name
Initials
Generational qualifier
Common name
Domain defined attribute types and values (up to four occurrences)
Physical delivery country name
Physical delivery service name
Postal code
NOTE If an O/R attribute is omitted, the MTA matches any value for that
attribute.
One or more wildcards, asterisks (*), can be inserted into any of
these attributes except for the country code. If an asterisk is
entered into the country code, the asterisk must be the only
character entered. The asterisk matches any string of characters
and can be inserted anywhere within the attribute.
A null character (#) can be entered into any of these attributes.
If the null character is entered, it must be the only character in
the attribute. The null character in an attribute matches that
attribute if that attribute is not present in the O/R address.
The fieldson the screen are:
Country Code
Optional. The country of the route's recipient
O/R address. See Appendix C for a list of
country codes.
Administration Domain
Name
Optional. The name identifying the public
authority of the recipient O/R address. This
field is a printable string of up to 16
characters.
Private Domain Name
Optional. The name identifying the private MHS
network of the route's recipient O/R address.
This field is a printable string of up to 16
characters.
Organization Name
Optional. The name of the organization of the
route's recipient O/R address. The name is a
string of up to 64 characters.
Organization Unit Names
Optional. The names of specific units within
the organization of the route's recipient O/R
address. Up to four units can be specified
with Organization Unit 1 being the highest in
the organizational hierarchy, Organization Unit
2 being the second highest, etc. Each
organization unit name is a string of up to 32
characters.
Destination
Required. The name of the adjacent MTA, HP
X.400/HP Desk Node, OpenMail connection,
Sendmail connection, or API client that is the
destination for this route. The adjacent MTA,
HP X.400/HP Desk Node, OpenMail connection,
Sendmail connection or API client must already
be configured or an error occurs.
When the fields on this screen are correctly defined,
* Press the Done Key. The window is removed from the scree.
* Press the Perform Task key, and a confirmation message displays.
The data in the fields clear so you can continue adding additional
routes.
If your press the Perform Task key without specifying any value in the
destination field, the following error message displays:
Error: Entry is required
If you press the Perform Task key without specifying a value for any
route attributes, the following error message displays:
Error: You must specify a value for at least one field in a route.
(X4MSG 4328)
You must enter the destination and at least one value in one other field
before pressing the Perform Task key.
If you need to cancelthe data you just typed,
* Press the Exit Task key. A confirmation displays asking if you
want to exit without updating the values of the fields.
If you want to define additional routing attributessuch as the X.121
Address,
* Press the Action Menu key to display the Action Menu so you can
select Terminal Address Fields, Personal Name Fields, Domain
Defined Attributes, or Physical Delivery Fields.
Terminal Address Fields Window.
Select the Terminal Address Fields item from the Add Route Action Menu to
display the Terminal Address Fields window.
![[]](../../pic3k/M011985/FFN393c50.gif)
Figure 8-3. Terminal Address Fields Window
The fieldson this window are:
X121 Address (network
address)
Optional. The international numeric address of
the route's recipient O/R address. The address
contains up to 15 digits.
Telematic Terminal
Identifier
Optional. The identifier for a telematic
terminal such as telex or teletex answerback.
The identifier is a printable string of up to
24 characters.
UA Unique Numeric
Identifier (numeric user
identifier) Optional. The unique number that might be
given to an X.400 user. The identifier is a
printable string of up to 32 characters.
When the fields on this screen are correctly defined,
* Press the Donekey. The window is removed from the screen.
* Press the Perform Task key.
Personal Name Fields Window.
Select the Personal Name Fields item from the Add Route Action Menu to
display the Personal Name Fields window.
![[]](../../pic3k/M011985/FFN403c50.gif)
Figure 8-4. Personal Name Fields Window
The fieldson this window are:
Surname
Optional. The surname of the X.400 user. The
name is a printable or T.61 string of up to 40
characters.
Given Name
Optional. The given name of the X.400 user.
The name is a printable or T.61 string of up to
16 characters.
Initials
Optional. The initials of the X.400 user. The
initials are a printable or T.61 string of up
to 5 characters.
Genera- tional Qualifier
Optional. The generational qualifier of the
X.400 user. The generational qualifier is a
printable or T.61 string of up to 3 characters.
Common Name
Optional. 1988 X.400 standard only. The
common name of the X.400 user. The common name
is a printable or T.61 string of up to 64
characters.
When the fields on this screen are correctly defined,
* Press the Donekey. The window is removed from the screen.
* Press the Perform Task key.
Domain Defined Attributes Window.
Select the Domain Defined Attributes item from the Add Route Action Menu
to display the Domain Defined Attributes window.
![[]](../../pic3k/M011985/FFN413c50.gif)
Figure 8-5. Domain Defined Attributes Window
The fieldson this window are:
Attribute Type
Optional. The DDA attribute type. Up to four
types can be specified. The type is a
printable or T.61 string of up to 8 characters.
Attribute Value
Optional. The DDA attribute value. Up to four
values can be specified. The value is a
printable or T.61 string of up to 128
characters.
When the fields on this screen are correctly defined,
* Press the Donekey. The window is removed from the screen.
* Press the Perform Task key.
Physical Delivery Fields Window.
Physical delivery is only available with the 1988 X.400 standard. Select
the Physical Delivery Fields item from the Add Route Action Menu to
display the Physical Delivery Fields window.
![[]](../../pic3k/M011985/FFN423c50.gif)
Figure 8-6. Physical Delivery Fields Window
The fields on this window are:
Physical Delivery
Country Name:
Optional. The country where the physical
delivery recipient is located. This is a
printable or T.61 string of up to 3 characters.
See Appendix C for a list of country codes.
Physical Delivery
Service Name:
Optional. The name of the physical delivery
service for this message. This is a service
offered by an ADMD to convert electronic
messages into physical postal forms and is a
printable or T.61 string of up to 16
characters.
Postal Code:
Optional. Postal code of the physical delivery
recipient. For example, in the U.S.A., this
might be the zip code. This is a printable or
T.61 string of up to 16 characters.
NOTE If a route requires a physical delivery field with printable
characters and T.61 format, two separate routes must be configured.
If an attribute contains both printable characters and T.61 format,
matching one of the formats is considered a match of that
attribute.
When the fields on this screen are correctly defined,
* Press the Donekey. The window is removed from the screen.
* Press the Perform Task key.
Modifying a Route
To modify a route,
* Select the route to be modified from the Configure X.400 Routes
screen.
* Press the Action Menu key.
* Select the Modify Route item from the Action Menu.
This displays the Modify Route screen.
![[]](../../pic3k/M011985/FFN433c50.gif)
Figure 8-7. Modify Route Screen
For a description of the fields, refer to the Add a Route screen field
descriptions.
Refer to the Wildcards and Null Character and Initial Routes Added
Automatically sections of this chapter on restrictions for modifying
routes.
When the fields on this screen are correctly defined,
* Press the Perform Taskkey. A message appears confirming that the
route has been modified.
If you press the Perform Task key without specifying a value in the
destination field, the following error message displays:
Error: Entry is required
If you press the Perform Task key without specifying a value for any
route attributes, the following error message displays:
Error: You must specify a value for at least one field in a route.
(X4MSG 4328)
You must enter the destination and at least one value in one other field
before pressing the Perform Task key.
If you need to cancelthe data you just typed,
* Press the Exit Task key. A confirmation displays asking if you
want to exit without updating the values of the fields.
If you need to modify additional routing attributes,
* Press the Action Menu key so you can select Terminal Address
Fields, Personal Name Fields, Domain Defined Attributes, or
Physical Delivery Fields. Refer to these windows discussed
earlier in this chapter for more information.
Deleting a Route
To delete a route,
* Select the route to be deleted on the Configure X.400 Routes
screen.
* Press the Action Menu key.
* Select the Delete Route item on the Action Menu.
This displays the Delete Route window.
![[]](../../pic3k/M011985/FFN443c50.gif)
Figure 8-8. Delete Route Window
To deletethe selected route,
* Press the Confirm key.
To cancelthe delete operation,
* Press the Cancel key.
NOTE You cannot delete the first route of an HP X.400/HP Desk Node,
Sendmail connection, OpenMail connection, or API client. A message
displays when you attempt to delete the first route to such a
destination. The first route to an HP X.400/HP Desk Node, Sendmail
connection, OpenMail connection, and API client is indicated by an
* immediately to the right of the type field.
Configuring a Default Destination.
The Configure Default Destination screen allows you to configure a
default route destination (which can be an adjacent MTA, HP X.400/HP Desk
Node, Sendmail connection, OpenMail connection, or API client). If the
MTA cannot route a message, instead of generating a non-delivery report,
the MTA routes the message to the default destination. If the RTS
returns a message to the MTA, these messages can also be routed to the
default destination.
Select the Configure Default Destination item from the Configure X.400
Routes Action Menu to display the Configure Default Destination screen.
![[]](../../pic3k/M011985/FFN453c50.gif)
Figure 8-9. Configure Default Destination Window
The fields on this window are:
Default Route
Destination
Optional. Where a message is routed if the MTA
cannot deliver a message. This can be an
adjacent MTA name, an HP X.400/HP Desk Node
name, the OpenMail connection name, the
Sendmail connection name, or an API client
name. This field is a printable string of up
to 32 characters.
Do you want messages Default: n. If the RTS cannot deliver a
returned to the MTA by message, it returns the message to the MTA. The
the RTS to be routed to
the default destination?
(y/n)
MTA tries to find an alternate route for the
message. If the MTA cannot find an alternate
route, then if the value of this field is y,
the MTA routes the message to the default
destination. If the value of this field is n,
a non-delivery report is generated for the
message.
When the fields on this screen are correctly defined,
* Press the Perform Task key.
To delete the default destination,
* Press the Action Menu key and select Delete Default Destination.