1. Make sure that the Monitor Agent software is available in the software distribution directory you created in Step 6 in Section 14.1, Setting Up a New GroupWise System in a Linux Cluster.

2. Mount the GroupWise partition (Monitor Agent Clustering Worksheet item 2) where the Monitor Agent Installation program can access a domain database.

3. From the software distribution directory, start the Installation program and select Configure GroupWise for Clustering.

   

4. Install the Monitor Agent software, following the steps provided in Installing the Linux Monitor Agent in Installing GroupWise Monitor in the GroupWise 8 Installation Guide.

5. Configure the Monitor Agent, following the steps provided in Configuring the Linux Monitor Agent in Installing GroupWise Monitor in the GroupWise 8 Installation Guide, paying special attention to the cluster resource information on the System Options page.

   

   As a result of selecting Configure GroupWise for Clustering on the preferred node, the following cluster-specific configuration actions are performed:

   • The Monitor Agent configuration file (monitor.xml) is created in mount_point/groupwise/agents/share on the shared resource so that the Monitor Agent uses the same configuration file regardless of which cluster node it is running on. The HOME_PATH option includes the mount point and the path to the database so that the configuration file is valid when mounted to each cluster node.

   • The --log startup switch in the grpwise-ma script is set to a location on the shared resource (mount_point/groupwise/agents/log) so that Monitor Agent logging information is written to the same log file regardless of which cluster node it is running on. Gateway accounting files that you can use to generate reports are stored in the acct subdirectory of this location.

   • The Monitor Agent is not configured to start automatically on system startup. In a cluster, you do not want the Monitor Agent to start automatically whenever a node restarts.

6. Continue with Running the Monitor Agent Installation Program on Subsequent Nodes

1. On the next node in the Monitor Agent failover list, mount the GroupWise partition (Monitor Agent Clustering Worksheet item 2) where the Monitor Agent Installation program can access a domain database.

2. From the software distribution directory you created in Step 6 in Section 14.1, Setting Up a New GroupWise System in a Linux Cluster, start the GroupWise Installation program and select Configure GroupWise for Clustering.

   

3. Install the Monitor Agent software on the cluster node as usual, but do not use the Configure option.

   For the Monitor Agent, you do not need to import clustering data on subsequent nodes as you do for the other GroupWise agents.

4. Repeat Step 1 through Step 3 for each cluster node in the Monitor Agent failover list.

   After you install the Monitor Agent on each node in its failover list, the cluster node is ready for the Monitor Agent to fail over to it.

5. Continue with Configuring the Monitor Agent Web Console for SSL.

1. Create a directory on the Monitor Agent partition where you want to store the certificate file.

2. In the grpwise-ma script, use the --httpcertfile switch to specify the full path to the directory you created in Step 1.

1. Test the Monitor by starting it as a daemon, as described in Starting the Linux Monitor Agent as a Daemon in Installing GroupWise Monitor in the GroupWise 8 Installation Guide.

   /etc/initd/grpwise-ma start
   /etc/initd/grpwise-ma status
   

2. Then stop the Monitor Agent.

   /etc/initd/grpwise-ma stop
   /etc/initd/grpwise-ma status
   

3. Return to Running the Monitor Installation Program on the Preferred Node for each node in the Monitor Agent failover list (Monitor Agent Clustering Worksheet item 4)

To set up the load script in iManager:

1. Expand Clusters, then click Cluster Options.

2. In the Cluster field, browse to the Cluster object where the Monitor Agent cluster resource is located.

3. Click the Cluster object to display the cluster resources that belong to the cluster.

4. Select the Monitor Agent cluster resource that you created when you set up the Monitor Agent partition, then click Properties.

   The default load script from a generic IP service template appears as follows:

   #!/bin/bash 
   . /opt/novell/ncs/lib/ncsfuncs
   
   # mount the file system
   exit_on_error mount -t reiserfs /dev/evms/vol /mnt/generic
   
   # add the IP address
   exit_on_error add_secondary_ipaddress a.b.c.d
   
   # start the service
   exit_on_error /etc/init.d/myservice start
   
   # return status
   exit 0
   

5. If this is an NSS volume or a shared pool, make the following changes to set up the Monitor Agent load script:

   1. As needed, in the mount command, change reiserfs to whatever file system type is in use on nodes in the cluster.

   2. In the mount command, change vol to the actual device name of the device in use on nodes in the cluster.

   3. In the mount command, change /mnt/generic to the mount point directory in use on nodes in the cluster.

   4. In the add_secondary_ipaddress command, change a.b.c.d to the secondary IP address of the Monitor Agent cluster resource (Monitor Agent Clustering Worksheet item 1)

   5. In the start service command, change myservice start to the command to start the Monitor Agent.

      /etc/init.d/grpwise-ma start
      
      

