All  viosStat  element attributes are taken one by one and checked for relevant value changes.  The corresponding attributes of the VIOS resources on the KSYS side are updated with the  new values (Example 2-214). In our case,  HMrespSec  was changed to  1  in Example 2-213 on  page 238 by the  setHMrespSec  call. Example 2-214 VIOS health state attributes on the KSYS side # lsrsrc -s 'Name="rt13v2"' IBM.VMR_VIOS|egrep -i  "uuid|stat|hm|resp|data|reason|sync|msg" ViosUuid = "315CE56B-9BA0-46A1-B4BC-DA6108574E7E" CecUuid = "4462c37c-65c6-3614-b02a-aa09d752c2ee" State = "MANAGED" ActiveHM = 101 CAAstate = "UP" PoolState = "UP" HMrespSec = 1 HMresponsive = "Yes" WarnMsg = "" InfoMsg = "" HMVersions = {"2.00"} PartitionState = "" HMmode = "Active" CAAstateReason = "" CAAreposState = "UP" RMCState = "active" # ksysmgr -v q vios rt13v2|egrep -i "uuid|stat|hm|resp|data|reason|sync|msg" UUID: 315CE56B-9BA0-46A1-B4BC-DA6108574E7E RMC_state: active State: MANAGED HMstate: Yes HMmode: Active Last_response: 1 seconds CAA_state: UP Pool_state: UP HM_versions: 2.00 # Nothing abnormal is detected in this happy case example, so the flow finishes and the FDE  thread enters a new 20-second sleep period before starting a new QQ or NA check. This  happy case pattern repeats in a normal steady state operation. The same QQ flow pattern is followed when case events happen. An abnormal situation  exercise is simulated in “CAA event monitoring” on page 128, where we simulate a VIOS  failure by shutting down a VIOS node. Then, we restart the VIOS node. We describe the way  that generated CAA events are conveyed to the HSD, the FDE, and up the stack to other  KSYS components, such as the event notification subsystem. Fresh VIOS health state data that is obtained this way feeds continuously into the FDE  thread. The FDE thread decides on the next action, which is to do nothing if all is  OK  or to  notify the user and decide on host relocation if something abnormal is found, as described in  “Host relocation decision” on page 95. Chapter 2. IBM VM Recovery Manager High Availability components  239