Using LISP to Solve Today's IP Host Mobility Challenges (IOS Advantage Webinar)
 

Using LISP to Solve Today's IP Host Mobility Challenges (IOS Advantage Webinar)

on

  • 3,967 views

The Locator/ID Separation Protocol (LISP) implements a new routing architecture through a set of protocols that utilize a level of indirection to separate an IP address into two namespaces: Endpoint ...

The Locator/ID Separation Protocol (LISP) implements a new routing architecture through a set of protocols that utilize a level of indirection to separate an IP address into two namespaces: Endpoint Identifiers (EIDs), which are assigned to end-hosts, and Routing Locators (RLOCs), which are assigned to devices (primarily routers) that make up the global routing system. By separating the host address (EID) from its location (RLOC), LISP provides key benefits in many network environments, including mobility environments where hosts are now able to move anywhere within the network while keeping their IP (EID) while changing their location (RLOC).

LISP Host Mobility addresses today's enterprise data center and campus mobility challenges. This session discusses how next generation technologies such as LISP and OTV solve the networking issues associated with VM mobility and multi-tenant segmentation in the data center. An overview of the technologies and their solutions for LAN extension, mobility and segmentation is provided.

Agenda
* Business Drivers
* Brief LISP Architectural Overview
* Data Center Host Mobility Deployment Use Case
* Enterprise "Vision" for LISP
* LISP Development Status
* Conclusion

Replay the WebEx recording: https://cisco.webex.com/ciscosales/lsr.php?AT=pb&SP=EC&rID=63533782&rKey=b6212b1f49aa7674

Click here for a link to the mp4: https://communities.cisco.com/servlet/JiveServlet/download/30500-6-43940/Using%20LISP%20to%20Solve%20Today%27s%20IP%20Host%20Mobility%20Challenges.mp4
Learn more about upcoming TechAdvantage (formerly IOS Advantage) sessions at: http://www.cisco.com/go/iosadvantage

Statistics

Views

Total Views
3,967
Views on SlideShare
3,906
Embed Views
61

Actions

Likes
1
Downloads
161
Comments
0

4 Embeds 61

http://johnyork945.wordpress.com 56
http://www.linkedin.com 3
http://moderation.local 1
http://cdnstage-portal1.cdnstage.cv2bu.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Using LISP to Solve Today's IP Host Mobility Challenges (IOS Advantage Webinar) Using LISP to Solve Today's IP Host Mobility Challenges (IOS Advantage Webinar) Presentation Transcript

  • Cisco IOS Advantage Webinars Using LISP to Solve Todays IP Host Mobility Challenges Victor Moreno and Darrel Lewis We’ll get started a few minutes past the top of the hour. Note: you may not hear any audio until we get started.© 2012 Cisco and/or its affiliates. All rights reserved. 1
  • Register for a Techtorial Session: http://www.ciscolive.com/london/registration-packages/•  TECIPM-3191 - Advanced LISP Techtorial Other Techtorial Sessions from Cisco Software Experts Session Number Advanced Network Automation TECNMS-3601 Application Awareness in the Network; the Route to Application Visibility and Control TECRST-2672 Converged Access: Wired/Wireless System Architecture, Design and Operations TECCRS-2678 Enterprise QoS Design Strategy TECRST-2501 IPv6 for Dummies: An Introduction to IPv6 TECMPL-2192 IPv6 Security TECRST-2680 Scaling the IP NGN with Unified MPLS TECNMS-3601 Software Defined Networking and Use Cases TECSPG-2667 Understanding and Deploying IP Multicast Networks TECIMP-1008 © 2010 Cisco and/or its affiliates. All rights reserved. 2
  • Speakers Panelists Max Ardica Arnel Dionisio Technical Leader Technical Leader Engineering Engineering ardica@cisco.com adionisi@cisco.com Victor Moreno Darrel Lewis Gregg Schudel Solomon RajkumarDistinguished Engineer Technical Leader SW Development Engineer Engineer Technical Marketing Engineering Engineering Technical Marketingvimoreno@cisco.com darlewis@cisco.com srajkuma@cisco.com gschudel@cisco.com © 2010 Cisco and/or its affiliates. All rights reserved. 3
  • •  Submit questions in Q&A panel and send to “All Panelists” Avoid CHAT window for better access to panelists •  For Webex audio, select COMMUNICATE > Join Audio Broadcast •  For Webex call back, click ALLOW phone button at the bottom of participants side panel •  Where can I get the presentation? Or send email to: ask_techadvantage@cisco.com •  Please complete the post-event survey •  Join us November 7th for our next TechAdvantage Webinar: Media Services Proxy (MSP) for Enhanced Media Awareness and Building Plug-And-Play Media Networks www.cisco.com/go/iosadvantage© 2010 Cisco and/or its affiliates. All rights reserved. 4
  •   Host Mobility Business Drivers   What is LISP?   How Does LISP Work?   How are Customers Using LISP?   LISP Host Mobility – Fundamentals – Across Subnets – Extending Subnets – Customer Example   LISP Status and References   LISP Summary© 2010 Cisco and/or its affiliates. All rights reserved. 5
  • © 2010 Cisco and/or its affiliates. All rights reserved. 6
  • Legacy IT model: Client/Server Attributes: Client Server •  Simple •  Secure •  Static Emerging IT model: Mobile/Cloud M C M C Attributes: M C •  Connected M C •  Scalable M M C C •  Multi-tenant M C© 2010 Cisco and/or its affiliates. All rights reserved. 7
  • Distributed  Data  Center  Goals:   •  Seamless  workload  mobility  between   mul3ple  datacenters   •  Distributed  applica3ons  closer  to  end  users       •  Pool  and  maximize  global  compute   resources     •  Ensure  business  con3nuity  with  workload   mobility  and  distributed  deployments       Geographically Dispersed   Data Centers© 2010 Cisco and/or its affiliates. All rights reserved. 8
  • •  Today’s networks aren’t designed for mobility •  IP addresses are statically assigned to devices, access points, or services. •  Connecting resources on different private networks and public networks with different owners is challenging •  Mobility, Movement between networks means device, service or network element connectivity necessarily always lost. Scalability and •  Today’s networks can’t scale Interconnection •  Cloud, mobility and Internet of things are Issues Must Be overextending the ability of today’s routers to route data packets. Solved Together •  Mobility of devices and/or network elements leads to a ballooning of the amount of information stored in routing tables. •  Today’s networks require new security models •  In a world of multiple devices and multi-tenancy it’s not feasible to manually build every needed virtual private network© 2010 Cisco and/or its affiliates. All rights reserved. 9
  • Overview   LISP (Location / ID Separation Protocol) is an addressing architecture and set of protocols comprising an Endpoint Identifier (defining who a user is) and a Routing Locator (defining where the user is connected).   LISP separates the identity of the device or access point from where the device is located enabling Internet services to remain continually connected when users move around or change devices. Use-cases Benefits   Global Workload Mobility   Mobility IP address Portability   Workload Portability to Cloud   Scalability  On-Demand Route lookup   Secure Multi-tenancy across organizations   Security  Tenant ID based Segmentation   Rapid IPv6 Deployment   Address Family Independence Evolving the World’s Networks for the Cloud Era © 2010 Cisco and/or its affiliates. All rights reserved. 10
  • BusinessBusiness Goals LISP Enables BenefitsContinuous Distributed Clusters with Network Stability, ApplicationOperation accelerate Disaster Recovery Resiliency Compute Workloads Anywhere, beyond a GeoGlobal Availability single physical data center or organization Diversity Dynamic Add Capacity at will for peaks, on-demandRespond to Change Business additions in private or public cloud Flexibility © 2010 Cisco and/or its affiliates. All rights reserved. 11 11
  • BusinessBusiness Goals LISP Enables Benefits Faster ServiceNew Services Creation Unleash Compute Virtualization TTMMaximize Asset Workload Migration and Server Employ IdleUtilization Consolidation Resources Lower Cost ofReduce Expenses Simplify Inter-site Change Management Managing © 2010 Cisco and/or its affiliates. All rights reserved. 12 12
  • Mobility Overview   Topology independent addressing Provider  B   Provider  A     Overlay solution   IPv4 or IPv6 agnostic Primary DC Secondary DC Benefits   Integrated Mobility Applicability   Mobility across organizations (SPs, Cloud   Active-Active Data Centers Providers)   Data Center Disaster Recovery   IPv4, IPv6 or a combination   Workload Portability to Cloud (aka Bursting)   Optimal traffic path (no triangulation)   Federated Cloud open connectivity Evolving the World’s Networks for the Cloud Era © 2010 Cisco and/or its affiliates. All rights reserved. 13
  • © 2010 Cisco and/or its affiliates. All rights reserved. 14
  • Routing DFZ Table Site 3 IPv4 Internet Site 1 Transit SP AS 200 AS 300 Site 2 12. 0/8 13. 0/8 Tier 1 SP Commodity SP eBGP 64.1.0.0/17 eBGP 64.1.0.0/16 64.2.128.0/17 64.2.0.0/16 Locators 12.1.1.2/30 12.1.1.6/30 eBGP 13.1.1.6/30 64.1.128.0/17 13.1.1.2/30 64.1.0.0/16 eBGP 64.2.0.0/17 64.2.0.0/16 West-DC East-DC 64.1.0.12/32   AS 101 AS 102 IDs 64.1.0.0/16   64.2.0.0/16   64.1.0.0/16 64.2.0.0/16© 2010 Cisco and/or its affiliates. All rights reserved. 15
  • Routing DFZ Table•  What if ID address and LISP Locator address are in Mapping different databases?•  This creates a “level of System indirection” between ID and LOCATION in the network! Site 3 IPv4 Internet Site 1 Transit SP AS 200 12. 0/8 Clear Separation at the Network Layer:: AS 300 • who/what you are looking for 2 Site 13. 0/8 Tier 1 SP vs. … Commodity SP • how to best get there Locators 12.1.1.2/30 ID/Loc Split is common already! 12.1.1.6/30 13.1.1.6/30 Two basic approaches: 13.1.1.2/30 • Translations (e.g. NAT) vs. … West-DC East-DC • Tunnels (e.g. GRE, IPsec, MPLS) AS 101 64.1.0.12/32   Both approaches are limited to local scope AS 102 IDs 64.1.0.0/16   64.2.0.0/16   64.1.0.0/16 64.1.0.0/16 What is needed is Locator/ID Separation on a GLOBAL Scope.© 2010 Cisco and/or its affiliates. All rights reserved. 16
  • Routing DFZ Table •  Let’s scale the ID address LISP databases to 1010 and allow Mapping it to hold any prefix length (even /32’s and /128’s) System •  Let’s provide a mechanism to provide on-the-fly resolution Site 3 IPv4 Internet Site 1 of ID and locator (like DNS) •  High scale design, and ability Transit SP to change locator for fixed AS 200 ID enables Mobility! 12. 0/8 AS 300 Site 2 13. 0/8 Tier 1 SP Commodity SPNote: Loc/ID Split enables “Mobility” Locators 12.1.1.2/30But, can’t we handle “mobility” today, for example, 12.1.1.6/30 13.1.1.6/30with something like Global Site Selector (GSS)? 13.1.1.2/30   GSS uses DNS •  what do you do for all the applications that have hard-coded IP address? West-DC East-DC •  How do you move “existing flows” without rebuilding 64.1.0.12/32   TCP sessions? AS 101 AS 102   DNS is an “application” IDs 64.1.0.0/16   64.2.0.0/16   64.1.0.0/16 64.2.0.0/16 •  Using DNS for “routing” is never a good idea •  If DNS goes down, routing goes down. © 2010 Cisco and/or its affiliates. All rights reserved. 17
  • LISP changes the routing architecture to implement a level of indirection between a hosts IDENTITY and its LOCATION in the network LISP radical changes the current ROUTING Architecture •  Radical changes lead to DISRUPTION opportunities •  LISP allows both SPs and Enterprises to do remarkably different things than traditional approaches allow •  LISP enables NEW services (VPNs, IPv6, Mobility, “cloud”) in one, common, simple architecture© 2010 Cisco and/or its affiliates. All rights reserved. 18
  • © 2010 Cisco and/or its affiliates. All rights reserved. 19
  •   LISP Loc/ID Split namespaces EID a.a.a.0/24 b.b.b.0/24 c.c.c.0/24  RLOC   w.x.y.1 x.y.w.2 z.q.r.5 MS/MR   d.d.0.0/16 z.q.r.5 ‒  EID  (Endpoint  Iden>fier)  is  the  IP  address  of  a   EID  Space   host  –  just  as  it  is  today EID a.a.a.0/24 b.b.b.0/24  RLOC   w.x.y.1 x.y.w.2 c.c.c.0/24 z.q.r.5 ‒  RLOC  (Rou>ng  Locator)  is  the  IP  address  of   d.d.0.0/16 z.q.r.5 Non-­‐LISP   xTR   the  LISP  router  for  the  host Prefix        Next-­‐hop   EID-­‐to-­‐RLOC   w.x.y.1  e.f.g.h   mapping   ‒  EID-­‐to-­‐RLOC  mapping  is  the  distributed   x.y.w.2 z.q.r.5 z.q.r.5  e.f.g.h    e.f.g.h    e.f.g.h   architecture  that  maps  EIDs  to  RLOCs   PxTR   RLOC  Space     Network-­‐based  solu3on     Address  Family  agnos3c   xTR   xTR   EID  Space     No  host  changes     Incrementally  deployable     Minimal  configura3on   (support  LISP  and  non-­‐LISP)     No  DNS  changes     Support  for  mobility  © 2010 Cisco and/or its affiliates. All rights reserved. 20
  •   LISP “Level of Indirection” is analogous to a DNS lookup ‒  DNS resolves IP addresses for URL Answering the “WHO IS” question   [ who is lisp.cisco.com ] ? DNS DNS host Server Name-to-IP URL Resolution [153.16.5.29, 2610:D0:110C:1::3 ] ‒  LISP resolves locators for queried identities Answering the “WHERE IS” question   [ where is 2610:D0:110C:1::3 ] ? LISP LISP LISP Identity-to-locator Mapping router System Mapping Resolution [ locator is 128.107.81.169 ]© 2010 Cisco and/or its affiliates. All rights reserved. 21
  • ITR – Ingress Tunnel Router PI EID-prefix ‒  Receives packets from site- 32.1.1.0/24 xTR-1 facing interfaces 10.0.0.2 ETR Site 3 ITR packet flow IPv4 Internet ‒  Encap to remote LISP sites, or ETR 11.0.0.2 native-fwd to non-LISP sites S ITR32.1.1.32   xTR-2 LISP Site 1 ETR – Egress Tunnel Router ‒  Receives packets from core- facing interfaces 12.1.1.2/30 12.1.1.6/30 xTR-1 ETR ETR xTR-2 ‒  De-cap packets, deliver to ITR ITR local EIDs at site West-DC East-DC PI EID-prefix 64.1.0.0/16 D 64.1.0.12/32   64.2.0.0/16   LISP Site 2
  • Map-Cache Entry1 DNS entry: EID-prefix: 64.1.0.0/16 D.abc.com A 64.1.0.12 Locator-set: Notes: 12.1.1.2, priority: 1, weight: 50 This policy controlled PI EID-prefix 12.1.1.6, priority: 1, weight: 50 by the destination site ‒  The destination site controls its 32.1.1.0/24 xTR-1 3 ingress policy (active/active in 10.0.0.2 ETR Site 3 ITR IPv4 Internet this case) ETR 10.0.0.2 -> 12.1.1.6 11.0.0.2 5 ‒  5-tuple hash per-flow selects S ITR 32.1.1.32 -> 64.1.0.12 32.1.1.32 -> 64.1.0.12 4 RLOC for encapsulation 32.1.1.32   xTR-2 2 LISP Site 1 10.0.0.2 -> 12.1.1.6 32.1.1.32 -> 64.1.0.12 6 12.1.1.2/30 12.1.1.6/30 ETR ETR xTR-1 xTR-2 ITR ITR West-DC East-DC 32.1.1.32 -> 64.1.0.12 7 PI EID-prefix 64.1.0.0/16 D 64.1.0.12/32   64.2.0.0/16   LISP Site 2
  •   LISP Control Plane Provides On-Demand Mappings ‒  Control Plane is separate from data plane ‒  Map-Resolver and Map-Server (similar to DNS Resolver and DNS Server) ‒  LISP Control Plane Messages for EID-to-RLOC resolution ‒  Distributed databases and map-caches hold mappings© 2010 Cisco and/or its affiliates. All rights reserved. 24
  • MS – Map-Server ‒  LISP site ETRs register their Mapping System EID prefixes here; requires “lisp site” policy, authentication key MR MS PI EID-prefix 32.1.1.0/24 xTR-1 ETR 10.0.0.2 ‒  Receives Map-Requests via Site 3 ITR IPv4 Internet Mapping System; forwards ETR 11.0.0.2 Map-Requests to registered S ITR ETRs32.1.1.32   xTR-2 LISP Site 1 MR – Map-Resolver ‒  Receives Map-Request from 12.1.1.2/30 12.1.1.6/30 ITRs ETR ETR xTR-1 ITR ITR xTR-2 ‒  Forwards Map-Request to West-DC East-DC Map-Servers D ‒  Sends Negative Map-Replies PI EID-prefix 64.1.0.0/16 64.2.0.0/16   64.1.0.12/32   for Map-Requests for non-LISP LISP Site 2 sites
  • Mapping System Mapping-Database (ETR) MR MS ‒  EID-to-RLOC mappings in all PI EID-prefix 32.1.1.0/24 xTR-1 ETRs for local LISP site 10.0.0.2 ETR ‒  ETR authoritative for site EIDs Site 3 ITR IPv4 Internet sends Map-Replies to ITRs ETR 11.0.0.2 S ITR ‒  ETRs can tailor policy based32.1.1.32   xTR-2 LISP Site 1 on Map-Request source Map Cache (ITR) 12.1.1.2/30 ‒  Stores mappings for sites ITR 12.1.1.6/30 ETR ETR currently sending packets to xTR-1 xTR-2 ITR ITR ‒  Populated by receiving Map- West-DC East-DC Replies for its Map-Requests PI EID-prefix 64.1.0.0/16 D 64.1.0.12/32   64.2.0.0/16   ‒  ITRs must respect Map-Reply policy (TTLs, RLOC up/down LISP Site 2 status, RLOC priorities/weights
  •   Control Plane “EID Registration” ‒  Map-Register message Sent by ETR to MS to register its associated EID prefixes Specifies the RLOC(s) to be used by the MS when forwarding Map-Requests to the ETR   Control Plane “Data-triggered” mapping service ‒  Map-Request message Sent by an ITR when it needs for EID/RLOC mapping, to test an RLOC for reachability, or to refresh a mapping before TTL expiration (Solicit Map-Request (SMR)) ‒  Map-Reply message Sent by an ETR in response to a valid map-request to provide the EID/RLOC mapping and site ingress policy for the requested EID ‒  Map-Notify message Sent by Map-Server to ETR to acknowledge that its requested EID prefixes were registered successfully© 2010 Cisco and/or its affiliates. All rights reserved. 27
  • Other sites… 2 Mapping System MR MS PI EID-prefix Notes: 32.1.1.0/24 xTR-1 66.2.2.2 ETR 10.0.0.2 ‒  The ETR registers the EIDs Site 3 ITR IPv4 Internet 1 that it is authoritative for ETR 12.1.1.6-> 66.2.2.2 11.0.0.2 ‒  The MS is configured for the S ITR LISP Map-Register32.1.1.32   xTR-2 (udp 4342) site EIDs, and must have the LISP Site 1 SHA-2 64.1.0.0/16 same authentication key 12.1.1.2, 12.1.1.6 12.1.1.2/30 12.1.1.6/30 ETR ETR xTR-1 xTR-2 ITR ITR West-DC East-DC PI EID-prefix 64.1.0.0/16 D 64.1.0.12/32   64.2.0.0/16   LISP Site 2
  • 1 DNS entry: 11.0.0.2-> 66.2.2.2 3 Mapping System D.abc.com A 64.1.0.12 LISP ECM (udp 4342) MR MS 66.2.2.2 -> 12.1.1.6 4 PI EID-prefix LISP ECM Notes: 11.0.0.2 -> 64.1.0.12 32.1.1.0/24 xTR-1 66.2.2.2 (udp 4342) ETR Map-Request 10.0.0.2 (udp 4342) ‒  Encapsulated Control Message 11.0.0.2 -> 64.1.0.12 Site 3 ITR nonce IPv4 Internet Map-Request (ECM) header is used between (udp 4342) ETR 11.0.0.2 nonce an xTR and the Mapping S ITR System 32.1.1.32   xTR-2 32.1.1.32 -> 64.1.0.12 LISP Site 1 2 ‒  The IP address in the Map- 6 How do I get to 64.1.0.12? Map-Cache Entry Request (64.1.0.12 in this EID-prefix: 64.1.0.0/16 case) is the host that the ITR is Locator-set: 5 12.1.1.6 -> 11.0.0.2 12.1.1.2, priority: 1, weight: 50 trying to reach. 12.1.1.2/30 Map-Reply 12.1.1.6/30 12.1.1.6, priority: 1, weight: 50 (udp 4342) ETR xTR-1 ETR xTR-2 ‒  The Map-Reply includes the nonce ITR 64.1.0.0/16 ITR entire prefix (64.1.0.0/16 in West-DC [1, 50] 12.1.1.2 East-DC this case) covering the 12.1.1.6 [1, 50] D requested host. PI EID-prefix 64.1.0.0/16 64.1.0.12/32   64.2.0.0/16   LISP Site 2
  • 2 11.0.0.2-> 66.2.2.2 Mapping System LISP ECM (udp 4342) MR MS 66.2.2.2 -> 11.0.0.2 3 PI EID-prefix LISP ECM 11.0.0.2 -> 64.1.0.12 (udp 4342) 32.1.1.0/24 xTR-1 Map-Request 66.2.2.2 10.0.0.2 ETR (udp 4342) 11.0.0.2 -> 64.1.0.12 Site 3 ITR nonce IPv4 Internet Map-Request (udp 4342) ETR 11.0.0.2 nonce S ITR32.1.1.32   xTR-2 LISP Site 1 Notes: 1 12.1.1.6 -> 11.0.0.2 ‒  Solicit Map Request is sent in 12.1.1.2/30 Map-Request 12.1.1.6/30 4 order to inform ITR’s that their (udp 4342) ETR ETR Map-Reply sent… xTR-1 Nonce ITR ITR xTR-2 12.1.1.6 -> 11.0.0.2 Map-Cache might be out of 64.1.0.12/32 West-DCMap Reqst Solicit Map-Reply East-DC date (udp 4342) 64.1.0.12 has nonce PI EID-prefix 64.1.0.0/16 D moved away… 64.1.0.12/32   64.2.0.0/16   64.1.0.12/32 12.1.1.2 [1, 50] 12.1.1.6 [1, 50] LISP Site 2 © 2010 Cisco and/or its affiliates. All rights reserved. 30
  • © 2010 Cisco and/or its affiliates. All rights reserved. 31
  • 1.  Efficient Multi-Homing 2.  IPv6 Transition Support 3.  Efficient Virtualization/VPN 4.  Data Center/Host Mobility 5.  LISP Mobile-Node These ‘core’ Use-Cases highlight functionality that is integrated in LISP. All use-case :: multi-homing, v6 transition, virtualization, and mobility work together as well© 2010 Cisco and/or its affiliates. All rights reserved. 32
  • Data Center/Host Mobility  Needs: Legacy Site Legacy Site Legacy Site ­  Host-Mobility extending subnets and across subnets LISP Site ­  Move detection, dynamic EID-to-RLOC PxTR mappings, traffic redirection Mapping DB xTR  LISP Solution: IP  Network ­  LISP for across subnets moves ­  Host IP (/32) remains the same VM move  Benefits: West East ­  VM/OS agnostic, seamless, integrated, DC VM VM DC a.b.c.1 global workload mobility (cloud bursting) a.b.c.1 ­  Direct Path after move (no triangulation) ­  No IP address changes across move   Example: ­  Connections survive across moves ­  No routing re-convergence or DNS updates VXNet is providing Disaster Recovery and Workload mobility solutions to NYC financial institutions ­  ARP elimination© 2010 Cisco and/or its affiliates. All rights reserved. 33
  • Moves With LAN Extension Moves Without LAN Extension LISP Site LISP Site Non- XTR   LISP Site XTR   DR Location Mapping DB Mapping DB or Cloud IP Network Provider DC Internet or Shared WAN LAN Extension LISP-­‐VM  (XTR)   LISP-­‐VM  (XTR)   West-DC East-DC West-DC East-DC  Rou3ng  for  Extended  Subnets    IP  Mobility  Across  Subnets   Active-Active Data Centers Disaster Recovery Distributed Data Centers Cloud Bursting  Applica3on  Members  Distributed    Applica3on  Members  In  One  Loca3on   Broadcasts across sites© 2010 Cisco and/or its affiliates. All rights reserved. 34
  • 1.  Detect the host move a)  For any host, without agents on the host or protocols b)  Without dependence on any hypervisor 2.  Register the new host location with the Mapping System 3.  Notify other xTRs/PITRs of the move a)  Update routing tables at old sites b)  Update LISP Map-Caches© 2010 Cisco and/or its affiliates. All rights reserved. 35
  • © 2010 Cisco and/or its affiliates. All rights reserved. 36
  • ip lisp itr-etr ip lisp itr-etrip lisp database-mapping 64.1.0.0/16 12.1.1.2 pri 1 wei 50 ip lisp database-mapping 64.1.0.0/16 12.1.1.2 pri 1 wei 50 Mapping Systemip lisp database-mapping 64.1.0.0/16 12.1.1.6 pri 1 wei 50 ip lisp database-mapping 64.1.0.0/16 12.1.1.6 pri 1 wei 50ip lisp itr map-resolver 66.2.2.2 ip lisp itr map-resolver 66.2.2.2 MR MSip lisp PI EID-prefix etr map-server 66.2.2.2 key some-key-DC ip lisp etr map-server 66.2.2.2 key some-key-DC 32.1.1.0/24lisp dynamic-eid WEBINAR_MOB_ASM xTR-1 66.2.2.2 lisp dynamic-eid WEBINAR_MOB_ASM 10.0.0.2 The 64.1.0.0/24 from the database-mapping 64.1.0.0/24 12.1.1.2 pri 1 wei 50 ETR database-mapping 64.1.0.0/24 12.1.1.2 pri 1 wei 50 database-mapping 64.1.0.0/24 12.1.1.6 pri 1 wei 50 map-notify-group 239.1.1.1 Site 3 ITR IPv4 Internet database-mapping 64.1.0.0/24 12.1.1.6 pri 1 wei 50 map-notify-group 239.1.1.1 entire /16 is configured as able to “roam” in this case ETRinterface vlan 100 32.1.1.32   11.0.0.2 interface vlan 100 ITR ip address 64.1.0.2/24 ip address 64.1.0.3/24 lisp mobility WEBINAR_MOB_ASM xTR-2 lisp mobility WEBINAR_MOB_ASM ip proxy-arp LISP Site 1 ip proxy-arp hsrp 101 hsrp 101 mac-address 0000.0e1d.010c mac-address 0000.0e1d.010c ip 64.1.0.1 ip 64.1.0.1 12.1.1.2/30 12.1.1.6/30 13.1.1.6/30 13.1.1.2/30 ETR ETR ETR ETR xTR-1 xTR-2 xTR-3 xTR-4 ITR ITR ITR ITR West-DC 64.1.0.0/24 64.2.0.0/24 East-DC 64.1.0.0/16 64.1.0.12/32   64.1.0.12/32   64.2.0.0/16   LISP Site DC-1 LISP Site DC-2
  • ip lisp itr-etr ip lisp itr-etr ip lisp database-mapping 64.2.0.0/16 13.1.1.2 priSystem 50 Mapping 1 wei ip lisp database-mapping 64.2.0.0/16 13.1.1.2 pri 1 wei 50 ip lisp database-mapping 64.2.0.0/16 13.1.1.6 pri 1 wei 50 ip lisp database-mapping 64.2.0.0/16 13.1.1.6 pri 1 wei 50 ip lisp itr map-resolver 66.2.2.2 MR ip MS lisp itr map-resolver 66.2.2.2 PI ip lisp etr map-server 66.2.2.2 key some-key-DC EID-prefix ip lisp etr map-server 66.2.2.2 key some-key-DC 32.1.1.0/24 xTR-1 lisp dynamic-eid WEBINAR_MOB_ASM 66.2.2.2 lisp dynamic-eid WEBINAR_MOB_ASMThe 64.1.0.0/24 from the 10.0.0.2entire /16 is configured as database-mapping 64.1.0.0/24 13.1.1.2 pri 1 wei 50 ETR database-mapping 64.1.0.0/24 13.1.1.2 pri 1 wei 50able to “roam” in this case database-mapping 64.1.0.0/24 13.1.1.6 pri 1 wei 50 Site 3 ITR map-notify-group 239.1.1.2 IPv4 Internet database-mapping 64.1.0.0/24 13.1.1.6 pri 1 wei 50 map-notify-group 239.1.1.2 ETR 11.0.0.2 32.1.1.32   interface vlan 100 ITR interface vlan 100 ip address 64.2.0.2/24 ip address 64.2.0.3/24 xTR-2 lisp mobility WEBINAR_MOB_ASM lisp mobility WEBINAR_MOB_ASM ip proxy-arp LISP Site 1 ip proxy-arp hsrp 102 hsrp 102 mac-address 0000.0e1d.010c mac-address 0000.0e1d.010c ip 64.2.0.1 ip 64.2.0.1 12.1.1.2/30 12.1.1.6/30 13.1.1.6/30 13.1.1.2/30 ETR ETR ETR ETR xTR-1 xTR-2 xTR-3 xTR-4 ITR ITR ITR ITR West-DC 64.1.0.0/24 64.2.0.0/24 East-DC 64.1.0.0/16 64.1.0.12/32   64.1.0.12/32   64.2.0.0/16   LISP Site DC-1 LISP Site DC-2
  • ip lisp itr-etr ip lisp itr-etrip lisp database-mapping 64.1.0.0/16 12.1.1.2 pri 1 wei 50 Mapping System ip lisp database-mapping 64.2.0.0/16 13.1.1.2 pri 1 wei 50ip lisp database-mapping 64.1.0.0/16 12.1.1.6 pri 1 wei 50 ip lisp database-mapping 64.2.0.0/16 13.1.1.6 pri 1 wei 50ip lisp itr map-resolver 66.2.2.2 MR ip MS lisp itr map-resolver 66.2.2.2ip lisp PI EID-prefix etr map-server 66.2.2.2 key some-key-DC ip lisp etr map-server 66.2.2.2 key some-key-DC 32.1.1.0/24lisp dynamic-eid WEBINAR_MOB_ASM xTR-1 66.2.2.2 lisp dynamic-eid WEBINAR_MOB_ASM 10.0.0.2 database-mapping 64.1.0.0/24 12.1.1.2 pri 1 wei 50 ETR database-mapping 64.1.0.0/24 13.1.1.2 pri 1 wei 50 database-mapping 64.1.0.0/24 12.1.1.6 pri 1 wei 50 map-notify-group 239.1.1.1 Site 3 ITR IPv4 Internet database-mapping 64.1.0.0/24 13.1.1.6 pri 1 wei 50 map-notify-group 239.1.1.2 ETRinterface vlan 100 32.1.1.32   11.0.0.2 interface vlan 100 ITR ip address 64.1.0.2/24 ip address 64.2.0.3/24 lisp mobility WEBINAR_MOB_ASM xTR-2 lisp mobility WEBINAR_MOB_ASM ip proxy-arp LISP Site 1 ip proxy-arp hsrp 101 hsrp 102 mac-address 0000.0e1d.010c mac-address 0000.0e1d.010c ip 64.1.0.1 ip 64.2.0.1 12.1.1.2/30 12.1.1.6/30 13.1.1.6/30 13.1.1.2/30 ETR ETR ETR ETR xTR-1 xTR-2 xTR-3 xTR-4 ITR ITR ITR ITR West-DC 64.1.0.0/24 64.2.0.0/24 East-DC 64.1.0.0/16 64.1.0.12/32   64.1.0.12/32   64.2.0.0/16   LISP Site DC-1 LISP Site DC-2
  • Mapping System router lisp site Site1 MR MS authentication-key some-key-1 PI EID-prefix eid-prefix 32.1.1.0/24 32.1.1.0/24 xTR-1 66.2.2.2 site DC-1 10.0.0.2 authentication-key some-key-DC ETR eid-prefix 64.1.0.0/16 accept-more-specifics Site 3 ITR IPv4 Internet ! eid-prefix 64.2.0.0/16 ETR 11.0.0.2 32.1.1.32   ITR xTR-2 LISP Site 1router lisp database-mapping 32.1.1.0/24 10.0.0.2 priority 1 weight 50 database-mapping 32.1.1.0/24 11.0.0.2 priority 1 weight 50 ipv4 itr ipv4 etr ipv4 itr map-resolver 66.2.2.2 12.1.1.2/30 12.1.1.6/30 13.1.1.6/30 ipv4 etr map-server 66.2.2.2 key some-key-1 13.1.1.2/30 ETR ETR ETR ETR xTR-1 xTR-2 xTR-3 xTR-4 ITR ITR ITR ITR West-DC 64.1.0.0/24 64.2.0.0/24 East-DC 64.1.0.0/16 64.1.0.12/32   64.1.0.12/32   64.2.0.0/16   LISP Site DC-1 LISP Site DC-2
  • 6 64.1.0.0/16 – 12.1.1.2/12.1.1.6 64.2.0.0/16 – 13.1.1.2/13.1.1.6 64.1.0.12/32 – 13.1.1.2/13.1.1.6 Mapping System MR MS PI EID-prefix 7 32.1.1.0/24 xTR-1 Map-Notify 66.2.2.2 5 64.1.0.12/32 10.0.0.2 Map-Register ETR 64.1.0.12/32 Site 3 ITR 13.1.1.2/13.1.1.6 IPv4 Internet 13.1.1.2/13.1.1.6 ETR 11.0.0.2 32.1.1.32   ITR xTR-2 LISP Site 1 2 4 Routing Table: Routing Table: 10 64.2.0.0/24 – Local 64.2.0.0/24 – LocalRouting Table: 64.1.0.12/32 – Local 64.1.0.12/32 – Local64.1.0.0/24 – Local64.1.0.12/32 – Null0 12.1.1.2/30 12.1.1.6/30 13.1.1.6/30 13.1.1.2/30 ETR ETR ETR ETR xTR-1 xTR-2 xTR-4 ITR 9 ITR xTR-3 ITR 3 ITR West-DC 64.1.0.0/24 64.2.0.0/24 East-DC 1 64.1.0.0/16 64.1.0.12/32   64.1.0.12/32   64.2.0.0/16   Map-Notify Map-Notify 64.1.0.12/32 Routing Table: LISP Site DC-2 64.1.0.12/32 LISP Site DC-1 64.1.0.0/24 – Local 13.1.1.2/13.1.1.6 13.1.1.2/13.1.1.6 8 64.1.0.12/32 – Null0
  • 1.  ITRs, PITRs with cached mappings continue to send traffic to the old locators until updated Old DC xTR site knows the host has moved (/32 Null0 route) Mapping System MR MS 2.  Old DC xTR sends Solicit Map PI EID-prefix Request (SMR) messages to any 32.1.1.0/24 xTR-1 66.2.2.2 encapsulators sending traffic to “it” ETR 10.0.0.2 for the moved host Site 3 ITR 3 IPv4 Internet 3.  SMR causes ITR to initiate a new 1 5 map-r ETR 32.1.1.32   ITR 11.0.0.2 map-request/map-reply process eques xTR-2 4.  Map-Reply updates map-cache LISP Site 1 2 with new location t64.1.0.0/16 – 12.1.1.2/12.1.1.664.2.0.0/16 – 13.1.1.2/13.1.1.6 5.  Traffic now flows to the HOST at its64.1.0.12/32 – 13.1.1.2/13.1.1.6 NEW location4 12.1.1.2/30 12.1.1.6/30 13.1.1.6/30 13.1.1.2/30 ETR ETR ETR ETR xTR-1 xTR-2 xTR-3 xTR-4 ITR ITR ITR ITR West-DC 64.1.0.0/24 64.2.0.0/24 East-DC 64.1.0.0/16 64.1.0.12/32   64.1.0.12/32   64.2.0.0/16   LISP Site DC-1 LISP Site DC-2
  • © 2010 Cisco and/or its affiliates. All rights reserved. 43
  •   Not necessarily for moving workloads: Can be solved with IP mobility solutions: LISP Host Mobility Moving Workloads Hypervisor Hypervisor Control Hypervisor Traffic (routable) IP Network   Application High Availability  Distributed Clusters e.g. Node Discovery & Heartbeats in Clustered Applications Distributed App (GeoCluster) OS OS OS Non-IP application traffic (heartbeats) LAN Extension (OTV) IP Network© 2010 Cisco and/or its affiliates. All rights reserved. 44
  •   A subnet usually implies location  Yet we use LAN extensions to stretch LISP site subnets across locations XTR   Location semantics of subnets are lost  Traditional routing relies on the location IP Network semantics of the subnet Can’t tell if a server is at the East or West location of the subnet LAN Extension  More granular (host level) information is required West-DC East-DC LISP provides host level location semantics© 2010 Cisco and/or its affiliates. All rights reserved. 45
  • ip lisp itr-etr ip lisp itr-etrip lisp database-mapping 64.1.0.0/16 12.1.1.2 pri 1 wei 50 ip lisp database-mapping 64.1.0.0/16 12.1.1.2 pri 1 wei 50 Mapping Systemip lisp database-mapping 64.1.0.0/16 12.1.1.6 pri 1 wei 50 ip lisp database-mapping 64.1.0.0/16 12.1.1.6 pri 1 wei 50ip lisp itr map-resolver 66.2.2.2 ip lisp itr map-resolver 66.2.2.2 MR MSip lisp etr map-server 66.2.2.2 key some-key-DC ip lisp etr map-server 66.2.2.2 key some-key-DC PI EID-prefixlisp dynamic-eid 32.1.1.0/24 WEBINAR_MOB_ESM xTR-1 66.2.2.2 lisp dynamic-eid WEBINAR_MOB_ESM 10.0.0.2 database-mapping 64.1.0.0/24 12.1.1.2 pri 1 wei 50 ETR database-mapping 64.1.0.0/24 12.1.1.2 pri 1 wei 50 The 64.1.0.0/24 from the entire /16 is configured as database-mapping 64.1.0.0/24 12.1.1.6 pri 1 wei 50 map-notify-group 239.1.1.1 Site 3 ITR IPv4 Internet database-mapping 64.1.0.0/24 12.1.1.6 pri 1 wei 50 map-notify-group 239.1.1.1 able to “roam” in this case ETRinterface vlan 100 11.0.0.2 interface vlan 100 32.1.1.32   ITR ip address 64.1.0.2/24 ip address 64.1.0.3/24 lisp mobility WEBINAR_MOB_ESM xTR-2 lisp mobility WEBINAR_MOB_ESM The 64.1.0.0/24 from the entire /16 lisp extended-subnet-mode lisp extended-subnet-mode is on the interface as well. This LISP Site 1 hsrp 101 hsrp 101 will be “extended” to the other DC ip 64.1.0.1 ip 64.1.0.1 12.1.1.2/30 12.1.1.6/30 13.1.1.6/30 13.1.1.2/30 LAN Extension (OTV) ETR ETR ETR ETR xTR-1 xTR-2 xTR-3 xTR-4 ITR ITR ITR ITR West-DC 64.1.0.0/24 64.1.0.0/24 East-DC 64.1.0.0/16 64.1.0.12/32   64.1.0.12/32   64.2.0.0/16   LISP Site DC-1 LISP Site DC-2
  • ip lisp itr-etr ip lisp itr-etr ip lisp database-mapping 64.2.0.0/16 13.1.1.2 priSystem 50 Mapping 1 wei ip lisp database-mapping 64.2.0.0/16 13.1.1.2 pri 1 wei 50 ip lisp database-mapping 64.2.0.0/16 13.1.1.6 pri 1 wei 50 ip lisp database-mapping 64.2.0.0/16 13.1.1.6 pri 1 wei 50 ip lisp itr map-resolver 66.2.2.2 MR ip MS lisp itr map-resolver 66.2.2.2 PI ip lisp etr map-server 66.2.2.2 key some-key-DC EID-prefix ip lisp etr map-server 66.2.2.2 key some-key-DC 32.1.1.0/24 xTR-1 lisp dynamic-eid WEBINAR_MOB_ESM 66.2.2.2 lisp dynamic-eid WEBINAR_MOB_ESM 10.0.0.2 ETR 3.7 database-mapping 64.1.0.0/24 13.1.1.2 pri 1 wei 50 database-mapping 64.1.0.0/24 13.1.1.2 pri 1 wei 50 database-mapping 64.1.0.0/24 13.1.1.6 pri 1 wei 50 Site 3 ITR map-notify-group 239.1.1.1 IPv4 Internet database-mapping 64.1.0.0/24 13.1.1.6 pri 1 wei 50 map-notify-group 239.1.1.1 ETR 11.0.0.232.1.1.32   interface vlan 100 ITR interface vlan 100 ip address 64.1.0.4/24 ip address 64.1.0.5/24 xTR-2 lisp mobility WEBINAR_MOB_ESM lisp mobility WEBINAR_MOB_ESM Notice that a 64.1.0.0/24 is lisp extended-subnet-mode LISP Site 1 lisp extended-subnet-mode “extended” from the other hsrp 101 hsrp 101 DC in this case. ip 64.1.0.1 ip 64.1.0.1 12.1.1.2/30 12.1.1.6/30 13.1.1.6/30 13.1.1.2/30 LAN Extension (OTV) ETR ETR ETR ETR xTR-1 xTR-2 xTR-3 xTR-4 ITR ITR ITR ITR West-DC 64.1.0.0/24 64.1.0.0/24 East-DC 64.1.0.0/16 64.1.0.12/32   64.1.0.12/32   64.2.0.0/16   LISP Site DC-1 LISP Site DC-2
  • ip lisp itr-etr ip lisp itr-etrip lisp database-mapping 64.1.0.0/16 12.1.1.2 pri 1 wei 50 Mapping System ip lisp database-mapping 64.2.0.0/16 13.1.1.2 pri 1 wei 50ip lisp database-mapping 64.1.0.0/16 12.1.1.6 pri 1 wei 50 ip lisp database-mapping 64.2.0.0/16 13.1.1.6 pri 1 wei 50ip lisp itr map-resolver 66.2.2.2 MR ip MS lisp itr map-resolver 66.2.2.2ip lisp etr map-server 66.2.2.2 key some-key-DC PI EID-prefix ip lisp etr map-server 66.2.2.2 key some-key-DClisp dynamic-eid 32.1.1.0/24 WEBINAR_MOB_ESM xTR-1 66.2.2.2 lisp dynamic-eid WEBINAR_MOB_ESM 10.0.0.2 database-mapping 64.1.0.0/24 12.1.1.2 pri 1 wei 50 ETR database-mapping 64.1.0.0/24 13.1.1.2 pri 1 wei 50 database-mapping 64.1.0.0/24 12.1.1.6 pri 1 wei 50 map-notify-group 239.1.1.1 Site 3 ITR IPv4 Internet database-mapping 64.1.0.0/24 13.1.1.6 pri 1 wei 50 map-notify-group 239.1.1.1 ETRinterface vlan 100 11.0.0.2 32.1.1.32   ITR interface vlan 100 ip address 64.1.0.2/24 ip address 64.1.0.5/24 lisp mobility WEBINAR_MOB_ESM xTR-2 lisp mobility WEBINAR_MOB_ESM lisp extended-subnet-mode LISP Site 1 lisp extended-subnet-mode hsrp 101 hsrp 101 ip 64.1.0.1 ip 64.1.0.1 12.1.1.2/30 12.1.1.6/30 13.1.1.6/30 13.1.1.2/30 LAN Extension (OTV) ETR ETR ETR ETR xTR-1 xTR-2 xTR-3 xTR-4 ITR ITR ITR ITR West-DC 64.1.0.0/24 64.1.0.0/24 East-DC 64.1.0.0/16 64.1.0.12/32   64.1.0.12/32   64.2.0.0/16   LISP Site DC-1 LISP Site DC-2
  • router lisp site Site1 Mapping System authentication-key some-key-1 eid-prefix 32.1.1.0/24 MR MS site DC PI EID-prefix authentication-key some-key-DC 32.1.1.0/24 xTR-1 66.2.2.2 eid-prefix 64.1.0.0/16 accept-more-specifics 10.0.0.2 eid-prefix 64.2.0.0/16 ETR ! Site 3 ITR IPv4 Internet ETR 11.0.0.2 32.1.1.32   ITR xTR-2 LISP Site 1router lisp database-mapping 32.1.1.0/24 10.0.0.2 priority 1 weight 50 database-mapping 32.1.1.0/24 11.0.0.2 priority 1 weight 50 ipv4 itr ipv4 etr ipv4 itr map-resolver 66.2.2.2 12.1.1.2/30 12.1.1.6/30 13.1.1.6/30 ipv4 etr map-server 66.2.2.2 key some-key-1 13.1.1.2/30 LAN Extension (OTV) ETR ETR ETR ETR xTR-1 xTR-2 xTR-3 xTR-4 ITR ITR ITR ITR West-DC 64.1.0.0/24 64.1.0.0/24 East-DC 64.1.0.0/16 64.1.0.12/32   64.1.0.12/32   64.2.0.0/16   LISP Site DC-1 LISP Site DC-2
  • Note: 6 64.1.0.0/16 – 12.1.1.2/12.1.1.6 •  Null0 host routes indicate the 12.1.1.2/12.1.1.6 64.1.0.12/32 – 13.1.1.2/13.1.1.6 host is “away” 64.2.0.0/16 – 13.1.1.2/13.1.1.6 •  64.1.0.0/24 is configured as the dynamic-EID range Mapping System MR MS PI EID-prefix 32.1.1.0/24 xTR-1 66.2.2.2 5 10.0.0.2 Map-Register ETR 64.1.0.12/32 Site 3 ITR IPv4 Internet 13.1.1.2/13.1.1.6 ETR 11.0.0.2 32.1.1.32   ITR xTR-2 LISP Site 1 2 4 4 Routing Table: Routing Table:Routing Table: 64.1.0.0/24 – Local 64.1.0.0/24 – Local64.1.0.0/24 – Local 64.1.0.12/32 – Null0 Local 64.1.0.12/32 – Null0 Local64.1.0.12/32 – Local Null0 12.1.1.2/30 12.1.1.6/30 13.1.1.6/30 13.1.1.2/30 LAN Extension (OTV) ETR ETR ETR ETR xTR-1 xTR-2 xTR-4 ITR ITR xTR-3 ITR 3 ITR West-DC 64.1.0.0/24 64.1.0.0/24 1 East-DC 64.1.0.12/32   64.1.0.0/16 64.1.0.12/32   64.2.0.0/16   Map-Notify Routing Table: Map-Notify 64.1.0.12/32 64.1.0.0/24 –LISP Site DC-2 Local 64.1.0.12/32 LISP Site DC-1 13.1.1.2/13.1.1.6 4 64.1.0.12/32 – Local Null0 13.1.1.2/13.1.1.6
  • 1.  ITRs, PITRs with cached mappings continue to send traffic to the old locators until updated Old DC xTR site knows the host has moved (/32 Null0 route) Mapping System MR MS 2.  Old DC xTR sends Solicit Map PI EID-prefix Request (SMR) messages to any 32.1.1.0/24 xTR-1 66.2.2.2 encapsulators sending traffic to “it” ETR 10.0.0.2 for the moved host Site 3 ITR 3 IPv4 Internet 3.  SMR causes ITR to initiate a new 1 5 map-r ETR 32.1.1.32   ITR 11.0.0.2 map-request/map-reply process eques xTR-2 4.  Map-Reply updates map-cache LISP Site 1 2 with new location t64.1.0.0/16 – 12.1.1.2/12.1.1.6 13.1.1.2/13.1.1.664.1.0.12/32 – 12.1.1.2/12.1.1.6 5.  Traffic now flows to the HOST at its64.2.0.0/16 – 13.1.1.2/13.1.1.6 NEW location4 12.1.1.2/30 12.1.1.6/30 13.1.1.6/30 13.1.1.2/30 ETR ETR ETR ETR xTR-1 xTR-2 xTR-3 xTR-4 ITR ITR ITR ITR West-DC 64.1.0.0/24 64.1.0.0/24 East-DC 64.1.0.0/16 64.1.0.12/32   64.1.0.12/32   64.2.0.0/16   LISP Site DC-1 LISP Site DC-2
  • © 2010 Cisco and/or its affiliates. All rights reserved. 52
  • Customer-­‐A   Customer-­‐A   Site  2   CE2 CE4 Site  4   ITR/ETR   ITR/ETR   PE2 PE4 Customer-­‐A   MPLS-­‐VPN   Customer-­‐A   Customer-­‐A   Site  1   PE1 MPLS Core PE3 CE3 Site  3   CE1 ITR/ETR   ITR/ETR   PE5 PE6 MS/MR   MS/MR   CE5 CE6 CE7 CE8 LAN Extension (OTV) Blue/DC  1   ITR/ETR   ITR/ETR   Blue/DC  2   172.17.0.0/16   (Loca>on  1)   (Loca>on  2)   172.18.0.0/16   172.17.0.0/24 DYNAMIC EID© 2010 Cisco and/or its affiliates. All rights reserved. 53
  • IOS   router  lisp    eid-­‐table  default  instance-­‐id  0   Customer-­‐A      database-­‐mapping  172.16.1.0/24  10.1.1.2  pri  1  wei  100   Customer-­‐A   Site  2      exit   Site  4   CE2 CE4  !   ITR/ETR    ipv4  itr   ITR/ETR   PE2 PE4 IOS    ipv4  etr    ipv4  itr  map-­‐resolver  10.1.5.1   router  lisp   RLOC GE0/0/0 Customer-­‐A   10.1.1.2/30  ipv4  etr  map-­‐server  10.1.5.1  key  s3cr3t      !   MPLS-­‐VPN    ipv4  itr  map-­‐resolver  10.1.6.1      site  DCs   Customer-­‐A    ipv4  etr  map-­‐server  10.1.6.1  key  s3cr3t   Customer-­‐A        authen>ca>on-­‐key  DCs3cr3t   Site  1   PE1 !   MPLS Core PE3 Site  3        eid-­‐prefix  172.17.0.0/16  accept-­‐more-­‐specifics   CE3 CE1      eid-­‐prefix  172.18.0.0/16   ITR/ETR        exit   ITR/ETR   EID 172.16.1.0/24 RLOC GE0/0/0 RLOC GE0/0/0    !   PE5 PE6 10.1.5.1 10.1.6.1  site  Site-­‐1        authen>ca>on-­‐key  s3cr3t   MS/MR   MS/MR        eid-­‐prefix  172.16.1.0/24   CE5 CE6 CE7 CE8    exit      !   LAN Extension (OTV) -­‐-­‐<more  sites>-­‐-­‐-­‐   Blue/DC  1   ITR/ETR   ITR/ETR   Blue/DC  2map-­‐server      ipv4     172.17.0.0/16   (Loca>on  1)   (Loca>on  2) ap-­‐resolver      ipv4  m   172.18.0.0/16      exit    !   172.17.0.0/24 DYNAMIC EID© 2010 Cisco and/or its affiliates. All rights reserved. 54
  • NX-­‐OS   ip  lisp  itr-­‐etr   ip  lisp  database-­‐mapping  172.18.0.0/16  10.2.6.1  p  1  w  50   NX-­‐OS   ip  lisp  database-­‐mapping  172.18.0.0/16  10.2.6.5  p  1  w  50   ip  lisp  itr-­‐etr     ip  lisp  database-­‐mapping  172.17.0.0/16  10.2.5.1  p  1  w  50   ip  lisp  database-­‐mapping  172.17.0.0/16  10.2.5.5  p  1  w  50   ip  lisp  itr  map-­‐resolver  10.1.5.1       ip  lisp  itr  map-­‐resolver  10.1.6.1     ip  lisp  etr  map-­‐server  10.1.5.1  key  DCs3cr3t   ip  lisp  itr  map-­‐resolver  10.1.5.1     ip  lisp  etr  map-­‐server  10.1.6.1  key  DCs3cr3t     ip  lisp  itr  map-­‐resolver  10.1.6.1     ip  lisp  etr  map-­‐server  10.1.5.1  key  DCs3cr3t     Customer-­‐A   lisp  dynamic-­‐eid  CUST-­‐A-­‐ROAM   Customer-­‐A   Site  2   ip  lisp  etr  map-­‐server  10.1.6.1  key  DCs3cr3t     CE2    database-­‐mapping  172.17.0.0/24  1Site  4   p  1  w  50   CE4 0.2.6.1        database-­‐mapping  172.17.0.0/24  10.2.6.5  p  1  w  50   ITR/ETR   lisp  dynamic-­‐eid  CUST-­‐A-­‐ROAM   ITR/ETR      database-­‐mapping  172.17.0.0/24  10.2.5.1  p  1  w  50      map-­‐no>fy-­‐group  239.1.1.1   PE2 PE4      database-­‐mapping  172.17.0.0/24  10.2.5.5  p  1  w  50   interface  vlan  100      map-­‐no>fy-­‐group  239.1.1.1   Customer-­‐A      ip  address  172.17.0.4/24  (or  172.17.0.5/24)     MPLS-­‐VPN   interface  vlan  100      lisp  mobility    CUST-­‐A-­‐ROAM      ip  address  172.17.0.2/24  (or  172.17.0.3/24)      lisp  extended-­‐subnet-­‐mode   Customer-­‐A      hsrp  101   Customer-­‐A   Site  1   PE1 MPLS Core    lisp  mobility    CUST-­‐A-­‐ROAM      lisp  extended-­‐subnet-­‐mode   Site  3   PE3        preempt  delay  reload  300  (one  side  only)   CE3 CE1        priority  130  (or  120)      hsrp  101   ITR/ETR          preempt  delay  reload  300  (one  side  only)          ip  172.17.0.1   ITR/ETR          priority  130  (or  120)   PE5 PE6        ip  172.17.0.1   RLOC-A RLOC-B RLOC-C RLOC-D MS/MR   10.2.5.1 10.2.5.5 MS/MR   10.2.6.1 10.2.6.5 CE5 CE6 CE7 CE8 LAN Extension (OTV) Blue/DC  1   ITR/ETR   ITR/ETR   Blue/DC  2   172.17.0.0/16   (Loca>on  1)   (Loca>on  2)   172.18.0.0/16   172.17.0.0/24 DYNAMIC EID© 2010 Cisco and/or its affiliates. All rights reserved. 55
  • Customer-­‐A   Customer-­‐A   Site  2   CE2 CE4 Site  4   ITR/ETR   ITR/ETR   PE2 PE4 RLOC GE0/0/0 Customer-­‐A   10.1.1.2/30 MPLS-­‐VPN   Customer-­‐A   Customer-­‐A   Site  1   PE1 MPLS Core PE3 CE3 Site  3   CE1 ITR/ETR   ITR/ETR   EID 172.16.1.0/24 PE5 PE6 map-cache EID-­‐prefix:    172.17.0.12/32   RLOC-A RLOC-B RLOC-C RLOC-D MS/MR   10.2.5.1 10.2.5.5 MS/MR   10.2.6.1 10.2.6.5 Locator-­‐set:     CE5 CE6 CE7 CE8    10.2.5.1,  priority:  1,  weight:  50      10.2.5.5,  priority:  1,  weight:  50   LAN Extension (OTV) Blue/DC  1   ITR/ETR   ITR/ETR   Blue/DC  2   172.17.0.0/16   (Loca>on  1)   (Loca>on  2)   172.18.0.0/16   172.17.0.0/24 172.17.0.12/32   DYNAMIC EID the server is here© 2010 Cisco and/or its affiliates. All rights reserved. 56
  • Customer-­‐A   Customer-­‐A   Site  2   CE2 CE4 Site  4   ITR/ETR   ITR/ETR   PE2 PE4 RLOC GE0/0/0 Customer-­‐A   10.1.1.2/30 MPLS-­‐VPN   Customer-­‐A   Customer-­‐A   Site  1   PE1 MPLS Core PE3 CE3 Site  3   CE1 ITR/ETR   ITR/ETR   EID 172.16.1.0/24 PE5 PE6 map-cache EID-­‐prefix:    172.17.0.12/32   RLOC-A RLOC-B RLOC-C RLOC-D MS/MR   10.2.5.1 10.2.5.5 MS/MR   10.2.6.1 10.2.6.5 Locator-­‐set:     CE5 CE6 CE7 CE8    10.2.5.1,  priority:  1,  weight:  50   10.2.6.1,      10.2.5.5,  priority:  1,  weight:  50   10.2.6.5,   LAN Extension (OTV) Blue/DC  1   ITR/ETR   ITR/ETR   Blue/DC  2   172.17.0.0/16   (Loca>on  1)   (Loca>on  2)   172.18.0.0/16   172.17.0.0/24 DYNAMIC EID172.17.0.12/32   the server moves here© 2010 Cisco and/or its affiliates. All rights reserved. 57
  • © 2010 Cisco and/or its affiliates. All rights reserved. 58
  •   Cisco Releases Cisco LISP Releases: http://lisp.cisco.com NX-OS since December 2009… Nexus 7000, UCS C200 IOS since December 2009… ISR, ISRG2, 7200 IOS-XE since March 2010… ASR1K IOS-XR since March 2012… CRS-3 Coming soon… ASR9K, and others   Other Releases Other LISP Releases: http://www.lisp4.net Furukawa Network Solutions Corp FreeBSD :: Open LISP Linux :: Aless, LISPmob, OpenWrt (coming soon…) Android :: Gingerbread (coming soon…) Other vendors… Check the site!© 2010 Cisco and/or its affiliates. All rights reserved. 59
  •   LISP Information IETF LISP Working Group …………..… http://tools.ietf.org/wg/lisp/ LISP Beta Network Site ………………… http://www.lisp4.net or http://www.lisp6.net Cisco LISP Site ………………………… http://lisp.cisco.com (IPv4 and IPv6) Cisco LISP Marketing Site …………….. http://www.cisco.com/go/lisp/ LISP DDT Root ………………………..… http://www.ddt-root.org   LISP Host Mobility Information LISP Host Mobility Configuration Guide …. http://lisp.cisco.com/lisp_down.html   LISP Mailing Lists IETF LISP Working Group ………… lisp@ietf.org Cisco LISP Questions ……………… lisp-support@cisco.com LISPmob Questions ………………... users@lispmob.org© 2010 Cisco and/or its affiliates. All rights reserved. 60
  • © 2010 Cisco and/or its affiliates. All rights reserved. 61
  • 1.  Multihoming 2.  IPv6 Transition 3.  Virtualization/VPN IPv4 Core xTR 4.  Mobility IPv4 Network xTR IPv4 Core v4LISP is an Architecture…© 2010 Cisco and/or its affiliates. All rights reserved. 62
  • 1.  Multihoming 2.  IPv6 Transition 3.  Virtualization/VPN IPv6 Network IPv6 Core xTR 4.  Mobility IPv4 Network v6 xTR IPv4 Core v4LISP is an Architecture…© 2010 Cisco and/or its affiliates. All rights reserved. 63
  • 1.  Multihoming 2.  IPv6 Transition 3.  Virtualization/VPN IPv6 Network IPv6 Core xTR 4.  Mobility IPv4 Network v6 xTR IPv4 Core v4LISP is an Architecture…© 2010 Cisco and/or its affiliates. All rights reserved. 64
  • 1.  Multihoming 2.  IPv6 Transition 3.  Virtualization/VPN IPv6 Network IPv6 Core xTR 4.  Mobility IPv4 Network v6 xTR IPv4 Core v4LISP is an Architecture…© 2010 Cisco and/or its affiliates. All rights reserved. 65
  •   Enables IP Number Portability   Deployment simplicity ‒  With session survivability ‒  No host changes ‒  Never change host IP addresses; No renumbering costs ‒  Minimal CPE changes ‒  No DNS “name == EID” binding change ‒  Some new core infrastructure components  Uses pull vs. push routing   LISP use-cases are complimentary ‒  OSPF and BGP are push models; ‒  Simplified multi-homing with Ingress traffic routing stored in the forwarding plan Engineering; no need for BGP ‒  LISP is a pull model; Analogous to DNS; massively ‒  Address Family agnostic support scalable ‒  Virtualization support  Can be used over any IP network ‒  End-host mobility without renumbering ‒  Address Family agnostic   An Open Standard ‒  Incrementally deployable ‒  No Cisco Intellectual Property Rights ‒  End systems can be unaware of LISP© 2010 Cisco and/or its affiliates. All rights reserved. 66
  • •  Thank you! •  Please complete the post-event survey. •  Join us November 7th for our next webinar: Media Services Proxy (MSP) for Enhanced Media Awareness and building Plug-And-Play Media Networks To register, go to www.cisco.com/go/iosadvantage© 2010 Cisco and/or its affiliates. All rights reserved. 67