24:[06] 11/19/18 T(9192) _VMR 13:49:27.865442 DEBUG needAttn.C[167]: machine_type = 8286 25:[06] 11/19/18 T(9192) _VMR 13:49:27.865444 DEBUG needAttn.C[176]: model = 42A # 

Comparing the moment when the FDE thread entered its run (13:49:26.243690) with the moment the event thread Handler entered (13:49:26.242487 in Example 2-37 on page 74), we see that the FDE thread started 1.2 ms later. The FDE thread logs at its start details about the VIOS that it uses for polling and then initiates its first scan, which is a QuickQuery. The steps of the QuickQuery are as follows: 

1. This first FDE polling scan is started by starting a doQuickQuery  call, which is logged in the fde  trace file at 13:49:26.265471, and also logged as tried by the rthmc3 HMC at 13:49:26.265495. 

2. So, the FDE thread logs its first message in the ksys  trace file, which is the record about the empty HMC session found, at 13:49:26.265532 (Example 2-37 on page 74). 

3. After the new HMC session is opened at 13:49:26.265536 (Example 2-37 on page 74), the QuickQuery request is submitted to a VIOS at 13:49:26.517072 (Example 2-38 on page 76). 

4. The response is obtained by job polling, and a record about its completion is logged in the ksys  trace file at 13:49:27.865262. 

5. The first FDE doQuickQuery  call logs its return at 13:49:27.865296 1.6 seconds after its invocation. 

The whole sequence of HMC and VIOS low-level steps for this first QuickQuery request after the daemon restart as they are logged in the krest  and krestlog  trace files is described in “QuickQuery asynchronous job example” on page 1 05. Also, a complete analysis of a generic QuickQuery request flow, including the way its response payload content is parsed and further processed by the KSYS side, is available in “QuickQuery flow” on page 234. 

After the first QuickQuery occurrence at line 705 of our ksys  log file and the subsequent two lines that are shown in Example 2-37 on page 74 (706 - 707), we continue with the next section of 25 rows from the ksys  log, as shown in Example 2-39. All these lines are ksys records that are logged by the FDE thread about VIOS- and CEC-related initialization actions performed while parsing and processing this first QuickQuery response payload. 

# sed '708,$!d;=' post-restart_ksys.log|sed 'N;s/
/:/'|head -25 708:[15] 11/19/18 T(9192) _VMR 13:49:27.865476 DEBUG VMR_VIOS.C[4158]: 709: 710: CEC IS UP, READY FOR RELOCATION 711: 712: 713:[15] 11/19/18 T(9192) _VMR 13:49:27.866167 DEBUG VMR_VIOS.C[4172]: Adding cleanLpars task for the cec 4462c37c-65c6-3614-b02a-aa09d752c2ee 714:[15] 11/19/18 T(9192) _VMR 13:49:27.866172 DEBUG VMR_LPAR.C[11257]: adding task for clean_lpars 715:[15] 11/19/18 T(9192) _VMR 13:49:27.866180 DEBUG VMR_LPAR.C[11260]: Add task is done for CLEAN_LPARS 716:[15] 11/19/18 T(9192) _VMR 13:49:27.866198 DEBUG VMR_SITE.C[6261]: INFO: eventNotify entering. event:VIOS_CAA_STATE_UP_DETECTED, event type:3, comp:VIOS, notificationLevel:low, dupEventProcess:yes 717:[15] 11/19/18 T(9192) _VMR 13:49:27.866540 DEBUG VMR_SITE.C[7096]: ERROR: catopen Failed 

