Cascading SI with Transitive network isn't working

Bug #1505449 reported by Nachi Ueno on 2015-10-13
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R2.20
Medium
Sachin Bansal
Trunk
Medium
Sachin Bansal

Bug Description

Cascading SI with Transitive network isn't working

(verified on R2.1)

This is a topology.

Red Network <-> [SI_Red1] <-> [SI_Red2] <-> Transitive Network <-> <-> [SI_Blue1] <-> [SI_Blue2] <-> Blue Network

All SIs are transparent FW.

It looks like both of SI's right hand side routing instance exporting RT of transitive network, so routing get messed up, or
packet looping get happened.

Nischal Sheth (nsheth) on 2015-10-13
tags: added: config
information type: Proprietary → Public

Review in progress for https://review.opencontrail.org/14425
Submitter: Sachin Bansal (<email address hidden>)

Reviewed: https://review.opencontrail.org/14425
Committed: http://github.org/Juniper/contrail-controller/commit/2d871d887c2dde2a3bd11c83683d541968c3239c
Submitter: Zuul
Branch: master

commit 2d871d887c2dde2a3bd11c83683d541968c3239c
Author: Sachin Bansal <email address hidden>
Date: Wed Oct 14 10:14:34 2015 -0700

Use correct SI name to add route-target

For transit VN, the route target of the primary RI should be added to the first
service RI (for left VN), or last service RI (for right VN). Earlier, we were
always adding it to the first service RI.

Change-Id: I7e086753b4710431b419e19add132ba3ed5f1b45
Closes-Bug: 1505449

Review in progress for https://review.opencontrail.org/14551
Submitter: Sachin Bansal (<email address hidden>)

Reviewed: https://review.opencontrail.org/14551
Committed: http://github.org/Juniper/contrail-controller/commit/178eb383a0df0f46a44d97ed45ff7fdcfc3e4901
Submitter: Zuul
Branch: R2.20

commit 178eb383a0df0f46a44d97ed45ff7fdcfc3e4901
Author: Sachin Bansal <email address hidden>
Date: Tue Oct 20 09:33:18 2015 -0700

For transit VN, the route target of the primary RI should be added to the first
service RI (for left VN), or last service RI (for right VN). Earlier, we were
always adding it to the first service RI.

Change-Id: I7e086753b4710431b419e19add132ba3ed5f1b45
Closes-Bug: 1505449

Review in progress for https://review.opencontrail.org/15792
Submitter: Sunil Basker (<email address hidden>)

Review in progress for https://review.opencontrail.org/15817
Submitter: Sunil Basker (<email address hidden>)

Sunil Basker (sunilbasker) wrote :

Adding the following tests to address the test gap

Scenario #1:
Left-VN — left-services — Transit-VN — right-services — Right-VN

Test cases:
Single instance – symmetric: same type of service on both left & right
1. in-network-nat
2. In-network
3. Transparent

Single instance – asymmetric: different services on left & right
4. left: in-network-nat & right: transparent
5. left: in-network & right: transparent
6. left: in-network & right: in-network-nat

Two instances – symmetric: right & left have a same type of services
7. transparent (2 instances)
8. in-network (2 instances)
9. in-network, in-network-nat
10. transparent, in-network-nat
11. transparent, in-network

Reviewed: https://review.opencontrail.org/15792
Committed: http://github.org/Juniper/contrail-test/commit/5a3fd3922a0aa5a857c32a9532d4d9c09f3c8fb6
Submitter: Zuul
Branch: master

commit 5a3fd3922a0aa5a857c32a9532d4d9c09f3c8fb6
Author: Sunil Basker <email address hidden>
Date: Mon Dec 14 18:40:20 2015 +0530

Address test gap related to bug#1505449

Change-Id: I6fcc8f26ba882769e5e3fb10b9741d4484d628ce
Closes-Bug: #1505449

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

Other bug subscribers