[EVPN VXLAN] Multi Homing: Control node not accepting the Type 1 route when address family Route Target enabled
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R4.0 |
Fix Committed
|
Critical
|
Suresh Balineni | |||
R4.1 |
Fix Committed
|
Critical
|
Suresh Balineni | |||
Trunk |
Fix Committed
|
Critical
|
Suresh Balineni |
Bug Description
QFX is advertising type 1 route with community target configured under switch-option (target:65000:1) which is different than RI route target. But contrail control does not have that in import target list. This particular vrf target is configured by DM and should be added in contrail control import list as well.
When route-target community is disabled seeing the route in bgp evpn table
* 1:172.16.
BGP group _contrail_asn-65000 type Internal
Route Distinguisher: 172.16.2.1:0
Route Label: 1
Nexthop: Self
Flags: Nexthop Change
Localpref: 100
AS path: [65000] I
Communities: target:65000:1 encapsulation:
Corroponding DM route
root@5b11-qfx2# run show configuration groups __contrail__ switch-options
vtep-source-
route-distinguisher 172.16.2.1:1;
vrf-import [ _contrail_
vrf-target {
target:65000:1;
auto;
}
description: | updated |
Changed in juniperopenstack: | |
importance: | Undecided → High |
assignee: | nobody → Nischal Sheth (nsheth) |
milestone: | none → r4.1.0.0-fcs |
information type: | Proprietary → Public |
tags: |
added: device-manager removed: contrail-control |
Review in progress for https:/ /review. opencontrail. org/37512
Submitter: Suresh Balineni (<email address hidden>)