Table of Contents
Advertisement
2.8 Deciding How to Install and Configure the
Agents in a Cluster
There are several cluster-specific issues to consider as you plan to install the NetWare MTA and
POA in your clustered GroupWise system:
Section 2.8.1, "Planning Secondary IP Addresses and Cluster-Unique Port Numbers for Agents
in the Cluster," on page 31
Section 2.8.2, "Determining Appropriate Failover Paths for the Agents," on page 33
Section 2.8.3, "Deciding Where to Install the Agent Software," on page 34
Section 2.8.4, "Deciding Whether to Run the Agents in Protected Memory," on page 36
Section 2.8.5, "Planning the NetWare Agent Installation," on page 37
2.8.1 Planning Secondary IP Addresses and Cluster-Unique
Port Numbers for Agents in the Cluster
The GroupWise agents listen on all IP addresses, both primary and secondary, that are bound to the
server on their specified port numbers. This means that any time there is a possibility of two of the
same type of agent loading on the same node, it is important that each agent use a cluster-unique port
number, even though each agent is using a unique secondary IP address. The best way for you to
avoid port conflicts is to plan your cluster so that each agent in the cluster runs on a cluster-unique
port. Print out a copy of the
addresses and cluster-unique port numbers for all GroupWise agents.
The following filled-out version of the IP Address Worksheet illustrates one way this can be done:
Domain Information
MTA
Domain
IP Address
Provo1
172.16.5.81
Post Office Information
POA
Post Office
IP Address
Development
(same as MTA)
Manufacturing
172.16.5.82
"IP Address Worksheet" on page 40
MTA
MTA
MTP Port
HTTP Port
7100
7180
POA
POA
C/S Port
MTP Port
1677
7101
1678
7102
to help you plan secondary IP
POA
HTTP Port
7181
7182
Planning GroupWise in a NetWare Cluster
31
Advertisement
Table of Contents
