Sponsored Content
Full Discussion: Cluster configuration file
Operating Systems Linux Red Hat Cluster configuration file Post 302771279 by mastansaheb on Wednesday 20th of February 2013 06:47:21 AM
Old 02-20-2013
Cluster configuration file

Hi Everybody,


I would like to know meaning of following parameters in cluster.conf file in linux

Code:
<device name="blade_fence" blade="2" option="off"
<clusternode name="Blade1-int" votes="1" nodeid="1">

what do you mean by "option=off" and "votes=1"

Thanks

Last edited by zaxxon; 02-20-2013 at 08:39 AM..
 

10 More Discussions You Might Find Interesting

1. High Performance Computing

Building a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris

Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris. More... (0 Replies)
Discussion started by: Linux Bot
0 Replies

2. High Performance Computing

SUN Cluster Vs Veritas Cluster

Dear All, Can anyone explain about Pros and Cons of SUN and Veritas Cluster ? Any comparison chart is highly appreciated. Regards, RAA (4 Replies)
Discussion started by: RAA
4 Replies

3. Solaris

SC3.2 issue - cluster transport configuration not right - resulting fail

I am trying to set up a two host cluster. trouble is with the cluster transport configuration. i'm using e1000g2 and g3 for the cluster transport. global0 and global1 are my two nodes, and I am running the scinstall from global1. i think i should be expecting, is this: The following... (19 Replies)
Discussion started by: frustin
19 Replies

4. Solaris

Sun cluster and Veritas cluster question.

Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC. Am thinking how to migrate to sun cluster setup instead. My plan as follows leave the existing vcs intact as a fallback plan. Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies

5. AIX

HACMP 5.4.1 Two-Node-Cluster-Configuration-Assistant fails

This post just as a follow-up for thread https://www.unix.com/aix/115548-hacmp-5-4-aix-5300-10-not-working.html: there was a bug in the clcomdES that would cause the Two-Node-Cluster-Configuration-Assistant to fail even with a correct TCP/IP adapter setup. That affected HACMP 5.4.1 in combinatin... (0 Replies)
Discussion started by: shockneck
0 Replies

6. Solaris

Cluster interconnect, adapter configuration

