08-15-2019
Systemmirror v6.1 cluster issues.
We had an issue during an LPM of a cluster node that seemed to be a network related issue. After that we rebooted everything and brought it all back up but now both nodes of the cluster don't see either as being "up" (clstat). They see themselves but not the other node. One of the odd issues is that the cl_clcmd will execute a command on both nodes. I can also start cluster services on both nodes from one node. This is an active/active setup running cluster version 6.1.0 sp14
9 More Discussions You Might Find Interesting
1. AIX
Hi All
I have two Pseries servers with AIX 5L as operating systems. HACMP cluster was there. For some reasons I have to change IP addresses of Servers. So How could I do it?
Ajay (2 Replies)
Discussion started by: ajay234
2 Replies
2. High Performance Computing
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
3. High Performance Computing
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
4. Linux
I have a cluster set up with a head node and compute nodes running TORQUE and MOAB. The distro is ROCKS 5.3. I've been having problems with the connectivity for the past couple weeks now. Every couple hours it seems like the network connectivity will just stop working: sometimes it'll start back up... (0 Replies)
Discussion started by: gandalf85
0 Replies
5. Solaris
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
6. UNIX for Dummies Questions & Answers
Hi friends pls give be a brief definition about clusters , i heard abt it its a server isnt any one have idea abt it
how to form a cluster ?
whts the configuration need for comning a cluster ?
wht os they used in it ?
How many servers can installed in a cluster ?
give me full detailes abt... (1 Reply)
Discussion started by: babinlonston
1 Replies
7. Solaris
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
8. Solaris
I am new to clustering enviornment , so can anyone tell me command or set of command or script that can determin whether any particular server is in cluster or not? (5 Replies)
Discussion started by: omkar.jadhav
5 Replies
9. Solaris
I have two servers which are working active active (cluster).
my problem is :
When I put the following command :hastat -a to know the active node I have this message:"could not detect active node"
NB:the version of my solaris is 10 8/07 s10x_u4wos_12h x86
How to solve this problem
... (0 Replies)
Discussion started by: zineb06
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)