Hi Steven, Sato-san & all SNMP interested folk

I have done some work (with bits of Sato-san's snmp code in it) to get
snmp traps to work.

To get the different cluster programs working in a consistent way
it has been agreed to use dbus to send signals and for "foghorn"
(http://git.fedorahosted.org/git/foghorn.git) to map the dbus
signals into snmp traps.

In corosync we also want to support plain snmp using agentx
(like what Sato-san did).

If you are interested, the work I have done so-far is here:
http://gitorious.org/corosync/corosync-notify

I have not as yet included Sato-san's link status (just to keep it
simple).

Feel free to contribute, just note I am going on holiday
for 2 weeks and Steven will continue this work.

Read the TODO section to see how to run/test and what needs doing.

Regards
Angus Salkeld

Example dbus signals output from "dbus-monitor --system"

signal sender=:1.158 -> dest=(null destination) serial=2 
path=/com/redhat/cluster/corosync; interface=com.redhat.cluster.corosync; 
member=ApplicationConnectionState
   string "troll"
   int32 23374016
   string "corosync-notify:1831:12"
   string "connected"
signal sender=:1.158 -> dest=(null destination) serial=3 
path=/com/redhat/cluster/corosync; interface=com.redhat.cluster.corosync; 
member=ApplicationConnectionState
   string "troll"
   int32 23374016
   string "corosync-notify:1831:13"
   string "disconnected"
signal sender=:1.158 -> dest=(null destination) serial=4 
path=/com/redhat/cluster/corosync; interface=com.redhat.cluster.corosync; 
member=QorumState
   string "troll"
   int32 23374016
   string "quorate"
signal sender=:1.158 -> dest=(null destination) serial=5 
path=/com/redhat/cluster/corosync; interface=com.redhat.cluster.corosync; 
member=NodeState
   string "r1"
   int32 1533323456
   string "192.168.100.91"
   string "left"

_______________________________________________
Openais mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/openais

Reply via email to