The other node name of a SUN cluster Post: 302092294

Sponsored Content

Top Forums Shell Programming and Scripting The other node name of a SUN cluster Post 302092294 by heartwork on Sunday 8th of October 2006 12:54:47 PM

10-08-2006

Registered User

The other node name in a SUN cluster

Hello,

Under ksh I have to run a script on one of the nodes of a Solaris 8 cluster which at some time must execute a command on the alternate node:
# rsh <name> "command"

I have to implement this script on all the clusters of my company (a lot of...).
Fortunately, the names of the two nodes obey the following rule: a common string excepting the last character which is 1 on one node and 2 for the other.
I don't want to read the names of the machines in /etc/hosts which is really a mess on some clusters... (obsolete names etc.)

I thought to the following solution:

1. Read in a variable the name of the current node (uname ... ?!?)

2. In the script I added a part that get from the current node name the other node name. From some reason... when I run from the ksh the commands one by one it works fine:

Code:

root@carp # X=abc12
root@carp # numofchar=${#X}
root@carp # numofcharminus1=`expr $numofchar "-" 1`
root@carp # Y=`echo "$X" | cut -c1-${numofcharminus1}`
root@carp # Z=`echo "$X" | cut -c${numofchar}`
root@carp # T=`expr 3 "-" $Z`
root@carp # echo $Y$T
abc11

but when I insert them in the script I got error messages like:

Y=`echo "$X" | cut -c1-${numofcharminus1}`
cut - invalid range

T=`expr 3 "-" $Z`
invalid expression

I don't use scripting too often but I can't see what's wrong in my solution... a CR rule/type conversion... I am too tired and I must finish it until tommorow so please can someone help me! Maybe someone forsee another solution?

Regards

Last edited by heartwork; 10-08-2006 at 04:18 PM..

heartwork

View Public Profile for heartwork

Find all posts by heartwork

9 More Discussions You Might Find Interesting

1. HP-UX

Node can't join cluster

Need help guys! when running cmrunnode batch i'm getting this error cmrunnode : Waiting for cluster to...

2. HP-UX

MC/SG Fail to join cluster node

Hi, Please advise me whereas I have two node cluster server configured with MC/SG. Application and DB are running on Node 1, while Node 2 is standby. All the volume group devices are part of cluster environment. There is only one package running at node 1. Node 2 is having the problem to...

3. High Performance Computing

Setting up 2 node cluster using solaris 10

hi, i am trying to setup a 2 node cluster environment. following is what i have; 1. 2 x sun ultra60 - 450MHz procs, 1GB RAM, 9GB HDD, solaris 10 2. 2 x HBA cards 3. 2 x Connection leads to connect ultra60 with D1000 4. 1 x D1000 storage box. 5. 3 x 9GB HDD + 2 x 36GB HDD first of all,...

4. Solaris

Active Sun cluster node?

I now the logical name and Virtual IP of the cluster. How can I find the active sun cluster node without having root access?

5. Solaris

Single node Sun Cluster with zones

How can we add a shared zfs dataset between 2 zones on a same host. I have sun cluster 3.2 installed in a server which has 2 zones. I want to share a zfs data set between these 2 zones how can we do that ?

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

7. Solaris

Sun Cluster 3.2 x86: Node is rebooting itself

Hey Admins, I am running sun cluster 3.2 x86 on Vmware. I m facing an issue from 2 days.. One main node is continuously rebooting..... not sure... whats woring... I just had change heartbeat timeout values on 1 this node... Now both node are just rebooting itself..seems panic.. Any...

8. Solaris

Sun cluster 4.0 - zone cluster failover doubt

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

9. AIX

Cluster node not starting

Setting up HACMP 6.1 on a two node cluster. The other node works fine and can start properly on STABLE state (VGs varied, FS mounted, Service IP aliased). However, the other node is always stuck on ST_JOINING state. Its taking forever and you can't stop the cluster as well or recover from script...

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)