[NETVIRT-622] [l3vpn_ecmp] Bug in loadbalancing group programming for directly connected subnet routes Created: 17/Apr/17 Updated: 04/May/17 Resolved: 04/May/17 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | General |
| Affects Version/s: | Carbon |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Gobinath Suganthan | Assignee: | Gobinath Suganthan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 8235 |
| Description |
|
When an extra route is added(extra route with macaddress), the loadbalancing group programmed for ecmp should contain either buckets pointing to the local nexthop group or the tunnels. But in case of the directly connected subnet routes, the groupIds of the loadbalancing group and the local nexthop group turns out to be same, the latter overriding it. |
| Comments |
| Comment by Gobinath Suganthan [ 17/Apr/17 ] |
|
When an extra route is added(extra route with macaddress), the loadbalancing group programmed for ecmp should contain either buckets pointing to the local nexthop group or the tunnels. But in case of the directly connected subnet routes, the groupIds of the loadbalancing group and the local nexthop group turns out to be same, the latter overriding it. |