DM: Incorrect RT export policy for private VN

Bug #1457264 reported by amit surana
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R2.20
Fix Committed
High
Suresh Balineni
Trunk
Fix Committed
High
Suresh Balineni

Bug Description

When DM pushes the VRF config corresponding to a contrail VN, it sets the route import/export policy. This VRF should export only the configured RT and should import all RTs that are permitted based on policy configurations. Currently, the export policy is set to export all RT.

VN1 with RT 10000 and VN2 with RT 20000 are created. The resulting policy-options:

policy-options {
    policy-statement __contrail__ef083ed0-9550-46ff-80ff-c6a976bd9f88_VN-1-L3-export {
        term t1 {
            then {
                community add target_64512_20000;
                community add target_64512_10000;
                community add target_64512_8000001;
                community add target_64512_8000002;
                accept;
            }
        }
    }

Nischal Sheth (nsheth)
information type: Proprietary → Public
tags: added: device-manager
Nischal Sheth (nsheth)
summary: - [R2.20] DM: Incorrect RT export policy for private VN
+ DM: Incorrect RT export policy for private VN
Revision history for this message
Nischal Sheth (nsheth) wrote :

@Amit

Discussed the other question you asked Suresh i.e. why add the
auto-generated targets to MX config. We should continue doing
that because it's not mandatory for the user to configure route
target on the VN. It's needed only if the routes need to go to
a WAN network that uses it's own RT to represent the VPN. If
the 2 VN is needed on the MX only to do inter-VN L3 forwarding
user shouldn't need to configure the RT on the VN.

IOW, once Suresh has fixed this bug, you should test the inter-
subnet routing functionality without configuring RTs on the VNs.

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

Review in progress for https://review.opencontrail.org/10729
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/10729
Committed: http://github.org/Juniper/contrail-controller/commit/5b80966ea97675c0f5c0b6c5bbc10ce324e5a00a
Submitter: Zuul
Branch: R2.20

commit 5b80966ea97675c0f5c0b6c5bbc10ce324e5a00a
Author: sbalineni <email address hidden>
Date: Fri May 22 15:14:26 2015 -0700

DM: set only VN's export targets on MX

Change-Id: I29c1e5b9eedc46373c83e928cf348467c9b2e9ca
Closes-Bug: 1457264

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

Reviewed: https://review.opencontrail.org/10728
Committed: http://github.org/Juniper/contrail-controller/commit/828a9d6a590e2035377cfe62c82114f8457c9f93
Submitter: Zuul
Branch: master

commit 828a9d6a590e2035377cfe62c82114f8457c9f93
Author: sbalineni <email address hidden>
Date: Fri May 22 15:08:24 2015 -0700

DM: set only VN's export targets on MX

Closes-Bug: 1457264

Change-Id: Ib9cab4b01f12991f40c6daaec6d773e9294767e2

amit surana (asurana-t)
no longer affects: juniperopenstack/r2.30
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.