Solaris cluster critical issue

8 More Discussions You Might Find Interesting

1. Solaris

Patching Procedure in Solaris 10 with sun cluster having Solaris zone

Hi Gurus I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow. Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently...

2. AIX

Cluster communication issue

Hi, I am using Power HA7.1.1 SP5 AIx 7.1 My both cluster nodes are independently working. RG informations are not updating each other. Node A shows that node B is down and vice versa. RG1 is running node A, RG2 running on node B. === clRGinfo From Node B === RG01 OFFLINE ...

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

4. Solaris

Sun Cluster 3.2 Issue

Hello everyone, I have two Solaris 10 servers that are on cluster. The cluster is a Sun Cluster 3.2 I have a script cronned that stop/start a ressource in a resource group everyday. Today I have checked the status of the ressources and I found that my ressource group have a "Error--stop...

5. Solaris

Sun Cluster switching issue

I have installed sun cluster 3.2 on two sprac servers. Configured a failover resource group. Added a LogicalHostname resource to it. LogicalHostname is also added to /etc/hosts with ip address. I am able to access cluster by share ip used for logical hostname but when i try to switch the resource...

6. Solaris

Sun Cluster configuration issue

I am using VMware Workstation-7 on Windows-XP host . I am trying to configure Solaris 10-X86 guest os based 2 nodes Sun Cluster . I have added one extra Virtual Lan adapter on my VMware with another subnet (that I would like to put for SUN Cluster private communication). I have...

7. Solaris

Issue while installing: Solaris 10 SPARC Recommended Patch Cluster (2009.10.23)

Hello, As explained, I've encountered an issue while installing Solaris 10 SPARC Recommended Patch Cluster (2009.10.23). Actually, patch no 120011-14 stops with the following error: ERROR: attribute verification of </var/run/.patchSafeMode/root/usr/bin/passwd> failed file type <f>...

8. High Performance Computing

Building a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris

Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris. More...

LEARN ABOUT HPUX

cmruncl

cmruncl(1m)															       cmruncl(1m)

NAME

       cmruncl - run a high availability cluster

SYNOPSIS

       cmruncl [-f] [-v] [-n node_name...]  [-t | -w none]

DESCRIPTION

       cmruncl causes all nodes in a configured cluster or all nodes specified to start their cluster daemons and form a new cluster.

       To  start  a  cluster,  a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the cluster configuration
       file. See access policy in cmquerycl(1m).

       This command should only be run when the cluster is not active on any of the configured nodes.  This command verifies the network  configu-
       ration  before  causing	the nodes to start their cluster daemons.  If a cluster is already running on a subset of the nodes, the cmrunnode
       command should be used to start the remaining nodes and force them to join the existing cluster.

       If node_name is not specified, the cluster daemons will be started on all the nodes in the cluster.  All  nodes	in  the  cluster  must	be
       available for the cluster to start unless a subset of nodes is specified.

   Options
       cmruncl supports the following options:

	      -f	Force cluster startup without warning message and continuation prompt that are printed with the -n option.

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

	      -n  node_name...
			Start the cluster daemon on the specified subset of node(s).

	      -w none	By default network probing is performed to check that the network connectivity is the same as when the cluster was config-
			ured. 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
	      cmruncl returns the following value:

	       0   Successful completion.
	       1   Command failed.

EXAMPLES

       Run the cluster daemon:

	      cmruncl

       Run the cluster daemons on node1 and node2:

	      cmruncl -n node1 -n node2

AUTHOR

       cmruncl was developed by HP.

SEE ALSO

       cmquerycl(1m), cmhaltcl(1m), cmhaltnode(1m), cmrunnode(1m), cmviewcl(1m), cmeval(1m).

						      Requires Optional Serviceguard Software					       cmruncl(1m)

Solaris