02-16-2010
Comparing Cluster Members
Does anyone know of a good utility that will do a binary compare of all the files on two cluster members? We are looking for something we can run on a monthly batch basis to monitor for configuration drift between AIX/HACMP and Solaris/VCS cluster member pairs, use as an ad hoc diagnostic tool when an app runs fine on one cluster node but not the other, or to compare test and prod systems to figure out why a problem cannot be reproduced in the test environment.
I realize tight system management procedures are the best preventative, but when you have eight sysadmins with root (sudo) access and another dozen people with varying access to app directories, some type of drift is inevitable. We need something that can at least help us prove that the machines are identical so we can direct diagnostic efforts back to the application.
7 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
The Members Only Forum sub-heading has a spelling mistake. It should read visible. (1 Reply)
Discussion started by: dangral
1 Replies
2. High Performance Computing
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
Dear All,
Can anyone explain about Pros and Cons of SUN and Veritas Cluster ?
Any comparison chart is highly appreciated.
Regards,
RAA (4 Replies)
Discussion started by: RAA
4 Replies
4. Linux
Hi all,
I am new to Linux.Can anyone tell me how to display or list all the members in a group?
Thanks in advance. (9 Replies)
Discussion started by: arthi
9 Replies
5. Solaris
Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC.
Am thinking how to migrate to sun cluster setup instead.
My plan as follows leave the existing vcs intact as a fallback plan.
Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies
6. 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
7. What is on Your Mind?
Got a raise and a formal position of 'unix system engineer' in 2016.
I would like to thank you members and admins.
This would not be possible without you.
I will mention some..
Thank you Don, for making me learn and understand the importance of standards, which i try to apply as much as i... (3 Replies)
Discussion started by: Peasant
3 Replies
LEARN ABOUT HPUX
cmrunnode
cmrunnode(1m) cmrunnode(1m)
NAME
cmrunnode - run a node in a high availability cluster
SYNOPSIS
cmrunnode [-v] [node_name...] [-t | -w none]
DESCRIPTION
cmrunnode causes a node to start its cluster daemon to join the existing cluster. This command verifies the network configuration before
causing the node to start its cluster daemon.
To start a cluster on one of its nodes, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the clus-
ter configuration file. See access policy in cmquerycl(1m).
Starting a node will not cause any active packages to be moved to the new node. However, if a package is DOWN, has its switching enabled,
and is able to run on the new node, that package will automatically run there.
If node_name is not specified, the cluster daemon will be started on the local node and will join the existing cluster.
Options
cmrunnode supports the following options:
-v Verbose output will be displayed.
-t Test only. Provide an assessment of the package placement without affecting the current state of the nodes or packages. The -w
option is not required with the -t option as -t does not validate network connectivity, but assumes that all the nodes can meet
any external dependencies such as EMS resources, package subnets, and storage.
node_name...
Start the cluster daemon on the specified node(s).
-w none
By default network probing is performed to check that the network connectivity is the same as when the cluster was configured.
Any anomalies are reported before the cluster daemons are started. The -w none option disables this probing. The option should
only be used if this network configuration is known to be correct from a recent check.
RETURN VALUE
cmrunnode returns the following value:
0 Successful completion.
1 Command failed.
EXAMPLES
Run the cluster daemon on the current node:
cmrunnode
Run the cluster daemons on node1 and node2:
cmrunnode node1 node2
AUTHOR
cmrunnode was developed by HP.
SEE ALSO
cmquerycl(1m), cmhaltcl(1m), cmhaltnode(1m), cmruncl(1m), cmviewcl(1m), cmeval(1m).
Requires Optional Serviceguard Software cmrunnode(1m)