zNetLaB › Guided labs › Enterprise
A LISP control plane for a fabric
Enterprise Advanced 3 devices 3 checked tasks 100 points Plan lab
Fabric networks separate where a host is from who it is. Build a map-server and two edge routers, register the endpoints, and let traffic find them through the map-cache. You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This lab is part of the full simulator: open it free for 7 days with a new account, then with a plan. It needs an account, which keeps your progress.
The scenario
Fabric networks separate where a host is from who it is. Build a map-server and two edge routers, register the endpoints, and let traffic find them through the map-cache.
Your role: a network engineer on the enterprise team. Level: Advanced Done when: all 3 goals show as passed (100 points).
Network status
Devices: 3 routers, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. X1, MS, X2 start with an empty configuration. Known problems
None: nothing is misconfigured. The network is simply not finished: what the goals list is what you have to build or secure. Goals
The map-server has the site registered (40 pts) Both edge routers run as ITR and ETR (20 pts) The core has no route to the endpoints (40 pts) The activity, in order
The map-server has the site registered Why: Reading a show command is the core skill of troubleshooting: the output is the truth, not your configuration. Verify with: show lisp site Both edge routers run as ITR and ETR Why: This is the task that checks your configuration directly: the line must really be there, not just look right. Verify with: show running-config The core has no route to the endpoints Why: A route that should not exist is a leak or a loop waiting to happen. Verify with: show ip route Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong. Why this matters
Fabric networks separate where a host is from who it is. Build a map-server and two edge routers, register the endpoints, and let traffic find them through the map-cache.
What you will be able to do
The map-server has the site registered
Both edge routers run as ITR and ETR
The core has no route to the endpoints
The network
Catalyst 8000V — 3 devices in all, already cabled.
Gi1 Gi1 Gi2 Gi1 X1 MS X2 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
X1 Catalyst 8000V configure it MS Catalyst 8000V configure it X2 Catalyst 8000V configure it
Cabling
X1 Gi1 ↔ MS Gi1 MS Gi2 ↔ X2 Gi1
What is configured at the start
Nothing is configured to start with beyond the addresses above: you build the configuration from a clean start.
Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 The map-server has the site registered 40 On MS: show lisp site output matches BRANCH\s+\S+\s+yes. 2 Both edge routers run as ITR and ETR 20 On X1: show running-config contains the line(s) matching etr map-server 2\.2\.2\.2 key KEY. 3 The core has no route to the endpoints 40 On MS: show ip route does not list 172.16.2.1/32.
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
MS interface GigabitEthernet1
ip address 10.1.1.2 255.255.255.0
no shutdown
exit
interface GigabitEthernet2
ip address 10.2.2.2 255.255.255.0
no shutdown
exit
interface Loopback0
ip address 2.2.2.2 255.255.255.255
exit
ip route 1.1.1.1 255.255.255.255 10.1.1.1
ip route 3.3.3.3 255.255.255.255 10.2.2.3
router lisp
service ipv4
map-server
map-resolver
exit-service-ipv4
site BRANCH
authentication-key KEY
eid-prefix 172.16.0.0/16 accept-more-specifics
exit-site
exit X1 interface GigabitEthernet1
ip address 10.1.1.1 255.255.255.0
no shutdown
exit
interface Loopback0
ip address 1.1.1.1 255.255.255.255
exit
interface Loopback1
ip address 172.16.1.1 255.255.255.255
exit
ip route 0.0.0.0 0.0.0.0 10.1.1.2
router lisp
locator-set RLOC
1.1.1.1 priority 1 weight 100
exit-locator-set
instance-id 0
service ipv4
eid-table default
database-mapping 172.16.1.1/32 locator-set RLOC
itr map-resolver 2.2.2.2
itr
etr map-server 2.2.2.2 key KEY
etr
exit-service-ipv4
exit-instance-id
exit X2 interface GigabitEthernet1
ip address 10.2.2.3 255.255.255.0
no shutdown
exit
interface Loopback0
ip address 3.3.3.3 255.255.255.255
exit
interface Loopback1
ip address 172.16.2.1 255.255.255.255
exit
ip route 0.0.0.0 0.0.0.0 10.2.2.2
router lisp
locator-set RLOC
3.3.3.3 priority 1 weight 100
exit-locator-set
instance-id 0
service ipv4
eid-table default
database-mapping 172.16.2.1/32 locator-set RLOC
itr map-resolver 2.2.2.2
itr
etr map-server 2.2.2.2 key KEY
etr
exit-service-ipv4
exit-instance-id
exit Related labs
Where to start
The lessons all guided labs plans
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.