-
Notifications
You must be signed in to change notification settings - Fork 72
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
lag: Support back-2-back dual mlag use case with crossed links #1850
Open
jbemmel
wants to merge
21
commits into
ipspace:dev
Choose a base branch
from
jbemmel:mlag_cross
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+661
−238
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Considering you had to add extra code to support the default edge-to-core MLAG wiring in most L2only fabrics, it might be time I take a look at that code :( Not going to happen soon though. |
Refactored lag analysis code: """
create_lag_interfaces -- create interfaces of type "lag" for each link marked as _virtual_lag
"""
def create_lag_interfaces(link: Box, mlag_pairs: dict, topology: Box) -> None:
members = link.pop('lag.members',[]) # Remove lag.members, normalized in phase I
A: typing.Set[str] = set( [members[0].interfaces[0].node] ) # Split nodes into 'A' and 'B' groups
B: typing.Set[str] = set( [members[0].interfaces[1].node] )
for m in members[1:]:
a = m.interfaces[0].node
b = m.interfaces[1].node
a_peer = mlag_pairs[a] if a in mlag_pairs else None
b_peer = mlag_pairs[b] if b in mlag_pairs else None
if a in A or a_peer in A or b in B or b_peer in B:
A.add(a)
B.add(b)
elif a in B or a_peer in B or b in A or b_peer in A:
A.add(b)
B.add(a)
else:
log.error(f'Unsupported configuration of members on LAG link {link._linkname}, must consist of ' +
'either 2, 3 or 4 different nodes connected as 1:1, 1:2 or 2:2',
category=log.IncorrectValue,
module='lag')
return |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To date, a topology with 4 nodes implicitly assumes 2 single links between them, i.e.
This PR adds support for crossed dual-mlag, i.e.