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

You must have set the environment variables CPS_USERNAME and
CPS_DOMAINTYPE to run the cpsadm command on the SF Oracle RAC cluster
(client cluster) nodes.
To check the connectivity of CP server
◆
Run the following command to check whether a CP server is up and running
at a process level:
# cpsadm -s cp_server -a ping_cps
where cp_server is the virtual IP address or virtual hostname on which the
CP server is listening.
Troubleshooting server-based fencing on the SF Oracle RAC 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 SF Oracle RAC cluster (client cluster) node.
Issues during fencing startup on SF Oracle RAC cluster nodes
set up for server-based fencing
Table 3-20
Fencing startup issues on SF Oracle RAC cluster (client cluster)
nodes
Description and resolutionIssue
If you receive a connection error message after issuing the cpsadm command on the SF
Oracle RAC cluster, perform the following actions:
■ Ensure that the CP server is reachable from all the SF Oracle RAC cluster nodes.
■ Check that the SF Oracle RAC 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 SF Oracle RAC
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 SF Oracle RAC 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 SF Oracle RAC
Troubleshooting I/O fencing
212