[NETVIRT-250] Origin for some routes is not being set properly Created: 07/Nov/16 Updated: 19/Oct/17 Resolved: 16/Nov/16 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | General |
| Affects Version/s: | Boron |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Miguel Perez | Assignee: | Unassigned |
| 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: | 7107 |
| Description |
|
Routes origin for locally connected VMs and/or Subnets is being mistakenly set as STATIC. The origin of the routes should attend to this classification: BGP - Indicates Routes Imported via BGP into ODL CONNECTED – Every subnet (for example a VPN) has a route directly connected STATIC - The static routes introduced by the OpenStack command “extra routes” SELFIMPORTED - Indicates this Route is replayed route on a new BGP VPN, LOCAL - https://supportforums.cisco.com/document/63281/local-host-routes-routing-table INTERVPNLINK – Indicates Routes replayed by InterVPNLink due to This classification has been taken from Cisco documentation and forums, and adapted to our own use case. So according to above, Routes to VMs should be tagged as "LOCAL" and routes to Subnets should be tagged as "CONNECTED". This is an example of how the route origin should be set: opendaylight-user@root>fib-show |