Installation guide

fenceNo d eName - name of the fenced node
fenceNo d eID - node id of the fenced node
fenceR esult - the result of the fence operation (0 for success, -1 for something went wrong, -
2 for no fencing methods defined)
rg managerServi ceStateC hang e
This trap occurs when the state of a cluster service changes. The notification includes the
following fields:
rg managerServi ceName - the name of the service, which includes the service type (for
example, service: fo o or vm:fo o ).
rg managerServi ceState - the state of the service. This excludes transitional states such as
starting and sto ppi ng to reduce clutter in the traps.
rg managerServi ceFl ag s - the service flags. There are currently two supported flags:
fro zen, indicating a service which has been frozen using cl usvcad m -Z, and parti al ,
indicating a service in which a failed resource has been flagged as no n-criti cal so that
the resource may fail and its components manually restarted without the entire service being
affected.
rg managerServi ceC urrentOwner - the service owner. If the service is not running, this will
be (no ne).
rg managerServi ceP revi o usO wner - the last service owner, if known. If the last owner is
not known, this may indicate (no ne).
The co ro sync-no d i fyd daemon generates the following traps:
co ro syncNoti cesNod eStatus
This trap occurs when a node joins or leaves the cluster. The notification includes the following
fields:
co ro syncO bjectsNo d eName - node name
co ro syncO bjectsNo d eID - node id
co ro syncO bjectsNo d eAd d ress - node IP address
co ro syncO bjectsNo d eStatus - node status (jo i ned or left)
co ro syncNoti cesQuo rumStatus
This trap occurs when the quorum state changes. The notification includes the following fields:
co ro syncO bjectsNo d eName - node name
co ro syncO bjectsNo d eID - node id
co ro syncO bjectsQ uo rumStatus - new state of the quorum (quo rate or NO T q uo rate)
co ro syncNoti cesAppStatus
This trap occurs when a client application connects or disconnects from Corosync.
co ro syncO bjectsNo d eName - node name
co ro syncO bjectsNo d eID - node id
⁠Chapt er 1 0 . SNMP Configurat ion wit h t he Red Hat High Availabilit y Add- O n
159