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

If you encounter issues while administering CVM, refer to the troubleshooting
section for assistance.
See “Troubleshooting CVM” on page 220.
Establishing CVM cluster membership manually
In most cases you do not have to start CVM manually; it normally starts when
VCS is started.
Run the following command to start CVM manually:
# vxclustadm -m vcs -t gab startnode
vxclustadm: initialization completed
Note that vxclustadm reads main.cf for cluster configuration information and is
therefore not dependent upon VCS to be running. You do not need to run the
vxclustadm startnode command as normally the hastart (VCS start) command
starts CVM automatically.
To verify whether CVM is started properly:
# vxclustadm nidmap
Name CVM Nid CM Nid State
galaxy 0 0 Joined: Master
nebula 1 1 Joined: Slave
Changing the CVM master manually
You can change the CVM master manually from one node in the cluster to another
node, while the cluster is online. CVM migrates the master node, and reconfigures
the cluster.
Symantec recommends that you switch the master when the cluster is not handling
VxVM configuration changes or cluster reconfiguration operations. In most cases,
CVM aborts the operation to change the master, if CVM detects that any
configuration changes are occurring in the VxVM or the cluster. After the master
change operation starts reconfiguring the cluster, other commands that require
configuration changes will fail.
See “Errors during CVM master switching” on page 153.
To change the master online, the cluster must be cluster protocol version 100 or
greater.
151Administering SF Oracle RAC and its components
Administering CVM