Sun Cluster 3.2 Issue Post: 302839017

Sponsored Content

Operating Systems Solaris Sun Cluster 3.2 Issue Post 302839017 by adilyos on Wednesday 31st of July 2013 06:28:03 AM

07-31-2013

Registered User

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 failed" status. A ressource in this ressource group have a "Stop failed" status.

Here is a part of the result of "scstat -g" command:

Code:

Group Name       Node Name              State              Suspended
 Group: xxxx           server1                  Error--stop       failed No
  Group: xxxxx        server2                  Offline                  No

Resource Name  Node Name                State          Status Message

 Resource: xxxxx       server1                  Online             Online
  Resource: xxxx        server2                  Offline             Offline

  Resource: xxxxx        server1                 Stop failed       Faulted
  Resource: xxxxxx       server2                 Offline             Offline

The logs are located at "/var/cluster/logs" and are a binary files, so I don't have any information about what happened.

Can anyone explain me what happened ? Is that critical ? What's the solution?

Thak you very much.

Best Regards,

adilyos

View Public Profile for adilyos

Find all posts by adilyos

9 More Discussions You Might Find Interesting

1. High Performance Computing

SUN Cluster Vs Veritas Cluster

Dear All, Can anyone explain about Pros and Cons of SUN and Veritas Cluster ? Any comparison chart is highly appreciated. Regards, RAA

2. Solaris

Sun Cluster

Hi All I hav working knowledge on solarois 10. Could anyone suggest me any doc or material for learning SUN cluster from scratch. Anything from basic level . Thanks in advance!!

3. Solaris

Sun cluster and Veritas cluster question.

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

4. Solaris

Sun cluster 3.2

Hi I have a new mount point which is to added to to an existing resource group. I read many docs but I am not able to find the exact methods. Could anyone help me pls.

5. Solaris

Sun cluster 3.1

Hi, I have upgraded a Sparc T2000 server which is node 2, in a Sun Cluster 3.1 two node cluster from Solaris 10 Update 2, to 10 Update 7. This is a requirement for a NetApps solution as we currently have a Sun 3510 SAN. I am at a stage where I believe the two nodes will not communicate over the...

6. Solaris

Sun cluster

Any body can tell me where i can download sun cluster installation and configuration video. is there any option to install cluster in 32 bit virtual machine. please help

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

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

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

LEARN ABOUT OPENSOLARIS

scversions

scversions(1M)						  System Administration Commands					    scversions(1M)

NAME

       scversions - Sun Cluster version management

SYNOPSIS

       scversions [-c]

DESCRIPTION

       Note -

	 Beginning  with  the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software
	 still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more  infor-
	 mation about the object-oriented command set, see the Intro(1CL) man page.

       The  scversions	command  commits  the cluster to a new level of functionality after a rolling-upgrade to new Sun Cluster software. With no
       arguments, the scversions command prints a message indicating whether a commitment is needed.

OPERANDS

       The following operands are supported:

       -c	    Commit the set of nodes that are currently active members of the cluster to the highest possible level of functionality.

		    When you upgrade a node (either through upgrade to a new release of the product or by application of a patch) and boot it back
		    into  the  cluster, some of the internal protocols on that node might have to run at lower versions in order to cooperate cor-
		    rectly with other nodes in the cluster.  When the cluster is in this state, some administrative actions might be disabled  and
		    some new functionality introduced in the upgrade might be unavailable.

		    When  you  run  this  command once from any node after all nodes are upgraded, the cluster switches to the highest versions of
		    internal protocols possible. Assuming that all nodes have the same Sun Cluster software installed at that time, all new  func-
		    tionality becomes available and any administrative restrictions are removed.

		    If	a  node that has not been upgraded is an active member of the cluster at the time you run the -c option to scversions, the
		    command has no effect because the cluster is already running at the highest possible level of functionality.

		    If a node has not been upgraded and is not an active member of the cluster when you run the -c option to scversions (for exam-
		    ple,  if  that  node is down for maintenance), the internal protocols of the cluster are upgraded to the highest possible ver-
		    sions.  You might have to upgrade the node that was not an active member of the cluster to enable it to rejoin the cluster.

EXIT STATUS

       0	    Success

       non-zero     Failure

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWsczu			   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Evolving			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       scinstall(1M)

Sun Cluster 3.2 						    17 Aug 2007 						    scversions(1M)