zNetLaB › Guided labs › Enterprise
Group-based policy with SGTs
Enterprise Advanced 3 devices 4 checked tasks 100 points Plan lab
Two hosts talk through a router. Without touching an IP access list, give them groups and write one policy between the 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
Two hosts talk through a router. Without touching an IP access list, give them groups and write one policy between the groups.
Your role: a network engineer on the enterprise team. Level: Advanced Done when: all 4 goals show as passed (100 points).
Network status
Devices: 2 PCs, 1 router, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. H1 is a host with 10.1.1.10/24, gateway 10.1.1.1. H2 is a host with 10.2.2.10/24, gateway 10.2.2.1. R starts 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
Enforcement is on (20 pts) The hosts are in groups 10 and 20 (20 pts) The policy names the role-based list (20 pts) H1 can no longer reach H2 (40 pts) The activity, in order
Enforcement is on 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 hosts are in groups 10 and 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 sgt-map all The policy names the role-based list 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: Blocking traffic is half of security. You prove a block by showing the same ping that worked before now fails. Verify with: ping 10.2.2.10 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
Two hosts talk through a router. Without touching an IP access list, give them groups and write one policy between the groups.
What you will be able to do
Enforcement is on
The hosts are in groups 10 and 20
The policy names the role-based list
H1 can no longer reach H2
The network
PC, Catalyst 8000V — 3 devices in all, already cabled.
Fa0 Gi1 Gi2 Fa0 H1 10.1.1.10/24 · gw 10.1.1.1 R H2 10.2.2.10/24 · gw 10.2.2.1 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
H1 PC 10.1.1.10 / 255.255.255.0 gw 10.1.1.1 R Catalyst 8000V configure it H2 PC 10.2.2.10 / 255.255.255.0 gw 10.2.2.1
Cabling
H1 Fa0 ↔ R Gi1 R 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 Enforcement is on 20 On R: show running-config contains the line(s) matching cts role-based enforcement. 2 The hosts are in groups 10 and 20 20 On R: show cts role-based sgt-map all output matches 10\.2\.2\.10\s+20. 3 The policy names the role-based list 20 On R: show cts role-based permissions output matches from group 10 to group 20. 4 H1 can no longer reach H2 40 On H1: ping 10.2.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:
R interface GigabitEthernet1
ip address 10.1.1.1 255.255.255.0
no shutdown
exit
interface GigabitEthernet2
ip address 10.2.2.1 255.255.255.0
no shutdown
exit
cts role-based enforcement
cts role-based sgt-map 10.1.1.10 sgt 10
cts role-based sgt-map 10.2.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.