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

Chris Tothill Chris.Tothill at bristol.ac.uk
Thu Jun 27 12:42: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.


Are you using active/active channel bonding? If so I'd suggest trying
active/passive (or just a single direct connection with no bonding) and see
if that helps. If in doubt, simplify...

Incidentally, with gigE my experience is that you don't actually need a
'crossover' cable to do direct connection, a normal 'straight' cable works
just as well. I think this is because gigE uses all 4 pairs simultaneously
in both directions rather than one pair in each direction as 100M does.

Chris

---------------------------
Christopher Tothill
Zone D Senior IT Support Specialist (Chemistry Unix Support)
W227, School of Chemistry, University of Bristol
Tel: (+44 117 33) 17045
Chris.Tothill at bristol.ac.uk
---------------------------


On 27 June 2013 03:12, Gerald Brandt <gbr at majentis.com> wrote:

> Hi,
>
> I'm running Intel e1000 with crossover cable, and I just noticed in my log
> files I'm getting this:
>
> [3535162.766591] e1000e: eth1 NIC Link is Down
> [3535168.243278] e1000e: eth1 NIC Link is Up 10 Mbps Full Duplex, Flow
> Control: Rx/Tx
> [3535168.243282] e1000e 0000:02:00.0: eth1: 10/100 speed: disabling TSO
> [3535176.574432] e1000e: eth1 NIC Link is Down
> [3535178.495165] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow
> Control: Rx/Tx
> [3535214.602022] e1000e: eth1 NIC Link is Down
> [3535214.602465] e1000e 0000:02:00.0: eth1: Reset adapter
> [3535239.602540] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow
> Control: Rx/Tx
>
> Interesting.
>
> Gerald
>
>
> ----- Original Message -----
> > From: "cesar" <brain at click.com.py>
> > To: drbd-user at lists.linbit.com
> > Sent: Wednesday, June 26, 2013 5:56:17 PM
> > Subject: Re: [DRBD-user] r0 ok, r1 PingAck did not arrive in time
> >
> > 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?
> >
> > 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)
> >
> > 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.
> >
> > When i have my new NICs Intel, i will can tell you about of my
> > experiences
> >
> > Best regards
> > Cesar
> >
> >
> >
> > --
> > View this message in context:
> >
> http://drbd.10923.n7.nabble.com/r0-ok-r1-PingAck-did-not-arrive-in-time-tp17953p17960.html
> > Sent from the DRBD - User mailing list archive at Nabble.com.
> > _______________________________________________
> > drbd-user mailing list
> > drbd-user at lists.linbit.com
> > http://lists.linbit.com/mailman/listinfo/drbd-user
> >
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20130627/b1472478/attachment.htm>


More information about the drbd-user mailing list