[GENIUS-23] L3VPN is not honoring VTEP add or delete in operational cloud Created: 22/Sep/16 Updated: 19/Oct/17 Resolved: 01/Mar/17 |
|
| Status: | Resolved |
| Project: | genius |
| Component/s: | General |
| Affects Version/s: | (unspecified) |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Hanamantagoud V Kandagal | 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: | 6786 |
| Description |
|
L3VPN currently doesn't react to VTEP IP changes (add or delete). Whenever VTEP IP on a DPN is added or deleted , the next-hop IP of VMs in FIB entries on that DPN needs to be updated appropriately. To know which all VM FIB entries to be modified , a new DpnToInterfaceList operational datastore (DS) is being introduced in InterfaceManager. InterfaceManager will update the DpnToInterfaceList operational DS , when VM is booted or deleted. Whenever VTEP IP is added/deleted on a DPN , VPN would get a VxLAN tunnel event. VPN will query the InterfaceManager using RPC for a given DPNId to retrieve the list of VpnInterfaces(VM ports). |
| Comments |
| Comment by Hanamantagoud V Kandagal [ 18/Nov/16 ] |
|
Review link |