To migrate from server-based fecing to disk-based fencing using the installer

1. Make sure system-to-system communication is functioning properly.
2. Make sure that the VCS cluster is configured to use server-based fencing.

   # vxfenadm -d

   For example, if the VCS cluster uses server-based fencing, the output appears similar to the following:

   I/O Fencing Cluster Information:
   ================================
   Fencing Protocol Version: 201
   Fencing Mode: Customized
   Fencing Mechanism: cps
   Cluster Members:
   		* 0 (galaxy)
   		1 (nebula)
   RFSM State Information:
   		node 0 in state 8 (running)
   		node 1 in state 8 (running)

3. On any node in the cluster, start the installvcs program with the -fencing option.

   # /opt/VRTS/install/installvcs -fencing

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

   Note the location of log files which you can access in the event of any problem with the configuration process.

4. Confirm that you want to proceed with the I/O fencing configuration.

   The installer verifies whether I/O fencing is configured in enabled mode.

5. Confirm that you want to reconfigure I/O fencing.
6. Review the I/O fencing configuration options that the program presents. Type 4 to migrate to disk-based I/O fencing.

   Select the fencing mechanism to be configured in this
   Application Cluster [1-4,q] 4

7. From the list of coordination points that the installer presents, select the coordination points that you want to replace.

   For example:

   Select the coordination points you would like to remove
   from the currently configured coordination points:
      1) emc_clariion0_62
      2) [10.209.80.197]:14250,[10.209.80.199]:14300
      3) [10.209.80.198]:14250
      4) All
      5) None
      b) Back to previous menu
   Enter the options separated by spaces: [1-5,b,q,?] (5)? 2 3

8. Enter the total number of new coordination points.
9. Enter the total number of new coordinator disks.
10. From the list of available disks that the installer presents, select two disks which you want to configure as coordinator disks.

    For example:

    List of available disks:
       1) emc_clariion0_61
       2) emc_clariion0_65
       3) emc_clariion0_66
       b) Back to previous menu
    Select 2 disk(s) as coordination points. Enter the disk options
    separated by spaces: [1-3,b,q]2 3

11. Verify and confirm the coordination points information for the fencing reconfiguration.
12. To migrate to disk-based fencing, select the I/O fencing mode as SCSI3.

    Select the vxfen mode: [1-2,b,q,?] (1) 1

    The installer initializes the coordinator disks and the coordinator disk group, and deports the disk group. Press Enter to continue.

13. Review the output as the installer prepares the vxfenmode.test file on all nodes and runs the vxfenswap script.

    Note the location of the vxfenswap.log file which you can access in the event of any problem with the configuration process.

    The installer cleans up the application cluster information from the CP servers.

14. If you want to send this installation information to Symantec, answer y at the prompt.

    Would you like to send the information about this installation
    to Symantec to help improve installation in the future? [y,n,q,?] (y) y

15. After the migration is complete, verify the change in the fencing mode.

    # vxfenadm -d

    For example, after the migration from server-based fencing to disk-based fencing in the VCS cluster:

    I/O Fencing Cluster Information:
    ================================
    Fencing Protocol Version: 201
    Fencing Mode: SCSI3
    Fencing SCSI3 Disk Policy: dmp
    Cluster Members:
    		* 0 (galaxy)
    		1 (nebula)
    RFSM State Information:
    		node 0 in state 8 (running)
    		node 1 in state 8 (running)

16. Verify the current coordination points that the vxfen driver uses.

    # vxfenconfig -l

To manually migrate from server-based fencing to disk-based fencing

1. Make sure system-to-system communication is functioning properly.
2. Make sure that the VCS cluster is online and uses server-based fencing.

   # vxfenadm -d

   For example, if VCS cluster uses server-based fencing:

   I/O Fencing Cluster Information:
   ================================
   Fencing Protocol Version: 201
   Fencing Mode: Customized
   Fencing Mechanism: cps
   Cluster Members:
   		* 0 (galaxy)
   		1 (nebula)
   RFSM State Information:
   		node 0 in state 8 (running)
   		node 1 in state 8 (running)

3. Make sure that you performed the following preparatory tasks to configure disk-based fencing:

   • Identifying disks to use as coordinator disks

   • Setting up coordinator disk group

   • Creating I/O configuration files

   See the Veritas Cluster Server Installation Guide for the procedures.
4. Create a new /etc/vxfenmode.test file with the fencing configuration changes such as the scsi3 disk policy information.

   Refer to the sample vxfenmode files in the /etc/vxfen.d folder.

5. From any node in the VCS cluster, start the vxfenswap utility:

   # vxfenswap -g diskgroup [-n]

6. Review the message that the utility displays and confirm whether you want to commit the change.

   • If you do not want to commit the new fencing configuration changes, press Enter or answer n at the prompt.

     Do you wish to commit this change? [y/n] (default: n) n

     The vxfenswap utility rolls back the migration operation.

   • If you want to commit the new fencing configuration changes, answer y at the prompt.

     Do you wish to commit this change? [y/n] (default: n) y

     If the utility successfully commits, the utility moves the /etc/vxfenmode.test file to the /etc/vxfenmode file.

7. After the migration is complete, verify the change in the fencing mode.

   # vxfenadm -d

   For example, after the migration from server-based fencing to disk-based fencing in the VCS cluster:

   I/O Fencing Cluster Information:
   ================================
   Fencing Protocol Version: 201
   Fencing Mode: SCSI3
   Fencing SCSI3 Disk Policy: dmp
   Cluster Members:
   		* 0 (galaxy)
   		1 (nebula)
   RFSM State Information:
   		node 0 in state 8 (running)
   		node 1 in state 8 (running)

8. Verify the current coordination points that the vxfen driver uses.

   # vxfenconfig -l