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

Table 1-2
I/O fencing scenarios (continued)
Operator actionNode B: What
happens?
Node A: What
happens?
Event
Power on the failed
disk array so that
subsequent network
partition does not
cause cluster
shutdown, or replace
coordinator disks.
See “Replacing I/O
fencing coordinator
disks when the
cluster is online”
on page 123.
Node B has left the
cluster.
Node A continues to
operate in the
cluster.
The disk array
containing two of the
three coordinator
disks is powered off.
Node B gracefully
leaves the cluster and
the disk array is still
powered off. Graceful
leave implies a clean
shutdown so that
vxfen is properly
unconfigured.
Power on the failed
disk array and restart
I/O fencing driver to
enable Node A to
register with all
coordinator disks, or
replace coordinator
disks.
See “Replacing
defective disks when
the cluster is offline”
on page 206.
Node B has left
cluster due to crash
or network partition.
Node A races for a
majority of
coordinator disks.
Node A fails because
only one of the three
coordinator disks is
available. Node A
panics and removes
itself from the
cluster.
The disk array
containing two of the
three coordinator
disks is powered off.
Node B abruptly
crashes or a network
partition occurs
between node A and
node B, and the disk
array is still powered
off.
About CP server
This section discusses the CP server features.
The following CP server features are described:
■ SF Oracle RAC cluster configurations with server-based I/O fencing
■ I/O fencing enhancements provided by the CP server
■ About making CP server highly available
■ Recommended CP server configurations
■ About secure communication between the SF Oracle RAC cluster and CP server
53Overview of Veritas Storage Foundation for Oracle RAC
About preventing data corruption with I/O fencing