Setting up non-SCSI-3 I/O fencing in virtual environments using installer

If you have installed Veritas InfoScale Enterprise in virtual environments that do not support SCSI-3 PR-compliant storage, you can configure non-SCSI-3 fencing.

To configure I/O fencing using the installer in a non-SCSI-3 PR-compliant setup

  1. Start the installer with -fencing option.
    # /opt/VRTS/install/installer  -fencing

    The installer starts with a copyright message and verifies the cluster information.

  2. Confirm that you want to proceed with the I/O fencing configuration at the prompt.

    The program checks that the local node running the script can communicate with remote nodes and checks whether VCS 7.3 is configured properly.

  3. For server-based fencing, review the I/O fencing configuration options that the program presents. Type 1 to configure server-based I/O fencing.
    Select the fencing mechanism to be configured in this
    Application Cluster
    [1-7,q] 1
  4. Enter n to confirm that your storage environment does not support SCSI-3 PR.
    Does your storage environment support SCSI3 PR? 
    [y,n,q] (y) n
  5. Confirm that you want to proceed with the non-SCSI-3 I/O fencing configuration at the prompt.
  6. For server-based fencing, enter the number of CP server coordination points you want to use in your setup.
  7. For server-based fencing, enter the following details for each CP server:

    • Enter the virtual IP address or the fully qualified host name.

    • Enter the port address on which the CP server listens for connections.

      The default value is 443. You can enter a different port address. Valid values are between 49152 and 65535.

    The installer assumes that these values are identical from the view of the VCS cluster nodes that host the applications for high availability.
  8. For server-based fencing, verify and confirm the CP server information that you provided.
  9. Verify and confirm the VCS cluster configuration information.

    Review the output as the installer performs the following tasks:

    • Updates the CP server configuration files on each CP server with the following details for only server-based fencing, :

      • Registers each node of the VCS cluster with the CP server.

      • Adds CP server user to the CP server.

      • Adds VCS cluster to the CP server user.

    • Updates the following configuration files on each node of the VCS cluster

      • /etc/vxfenmode file

      • /etc/default/vxfen file

      • /etc/vxenviron file

      • /etc/llttab file

      • /etc/vxfentab (only for server-based fencing)

  10. Review the output as the installer stops VCS on each node, starts I/O fencing on each node, updates the VCS configuration file main.cf, and restarts VCS with non-SCSI-3 fencing.

    For server-based fencing, confirm to configure the CP agent on the VCS cluster.

  11. Confirm whether you want to send the installation information to us.
  12. After the installer configures I/O fencing successfully, note the location of summary, log, and response files that installer creates.

    The files provide useful information which can assist you with the configuration, and can also assist future configurations.