Sponsored Content
Top Forums Shell Programming and Scripting The other node name of a SUN cluster Post 302092296 by heartwork on Sunday 8th of October 2006 02:23:55 PM
Old 10-08-2006
Sorry I had no intention... I am searching desperately an answer to my problem... even it might be easy...

Quote:
Originally Posted by nathan
This looks just like this thread. I believe that's against rule #4.
 

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... (1 Reply)
Discussion started by: Tris
1 Replies

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... (1 Reply)
Discussion started by: rauphelhunter
1 Replies

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,... (1 Reply)
Discussion started by: solman17
1 Replies

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? (3 Replies)
Discussion started by: sreeniatbp
3 Replies

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 ? (7 Replies)
Discussion started by: fugitive
7 Replies

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... (0 Replies)
Discussion started by: dn2011
0 Replies

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... (1 Reply)
Discussion started by: snchaudhari2
1 Replies

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... (0 Replies)
Discussion started by: NVA
0 Replies

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... (2 Replies)
Discussion started by: depam
2 Replies
scha_cluster_get(1HA)					       Sun Cluster Commands					     scha_cluster_get(1HA)

NAME
scha_cluster_get - access cluster information SYNOPSIS
scha_cluster_get -O optag [args] DESCRIPTION
The scha_cluster_get command accesses and generates information about a cluster. You can access information about the cluster, nodes, zones, host names, resource groups, resource types, and states. The command is intended for use in shell script implementations of callback methods for resource types. These callback methods for resource types represent services that are controlled by the cluster's Resource Group Manager (RGM). This command provides the same information as the scha_resource_get() function. This command sends output to the standard output (stdout) in formatted strings on separate lines, as described in the scha_cmds(1HA) man page. You can store the output in shell variables. You can also parse the output with shell commands such as the awk command. OPTIONS
The following options are supported: -O optag The optag argument indicates the information to be accessed. Depending on the optag, an additional argument may be needed to indicate the cluster node or zone for which information is to be retrieved. Note - optag options, such as NODENAME_LOCAL and NODENAME_NODEID, are not case sensitive. You can use any combination of uppercase and lowercase letters when you specify optag options. The following optag values are supported: ALL_NODEIDS Generates on successive lines the numeric node identifiers of all nodes in the cluster. ALL_NODENAMES Generates on successive lines the names of all nodes in the cluster. ALL_NONGLOBAL_ZONES Generates on successive lines the nodename:zonename string of all the non-global zones on all nodes in the cluster. ALL_NONGLOBAL_ZONES_NODEID Generates on successive lines the nodename:zonename string of all non-global zones on the cluster node whose numeric node identifier is given as the argument. ALL_PRIVATELINK_HOSTNAMES Generates on successive lines the host names by which all cluster nodes are addressed on the cluster interconnect. ALL_RESOURCEGROUPS Generates on successive lines the names of all the resource groups that are being managed in the cluster. ALL_RESOURCETYPES Generates on successive lines the names of all the resource types that are registered in the cluster. ALL_ZONES Generates on successive lines the nodename:zonename string of all zones, including the global zone, on all nodes in the cluster. ALL_ZONES_NODEID Generates on successive lines the nodename:zonename string of all zones, including the global zone, on the cluster node whose numeric node identifier is given as the argument. CLUSTERNAME Generates the name of the cluster. NODEID_LOCAL Generates the numeric node identifier for the node where the command is executed. NODEID_NODENAME Generates the numeric node identifier of the node indicated by the name. Requires an additional unflagged argument that is the name of a cluster node. NODENAME_LOCAL Generates the name of the cluster node where the command is executed. NODENAME_NODEID Generates the name of the cluster node indicated by the numeric identifier. Requires an additional unflagged argu- ment that is a numeric cluster node identifier. NODESTATE_LOCAL Generates UP or DOWN depending on the state of the node where the command is executed. NODESTATE_NODE Generates UP or DOWN depending on the state of the named node. Requires an additional unflagged argument that is the name of a cluster node. PRIVATELINK_HOSTNAME_LOCAL Generates the host name by which the node on which the command is run is addressed over the cluster interconnect. PRIVATELINK_HOSTNAME_NODE Generates the host name by which the named node is addressed on the cluster interconnect. Requires an additional unflagged argument that is the name of a cluster node. SYSLOG_FACILITY Generates the number of the syslog(3C) facility that the RGM uses for log messages. The value is 24, which corre- sponds to the daemon facility. You can use this value as the facility level in the logger(1) command to log mes- sages in the cluster log. ZONE_LOCAL Generates the name of the zone from which the command is issued. The format of the zone name that is returned is nodename:zonename. EXAMPLES
Example 1 Using the scha_cluster Command in a Shell Script The following shell script uses the scha_cluster command to print whether each cluster node is up or down: #!/bin/sh nodenames=`scha_cluster_get -O All_Nodenames` for node in $nodenames do state=`scha_cluster_get -O NodeState_Node $node` printf "State of node: %sexit: %dvalue: %s0 "$node" $? "$state" done EXIT STATUS
The following exit status codes are returned: 0 Successful completion. nonzero An error occurred. Error codes are described in scha_calls(3HA). ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWscdev | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ SEE ALSO
awk(1), logger(1), sh(1), scha_cmds(1HA), syslog(3C), scha_calls(3HA), scha_cluster_get(3HA), attributes(5) Sun Cluster 3.2 6 Sep 2006 scha_cluster_get(1HA)
All times are GMT -4. The time now is 10:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy