Search <book_title>...

InfoScale™ 9.0 Storage Foundation and High Availability Configuration and Upgrade Guide - Linux

Last Published: 2025-04-21

Product(s): InfoScale & Storage Foundation (9.0)

Platform: Linux

Section I. Introduction to SFHA
1. Introducing Storage Foundation and High Availability
Section II. Configuration of SFHA
Section III. Upgrade of SFHA
Section IV. Post-installation tasks
1. Performing post-installation tasks
  1. Switching on Quotas
  2. About configuring authentication for SFDB tools
    1. Configuring vxdbd for SFDB tools authentication
Section V. Adding and removing nodes
1. Adding a node to SFHA clusters
2. Removing a node from SFHA clusters
  1. Removing a node from a SFHA cluster
Section VI. Configuration and upgrade reference

Enabling or disabling the preferred fencing policy

You can enable or disable the preferred fencing feature for your I/O fencing configuration.

You can enable preferred fencing to use system-based race policy, group-based race policy, or site-based policy. If you disable preferred fencing, the I/O fencing configuration uses the default count-based race policy.

Preferred fencing is not applicable to majority-based I/O fencing.

See About preferred fencing.

To enable preferred fencing for the I/O fencing configuration

Make sure that the cluster is running with I/O fencing set up.
```
# vxfenadm -d
```
Make sure that the cluster-level attribute UseFence has the value set to SCSI3.
```
# haclus -value UseFence
```
To enable system-based race policy, perform the following steps:
- Make the VCS configuration writable.
```
# haconf -makerw
```
- Set the value of the cluster-level attribute PreferredFencingPolicy as System.
```
# haclus -modify PreferredFencingPolicy System
```
- Set the value of the system-level attribute FencingWeight for each node in the cluster.
  For example, in a two-node cluster, where you want to assign sys1 five times more weight compared to sys2, run the following commands:
```
# hasys -modify sys1 FencingWeight 50
# hasys -modify sys2 FencingWeight 10
```
- Save the VCS configuration.
```
# haconf -dump -makero
```
- Verify fencing node weights using:
```
# vxfenconfig -a
```
To enable group-based race policy, perform the following steps:
- Make the VCS configuration writable.
```
# haconf -makerw
```
- Set the value of the cluster-level attribute PreferredFencingPolicy as Group.
```
# haclus -modify PreferredFencingPolicy Group
```
- Set the value of the group-level attribute Priority for each service group.
  For example, run the following command:
```
# hagrp -modify service_group Priority 1
```
  Make sure that you assign a parent service group an equal or lower priority than its child service group. In case the parent and the child service groups are hosted in different subclusters, then the subcluster that hosts the child service group gets higher preference.
- Save the VCS configuration.
```
# haconf -dump -makero
```
To enable site-based race policy, perform the following steps:
- Make the VCS configuration writable.
```
# haconf -makerw
```
- Set the value of the cluster-level attribute PreferredFencingPolicy as Site.
```
# haclus -modify PreferredFencingPolicy Site
```
- Set the value of the site-level attribute Preference for each site.
```
For example, 
# hasite -modify Pune Preference 2
```
- Save the VCS configuration.
```
# haconf -dump  - makero
```
To view the fencing node weights that are currently set in the fencing driver, run the following command:
```
# vxfenconfig -a
```

To disable preferred fencing for the I/O fencing configuration

Make sure that the cluster is running with I/O fencing set up.
```
# vxfenadm -d
```
Make sure that the cluster-level attribute UseFence has the value set to SCSI3.
```
# haclus -value UseFence
```
To disable preferred fencing and use the default race policy, set the value of the cluster-level attribute PreferredFencingPolicy as Disabled.
```
# haconf -makerw
# haclus -modify PreferredFencingPolicy Disabled
# haconf -dump -makero
```