Response file variables to configure server-based I/O fencing


Response file variables to configure server-based I/O fencing
Prev	Appendix C. Configuring I/O fencing using a response file	Next

You can use a CP server response file to configure server-based customized I/O fencing. The installer uses the CP server response file for the following types of I/O fencing configurations:

Client cluster fencing (server-based I/O fencing configuration itself)

The installer configures server-based customized I/O fencing on the SFCFS cluster without prompting for user input.
Disk-based fencing with the disk group already created

The installer configures fencing in disk-based mode on the SFCFS cluster without prompting for user input.

Disk-based fencing configuration is one in which SCSI-3 disks are used as the only coordination points.

Disk-based fencing with the disk group already created means that the disk group consisting of the coordinating disks already exists on the SFCFS cluster nodes.
Disk-based fencing with the disk group to be created

The installer creates the disk group and configures fencing properly on all the nodes in the SFCFS cluster without user intervention.

Disk-based fencing with the disk group to be created means that the disk group does not exist yet, but will be created with the disks mentioned as coordination point.

Table: CP server response file definitions lists the fields in the response file that are relevant for server-based customized I/O fencing.

Table: CP server response file definitions

Response file field

Definition

fencing_cpc_config_cpagent

Enter '1' or '0' depending upon whether you want to configure the Coordination Point agent using the installer or not.

Enter "0" if you do not want to configure the Coordination Point agent using the installer.

Enter "1" if you want to use the installer to configure the Coordination Point agent.

fencing_cpc_cpagentgrp

Name of the service group which will have the Coordination Point agent resource as part of it.

Note:

This field is obsolete if the fencing_cpc_config_cpagent field is given a value of '0'.

fencing_cpc_cps

Virtual IP address or Virtual hostname of the CP servers.

fencing_cpc_reusedg

This response file field indicates whether to reuse an existing DG name for the fencing configuration in customized fencing (CP server and coordinator disks).

Enter either a "1" or "0".

Entering a "1" indicates reuse, and entering a "0" indicates do not reuse.

When reusing an existing DG name for the mixed mode fencing configuration. you need to manually add a line of text , such as "$CFG{fencing_cpc_reusedg}=0" or "$CFG{fencing_cpc_reusedg}=1" before proceeding with a silent installation.

fencing_cpc_dgname

The name of the disk group to be used in the customized fencing, where at least one disk is being used.

fencing_cpc_diffab

This response field indicates whether the CP servers and SFCFS clusters use different root brokers.

Entering a "1" indicates that they are using different root brokers.

Entering a "0" indicates that they are not using different root brokers.

fencing_cpc_disks

The disks being used as coordination points if any.

fencing_cpc_ncps

Total number of coordination points being used, including both CP servers and disks.

fencing_cpc_ndisks

The number of disks being used.

fencing_cpc_ports

The port of the CP server that is denoted by cps .

fencing_cpc_ccab

The name of the authentication broker (AB) for any one of the SFCFS cluster nodes.

fencing_cpc_cpsabport

The port at which the authentication broker (AB) mentioned above listens for authentication..

fencing_cpc_ccabport

The port at which the authentication broker (AB) mentioned above listens for authentication.

fencing_cpc_mechanism

The disk mechanism that is used by customized fencing.

The value for this field is either "raw" or "dmp"

fencing_cpc_cpsab

The name of the authentication broker (AB) for any one of the CP servers.

fencing_cpc_security

This field indicates whether security is enabled or not

Entering a "1" indicates that security is enabled. Entering a "0" indicates that security has not been enabled.

Prev	Up	Next
Configuring I/O fencing using response files	Home	Sample response file for configuring server-based I/O fencing