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

■ 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.
Troubleshooting server-based fencing on the SFCFS cluster nodes
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.
Issues during fencing startup on SFCFS cluster nodes set up
for server-based fencing
Table 7-1
Fencing startup issues on SFCFS cluster (client cluster) nodes
Description and resolutionIssue
If you receive a connection error message after issuing the cpsadm command on the SFCFS
cluster, perform the following actions:
■ Ensure that the CP server is reachable from all the SFCFS cluster nodes.
■ Check that the SFCFS cluster nodes use the correct CP server virtual IP or virtual
hostname and the correct port number.
Check the /etc/vxfenmode file.
■ Ensure that the running CP server is using the same virtual IP/virtual hostname and
port number.
cpsadm command on
the SFCFS cluster gives
connection error
Authorization failure occurs when the CP server's nodes or users are not added in the CP
server configuration. Therefore, fencing on the SFCFS cluster (client cluster) node is not
allowed to access the CP server and register itself on the CP server. Fencing fails to come
up if it fails to register with a majority of the coordination points.
To resolve this issue, add the CP server node and user in the CP server configuration and
restart fencing.
Authorization failure
Troubleshooting SFCFS
Troubleshooting I/O fencing
186