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)
Appropriate value for the security configuration
CP server or CP servers
Coordinator disk group (if applicable to your I/O fencing configuration)
The customized fencing framework also generates the /etc/vxfentab
file which has security setting and the 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
/etc/rc.config.d/vxfenconf
You must change the values of the VXFEN_START and the VXFEN_STOP environment variables to 1.
/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.
The following sample file output displays what the /etc/vxfenmode
file contains:
/etc/vxfenmode
file, run the vxfen init script to start fencing.
For example:
# /sbin/init.d/vxfen start
/var/VRTSvcs/vcsauth/data/CPSADM
directory.