Sponsored Content
Operating Systems Linux Red Hat RHEL 7 PaceMaker Fence Agent Options Post 302981863 by Padow1 on Tuesday 20th of September 2016 04:26:58 PM
Old 09-20-2016
Pacemaker is new in RHEL7 and is not well documented by Red Hat and the community site uses different commands/syntax so not much carries over cleanly. Pacemaker can be a pain to configure but it works very well once going and does the job it is designed to do very well. That being said, I haven't found a use case where I would use it on VM's.

Stonith/fencing is a vital part of pacemaker, but if you are just testing you can disable it and the resources will start without it.

Code:
pcs property set stonith-enabled=false

 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

electric fence

hi, i have downloaded electric fence from website,but i dnt know to install it in my system,plz tel me the procedure to install new packages into my system. (2 Replies)
Discussion started by: m.mujahid
2 Replies

2. UNIX for Dummies Questions & Answers

Fence status - beginners problems!!

Hi, I'd like to try and capture a fence status from Maestro and move it to another file, but each time I try it fails. For example, when using Maestro (conman) I enter: status I then get the fence status showing as 0 I then create a .dat file: touch statustest.dat If I... (0 Replies)
Discussion started by: tjhorwood
0 Replies

3. Red Hat

Error throwing while installing vsftpd package in rhel 6. using rhel 6 dvd.

Hi all, Im studying rhcsa as of now, so yum installation and dependencies are messing me to not workit out. i have dual os, win 7 & rhel 6. i have tried this installation of vsftpd package with rhel 6 dvd in VM rhel 6 in win 7 as well as host rhel 6.still the same issue. below error... (6 Replies)
Discussion started by: redhatlbug
6 Replies

4. Red Hat

Oracle ha from rgmanager to pacemaker

Hi, I've got one question about oracle rgmanager resource agent and ocf script. Rgmanager oracledb.sh script has an options called "vhost" which set the "ORACLE_HOSTNAME" value when you have different different cards on the same machine and different oracle instances. In ocf: heartbeat:... (0 Replies)
Discussion started by: lantuin
0 Replies

5. Red Hat

PaceMaker Cluster Fence Device

I have 2 VM's setup with a shared VMware disk running RHEL 7.1 (just updated to 7.2 with yum update), and would like to know what is the easiest Fence device to implement for testing purposes. Apparently, I need a fence device before my IP resources will come online. I have the cluster... (1 Reply)
Discussion started by: mrmurdock
1 Replies

6. AIX

IBM Power Linux Cluster Fence device on Power8 Platform

wasn't quite sure which forum to post in. What typical fence device to configure for a Power Linux PaceMaker Cluster running on the Power8 Platform (S822 Model of hardware), or what should be ordered with the S822 for use as a Fence Device? (5 Replies)
Discussion started by: mrmurdock
5 Replies

7. Red Hat

[HA] Red Hat 7, pacemaker and start/stop scripts

Hi there, I am wondering if I could add start/stop ksh scripts provided by 3rd party to cluster... I read that script must be ocf/lsb compliant, however, in AIX I can just set up two separate scripts for starting and stopping application. Can similar be done under RH Linux cluster? Cheers, c (1 Reply)
Discussion started by: cyjan
1 Replies

8. Shell Programming and Scripting

Bash script to add multiple resources to NFS pacemaker cluster

All, I'm looking for some guidance on how to accomplish automating the addition of exports to an HA Pacemaker NFS cluster. I would like to do it in bash for logistics reasons. The resource creation command looks like this: pcs resource create nfs-b2b-hg-media-10.1 exportfs... (6 Replies)
Discussion started by: hburnswell
6 Replies

9. Red Hat

Linux PaceMaker Equivalent to a SharedAddress Resource Type

