zNetLaB › Guided labs › Enterprise
Campus fabric: LISP, VXLAN and group policy
Enterprise Advanced 5 devices 5 checked tasks 100 points Plan lab
Hosts sit behind two fabric edges. LISP says where each host is, VXLAN carries the traffic and its group, and the far edge enforces a policy between groups. 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
Hosts sit behind two fabric edges. LISP says where each host is, VXLAN carries the traffic and its group, and the far edge enforces a policy between groups.
Your role: a network engineer on the enterprise team. Level: Advanced Done when: all 5 goals show as passed (100 points).
Network status
Devices: 2 PCs, 3 routers, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. H1 is a host with 172.16.1.10/24, gateway 172.16.1.1. H2 is a host with 172.16.2.10/24, gateway 172.16.2.1. 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 (20 pts) Both edges encapsulate in VXLAN (20 pts) H1 is in group 10 on its own edge (20 pts) The far edge enforces from group 10 to group 20 (20 pts) H1 can no longer reach H2 (20 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 edges encapsulate in VXLAN 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 H1 is in group 10 on its own edge Why: Reading a show command is the core skill of troubleshooting: the output is the truth, not your configuration. Verify with: show cts role-based sgt-map all The far edge enforces from group 10 to group 20 Why: Reading a show command is the core skill of troubleshooting: the output is the truth, not your configuration. Verify with: show cts role-based permissions H1 can no longer reach H2 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 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
Hosts sit behind two fabric edges. LISP says where each host is, VXLAN carries the traffic and its group, and the far edge enforces a policy between groups.
What you will be able to do
The map-server has the site registered
Both edges encapsulate in VXLAN
H1 is in group 10 on its own edge
The far edge enforces from group 10 to group 20
The network
PC, Catalyst 8000V — 5 devices in all, already cabled.
Fa0 Gi2 Gi1 Gi1 Gi2 Gi1 Gi2 Fa0 H1 172.16.1.10/24 · gw 172.16.1.1 X1 MS X2 H2 172.16.2.10/24 · gw 172.16.2.1 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
H1 PC 172.16.1.10 / 255.255.255.0 gw 172.16.1.1 X1 Catalyst 8000V configure it MS Catalyst 8000V configure it X2 Catalyst 8000V configure it H2 PC 172.16.2.10 / 255.255.255.0 gw 172.16.2.1
Cabling
H1 Fa0 ↔ X1 Gi2 X1 Gi1 ↔ MS Gi1 MS Gi2 ↔ X2 Gi1 X2 Gi2 ↔ H2 Fa0
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 20 On MS: show lisp site output matches BRANCH\s+\S+\s+yes. 2 Both edges encapsulate in VXLAN 20 On X1: show running-config contains the line(s) matching encapsulation vxlan. and On X2: show running-config contains the line(s) matching encapsulation vxlan. 3 H1 is in group 10 on its own edge 20 On X1: show cts role-based sgt-map all output matches 172\.16\.1\.10\s+10. 4 The far edge enforces from group 10 to group 20 20 On X2: show cts role-based permissions output matches from group 10 to group 20. 5 H1 can no longer reach H2 20 On X2: show running-config contains the line(s) matching cts role-based enforcement. and On H1: ping 172.16.2.10 must fail — the policy blocks it.
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 GigabitEthernet2
ip address 172.16.1.1 255.255.255.0
no shutdown
exit
interface Loopback0
ip address 1.1.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
encapsulation vxlan
database-mapping 172.16.1.0/24 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
cts role-based sgt-map 172.16.1.10 sgt 10 X2 interface GigabitEthernet1
ip address 10.2.2.3 255.255.255.0
no shutdown
exit
interface GigabitEthernet2
ip address 172.16.2.1 255.255.255.0
no shutdown
exit
interface Loopback0
ip address 3.3.3.3 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
encapsulation vxlan
database-mapping 172.16.2.0/24 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
cts role-based enforcement
cts role-based sgt-map 172.16.2.10 sgt 20
ip access-list role-based DENYALL
deny ip
exit
cts role-based permissions from 10 to 20 DENYALL 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.