Show Table of Contents
11.2. Configuring SNMP with the Red Hat High Availability Add-On
To configure SNMP with the Red Hat High Availability Add-On, perform the following steps on each node in the cluster to ensure that the necessary services are enabled and running.
- To use SNMP traps with the Red Hat High Availability Add-On, the
snmpdservice is required and acts as the master agent. Since thefoghornservice is the subagent and uses the AgentX protocol, you must add the following line to the/etc/snmp/snmpd.conffile to enable AgentX support:master agentx
- To specify the host where the SNMP trap notifications should be sent, add the following line to the to the
/etc/snmp/snmpd.conffile:trap2sink host
For more information on notification handling, see thesnmpd.confman page. - Make sure that the
snmpddaemon is enabled and running by executing the following commands:#
chkconfig snmpd on#service snmpd start - If the
messagebusdaemon is not already enabled and running, execute the following commands:#
chkconfig messagebus on#service messagebus start - Make sure that the
foghorndaemon is enabled and running by executing the following commands:#
chkconfig foghorn on#service foghorn start - Execute the following command to configure your system so that the
COROSYNC-MIBgenerates SNMP traps and to ensure that thecorosync-notifyddaemon is enabled and running:#
echo "OPTIONS=\"-d\" " > /etc/sysconfig/corosync-notifyd#chkconfig corosync-notifyd on#service corosync-notifyd 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
foghorn service and translated into SNMPv2 traps. These traps are then passed to the host that you defined with the trapsink entry to receive SNMPv2 traps.

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.