Le 19/09/2013 01:21, David Lang a écrit :
since I see a lot of pacemaker related discussion happening here, i'll
ask the question here as well as the 'official' corosync list :-)
I'm trying to get a cluster up and running without using multicast, I've
made my cluster.conf be the following, but the systems are still sending
to the multicast address and not seeing each other as a result.
Is there something that I did wrong in creating the cman segment of the
file? unforutunantly the cluster.conf man page just referrs to the
corosync.conf man page, but the two files use different config styles.
If not, what else do I need to do to disable multicast and just use udpu?
<cluster config_version="8" name="qedgep3">
<fence_daemon/>
<clusternodes>
<clusternode name="pprdeliea304" nodeid="1">
<fence>
</fence>
</clusternode>
<clusternode name="pprdeliea305" nodeid="2">
<fence>
</fence>
</clusternode>
</clusternodes>
<cman two_node="1" expected_votes="1">
<totem vsftype="none" token="5000"
token_retransmits_before_loss_const="10" join="60" consensus="4800"
rrp_mode="none" transport="udpu">
<interface ringnumber="0" bindnetaddr="10.1.18.0" mcastport="5405"
ttl="1"
<member memberaddr="10.1.18.177" />
<member memberaddr="10.1.18.178" />
</interface>
</totem>
</cman>
<fencedevices/>
<rm>
<failoverdomains/>
<resources/>
</rm>
</cluster>
Well I don't know how you ended-up with such a cluster.conf file, here
is mine and it uses udpu + rrp (redundant rings)
<cluster config_version="14" name="pcmk1">
<fence_daemon/>
<clusternodes>
<clusternode name="node01.local" nodeid="1">
<altname name="node01_alt.local" port="5405"/>
<fence>
<method name="pcmk-redirect">
<device name="pcmk" port="node01.local"/>
</method>
</fence>
</clusternode>
<clusternode name="node02.local" nodeid="2">
<altname name=""node02_alt.local" port="5405"/>
<fence>
<method name="pcmk-redirect">
<device name="pcmk" port="node02.local"/>
</method>
</fence>
</clusternode>
</clusternodes>
<cman keyfile="/etc/corosync/authkey" port="1337" transport="udpu"/>
<fencedevices>
<fencedevice agent="fence_pcmk" name="pcmk"/>
</fencedevices>
<rm>
<failoverdomains/>
<resources/>
</rm>
<totem rrp_mode="active"/>
</cluster>
FYI, here are the commands used to create this configuration:
# Define the cluster
ccs -f /etc/cluster/cluster.conf --createcluster pcmk1
# Create redundant rings
ccs -f /etc/cluster/cluster.conf --addnode node01.local
ccs -f /etc/cluster/cluster.conf --addalt node01.local node01_alt.local
ccs -f /etc/cluster/cluster.conf --addnode node02.local
ccs -f /etc/cluster/cluster.conf --addalt node02.local node02_alt.local
# Delegate fencing
ccs -f /etc/cluster/cluster.conf --addmethod pcmk-redirect node01.local
ccs -f /etc/cluster/cluster.conf --addmethod pcmk-redirect node02.local
ccs -f /etc/cluster/cluster.conf --addfencedev pcmk agent=fence_pcmk
ccs -f /etc/cluster/cluster.conf --addfenceinst pcmk node01.local
pcmk-redirect port=node01.local
ccs -f /etc/cluster/cluster.conf --addfenceinst pcmk node02.local
pcmk-redirect port=node02.local
# Encrypt rings and define port (important to stick with default port if
SELinux=enforcing)
ccs -f /etc/cluster/cluster.conf --setcman
keyfile="/etc/corosync/authkey" transport="udpu" port="5405"
# Finally, choose your favorite rrp_mode
ccs -f /etc/cluster/cluster.conf --settotem rrp_mode="active"
And finally, my 0.02$ post explaining how to move from the "the plugin"
to a cman-based stack:
http://floriancrouzat.net/2013/04/rhel-6-4-pacemaker-1-1-8-adding-cman-support-and-getting-rid-of-the-plugin/
--
Cheers,
Florian Crouzat
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
