| Event
|
Severity Level
|
Description
|
|---|
Remote cluster has faulted.
(Global Cluster Option)
|
Error
|
The trap for this event includes information on how to take over the global service groups running on the remote cluster before the cluster faulted.
|
Heartbeat is down.
|
Error
|
The connector on the local cluster lost its heartbeat connection to the remote cluster.
|
Remote cluster is in RUNNING state.
(Global Cluster Option)
|
Information
|
Local cluster has complete snapshot of the remote cluster, indicating the remote cluster is in the RUNNING state.
|
Heartbeat is "alive."
(Global Cluster Option)
|
Information
|
Self-explanatory.
|
User has logged on to VCS.
|
Information
|
A user log on has been recognized because a user logged on via Cluster Manager, or because a haxxx command was invoked.
|
| Event
|
Severity Level
|
Description
|
|---|
Resource state is unknown.
|
Warning
|
VCS cannot identify the state of the resource.
|
Resource monitoring has timed out.
|
Warning
|
Monitoring mechanism for the resource has timed out.
|
Resource is not going offline.
|
Warning
|
VCS cannot take the resource offline.
|
Health of cluster resource declined.
|
Warning
|
Used by agents to give additional information on the state of a resource. Health of the resource declined while it was online.
|
Resource went online by itself.
|
Warning (not for first probe)
|
The resource was brought online on its own.
|
Resource has faulted.
|
Error
|
Self-explanatory.
|
Resource is being restarted by agent.
|
Information
|
The resource is being restarted by its agent.
|
The health of cluster resource improved.
|
Information
|
Used by agents to give extra information about state of resource. Health of the resource improved while it was online.
|
Resource monitor time has changed.
|
Warning
|
This trap is generated when statistics analysis for the time taken by the monitor entry point of an agent is enabled for the agent. See VCS Agent Statistics for more information.
This trap is generated when the agent framework detects a sudden or gradual increase or decrease in the time taken to run the monitor entry point for a resource. The trap information contains details of the change in time required to run the monitor entry point and the actual times that were compared to deduce this change.
|
Resource is in ADMIN_WAIT state.
|
Error
|
The resource is in the admin_wait state. See Controlling Clean Behavior on Resource Faults for more information.
|
| Event
|
Severity Level
|
Description
|
|---|
Service group has faulted.
|
Error
|
Self-explanatory.
|
Service group concurrency violation.
|
SevereError
|
A failover service group has become online on more than one node in the cluster.
|
Service group has faulted and cannot be failed over anywhere.
|
SevereError
|
Specified service group has faulted on all nodes where group could be brought online, and there are no nodes to which the group can fail over.
|
Service group is online
|
Information
|
Self-explanatory.
|
Service group is offline.
|
Information
|
Self-explanatory.
|
Service group is autodisabled.
|
Information
|
VCS has autodisabled the specified group because one node exited the cluster.
|
Service group is restarting.
|
Information
|
Self-explanatory.
|
Service group is being switched.
|
Information
|
The service group is being taken offline on one node and being brought online on another.
|
Service group restarting in response to persistent resource going online.
|
Information
|
Self-explanatory.
|
The global service group is online/partial on multiple clusters.
(Global Cluster Option)
|
SevereError
|
A concurrency violation occurred for the global service group.
|
Attributes for global service groups are mismatched.
(Global Cluster Option)
|
Error
|
The attributes ClusterList, AutoFailOver, and Parallel are mismatched for the same global service group on different clusters.
|
