Veritas Storage Foundation and High Availability Solutions Release Notes

About Veritas Storage Foundation and High Availability SolutionsSoftware limitations139See the Veritas Cluster Server Installation Guide for instructions on upgradingCluster Manager.Cluster Manager does not work if the hosts file contains IPv6 entriesVCS Cluster Manager fails to connect to the VCS engine if the /etc/hosts filecontains IPv6 entries.Workaround: Remove IPv6 entries from the /etc/hosts file.VCS Simulator does not support I/O fencingWhen running the Simulator, be sure the UseFence attribute is set to the default,“None”.Limited support from Cluster Manager (Java console)Features introduced in VCS 6.0 may not work as expected with Java console.However, CLI option of the simulator supports all the VCS 6.0 features. You arerecommended to use Veritas Operations Manager (VOM) since all new featuresare already supported in VOM. However, Java console may continue to work asexpected with features of releases prior to VCS 6.0.Port change required to connect to secure cluster [2615068]In order to connect to secure cluster, the default port must be changed from 2821to 14149. You must choose Advancedsettings in the Login dialog box and changeIP: 2821 to IP: 14149 for secure cluster login.Limitations related to I/O fencingThis section covers I/O fencing-related software limitations.Preferred fencing limitation when VxFEN activates RACER node re-electionThe preferred fencing feature gives preference to more weighted or largersubclusters by delaying the smaller subcluster. This smaller subcluster delay iseffective only if the initial RACER node in the larger subcluster is able to completethe race. If due to some reason the initial RACER node is not able to complete therace and the VxFEN driver activates the racer re-election algorithm, then thesmaller subcluster delay is offset by the time taken for the racer re-election andthe less weighted or smaller subcluster could win the race. This limitation thoughnot desirable can be tolerated.