Clicking thebutton also displays an additional section on this page called . Monitors are an important part of the automatic failover feature, and are separate processes that perform a specialized task to analyze the health of a specific cluster or all clusters in the BCC. These monitors report an indication of health to BCC. BCC in turn uses the reported information to analyze the failover policy to determine if resources should be migrated from a specific cluster. Business Continuity Clustering 1.1 ships with two monitors (nodecnt and node pnt) that report an indication of health that represents either the percentage or number of nodes that do not belong to a specific cluster.
If they are configured by using the Cluster Membership Monitoring Settings table, the fields undershould already contain information for the health monitor (nodepnt or nodecnt) included with Business Continuity Clustering 1.1. Although default values have already been set, you can customize some of the monitor settings for the cluster membership monitors. If you have created your own custom monitor, you can click to add configuration settings to your monitor.
In iManager, underin the section, select a monitor and click .
Under, select the cluster or clusters that you want this monitor to apply to.
Specify the maximum health indication that the monitor will report.
This value is used when creating a failover policy to validate the rules. This is the maximum value that can be used for the threshold type when you create a failover policy. For example, if you specified percent fail membership monitoring, the maximum values would be 100 (for 100 percent) for the nodepnt monitor. If you specified nodes fail membership monitoring, the maximum value for the nodecnt monitor is the maximum number of nodes permitted in a cluster, which is 32. If you created your own custom monitor, the values could be different.
For the nodepnt and nodecnt monitors, thevalue is for information only, and should not be changed.
Under, specify the number of seconds the monitor will wait each time it contacts the cluster or clusters to get health information.
Theis not used with the default nodepnt and nodecnt monitors. This value might be used for some custom monitors.
Specify Linux as the platform that you want to be monitored by the health monitor and whether you want the monitor enabled for the selected clusters.
Thefield specifies a monitor-specific string value that is passed to the monitor as a startup parameter.
The nodepnt and nodecnt monitors do not support optional parameters.
Clickto save your settings.
NOTE:See the BCC NDK documentation for more information on creating custom failover policies.