From: Jarod Wilson
Date: Fri, 24 May 2019 09:49:28 -0400
> Once in a while, with just the right timing, 802.3ad slaves will fail to
> properly initialize, winding up in a weird state, with a partner system
> mac address of 00:00:00:00:00:00. This started happening after a fix to
> properly track
On 5/24/19 6:38 PM, Mahesh Bandewar (महेश बंडेवार) wrote:
On Fri, May 24, 2019 at 2:17 PM Jay Vosburgh wrote:
Jarod Wilson wrote:
Once in a while, with just the right timing, 802.3ad slaves will fail to
properly initialize, winding up in a weird state, with a partner system
mac address of 0
On 5/24/19 5:16 PM, Jay Vosburgh wrote:
Jarod Wilson wrote:
Once in a while, with just the right timing, 802.3ad slaves will fail to
properly initialize, winding up in a weird state, with a partner system
mac address of 00:00:00:00:00:00. This started happening after a fix to
properly track li
On Fri, May 24, 2019 at 2:17 PM Jay Vosburgh wrote:
>
> Jarod Wilson wrote:
>
> >Once in a while, with just the right timing, 802.3ad slaves will fail to
> >properly initialize, winding up in a weird state, with a partner system
> >mac address of 00:00:00:00:00:00. This started happening after a
Jarod Wilson wrote:
>Once in a while, with just the right timing, 802.3ad slaves will fail to
>properly initialize, winding up in a weird state, with a partner system
>mac address of 00:00:00:00:00:00. This started happening after a fix to
>properly track link_failure_count tracking, where an 802
Once in a while, with just the right timing, 802.3ad slaves will fail to
properly initialize, winding up in a weird state, with a partner system
mac address of 00:00:00:00:00:00. This started happening after a fix to
properly track link_failure_count tracking, where an 802.3ad slave that
reported i
6 matches
Mail list logo
