Fallover and notify actions
In both process and custom monitoring methods, when the monitor detects a problem, PowerHA® SystemMirror® attempts to restart the application on the current node and continues the attempts until the specified restart count has been exhausted.
When an application cannot be restarted within the restart count, PowerHA SystemMirror takes one of two actions, which you specified when configuring the application monitor:
- Choosing fallover causes the resource group containing the application to fall over to the node with the next highest priority according to the nodelist. (See Application monitoring prerequisites and considerations for more information.)
- Choosing notify causes PowerHA SystemMirror to generate a server_down event, which informs the cluster of the failure.