</vmStatList> </needsAtt> </Response></VIO> Tue Aug 27 22:09:56 CUT 2019 <VIO><Response> <needsAtt> <vmStatList> <vmList machine_type="8408" model="E8E" serial="21282FW"> </vmList> </vmStatList> </needsAtt> <needsAtt> <vmStatList> <vmList machine_type="8408" model="E8E" serial="212424W"> <vmStat uuid="61be20f0-09a8-4753-b5e5-564f8a545ed5"><VM state="STARTED" missedHb='43' > </VM> </vmStat> </vmList> </vmStatList> </needsAtt> </Response></VIO> ... 

We observe that a new vmStat  element shows up inside the vmList  for our VM only when both the first and second HM update their missed heartbeat time stamps in the HSDB. Example 2-221 on page 245 shows that at 22:09:55, shortly after the missed heartbeat, a time stamp update was performed by the second HM at 22:09:54.303 ( vioHmClientMissed return). Inside the new vmStat  element, a VM  subelement is now present with the state  and missedHb  attributes having values set as retrieved  from the HSDB. The update of the VM state to the STARTED  state is described in “HM-VMM communication establishment” on page 215. The VM state is now retrieved from the HSDB as it was set then. 

We also observe that the missedHb  attribute value looks like an elapsed time in seconds value rather than an integer counter of missed heartbeats value. At 22:09:55, the value is 42 , 1 second later is 43 , and so on. The /usr/lib/vioHADR2.00.xsd  VIOS reference file documents this attribute as missedHB: integer regarding number of Heartbeats missed by the VM . We check the health library and HSDB logs around 22:09:55 to get more insight into how the value of this missedHb  attribute is computed. 

Example 2-222 shows the entries that are logged in vioshs.log  by the NA request that is issued at 22:09:55, the first one that returns a missedHb  value, and the final entries that are logged by the prior NA request issued a second earlier. 

# alog -f /home/ios/logs/health/viohs.log -o > viohs.log.NeedsAttn.missedHb # more viohs.log.NeedsAttn.missedHb [START 19333444 71762285 08/27/19-22:09:54.695 ha_util.c 1.43 230] ... [3 19333444 71762285 08/27/19-22:09:54.770 hs_atten.c hsGetHighest 1.108 429] ====>> 61be20f0-09a8-4753-b5e5-564f8a545ed5: count1:40 count2=0 [3 19333444 71762285 08/27/19-22:09:54.770 hs_atten.c hsGetHighest 1.108 514] ====>> 61be20f0-09a8-4753-b5e5-564f8a545ed5: highCnt:40 whichVios=1 [3 19333444 71762285 08/27/19-22:09:54.770 hs_atten.c hs_check_and_segregate_vms 1.108 3727] >>Missing HB from VIOS:1 cnt=40 noEntry=0 

