Sponsored Content
Operating Systems Solaris Solaris Cluster Failover based on scan rate Post 302892731 by edydsuranta on Friday 14th of March 2014 10:25:41 AM
Old 03-14-2014
Quote:
Originally Posted by hergp
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.
Hi hergp,

Thank you for your response. Your though really helpful.
I'm new user in Solaris, do you have a tutorial to set the script as probe_command?

I want to test in virtual box first.
 

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
OCF_HEARTBEAT_EVMSSC(7) 					OCF resource agents					   OCF_HEARTBEAT_EVMSSC(7)

NAME
ocf_heartbeat_EvmsSCC - Manages EVMS Shared Cluster Containers (SCCs) (deprecated) SYNOPSIS
EvmsSCC [start | stop | status | monitor | meta-data] DESCRIPTION
Deprecation warning: EVMS is no longer actively maintained and should not be used. This agent is deprecated and may be removed from a future release. -- Resource script for EVMS shared cluster container. It runs evms_activate on one node in the cluster. SUPPORTED PARAMETERS
ignore_deprecation If set to true, suppresses the deprecation warning for this agent. (optional, boolean, default false) SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 60. stop Stops the resource. Suggested minimum timeout: 60. notify Suggested minimum timeout: 60. status Performs a status check. Suggested minimum timeout: 10. Suggested interval: 10. monitor Performs a detailed status check. Suggested minimum timeout: 10. Suggested interval: 10. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5. EXAMPLE
The following is an example configuration for a EvmsSCC resource using the crm(8) shell: primitive p_EvmsSCC ocf:heartbeat:EvmsSCC op monitor depth="0" timeout="10" interval="10" SEE ALSO
http://www.linux-ha.org/wiki/EvmsSCC_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 03/09/2014 OCF_HEARTBEAT_EVMSSC(7)
All times are GMT -4. The time now is 02:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy