LISP Flow Mapping


LISP (Locator ID Separation Protocol) Flow Mapping service provides mapping services, including LISP Map-Server and LISP Map-Resolver services that store and serve mapping data to dataplane nodes and to OpenDaylight applications. Mapping data can include mapping of virtual addresses to physical network addresses where the virtual nodes are reachable or hosted. Mapping data can also include a variety of routing policies including traffic engineering and load balancing. To leverage this service, OpenDaylight applications and services can use the northbound REST API to define the mappings and policies in the LISP Mapping Service. Dataplane devices capable of LISP control protocol can leverage this service through a southbound LISP plugin. LISP-enabled devices must be configured to use this OpenDaylight service, since their Map- Server and/or Map-Resolver.

Southbound LISP plugin supports the LISP control protocol (that is, Map-Register, Map-Request, Map-Reply messages). It can also be used to register mappings in the OpenDaylight mapping service.

Major Features


  • Feature URL: MSMR

  • Feature Description: This is the core feature that provides the Mapping Services and includes the LISP southbound plugin feature as well.

  • Top Level: Yes

  • User Facing: Yes

  • Experimental: No

  • CSIT Test: CSIT


  • Feature URL: Neutron

  • Feature Description: This feature provides Neutron integration.

  • Top Level: Yes

  • User Facing: Yes

  • Experimental: Yes


Security Considerations

  • Do you have any external interfaces other than RESTCONF?

    • Yes, the southbound plugin.

  • If so, how are they secure?

    • LISP southbound plugin follows LISP RFC6833 security guidelines.

  • What port numbers do they use?

    • Port used: 4342

  • Other security issues?

    • None

Quality Assurance

  • Sonar Report (59.6%)

  • CSIT Jobs

  • All modules have been unit tested. Integration tests have been performed for all major features. System tests have been performed on most major features.

  • Registering and retrieval of basic mappings have been tested more thoroughly. More complicated mapping policies have gone through less testing.


  • Is it possible to migrate from the previous release? If so, how?

    • LISP Flow Mapping service will auto-populate the data structures from existing MD-SAL data upon service start if the data has already been migrated separately. No automated way for transferring the data is provided in this release.


  • Is this release compatible with the previous release?

    • Yes

  • Any API changes?

    • No

  • Any configuration changes?

    • No

Bugs Fixed

  • None

Known Issues


  • List of features/APIs that were EOLed, deprecated, and/or removed from this release.

    • N/A


  • The LISP implementation module and southbound plugin conforms to the IETF RFC6830 and RFC6833, with the following exceptions:

    • In Map-Request message, M bit(Map-Reply Record exist in the MapRequest) is processed, but any mapping data at the bottom of a Map-Request are discarded.

    • LISP LCAFs are limited to only up to one level of recursion, as described in the IETF LISP YANG draft.

    • No standards exist for the LISP Mapping System northbound API as of this date.

Release Mechanics