Veritas Storage Foundation 5.1 SP1 Cluster File System Installation Guide (5900-1510, April 2011)

See “Troubleshooting issues related to the CP server service group” on page 455.
See “Checking the connectivity of CP server” on page 455.
See “Issues during fencing startup on SFCFS cluster nodes set up for server-based
fencing” on page 456.
See “Issues during online migration of coordination points” on page 458.
See “Troubleshooting server-based I/O fencing in mixed mode” on page 459.
See “Checking keys on coordination points when vxfen_mechanism value is set
to cps” on page 463.
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.
You must have set the environment variables CPS_USERNAME and
CPS_DOMAINTYPE to run the cpsadm command on the SFCFS 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.
455Troubleshooting cluster installation
Troubleshooting server-based I/O fencing