CloudLabBox
Try the free demo

CCNP ENCOR lab 36 of 36

Overlay explorer: LISP, the SD-Access control plane in miniature

Connect two warehouse networks across a core that knows nothing about them, using LISP: xTRs register their EID prefixes with a map server, resolve each other on demand and tunnel the traffic, which is the control-plane idea behind SD-Access.

Run this lab

It needs Lite: its 6 nodes are set to 6 vCPU and 4,096 MB in total. That fits the free demo too.

In your workspace: Shared, then CCNP ENCOR 350-401 guided labs, then 36 - Overlay explorer - LISP the SD-Access control plane in miniature

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Advanced
Time
About 60 minutes
Nodes need
6 vCPU, 4,096 MB
Smallest plan
Lite

The scenario

Fernhill Freight is evaluating SD-Access for its warehouses. Before the vendor workshop, the architects want the team to understand the fabric's control plane hands-on. You'll build it in miniature with LISP: two warehouse networks (EIDs 172.16.1.0/24 and 172.16.2.0/24) sit behind tunnel routers XTR1 and XTR2, a core (CORE) routes only the 10.0.0.0/8 locator space, and MSMR keeps the directory of who is where.

DeviceInterfaceAddressRole
XTR1Lo0 / Gi0/0 / Gi0/110.255.0.1 (RLOC) / 10.0.1.1/30 / 172.16.1.1/24Leeds xTR
XTR2Lo0 / Gi0/0 / Gi0/110.255.0.2 (RLOC) / 10.0.2.1/30 / 172.16.2.1/24Bristol xTR
MSMRLo0 / Gi0/010.255.0.3 / 10.0.3.1/30map server and map resolver
COREGi0/0–0/2 / Lo010.0.1.2, 10.0.2.2, 10.0.3.2 / 10.255.0.254underlay router
PC1 / PC2eth0172.16.1.10 / 172.16.2.10 (gateways .1)scanners

OSPF already routes the 10.x locator space. The EID prefixes are deliberately not in OSPF. LISP site key: Fh-LISP-2026.

Topology: CORE in the middle with XTR1, XTR2 and MSMR attached; PC1 behind XTR1, PC2 behind XTR2.

What you’ll practise

  • Explain EIDs, RLOCs, xTRs, map servers and map resolvers, and the register/request/reply exchange
  • Configure a combined map server and map resolver with sites and authentication keys
  • Configure two xTRs with database mappings, map servers and map resolvers
  • Verify registrations, the map-cache and end-to-end forwarding across a core without EID routes
  • Relate LISP and VXLAN to the SD-Access fabric

The tasks

  1. See why the core can't help
  2. Build the mapping system
  3. Make the xTRs register and resolve
  4. Send traffic through the overlay
  5. Connect it to SD-Access

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of Overlay explorer - LISP the SD-Access control plane in miniature6 nodes, 5 links. Every link is listed as text below the diagram.COREXTR1XTR2MSMRPC1PC2Gi0/1eth0Gi0/1eth0Gi0/0Gi0/2Gi0/0Gi0/0Gi0/0Gi0/1
6 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • XTR1 Gi0/0 to CORE Gi0/0
  • XTR2 Gi0/0 to CORE Gi0/1
  • MSMR Gi0/0 to CORE Gi0/2
  • XTR1 Gi0/1 to PC1 eth0
  • XTR2 Gi0/1 to PC2 eth0
Nodes in Overlay explorer: LISP, the SD-Access control plane in miniature, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
CORECisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
XTR1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
XTR2Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
MSMRCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PC1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB
PC2VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder CCNP ENCOR 350-401 guided labs.

  3. Open 36 - Overlay explorer - LISP the SD-Access control plane in miniature and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More CCNP ENCOR labs

All CCNP ENCOR labs

Related labs in other courses

CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.