My corosync.conf file is :
totem {
version: 2
secauth: off
threads: 0
interface {
ringnumber: 0
bindnetaddr: 192.168.10.0
mcastaddr: 226.95.1.1
mcastport: 5405
}
}
logging {
fileline: off
to_stderr: no
to_file: yes
logfile: /tmp/corosync.log
debug: on
timestamp: on
logger_subsys {
subsys: TOTEM
debug: on
}
}
amf {
mode: disabled
}
I see that the nodes are not forming a cluster. Please help.
Thanks,
Smitha
-----Original Message-----
From: Steven Dake [mailto:[email protected]]
Sent: Tuesday, July 06, 2010 3:03 PM
To: Radhakrishnan, Smitha
Cc: [email protected]
Subject: Re: [Openais] Using corosync on second network interface card
On 07/06/2010 02:08 AM, Radhakrishnan, Smitha wrote:
> Hello,
>
> Iam configuring corosync using a second network interface card. But the
> issue that Iam facing is that, corosync is sending messages only to
> multicast
>
> address. Corosync is not able to reach the other node in the cluster
> which also uses a second network interface card. I suspect corosync is
> not forming a cluster here.
>
> On Node 1 I got :
>
> corosync-cfgtool -s
>
> Printing ring status.
>
> Local node ID 235579584
>
> RING ID 0
>
> id = 192.168.10.14
>
> status = ring 0 active with no faults
>
> and on Node 2 :
>
> corosync-cfgtool -s
>
> Printing ring status.
>
> Local node ID 202025152
>
> RING ID 0
>
> id = 192.168.10.12
>
> status = ring 0 active with no faults
>
> Could you please let me know whether corosync detects only eth0?
>
> Thanks in advance.
>
> Thanks,
>
> Smitha
>
What does your corosync.conf file look like?
Regards
-steve
>
>
> _______________________________________________
> Openais mailing list
> [email protected]
> https://lists.linux-foundation.org/mailman/listinfo/openais
_______________________________________________
Openais mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/openais
