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
PACEMAKER(8)						  System Administration Utilities					      PACEMAKER(8)

NAME
Pacemaker - Part of the Pacemaker cluster resource manager SYNOPSIS
crm_resource (query|command) [options] DESCRIPTION
crm_resource - Perform tasks related to cluster resources. Allows resources to be queried (definition and location), modified, and moved around the cluster. OPTIONS
-?, --help This text -$, --version Version information -V, --verbose Increase debug output -Q, --quiet Print only the value on stdout -r, --resource=value Resource ID Queries: -L, --list List all resources -l, --list-raw List the IDs of all instantiated resources (no groups/clones/...) -O, --list-operations List active resource operations. Optionally filtered by resource (-r) and/or node (-N) -o, --list-all-operations List all resource operations. Optionally filtered by resource (-r) and/or node (-N) -q, --query-xml Query the definition of a resource (template expanded) -w, --query-xml-raw Query the definition of a resource (raw xml) -W, --locate Display the current location(s) of a resource -A, --stack Display the prerequisites and dependents of a resource -a, --constraints Display the (co)location constraints that apply to a resource Commands: -p, --set-parameter=value Set the named parameter for a resource. See also -m, --meta -g, --get-parameter=value Display the named parameter for a resource. See also -m, --meta -d, --delete-parameter=value Delete the named parameter for a resource. See also -m, --meta -M, --move Move a resource from its current location, optionally specifying a destination (-N) and/or a period for which it should take effect (-u) If -N is not specified, the cluster will force the resource to move by creating a rule for the current location and a score of -INFINITY NOTE: This will prevent the resource from running on this node until the constraint is removed with -U -U, --un-move Remove all constraints created by a move command Advanced Commands: -D, --delete Delete a resource from the CIB -F, --fail Tell the cluster this resource has failed -R, --refresh (Advanced) Refresh the CIB from the LRM -C, --cleanup (Advanced) Delete a resource from the LRM -P, --reprobe (Advanced) Re-check for resources started outside of the CRM Additional Options: -N, --node=value Host uname -t, --resource-type=value Resource type (primitive, clone, group, ...) -v, --parameter-value=value Value to use with -p, -g or -d -u, --lifetime=value Lifespan of migration constraints -m, --meta Modify a resource's configuration option rather than one which is passed to the resource agent script. For use with -p, -g, -d -z, --utilization Modify a resource's utilization attribute. For use with -p, -g, -d -s, --set-name=value (Advanced) ID of the instance_attributes object to change -i, --nvpair=value (Advanced) ID of the nvpair object to change/delete -f, --force EXAMPLES
List the configured resources: # crm_resource --list Display the current location of 'myResource': # crm_resource --resource myResource --locate Move 'myResource' to another machine: # crm_resource --resource myResource --move Move 'myResource' to a specific machine: # crm_resource --resource myResource --move --node altNode Allow (but not force) 'myResource' to move back to its original location: # crm_resource --resource myResource --un-move Tell the cluster that 'myResource' failed: # crm_resource --resource myResource --fail Stop a 'myResource' (and anything that depends on it): # crm_resource --resource myResource --set-parameter target-role --meta --parameter-value Stopped Tell the cluster not to manage 'myResource': The cluster will not attempt to start or stop the resource under any circumstances. Useful when performing maintenance tasks on a resource. # crm_resource --resource myResource --set-parameter is-managed --meta --parameter-value false Erase the operation history of 'myResource' on 'aNode': The cluster will 'forget' the existing resource state (including any errors) and attempt to recover the resource. Useful when a resource had failed permanently and has been repaired by an administrator. # crm_resource --resource myResource --cleanup --node aNode AUTHOR
Written by Andrew Beekhof REPORTING BUGS
Report bugs to pacemaker@oss.clusterlabs.org Pacemaker 1.1.7 April 2012 PACEMAKER(8)
All times are GMT -4. The time now is 02:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy