To set up the load script:

1. In ConsoleOne, browse to and select the Cluster object.

   If necessary, click View > Console View to display its contents.

2. Right-click the Volume Resource object (volume_SERVER), then click Properties > Load to display the default volume resource load script for the Internet Agent volume.

   The next step assumes that this is the first time you have edited this load script. If other GroupWise agents are already running from this volume, some of the modifications have already been made.

3. Make the following changes to the default load script:

   • Remove the trustmig command. It is not necessary to migrate trustees for the Internet Agent volume. Removing this line helps the load script to execute faster.

   • On NetWare 5.1, if you are using SLP as a short name resolution method, as described in Configuring Short Name Resolution, add the cvsbind add command for the Internet Agent volume to the load script.

     cvsbind add cluster_volume_SERVER IP_address
     

   • If you selected vol:\system on Internet Agent volume as the installation location (Internet Agent Clustering Worksheet items 4 and 6), add a search add command to add the new vol:\system directory to the server search path.

     search add volume:\system
     

   • If you selected sys:\system on each node as the installation location (Internet Agent Clustering Worksheet items 4 and 6) but you are storing the MTA startup file and the Internet Agent configuration file on the Internet Agent volume, add that location to the server search path.

   • If you marked No under Load Internet Agent and Its MTA in Protected Memory? (Internet Agent Clustering Worksheet item 8), add the following abend recovery options:

     set auto restart after abend = 2
     set auto restart after abend delay time = 0
     set auto restart down timeout = 60
     set developer option = off
     

     These settings provide the best possible handling of GroupWise databases in the event that an abend should occur within the cluster.

   • Transfer the MTA load command from the grpwise.ncf file located in the vol:\system directory into the load script. Use Ctrl+C and Ctrl+V to copy and paste text into the load script page. Then delete or rename the grpwise.ncf file to avoid future confusion.

     load volume:\system\gwmta.nlm @domain.mta
     

   • Add a delay so that the MTA is fully loaded before the Internet Agent starts to load:

     load delay.nlm 
     delay 10
     

     The length of the delay varies from system to system; ten seconds is a good starting place.

   • Transfer the Internet Agent load command from the gwia.ncf file located in the vol:\system directory into the load script. Use Ctrl+C and Ctrl+V to copy and paste text into the load script page. Then delete or rename the gwia.ncf file to avoid future confusion.

     load volume:\system\gwia.nlm @gwia.cfg
     

   • If you marked Yes under Load Internet Agent and Its MTA in Protected Memory? (Internet Agent Clustering Worksheet item 8), add the address space parameter to the load commands to specify the protected address space where the Internet Agent and its MTA will run. Add a protection restart command for the address space name.

     load address space=addr_space_name
                               volume:\system\gwmta.nlm @domain.mta
     load address space=addr_space_name
                               volume:\system\gwia.nlm @gwia.cfg
     protection restart addr_space_name
     

   The result would look similar to the following example:

   

   NOTE:The set commands are needed in the load script only when the MTA and the Internet Agent are not running in protected memory. The address space parameters are needed in the load commands only when the MTA and the Internet Agent are running in protected memory.

4. Click Apply to save the load script.

5. If necessary, click OK to confirm that you must offline and then online the volume resource in order for the changes to take effect.

6. Continue with Modifying the Volume Resource Unload Script for the Internet Agent.

To set up the unload script:

1. In ConsoleOne, in the properties pages for the Volume Resource object (volume_SERVER), click Unload to display the default volume resource unload script.

   The next step assumes that this is the first time you have edited this unload script. If other GroupWise agents are already running from this volume, some of the modifications have already been made.

