Modifying VCS configuration to use I/O fencing

After you add coordinator disks and configure I/O fencing, add the UseFence = SCSI3 cluster attribute to the VCS configuration file /etc/VRTSvcs/conf/config/main.cf. If you reset this attribute to UseFence = None, VCS does not make use of I/O fencing abilities while failing over service groups. However, I/O fencing needs to be disabled separately.

To modify VCS configuration to enable I/O fencing

  1. Save the existing configuration:

    # haconf -dump -makero
  2. Stop VCS on all nodes:

    # hastop -all
  3. If the I/O fencing driver vxfen is already running, stop the I/O fencing driver.

    # /sbin/init.d/vxfen stop
  4. Make a backup copy of the main.cf file:

    # cd /etc/VRTSvcs/conf/config
    # cp main.cf main.orig
  5. On one node, use vi or another text editor to edit the main.cf file. To modify the list of cluster attributes, add the UseFence attribute and assign its value as SCSI3.

    cluster clus1(
    UserNames = { admin = "cDRpdxPmHpzS." }
    Administrators = { admin }
    HacliUserLevel = COMMANDROOT
    CounterInterval = 5
    UseFence = SCSI3
    )
  6. Save and close the file.

  7. Verify the syntax of the file /etc/VRTSvcs/conf/config/main.cf:

    # hacf -verify /etc/VRTSvcs/conf/config
  8. Using rcp or another utility, copy the VCS configuration file from a node (for example, galaxy) to the remaining cluster nodes.

    For example, on each remaining node, enter:

    # rcp galaxy:/etc/VRTSvcs/conf/config/main.cf \
    /etc/VRTSvcs/conf/config

  9. Start the I/O fencing driver and VCS. Perform the following steps on each node:

    • Start the I/O fencing driver.

      The vxfen startup script also invokes the vxfenconfig command, which configures the vxfen driver to start and use the coordinator disks that are listed in /etc/vxfentab.

      # /sbin/init.d/vxfen start
    • Start VCS.

      # /opt/VRTS/bin/hastart