On 01/19/2012 09:45 AM, Oren Nechushtan wrote:
> Hi,
> I have a corosync API question, more techniquely: cman+pacemaker+corosync.
>
> Is there an analogue command to heartbeat cl_status command?
> This command was used for testing if a specific interface is working
> properly or not.
> The use case is to detect if one of the interfaces used by corosync
> (multi-homed configuration) is not working properly
> - display warning
> - trigger a pacemaker resource exception handling: resource changes
> interface if another interface is working fine
>
> There are many ways to test this externally, but I currently failed to
> find a specific corosync command for doing this.
> This should catch:
> - ifconfig down on either nodes
> - Link down on either nodes
>
> The configuration is
> Two nodes
> Two sync interfaces
> Cross cables
>
There is a very poorly designed API called
cs_error_t
corosync_cfg_ring_status_get (
corosync_cfg_handle_t cfg_handle,
char ***interface_names,
char ***status,
unsigned int *interface_count)
You can see how to use this in
tools/corosync-cfgtool.c:79 (in master)
Regards
-steve
> Just for the record I am familiar with heartbeat and started using
> corosync several month ago.
>
> Versions:
> Linux 1 2.6.32-220.2.1.el6.i686 #1 SMP Thu Dec 22 18:50:52 GMT 2011 i686
> i686 i386 GNU/Linux
>
> corosync-1.4.1-4.el6.i686
> corosynclib-1.4.1-4.el6.i686
> pacemaker-1.1.6-3.el6.i686
> pacemaker-libs-1.1.6-3.el6.i686
> pacemaker-cluster-libs-1.1.6-3.el6.i686
> pacemaker-cli-1.1.6-3.el6.i686
> cman-3.0.12.1-23.el6.i686
>
> Thanks in advance,
> Oren
>
>
> _______________________________________________
> discuss mailing list
> discuss@xxxxxxxxxxxx
> http://lists.corosync.org/mailman/listinfo/discuss
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
