VCS behavior after a resource is declared faulted
Prev	Controlling VCS behavior	Next

---

VCS behavior after a resource is declared faulted

After a resource is declared faulted, VCS fires the resfault trigger and examines the value of the FaultPropagation attribute.

• If FaultPropagation is set to 0, VCS does not take other resources offline, and changes the group state to offline|faulted or partial|faulted. The service group does not fail over.

  If FaultPropagation is set to 1, VCS takes all resources in the dependent path of the faulted resource offline, up to the top of the tree.

• VCS then examines if any resource in the dependent path is critical. If no resources are critical, the service group is left in its offline|faulted or partial|faulted state. If a resource in the path is critical, VCS takes the all resources in the service group offline in preparation of a failover.
• If the AutoFailOver attribute is set to 0, the service group is not failed over; it remains in a faulted state. If AutoFailOver is set to 1, VCS examines if any systems in the service group's SystemList are possible candidates for failover. If no suitable systems exist, the group remains faulted and VCS calls the nofailover trigger. If eligible systems are available, VCS examines the FailOverPolicy to determine the most suitable system to which to fail over the service group.
• If FailOverPolicy is set to Load, a NoFailover situation may occur because of restrictions placed on service groups and systems by Service Group Workload Management.

Click the thumbnail above to view full-sized image.