Re: Cluster config with two nodes - quorum-policy

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

 



Forgot to cc the list.

On Wed, Feb 20, 2013 at 5:31 PM, Dan Frincu <df.cluster@xxxxxxxxx> wrote:
> Hi,
>
> On Wed, Feb 20, 2013 at 12:55 PM, ml ml <mliebherr99@xxxxxxxxxxxxxx> wrote:
>> Hello List,
>>
>> i have a two nodes, both have 4 NICs
>> - 2x WAN (bonding)
>> - 2x LAN (bonding)
>>
>> This is my property configuration:
>>
>> property $id="cib-bootstrap-options" \
>>         dc-version="1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b" \
>>         cluster-infrastructure="openais" \
>>         expected-quorum-votes="2" \
>>         stonith-enabled="false" \
>>         no-quorum-policy="ignore" \
>>         default-action-timeout="60" \
>>         last-lrm-refresh="1361196271"
>
> This is the pacemaker related configuration, it's of no concern to your query.
>
> You need to define 2 interface directives in
> /etc/corosync/corosync.conf, one for each of your IP's.
> Something like:
>
> On node1:
>         # This specifies the mode of redundant ring, which may be
> none, active, or passive.
>         rrp_mode: passive
> totem {
>         version: 2
>         secauth: off
>         threads: 0
>         interface {
>                 ringnumber: 0
>                 bindnetaddr: 192.168.1.1 # LAN BOND IP
>                 mcastaddr: 226.94.1.1
>                 mcastport: 5405
>                 ttl: 1
>         }
>         interface {
>                 ringnumber: 1
>                 bindnetaddr: 1.2.3.4 # WAN BOND IP
>                 mcastaddr: 226.94.1.2
>                 mcastport: 5405
>                 ttl: 1
>         }
> }
>
> On node2:
>         # This specifies the mode of redundant ring, which may be
> none, active, or passive.
>         rrp_mode: passive
> totem {
>         version: 2
>         secauth: off
>         threads: 0
>         interface {
>                 ringnumber: 0
>                 bindnetaddr: 192.168.1.2 # LAN BOND IP
>                 mcastaddr: 226.94.1.1
>                 mcastport: 5405
>                 ttl: 1
>         }
>         interface {
>                 ringnumber: 1
>                 bindnetaddr: 1.2.3.5 # WAN BOND IP
>                 mcastaddr: 226.94.1.2
>                 mcastport: 5405
>                 ttl: 1
>         }
> }
>
> After starting corosync with this configuration, you should see both
> rings as active in the output of corosync-cfgtool -s.
>
> HTH,
> Dan
>
>>
>>
>> How can i now configure corosync to check its other node over WAN and LAN?
>>
>> If i now cut of the monitornig link i get a split cluster. Can i
>> somehow have a two way monitoring way and maybe also ping my gateway
>> to see if its alone or cut off?
>>
>>
>> Thanks,
>> Mario
>> _______________________________________________
>> discuss mailing list
>> discuss@xxxxxxxxxxxx
>> http://lists.corosync.org/mailman/listinfo/discuss
>
>
>
> --
> Dan Frincu
> CCNA, RHCE



-- 
Dan Frincu
CCNA, RHCE
_______________________________________________
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