[DRBD-user] r0 ok, r1 PingAck did not arrive in time

Lars Ellenberg lars.ellenberg at linbit.com
Thu Jun 27 16:12:54 CEST 2013

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

On Thu, Jun 27, 2013 at 02:01:20PM +0000, Lukas Gradl wrote:
> Zitat von cesar <brain at click.com.py>:
> >Hi  Lukas Gradl-4
> >
> >I have PVE 2.3 with the same problem
> >
> >But my NICs are Realtek, and soon i will change of brand for Intel, and i
> >have connected in crossover-cable mode, because a "Switch" in the middle can
> >change the data of the packets.
> >
> >Please answer this questions:
> >
> >What are the model of your NICs for use with DRBD on each PVE Node?
> Intel 82574L on all NICs
> >
> >Do you have the link in crossover-cable mode (ie link NIC to NIC)?, if not,
> >just do it !!! (DRBD suggested highly do NIC to NIC)
> it is NIC to NIC
> >The latest "PVE 2.3" and "PVE 3.x" version have the kernel for support DRBD
> >8.3.13, update your PVE and your DRBD and after you must do test. After,
> >please  tell me about of this test.
> We run a kernel with 8.3.10. As this is a production system it's not
> that easy to update.

I don't remember the details from the top of my head,
8.3.10 was more than two years ago.

But from the changelog of 8.3.11:

 * Fixed wrong connection drops ("PingAck did not arrive in time") with
    asymmetrically congested networks

Just saying ...

: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
please don't Cc me, but send to list   --   I'm subscribed

More information about the drbd-user mailing list