Configuring server-based fencing on the VCS cluster manually

Last published : Sep 11, 2026
The configuration process for the client or VCS cluster to use CP server as a coordination point requires editing the /etc/vxfenmode file.
You need to edit this file to specify the following information for your configuration:
  • Fencing mode
  • Fencing mechanism
  • Fencing disk policy (if applicable to your I/O fencing configuration)
  • CP server or CP servers
  • Coordinator disk group (if applicable to your I/O fencing configuration)
  • Set the order of coordination points
    Note: Whenever coordinator disks are used as coordination points in your I/O fencing configuration, you must create a disk group (vxfencoorddg). You must specify this disk group in the/etc/vxfenmodefile. SeeSetting up coordinator disk groups.
The customized fencing framework also generates the /etc/vxfentab file which has coordination points (all the CP servers and disks from disk group specified in /etc/vxfenmode file).
To configure server-based fencing on the VCS cluster manually
  1. Use a text editor to edit the following file on each node in the cluster:
/etc/default/vxfen
You must change the values of the VXFEN_START and the VXFEN_STOP environment variables to 1.
  1. Use a text editor to edit the /etc/vxfenmode file values to meet your configuration specifications.
    • If your server-based fencing configuration uses a single highly available CP server as its only coordination point, make sure to add the single_cp=1 entry in the /etc/vxfenmode file.
    • If you want the vxfen module to use a specific order of coordination points during a network partition scenario, set the vxfen_honor_cp_order value to be 1. By default, the parameter is disabled.
The following sample file output displays what the /etc/vxfenmode file contains:
See Sample vxfenmode file output for server-based fencing.
  1. After editing the /etc/vxfenmode file, run the vxfen init script to start fencing.
For example:
\# /etc/init.d/vxfen.rc start