RTC should limit eBGP peers to which VPN routes are advertised
Bug #1582933 reported by
Nischal Sheth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
High
|
Nischal Sheth | |||
R2.21.x |
Fix Committed
|
High
|
Nischal Sheth | |||
R2.22.x |
Fix Committed
|
High
|
Nischal Sheth | |||
R3.0 |
Fix Committed
|
High
|
Nischal Sheth | |||
Trunk |
Fix Committed
|
High
|
Nischal Sheth |
Bug Description
Current implementation of RTC (RFC 4684) advertises VPN routes to all
eBGP peers by default. This includes non-best eBGP peers in multiple
ASes.
Change this to only consider peers in the same neighbor AS as the best
eBGP path for a given RTC route. Note that different RTC routes for
the same RT can and will result in VPN routes being advertised to more
than 1 AS. This is correct behavior.
Review in progress for https:/ /review. opencontrail. org/20336
Submitter: Nischal Sheth (<email address hidden>)