Sponsored Content
Full Discussion: failover on 4.5 hacmp
Operating Systems AIX failover on 4.5 hacmp Post 302208809 by encrypted on Wednesday 25th of June 2008 03:22:51 AM
Old 06-25-2008
Failover can be triggered by anything as unplugging a network interface cable to one of the nodes. Smilie
 

10 More Discussions You Might Find Interesting

1. Solaris

Interfaces do not failover

Would anyone know why a V440 Solaris 9 machine's interfaces (ce0 and ce1) will not failover? Both interfaces are on the same subnet, but different IPs. I can pull the plug on once interface (ce0) and ce1 will be accessible. I can reverse it and pull ce1, and ce0 will NOT be accessible. ... (5 Replies)
Discussion started by: StorageGuy
5 Replies

2. AIX

Can anyone shed some light on this HACMP failover?

Hello All, Here is a snipet from our cluster.log, I was wondering if anyone could shed some light on what may have caused the failover. The first two lines indicate a possible memory issue which I am currently looking into. Thanks. (0 Replies)
Discussion started by: Wez
0 Replies

3. UNIX for Advanced & Expert Users

directories failover

Hi, I have 3 directories (/1 /2 and /3) with same contents and want to achieve fail over among them. The Solution i thought of: 1. link /data to /1 (and provide users with /data to access) 2. CRON a script (to run every minute) to verify if /1 exist or not, if it does not exist (or its... (3 Replies)
Discussion started by: prvnrk
3 Replies

4. AIX

hacmp ip load balancer failover

Hi All, How do I failover on the ip load balancer (back and forth)? It involves first to load a new config on the passive ip. If success, load the new config on the ip active (which is now passive). Any idea, please. Thanks in advance. (0 Replies)
Discussion started by: itik
0 Replies

5. Solaris

IPMP failover: Why is it occurring?

The active NIC has been failing back and forth on two of our T2000s. I don't know when the problem originally began, but I can see failovers in the messages.* files. The network guy says the switches are clean (no errors) so I'm left looking at the configuration or any other issue that may be... (5 Replies)
Discussion started by: dangral
5 Replies

6. Solaris

EMC Failover

Hi guys, I'm running vxdmp and powerpath at the same time. Vxdmp for internal disks and powerpath for external. The problem is that, on the failover tests which a fiber cable should be removed, the system cannot recognize the disks. Any hints on how to configure powerpath in order to... (4 Replies)
Discussion started by: glenioborges
4 Replies

7. IP Networking

IP failover needed

All, I am looking to setup a simple IP failover setup, but it seems every place i look has some difficult setup like pacemaker or LVS. I only want to handle the IP piece to failover a VIP. Any suggestions? I checked out keepalived and that my work for me. (4 Replies)
Discussion started by: markdjones82
4 Replies

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

9. AIX

HACMP does not start db2 after failover (db2nodes not getting modified by hacmp)

hi, when I do a failover, hacmp always starts db2 but recently it fails to start db2..noticed the issue is db2nodes.cfg is not modified by hacmp and is still showing primary node..manually changed the node name to secondary after which db2 started immediately..unable to figure out why hacmp is... (4 Replies)
Discussion started by: gkr747
4 Replies

10. AIX

HACMP with VIO, service IP failover

Would anyone please kindly help to solve this problem... An LPAR with the below network configuration. ent0 and ent1 are logical lan (virtual ethernet) from VIO SEA. en0 1.2.3.4 <- boot ip 192.168.1.1 <- persistent ip 192.168.1.10 <- service ip en1 11.22.33.44 <- boot ip When I... (6 Replies)
Discussion started by: skeyeung
6 Replies
CRM_FAILCOUNT(8)						  [FIXME: manual]						  CRM_FAILCOUNT(8)

NAME
crm_failcount - manipulate the failcount attribute on a given resource SYNOPSIS
crm_failcount [-?|-V] -D -u|-U node -r resource crm_failcount [-?|-V] -G -u|-U node -r resource crm_failcount [-?|-V] -v string -u|-U node -r resource DESCRIPTION
Heartbeat implements a sophisticated method to compute and force failover of a resource to another node in case that resource tends to fail on the current node. A resource carries a resource_stickiness attribute to determine how much it prefers to run on a certain node. It also carries a resource_failure_stickiness that determines the threshold at which the resource should failover to another node. The failcount attribute is added to the resource and increased on resource monitoring failure. The value of failcount multiplied by the value of resource_failure_stickiness determines the failover score of this resource. If this number exceeds the preference set for this resource, the resource is moved to another node and not run again on the original node until the failure count is reset. The crm_failcount command queries the number of failures per resource on a given node. This tool can also be used to reset the failcount, allowing the resource to run again on nodes where it had failed too often. OPTIONS
--help, -? Print a help message. --verbose, -V Turn on debug information. Note Increase the level of verbosity by providing additional instances. --quiet, -Q When doing an attribute query using -G, print just the value to stdout. Use this option with -G. --get-value, -G Retrieve rather than set the preference. --delete-attr, -D Specify the attribute to delete. --attr-value string, -v string Specify the value to use. This option is ignored when used with -G. --node-uuid node_uuid, -u node_uuid Specify the UUID of the node to change. --node-uname node_uname, -U node_uname Specify the uname of the node to change. --resource-id resource name, -r resource name Specify the name of the resource on which to operate. EXAMPLES
Reset the failcount for the resource myrsc on the node node1: crm_failcount -D -U node1 -r my_rsc Query the current failcount for the resource myrsc on the node node1: crm_failcount -G -U node1 -r my_rsc FILES
/var/lib/heartbeat/crm/cib.xml--the CIB (minus status section) on disk. Editing this file directly is strongly discouraged. SEE ALSO
???, ???, and the Linux High Availability FAQ Web site[1] AUTHOR
crm_failcount was written by Andrew Beekhof. NOTES
1. Linux High Availability FAQ Web site http://www.linux-ha.org/v2/faq/forced_failover [FIXME: source] 07/05/2010 CRM_FAILCOUNT(8)
All times are GMT -4. The time now is 01:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy