<div dir="ltr"><div><div><div><div><div><div><div>Johan,<br><br></div>It there is temporary networking issue and you still want engine not to fence the host you can<br></div>increase heartbeat interval in the engine configuration. It would tell engine to wait longer<br></div>before assuming that the host is not responding.<br><br></div>Please provide the logs so we can understand why there is communication issue in the first<br></div>place.<br><br></div>Thanks,<br></div>Piotr<br><div><div><div><div><div><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 17, 2016 at 12:52 PM, Nir Soffer <span dir="ltr"><<a href="mailto:nsoffer@redhat.com" target="_blank">nsoffer@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Mar 17, 2016 at 10:49 AM, Johan Kooijman <<a href="mailto:mail@johankooijman.com">mail@johankooijman.com</a>> wrote:<br>
> Hi all,<br>
><br>
> Since we upgraded to the latest ovirt node running 7.2, we're seeing that<br>
> nodes become unavailable after a while. It's running fine, with a couple of<br>
> VM's on it, untill it becomes non responsive. At that moment it doesn't even<br>
> respond to ICMP. It'll come back by itself after a while, but oVirt fences<br>
> the machine before that time and restarts VM's elsewhere.<br>
><br>
> Engine tells me this message:<br>
><br>
> VDSM host09 command failed: Message timeout which can be caused by<br>
> communication issues<br>
><br>
> Is anyone else experiencing these issues with ixgbe drivers? I'm running on<br>
> Intel X540-AT2 cards.<br>
<br>
We will need engine and vdsm logs to understand this issue.<br>
<br>
Can you file a bug and attach ful logs?<br>
<span class="HOEnZb"><font color="#888888"><br>
Nir<br>
</font></span></blockquote></div><br></div></div></div></div></div></div></div></div></div></div>