Juniper Openstack

[EVPN VXLAN] For TSN IP , only the first IM route getting programed in QFX route table

  1. Series trunk
  2. Bug #1715817
Bug #1715817 reported by chhandak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R4.0
Fix Committed
Critical
Suresh Balineni
Juniper Openstack r4.0.1.0 "r4.0.1.0"
Trunk
Fix Committed
Critical
Suresh Balineni
Juniper Openstack r4.1.0.0-fcs "r4.1"

Bug Description

When we have multiple VNI configured in EVPN Instance, contrail control is publishing TSN IP for each VNI as inclusive multicast route.
In QFX we can see all the route received from contrail control node but only the first one is getting programmed in the route table.

root@5b11-qfx2# run show route receive-protocol bgp 172.16.180.101

inet.0: 15 destinations, 18 routes (15 active, 0 holddown, 0 hidden)

:vxlan.inet.0: 12 destinations, 12 routes (12 active, 0 holddown, 0 hidden)

inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

bgp.rtarget.0: 6 destinations, 13 routes (6 active, 0 holddown, 0 hidden)
  Prefix Nexthop MED Lclpref AS path
  65000:65000:8000001/96
* 172.16.180.101 100 I
  65000:65000:8000002/96
                          172.16.180.101 100 I
  65000:65000:8000003/96
                          172.16.180.101 100 I

bgp.evpn.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
  Prefix Nexthop MED Lclpref AS path
  3:172.16.180.101:2::10000::172.16.180.101/248 IM
* 172.16.180.101 200 100 ?
  3:172.16.180.101:3::10001::172.16.180.101/248 IM
* 172.16.180.101 200 100 ?
  3:172.16.180.103:2::10000::172.16.180.103/248 IM
* 172.16.180.103 200 100 ?
  3:172.16.180.103:3::10001::172.16.180.103/248 IM
* 172.16.180.103 200 100 ?

default-switch.evpn.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
  Prefix Nexthop MED Lclpref AS path
  3:172.16.180.101:2::10000::172.16.180.101/248 IM
* 172.16.180.101 200 100 ? >>> only for VNI 10000
  3:172.16.180.103:2::10000::172.16.180.103/248 IM
* 172.16.180.103 200 100 ?

>> for VNI 10001 IM route for 172.16.180.101 and 172.16.180.103 missing

Currently DM is configuring different policy statement for each VNI and importing multiple policy. Instead when we configure only one vrf-import policy and add all import communities in this policy, each community as a new term, it worked fine.

Now configured two VNI and made following changes:

root@5b11-qfx2# show | compare rollback 1
[edit groups __contrail__ policy-options policy-statement _contrail_vn-scale-test1-10000-l2-4-import]
      term t1 { ... }
+ term t2 {
+ from community _contrail_target_65000_8000003;
+ then accept;
+ }
[edit groups __contrail__ policy-options]
! inactive: policy-statement _contrail_vn-scale-test1-10001-l2-5-import { ... }
[edit groups __contrail__ switch-options]
- vrf-import [ _contrail_vn-scale-test1-10000-l2-4-import _contrail_vn-scale-test1-10001-l2-5-import ];
+ vrf-import _contrail_vn-scale-test1-10000-l2-4-import;

Output
—————
root@5b11-qfx2# run show route receive-protocol bgp 172.16.180.101

inet.0: 15 destinations, 18 routes (15 active, 0 holddown, 0 hidden)

:vxlan.inet.0: 12 destinations, 12 routes (12 active, 0 holddown, 0 hidden)

inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

bgp.rtarget.0: 6 destinations, 13 routes (6 active, 0 holddown, 0 hidden)
  Prefix Nexthop MED Lclpref AS path
  65000:65000:8000001/96
* 172.16.180.101 100 I
  65000:65000:8000002/96
                          172.16.180.101 100 I
  65000:65000:8000003/96
                          172.16.180.101 100 I

bgp.evpn.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
  Prefix Nexthop MED Lclpref AS path
  3:172.16.180.101:2::10000::172.16.180.101/248 IM
* 172.16.180.101 200 100 ?
  3:172.16.180.101:3::10001::172.16.180.101/248 IM
* 172.16.180.101 200 100 ?
  3:172.16.180.103:2::10000::172.16.180.103/248 IM
* 172.16.180.103 200 100 ?
  3:172.16.180.103:3::10001::172.16.180.103/248 IM
* 172.16.180.103 200 100 ?

default-switch.evpn.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
  Prefix Nexthop MED Lclpref AS path
  3:172.16.180.101:2::10000::172.16.180.101/248 IM
