VCS Failover Policy does not take into consideration AutoFailover = 2 and SystemZones when the nodes within a SystemZone are brought down or rebooted.
Article ID: 100005535
Updated On:
Resolution
Veritas has fixed the code to ensure that if you set the AutoFailover
attribute to 2, then VCS fails over service groups to a node that is in the
same SystemZone. If VCS does not find an eligible target node in the same
SystemZone, VCS does not fail over the service group.
Please install Veritas Cluster Server 5.1 RP2 Hotfix 2 following the instructions in its README. You will need to upgrage VCS 5.1RP1 to VCS5.1RP2 prior to installing this hotfix. This refers to Veritas Incident number 2296171.
Issue/Introduction
VCS Failover Policy does not take into consideration AutoFailover = 2 and SystemZones when the nodes within a SystemZone are brought down or rebooted.
Even if you set the value of the AutoFailover attribute to 2, VCS may fail over
a service group from a FAULTED node to a node in another SystemZone.
Even if you set the value of the AutoFailover attribute to 2, VCS may fail over
a service group from a FAULTED node to a node in another SystemZone.
Was this article helpful?
Yes
No
Powered by
