[LISPMAP-55] Parent subscribers are not SMR'ed when a Src/Dst mapping is added Created: 07/Jul/15  Updated: 19/Oct/17  Resolved: 15/Jul/15

Status: Resolved
Project: lispflowmapping
Component/s: Service
Affects Version/s: Lithium
Fix Version/s: None

Type: Bug
Reporter: Lori Jakab Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 3950
Priority: High

 Description   

If a mapping exists for EID A and Src/Dst mapping is added for B|A, the subscribers of A are not notified. In case some of the subscribers are responsible for the B prefix, they miss the new policy. ODL should SMR both A and B|A subscribers.



 Comments   
Comment by Lori Jakab [ 07/Jul/15 ]

Not that even if a subscriber is actually using mapping B|A, it is added to the list of subscribers for A if it didn't explicitly ask for an LCAF 12 Src/Dst EID. So this bug applies both for mapping transition from A to B|A, as well as for updates to B|A when the subscriber simply asks for A.

Comment by Lori Jakab [ 07/Jul/15 ]

Fix submitted: https://git.opendaylight.org/gerrit/#/c/23819/

Comment by Florin Coras [ 14/Jul/15 ]

I tested this with IOS routers and it's still not working.

To reproduce: assume communication between routers A and B. As a first step, register normal/dst mappings for both xtrs and ping from A to B to ensure that A becomes a subscriber for B's mapping. Second, overwrite B's mapping with a src/dst mapping. The expected behavior is to have ODL SMR A about the change, however this does not happen.

Generated at Wed Feb 07 20:06:24 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.