# ksysmgr trace log=ksys > ksys.log.posthamonitorenable # ksysmgr trace log=fde > fde.log.posthamonitorenable # ksysmgr trace log=fdelong > fdelong.log.posthamonitorenable # ksysmgr trace log=user > user.log.posthamonitorenable # ls fde.log.posthamonitorenable krestlong.log.posthamonitorenable fdelong.log.posthamonitorenable ksys.log.posthamonitorenable krest.log.posthamonitorenable user.log.posthamonitorenable # Checking the entries in the  user  trace file that are logged after the discovery command start  moment,  Tue Apr 30 08:59:54 CUT 2019 , we see a first trace of the discovery flow in an  abridged form that is more detailed than the command output in Example 2-141 on page 178.  We divide this  user  trace file content, as shown in Example 2-177 and Example 2-178 on  page 206. In Example 2-177, we see that the host group discovery starts with a successful  verification block for the HMC, followed by a first CEC verification block, inside which VIOS  and trunk adapter verifications are passed successfully. # more user.log.posthamonitorenable [09] 04/30/19 T(203) _VMR 08:59:13.165979 [ INFO]: SCHEDULER initiated QUICK discoverVerify  Completed [09] 04/30/19 T(9113) _VMR 08:59:57.241032 DEBUG VMR_HG.C[4919]: ------------- HG Verification  process START for HG : rbHG ------------ [09] 04/30/19 T(9113) _VMR 08:59:57.324091 [ INFO,VMR_HMCRccp,] Starting verify_HMCRccp [09] 04/30/19 T(9113) _VMR 08:59:57.324110 [ INFO,VMR_HMCRcp,usaxhmc013ccpf1] Verify_HMCRcp  for HMC = usaxhmc013ccpf1, IP = 129.41.127.3 [09] 04/30/19 T(9113) _VMR 08:59:57.324116 [ INFO,VMR_HMCRcp,usaxhmc013ccpf1] Start  discover_HMC usaxhmc013ccpf1 [09] 04/30/19 T(9113) _VMR 08:59:57.636845 [ INFO,VMR_HMCRcp,usaxhmc013ccpf1] End  discover_HMC usaxhmc013ccpf1 [09] 04/30/19 T(9113) _VMR 08:59:57.636887 [ INFO,VMR_HMCRcp,usaxhmc013ccpf1] CEC List &  SessionID is same. So no update is required. [09] 04/30/19 T(9113) _VMR 08:59:57.636894 [ INFO,VMR_HMCRcp,usaxhmc013ccpf1] Verify_HMCRcp  for HMC = usaxhmc013ccpf1 completed [09] 04/30/19 T(9113) _VMR 08:59:57.636901 [ INFO,VMR_HMCRccp,] Completed verify_HMCRccp [09] 04/30/19 T(9113) _VMR 09:00:13.643946 [  INFO,VMR_CECRcp,3a53a6fc-8dcb-3671-a853-70526651f83d] verify_CECRcp  CEC:Server-8408-E8E-SN212424W(3a53a6fc-8dcb-3671-a853-70526651f83d), cluster_type:HA [09] 04/30/19 T(9113) _VMR 09:00:30.660046 [  INFO,VMR_VIOSRcp,5C3196A3-C41F-4B5C-9861-DEE6077081C6] Performing verify_VIOSRcp on VIOS  usaxvib063ccpx1 [09] 04/30/19 T(9113) _VMR 09:00:31.654865 DEBUG VMR_VIOS.C[5751]: verifyTrunkAdapter passed  on usaxvib063ccpx1 [09] 04/30/19 T(9113) _VMR 09:00:31.664472 [  INFO,VMR_VIOSRcp,5C3196A3-C41F-4B5C-9861-DEE6077081C6] verify_VIOSRcp done for VIOS  usaxvib063ccpx1 [09] 04/30/19 T(9113) _VMR 09:00:31.664495 [  INFO,VMR_VIOSRcp,0AB5001F-2C3E-4FBB-97EA-41D3F8C4F898] Performing verify_VIOSRcp on VIOS  usaxvia063ccpx1 [09] 04/30/19 T(9113) _VMR 09:00:33.430476 DEBUG VMR_VIOS.C[5751]: verifyTrunkAdapter passed  on usaxvia063ccpx1 Chapter 2. IBM VM Recovery Manager High Availability components  205 Example 2-177 The user trace file records for VM monitoring enable discovery