10 More Discussions You Might Find Interesting
1. Red Hat
Hi All;
I try to build a Redhat Cluster (CentOS 6) on vmware. But each node sees the other down like:
# clustat
Cluster Status for mycluster @ Wed Apr 8 11:01:38 2015
Member Status: Quorate
Member Name ID Status
------ ---- ... (1 Reply)
Discussion started by: Meacham12
1 Replies
2. Red Hat
Hi All;
I try to build a Redhat Cluster (CentOS 6) on vmware. But each node sees the other down like:
# clustat
Cluster Status for mycluster @ Wed Apr 8 11:01:38 2015
Member Status: Quorate
Member Name ID Status
------ ---- ... (0 Replies)
Discussion started by: Meacham12
0 Replies
3. Red Hat
HI,
Can you guys help me to install redhat cluster on VMware Workstation.
How to download cluster suite and how to configure on Workstation. (1 Reply)
Discussion started by: karthik9358
1 Replies
4. Red Hat
Hello Experts,
Please help me with the exact steps on configuring two node cluster on RHEL 6.2,
I failed to configure the simplest cluster by below steps,
1- install RHEL 6.2 64-bit on both nodes
2- add to hosts file of each server ( 1 IP in local NW and another in IP private NW).
x.x.x.x ... (1 Reply)
Discussion started by: karmellove
1 Replies
5. Red Hat
Hello,
can someone please suggest me in configuring the mysql db on redhat cluster, I have few questions.
1. where do I have to configure heart beat links, and is there any file in the redhat cluster that we update it to use these ipaddress and these interface on the node.
2. I am configuring... (0 Replies)
Discussion started by: bobby320
0 Replies
6. Red Hat
hello,
I was going through clustering documentation for Redhat, it says "Enable IP Aliasing support in the kernel by setting the CONFIG_IP_ALIAS kernel option to y. When specifying kernel options, under Networking Options, select IP aliasing support", I knew I should update /etc/sysctl.conf with... (1 Reply)
Discussion started by: bobby320
1 Replies
7. Red Hat
hi all ,
I'm trying for the Red-hat cluster setup with the ' Enable shared storage support'. But hang up with a error that
"Packages of set "Clustered Storage" are not present in any available repository". I made this setup by installing the rpm manually..I ve attached the rpm list and error... (0 Replies)
Discussion started by: sriniv666
0 Replies
8. Red Hat
Hi Friends,
I am trying to configure redhat high availability cluster on rhel5 32bit.
As i am not having the RHN subscription, I have to intsall all the cluster suite manually. I am not aware what all are the rpms needs to be installed. Please let me know about the rpms needs to be installed.... (3 Replies)
Discussion started by: arumon
3 Replies
9. Red Hat
Hello;
I have 2 node Redhat Cluster (RHEL4 U4 and Cluster Suite) I'm using mc_data fiber channel switch for fencing
when I want to fence manually using
fence_mcdata -a x.x.x. -l xxx -p xxxx -n 5 -o disable
following messages appears
fencing node "test1"
agent "fence_mcdata" reports:... (0 Replies)
Discussion started by: sakir19
0 Replies
10. Red Hat
Hi,
I am trying to setup redhat native cluster 5, i installed all the required rpms and issued the command service cman start (cman is the cluster manager)
this gives me output...
#service cman start
Starting cluster:
Loading modules... done
Mounting configfs... done
... (0 Replies)
Discussion started by: santhoshb
0 Replies
cmruncl(1m) cmruncl(1m)
NAME
cmruncl - run a high availability cluster
SYNOPSIS
cmruncl [-f] [-v] [-n node_name...] [-t | -w none]
DESCRIPTION
cmruncl causes all nodes in a configured cluster or all nodes specified to start their cluster daemons and form a new cluster.
To start a cluster, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the cluster configuration
file. See access policy in cmquerycl(1m).
This command should only be run when the cluster is not active on any of the configured nodes. This command verifies the network configu-
ration before causing the nodes to start their cluster daemons. If a cluster is already running on a subset of the nodes, the cmrunnode
command should be used to start the remaining nodes and force them to join the existing cluster.
If node_name is not specified, the cluster daemons will be started on all the nodes in the cluster. All nodes in the cluster must be
available for the cluster to start unless a subset of nodes is specified.
Options
cmruncl supports the following options:
-f Force cluster startup without warning message and continuation prompt that are printed with the -n option.
-v Verbose output will be displayed.
-t Test only. Provide an assessment of the package placement without affecting the current state of the nodes or packages.
The -w option is not required with the -t option as -t does not validate network connectivity, but assumes that all the
nodes can meet any external dependencies such as EMS resources, package subnets, and storage.
-n node_name...
Start the cluster daemon on the specified subset of node(s).
-w none By default network probing is performed to check that the network connectivity is the same as when the cluster was config-
ured. Any anomalies are reported before the cluster daemons are started. The -w none option disables this probing. The
option should only be used if this network configuration is known to be correct from a recent check.
RETURN VALUE
cmruncl returns the following value:
0 Successful completion.
1 Command failed.
EXAMPLES
Run the cluster daemon:
cmruncl
Run the cluster daemons on node1 and node2:
cmruncl -n node1 -n node2
AUTHOR
cmruncl was developed by HP.
SEE ALSO
cmquerycl(1m), cmhaltcl(1m), cmhaltnode(1m), cmrunnode(1m), cmviewcl(1m), cmeval(1m).
Requires Optional Serviceguard Software cmruncl(1m)