Veritas Storage Foundation 5.1 SP1 for Oracle RAC Administrator"s Guide (5900-1512, April 2011)

■ 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 SF Oracle RAC cluster (client cluster) node.
See “Troubleshooting issues related to the CP server service group” on page 211.
See “Checking the connectivity of CP server” on page 211.
See “Issues during fencing startup on SF Oracle RAC cluster nodes set up for
server-based fencing” on page 212.
See “Issues during online migration of coordination points” on page 214.
See “Troubleshooting server-based I/O fencing in mixed mode” on page 215.
See “Checking keys on coordination points when vxfen_mechanism value is set
to cps” on page 219.
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.
■ Check the VCS engine log (/var/VRTSvcs/log/engine_[ABC].log) to see if
any of the CPSSG service group resources are FAULTED.
■ Review the sample dependency graphs to make sure the required resources
are configured correctly.
Checking the connectivity of CP server
You can test the connectivity of CP server using the cpsadm command.
211Troubleshooting SF Oracle RAC
Troubleshooting I/O fencing