Response file variables to configure disk-based I/O fencing
Table: Response file variables specific to configuring disk-based I/O fencing lists the response file variables that specify the required information to configure disk-based I/O fencing for VCS.
Table: Response file variables specific to configuring disk-based I/O fencing
| Variable | List or Scalar | Description |
|---|---|---|
| CFG{opt}{fencing} | Scalar | Performs the I/O fencing configuration. |
| (Required) | ||
| CFG{fencing_option} | Scalar | 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_dgname} | Scalar | Specifies the disk group for I/O fencing. |
| (Optional) | ||
| Note: You must define the fencing_dgname variable to use an existing disk group. If you want to create a new disk group, you must use both the fencing_dgname variable and the fencing_newdg_disks variable. | ||
| CFG{fencing_newdg_disks} | List | Specifies the disks to use to create a new disk group for I/O fencing. |
| (Optional) | ||
| Note: You must define the fencing_dgname variable to use an existing disk group. If you want to create a new disk group, you must use both the fencing_dgname variable and the fencing_newdg_disks variable. | ||
| CFG{fencing_cpagent_monitor_freq} | Scalar | Specifies the frequency at which the Coordination Point Agent monitors for any changes to the Coordinator Disk Group constitution. |
| Note: Coordination Point Agent can also monitor changes to the Coordinator Disk Group constitution such as a disk being accidently deleted from the Coordinator Disk Group. The frequency of this detailed monitoring can be tuned with the LevelTwoMonitorFreq attribute. For example, if you set this attribute to 5, the agent will monitor the Coordinator Disk Group constitution every five monitor cycles. If LevelTwoMonitorFreq attribute is not set, the agent will not monitor any changes to the Coordinator Disk Group. 0 means not to monitor the Coordinator Disk Group constitution. | ||
| CFG {fencing_config_cpagent} | Scalar | 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} | Scalar | 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_auto_refresh_reg} | Scalar | Enable the auto refresh of coordination points variable in case registration keys are missing on any of CP servers. |
Related information