The level of detail is good, but is there a question too?
On Tuesday, December 4, 2012, Dhiraj Hadkar wrote:
> Hello Andrew,
>
> I have Corosync version:
>
>
> [root@node1]# corosync -v
> Corosync Cluster Engine, version '1.4.4'
> Copyright (c) 2006-2009 Red Hat, Inc.
>
> [root@node2]# corosync -v
> Corosync Cluster Engine, version '1.4.4'
> Copyright (c) 2006-2009 Red Hat, Inc.
>
> 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.
>
>
> Details of my setup:
>
> /var/log/cluster/corosync.log contents:
>
> Dec 01 17:59:22 corosync [MAIN ] Corosync Cluster Engine ('1.4.4'):
> started and ready to provide service.
> Dec 01 17:59:22 corosync [MAIN ] Corosync built-in features: nss
> Dec 01 17:59:22 corosync [MAIN ] Successfully read main configuration
> file '/etc/corosync/corosync.conf'.
> Dec 01 17:59:22 corosync [TOTEM ] Initializing transport (UDP/IP Unicast).
> Dec 01 17:59:22 corosync [TOTEM ] Initializing transmit/receive security:
> libtomcrypt SOBER128/SHA1HMAC (mode 0).
> Dec 01 17:59:23 corosync [TOTEM ] The network interface [172.16.202.153]
> is now up.
> Dec 01 17:59:23 corosync [SERV ] Service engine loaded: corosync extended
> virtual synchrony service
> Dec 01 17:59:23 corosync [SERV ] Service engine loaded: corosync
> configuration service
> Dec 01 17:59:23 corosync [SERV ] Service engine loaded: corosync cluster
> closed process group service v1.01
> Dec 01 17:59:23 corosync [SERV ] Service engine loaded: corosync cluster
> config database access v1.01
> Dec 01 17:59:23 corosync [SERV ] Service engine loaded: corosync profile
> loading service
> Dec 01 17:59:23 corosync [SERV ] Service engine loaded: corosync cluster
> quorum service v0.1
> Dec 01 17:59:23 corosync [MAIN ] Compatibility mode set to whitetank.
> Using V1 and V2 of the synchronization engine.
> Dec 01 17:59:23 corosync [TOTEM ] adding new UDPU member {172.16.202.153}
> Dec 01 17:59:23 corosync [TOTEM ] adding new UDPU member {172.16.202.154}
>
>
> Corosync.conf:
>
> # Please read the corosync.conf.5 manual page
> compatibility: whitetank
>
> totem {
> version: 2
> secauth: off
> interface {
> member {
> memberaddr: 172.16.202.153
> }
> member {
> memberaddr: 172.16.202.154
> }
> ringnumber: 0
> bindnetaddr: 172.16.0.0
> mcastport: 5405
> ttl: 1
> }
> transport: udpu
> }
>
> logging {
> fileline: off
> to_logfile: yes
> to_syslog: yes
> logfile: /var/log/cluster/corosync.log
> debug: off
> timestamp: on
> logger_subsys {
> subsys: AMF
> debug: off
> }
> }
>
> Verification for config creation:
>
> [root@node1]# /sbin/ifconfig eth1 | grep "inet addr" | awk -F: '{print
> $2}' | awk '{print $1}'
> 172.16.202.153
> [root@node1]# ipcalc -n `ip addr show eth1 | grep 'inet ' |awk '{print
> $2}'` | awk -F= '{print $2}'
> 172.16.0.0
>
> [root@node2]# /sbin/ifconfig eth1 | grep "inet addr" | awk -F: '{print
> $2}' | awk '{print $1}'
> 172.16.202.154
> [root@node2 libqb]# ipcalc -n `ip addr show eth1 | grep 'inet ' |awk
> '{print $2}'` | awk -F= '{print $2}'
> 172.16.0.0
>
>
> [root@node1]# corosync-cfgtool -s
> Printing ring status.
> Local node ID -1714810708
> RING ID 0
> id = 172.16.202.153
> status = ring 0 active with no faults
>
> [root@node2 pacemaker]# corosync-cfgtool -s
> Printing ring status.
> Local node ID -1698033492
> RING ID 0
> id = 172.16.202.154
> status = ring 0 active with no faults
> [root@node2 pacemaker]#
>
> Thanks in Advance for advise,
> Best Regards,
> Dhir
>
>
>
>
> ________________________________
> 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.
> ________________________________
>
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org <javascript:;>
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