6. If this is a traditional Linux volume, use the following load script:

   #! /bin/bash
   . /opt/novell/ncs/lib/ncsfunc
   
   # define the IP address
   RESOURCE_IP=123.123.1.
   
   # define the file system type
   MOUNT_FS=reiserf
   
   # define the device
   exit_on_error evms -f /var/opt/novell/ncs/ContainerActivate -rl
                                                    Share ‘uname -n‘
   MOUNT_DEV=/dev/evms/Share/dat
   
   # define the mount point
   MOUNT_POINT=/mnt/mount_point
   
   # mount the file system
   exit_on_error mount -t $MOUNT_FS $MOUNT_DEV $MOUNT_POINT
   
   # add the IP address
   exit_on_error add_secondary_ipaddress $RESOURCE_IP
   
   /etc/init.d/grpwise-ma start
   
   exit 0
   

   Make the following changes to set up the load script for the Monitor Agent:

   1. On the RESOURCE_IP line, change 123.123.1.1 to the secondary IP address of the GroupWise partition (Monitor Agent Clustering Worksheet item 1).

   2. As needed, on the MOUNT_FS line, change reiserfs to whatever file system type is in use on nodes in the cluster.

   3. On the MOUNT_DEV line, change /dev/evms/Share/dat to the actual device name in use on nodes in the cluster.

   4. On the MOUNT_POINT line, change /mnt/mount_point to the mount point directory in use on nodes in the cluster.

   5. Use the following command to start the Monitor Agent:

      /etc/init.d/grpwise-ma start
      

7. Click OK to save the load script.

1. On the Cluster Resource Properties page of the Monitor Agent cluster resource, click Scripts > Unload Script.

   The default unload script appears as follows:

   #!/bin/bash
   . /opt/novell/ncs/lib/ncsfuncs
   
   # request service stop
   ignore_error /etc/init.d/myservice stop
   
   # stop service otherwise
   sleep 8
   ignore_error fuser -k /mnt/generic
   
   # del the IP address
   ignore_error del_secondary_ipaddress a.b.c.d
   
   # umount the file system
   exit_on_error umount /mnt/generic
   
   # return status
   exit 0
   

2. If this is an NSS volume or a shared pool, make the following changes:

   1. In the request service stop section, change myservice stop to the command to stop the Monitor Agent.

      /etc/init.d/grpwise-ma stop 
      

   2. In the stop service otherwise section (used if the agents do not stop normally), remove these commands:

      sleep 8
      ignore_error fuser -k /mnt/generic
      
      

   3. Use these commands instead:

      ignore_error /etc/init.d/grpwise-ma stop
      sleep 8
      ignore_error pkill -fx "/opt/novell/groupwise/agents/bin/gwmon 
                                                  --home /domain_directory"
      

   4. In the del IP address section, change a.b.c.d to the secondary IP address used in the load script.

   5. In the umount file system section, change /mnt/generic to the mount point directory used in the load script.

3. If this is a traditional Linux volume, use the following unload script:

   #!/bin/bash
   . /opt/novell/ncs/lib/ncsfuncs
   
   /etc/init.d/grpwise-ma stop 
   
   # define the IP address
   RESOURCE_IP=172.16.5.18
   
   # define the mount point
   MOUNT_POINT=/mnt/mount_point
   
   sleep 8
   
   ignore_error fuser -k $MOUNT_POINT
   
   # del the IP address
   ignore_error del_secondary_ipaddress $RESOURCE_IP
   
   # umount the file system
   exit_on_error umount $MOUNT_POINT
   
   # return status
   exit 0
   

   Make the following changes to set up the unload script for the Monitor Agent.

   1. Use the following command to stop the Monitor Agent:

      /etc/init.d/grpwise-ma stop
      

   2. On the RESOURCE_IP line, change 172.16.5.18 to the secondary IP address used in the load script.

   3. On the MOUNT_POINT line, change /mnt/mount_point to the mount point directory used in the load script.

   4. Adjust the sleep command as needed so that the Monitor Agent can shut down normally on your system without being inadvertently killed. by the fuser -k command that follows.

   5. In the fuser -k command (used if the Monitor Agent does not stop normally), change -k to -mk.

      The -m parameter obtains the PID numbers of the processes to kill.

4. Click OK to save the unload script.

1. On the Cluster Resource Properties page of the Monitor Agent cluster resource, click General.

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

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

   • Starts automatically on the next node in its failover list

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

     If you are considering changing these defaults, see the OES 11 Novell Cluster Services 2 for Linux Administration Guide.

2. Under Preferred Nodes, arrange the nodes in the cluster into the desired failover list for the Monitor Agent (Monitor Agent Clustering Worksheet item 4).

3. Click OK.