BRCM SAI 4.2.1.5-7 fix WARM BOOT "Removing the ip2me trap entry returns error & crash Orchagent" #6244
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.
- Why I did it
In SAI 4.2.1.5 there is a Warm-reboot issue discovered by nightly test (#6069)
It appears that this issue was due to the new SAI added additional checking (FALSE Positive) that rejected the attempt to delete the hotif IP2ME trap. BRCM case was raised by DELL (CS00011466224) and a fix was provided by BRCM.
- How to verify it
With the new libsai debian with the patch fix warm-reboot no longer encounter this hostif IP2ME trap delete failure and warm-reboot completes successfully.
- Description for the changelog
Moving BRCM SAI 4.2.1.5-6 to 4.2.1.5-7 to pick up fix WARM BOOT "Removing the ip2me trap entry returns error & crash Orchagent (CS00011466224)"
Fixes ##6069