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
LEARN ABOUT OPENSOLARIS
scversions
scversions(1M) System Administration Commands scversions(1M)
NAME
scversions - Sun Cluster version management
SYNOPSIS
scversions [-c]
DESCRIPTION
Note -
Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software
still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor-
mation about the object-oriented command set, see the Intro(1CL) man page.
The scversions command commits the cluster to a new level of functionality after a rolling-upgrade to new Sun Cluster software. With no
arguments, the scversions command prints a message indicating whether a commitment is needed.
OPERANDS
The following operands are supported:
-c Commit the set of nodes that are currently active members of the cluster to the highest possible level of functionality.
When you upgrade a node (either through upgrade to a new release of the product or by application of a patch) and boot it back
into the cluster, some of the internal protocols on that node might have to run at lower versions in order to cooperate cor-
rectly with other nodes in the cluster. When the cluster is in this state, some administrative actions might be disabled and
some new functionality introduced in the upgrade might be unavailable.
When you run this command once from any node after all nodes are upgraded, the cluster switches to the highest versions of
internal protocols possible. Assuming that all nodes have the same Sun Cluster software installed at that time, all new func-
tionality becomes available and any administrative restrictions are removed.
If a node that has not been upgraded is an active member of the cluster at the time you run the -c option to scversions, the
command has no effect because the cluster is already running at the highest possible level of functionality.
If a node has not been upgraded and is not an active member of the cluster when you run the -c option to scversions (for exam-
ple, if that node is down for maintenance), the internal protocols of the cluster are upgraded to the highest possible ver-
sions. You might have to upgrade the node that was not an active member of the cluster to enable it to rejoin the cluster.
EXIT STATUS
0 Success
non-zero Failure
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWsczu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
scinstall(1M)
Sun Cluster 3.2 17 Aug 2007 scversions(1M)