[Pacemaker] handling snmp trap with crm_mon

[Junko IKEDA]

Hi,

I try to handle SNMP trap with crm_mon.
It seems that the latest crm_mon requires net-snmp 5.4 for enabling SNMP, so
I built net-snmp 5.4 on Red Hat, and rebuild Pacemaker 1.0.2 --with-snmp.

Usage is, just set "-S <target>" ?
# crm_mon -S 192.168.16.18

I set SNMP manager's IP address(192.168.16.18) as <target>, but nothing
happen during some events, like starting resources or fail over ...
Should I edit some SNMP configuration files, too?

When I call the following command from Pacemaker server(192.168.16.204),
SNMP manager can notice it.

* Pacemaker server;
# snmptrap -v 2c -c public 192.168.16.18 '' .1.3.6.1.2.1.1.3.0

* SNMP manager(/var/log/snmptrap.log);
snmptrapd[13151]: 2009-02-25 15:40:30 <UNKNOWN> [UDP:
[192.168.16.204]:32772]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks:
(18192695) 2 days, 2:32:06.95      SNMPv2-MIB::snmpTrapOID.0 = OID:
DISMAN-EVENT-MIB::sysUpTimeInstance

Does crm_mon also use LINUX-HA-MIB.mib as the same as hbagent?

I think SNMP function is also included in pacemaker-pygui, is there any
differences between pygui and crm_mon?

Best Regards,
Junko Ikeda

NTT DATA INTELLILINK CORPORATION