8.6 Configuring Cluster Event Email Notification

OES Cluster Services can automatically send out email messages for certain cluster events like cluster and resource state changes or nodes joining or leaving the cluster. The subject line provides information about the cluster name, resource name, action taken, and node name. For example:

CL1: POOL1_SERVER online on NODE1

You can enable or disable email notification for the cluster and specify up to eight administrator email addresses for cluster notification.

8.6.1 Configuring an Email Port

OES Cluster Services uses Postfix to send cluster email alerts, using the primary IP address. Postfix uses port 25 by default. If you have a cluster resource that uses SMTP (which also defaults to port 25), the port conflict between Postfix and SMTP can prevent that resource from working in the cluster. To avoid a port conflict, you can change the Postfix port configuration, or you can bind the clustered service to its resource’s secondary IP address.

To configure Postfix to use a different port, you can edit the /etc/postfix/main.cf file and change the values for the inet_interfaces, mydestination, and mynetworks_style directives. You can change the listen port for the smtpd process in the /etc/postfix/master.cf file. For more information about configuring Postfix, see the Postfix website.

To bind a service to its resource’s secondary IP address, refer to the cluster documentation for the service. For example, the GroupWise Internet Agent (GWIA) uses SMTP. Because both Postfix and the GWIA default to using port 25, you must configure the GWIA to bind exclusively to its resource’s secondary IP address in order to avoid a port conflict between Postfix and the GWIA. For information about how to set up the secondary IP address and to bind the GWIA to it, see the following sections in the GroupWise 2012 Interoperability Guide:

8.6.2 Configuring the Notification Policies

  1. In iManager, select Clusters > My Clusters.

  2. In your personalized My Clusters list, select the check box next to the cluster you want to manage.

    If the cluster does not appear in your list, add the cluster to your list as described in Section 8.2, Setting Up a Personalized List of Clusters to Manage.

  3. Click Action > Edit Properties to open the Properties dialog box.

  4. Click the Policies tab.

  5. Under Notification, select or deselect the Enable Cluster Notification Events check box to enable or disable email notification.

  6. If you enable email notification, configure the notification settings:

    1. Add up to eight email addresses in the field provided.

      You can click the buttons next to the field to add, delete, or edit email addresses. Repeat this process for each email address you want on the notification list.

    2. Specify the type of cluster events you want administrators to receive messages for.

      • Only Critical Events: (Default) Select this option to receive notification only of critical events like a node failure or a resource going comatose.

      • Verbose Messages: Select this option to receive notification of all cluster state changes including critical events, resource state changes, and nodes joining and leaving the cluster.

    3. Specify whether you want to receive notification of all cluster state changes in XML format by selecting the XML Messages option.

      XML is selected by default. XML format messages can be interpreted and formatted with a parser that lets you customize the message information for your specific needs.

  7. Click Apply or OK to save changes.