Response file variables to configure server-based I/O fencing
You can use a coordination point server-based fencing response file to configure server-based customized I/O fencing.
Table: Coordination point server (CP server) based fencing response file definitions lists the fields in the response file that are relevant for server-based customized I/O fencing.
Related information
Table: Coordination point server (CP server) based fencing response file definitions
| Response file field | Definition |
|---|---|
| CFG {fencing_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. | |
| CFG {fencing_cpagentgrp} | Name of the service group which will have the Coordination Point agent resource as part of it. |
| Note: This field is obsolete if thefencing_config_cpagentfield is given a value of '0'. | |
| CFG {fencing_cps} | Virtual IP address or Virtual hostname of the CP servers. |
| CFG {fencing_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_reusedg}=0" | |
| or "$CFG{fencing_reusedg}=1" before proceeding with a silent installation. | |
| CFG {fencing_dgname} | The name of the disk group to be used in the customized fencing, where at least one disk |
| is being used. | |
| CFG {fencing_disks} | The disks being used as coordination points if any. |
| CFG {fencing_ncp} | Total number of coordination points being used, including both CP servers and disks. |
| CFG {fencing_ndisks} | The number of disks being used. |
| CFG {fencing_cps_vips} | The virtual IP addresses or the fully qualified host names of the CP server. |
| CFG {fencing_cps_ports} | The port that the virtual IP address or the fully qualified host name of the CP server listens on. |
| CFG{fencing_option} | Specifies the I/O fencing configuration mode. |
| - 1 - Coordination Point Server-based I/O fencing | |
| - 2 - Coordinator disk-based I/O fencing | |
| - 3 - Disabled-based I/O fencing | |
| - 4 - Online fencing migration | |
| - 5 - Refresh keys/registrations on the existing coordination points | |
| - 6 - Change the order of existing coordination points | |
| - 7 - Majority-based fencing (Required) | |
| CFG{fencing_auto_refresh_reg} | Enable this variable if registration keys are missing on any of the CP servers. |