| no actions since appropriate actions depend on |
| the local network configuration. |
5.1.1.3 Network Adapter Events | |
swap_adapter | This event occurs when the service adapter on a |
| node fails. The swap_adapter event exchanges |
| or swaps the IP addresses of the service and a |
| standby adapter on the same HACMP network |
| and then reconstructs the routing table. |
swap_adapter_complete This event occurs only after a swap_adapter
| event has successfully completed. The |
| swap_adapter_complete event ensures that the |
| local ARP cache is updated by deleting entries |
| and pinging cluster IP addresses. |
fail_standby | This event occurs if a standby adapter fails or |
| becomes unavailable as the result of an IP |
| address takeover. The fail_standby event |
| displays a console message indicating that a |
| standby adapter has failed or is no longer |
| available. |
join_standby | This event occurs if a standby adapter becomes |
| available. The join_standby event displays a |
| console message indicating that a standby |
| adapter has become available. |
5.1.1.4 Cluster Status Events | |
config_too_long | This event occurs when a node has been in |
| reconfiguration for more than six minutes. The |
| event periodically displays a console |
| message. |
reconfig_topology_start | This event marks the beginning of a dynamic |
| reconfiguration of the cluster topology. |
reconfig_topology_completeThis event indicates that a cluster topology dynamic reconfiguration has completed.
reconfig_resource_acquire This event indicates that cluster resources that are affected by dynamic reconfiguration are being acquired by appropriate nodes.
reconfig_resource_release This event indicates that cluster resources affected by dynamic reconfiguration are being released by appropriate nodes.
Cluster Customization 121
