Item |
Explanation |
---|---|
1) Software Version Updates for Cluster: |
List any servers that need to be updated so that all nodes in the cluster are running the same version of NetWare. For more information, see Section 2.1, Meeting Software Version Requirements. |
2) eDirectory Tree for Cluster: |
Record the eDirectory tree where you created the new Novell Cluster object when you installed Novell Cluster Services. For more information, see Section 2.2, Installing Novell Cluster Services |
3) Cluster Name:
|
Record the name of the new NetWare Cluster object that you created for your GroupWise system. Also record the virtual IP address of the cluster that will remain constant regardless of which node is currently active. For more information, see Section 2.2, Installing Novell Cluster Services. |
4) Cluster Context: |
Record the full context where you created the new NetWare Cluster object. For more information, see Section 2.2, Installing Novell Cluster Services. |
5) Nodes in Cluster |
List the nodes that are part of the cluster that you set up for your GroupWise system. For more information, see Section 2.2, Installing Novell Cluster Services. |
6) Shared Volumes for GroupWise Administration: Cluster Enabled?
GroupWise Administration Snap-ins to ConsoleOne
GroupWise Software Distribution Directory
|
Specify the names (cluster_volume) of the shared volumes where the GroupWise administration snap-ins to ConsoleOne and the GroupWise software distribution directory will reside. For cluster-enabling, specify the IP addresses of the virtual servers (volume_SERVER.cluster) to which the cluster-enabled volumes are tied. For more information, see Section 2.6, Deciding Whether to Cluster-Enable the Shared Volumes Used by GroupWise. |
7) Shared Volume for Domain: Cluster Enabled?
Post Office on Same Volume as Domain?
|
Specify the name (cluster_volume) of the shared volume where the GroupWise domain will reside. For cluster-enabling, specify the IP address of the virtual server (volume_SERVER.cluster) to which the cluster-enabled volume is tied. For more information, see Section 2.4, Planning a New Clustered Post Office and Section 2.6, Deciding Whether to Cluster-Enable the Shared Volumes Used by GroupWise. |
8) Shared Volume for Post Office: Cluster Enabled?
|
Specify the name (cluster_volume) of the shared volume where the GroupWise post office will reside. For cluster-enabling, specify the IP address of the virtual server (volume_SERVER.cluster) to which the cluster-enabled volume is tied. For more information, see Section 2.4, Planning a New Clustered Post Office and Section 2.6, Deciding Whether to Cluster-Enable the Shared Volumes Used by GroupWise. |
9) IP Address Resolution Methods:
|
Mark the short name address resolution methods you want to implement to ensure that the UNC paths stored in ConsoleOne can be successfully resolved into physical network addresses. For more information, see Section 2.7, Ensuring Successful Name Resolution for GroupWise Volumes |
10) Domain Name: Domain Database Location: |
Specify a unique name for the domain. Specify the directory on the GroupWise volume where you want to create the new domain. For more information, see Section 2.3, Planning a New Clustered Domain. |
11) Post Office Name: Post Office Database Location: |
Specify a unique name for the post office. Specify the directory on the GroupWise volume where you want to create the post office. For more information, see Section 2.4, Planning a New Clustered Post Office. |
12) Document Storage Area Location:
Document Storage Area Access |
If you need a library for a clustered post office, mark where you want to create its document storage area and provide a directory if necessary. For more information, see Section 2.5, Planning a New Library for a Clustered Post Office. |
Domain |
MTA IP Address |
MTA MTP Port |
MTA HTTP Port |
||
---|---|---|---|---|---|
|
|
|
|
Post Office |
POA IP Address |
POA C/S Port |
POA MTP Port |
POA HTTP Port |
|
---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Internet Agent |
GWIA IP Address |
MTA MTP Port |
MTA Live Remote Port |
MTA HTTP Port |
GWIA HTTP Port |
---|---|---|---|---|---|
GWIA Domain MTA |
|
|
|
|
N/A |
Internet Agent (GWIA) |
(same) |
N/A |
N/A |
N/A |
|
WebAccess Agent |
WebAccess IP Address |
MTA MTP Port |
MTA HTTP Port |
WebAccess Agent Port |
WebAccess HTTP Port |
---|---|---|---|---|---|
WebAccess Domain MTA |
|
|
|
N/A |
N/A |
WebAccess Agent (GWINTER) |
(same) |
N/A |
N/A |
|
|
Item |
Explanation |
---|---|
1) agent installation location:
|
Mark the location where you will install the agent software. If necessary, specify the location where you will consolidate multiple agent startup files on a GroupWise volume. For more information, see Deciding Where to Install the Agent Software. |
2) Domain Name: Domain Location: |
Transfer this information from the System Clustering Worksheet (item 10). |
3) Domain Failover Path: |
List other nodes in the cluster where the GroupWise domain and its MTA could fail over. For more information, see Determining Appropriate Failover Paths for the Agents. |
4) MTA Network Information:
|
Gather the MTA network address information from the IP Address Worksheet. For more information, see Planning Secondary IP Addresses and Cluster-Unique Port Numbers for Agents in the Cluster. |
5) Post Office Name: Post Office Location: |
Transfer this information from the System Clustering Worksheet (item 11). |
6) Post Office Failover Path: |
List other nodes in the cluster where the GroupWise post office and its POA could fail over. For more information, see Determining Appropriate Failover Paths for the Agents. |
7) POA Network Information:
|
Gather the POA network address information from the IP Address Worksheet. For more information, see Planning Secondary IP Addresses and Cluster-Unique Port Numbers for Agents in the Cluster. |
8) Load Agents in Protected Memory?
|
Mark whether you need to run the agents in protected memory. If so, specify a unique address space for each agent. For the POA, specify a user name and password if required by your version of NetWare. For more information, see Deciding Whether to Run the Agents in Protected Memory. |