Moving BRCM SAI 4.2.1.3 to 4.2.1.3-1 to pick up fix for CS00011396506… #5878
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 fix CRM nexthop resource in-use leak
- Why I did it
SAI 4.2.1.3 has a CRM resource leak issue with nexthop resource for both IPV4 and IPV6. A patch to address this issue was provided by BRCM and validated with a private build. merging this fix to master branch.
- How to verify it
For details about CRM issue please refer to (#5583).
Repeated the test procedure and validated that the leak is no longer observed with SAI 4.2.1.3-1
- Which release branch to backport (provide reason below if selected)
Only if 202006 is also SAI4.2.1 based.
- Description for the changelog
Moving BRCM SAI 4.2.1.3 to 4.2.1.3-1 to pick up fix for CS00011396506 to fix CRM nexthop (IPV4/IPV6) resource in-use leak
Fixes #5583