Hello I have problem with scinstall. I found information that i should`t configure public network before using scinstall. Each node configuration: 4 node, 3 network adapter on each node. 1 for public adapter and 2 for cluster interconnect. Two switches. After scinstall first node is... (1 Reply)
Discussion started by: time0ut
1 Replies

7. Solaris

In cluster configuration ora* VGs are not controlled by VCS

Need some one to explain "In cluster configuration ora* VGs are not controlled by VCS". Actually, I am not aware of this. Thanks, Rama (0 Replies)
Discussion started by: ramareddi16
0 Replies

8. Solaris

Sun Cluster configuration issue

I am using VMware Workstation-7 on Windows-XP host . I am trying to configure Solaris 10-X86 guest os based 2 nodes Sun Cluster . I have added one extra Virtual Lan adapter on my VMware with another subnet (that I would like to put for SUN Cluster private communication). I have... (0 Replies)
Discussion started by: sanjee
0 Replies

9. Solaris

Sun cluster 4.0 - zone cluster failover doubt

Hello experts - I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts. (1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over) (2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies

10. UNIX and Linux Applications

Configuration of Linux cluster managment on Red Hat 5.x server

Hi Experts, I have question regarding linux cluster managment on Red Hat 5.x server. When I try to install 'luci' or 'ricci' in one of our linux servers it is giving me below error:- yum install luci Loaded plugins: katello, product-id, rhnplugin, security, subscription-manager Updating... (0 Replies)
Discussion started by: Amey Joshi
0 Replies
cman(5) 					      cluster.conf cman configuration section						   cman(5)

NAME
cman - cluster.conf cman configuration section DESCRIPTION
Cman configuration values are placed in the <cman> </cman> section of cluster.conf. Per-node configuration related to cman is placed in the standard <clusternode> </clusternode> sections. All cman configuration settings are optional; usually none are used. The <cman> section is placed under the <cluster> section in cluster.conf. <cluster> <cman> </cman> ... </cluster> UDP port By default, cman will use UDP port 5405/5404 for internode communication. This can be changed by setting a port number as follows: <cman port="6809"> </cman> This will cause cman to use ports 6809 and 6808 for cluster communications. Expected votes The expected votes value is used by cman to determine quorum. The cluster is quorate if the sum of votes of existing members is over half of the expected votes value. By default, cman sets the expected votes value to be the sum of votes of all nodes listed in cluster.conf. This can be overridden by setting an explicit expected_votes value as follows: <cman expected_votes="3"> </cman> If the cluster becomes partitioned, improper use of this option can result in more than one partition gaining quorum. In that event, nodes in each partition will enable cluster services. Two node clusters Ordinarily, the loss of quorum after one out of two nodes fails will prevent the remaining node from continuing (if both nodes have one vote.) Special configuration options can be set to allow the one remaining node to continue operating if the other fails. To do this only two nodes, each with one vote, can be defined in cluster.conf. The two_node and expected_votes values must then be set to 1 in the cman section as follows. <cman two_node="1" expected_votes="1"> </cman> Node votes By default, a node is given one vote toward the calculation of quorum. This can be changed by giving a node a specific number of votes as follows: <clusternode name="nd1" votes="2"> </clusternode> Node ID All nodes must have a unique node ID. This is a single integer that identifies it to the cluster. A node's application to join the cluster may be rejected if you try to set the nodeid to one that is already used. <clusternode name="nd1" nodeid="1"> </clusternode> Multi-home configuration It is quite common to use multiple ethernet adapters for cluster nodes, so they will tolerate the failure of one link. A common way to do this is to use ethernet bonding. Alternatively you can get corosync to run in redundant ring mode by specifying an 'altname' for the node. This is an alternative name by which the node is known, that resolves to another IP address used on the other ethernet adapter(s). You can optionally specify a different port and/or multicast address for each altname in use. Up to 9 altnames (10 interfaces in total) can be used. Note that if you are using the DLM with cman/corosync then you MUST tell it to use SCTP as it's communications protocol as TCP does not support multihoming. <clusternode name="nd1" nodeid="1"> <altname name="nd1a" port="6809" mcast="229.192.0.2"/> </clusternode> <dlm protocol="sctp"/> Multicast network configuration cman uses multicast UDP packets to communicate with other nodes in the cluster. By default it will generate a multicast address using 239.192.x.x where x.x is the 16bit cluster ID number split into bytes. This, in turn is generated from a hash of the cluster name though it can be specified explicitly. The purpose of this is to allow multiple clusters to share the same subnet - they will each use a different multicast address. You might also/instead want to isolate clusters using the port number as shown above. It is possible to override the multicast address by specifying it in cluster.conf as shown: <cman> <multicast addr="229.192.0.1"/> </cman> Cluster ID The cluster ID number is used to isolate clusters in the same subnet. Usually it is generated from a hash of the cluster name, but it can be overridden here if you feel the need. Sometimes cluster names can hash to the same ID. <cman cluster_id="669"> </cman> corosync security key All traffic sent out by cman/corosync is encrypted. By default the security key used is simply the cluster name. If you need more security you can specify a key file that contains the key used to encrypt cluster communications. Of course, the contents of the key file must be the same on all nodes in the cluster. It is up to you to securely copy the file to the nodes. <cman keyfile="/etc/cluster/corosync.key"> </cman> Note that this only applies to cluster communication. The DLM does not encrypt traffic. Other corosync parameters When corosync is started by cman (cman_tool runs corosync), the corosync.conf file is not used. Many of the configuration parame- ters listed in corosync.conf can be set in cluster.conf instead. Cman will read corosync parameters from the following sections in cluster.conf and load them into corosync: <cluster> <totem /> <event /> <aisexec /> <group /> </cluster> See the corosync.conf(5) man page for more information on keys that are valid for these sections. Note that settings in the <clus- ternodes> section will override settings in the sections above, and options on the cman_tool command line will override both. In particular, settings like bindnetaddr, mcastaddr, mcastport and nodeid will always be replaced by values in <clusternodes>. Cman uses different defaults for some of the corosync parameters listed in corosync.conf(5). If you wish to use a non-default set- ting, they can be configured in cluster.conf as shown above. Cman uses the following default values: <totem vsftype="none" token="10000" token_retransmits_before_loss_const="20" join="60" consensus="4800" rrp_mode="none" <!-- or rrp_mode="active" if altnames are present > /> <aisexec user="root" group="root" /> Here's how to set the token timeout to five seconds: <totem token="5000"/> SEE ALSO
cluster.conf(5), corosync.conf(5), cman_tool(8) cman(5)
All times are GMT -4. The time now is 08:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy