EVPN VXLAN: DM changing rt value in QFX 5100 config once policy is applied in VN

Bug #1714843 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
Trunk
Fix Committed
Critical
Suresh Balineni

Bug Description

DM is messing up with the config once we are adding policy to VN and vn has 2 import targets. Ideally policy should not have any impact on Leaf as it is L2 domain. Can you please take a look?

Steps to recreate:
Create a VN . It has RT value target:65000:8000002 . Same is pushed to QFX.
Adding policy to VN which allow traffic between VN and New VN. Now VN has 2 RT value target:65000:8000002 and target:65000:8000003. Here DM pushing target:65000:8000003 to QFX. Ideally it should not change any config in Leaf.

Chenge in config after applying policy in contrail VN
------------------------------------------------------
root@5b11-qfx2# show | compare rollback 1
[edit groups __contrail__ protocols evpn vni-options vni 4]
- vrf-target target:65000:8000002;
+ vrf-target target:65000:8000003;
[edit groups __contrail__ policy-options policy-statement _contrail_vn-test-1-l2-4-import term t1 from]
- community _contrail_target_65000_8000002;
+ community [ _contrail_target_65000_8000002 _contrail_target_65000_8000003 ];
[edit groups __contrail__ policy-options]
+ community _contrail_target_65000_8000003 members target:65000:8000003;

http://10.87.69.1:8083/Snh_ShowRoutingInstanceSummaryReq?search_string=

Setup Details:
env.roledefs = {
    'all': [host1, host2, host3],
    'cfgm': [host1],
    'openstack': [host1],
    'control': [host1],
    'compute': [host1, host2, host3],
    'collector': [host1],
    'webui': [host1],
    'database': [host1],
    'build': [host_build],
    'tsn': [host1, host3],
}

#Hostnames
env.hostnames = {
    host1: '5b11s14',
    host2: '5b11s15',
    host2: '5b11s17',
}

chhandak (chhandak)
Changed in juniperopenstack:
importance: Undecided → Critical
assignee: nobody → Hari Prasad Killi (haripk)
milestone: none → r4.0.1.0
information type: Proprietary → Public
summary: - EVPN VXLAN: TSN HA: After applying policy to the VN qfx is getti ng
- removed from composite next hop
+ EVPN VXLAN: TSN HA: After applying policy to the VN qfx is getting
+ removed from TSN composite next hop
tags: added: vrouter
Changed in juniperopenstack:
assignee: Hari Prasad Killi (haripk) → Manish Singh (manishs)
chhandak (chhandak)
summary: - EVPN VXLAN: TSN HA: After applying policy to the VN qfx is getting
+ EVPN VXLAN: TSN HA: After applying policy to the VN, qfx is getting
removed from TSN composite next hop
Revision history for this message
Manish Singh (manishs) wrote : Re: EVPN VXLAN: TSN HA: After applying policy to the VN, qfx is getting removed from TSN composite next hop

Here is further analysis. Does not seem to be agent issue.
On QFX please explain following:

Qfx2:

root@5b11-qfx2> show ethernet-switching instance |grep contrail
vlan Default default-switch contrail_vn-test-1-l2-4 1067 NA

{master:0}
root@5b11-qfx2> show configuration |display set |grep contrail |grep vni-optio
set groups __contrail__ protocols evpn vni-options vni 4 vrf-target target:65000:8000003

qfx3:

root@5b11-qfx3> show ethernet-switching instance |grep contrail
vlan Default default-switch contrail_vn-test-2-l2-5 1311 NA

{master:0}
root@5b11-qfx3> show configuration |display set |grep contrail |grep vni-optio
set groups __contrail__ protocols evpn vni-options vni 5 vrf-target target:65000:8000003

{master:0}
root@5b11-qfx3>

Above it is seen that vrf-target for both are 65000:8000003 but I don’t see any config for 65000:8000002.
In contrail 8000002 belongs to vn-test-2 while 8000003 belongs to vn-test-1.
Since both QFX do not have any config for 800002 we don’t see any replication list for same in contrail.
If you check for vn-test-2 you will find both QFX in replication list. Though there is one more config issue. Why on Qfx2 vni 4 matches to 800003 and not 8000002.

So am not sure how it was working before and its relation to policy. Any idea?

Revision history for this message
Manish Singh (manishs) wrote :

In CN introspect, routes are not seen here.
http://10.87.69.1:8083/Snh_ShowRouteReq?x=bgp.evpn.0

Changed in juniperopenstack:
assignee: Manish Singh (manishs) → chhandak (chhandak)
chhandak (chhandak)
description: updated
Changed in juniperopenstack:
assignee: chhandak (chhandak) → Suresh Balineni (sbalineni)
summary: - EVPN VXLAN: TSN HA: After applying policy to the VN, qfx is getting
- removed from TSN composite next hop
+ EVPN VXLAN: DM changing rt value in QFX 5100 config once policy is
+ applied in VN
chhandak (chhandak)
tags: added: blocker device-manager
removed: vrouter
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

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

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

Review in progress for https://review.opencontrail.org/35287
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/35285
Committed: http://github.com/Juniper/contrail-controller/commit/1fd89172672719deaed327b1de839c537a991aa2
Submitter: Zuul (<email address hidden>)
Branch: master

commit 1fd89172672719deaed327b1de839c537a991aa2
Author: sbalineni <email address hidden>
Date: Tue Sep 5 15:53:13 2017 -0700

[DM]: QFX L2 Leaf - Configure only VN's route target under evpn instance

- Should not import connected RI's route targets
- Configure Evpn options only in the case of QFX acting as Leaf
- added UT

Change-Id: Ia7d1348af97ae11fa2be8f783131e2e14e89af2c
Closes-Bug: #1714843

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

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

commit 54244768f2c829d3f773e394c74d52f51f80e6d4
Author: sbalineni <email address hidden>
Date: Tue Sep 5 15:53:13 2017 -0700

[DM]: QFX L2 Leaf - Configure only VN's route target under evpn instance

- Should not import connected RI's route targets
- Configure Evpn options only in the case of QFX acting as Leaf
- added UT

Change-Id: Ia7d1348af97ae11fa2be8f783131e2e14e89af2c
Closes-Bug: #1714843

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

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

commit 655b7312e3d1ba40977ac8e3bbfef99009532972
Author: sbalineni <email address hidden>
Date: Fri Sep 22 15:36:45 2017 -0700

[DM]: QFX L2 Leaf - Configure only VN's route target under evpn instance

- Should not import connected RI's route targets
- This issue should have been fixed with bug: 1714843
But, for some reason, did not check condition properly in this change:
https://review.opencontrail.org/#/c/35287/

Change-Id: Ie957d562c3a2be15727b53b3919ec82cf08f1563
Closes-Bug: #1719007

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

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

commit 301f0682fac26cf61641dab50d469dc8da94604f
Author: sbalineni <email address hidden>
Date: Fri Sep 22 15:36:45 2017 -0700

[DM]: QFX L2 Leaf - Configure only VN's route target under evpn instance

- Should not import connected RI's route targets
- This issue should have been fixed with bug: 1714843
But, for some reason, did not check condition properly in this change:
https://review.opencontrail.org/#/c/35287/

Change-Id: Ie957d562c3a2be15727b53b3919ec82cf08f1563
Closes-Bug: #1719007

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

Other bug subscribers

Remote bug watches

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