Nov 13 13:40:18 EVENT COMPLETED: rg_move clnode_2 1 RELEASE 0 Nov 13 13:40:18 EVENT COMPLETED: rg_move_release clnode_2 1 0 Nov 13 13:40:18 EVENT START: rg_move_fence clnode_2 1 Nov 13 13:40:19 EVENT COMPLETED: rg_move_fence clnode_2 1 0 Nov 13 13:40:21 EVENT START: node_down_complete clnode_1 Nov 13 13:40:21 EVENT COMPLETED: node_down_complete clnode_1 0 Nov 13 13:40:03 clnode_2 [...] EVENT START: split_merge_prompt split  Nov 13 13:40:03 clnode_2 [...] CONFIGRM_SITE_SPLIT_ST ConfigRM received Site Split event  notification Nov 13 13:40:03 clnode_2 [...] EVENT COMPLETED: split_merge_prompt split 0  Nov 13 13:40:09 clnode_2 [...] CONFIGRM_PENDINGQUORUM_ER The operational quorum state of  the active peer domain has changed to PENDING_QUORUM. This state usually indicates that  exactly half of the nodes that are defined in the peer domain are online. In this state  cluster resources cannot be recovered although none will be stopped explicitly. Nov 13 13:40:12 clnode_2 [...] EVENT START: site_down site1  Nov 13 13:40:13 clnode_2 [...] EVENT START: site_down_remote site1  Nov 13 13:40:13 clnode_2 [...] EVENT COMPLETED: site_down_remote site1 0  Nov 13 13:40:13 clnode_2 [...] EVENT COMPLETED: site_down site1 0  Nov 13 13:40:13 clnode_2 [...] EVENT START: node_down clnode_1  Nov 13 13:40:13 clnode_2 [...] EVENT COMPLETED: node_down clnode_1 0  Nov 13 13:40:15 clnode_2 [...] EVENT START: network_down clnode_2 net_ether_01  Nov 13 13:40:15 clnode_2 [...] EVENT COMPLETED: network_down clnode_2 net_ether_01 0  Nov 13 13:40:15 clnode_2 [...] EVENT START: network_down_complete clnode_2 net_ether_01  Nov 13 13:40:16 clnode_2 [...] EVENT COMPLETED: network_down_complete clnode_2 net_ether_01  0  Nov 13 13:40:18 clnode_2 [...] EVENT START: rg_move_release clnode_2 1  Nov 13 13:40:18 clnode_2 [...] EVENT START: rg_move clnode_2 1 RELEASE  Nov 13 13:40:18 clnode_2 [...] EVENT COMPLETED: rg_move clnode_2 1 RELEASE 0  Nov 13 13:40:18 clnode_2 [...] EVENT COMPLETED: rg_move_release clnode_2 1 0  Nov 13 13:40:18 clnode_2 [...] EVENT START: rg_move_fence clnode_2 1  Nov 13 13:40:19 clnode_2 [...] EVENT COMPLETED: rg_move_fence clnode_2 1 0  Nov 13 13:40:21 clnode_2 [...] EVENT START: node_down_complete clnode_1  Nov 13 13:40:21 clnode_2 [...] EVENT COMPLETED: node_down_complete clnode_1 0  Nov 13 13:40:29 clnode_2 [...] CONFIGRM_NOQUORUM_ER The operational quorum state of the  active peer domain has changed to NO_QUORUM. This indicates that recovery of cluster  resources can no longer occur and that the node may be rebooted or halted in order to  ensure that critical resources are released so that they can be recovered by another  subdomain that may have operational quorum. Nov 13 13:40:29 clnode_2 [...] CONFIGRM_REBOOTOS_ER The operating system is being rebooted  to ensure that critical resources are stopped so that another subdomain that has  operational quorum may recover these resources without causing corruption or conflict. [...] Nov 13 13:41:32 clnode_2 [...] RMCD_INFO_0_ST The daemon is started. Nov 13 13:41:33 clnode_2 [...] CONFIGRM_STARTED_ST IBM.ConfigRM daemon has started.  Nov 13 13:42:03 clnode_2 [...] GS_START_ST Group Services daemon started DIAGNOSTIC  EXPLANATION HAGS daemon started by SRC. Log file is  /var/ct/1Z4w8kYNeHvP2dxgyEaCe2/log/cthags/trace. This log also includes the information about the  network_down  event. The  cluster.log  file includes much of the information in the  cluster.mmddyyy  log file. The  notable exception is that this one  cluster.log  also included information about the quorum  status losing and regaining quorum. For the disconnected or restarted node only, the  cluster.log  file has information about the restart event, as shown in Example 3-40. Example 3-40 The cluster.log entries on the restarted node The cluster.log file Chapter 3. Planning considerations  85