Sponsored Content
Full Discussion: Solaris 10 - Cluster Problem
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
Old 10-24-2008
Network

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!!!! Smilie

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.Smilie

########## 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!!!!Smilie

############## 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

Solaris and Cluster Patches

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

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

3. High Performance Computing

Sun Solaris cluster

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

Solaris Cluster

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

SVM metaset on 2 node Solaris cluster storage replicated to non-clustered Solaris node

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

Solaris Cluster Device Problem

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

Patching Procedure in Solaris 10 with sun cluster having Solaris zone

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
clinfo(1M)						  System Administration Commands						clinfo(1M)

NAME
clinfo - display cluster information SYNOPSIS
clinfo [-nh] DESCRIPTION
The clinfo command displays cluster configuration information about the node from which the command is executed. Without arguments, clinfo returns an exit status of 0 if the node is configured and booted as part of a cluster. Otherwise, clinfo returns an exit status of 1. OPTIONS
The following options are supported: -h Displays the highest node number allowed to be configured. This is different from the maximum number of nodes supported in a given cluster. The current highest configured node number can change immediately after the command returns since new nodes can be dynam- ically added to a running cluster. For example, clinfo -h might return 64, meaning that the highest number you can use to identify a node is 64. See the Sun Cluster 3.0 System Administration Guide for a description of utilities you can use to determine the number of nodes in a cluster. -n Prints the number of the node from which clinfo is executed. EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 An error occurred. This is usually because the node is not configured or booted as part of a cluster. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
attributes(5) SunOS 5.10 12 Mar 2002 clinfo(1M)
All times are GMT -4. The time now is 01:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy