10.4. SNMP Traps Produced by Red Hat High Availability Add-On

The foghorn daemon generates the following traps:

fenceNotifyFenceNode
This trap occurs whenever a fenced node attempts to fence another node. Note that this trap is only generated on one node - the node that attempted to perform the fence operation. The notification includes the following fields:
- fenceNodeName - name of the fenced node
- fenceNodeID - node id of the fenced node
- fenceResult - the result of the fence operation (0 for success, -1 for something went wrong, -2 for no fencing methods defined)
rgmanagerServiceStateChange
This trap occurs when the state of a cluster service changes. The notification includes the following fields:
- rgmanagerServiceName - the name of the service, which includes the service type (for example, service:foo or vm:foo).
- rgmanagerServiceState - the state of the service. This excludes transitional states such as starting and stopping to reduce clutter in the traps.
- rgmanagerServiceFlags - the service flags. There are currently two supported flags: frozen, indicating a service which has been frozen using clusvcadm -Z, and partial, indicating a service in which a failed resource has been flagged as non-critical so that the resource may fail and its components manually restarted without the entire service being affected.
- rgmanagerServiceCurrentOwner - the service owner. If the service is not running, this will be (none).
- rgmanagerServicePreviousOwner - the last service owner, if known. If the last owner is not known, this may indicate (none).

The corosync-nodifyd daemon generates the following traps:

corosyncNoticesNodeStatus
This trap occurs when a node joins or leaves the cluster. The notification includes the following fields:
- corosyncObjectsNodeName - node name
- corosyncObjectsNodeID - node id
- corosyncObjectsNodeAddress - node IP address
- corosyncObjectsNodeStatus - node status (joined or left)
corosyncNoticesQuorumStatus
This trap occurs when the quorum state changes. The notification includes the following fields:
- corosyncObjectsNodeName - node name
- corosyncObjectsNodeID - node id
- corosyncObjectsQuorumStatus - new state of the quorum (quorate or NOT quorate)
corosyncNoticesAppStatus
This trap occurs when a client application connects or disconnects from Corosync.
- corosyncObjectsNodeName - node name
- corosyncObjectsNodeID - node id
- corosyncObjectsAppName - application name
- corosyncObjectsAppStatus - new state of the application (connected or disconnected)