Veritas Storage Foundation 5.1 SP1 for Oracle RAC Administrator"s Guide (5900-1512, 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 SF Oracle RAC 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
Migrating from non-secure to secure setup for CP server and SF Oracle
RAC cluster communication
The following procedure describes how to migrate from a non-secure to secure
set up for the CP server and SF Oracle RAC cluster.
To migrate from non-secure to secure setup for CP server and SF Oracle RAC cluster
1
Stop fencing on all the SF Oracle RAC cluster nodes of all the clusters (which
are using the CP servers).
# /sbin/init.d/vxfen stop
2
Stop all the CP servers using the following command on each CP server:
# hagrp -offline CPSSG -any
Administering SF Oracle RAC and its components
Administering the CP server
146