The cluster probe enables failover support for profiles in the supported monitoring probes. Profiles of supported monitoring probes can be associated with different shared resource groups and follow that group even if it is transferred to another cluster node.
The cluster probe updates the changes that are made to the profile setup of the other monitoring probes also installed on the nodes of a cluster. When any monitoring probe profile is updated, the changes must be implemented on the probe that runs on the node which is in control of the associated resource group. The cluster probe automatically updates most of the changes of the monitoring probe profiles. However, general probe parameters must be updated manually on each of the nodes in the cluster.
A shared resource group is visible under the active cluster node in the navigation pane of the cluster probe's Configure GUI for the node that currently controls the shared resources. When one of the cluster nodes fails, the control of all of the shared resources is transferred to another functioning node. The shared resource group is then visible under the new functioning node in the navigation pane of the cluster probe's Configure GUI. The shared resource group failover alarm does not clear until the resource group moves back to the original cluster node.
You can view the cluster node status when you select the cluster. However, you can view the related group metrics only under that particular cluster node to which the shared resource group belongs.
Consider the following points for creating monitoring profiles for shared resources.
- A clustered probe must be deployed on all nodes of the cluster
- All nodes in the cluster must have the same monitoring probes (and versions) with the same general configuration.