After you have installed Novell Cluster Services, as described in Novell Cluster Services Overview and Installation, complete the following tasks to prepare the cluster for your GroupWise system:
Double-check each node in the cluster to make sure it meets the requirements described in Section 2.1, Meeting Software Version Requirements.
To cluster-enable a shared volume for use with GroupWise:
Select a System Clustering Worksheet item (6, 7, or 8) where you marked Yes under Cluster Enabled?.
Complete the steps in the cluster-enabling section of the cluster documentation for your version of NetWare, as listed in Section 1.0, Introduction to GroupWise 8 and Novell Cluster Services on NetWare.
The System Clustering Worksheet provides the volume to cluster-enable for use the GroupWise, the cluster-enabled volume IP address, and the failover path for the GroupWise volume.
For a review of the new Novell eDirectory objects that are created when you cluster-enable a shared volume, see Section 2.6, Deciding Whether to Cluster-Enable the Shared Volumes Used by GroupWise.
If you have installed the latest version of ConsoleOne and the Novell Cluster Services snap-in, you can rename the cluster-related objects in case your DNS name server cannot resolve object names that include the underscore (_) character.
Repeat Step 1 and Step 2 above for the other shared volumes on your System Clustering Worksheet that need to be cluster-enabled.
Continue with Configuring Short Name Resolution.
To ensure that GroupWise volumes are always locatable, configure the short name resolution methods that you want to rely on for GroupWise (System Clustering Worksheet item 9):
After configuring your selected short name resolution methods, continue with the task you need to perform:
Most commonly, you will use eDirectory to resolve the UNC path of a volume into its network address. For example, on the workstation where you run ConsoleOne, you need to map a drive to the location of a domain directory so that ConsoleOne can access the domain database. You could use a map command as shown in the example below:
map drive: = .cluster_volume.context
map m: = .GWCLUSTER_GWVOL1.GWServers
When specifying the map commands, use System Clustering Worksheet item 3 for cluster. Use System Clustering Worksheet item 7 or 8 for each volume where a domain or post office resides. Use System Clustering Worksheet item 4 for context.
Because each GroupWise volume where you plan to create a domain or post office has been associated with a virtual server, you should add lines for the new virtual servers to one or more of the following files as needed:
NetWare: sys:\etc\hosts (on all nodes in the cluster; recommended)
Windows XP/Vista: \winnt\system32\drivers\etc\hosts (on the administrator’s workstation only; optional)
The lines you add to a hosts file could look similar to the following example:
IP_address cluster_volume_SERVER.context cluster_volume_SERVER
Remember that cluster_volume_SERVER represents the name of the virtual server created when you cluster-enabled the volume.
172.16.5.81 gwcluster_gwvol1_SERVER.gwcluster.com
gwcluster_gwvol1_SERVER
When specifying the lines in the hosts files, use System Clustering Worksheet item 7 or 8 for each IP_address and volume where a domain or post office resides. Use System Clustering Worksheet item 3 for cluster. Use System Clustering Worksheet item 4 for context.
Because each GroupWise volume where you plan to create a domain or post office has been associated with a virtual server, you should add all your new virtual servers to DNS. Then you could use a map command as shown in the example below (all on one line, of course):
map drive: = \\volume_SERVER.cluster.com\volume
Remember that volume_SERVER represents the name of the Volume Resource object created when you cluster-enabled the volume. A cluster-enabled volume can function like a server, as these commands illustrate.
map m: = \\gwvol1_SERVER.gwcluster.com\gwvol1
Or, if the ConsoleOne workstation is in the same DNS domain as the GroupWise volume:
map drive: = \\volume_SERVER\volume
map m: = \\gwvol1_SERVER\gwvol1
When specifying the map commands you will need, use System Clustering Worksheet item 7 or 8 for each volume where a domain or post office resides. Use System Clustering Worksheet item 3 for cluster.
On NetWare 6.5, Novell Cluster Services automatically propagates virtual server information into SLP and provides the most reliable name resolution.