Pools Rebooted Automatically

[Super6VCA]

Not sure what happened but it appeared that a few of my pools just rebooted for no reason.  Everyone connected got kicked out and it took an extremely long time for each VM to get back online in view manager.  Some VM's as long as 10 minutes.  I can't find anything in the logs that says that the VM's rebooted or that anything happened.  However when I did look at the view manager.  It showed most of the VM's in each of those pools as AGENT Unreachable the status.  Anyone ever seen this occur or know what logs will can show me what happened?  Any help or suggestions are welcome. 

Found this in the Connection server log...  

<DesktopControlSessions> [Audit] OFFLINE:Server:cn=3927fef1-3f07-4b70-a6e4-83ab4827ac4e,ou=servers,dc=vdi,dc=vmware,dc=int;Pool:null;DNS:ipHostNumber=mwndoc-10.neuro.com, ipHostNumberOverride not set;

2014-08-01T13:10:10.049-05:00 INFO  (0D48-0540) <DesktopControlSessions> [Audit] OFFLINE:Server:cn=89c54bd4-3f9d-45d0-abb4-37ac90e2a374,ou=servers,dc=vdi,dc=vmware,dc=int;Pool:null;DNS:ipHostNumber=mwndoc-4.neuro.com, ipHostNumberOverride not set;

2014-08-01T13:10:50.060-05:00 INFO  (0D48-0540) <DesktopControlSessions> [Audit] OFFLINE:Server:cn=dafc2f20-7f6e-4bfb-8930-1589e5d50e07,ou=servers,dc=vdi,dc=vmware,dc=int;Pool:null;DNS:ipHostNumber=mwndoc-7.neuro.com, ipHostNumberOverride not set;

2014-08-01T13:10:50.062-05:00 INFO  (0D48-0540) <DesktopControlSessions> [Audit] OFFLINE:Server:cn=733188e8-12f3-469d-ba61-589affe22602,ou=servers,dc=vdi,dc=vmware,dc=int;Pool:null;DNS:ipHostNumber=mshroam-8.msh.mwsurgical.com, ipHostNumberOverride not set;

2014-08-01T13:10:50.063-05:00 INFO  (0D48-0540) <DesktopControlSessions> [Audit] OFFLINE:Server:cn=eb69b6c5-c440-40c6-958a-68ba169d5983,ou=servers,dc=vdi,dc=vmware,dc=int;Pool:null;DNS:ipHostNumber=mwndoc-6.neuro.com, ipHostNumberOverride not set;

2014-08-01T13:10:50.065-05:00 INFO  (0D48-0540) <DesktopControlSessions> [Audit] OFFLINE:Server:cn=39149799-6b98-4eb2-b796-8a21c5e41b21,ou=servers,dc=vdi,dc=vmware,dc=int;Pool:null;DNS:ipHostNumber=mshroam-6.msh.mwsurgical.com, ipHostNumberOverride not set;

2014-08-01T13:10:50.067-05:00 INFO  (0D48-0540) <DesktopControlSessions> [Audit] OFFLINE:Server:cn=d3c287b5-e4e4-443a-ad47-728a2246c576,ou=servers,dc=vdi,dc=vmware,dc=int;Pool:null;DNS:ipHostNumber=mshtrans-1.msh.mwsurgical.com, ipHostNumberOverride not set;

2014-08-01T13:10:50.068-05:00 INFO  (0D48-0540) <DesktopControlSessions> [Audit] OFFLINE:Server:cn=348ea6ce-eb95-4573-b53b-5f3aea0ef144,ou=servers,dc=vdi,dc=vmware,dc=int;Pool:null;DNS:ipHostNumber=mwndoc-1.neuro.com, ipHostNumberOverride not set;

2014-08-01T13:10:50.070-05:00 INFO  (0D48-0540) <DesktopControlSessions> [Audit] OFFLINE:Server:cn=bf64ffb5-6b8c-4fd4-9d92-fc529f4ec77f,ou=servers,dc=vdi,dc=vmware,dc=int;Pool:null;DNS:ipHostNumber=mshroam-3.msh.mwsurgical.com, ipHostNumberOverride not set;

[lanalyzer]

I guess the first to look at would be if the Virtual Machines were actually restarted or not from the vSphere side of things.

Also looking into HA events in vCenter as well as vmware.log file on the virtual machine directories as well.

ESXi host becoming unresponsive to HA heartbeats?

Windows logs inside the VMs?

I hope this gives some guidance.

JM

[chulerico]

definitely check from vCenter side, this option for example is killer, if set to restart instead of whats shown - leave powered on,

example a maintenance was done on the network/congestion made the host lose network connectivity, all machines on hosts affected will restart hitting hard CPU, memory, and storage.