* 172.16.180.101 200 100 ?
  3:172.16.180.101:3::10001::172.16.180.101/248 IM
* 172.16.180.101 200 100 ?
  3:172.16.180.103:2::10000::172.16.180.103/248 IM
* 172.16.180.103 200 100 ?
  3:172.16.180.103:3::10001::172.16.180.103/248 IM
* 172.16.180.103 200 100 ?

root@5b11-qfx2# run show route table default-switch.evpn.0

default-switch.evpn.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

3:172.16.2.1:1::10000::172.16.2.1/248 IM
                   *[EVPN/170] 06:08:28
                      Indirect
3:172.16.2.1:1::10001::172.16.2.1/248 IM
                   *[EVPN/170] 06:08:28
                      Indirect
3:172.16.3.1:1::10000::172.16.3.1/248 IM
                   *[BGP/170] 06:07:50, localpref 100, from 172.16.3.1
                      AS path: I, validation-state: unverified
                    > to 172.16.10.2 via xe-0/0/44.0
3:172.16.3.1:1::10001::172.16.3.1/248 IM
                   *[BGP/170] 06:07:50, localpref 100, from 172.16.3.1
                      AS path: I, validation-state: unverified
                    > to 172.16.10.2 via xe-0/0/44.0
3:172.16.180.101:2::10000::172.16.180.101/248 IM
                   *[BGP/170] 06:08:24, MED 200, localpref 100
                      AS path: ?, validation-state: unverified
                    > to 172.16.180.101 via xe-0/0/47.0
3:172.16.180.101:3::10001::172.16.180.101/248 IM
                   *[BGP/170] 00:18:51, MED 200, localpref 100
                      AS path: ?, validation-state: unverified
                    > to 172.16.180.101 via xe-0/0/47.0
3:172.16.180.103:2::10000::172.16.180.103/248 IM
                   *[BGP/170] 06:08:24, MED 200, localpref 100, from 172.16.180.101
                      AS path: ?, validation-state: unverified
                    > to 172.16.180.103 via xe-0/0/47.0
3:172.16.180.103:3::10001::172.16.180.103/248 IM
                   *[BGP/170] 00:18:51, MED 200, localpref 100, from 172.16.180.101
                      AS path: ?, validation-state: unverified
                    > to 172.16.180.103 via xe-0/0/47.0

chhandak (chhandak)
Changed in juniperopenstack:
importance: Undecided → Critical
information type: Proprietary → Public
summary: - [EVPn VXLAN] For TSN IP , only the first IM route getting programed in
+ [EVPN VXLAN] For TSN IP , only the first IM route getting programed in
QFX route table
Changed in juniperopenstack:
milestone: none → r4.0.1.0
tags: added: blocker
Rudra Rugge (rrugge)
Changed in juniperopenstack:
assignee: nobody → Sachin Bansal (sbansal)
Sachin Bansal (sbansal)
Changed in juniperopenstack:
assignee: Sachin Bansal (sbansal) → Suresh Balineni (sbalineni)
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R4.0

Review in progress for https://review.opencontrail.org/35414
Submitter: Suresh Balineni (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/35415
Submitter: Suresh Balineni (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/35414
Committed: http://github.com/Juniper/contrail-controller/commit/68c6752d7e7131d764e1dab76db0f889cfaa7eb0
Submitter: Zuul (<email address hidden>)
Branch: R4.0

commit 68c6752d7e7131d764e1dab76db0f889cfaa7eb0
Author: sbalineni <email address hidden>
Date: Fri Sep 8 15:43:23 2017 -0700

[DM]: QFX: do not configure reject under policy stmt

Today we configure policy with reject for each VN,
this will block other vn's traffic if this policy is met since all VN's belongs same RI

Change-Id: I2754f7e7a9a20666c98af19b6e716099c454a40f
Closes-Bug: #1715817

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote :

Reviewed: https://review.opencontrail.org/35415
Committed: http://github.com/Juniper/contrail-controller/commit/0877be657f78f3d2f72f514fee3231345ec99428
Submitter: Zuul (<email address hidden>)
Branch: master

commit 0877be657f78f3d2f72f514fee3231345ec99428
Author: sbalineni <email address hidden>
Date: Fri Sep 8 15:43:23 2017 -0700

[DM]: QFX: do not configure reject under policy stmt

Today we configure policy with reject for each VN,
this will block other vn's traffic if this policy is met since all VN's belongs same RI

Change-Id: I2754f7e7a9a20666c98af19b6e716099c454a40f
Closes-Bug: #1715817

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.