In HA platforms, there is the concept of a "Scalable Resource Type, which included the sharedaddress" that is used in commonly Web Servers resource groups. The sharedaddress resource type is provided so a developer can use this Resource type to build their own scalable resource group. I see... (1 Reply)
Discussion started by: mrmurdock
1 Replies
POLICY 
ENGINE(8) Pacemaker Configuration POLICY ENGINE(8) NAME
pengine - Policy Engine Options SYNOPSIS
[no-quorum-policy=enum] [symmetric-cluster=boolean] [default-resource-stickiness=integer] [is-managed-default=boolean] [maintenance-mode=boolean] [start-failure-is-fatal=boolean] [enable-startup-probes=boolean] [stonith-enabled=boolean] [stonith-action=enum] [stonith-timeout=time] [startup-fencing=boolean] [cluster-delay=time] [batch-limit=integer] [default-action-timeout=time] [stop-all-resources=boolean] [stop-orphan-resources=boolean] [stop-orphan-actions=boolean] [remove-after-stop=boolean] [pe-error-series-max=integer] [pe-warn-series-max=integer] [pe-input-series-max=integer] [node-health-strategy=enum] [node-health-green=integer] [node-health-yellow=integer] [node-health-red=integer] [placement-strategy=enum] DESCRIPTION
This is a fake resource that details the options that can be configured for the Policy Engine. SUPPORTED PARAMETERS
no-quorum-policy = enum [stop] What to do when the cluster does not have quorum What to do when the cluster does not have quorum Allowed values: stop, freeze, ignore, suicide symmetric-cluster = boolean [true] All resources can run anywhere by default default-resource-stickiness = integer [0] is-managed-default = boolean [true] Should the cluster start/stop resources as required maintenance-mode = boolean [false] Should the cluster monitor resources and start/stop them as required start-failure-is-fatal = boolean [true] Always treat start failures as fatal This was the old default. However when set to FALSE, the cluster will instead use the resource's failcount and value for resource-failure-stickiness enable-startup-probes = boolean [true] Should the cluster check for active resources during startup stonith-enabled = boolean [true] Failed nodes are STONITH'd stonith-action = enum [reboot] Action to send to STONITH device Action to send to STONITH device Allowed values: reboot, poweroff stonith-timeout = time [60s] How long to wait for the STONITH action to complete startup-fencing = boolean [true] STONITH unseen nodes Advanced Use Only! Not using the default is very unsafe! cluster-delay = time [60s] Round trip delay over the network (excluding action execution) The "correct" value will depend on the speed and load of your network and cluster nodes. batch-limit = integer [30] The number of jobs that the TE is allowed to execute in parallel The "correct" value will depend on the speed and load of your network and cluster nodes. default-action-timeout = time [20s] How long to wait for actions to complete stop-all-resources = boolean [false] Should the cluster stop all active resources (except those needed for fencing) stop-orphan-resources = boolean [true] Should deleted resources be stopped stop-orphan-actions = boolean [true] Should deleted actions be cancelled remove-after-stop = boolean [false] Remove resources from the LRM after they are stopped Always set this to false. Other values are, at best, poorly tested and potentially dangerous. pe-error-series-max = integer [-1] The number of PE inputs resulting in ERRORs to save Zero to disable, -1 to store unlimited. pe-warn-series-max = integer [-1] The number of PE inputs resulting in WARNINGs to save Zero to disable, -1 to store unlimited. pe-input-series-max = integer [-1] The number of other PE inputs to save Zero to disable, -1 to store unlimited. node-health-strategy = enum [none] The strategy combining node attributes to determine overall node health. Requires external entities to create node attributes (named with the prefix '#health') with values: 'red', 'yellow' or 'green'. Allowed values: none, migrate-on-red, only-green, progressive, custom node-health-green = integer [0] The score 'green' translates to in rsc_location constraints Only used when node-health-strategy is set to custom or progressive. node-health-yellow = integer [0] The score 'yellow' translates to in rsc_location constraints Only used when node-health-strategy is set to custom or progressive. node-health-red = integer [-INFINITY] The score 'red' translates to in rsc_location constraints Only used when node-health-strategy is set to custom or progressive. placement-strategy = enum [default] The strategy to determine resource placement The strategy to determine resource placement Allowed values: default, utilization, minimal, balanced AUTHOR
Andrew Beekhof <andrew@beekhof.net> Author. Pacemaker Configuration 07/05/2010 POLICY ENGINE(8)
All times are GMT -4. The time now is 12:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy