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

4
Use a text editor to access /etc/vxfenmode and update the values to the new
CP server (coordination points).
The values of the /etc/vxfenmode file have to be updated on all the nodes in
the SFCFS cluster.
Review and if necessary, update the vxfenmode parameters for security, the
coordination points, and if applicable to your configuration, vxfendg.
Refer to the text information within the vxfenmode file for additional
information about these parameters and their new possible values.
5
Run the vxfenswap utility from one of the nodes of the cluster.
The vxfenswap utility requires secure ssh connection to all the cluster nodes.
Use -n to use rsh instead of default ssh.
# vxfenswap [-n]
If validation of coordination points from all the nodes fails, the vxfenswap
utility rollbacks the coordination point replacement operation. Proceed to
restore /etc/vxfenmode with the backed up file on all the VCS cluster nodes.
You are then prompted to commit the change. Enter y for yes.
Confirm the successful execution of the vxfenswap utility by checking the
coordination points currently used by the vxfen driver.
For example, run the following command:
# vxfenconfig -l
Refreshing registration keys on the coordination points for
server-based fencing
Replacing keys on a coordination point (CP server) when the SFCFS cluster is
online involves refreshing that coordination point's registrations. You can perform
a planned refresh of registrations on a CP server without incurring application
downtime on the SFCFS cluster. You must refresh registrations on a CP server if
the CP server agent issues an alert on the loss of such registrations on the CP
server database.
The following procedure describes how to refresh the coordination point
registrations.
103Administering Storage Foundation Cluster File System and its components
Administering I/O Fencing