2. Make the following changes to the default unload script:

   • If you marked Yes under Load Internet Agent and Its MTA in Protected Memory? (Internet Agent Clustering Worksheet item 8), add an unload address space command and an unload kill address space command to ensure that the address space is completely cleaned up.

     unload address space=addr_space_name
     unload kill address space=addr_space_name
     

     If your system seems to be trying to kill the address space before the Internet Agent and its MTA have been completely unloaded, resulting in the agents hanging in the unloading state, set a delay of several seconds before issuing the unload kill address space command to allow the Internet Agent and its MTA adequate time to unload completely. The length of the delay varies from system to system; ten seconds is a good starting place.

     unload address space=addr_space_name 
     delay 10 
     unload kill address space=addr_space_name
     

   • If you marked No under Load Internet Agent and Its MTA in Protected Memory? (Internet Agent Clustering Worksheet items 8), create an unload command parallel to each load command that you placed in the load script.

     unload gwia.nlm
     unload gwmta.nlm
     

   • On NetWare 5.1, if you are using SLP as a short name resolution method, add the cvsbind del command for the Internet Agent volume to the unload script.

     cvsbind del cluster_volume_SERVER IP_address
     

   • Remove the trustmig command just like you did in the load script.

   The result would look similar to the following example:

   

3. Click Apply to save the unload script.

4. If necessary, click OK to confirm that you must offline and then online the volume resource in order for the changes to take effect.

5. Continue with Setting the Failover Path and Policies for the Internet Agent.

To modify the failover path and policies for the Internet Agent volume resource:

1. In ConsoleOne, in the properties pages for the Volume Resource object (volume_SERVER), click Nodes to display the default failover path for the Internet Agent volume resource.

   

2. Arrange the nodes in the cluster into the desired failover path for the Internet Agent volume (Internet Agent Clustering Worksheet item 3).

3. Click Apply to save the failover path.

4. Click Policies to display the default start, failover, and failback policies.

   

   The default policy settings are often appropriate. By default, a volume resource:

   • Fails over automatically if the node it is running on fails

   • Starts automatically on the next node in its failover path

   • Continues running at its failover location, even after its most preferred node is again available

   If you are considering changing these defaults, see the applicable section about failover and failback modes in the cluster documentation for your version of NetWare, as listed in Section 1.0, Introduction to GroupWise 7 and Novell Cluster Services on NetWare.

5. Click OK when you are finished editing the Internet Agent volume resource properties.

6. Continue with Enabling Internet Addressing for Your Clustered GroupWise System.

1. In ConsoleOne, browse to and select the Internet Agent domain in order to display its contents.

2. Right-click the Internet Agent object, then click Properties.

3. Continue with Verifying the Reference to the Volume Resource.

In the Internet Agent object properties pages:

1. Click SMTP/MIME > Settings.

2. Verify the contents of the Hostname/DNS "A Record" Name field.

   It displays the hostname as currently configured in DNS. It should match the Volume Resource object name (volume_SERVER) of the Internet Agent volume, not the name of a physical server in the cluster.

3. Make changes if necessary.

4. Continue with Verifying the Reference to the Virtual Server.

In the Internet Agent object properties pages:

1. Click Server Directories.

2. Verify that the displayed directories match the virtual server name (cluster_volume_SERVER) associated with the Volume Resource object, not the name of a physical server in the cluster.

3. Make changes if necessary.

4. Continue with Verifying Post Office Links.

In the Internet Agent object properties pages:

1. Click Post Office Links.

2. Verify that the Access Mode column displays C/S (for client/server mode) for all post offices serviced by the Internet Agent.

3. Verify that the Links column displays the secondary IP addresses of the GroupWise volumes where post offices reside, not the IP addresses of any physical servers in the cluster.

4. Make changes if necessary.

5. Continue with Forcing Use of the Internet Agent Secondary IP Address.

If you want the Internet Agent to send outgoing messages on its secondary IP address, rather than using the default of its primary IP address:

1. Click GroupWise > Network Address.

2. In the TCP/IP Address field, provide the secondary IP address (under Internet Agent Clustering Worksheet item 1) for the Internet Agent to use for sending outgoing messages.

3. Click SMTP/MIME, then click Settings.

4. Select Bind to TCP/IP Address at Connection Time.

5. Click OK.

6. Continue with Testing the Clustered Internet Agent.