-
Notifications
You must be signed in to change notification settings - Fork 390
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Scenario: With two VRF importing each other and with routing policy attached to both VRF to edit the BgpAttr of the routes, each DBEntry notification for route replication would end up deleting and re-adding back the replicated route and notifying the secondary route. This would cause an endless route replication loop Solution: Search for secondary path while replicating the route, should compare the BgpAttr with original BgpAttr of the secondary path. Added test to validate the above fix. i.e. time stamp of the replicated path is not updated on triggering the notification of the primary route. Change-Id: I3e6b31e8b36efbc091353e828b4f9dfa809cf5ff Closes-Bug: #1597687 (cherry picked from commit ca58c3d)
- Loading branch information
Showing
8 changed files
with
172 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
<?xml version="1.0" encoding="utf-8"?> | ||
<config> | ||
<routing-policy name='basic_1'> | ||
<term> | ||
<term-match-condition> | ||
<community>23:13</community> | ||
</term-match-condition> | ||
<term-action-list> | ||
<update> | ||
<local-pref>200</local-pref> | ||
</update> | ||
<action>accept</action> | ||
</term-action-list> | ||
</term> | ||
</routing-policy> | ||
<routing-policy name='basic_2'> | ||
<term> | ||
<term-match-condition> | ||
<community>23:13</community> | ||
</term-match-condition> | ||
<term-action-list> | ||
<update> | ||
<local-pref>50</local-pref> | ||
</update> | ||
<action>accept</action> | ||
</term-action-list> | ||
</term> | ||
</routing-policy> | ||
<routing-instance name="test_0"> | ||
<routing-policy to="basic_1"> | ||
<sequence>1.0</sequence> | ||
</routing-policy> | ||
<vrf-target>target:1:101</vrf-target> | ||
</routing-instance> | ||
<routing-instance name="test_1"> | ||
<routing-policy to="basic_2"> | ||
<sequence>1.0</sequence> | ||
</routing-policy> | ||
<vrf-target>target:1:102</vrf-target> | ||
</routing-instance> | ||
</config> |