OSI/MHS Configuration and Management Manual

Planning Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
3-3
Using OSI/MHS for Adjacent MTA Message Transfer
•
Any combination of the above
You also need to consider whether your subsystem will be used as an ADMD or a
PRMD. See Appendix B, Configuration Checklists, for checklists to help you describe
your subsystem.
Using OSI/MHS for Adjacent MTA Message Transfer
You can use OSI/MHS in a message-switching network. A message-switching network
provides a public service for X.400 messages in an ADMD environment or for private
service in a PRMD environment. Typically, an ADMD routes messages between
PRMDs within the ADMD, or it routes messages to other ADMDs for routing to PRMDs
in other domains. Taking this into consideration, there may be significant differences in
routing, management, and accounting.
If you plan to use your OSI/MHS subsystem to transfer messages between MTAs, you
should consider the following questions:
•
What are the characteristics of the MTAs with which you want to communicate?
•
How many adjacent MTAs will you have? What are their names? (The
maximum number is 800.)
•
How is the network access to these adjacent MTAs connected? X.25? LAN?
TCP/IP over one or both of these?
•
If connected over X.25, how many X.25 lines or controllers (or adapters for S-
series systems) will you need? Also, what are the specific characteristics of
the interface to the X.25 network (line speed, RS-232C, L3 window, and so
on)?
•
If connected over LANs, what are the specific characteristics of the interface to
the LAN?
•
What are the OSI addressing requirements?
•
What is the pattern of the message flow? Is there a peak time during the day in
which message traffic is greatest? Is there an idle time? Is there a pattern of
uniform behavior? These questions may determine how you configure the store
cleaner: for example, will you configure it for every hour or only at the end of the
day?
•
What is the maximum message size the MTA can handle? What are the average
and maximum sizes of messages from the MTA, and the average number of
recipients per message? OSI/MHS can relay messages of up to 40 MB.
•
How much throughput do you expect, and what are the throughput characteristics
of the adjacent MTA? These factors affect how you set up your MR groups.
•
What type of accounting information do you want to collect? What are your billing
requirements? (volume? frequency?)