On 01/11/2011 10:01 PM, MANISH OBERAI wrote:
>  
> Hello
>  
>         I am trying to create SLES 11 host and RHEL 6 host cluster using
> Pacemaker and Corosync. When I start cluster these 2 node does not join.
> Providing you the config details :-
>  
>         RHEL Host heartbeat ports for cluster communication : 172.16.0.1
> & 172.16.0.2 (with netmask 255.255.255.0)
>         SLES Host heartbeat ports for cluster communication : 172.16.0.5
> & 172.16.0.6 (with netmask 255.255.255.0)
>  
>         RHEL Host own address : 10.184.16.117 (incdcs117)
>         SLES Host own address : 10.184.16.119 (incdcs119)
>  
>         _*Corosync.conf file on both the nodes : -*_
>         compatibility: whitetank
>         totem {
>         version: 2
>         secauth: off
>         threads: 0
>         interface {
>                 ringnumber: 0
>                         bindnetaddr: 172.16.0.0
>                         mcastaddr: 226.94.1.1
>                         mcastport: 4000
>                  }
>                 }
>  
>         logging {
>         fileline: off
>         to_stderr: no
>         to_logfile: yes
>         to_syslog: yes
>         logfile: /var/log/cluster/corosync.log
>         debug: on
>         timestamp: on
>         logger_subsys {
>                 subsys: AMF
>                 debug: off
>         }
>         }
> 

could you run corosync-blackbox and send the output to the list?

Thanks!
-steve


>         amf {
>         mode: disabled
>         }
>         aisexec {
>                 user: root
>                 group: root
>                 }
>         service {
>                 # Load the Pacemaker Cluster Resource Manager
>                 name: pacemaker
>                 ver: 0
>                 }
>  
>  
> _*Output of crm_mon -1 (of SLES node)*_
>         incdcs119:~ # crm_mon -1
>         ============
>         Last updated: Wed Jan 12 10:29:59 2011
>         Stack: openais
>         Current DC: incdcs119 - partition WITHOUT quorum
>         Version: 1.1.2-2e096a41a5f9e184a1c1537c82c6da1093698eb5
>         1 Nodes configured, 2 expected votes
>         0 Resources configured.
>         ============
>  
>         Online: [ incdcs119 ]
>  
> _*Output of crm_mon -1 (of RHEL node)*_
>         [root@incdcs117 ~]# crm_mon -1
>         ============
>         Last updated: Wed Jan 12 10:31:26 2011
>         Stack: openais
>         Current DC: incdcs117 - partition WITHOUT quorum
>         Version: 1.1.2-f059ec7ced7a86f18e5490b67ebf4a0b963bccfe
>         1 Nodes configured, 2 expected votes
>         0 Resources configured.
>         ============
>  
>         Online: [ incdcs117 ]
>  
>  
>      Help is really appeciated. Why these 2 node are joining in the same
> cluster ?
>  
> *************************************************
> Best Regards,
> Manish Oberai
>  
>  
> -----Original Message-----
> From: Steven Dake [_mailto:[email protected]_]
> Sent: Tuesday, January 11, 2011 10:51 PM
> To: MANISH OBERAI
> Cc: [email protected]
> Subject: Re: [Openais] Query related to Corosync
>  
> On 01/11/2011 04:46 AM, MANISH OBERAI wrote:
>> Hello
>>         Is it possible to build cluster of  SLES host and RHEL host in
>> the same Corosync configuration ?
>> 
>  
> That will work just fine.  Pacemaker may have other considerations - I'd
> recommend asking on the Pacemaker list if you have questions about that
> topic.
>  
> We also test 32/64 bit bitsize cross communication support, and we have
> some basic support for big endian/little endian cross support, but the
> BE/LE communication needs a little work because of lack of testing hardware.
>  
> Regards
> -steve
>  
>> *************************************************
>> Best Regards,
>> *Manish Oberai*
>> 
>> 
>>
>>
>>
>> _______________________________________________
>> 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

Reply via email to