1 / 27

LISP, SDN, and OpenDaylight

LISP, SDN, and OpenDaylight. Vina Ermagan, Lori Jakab Cisco Systems. Agenda. LISP Overview LISP and SDN Availability in open source LISP in OpenDaylight Demos: Service Chaining and Disaster Recovery. Locator/ID Separation Protocol.

lavada
Download Presentation

LISP, SDN, and OpenDaylight

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LISP, SDN, andOpenDaylight Vina Ermagan, Lori Jakab Cisco Systems

  2. Agenda • LISP Overview • LISP and SDN • Availability in open source • LISP in OpenDaylight • Demos: Service Chaining and Disaster Recovery

  3. Locator/ID Separation Protocol LISP creates a Level of Indirection with two namespaces:EID and RLOC • EID (Endpoint Identifier)is the IP address of a host – just as it is today • RLOC (Routing Locator)is the IP address of the LISP router for the host • EID-to-RLOC mapping is the distributed architecture that maps EIDs to RLOCs VM VM VM VM VM VM Lisp Mapping Database OS RLOC Space App Site C Site B Internet Site A EID Space EID Space

  4. Locator/ID Separation Protocol Open Protocol: RFC published Data Plane: Encapsulation protocol to build a Multitenant Overlay - MAC in IP - IP in IP VM VM VM VM VM VM Lisp Mapping Database OS Control Plane: Mapping of Overlay address Space to underlying physical Network including policy routing Site C Site B App Internet Site A Any Physical Network: LAN,WAN,Hybrid

  5. Locator/ID Separation Protocol - policies Open Protocol: RFC published App OS Data Plane: Multitenant Overlay VM VM VM VM VM VM Lisp Mapping Database OS Control Plane: Mapping (+ policy) of overlay to underlying network Site C Site B App Internet Policy: - Multihoming - Load Balancing - Disaster Recovery Site A

  6. Locator/ID Separation Protocol - policies Open Protocol: RFC published Data Plane: Multitenant Overlay VM VM VM VM VM VM Database Control Plane: Mapping ( + policy) of overlay to underlying network OS App Policy: - Traffic Engineering - Service Chaining

  7. SDN and LISP • The consensus on SDN • Decoupling of Network Control Plane form the Data Plane • Programmable • Open • The goals of SDN • Increase flexibility and development speed of features and functionalities • LISP as we just saw • Enables network virtualization via dynamic multitenant overlays • Decoupled control plane and data plane • Programmable mapping system • Open

  8. LISP in Open Source • LISPmob.org • Linux • Android • OpenWRT • Open vSwtich • LISP DP • OpenDaylight • LISP CP • OpenStack • *coming soon

  9. LISP at ODL LISP Enabled Devices

  10. LISP at ODL LISP Enabled Devices

  11. LISP in OpenDaylight Load Balancing Traffic Engineering LISP Service OVSDB LISP Plugin LISP tunnel Legend: LISP OpenFlow ODL OVSDB LISPmob LISP CP Enabled Device OVS

  12. Available Interfaces ODL LISP Service Northbound Java API Map Server DAO Implementation Map Resolver Southbound

  13. Northbound API • Resources: • Key • Mapping • EID • src/dest • Supported mapping address types: • IPv4/IPv6/MAC • Distinguished Name • AS Numbers • Segment ID • Src/Dst • Explicit Locator Path (Traffic Eng/Service Chaining)

  14. REST API: key Request URL: http://localhost:8080/lispflowmapping/nb/v2/default/key Request body in JSON: { "key" : "asdf", "maskLength" : 24, "address" : { "ipAddress" : "10.0.0.1", "afi" : 1 } } • PUT • http://localhost:8080/lispflowmapping/nb/v2/default/key • GET • […] /nb/v2/default/key/{iid}/{afi}/{address}/{mask} • GET (src/dst) • […] /default/key/{iid}/{afi}/{srcAdd}/{srcML}/{dstAdd}/{dstML}

  15. REST API: mapping Request URL: http://localhost:8080/lispflowmapping/nb/v2/default/mapping Request body in JSON: { "key" : "asdf", "mapregister" : { "eidToLocatorRecords“ : [ { "prefixGeneric" : { "ipAddress" : “10.0.0.1”, "afi" : 1 }, "maskLength" : 24, "locators" : [ { "locatorGeneric" : { "ipAddress" : ”10.154.10.17“, "afi" : 1 }, "priority" : 1, "weight” :50} ] } ] } } • PUT • http://localhost:8080/lispflowmapping/nb/v2/default/mapping • GET • […] /nb/v2/default/mapping/{iid}/{afi}/{address}/{mask} • GET (src/dst) • […] /default/mapping/{iid}/{afi}/{srcAdd}/{srcML}/{dstAdd}/{dstML}

  16. Demo • Demo 1: Disaster Recovery • Demo 2: Service Chaining

  17. Demo topology Mapping Service Northbound API Map Server DAO Impl. Net Admin Map Resolver Southbound LISPmob Server 1 EID: 2.2.2.2 LISPmob Client LISPmob Server 2 EID: 1.1.1.1

  18. Demo – Disaster Recovery Define Key, mappings Mapping Service Northbound API Map Server DAO Impl. Net Admin Map Resolver Southbound LISPmob Server 1 EID: 2.2.2.2 LISPmob Client LISPmob Server 2 EID: 1.1.1.1

  19. Demo – Disaster Recovery Mapping Service Northbound API Map Server DAO Impl. Net Admin Map Resolver Southbound Where is 2.2.2.2? LISPmob Server 1 Ping 2.2.2.2 EID: 2.2.2.2 LISPmob Client LISPmob Server 2 EID: 1.1.1.1

  20. Demo – Disaster Recovery Mapping Service Northbound API Map Server DAO Impl. Net Admin Map Resolver Southbound LISPmob Server 1 Ping 2.2.2.2 Ping 2.2.2.2 EID: 2.2.2.2 LISPmob Client LISPmob Server 2 EID: 1.1.1.1

  21. Demo – Disaster Recovery Mapping Service 2.2.2.2: Server 2 has priority Northbound API Map Server DAO Impl. Net Admin Map Resolver Southbound LISPmob Server 1 Ping 2.2.2.2 Ping 2.2.2.2 EID: 2.2.2.2 LISPmob Client LISPmob Server 2 EID: 1.1.1.1

  22. Demo – Disaster Recovery Mapping Service Northbound API Map Server DAO Impl. Net Admin Map Resolver Southbound LISPmob Server 1 Ping 2.2.2.2 EID: 2.2.2.2 LISPmob Client Ping 2.2.2.2 LISPmob Server 2 EID: 1.1.1.1

  23. Demo – Service Chaining Mapping Service 2.2.2.2: Insert service node Northbound API Map Server DAO Impl. Net Admin Map Resolver Southbound LISPmob Server 1 Ping 2.2.2.2 EID: 2.2.2.2 LISPmob Client LISPmob Server 2 Ping 2.2.2.2 EID: 1.1.1.1 LISPmob Service-Node

  24. Demo – Service Chaining Mapping Service Northbound API Map Server DAO Impl. Net Admin Map Resolver Southbound LISPmob Server 1 Ping 2.2.2.2 Ping 2.2.2.2 EID: 2.2.2.2 LISPmob Client Ping 2.2.2.2 LISPmob Server 2 EID: 1.1.1.1 LISPmob Service-Node

  25. Demo – Service Chaining Mapping Service Northbound API Map Server DAO Policy=drop/forward Impl. Net Admin Map Resolver Southbound LISPmob Server 1 Ping 2.2.2.2 LISPmob Client LISPmob Server 2 LISPmob Service-Node

  26. Stay tuned… • Support for proactive SMR in case of policy change • Seamless integration with OVS • Tutorial for demo + API spec is on the Wiki: • https://wiki.opendaylight.org/view/OpenDaylight_Lisp_Flow_Mapping:User_Guide_for_Hydrogen#Tutorial

  27. Thanks! lispmob.org OpenWrt Android Linux

More Related