Fix to use non RegionalHub T3 peers when selecting port. #9023
Fix to use non RegionalHub T3 peers when selecting port. #9023judyjoseph merged 3 commits intosonic-net:masterfrom
Conversation
… type has roupemaps which filters route resulting in test failures.
|
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:
|
5bcdc1d to
7594bd5
Compare
|
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:
|
|
/easycla |
|
Cherry-pick PR to 202205: #9138 |
* Fix to use non RegionalHub T3 peers when selecting port. Regional hub type has roupemaps which filters route resulting in test failures.
|
@judyjoseph PR conflicts with 202305 branch |
|
@judyjoseph PR conflicts with 202205 branch |
|
This PR was merged before 202305 branch was created. Removing 202305 related labels. |
Already included in 202305 branch. |
Already cherry-picked to 202205 branch. |
Description of PR
When the minigraph/Config has T3 Peer is a "Regional Hub" type in DEVICE_NEIGHBOR_METADATA and if we select that T3 peer loopback IP for end to end ping -- the ping from T1 --> T3 loopback ip fails. This is because the the routemaps for that "Regional Hub" type filter the loopback routes advertised to SONiC T2.
Summary:
Fixes #9021
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
Fix was to use T3 peer devices of this SONiC T2 which is of other types like AZNGHub. So filter the ethernet/portchannel interfaces based on which peer type it is connected to.
How did you verify/test it?
Ran the above tests which were failing earlier and it passes now.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation