-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add information about LACP connection status for LAG ports #4964
Labels
Comments
pkazlenka
added a commit
that referenced
this issue
Jan 31, 2023
* Added support to traffgen to emit LACP packet
durgakako
pushed a commit
that referenced
this issue
Jan 31, 2023
pkazlenka
added a commit
that referenced
this issue
Feb 1, 2023
durgakako
pushed a commit
that referenced
this issue
Feb 1, 2023
pkazlenka
added a commit
that referenced
this issue
Feb 1, 2023
* Added new traffexam endpoint (/address/<idnr>/lacp)
pkazlenka
added a commit
that referenced
this issue
Feb 1, 2023
* Fixed wrong explanation in comment
pkazlenka
added a commit
that referenced
this issue
Feb 10, 2023
* Added new test for LACP connection * New class LAG representing LAG business entity * New experimental approach to switches picking * Implemented new methods for new traffgen feature
pkazlenka
added a commit
that referenced
this issue
Feb 10, 2023
* Added support to traffgen to emit LACP packet
pkazlenka
added a commit
that referenced
this issue
Feb 10, 2023
pkazlenka
added a commit
that referenced
this issue
Feb 10, 2023
* Added new traffexam endpoint (/address/<idnr>/lacp)
pkazlenka
added a commit
that referenced
this issue
Feb 10, 2023
* Fixed wrong explanation in comment
pkazlenka
added a commit
that referenced
this issue
Feb 10, 2023
* Added new test for LACP connection * New class LAG representing LAG business entity * New experimental approach to switches picking * Implemented new methods for new traffgen feature
pkazlenka
added a commit
that referenced
this issue
Feb 16, 2023
* Updated LACP emitting code to be closer to other methods approach
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
LAG ports has ability to reply on LACP packets
After LACP enabling kilda starts to receive LACP packets. (See LacpService in floodlight)
These packets contains information about state of LACP session.
Need to save this data in data base to have ability to see state of LACP session.
Example get LACP port output:
Good place for storing LACP info will be ConnectedDevices topology
The text was updated successfully, but these errors were encountered: