Hi Mark,<div><br></div><div>Please, tell me more about this.</div><div><br></div><div>I have been struggling with my e1000e NIC, and the cluster isn't synching at all. It goes until 2.8% (out of 16Tb) and the connection simply drops off. That is why I want to use another NIC, which use a chipset other that this e1000e.</div>
<div><br></div><div>I have already updated the driver to 1.9.5, and it's exactly what you said: "random nic resets". I thought it was (1) the cables, (2) the switch ports and finally (3) the switch itself. I have changed all these hardware, and still can't sync.</div>
<div><br></div><div>Tell more about this issue with the Intel e1000e, please!</div><div><br></div><div>Thanks,</div><div>Marcelo</div><div><br><div class="gmail_quote">On Mon, Mar 12, 2012 at 10:41 AM, Mark Deneen <span dir="ltr"><<a href="mailto:mdeneen@gmail.com">mdeneen@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Also, please check your e1000e driver version and update to the latest<br>
stable version (out of tree). With the in-tree revision, we suffered<br>
from random nic resets under certain conditions, which really gave<br>
DRBD headaches.<br>
<br>
-M<br>
<div><div class="h5"><br>
On Fri, Mar 9, 2012 at 11:37 AM, Marcelo Pereira <<a href="mailto:marcelops@gmail.com">marcelops@gmail.com</a>> wrote:<br>
> Hello guys,<br>
><br>
> I have been facing a problem with a server who can't sync at all due to<br>
> network issues. The NIC (two Intel e1000e) is showing several errors and is<br>
> being dropped off. Sometimes at the primary node, sometimes at the<br>
> secondary. It will not sync.<br>
><br>
> I have an unused NIC on both servers, and I would like to use them instead.<br>
> What should I do to move the configuration from one set of IP's to another??<br>
><br>
> So, that is my current /etc/drbd.conf:<br>
><br>
> global { usage-count no; }<br>
> resource pdc0 {<br>
> protocol C;<br>
> startup { wfc-timeout 0; degr-wfc-timeout 120; }<br>
> disk { on-io-error detach; } # ACK!<br>
> net { cram-hmac-alg "sha1"; shared-secret "xxxxxxx"; }<br>
> syncer { rate 10M; verify-alg sha1; }<br>
> on node0 {<br>
> device /dev/drbd0;<br>
> disk /dev/sdb;<br>
> address <a href="http://192.168.69.1:7788" target="_blank">192.168.69.1:7788</a>;<br>
> meta-disk internal;<br>
> }<br>
> on node1 {<br>
> device /dev/drbd0;<br>
> disk /dev/sdc;<br>
> address <a href="http://192.168.69.2:7788" target="_blank">192.168.69.2:7788</a>;<br>
> meta-disk internal;<br>
> }<br>
> }<br>
><br>
> And that is what it should be after:<br>
><br>
> global { usage-count no; }<br>
> resource pdc0 {<br>
> protocol C;<br>
> startup { wfc-timeout 0; degr-wfc-timeout 120; }<br>
> disk { on-io-error detach; } # ACK!<br>
> net { cram-hmac-alg "sha1"; shared-secret "xxxxxxx"; }<br>
> syncer { rate 10M; verify-alg sha1; }<br>
> on node0 {<br>
> device /dev/drbd0;<br>
> disk /dev/sdb;<br>
> address <a href="http://10.0.0.1:7788" target="_blank">10.0.0.1:7788</a>;<br>
> meta-disk internal;<br>
> }<br>
> on node1 {<br>
> device /dev/drbd0;<br>
> disk /dev/sdc;<br>
> address <a href="http://10.0.0.2:7788" target="_blank">10.0.0.2:7788</a>;<br>
> meta-disk internal;<br>
> }<br>
> }<br>
><br>
> Is it enough to just change the /etc/drbd.conf on both servers? What is the<br>
> exact procedure? I'm using DRBD v8.2.6.<br>
><br>
> Thanks,<br>
> Marcelo<br>
><br>
</div></div>> _______________________________________________<br>
> drbd-user mailing list<br>
> <a href="mailto:drbd-user@lists.linbit.com">drbd-user@lists.linbit.com</a><br>
> <a href="http://lists.linbit.com/mailman/listinfo/drbd-user" target="_blank">http://lists.linbit.com/mailman/listinfo/drbd-user</a><br>
><br>
</blockquote></div><br></div>