22.05.2017 Views

nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

Nexus Switching 2nd Edition

Nexus Switching 2nd Edition

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3. The LISP device performs a lookup for the destination (172.20.40.101) in the routing<br />

table. The destination is a LISP EID subnet; it is not injected in the RLOC space, so<br />

the lookup does not return any match, triggering the LISP control plane. The ITR<br />

receives mapping information from the Mapping database (MS) <strong>and</strong> populates the<br />

local map-cache. The destination EID subnet (10.17.1.0/24) is associated with the<br />

ROLCs. The ITR LISP router has a mapping entry of the following:<br />

EID-prefix: 172.20.40.0/24<br />

Locator-set:<br />

10.1.1.1, priority: 1, weight: 50<br />

10.1.1.2, priority: 1, weight: 50<br />

4. The ITR LISP router encapsulating into LISP has a mapping entry of the following:<br />

Click here to view code image<br />

1.1.1.13 -> 10.1.1.1 (LISP)<br />

40.1.1.10 -> 172.20.40.101 (Inside LISP Packet)<br />

5. The ETR LISP router in the Data Center de-encapsulates the LISP packet <strong>and</strong> sees the<br />

following:<br />

40.1.1.10 -> 172.20.40.101<br />

Figure 13-4 shows the format of the UDP LISP encapsulated packet.<br />

Figure 13-4. LISP Encapsulated Packet Format<br />

The ITR performs LISP encapsulation of the original IP traffic <strong>and</strong> sends it into the transport

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!