Planning Secondary Ip Addresses And Cluster - Novell GROUPWISE 8 - INTEROPERABILITY Manual

Section 2.8.4, "Deciding Whether to Run the Agents in Protected Memory," on page 34
Section 2.8.5, "Planning the NetWare Agent Installation," on page 34
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
Internet Agent Information
GWIA
Internet Agent
IP Address
GWIA Domain 172.16.5.83
MTA
Internet Agent (same as MTA)
(GWIA)
"IP Address Worksheet" on page 37
MTA MTA
MTP Port HTTP Port
7100 7180
POA POA
C/S Port MTP Port
1677 7101
1678 7102
MTA MTA Live
MTP Port Remote Port
7110 7677
N/A N/A
to help you plan secondary IP
POA
HTTP Port
7181
7182
MTA
GWIA
HTTP
HTTP Port
Port
7183 N/A
N/A 9850
Planning GroupWise in a NetWare Cluster 29