Hi Jan,
I tried to setup 1 cluster with 3 nodes to test the
unicast(udpu)configuration:
totem {
version: 2
token: 3000
token_retransmits_before_loss_const: 10
secauth: off
threads: 0
interface {
member {
memberaddr: 10.x.x.1
}
member {
memberaddr: 10.x.x.2
}
member {
memberaddr: 172.x.x.1
}
ringnumber: 0
bindnetaddr: <node ip>
mcastaddr: 226.94.1.1
mcastport: 5405
ttl: 100
}
transport: udpu
}
basically i followed below example for "udpu":
https://github.com/fghaas/corosync/blob/master/conf/corosync.conf.example.udpu
but it failed because Corosync need to add "mcastaddr" attribute.
Aafter add "mcastaddr" with value " 226.94.1.1", the nodes which in the sam
subnetwork: 10.x.x.1, 10.x.x.2 can show up in the "crm status", but the
node 172.x.x.1 cannot join this cluster.
btw: i tried to set ttl to 1 and 100, all failed.
any clue about it?
thanks,
Emre
2013/10/7 Jan Friesse <[email protected]>
> Emre,
> different subnets works without any problem as long as you set proper
> ttl (man corosync.conf / ttl).
>
> Heartbeat is integral part of totem protocol so there is nothing like
> separated heartbeat and transport protocol. Just use transport key
> (udp/udpu).
>
> Regards,
> Honza
>
> Emre He napsal(a):
> > Hi,
> >
> > i want to know if Corosync support unicast for cluster nodes heartbeat in
> > different sub-network? i google and found some pages said we can use
> below
> > configuration for unicast:
> >
> https://github.com/fghaas/corosync/blob/master/conf/corosync.conf.example.udpu
> >
> > but i cannot find any info about heartbeat styles: unicast or multicast
> or
> > broadcast on Corosync official wiki pages, where could i find this
> official
> > info?
> >
> > thanks,
> > Emre
> >
> >
> >
> > _______________________________________________
> > discuss mailing list
> > [email protected]
> > http://lists.corosync.org/mailman/listinfo/discuss
> >
>
>
_______________________________________________
discuss mailing list
[email protected]
http://lists.corosync.org/mailman/listinfo/discuss
