VCS alerts are identified by the alert ID, which is comprised of the following elements:
alert_type
—The type of the alert
See Types of alerts.
cluster
—The cluster on which the alert was generated
system
—The system on which this alert was generated
object
—The name of the VCS object for which this alert was generated. This could be a cluster or a service group.
Alerts are generated in the following format:
alert_type-cluster-system-object
This is an alert of type GNOFAILA generated on cluster Cluster1 for the service group oracle_grp.
VCS generates the following types of alerts.
Some reasons why a global group may not be able to fail over to a remote cluster:
Alerts require user intervention. You can respond to an alert in the following ways:
haalert
command to delete the alert. You must provide a comment as to why you are deleting the alert; VCS logs the comment to engine log.
An administrative alert will continue to live if none of the above actions are performed and the VCS engine (HAD) is running on at least one node in the cluster. If HAD is not running on any node in the cluster, the administrative alert is lost.
This section describes the actions you can perform on the following types of alerts:
VCS deletes a CFAULT alert when the faulted cluster goes back to the running state
VCS deletes the GNOFAILA and GNOFAIL alerts in response to the following events:
VCS may report a concurrency violation when you add a cluster to the ClusterList of the service group. A concurrency violation means that the service group is online on two nodes simultaneously.
Recommended Action: Verify the state of the service group in each cluster before making the service group global.