Re: [ovs-dev] [PATCH v2] lacp: Improve visibility with LACP

2023-08-16 Thread Mike Pattrick
On Fri, Aug 11, 2023 at 6:56 PM Ilya Maximets wrote: > > On 8/4/23 19:58, Mike Pattrick wrote: > > Diagnosing connectivity issues involving a bond can be complicated by a > > lack of logging in LACP. It is difficult to determine the health of > > sending and receving LACP packets. This is further

Re: [ovs-dev] [PATCH v2] lacp: Improve visibility with LACP

2023-08-11 Thread Ilya Maximets
On 8/4/23 19:58, Mike Pattrick wrote: > Diagnosing connectivity issues involving a bond can be complicated by a > lack of logging in LACP. It is difficult to determine the health of > sending and receving LACP packets. This is further complicated by the > tendency of some switches to toggle the car

Re: [ovs-dev] [PATCH v2] lacp: Improve visibility with LACP

2023-08-07 Thread Simon Horman
On Fri, Aug 04, 2023 at 01:58:49PM -0400, Mike Pattrick wrote: > Diagnosing connectivity issues involving a bond can be complicated by a > lack of logging in LACP. It is difficult to determine the health of > sending and receving LACP packets. This is further complicated by the > tendency of some s

[ovs-dev] [PATCH v2] lacp: Improve visibility with LACP

2023-08-04 Thread Mike Pattrick
Diagnosing connectivity issues involving a bond can be complicated by a lack of logging in LACP. It is difficult to determine the health of sending and receving LACP packets. This is further complicated by the tendency of some switches to toggle the carrier on interfaces that experience issues with