Veritas Storage Foundation 5.1 SP1 Cluster File System Administrator"s Guide (5900-1738, April 2011)

Troubleshooting server-based I/O fencing
All CP server operations and messages are logged in the /var/VRTScps/log
directory in a detailed and easy to read format. The entries are sorted by date and
time. The logs can be used for troubleshooting purposes or to review for any
possible security issue on the system that hosts the CP server.
The following files contain logs and text files that may be useful in understanding
and troubleshooting a CP server:
/var/VRTScps/log/cpserver_[ABC].log
/var/VRTSat/vrtsat_broker.txt (Security related)
If the vxcpserv process fails on the CP server, then review the following
diagnostic files:
/var/VRTScps/diag/FFDC_CPS_pid_vxcpserv.log
/var/VRTScps/diag/stack_pid_vxcpserv.txt
Note: If the vxcpserv process fails on the CP server, these files are present in
addition to a core file. VCS restarts vxcpserv process automatically in such
situations.
The file /var/VRTSvcs/log/vxfen/vxfend_[ABC].log contains logs and text files
that may be useful in understanding and troubleshooting fencing-related issues
on a SFCFS cluster (client cluster) node.
See Troubleshooting issues related to the CP server service group on page 185.
See Checking the connectivity of CP server on page 188.
See Issues during fencing startup on SFCFS cluster nodes set up for server-based
fencing on page 186.
See Issues during online migration of coordination points on page 189.
See Troubleshooting server-based I/O fencing in mixed mode on page 190.
See Checking keys on coordination points when vxfen_mechanism value is set
to cps on page 193.
Troubleshooting issues related to the CP server service group
If you cannot bring up the CPSSG service group after the CP server configuration,
perform the following steps:
Verify that the CPSSG service group and its resources are valid and properly
configured in the VCS configuration.
185Troubleshooting SFCFS
Troubleshooting I/O fencing