Installation guide

# chkco nfi g fo g ho rn o n
# servi ce fog ho rn start
6. Execute the following command to configure your system so that the C O R O SY NC -MIB
generates SNMP traps and to ensure that the co ro sync-noti fyd daemon is enabled and
running:
# echo "O P T IO NS= \"-d \" " > /etc/sysco nfi g /co ro sync-noti fyd
# chkco nfi g co ro sync-noti fyd o n
# servi ce coro sync-no ti fyd start
After you have configured each node in the cluster for SNMP and ensured that the necessary
services are running, D-bus signals will be received by the fog ho rn service and translated into
SNMPv2 traps. These traps are then passed to the host that you defined with the trapsi nk entry to
receive SNMPv2 traps.
10.3. Forwarding SNMP t raps
It is possible to forward SNMP traps to a machine that is not part of the cluster where you can use the
snmptrapd daemon on the external machine and customize how to respond to the notifications.
Perform the following steps to forward SNMP traps in a cluster to a machine that is not one of the
cluster nodes:
1. For each node in the cluster, follow the procedure described in Section 10.2, “ Configuring
SNMP with the Red Hat High Availability Add-On” , setting the trap2si nk host entry in the
/etc/snmp/snmpd . co nf file to specify the external host that will be running the snmptrapd
daemon.
2. On the external host that will receive the traps, edit the /etc/snmp/snmptrapd . co nf
configuration file to specify your community strings. For example, you can use the following
entry to allow the snmptrapd daemon to process notifications using the publ i c community
string.
authCommunity log,execute,net public
3. On the external host that will receive the traps, make sure that the snmptrapd daemon is
enabled and running by executing the following commands:
# chkco nfi g snmptrapd o n
# servi ce snmptrapd start
For further information on processing SNMP notifications, see the snmptrapd . co nf man page.
10.4. SNMP T raps Produced by Red Hat High Availabilit y Add-On
The fo g ho rn daemon generates the following traps:
fenceNo ti fyFenceNo d e
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:
Red Hat Ent erprise Linux 6 Clust er Administ rat ion
158