| 2018-12-10 10:07:25 |
aswani kumar |
bug |
|
|
added bug |
| 2018-12-10 10:07:43 |
aswani kumar |
nominated for series |
|
juniperopenstack/trunk |
|
| 2018-12-10 10:07:43 |
aswani kumar |
bug task added |
|
juniperopenstack/trunk |
|
| 2018-12-10 10:07:50 |
aswani kumar |
juniperopenstack/trunk: milestone |
|
r5.1.0 |
|
| 2018-12-10 10:08:04 |
aswani kumar |
juniperopenstack/trunk: assignee |
|
David Fannin (davidfannin) |
|
| 2018-12-10 10:08:10 |
aswani kumar |
juniperopenstack/trunk: importance |
Undecided |
Critical |
|
| 2018-12-10 10:08:20 |
aswani kumar |
tags |
|
contrail-command |
|
| 2018-12-10 10:36:45 |
aswani kumar |
description |
5.1 build 418 contrail command routing-policy
Routing policy should allow to set community and ext_community in the "from" filed to user defined community values
eg: FROM 'ext community target:64512:50000' protocol interface THEN action [accept]
Currently community and external_community in from field allow following values to choose from
of which it should be allowed to filter based upon other community_values
accept-own
no-advertise
no-export
no-advertise-subconfed
no-reoriginate |
5.1 build 418 contrail command routing-policy
Routing policy should allow to set community and ext_community in the "from" field to user defined community values
eg: FROM 'ext community target:64512:50000' protocol interface THEN action [accept]
Currently community and external_community in from field allow following values to choose from
of which it should be allowed to filter based upon other community_values
accept-own
no-advertise
no-export
no-advertise-subconfed
no-reoriginate |
|
| 2018-12-10 10:39:14 |
aswani kumar |
description |
5.1 build 418 contrail command routing-policy
Routing policy should allow to set community and ext_community in the "from" field to user defined community values
eg: FROM 'ext community target:64512:50000' protocol interface THEN action [accept]
Currently community and external_community in from field allow following values to choose from
of which it should be allowed to filter based upon other community_values
accept-own
no-advertise
no-export
no-advertise-subconfed
no-reoriginate |
5.1 build 418 contrail command routing-policy
Routing policy should allow to set community and ext_community in the "from" field to user defined community values
eg: FROM 'ext community target:64512:50000' protocol interface THEN action [accept]
Currently community and external_community in the 'from' field allows following values to choose from
accept-own
no-advertise
no-export
no-advertise-subconfed
no-reoriginate
of which it should also allow other community_values to filter |
|
| 2018-12-10 10:40:00 |
aswani kumar |
description |
5.1 build 418 contrail command routing-policy
Routing policy should allow to set community and ext_community in the "from" field to user defined community values
eg: FROM 'ext community target:64512:50000' protocol interface THEN action [accept]
Currently community and external_community in the 'from' field allows following values to choose from
accept-own
no-advertise
no-export
no-advertise-subconfed
no-reoriginate
of which it should also allow other community_values to filter |
5.1 build 418 contrail command routing-policy
Routing policy should allow to set community and ext_community in the "from" field to user defined community values
eg: FROM 'ext community target:64512:50000' protocol interface THEN action [accept]
Currently community and external_community in the 'from' field allows following values to choose from
accept-own
no-advertise
no-export
no-advertise-subconfed
no-reoriginate
of which it should also allow to pass other community_values as filter |
|
