Here LEGATO gives adjacent node listener receive timeouts too. I've just tried dnping under Linux (just because I remembered it existed) and found mean RTTs to MIM of min/avg/max = 93.6/95.0/96.1 ms and to LEGATO 256.0/487.5/981.9 ms. Perhaps this info is of help, Erik On Tue, May 27, 2014 at 05:11:23PM +0200, Johnny Billquist wrote: On 2014-05-27 17:06, Johnny Billquist wrote: On 2014-05-27 16:48, Paul_Koning at Dell.com wrote: On May 27, 2014, at 10:35 AM, Bob Armstrong <bob at jfcl.com> wrote: On 2014-05-27 07:07, Paul_Koning at Dell.com wrote: In other words, the listen timeout for Ethernet is 3 * hello time, for point to point it is 2 * hello time. But can you clarify who is dropping who (i.e. which end is timing out)? The message on LEGATO says "dropped by adjacent node" not "dropping adjacent node", which makes it sound as if MIM is timing out, not LEGATO (and then somehow telling LEGATO that, which is another mystery). Or is this just a poorly worded message? No, the message is very precise. If you see a message on LEGATO which reports adjacency MIM down for that reason, it means LEGATO received an Ethernet router hello message from MIM that no longer lists LEGATO as one of the routers that MIM can see. MIM will have a reason for not reporting LEGATO any longer. It should have logged a message stating that reason. Right. And MIM says "Adjacency listener receive timeout." So it would seem packets are lost from Bob/LEGATO... By the way. Note that it is only LEGATO that MIM had this problem with yesterday. All other nodes were stable. So it's not something local to the ethernet at update, neither to the bridge as such. It's either the network between Bob and Update, or the bridge on Bob's end, or something on the network at his end... Johnny