Sponsored Content
Operating Systems Linux Red Hat PaceMaker Cluster Fence Device Post 302979510 by mrmurdock on Monday 15th of August 2016 03:40:20 PM
Old 08-15-2016
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 installed and basic setup. since they took away my quorum disk (qdiskd) usage, what do I rely on for quorum?
 

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

Solaris cluster scdidadm Inquiry on device failed.

Solaris 10, Solaris Cluser 3.2, two node cluster, all software installed succefully, all nodes join to the cluster And on snod2 didn't recognize disks as a did devices and I can't make a quorum device. snod1#/usr/cluster/bin/cluster status === Cluster Nodes === --- Node Status --- Node... (2 Replies)
Discussion started by: Uran
2 Replies

4. Solaris

Increasing Raw device Sun Cluster 3.0

Hi All , I would like to know the procedure for increasing shared volume space in sun cluster . Currently the configuration is like these . Main stripe oradb1/d91 2 1 /dev/did/rdsk/d35s0 1 /dev/did/rdsk/d36s0 =Total 49 Gb oradb1/d94 -p oradb1/d91 -o 88080480 -b 14680064 ==Total 7 GB... (4 Replies)
Discussion started by: sahil_shine
4 Replies

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

6. Red Hat

RHEL 7 PaceMaker Fence Agent Options

my options are getting very limited very fast on what agent to use with my 2 Node RHEL 7 VM Cluster. fence_vmware_soap "plug id"? I have a ESX resource cluster of 7 blades being managed by a Vsphere 6.0 server. I found the blade that the Cluster VM(s) is housed on. WTF is the plug id... (3 Replies)
Discussion started by: mrmurdock
3 Replies

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

8. Solaris

Solaris Cluster Device Problem

I build up two node cluster (node1, node2) in virtualbox. For these two nodes I add 5 shared disk. (Also each node have own OS disk). 1 shared disk for vtoc 2 shared disk for NFS resource group 2 shared disk for WEB resource group When I finished my work; two nodes was ok and shared disk... (4 Replies)
Discussion started by: sonofsunra
4 Replies

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

10. 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
scconf_quorum_dev_scsi(1M)				  System Administration Commands				scconf_quorum_dev_scsi(1M)

NAME
scconf_quorum_dev_scsi - Add and remove shared SCSI quorum devices and change various SCSI cluster quorum configuration properties or states. SYNOPSIS
scconf {-a|-c|-r} -q globaldev=devicename otheroptions scconf {-a|-c|-r} -q name=devicename otheroptions DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. A SCSI quorum device is considered to be any Sun Cluster supported, attached storage that is connected to two or more nodes of the cluster. The device must be managed by DID, and the device name that is provided must be a DID device name. The SCSI quorum device has no other properties that can be specified. OPTIONS
The following options are specific to shared disk quorum devices. See scconf(1M) for the list of supported generic options. See scconf_quo- rum_dev_netapp_nas(1M) for options that are specific to NAS quorum devices. The add and remove forms of the command are used to add and remove shared quorum devices to or from the configuration. The change form of the command is used for changing various properties of cluster quorum configuration. The -q quorum-options available for each of the three forms of the command can be used to change the cluster quorum configuration are as follows: Add a shared quorum device: -q -a globaldev=devicename[, node=node,node=node[, ...]] or -q -a name= devicename,type=scsi or -q -a autoconfig[,noop] Change a property or state of quorum configuration: -q -c globaldev=devicename,{maintstate | reset} or -q -c autoconfig[,noop] Remove a shared quorum device: -q -r globaldev=devicename or -q -r name=devicename autoconfig When used with the add form of the command, automatically chooses and assigns one quorum device in the two-node cluster. The quorum device is chosen from the available devices. If a quorum device is already configured, the command aborts. When used with the change form of the command, automatically chooses and assigns one device that replaces all existing quorum devices in the two-node cluster. The quorum device is chosen from the available devices. All available devices in the cluster must be qualified to be a quorum device. The autoconfig suboption does not assess whether an available device is qualified to be a quorum device. If the cluster contains more than two nodes, the autoconfig suboption makes no changes to the quorum configuration. Do not use the autoconfig suboption if you intend to configure a NAS device as quorum. [,noop] Is valid with the autoconfig suboption. The command prints to standard output the list of quorum devices that the autoconfig suboption would add or change. The autoconfig,noop suboption makes no changes to the quorum configuration. When scconf is interrupted or fails while performing quorum-related operations, quorum configuration information can become inconsistent in the cluster configuration database. If an inconsistency occurs, either run the same scconf command again or run it with the reset option to reset the quorum information. With the add form of the command, if a name is specified without a node list, the quorum device is added with a port defined for every node to which the device is attached. But, if a node list is given, at least two nodes must be provided, and each node in the list must be ported to the device. EXAMPLES
Example 1 Adding SCSI Quorum Devices The following scconf commands adds a SCSI quorum device. -a -q globaldev=/dev/did/rdsk/d4s2 or -a -q name=/dev/did/rdsk/d4s2,type=scsi Example 2 Changing SCSI Quorum Devices The following scconf command changes a SCSI quorum device configuration. -c -q globaldev=/dev/did/rdsk/d4s2,reset or -c -q name=/dev/did/rdsk/d4s2,reset Example 3 Removing SCSI Quorum Devices The following scconf command removes the SCSI quorum device. qd1. -r -q globaldev=qd1 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), clquorum(1CL), cluster(1CL), scconf(1M), scconf_quorum_dev_netapp_nas(1M) Sun Cluster 3.2 10 Apr 2006 scconf_quorum_dev_scsi(1M)
All times are GMT -4. The time now is 01:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy