[mirrororch] Fix a bug where ERSPAN used LAG as the destination port and linked down the first LAG member #2547
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.
[mirrororch] Fix a bug where ERSPAN used LAG as the destination port and linked down the first LAG member.
[portsorch] Add a function to return a linked-up member of an input LAG.
What I did
When a destination port belongs to a LAG in an ERSPAN session,
detect the LAG member that is linked down and switch the destination port to a LAG member that is linked up.
Why I did it
Current ERSPAN is unaware of the LAG member port linking up or down.
How to verify it
The community tests and manual tests pass.
Signed-off-by: sdn@inspur.com