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

Note: The configuration file (/etc/vxfenmode) on each client node must not contain
a line specifying security=0. If there is no line specifying "security" parameter
or if there is a line specifying security=1, client node starts with security enabled
(which is the default).
Settings in non-secure mode
In non-secure mode, only authorization is provided on the CP server. Passwords
are not requested. Authentication and encryption are not provided. User
credentials of “cpsclient@hostname” of “vx” domaintype are used by the
customized fencing framework for communication between CP server or SF Oracle
RAC cluster node(s).
For each SF Oracle RAC cluster node, this user must be added on the CP server
database before fencing starts on the SF Oracle RAC cluster node(s). The user can
be verified by issuing the following command:
# cpsadm -s cpserver -a list_users
The following is an example of the command output:
Username/Domain Type Cluster Name / UUID Role
cpsclient@galaxy/vx cluster1 / {f0735332-e3709c1c73b9} Operator
Note: In non-secure mode, CP server configuration file (/etc/vxcps.conf) should
contain a line specifying security=0. Similarly, on each SF Oracle RAC cluster
node the configuration file (/etc/vxfenmode) should contain a line specifying
security=0.
Periodic health evaluation of the clusters
SF Oracle RAC provides a health check utility that evaluates the components and
configuration in an SF Oracle RAC cluster. The utility when invoked gathers
real-time operational information on cluster components and displays the report
on your system console. You must run the utility on each node in the cluster.
The utility evaluates the health of the following components:
■ Low Latency Transport (LLT)
■ LLT Multiplexer (LMX)
■ I/O fencing
■ Oracle Clusterware/Grid Infrastructure
■ PrivNIC
71Overview of Veritas Storage Foundation for Oracle RAC
Periodic health evaluation of the clusters