|
|
Sponsored Content
Special Forums
UNIX and Linux Applications
High Performance Computing
Solaris 10 - Cluster Problem
Post 302250785 by hi2joshi on Friday 24th of October 2008 08:43:41 AM
10-24-2008
Togr,
First, You are AWSOME and yes we have to catch RIGHT person these days to come out of any task if you are NEWBIE like me. I am catching you now!!!!
I have followed your suggested steps and tried again to build a two node cluster but nodes are not coming in cluster mode after rebooting by scinstall.
########## TWO NODE Cluster attempt ################
bash-3.00# clnode show
clnode: (C152734) This node is not in cluster mode.
#############################################
This messages is coming on both servers. I tried to create SINGLE node cluster on one node as well but after rebooting it, same above mentioned message!!!!
############## One Node Cluster Log ####################
bash-3.00# cat scinstall.log.5275
*** Establish Just the First Node of a New Cluster ***
Fri Oct 24 16:00:15 IST 2008
scinstall -ik -C hitarth -F -o -P task=quorum,state=INIT
Checking device to use for global devices file system ... done
Initializing cluster name to "hitarth" ... done
Initializing authentication options ... done
Setting the node ID for "solariscluster1" ... done (id=1)
Checking for global devices global file system ... done
Updating vfstab ... done
Updating nsswitch.conf ... done
Adding cluster node entries to /etc/inet/hosts ... done
Configuring IP multipathing groups ...done
Verifying that power management is NOT configured ... done
Unconfiguring power management ... done
/etc/power.conf has been renamed to /etc/power.conf.102408160153
Power management is incompatible with the HA goals of the cluster.
Please do not attempt to re-configure power management.
Ensure network routing is disabled ... done
Network routing has been disabled on this node by creating /etc/notrouter.
Having a cluster node act as a router is not supported by Sun Cluster.
Please do not re-enable network routing.
Rebooting ...
###################################################
P.S.- (1) Both nodes are connected with CROSSOVER cable for private network. (2) I haven't DISABLE auto quorum option while creating this cluster.
Please take out of this!!!!! I am getting frustrated now!!!!
Thanks
First, You are AWSOME and yes we have to catch RIGHT person these days to come out of any task if you are NEWBIE like me. I am catching you now!!!!
I have followed your suggested steps and tried again to build a two node cluster but nodes are not coming in cluster mode after rebooting by scinstall.
########## TWO NODE Cluster attempt ################
bash-3.00# clnode show
clnode: (C152734) This node is not in cluster mode.
#############################################
This messages is coming on both servers. I tried to create SINGLE node cluster on one node as well but after rebooting it, same above mentioned message!!!!
############## One Node Cluster Log ####################
bash-3.00# cat scinstall.log.5275
*** Establish Just the First Node of a New Cluster ***
Fri Oct 24 16:00:15 IST 2008
scinstall -ik -C hitarth -F -o -P task=quorum,state=INIT
Checking device to use for global devices file system ... done
Initializing cluster name to "hitarth" ... done
Initializing authentication options ... done
Setting the node ID for "solariscluster1" ... done (id=1)
Checking for global devices global file system ... done
Updating vfstab ... done
Updating nsswitch.conf ... done
Adding cluster node entries to /etc/inet/hosts ... done
Configuring IP multipathing groups ...done
Verifying that power management is NOT configured ... done
Unconfiguring power management ... done
/etc/power.conf has been renamed to /etc/power.conf.102408160153
Power management is incompatible with the HA goals of the cluster.
Please do not attempt to re-configure power management.
Ensure network routing is disabled ... done
Network routing has been disabled on this node by creating /etc/notrouter.
Having a cluster node act as a router is not supported by Sun Cluster.
Please do not re-enable network routing.
Rebooting ...
###################################################
P.S.- (1) Both nodes are connected with CROSSOVER cable for private network. (2) I haven't DISABLE auto quorum option while creating this cluster.
Please take out of this!!!!! I am getting frustrated now!!!!
Thanks
|
|
7 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Simple question:
After applying a cluster patch to a sun solaris box I am left with a root volume 81% full. I could run through the hassle of resizing the slices which is way too much work for a Ultra 5 running DNS only.
Is there a way to clean up the /var/sadm/pkg area, aka dump the save info. (5 Replies)
Discussion started by: edkung
5 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
Hi all,
I need ur help plz
how sun cluster work and i need good reference for that.
ur cooperate is appreciated (4 Replies)
Discussion started by: AshAdmin
4 Replies
4. Solaris
Hi All,
i have 2 zone
1- Oracle DB Primary Server
2- Oracle DB Secondary Server
i make script do r sync between this 2 zones
but i am planning to do is
make Solaris cluster between this zones
if the primary Server field the secondary server up and running automatically without any... (1 Reply)
Discussion started by: jamisux
1 Replies
5. Solaris
Hi,
Is it possible to have a Solaris cluster of 2 nodes at SITE-A using SVM and creating metaset using say 2 LUNs (on SAN). Then replicating these 2 LUNs to remote site SITE-B via storage based replication and then using these LUNs by importing them as a metaset on a server at SITE-B which is... (0 Replies)
Discussion started by: dn2011
0 Replies
6. Solaris
I build up two node cluster (node1, node2) in virtualbox. For these two nodes I add 5 shared disk. (Also each node have own OS disk).
1 shared disk for vtoc
2 shared disk for NFS resource group
2 shared disk for WEB resource group
When I finished my work; two nodes was ok and shared disk... (4 Replies)
Discussion started by: sonofsunra
4 Replies
7. Solaris
Hi Gurus
I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow.
Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 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)