The configuration process for the client or VCS cluster to use CP server as a coordination point requires editing the
You need to edit this file to specify the following information for your configuration:
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
To configure server-based fencing on the VCS cluster manually
You must change the values of the VXFEN_START and the VXFEN_STOP environment variables to 1.
/etc/vxfenmodefile 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
The following sample file output displays what the
/etc/vxfenmode file contains:
/etc/vxfenmodefile, run the vxfen init script to start fencing.
# /etc/init.d/vxfen.rc start
/etc/vxfenmodefile contains the value of security is set to 1.
Make sure that following command displays the certificate being used by cpsadm client,
EAT_DATA_DIR=/vat/VRTSvcs/vcsauth/data/CPSADM cpsat showcred