Hi,

I'm trying to make a configuration with Option 3, to avoid problems with 
corosync I had
with Option 0 (corosync + pacemaker plugin v0) . By the way, I tried the 
option 2 but
corosync did not start, but as the future is option 4 (not yet available 
if I well understand)
I choose to adopt option 3 for now.

With option 3, as it does not start , I would like to know if my 
corosync.conf is correct (see below)
because I replace pacemaker by corosync_cman in the "service" record, 
but how does it
know that it must work with pacemaker now ?

Thanks for help.
(Recall : I'm on RHEL6 with : corosync-1.2.3-21 cman-3.0.12-1 
pacemaker-1.1.2-2)
Alain

/_corosync.conf :_/
aisexec {
        user:   root
        group:  root
}

cluster {
        name: MYCLUSTER

        clusternodes {
                clusternode {
                        votes: 1
                        nodeid: 1
                        name: node0
                }
                clusternode {
                        votes: 1
                        nodeid: 2
                        name: node1
                }
        }
        cman {
                expected_votes: 2
                cluster_id: 1
                nodename: node0
                two_node: 1
                max_queued: 10
        }
}

service {
        name: corosync_cman
        ver:  0
}

quorum {
        provider:quorum_cman
}

totem {
        version: 2
        # How long before declaring a token lost (ms)
        token:          5000
        # How many token retransmits before forming a new configuration
        token_retransmits_before_loss_const: 20
        # How long to wait for join messages in the membership protocol (ms)
        join:           1000
        # How long to wait for consensus to be achieved before starting 
a new round of membership configuration (ms)
        consensus:      7500
        # Turn off the virtual synchrony filter
        vsftype:        none
        # Number of messages that may be sent by one processor on 
receipt of the token
        max_messages:   20
        # Disable encryption
        secauth:        off
        # How many threads to use for encryption/decryption
        threads:        0
        # Limit generated nodeids to 31-bits (positive signed integers)
        clear_node_high_bit: yes
        # Optionally assign a fixed node id (integer)
        # nodeid:         1
        # rrp_mode : set to active but automatically reset to none if 
only one network interface
        #            could be set alternatively to "passive" with 2 
network interfaces
        rrp_mode :       active
        interface {
                ringnumber: 0
                # The following three values need to be set based on 
your environment
                bindnetaddr: 18.20.0.0
                mcastaddr: 230.1.1.2
                mcastport: 5405
        }
 }
 logging {
        fileline: off
        to_syslog: yes
        to_stderr: no
        syslog_facility: daemon
        debug: on
        timestamp: on
 }

 amf {
        mode: disabled
 }
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to