Configuring a quarantine policy

You can configure a quarantine policy with PowerHA® SystemMirror® to isolate the previously active node that was hosting a critical resource group after a cluster split event or node failure occurs. The quarantine policy ensures that your application data is not corrupted or lost.

1. From the command line, enter smit sysmirror
2. In the SMIT interface, select Custom Cluster Configuration > Cluster Nodes and Networks > Initial Cluster Setup (Custom) > Configure Cluster Split and Merge Policy > Quarantine Policy, and press Enter.
3. Select one of the following options:

   Active Node Halt Policy

   Select this option to stop the node that is unresponsive before PowerHA SystemMirror acquires the critical resource group. To use this option, you must identify the critical resource group. The critical resource group is the first resource group that is processed when a cluster split occurs, and the Active Node Halt Policy is applied to your cluster.

   Disk Fencing

   The disks that are related to the critical resource group are fenced off from the previously active node. The disks in the volume groups that are configured for all resource groups on that node are fenced off. This option ensures that the node that contains the critical resource group cannot access the disks in case a cluster split event occurs. To use this option, you must identify the critical resource group and the storage subsystem must support SCSI-3 persistent reservation and ODM reserve_policy of PR_SHARED. This policy is applied to all disks that are part of the volume group and resource group.

4. Verify and synchronize the changes across the cluster.