acquire_service_addr | (If configured for IP address takeover.) |
| Configures boot addresses to the corresponding |
| service address, and starts TCP/IP servers and |
| network daemons by running the telinit |
| command. |
acquire_takeover_addr | The script checks to see if a configured standby |
| address exists, then swaps the standby address |
| with the takeover address. |
get_disk_vg_fs | Acquires disk, volume group, and file system |
| resources. |
node_up_remote | Causes the local node to release all resources |
| taken from the remote node and to place any |
| concurrent volume groups in concurrent mode. |
| Some of the scripts called by node_up_remote |
| include the following: |
release_takeover_addr | (If configured for IP address takeover.) Identifies |
| a takeover address to be released because a |
| standby adapter on the local node is |
| masquerading as the service address of the |
| remote node. Reconfigures the local standby |
| adapter to its original address (and hardware |
| address, if necessary). |
stop_server | Stops application servers belonging to the |
| reintegrating node. |
release_vg_fs | Releases volume groups and file systems |
| belonging to a resource group that the remote |
| node will be taking over. |
cl_deactivate_nfs | Unmounts NFS file systems. |
node_up_complete | This event occurs only after a node_up event |
| has successfully completed. Depending on |
| whether the node is local or remote, this event |
| initiates either a node_up_local_complete or |
| node_up_remote_complete event. |
node_up_local_complete Calls the start_server script to start application servers. This event occurs only after a node_up_local event has successfully completed.
node_up_remote_completeAllows the local node to do an NFS mount only after the remote node is completely up. This
