Routes with same prefix from static route tables should be accepted as ecmp routes
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| R3.0 |
Fix Committed
|
Medium
|
Suresh Balineni | |||
| Trunk |
Fix Committed
|
Medium
|
Suresh Balineni | |||
Bug Description
Version: 3.0-2713~kilo
Topo:
cfgm: nodec22
control: nodec22,
compute: nodeg8,
This is the vn/vm topo:
src vm(src vn)
The end goal here is to make the forward path non ecmp (source to destination) and reverse path ecmp(destination to source).
source vn in 10.1.1.0/24 and destination vn is 20.1.1.0/24
source vm is 10.1.1.4 and destination vm is 20.1.1.4
The 2 transit vns created here are not service vms and do not share an ip. transit vm 1's left interface is 10.1.1.3 and right interface is 20.1.1.3. transit vm 2's left interface is 10.1.1.5 and right is 20.1.1.5. They have routing enabled and sit in both source and destination vn. I have created network route tables for both source and destination vns as below:
source vn entry(both exact and generic route):
prefix 20.1.1.0/24 next-hop 10.1.1.3 next-hop-type ip-address
prefix 20.1.1.4/32 next-hop 10.1.1.5 next-hop-type ip-address
destination vn entry(same prefix):
prefix 10.1.1.0/24 next-hop 20.1.1.3 next-hop-type ip-address <<---same prefix
prefix 10.1.1.0/24 next-hop 20.1.1.5 next-hop-type ip-address <<---same prefix
As destination vn's prefixes are same, I expect the prefix to be installed as ecmp when being installed on the right vrf. The UI accepts them and there is no error there. The api command also shows both prefixes seperately.
root@nodec22:~# curl -u admin:contrail123 http://
% Total % Received % Xferd Average Speed Time Time Time Current
100 1428 100 1428 0 0 458k 0 --:--:-- --:--:-- --:--:-- 697k
{
"route-table": {
"fq_name": [
],
"href": "http://
"id_perms": {
},
"uuid": {
}
},
"name": "st-rt-dst",
"perms2": {
},
"routes": {
{
},
{
}
]
},
"uuid": "5fc664fb-
{
],
}
]
}
}
But the control node's inet table entry only picks up one of the entries for 10.1.1.0 with the next hop as 20.1.1.5(possibly the last entered entry) instaed of ecmp with 20.1.1.3 and 20.1.1.5 and introspect also has only one entry with the nh type as tunnel instead of ecmp.
If this feature is not supported/will not be supported, UI should block the creation of entries with same prefix.
| summary: |
- Same prefixed routes from static route tables should be accepted as ecmp - routes + Routes with same prefix from static route tables should be accepted as + ecmp routes |
| description: | updated |
| description: | updated |
| description: | updated |
| tags: |
added: config removed: contrail-control |
| Changed in juniperopenstack: | |
| assignee: | nobody → Suresh Balineni (sbalineni) |
| Shashikiran H (skiranh) wrote | #1 |
| Changed in juniperopenstack: | |
| importance: | High → Critical |
| tags: | added: blocker |
| OpenContrail Admin (ci-admin-f) wrote [Review update] master | #2 |
| OpenContrail Admin (ci-admin-f) wrote [Review update] R3.0 | #6 |
| tags: | removed: blocker |
| OpenContrail Admin (ci-admin-f) wrote [Review update] master | #8 |
| OpenContrail Admin (ci-admin-f) wrote [Review update] R3.0 | #10 |
| OpenContrail Admin (ci-admin-f) wrote [Review update] master | #14 |
| OpenContrail Admin (ci-admin-f) wrote A change has been merged | #16 |
| OpenContrail Admin (ci-admin-f) wrote | #17 |
| Changed in juniperopenstack: | |
| milestone: | r3.1.0.0-fcs → r3.0.1.0 |
| information type: | Proprietary → Public |
Other topologies are seeing issues where only 1 route from the list is getting updated. They might be related to this bug, where api is accepting multiple routes, but the rest of the chain is unable to handle it.