Veritas Storage Foundation 5.1 SP1 Cluster File System Release Notes (5900-1509, April 2011)

Reconfiguring Storage Foundation Cluster File System HA with

I/O fencing fails if you use the same CP servers

When you reconfigure an application cluster that uses server-based I/O fencing

(customized fencing mode), the installer does not remove the application cluster

information from the CP servers before the reconfiguration. As a result, if you

reconfigure the application cluster and choose to configure I/O fencing in

customized mode using the same CP servers, then reconfiguration of server-based

fencing for the application cluster fails. [2076240]

Workaround: Manually remove the application cluster information from the CP

servers after you reconfigure Storage Foundation Cluster File System HA but

before you reconfigure server-based I/O fencing for the application cluster.

See the Veritas Cluster Server Administrator's Guide for instructions to remove

the application cluster information from the CP servers.

CP server cannot bind to multiple IPs (2085941)

Coordination point server (CP server) binds only to a single virtual IP and listens

on the same. Application clusters cannot access the CP server if it fails to establish

connection to this virtual IP. Therefore, if the connection fails because of the

subnet in which the virtual IP of the CP server exists, you cannot access the CP

server even if there is another subnet through which the client can connect to the

CP server over a different IP.

Resolution: No known resolution for this issue.

Installer is unable to split a cluster that is registered with one

or more CP servers

Splitting a cluster that uses server-based fencing is currently not supported.

[2110148]

You can split a cluster into two and reconfigure Storage Foundation Cluster File

System HA on the two clusters using the installer. For example, you can split a

cluster clus1 into clus1A and clus1B.

However, if you use the installer to reconfigure the Storage Foundation Cluster

File System HA, the installer retains the same cluster UUID of clus1 in both clus1A

and clus1B. If both clus1A and clus1B use the same CP servers for I/O fencing,

then the CP server allows registration only from the cluster that attempts to

the installer reports failure during the reconfiguration of the cluster that uses

server-based fencing.

Workaround: None.

Storage Foundation Cluster File System Release Notes

Known issues