node_down_local_completeInstructs the Cluster Manager to exit when the local node has left the cluster. This event occurs only after a node_down_local event has successfully completed.
node_down_remote_completeStarts takeover application servers. This event runs only after a node_down_remote event has successfully completed.
start_server | Starts application servers. |
5.1.1.2 Network Events |
|
network_down | This event occurs when the Cluster Manager |
| determines a network has failed. A |
| network_down event can take one of two forms: |
| Local network_down, where only a particular |
| node has lost contact with a network. |
| Global network_down, where all of the nodes |
| connected to a network have lost contact with a |
| network. It is assumed in this case that a |
| |
| a |
| The network_down event mails a notification to |
| the system administrator, but takes no further |
| action since appropriate actions depend on the |
| local network configuration. |
network_down_complete This event occurs only after a network_down
| event has successfully completed. The default |
| network_down_complete event processing |
| takes no actions since appropriate actions |
| depend on the local network configuration. |
network_up | This event occurs when the Cluster Manager |
| determines a network has become available for |
| use. The default network_up event processing |
| takes no actions since appropriate actions |
| depend on the local network configuration. |
network_up_complete | This event occurs only after a network_up event |
| has successfully completed. The default |
| network_up_complete event processing takes |
