OSI/MHS Configuration and Management Manual

OSI/MHS Configuration and Management Manual—424827-003
3-1
3
Planning Your OSI/MHS Subsystem
Planning your OSI/MHS subsystem is a challenging task. You start by defining the
characteristics of your user community, and of existing and planned applications. Then
you consider the requirements those characteristics place on your network, and you
gradually narrow your focus until you have defined a complete and appropriate
configuration. At each step you must make decisions that often determine your next
step. This section attempts to guide you through the planning process and describes
the following considerations:
•
What are your user and application requirements?
•
What are your network-planning constraints? Does the network already exist, or
are you planning a new network?
•
What roles will your HP Nonstop™ subsystem have in your MHS? Will it be
connected to other MTAs? Will the Transfer X400 gateway or general user
gateways be installed? Will your OSI/MHS subsystem act as a message store for
mail users? Will you have local users communicating through the P7 API?
•
What are the criteria for determining route selection?
•
How will you set up the various components of your MHS?
•
How can you apply the NonStop fundamentals to your OSI/MHS subsystem?
This section describes these considerations and their implications. Many questions
overlap in several areas; these are repeated where applicable. This is not an
exhaustive list; this section presents guidelines to help you determine the questions
you need to answer.
Appendix B, Configuration Checklists, contains checklists of questions you should
answer in planning your configuration. These are available for you to copy and use as
worksheets to help you plan and configure your subsystem.
What Are Your User and Application
Requirements?
When reviewing your business needs, you need to consider such questions as:
•
Who are your users? Do they have specific requirements to which you must
adhere, or can you specify requirements to them?
•
If your users have specific requirements, what are they? (number of lines?
number of users? types of O/R names?)
•
How many users will you support?