@ANISH-GOTTAPU please break the PR if needed, but please note that we want following varieties:
Static LAG with raw traffic
Static LAG with BGP + traffic with auto mac learning
Dynamic LAG (LACP) with raw traffic
Dynamic LAG (LACP) with BGP + traffic with auto mac learning
Each LAG port should consist of 3 members (on both ends), min links should be 2 and we should validate the scenarios where traffic should flow correctly if one member goes down but does not flow correctly when two members go down.
There are other possible use cases, so let's review whatever LAG use cases we have as part of internal tests and log issues for them accordingly.
@ANISH-GOTTAPU please break the PR if needed, but please note that we want following varieties:
Each LAG port should consist of 3 members (on both ends), min links should be 2 and we should validate the scenarios where traffic should flow correctly if one member goes down but does not flow correctly when two members go down.
There are other possible use cases, so let's review whatever LAG use cases we have as part of internal tests and log issues for them accordingly.