sun Cluster resource group cant failover

10 More Discussions You Might Find Interesting

1. Solaris

Process to add mount point in Sun Cluster existing HAplus resource

Hi Well I would like to know step by step process of adding a mountpoint in HAPLUS resource in SUN cluster as I go the below command to add a mount point but not the step by step process of adding a mount point in existing HA Plus resource. clrs set -p FileSystemMountPoints+=<new_MP>...

2. Red Hat

Linux Cluster failover issue

Hi Guys, I am not much aware of clusters but i have few questions can someone provide the overview as it would be very helpful for me. How can i perform cluster failover test to see all the services are failing back to other node ? If it is using veritas cluster then what kind of...

3. Solaris

Solaris Cluster Failover based on scan rate

Dear Experts, If there is a possible Solaris Cluster failover to second node based on scan rate? I need the documentation If solaris cluster can do this. Thank You in Advance Edy

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

5. AIX

Adding a Volume Group to an HACMP Resource Group?

Hi, I have a 2 node Cluster. Which is working in active/passive mode (i.e Node#1 is running and when it goes down the Node#2 takes over) Now there's this requirement that we need a mount point say /test that should be available in active node #1 and when node #1 goes down and node#2 takes...

6. Gentoo

How to failover the cluster ?

How to failover the cluster ? GNU/Linux By which command, My Linux version 2008 x86_64 x86_64 x86_64 GNU/Linux What are the prerequisites we need to take while failover ? if any Regards

7. AIX

Resource Group Monitoring

Hi, I have a requirement to monitor the HACMP Resource Groups. At present in my environment, if the Resource Groups fail over from preferred node to Secondary node we dont get notification. Can some one help me in creating a scrript. I have more than one RG online. (Max 4 Resource Groups in...

8. Solaris

Sun Cluster 3.1 failover

Hi, We have two sun SPARC server in Clustered (Sun Cluster 3.1). For some reason, System 1 failed over to System 2. Where can I find the logs which could tell me the reason for this failover? Thanks

9. High Performance Computing

Veritas Cluster Server Management Console IP Failover

I have just completed a first RTFM of "Veritas Cluster Server Management Console Implementation Guide" 5.1, with a view to assessing it to possibly make our working lives easier. Unfortunately, at my organisation, getting a test installation would be worse than pulling teeth, so I can't just go...

10. HP-UX

ServiceGuard cluster & volume group failover

I have a 2-node ServiceGuard cluster. One of the cluster packages has a volume group assigned to it. When I fail the package over to the other node, the volume group does not come up automatically on the other node. I have to manually do a "vgchange -a y vgname" on the node before the package...

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)

High Performance Computing