Response file variables to configure non-SCSI-3 I/O fencing
Table: Non-SCSI-3 I/O fencing response file definitions lists the fields in the response file that are relevant for non-SCSI-3 I/O fencing.
Related information
Table: Non-SCSI-3 I/O fencing response file definitions
| Response file field | Definition |
|---|---|
| CFG{non_scsi3_fencing} | Defines whether to configure non-SCSI-3 I/O fencing. |
| Valid values are 1 or 0. Enter 1 to configure non-SCSI-3 I/O fencing. | |
| 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. | |
| Note: This variable does not apply to majority-based fencing. | |
| 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'. This variable does not apply to majority-based fencing. | |
| CFG {fencing_cps} | Virtual IP address or Virtual hostname of the CP servers. |
| Note: This variable does not apply to majority-based fencing. | |
| CFG {fencing_cps_vips} | The virtual IP addresses or the fully qualified host |
| names of the CP server. | |
| Note: This variable does not apply to majority-based fencing. | |
| CFG {fencing_ncp} | Total number of coordination points (CP servers only) being used. |
| Note: This variable does not apply to majority-based fencing. | |
| CFG {fencing_cps_ports} | The port of the CP server that is denoted by cps |
| . | |
| Note: This variable does not apply to majority-based fencing. | |
| CFG{fencing_auto_refresh_reg} | Enable this variable if registration keys |
| are missing on any of the CP servers. |