Veritas Cluster Server Release Notes

Veritas Cluster Server Release Notes
Known issues
46
Auto failover does not happen in case of two successive primary
and secondary cluster failures [2858187]
In case of three clusters (clus1, clus2, clus3) in a GCO with steward not configured,
if clus1 loses connection with clus2, it sends the inquiry to clus3 to check the state
of clus2 one of the following condition persists:
1. If it is able to confirm that clus2 is down, it will mark clus2 as FAULTED.
2. If it is not able to send the inquiry to clus3, it will assume that a network
disconnect might have happened and mark clus2 as UNKNOWN
In second case, automatic failover does not take place even if the
ClusterFailoverPolicy is set to Auto. You need to manually failover the global service
groups.
Workaround: Configure steward at a geographically distinct location from the clusters
to which the above stated condition is applicable.
GCO clusters remain in INIT state [2848006]
GCO clusters remain in INIT state after configuring GCO due to :
■
Trust between two clusters is not properly set if clusters are secure.
■ Firewall is not correctly configured to allow WAC port (14155).
Workaround: Make sure that above two conditions are rectified. Refer to Veritas
Cluster Server Administrator's Guide for information on setting up Trust relationships
between two clusters.
The ha commands may fail for non-root user if cluster is secure
[2847998]
The ha commands fail to work if you first use a non-root user without a home
directory and then create a home directory for the same user.
Workaround
1 Delete /var/VRTSat/profile/.
2 Delete /home/user_name/.VRTSat.
3 Delete /var/VRTSat_lhc/ file which same non-root user owns.
4 Run ha command with same non-root user (this will pass).