This parameter is used when the local OpenSwitch is experiencing a network outage and cannot communicate with the Adaptive Servers or companion OpenSwitch hosts. However, the specified action is invoked only when each ping has repeatedly failed more than the number of PING_RETRIES, while waiting for a response for longer than the amount of time of PING_WAIT.
Use:
DEFAULT – to clean up and exit, so that existing clients disconnect. When existing clients reconnect, they fail over to the active OpenSwitch companion.
CUSTOM, MANUAL, or CUSTOM_MANUAL – OpenSwitch is suspended and the specified custom or manual script is executed with the reason code 1005. OpenSwitch is suspended and waits indefinitely until the system administrator executes rp_go.
If NET_FAIL_ACTION is
set to CUSTOM or MANUAL, the respective script that is executed
must reside on a local file system. This is because the script executes
when the network is not responding and access to remote mounted
file systems may no longer exist.
See “User-specified actions” for additional details about these actions.
Valid exit codes are:
0 (zero) – the default exit
code. When the script exits with a zero (0), OpenSwitch performs
the default action (NET_FAIL_ACTION=DEFAULT).
1 – if you do not want the DEFAULT action performed, use an exit code of 1 for reason code 1005. For CUSTOM and MANUAL, when the script exits with 1, OpenSwitch remains up until it can reconnect to the network hosted Adaptive Server or companion OpenSwitch.
When you use CUSTOM_MANUAL, the manual script is executed only if the custom script exits with 1 (which indicates failure). When the manual script exits with 1, OpenSwitch remains up until it can reconnect to the network hosted Adaptive Server or companion OpenSwitch.
