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
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
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
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
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
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
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
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
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
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
cmdo(1m) cmdo(1m)
NAME
cmdo - Execute process on multiple remote Serviceguard nodes.
SYNOPSIS
cmdo [[-n node_name]...] [-t timeout] command
DESCRIPTION
cmdo will execute a process on a multiple remote Serviceguard nodes and return any output or return value.
cmdo is limited in several ways. cmdo is best suited for situations where other remote execution facilities are not available. For a more
full featured tool for remote execution within a cluster, see cexec(1m) provided by Distributed Systems Administration Utilities.
To use this command, the local user must have the root access role on each of the involved nodes. For more information on Serviceguard
access control policies, see the manual, Managing Serviceguard.
To use the cmdo command without specifying -n options, the local node must be configured into a Serviceguard cluster. If no -n options are
specified, the command will be executed on all available nodes in the cluster.
The command will be executed in an environment which matches the local node. All environment variables defined locally will be available
on the remote node.
Output from stderr and stdout for the remote process will be combined and delivered in one transmission. This command should not be used
for interactive commands or commands which will return large quantities of output. Output from each node will be displayed sequentially as
the operation is executed on each remote node.
Input via stdin is not supported.
Killing the cmdo process does not stop any remote executions of the command. cmdo should not be used on any command which may hang without
specifying a timeout value.
Options And Arguments
-t timeout
Kill the executed command if it does not exit within the specified timeout (in seconds)
-n node_name
Serviceguard node to execute command on. If no -n options are specified, all the nodes configured in the cluster are used.
command
Command to execute on remote node. May be quoted.
RETURN VALUE
cmdo returns the following values:
0 Successful completed on all nodes.
>0 Command failed on one or more nodes with the specified exit value.
EXAMPLES
Execute an 'ls' in a remote directory on all nodes within the cluster.
cmdo ls /tmp
Execute an 'ls' in a remote directory on two nodes not configured within a Serviceguard cluster.
cmdo -n node1 -n node2 ls /tmp
AUTHOR
cmdo was developed by HP.
SEE ALSO
cexec(1m), cmcp(1m), cmexec(1m), cmsync(1m), cmquerycl(1m), cmviewcl(1m)
Requires Optional Serviceguard Software cmdo(1m)