The level of detail is good, but is there a question too?<span></span><br><br>On Tuesday, December 4, 2012, Dhiraj Hadkar wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello Andrew,<br>
<br>
I have Corosync version:<br>
<br>
<br>
[root@node1]# corosync -v<br>
Corosync Cluster Engine, version '1.4.4'<br>
Copyright (c) 2006-2009 Red Hat, Inc.<br>
<br>
[root@node2]# corosync -v<br>
Corosync Cluster Engine, version '1.4.4'<br>
Copyright (c) 2006-2009 Red Hat, Inc.<br>
<br>
This I am inclined to use for unicast support. Would this have issues when I try with RHEL 5.4, also which is the best suited Pacemaker version for this version of corosync.<br>
<br>
<br>
Details of my setup:<br>
<br>
/var/log/cluster/corosync.log contents:<br>
<br>
Dec 01 17:59:22 corosync [MAIN ] Corosync Cluster Engine ('1.4.4'): started and ready to provide service.<br>
Dec 01 17:59:22 corosync [MAIN ] Corosync built-in features: nss<br>
Dec 01 17:59:22 corosync [MAIN ] Successfully read main configuration file '/etc/corosync/corosync.conf'.<br>
Dec 01 17:59:22 corosync [TOTEM ] Initializing transport (UDP/IP Unicast).<br>
Dec 01 17:59:22 corosync [TOTEM ] Initializing transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).<br>
Dec 01 17:59:23 corosync [TOTEM ] The network interface [172.16.202.153] is now up.<br>
Dec 01 17:59:23 corosync [SERV ] Service engine loaded: corosync extended virtual synchrony service<br>
Dec 01 17:59:23 corosync [SERV ] Service engine loaded: corosync configuration service<br>
Dec 01 17:59:23 corosync [SERV ] Service engine loaded: corosync cluster closed process group service v1.01<br>
Dec 01 17:59:23 corosync [SERV ] Service engine loaded: corosync cluster config database access v1.01<br>
Dec 01 17:59:23 corosync [SERV ] Service engine loaded: corosync profile loading service<br>
Dec 01 17:59:23 corosync [SERV ] Service engine loaded: corosync cluster quorum service v0.1<br>
Dec 01 17:59:23 corosync [MAIN ] Compatibility mode set to whitetank. Using V1 and V2 of the synchronization engine.<br>
Dec 01 17:59:23 corosync [TOTEM ] adding new UDPU member {172.16.202.153}<br>
Dec 01 17:59:23 corosync [TOTEM ] adding new UDPU member {172.16.202.154}<br>
<br>
<br>
Corosync.conf:<br>
<br>
# Please read the corosync.conf.5 manual page<br>
compatibility: whitetank<br>
<br>
totem {<br>
version: 2<br>
secauth: off<br>
interface {<br>
member {<br>
memberaddr: 172.16.202.153<br>
}<br>
member {<br>
memberaddr: 172.16.202.154<br>
}<br>
ringnumber: 0<br>
bindnetaddr: 172.16.0.0<br>
mcastport: 5405<br>
ttl: 1<br>
}<br>
transport: udpu<br>
}<br>
<br>
logging {<br>
fileline: off<br>
to_logfile: yes<br>
to_syslog: yes<br>
logfile: /var/log/cluster/corosync.log<br>
debug: off<br>
timestamp: on<br>
logger_subsys {<br>
subsys: AMF<br>
debug: off<br>
}<br>
}<br>
<br>
Verification for config creation:<br>
<br>
[root@node1]# /sbin/ifconfig eth1 | grep "inet addr" | awk -F: '{print $2}' | awk '{print $1}'<br>
172.16.202.153<br>
[root@node1]# ipcalc -n `ip addr show eth1 | grep 'inet ' |awk '{print $2}'` | awk -F= '{print $2}'<br>
172.16.0.0<br>
<br>
[root@node2]# /sbin/ifconfig eth1 | grep "inet addr" | awk -F: '{print $2}' | awk '{print $1}'<br>
172.16.202.154<br>
[root@node2 libqb]# ipcalc -n `ip addr show eth1 | grep 'inet ' |awk '{print $2}'` | awk -F= '{print $2}'<br>
172.16.0.0<br>
<br>
<br>
[root@node1]# corosync-cfgtool -s<br>
Printing ring status.<br>
Local node ID -1714810708<br>
RING ID 0<br>
id = 172.16.202.153<br>
status = ring 0 active with no faults<br>
<br>
[root@node2 pacemaker]# corosync-cfgtool -s<br>
Printing ring status.<br>
Local node ID -1698033492<br>
RING ID 0<br>
id = 172.16.202.154<br>
status = ring 0 active with no faults<br>
[root@node2 pacemaker]#<br>
<br>
Thanks in Advance for advise,<br>
Best Regards,<br>
Dhir<br>
<br>
<br>
<br>
<br>
________________________________<br>
This email (message and any attachment) is confidential and may be privileged. If you are not certain that you are the intended recipient, please notify the sender immediately by replying to this message, and delete all copies of this message and attachments. Any other use of this email by you is prohibited.<br>
________________________________<br>
<br>
<br>
<br>
_______________________________________________<br>
Pacemaker mailing list: <a href="javascript:;" onclick="_e(event, 'cvml', 'Pacemaker@oss.clusterlabs.org')">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
</blockquote>