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 failure. I can't see any error from hacmp.out.
Here's the latest error I see from clstrmgr.debug (This is from console so I just type it here
---------- Post updated at 03:52 AM ---------- Previous update was at 03:47 AM ----------
Also one thing to add is that, I can start the cluster on any node as long as I have not started any other node. Meaning I can start the cluster and RG on either node1 and node2 but If I start it on node1, node2 won't bring up by clstart and shows as ST_JOINING forever. Thus, I cannot do a failover to other node unless the other node is in stable state.
Last edited by Scrutinizer; 06-08-2013 at 06:22 AM..
Reason: code tags
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... (11 Replies)
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)
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)
Hi Gurus,
For learning purpose, I have installed a single node cluster 3.2 on Solaris 10 for practice. Now I am welling to create two non-global zone and create them as a fail over. Will appreciate your help and assistance.
Thanks (3 Replies)
Hi Gurus,
I am very new to clustering and for test i have created a single node cluster, now i want to remove the system from cluster. Did some googling however as a newbee in cluster unable to co related the info.
Please help
Thanks (1 Reply)
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)
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
LEARN ABOUT HPUX
cmsync
cmsync(1m)cmsync(1m)NAME
cmsync - Synchronize files or directories on multiple Serviceguard nodes.
SYNOPSIS
cmsync [-rv] [[-n node_name]...] [src_node:]src_file [...]
DESCRIPTION
cmsync copies files and/or directories to multiple Serviceguard nodes.
cmsync is limited in several ways. cmsync is best suited for situations where other remote copy facilities are not available. For a more
full featured tool for copying files between Serviceguard nodes, see ccp(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 cmsync command without specifying -n options, the local node must be configured into a Serviceguard cluster. If no -n options
are specified, the files will be copied to all available nodes in the cluster.
Paths may be relative to the current working directory or specified absolutely. Copies between two remote hosts are permitted.
If a file or directory already exists on a destination node, the destination node's copy will be overwritten with no prompting.
The cmsync command is not suited for large files or large numbers of files and may result in a heavy load on the command and Serviceguard
daemons. Other tools such as ccp should be considered for these purposes.
Options And Arguments
-r Recursively copy entire directories.
-v Verbose output will be displayed.
-n node_name
Serviceguard node to copy file to. If no -n options are specified, default is to copy to all nodes within the configured clus-
ter.
src_node
Serviceguard node to retrieve the file from. Defaults to the local node.
src_file
Path to source file on src_node.
RETURN VALUE
cmsync returns the following values:
0 Successful completion.
1 Command failed.
EXAMPLES
Copy the local file /etc/hosts to remote nodes node1 and node2
cmsync -n node1 -n node2 /etc/hosts
Distribute the remote file /etc/passwd to all nodes in the cluster.
cmsync node1:/etc/passwd
AUTHOR
cmsync was developed by HP.
SEE ALSO ccp(1m), cmcp(1m), cmexec(1m), cmdo(1m), cmquerycl(1m), cmviewcl(1m)
Requires Optional Serviceguard Software cmsync(1m)