Re: Link status in multi-homed setup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks

I've modified your patch a bit and posted it directly from git against
master.

Regards
-steve

On 01/25/2012 06:24 AM, Oren Nechushtan wrote:
> Hi,
> Here is a quick patch extending corosync-cfgtool -s allowing
>  Detection of faults on a single interface
>  Exit return code
>  
> I hope you'll find it useful
> Also, supporting <interface name> and <ring id> would be nice
> (currently, it uses corosync-cfgtool -i <interface static ip> -s, as in
> normal -s)
>  
> Best,
> Oren
>  
>> Date: Thu, 19 Jan 2012 12:51:11 -0700
>> From: sdake@xxxxxxxxxx
>> To: theoren28@xxxxxxxxxxx
>> CC: discuss@xxxxxxxxxxxx
>> Subject: Re:  Link status in multi-homed setup
>>
>> 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

_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss


[Index of Archives]     [Linux Clusters]     [Corosync Project]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Linux Kernel]     [Linux SCSI]     [X.Org]

  Powered by Linux