| 2017-12-20 08:48:06 |
Timothée carre |
bug |
|
|
added bug |
| 2017-12-20 08:48:30 |
Timothée carre |
information type |
Proprietary |
Public |
|
| 2017-12-20 08:50:47 |
Timothée carre |
summary |
changing import route target value not reflected into family route-target mb-bgp annoucements |
[4.0.2 - MP-BGP family route-target] changing import route target value not reflected into family route-target mb-bgp announcements |
|
| 2017-12-20 10:06:18 |
Timothée carre |
description |
If family route-target is used within an MP-BGP session between contrail-controller and a MX physical router, contrail does not send the route-target manually set into "Import Route Target(s)" parameter of a VN (so import and export target do not match).
Therefore the MX does not send corresponding routes.
On the other side, the MX effectively send the route target to contrail-controller even if it has been changed by policy (a vrf-export policy or vni-options vrf-target).
I'm using OpenContrail 4.0.2 docker image from docker hub. |
If family route-target is used within an MP-BGP session between contrail-controller and a MX physical router, contrail does not send the route-target manually set into "Import Route Target(s)" parameter of a VN (so import and export target do not match).
Therefore the MX does not send corresponding routes.
On the other side, the MX effectively send the route target to contrail-controller even if it has been changed by policy (a vrf-export policy or vni-options vrf-target).
I'm using OpenContrail 4.0.2 docker image from docker hub.
To be more precise, it seems like import only work with a value entered in "Route Target(s)" section and not in "Importe Route Target(s)" section.
"Export Route Target(s)" section seems to work as expected though. |
|
| 2017-12-20 14:38:49 |
Timothée carre |
description |
If family route-target is used within an MP-BGP session between contrail-controller and a MX physical router, contrail does not send the route-target manually set into "Import Route Target(s)" parameter of a VN (so import and export target do not match).
Therefore the MX does not send corresponding routes.
On the other side, the MX effectively send the route target to contrail-controller even if it has been changed by policy (a vrf-export policy or vni-options vrf-target).
I'm using OpenContrail 4.0.2 docker image from docker hub.
To be more precise, it seems like import only work with a value entered in "Route Target(s)" section and not in "Importe Route Target(s)" section.
"Export Route Target(s)" section seems to work as expected though. |
If family route-target is used within an MP-BGP session between contrail-controller and a MX physical router, contrail does not send the route-target manually set into "Import Route Target(s)" parameter of a VN (so import and export target do not match).
Therefore the MX does not send corresponding routes.
On the other side, the MX effectively send the route target to contrail-controller even if it has been changed by policy (a vrf-export policy or vni-options vrf-target).
I'm using OpenContrail 4.0.2 docker image from docker hub.
Another issue with route target within contrail is that import route target does not seem to work as expected.
To be more precise, it seems like import only work with a value entered in "Route Target(s)" section and not in "Importe Route Target(s)" section.
"Export Route Target(s)" section seems to work as expected though. |
|
| 2017-12-20 14:39:18 |
Timothée carre |
description |
If family route-target is used within an MP-BGP session between contrail-controller and a MX physical router, contrail does not send the route-target manually set into "Import Route Target(s)" parameter of a VN (so import and export target do not match).
Therefore the MX does not send corresponding routes.
On the other side, the MX effectively send the route target to contrail-controller even if it has been changed by policy (a vrf-export policy or vni-options vrf-target).
I'm using OpenContrail 4.0.2 docker image from docker hub.
Another issue with route target within contrail is that import route target does not seem to work as expected.
To be more precise, it seems like import only work with a value entered in "Route Target(s)" section and not in "Importe Route Target(s)" section.
"Export Route Target(s)" section seems to work as expected though. |
If family route-target is used within an MP-BGP session between contrail-controller and a MX physical router, contrail does not send the route-target manually set into "Import Route Target(s)" parameter of a VN (so import and export target do not match).
Therefore the MX does not send corresponding routes.
On the other side, the MX effectively send the route target to contrail-controller even if it has been changed by policy (a vrf-export policy or vni-options vrf-target).
I'm using OpenContrail 4.0.2 docker image from docker hub.
Another issue with route target within contrail is that import route target does not seem to work as expected.
To be more precise, it seems like import only work with a value entered in "Route Target(s)" section and not in "Import Route Target(s)" section.
"Export Route Target(s)" section seems to work as expected though. |
|
| 2018-01-13 02:59:36 |
Jeba Paulaiyan |
nominated for series |
|
juniperopenstack/trunk |
|
| 2018-01-13 02:59:36 |
Jeba Paulaiyan |
bug task added |
|
juniperopenstack/trunk |
|
| 2018-01-13 02:59:41 |
Jeba Paulaiyan |
juniperopenstack/trunk: importance |
Undecided |
High |
|
| 2018-01-13 03:00:05 |
Jeba Paulaiyan |
juniperopenstack/trunk: assignee |
|
Sachin Bansal (sbansal) |
|
| 2018-01-13 03:00:08 |
Jeba Paulaiyan |
juniperopenstack/trunk: milestone |
|
r5.0.0 |
|
| 2018-01-13 03:00:12 |
Jeba Paulaiyan |
tags |
|
contrail-control |
|
| 2018-01-13 03:00:25 |
Jeba Paulaiyan |
nominated for series |
|
juniperopenstack/r4.0 |
|
| 2018-01-13 03:00:25 |
Jeba Paulaiyan |
bug task added |
|
juniperopenstack/r4.0 |
|
| 2018-01-13 03:00:25 |
Jeba Paulaiyan |
nominated for series |
|
juniperopenstack/r4.1 |
|
| 2018-01-13 03:00:25 |
Jeba Paulaiyan |
bug task added |
|
juniperopenstack/r4.1 |
|
| 2018-01-13 03:00:29 |
Jeba Paulaiyan |
juniperopenstack/r4.1: importance |
Undecided |
High |
|
| 2018-01-13 03:00:31 |
Jeba Paulaiyan |
juniperopenstack/r4.0: importance |
Undecided |
High |
|
| 2018-01-13 03:00:36 |
Jeba Paulaiyan |
juniperopenstack/r4.0: assignee |
|
Sachin Bansal (sbansal) |
|
| 2018-01-13 03:00:42 |
Jeba Paulaiyan |
juniperopenstack/r4.1: assignee |
|
Sachin Bansal (sbansal) |
|
| 2018-01-13 03:00:45 |
Jeba Paulaiyan |
juniperopenstack/r4.0: milestone |
|
r4.0.3.0 |
|
| 2018-01-13 03:00:47 |
Jeba Paulaiyan |
juniperopenstack/r4.1: milestone |
|
r4.1.1.0 |
|
| 2018-01-14 01:59:44 |
Nischal Sheth |
juniperopenstack/r4.0: assignee |
Sachin Bansal (sbansal) |
venu kolli (vkolli) |
|
| 2018-01-14 01:59:57 |
Nischal Sheth |
juniperopenstack/r4.1: assignee |
Sachin Bansal (sbansal) |
venu kolli (vkolli) |
|
| 2018-01-14 02:00:12 |
Nischal Sheth |
juniperopenstack/trunk: assignee |
Sachin Bansal (sbansal) |
venu kolli (vkolli) |
|
| 2018-03-21 02:47:50 |
Jeba Paulaiyan |
juniperopenstack/trunk: milestone |
r5.0.0 |
r5.0.1 |
|
| 2018-03-21 02:47:51 |
Jeba Paulaiyan |
juniperopenstack/r4.1: milestone |
r4.1.1.0 |
r4.1.2.0 |
|
| 2018-07-17 08:16:08 |
Jeba Paulaiyan |
nominated for series |
|
juniperopenstack/r5.0 |
|
| 2018-07-17 08:16:08 |
Jeba Paulaiyan |
bug task added |
|
juniperopenstack/r5.0 |
|
| 2018-07-17 08:16:13 |
Jeba Paulaiyan |
juniperopenstack/r5.0: importance |
Undecided |
High |
|
| 2018-07-17 08:16:18 |
Jeba Paulaiyan |
juniperopenstack/r5.0: assignee |
|
venu kolli (vkolli) |
|
| 2018-07-17 08:16:21 |
Jeba Paulaiyan |
juniperopenstack/r5.0: milestone |
|
r5.0.1 |
|
| 2018-07-17 08:16:24 |
Jeba Paulaiyan |
juniperopenstack/trunk: milestone |
r5.0.1 |
r5.1.0 |
|
| 2018-08-07 09:18:18 |
Jeba Paulaiyan |
juniperopenstack/r5.0: milestone |
r5.0.1 |
r5.0.2 |
|
| 2018-10-08 23:00:15 |
Jeba Paulaiyan |
juniperopenstack/r5.0: milestone |
r5.0.2 |
r5.0.3 |
|
| 2018-10-20 17:40:54 |
Jeba Paulaiyan |
juniperopenstack/r4.1: milestone |
r4.1.2.0 |
|
|
