[chassis] [MA] Route flap fix#10206
Conversation
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
hi @abdosi @SuvarnaMeenakshi can you help to review this PR? |
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
@wenyiz2021 PR conflicts with 202305 branch |
|
Cherry-pick PR to 202205: #10553 |
Description of PR
Fix issue for packet chassis.
For VOQ chassis or other multi-asic duts, we were using VOQ_INBAND_INTERFACE and BGP_INTERNAL_NEIGHBOR to exclude internal interfaces in this test. However, packet chassis internal interfaces/portchannels do not have any IP associated with them.
Changes in this PR:
dev_portwe get is external port again by usingshow ip intand grep for this dev_port,show ip intwithout-d allwill not have internal links. Ideally the dev_port should already be an external link, but if there is any multi-asic device that does not have point#1 and point#2 above, this check will get hit and we skip applying this port todev_port.Note that by using
grep -wwe will be doing complete word match.Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
verified on one linecard of packet chassis.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation