[LISPMAP-40] Inconsistency between MD-SAL and DAO when EID-URI doesn't match mapping or key EID Created: 28/May/15  Updated: 19/Oct/17  Resolved: 11/Feb/16

Status: Resolved
Project: lispflowmapping
Component/s: General
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: 3410

 Description   

It is possible to add keys or mappings with different eid URIs using the same actual EID stored in the LispAddressContainer/maskLenght combination. In that case, the MD-SAL config datastore will have multiple mappings, while the DAO only one.

EXAMPLE
-------

PUT http://localhost:8181/restconf/config/lfm-mapping-database:mapping-database/instance-id/0/authentication-key/192.0.2.1/

{
"authentication-key": {
"eid": "192.0.2.1",
"LispAddressContainer": {
"Ipv4Address":

{ "afi": 1, "Ipv4Address": "192.0.2.1" }

},
"mask-length": 32,
"key-type": 1,
"authkey": "password"
}
}

—

PUT http://localhost:8181/restconf/config/lfm-mapping-database:mapping-database/instance-id/0/authentication-key/192.0.2.1bis/

{
"authentication-key": {
"eid": "192.0.2.1bis",
"LispAddressContainer": {
"Ipv4Address":

{ "afi": 1, "Ipv4Address": "192.0.2.1" }

},
"mask-length": 32,
"key-type": 1,
"authkey": "password"
}
}

MD-SAL config datastore will have two mappings, one for '192.0.2.1' and one for '192.0.2.1bis', while the DAO will have single entry for 192.0.2.1/32.

 Comments   
Comment by Vina Ermagan [ 11/Feb/16 ]

Fixed in Be

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