[LISPMAP-165] Adding a less specific NB mapping when an included more specific SB exists leads to SB taking preference Created: 07/Sep/17 Updated: 07/Dec/17 Resolved: 07/Dec/17 |
|
| Status: | Resolved |
| Project: | lispflowmapping |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | Oxygen, Nitrogen-SR2 |
| Type: | Bug | ||
| Reporter: | Lori Jakab | Assignee: | Lori Jakab |
| 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: | 9116 |
| Priority: | Normal |
| Description |
|
If we have a mapping like 192.168.1.0/24 in stored in SB, with subscribers, a new NB mapping like 192.168.0.0/16 being added will not trigger a notification for the subscribers. In a NB first policy the less specific NB mapping takes precedence, and subscribers of the existing SB should be notified to update their mappings, including removal of the SB mapping. |
| Comments |
| Comment by Lori Jakab [ 24/Oct/17 ] |
|
Patches: |