Sponsored Content
Operating Systems Solaris Solaris Cluster Failover based on scan rate Post 302892690 by hergp on Friday 14th of March 2014 05:54:33 AM
Old 03-14-2014
This should work if you add a resource of type SUNW.gds to the resource group. Create a shell script which checks for acceptable scan rates. Let the script return 0, if scan rate is ok and 1 otherwise. Then set this script as Probe_command of the resource. If scan rate is too high, the resource will "fail" and trigger a cluster switch of the resource group.

We don't have any running solaris cluster here any more, so I cannot verify this procedure. You should try it on a test machine first.
This User Gave Thanks to hergp For This Post:
 

10 More Discussions You Might Find Interesting

1. High Performance Computing

sun Cluster resource group cant failover

I have rcently setup a 4 node cluster running sun cluster 3.2 and I have installed 4 zones on each node. when installing the zones I had to install the zone on all nodes the on the last node do a zlogin -C <zonename> this worked ok. theni I tried to siwitch the zone to node a thei work... (14 Replies)
Discussion started by: lesliek
14 Replies

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

3. 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 (5 Replies)
Discussion started by: Mack1982
5 Replies

4. 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 (3 Replies)
Discussion started by: sidharthmellam
3 Replies

5. AIX

Scan Rate

Hello, How can i tell ifthe ratio between fr and sr is ok? is fr/sr ratio of 0.9 acceptable? thanks. (1 Reply)
Discussion started by: LiorAmitai
1 Replies

6. AIX

AIX Scan Rate threshold

Hi Guys, The management is being frisky about scan rate in the range of a few thousands ( 4 digit scan rates occasionally). After much research ive concluded that its ok to have high scan rates , unless it leads to swapping/ it falls above 1:4 ratio with free rate (fr:sr) My question is:... (2 Replies)
Discussion started by: muzahed
2 Replies

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

8. Solaris

Need Suggestions to monitoring Scan Rate

Hi All, I need suggestions to monitoring Scan Rate on Solaris Operating System. Any idea? Thanks Edy (5 Replies)
Discussion started by: edydsuranta
5 Replies

9. Solaris

Formula calculate scan rate

Hi There, Just curious here... If there formula to calculate scan rate on solaris? Thanks Edy (3 Replies)
Discussion started by: edydsuranta
3 Replies

10. 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... (2 Replies)
Discussion started by: munna529
2 Replies
scdscreate(1HA) 					       Sun Cluster Commands						   scdscreate(1HA)

NAME
scdscreate - create a Sun Cluster resource type template SYNOPSIS
scdscreate -V vendor_id -T resource_type_name -a [-s] [-n RT_version] [-d working_directory] [-k | -g] DESCRIPTION
The scdscreate command creates a template for making an application highly available (HA) or scalable. This command enables you to create C-, Generic Data Service (GDS)-, or Korn shell-based templates for both network aware (client-server model) and non-network aware (client- less) applications. You can create the template in one of two fundamentally different ways: GDS scdscreate creates a set of three driving scripts that work from a single resource type SUNW.gds, which is pre- installed on the cluster. These scripts are named startRT_Name, stopRT_Name, and removeRT_Name and starts, stops, and removes an instance of that application. In this model, the implementation of the SUNW.gds resource type that is pre-installed on the cluster is immutable. Generated Source Code scdscreate creates a template for a Sun Cluster resource type, whose instantiations run under the control of the Resource Group Manager (RGM) to make the given application highly available and scalable. Either model can create templates for network aware (client-server model) and non-network aware (client-less) applications. scdscreate creates a directory of the form $vendor_id$resource_type_name under working_directory. This directory contains the driving scripts, or the generated source, binary, and package files for the resource type. scdscreate also creates a configuration file, rtconfig, in which you can store configuration information for the resource type. scdscreate allows you to create only one resource type per direc- tory. You must create different resource types in different directories. OPTIONS
The following options are supported: -a This parameter specifies that the resource type that is being created is not network aware. scdscreate disables all the networking related code in the template that is created. -n RT_version This optional parameter specifies the version of the generated resource's type. If you omit this parameter, and you're creating a C- or Korn shell-based application, the text string 1.0 is used by default. If you omit this parameter, and you're creating a GDS-based application, the RT_version string of the GDS is used by default. The RT_version distinguishes between multiple registered versions, or upgrades, of the same base resource type. You cannot include the following characters in RT_version: blank, tab, slash (/), backslash (), asterisk (*), question mark (?), comma (,), semicolon (;), left square bracket ([), or right square bracket (]). -d working_directory Creates the template for the resource type in a directory other than the current directory. If you omit this argument, scdscreate creates the template in the current directory. -g This optional parameter generates the GDS-based form of the template to make an application highly available or scalable. -k This optional parameter generates source code in Korn shell command syntax rather than in C. See ksh(1). -s This optional parameter indicates that the resource type is scalable. You can configure an instance (resource) of a scalable resource type into a failover resource group, and hence, turn off the scalability feature. If you omit this argument, scdscreate creates the template for a failover resource type. -T resource_type_name The resource type name and resource type version, in conjunction with the vendor ID, uniquely identifies the resource type that is being created. -V vendor_id The vendor ID is typically the stock symbol, or some other identifier of the vendor that is creating the resource type. scdscreate affixes the vendor ID, followed by a period (.) to the beginning of the resource type name. This syntax ensures that the resource type name remains unique if more than one vendor uses the same resource type name. EXIT STATUS
0 The command completed successfully. nonzero An error occurred. FILES
working_directory/rtconfig Contains information from the previous session and facilitates the quit and restart feature of scdscre- ate. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWscdev | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
ksh(1), scdsbuilder(1HA), scdsconfig(1HA), attributes(5), rt_properties(5) Sun Cluster Data Services Developer's Guide for Solaris OS Sun Cluster 3.2 26 May 2004 scdscreate(1HA)
All times are GMT -4. The time now is 07:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy