Sponsored Content
Operating Systems Solaris High Availability zone on Sun Cluster Post 302508735 by DukeNuke2 on Tuesday 29th of March 2011 01:15:26 AM
Old 03-29-2011
have you checked the documentation?
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

iscsi high availability

Hi, I want to set up a iscsi high availability with sheepdog distributed storage. Here is my system set up. Four nodes with sheepdog distributed storage and i am sharing this storage through iscsi using two nodes as well as using a virtual ip set up using ucarp.Two nodes using same iqn. And... (0 Replies)
Discussion started by: jobycxa
0 Replies

2. 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... (0 Replies)
Discussion started by: NVA
0 Replies

3. Red Hat

Red Hat High Availability (HA) Cluster

How can we implement a service in HA, which in not available in HA. like sldap or customize application. Requirement Details. NODE1 service slapd is running.(Require) NODE2 service slapd is running.(Require) on both the node replication is happening. Now here requirement is need... (2 Replies)
Discussion started by: Priy
2 Replies

4. Solaris

High availability

hi guys I posted problem last time I didn't find answer to my issue. my problem is as below: I have two servers which work as an actif/standby in high availability system. but when i use command HASTAT -a i have the following message: couldn' find actif node. the servers are sun... (1 Reply)
Discussion started by: zineb06
1 Replies

5. 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... (1 Reply)
Discussion started by: nick101
1 Replies
scha_resource_setstatus(1HA)				       Sun Cluster Commands				      scha_resource_setstatus(1HA)

NAME
scha_resource_setstatus - set resource status SYNOPSIS
scha_resource_setstatus -R resource -G group -s status [-m msg] [-Z zonename] DESCRIPTION
The scha_resource_setstatus command sets the Status and Status_msg properties of a resource that is managed by the Resource Group Manager (RGM). This command is intended to be used by the resource's monitor to indicate the resource's state as perceived by the monitor. It pro- vides the same functionality as the scha_resource_setstatus(3HA) C function. When you execute the scha_resource_setstatus(1HA) command, the Status and Status_msg properties of the resource are updated with the values that you specify. Sun Cluster logs the change to the resource status in the cluster system log, which you can view with cluster administra- tion tools. You need solaris.cluster.resource.admin RBAC authorization to use this command. See rbac(5). You must also be able to assume a role to which the Sun Cluster Commands rights profile has been assigned to use this command. Authorized users can issue privileged Sun Cluster commands on the command line from the pfsh(1), pfcsh(1), or pfksh(1) profile shell. A profile shell is a special kind of shell that enables you to access privileged Sun Cluster commands that are assigned to the Sun Cluster Commands rights profile. A profile shell is launched when you run su(1M) to assume a role. You can also use pfexec(1) to issue privileged Sun Cluster com- mands. OPTIONS
The following options are supported: -G group Specifies the resource group that contains the resource. -m msg Specifies the text string that you want to assign to the Status_msg property of the resource. If you do not specify this option, the value of the resource's Status_msg is set to NULL. -R resource Specifies the resource whose status is to be set. -s status Specifies the value of status: OK, DEGRADED, FAULTED, UNKNOWN, or OFFLINE. -Z zonename Specifies the name of the non-global zone in which a resource group is configured to run. If the Global_zone property is set to TRUE, methods execute in the global zone even if the resource group that contains the resource runs in a non-global zone. The -Z option sets the status for the non-global zone where the resource group runs rather than for the global zone where the method runs. Use the -Z option only for resource types whose Global_zone property is set to TRUE. This option is not needed if the Global_zone prop- erty is set to FALSE. For more information about the Global_zone property, see the rt_properties(5) man page. EXAMPLES
Example 1 Setting the Status of Resource R1 With a Status_msg The following command sets the status of resource R1 in resource group RG2 to OK and sets the Status_msg to Resource R1 is OK: scha_resource_setstatus -R R1 -G RG2 -s OK -m "Resource R1 is OK" Example 2 Setting the Status of Resource R1 Without a Status_msg The following command sets the status of R1 in resource group RG2 to DEGRADED and sets the Status_msg to NULL: scha_resource_setstatus -R R1 -G RG2 -s DEGRADED Example 3 Setting the Status of Resource R1 in Zone Zone1 With a Status_msg The following example shows a resource type method or monitor that is implemented as a shell script. This shell script shows how to set the status of resource $resource in resource group $rg in zone $localzone to OK. This shell script also sets the Status_msg to "Resource R1 is OK". In this case, the -Z option must be specified because the resource type property Global_zone is assumed to be set to TRUE. resource= rg="" localzone="" zflag="" while getopts R:G:Z: do case $c in R) resource=$OPTARG;; G) rg=$OPTARG;; Z) zflag="-Z" localzone=$OPTARG;; esac done ... scha_resource_setstatus -R $resource -G $rg $zflag $localzone -s OK -m "Resource R1 is OK" EXIT STATUS
The following exit status codes are returned: 0 The command completed successfully. nonzero An error occurred. Failure error codes are described in scha_calls(3HA). ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWscdev | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ SEE ALSO
scha_cmds(1HA), scha_calls(3HA), scha_resource_setstatus(3HA), attributes(5), rbac(5), rt_properties(5) Sun Cluster 3.2 7 Sep 2006 scha_resource_setstatus(1HA)
All times are GMT -4. The time now is 06:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy