zNetLaB › Guided labs › Security
ASA to IOS site-to-site IPsec
Security Advanced 5 devices 4 checked tasks 100 points Plan lab
Branch A sits behind an ASAv, branch B behind an IOS router, with an internet router between them. Build IKEv1 with AES-256, SHA-256 and group 14 on both ends so the two LANs talk over the tunnel. 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
Branch A sits behind an ASAv, branch B behind an IOS router, with an internet router between them. Build IKEv1 with AES-256, SHA-256 and group 14 on both ends so the two LANs talk over the tunnel.
Your role: a security engineer. Level: Advanced Done when: all 4 goals show as passed (100 points).
Network status
Devices: 4 routers, 1 firewall, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. A, FW, I, RB, B 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
LAN A reaches LAN B (35 pts) The ASA has phase 1 up (20 pts) The ASA counts encrypted packets (25 pts) The IOS end agrees (20 pts)
The activity, in order
LAN A reaches LAN B On the ASA: inside and outside, a default route, an ACL from 10.1.0.0/24 to 10.2.0.0/24, an IKEv1 policy enabled on outside, a transform set, a crypto map on outside and a tunnel-group with the pre-shared key. On RB the mirror image with crypto isakmp and a crypto map.Why: Each goal is a state the lab can check on the running device. Verify with: ping 10.2.0.5 The ASA has phase 1 up Phase 1 settles once both ends agree on policy and key.Why: Each goal is a state the lab can check on the running device. Verify with: show crypto ikev1 sa The ASA counts encrypted packets The traffic from the ping is what the counters show.Why: Each goal is a state the lab can check on the running device. Verify with: show crypto ipsec sa The IOS end agrees On RB the ISAKMP SA rests in QM_IDLE once quick mode is done.Why: Each goal is a state the lab can check on the running device. Verify with: show crypto isakmp sa
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
Branch A sits behind an ASAv, branch B behind an IOS router, with an internet router between them. Build IKEv1 with AES-256, SHA-256 and group 14 on both ends so the two LANs talk over the tunnel.
What you will be able to do
LAN A reaches LAN B
The ASA has phase 1 up
The ASA counts encrypted packets
The IOS end agrees
The network
Catalyst 8000V, ASAv (simulated) — 5 devices in all, already cabled.
Gi1 Gi0/0 Gi0/1 Gi1 Gi2 Gi1 Gi2 Gi1 A FW I RB B Drawn from this lab: devices, cables, ports and the addresses already set.
Device Model Address already set
A Catalyst 8000V configure it
FW ASAv (simulated) configure it
I Catalyst 8000V configure it
RB Catalyst 8000V configure it
B Catalyst 8000V configure it
Cabling
A Gi1 ↔ FW Gi0/0
FW Gi0/1 ↔ I Gi1
I Gi2 ↔ RB Gi1
RB Gi2 ↔ B 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 LAN A reaches LAN B 35 On A: ping 10.2.0.5 must succeed.
2 The ASA has phase 1 up 20 On FW: show crypto ikev1 sa output matches MM_ACTIVE.
3 The ASA counts encrypted packets 25 On FW: show crypto ipsec sa output matches #pkts encaps: [1-9].
4 The IOS end agrees 20 On RB: show crypto isakmp sa output matches QM_IDLE.
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:
I interface GigabitEthernet1
ip address 100.0.0.2 255.255.255.0
no shutdown
exit
interface GigabitEthernet2
ip address 100.0.1.2 255.255.255.0
no shutdown
exit
A interface GigabitEthernet1
ip address 10.1.0.5 255.255.255.0
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 10.1.0.1
B interface GigabitEthernet1
ip address 10.2.0.5 255.255.255.0
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 10.2.0.1
RB interface GigabitEthernet1
ip address 100.0.1.1 255.255.255.0
no shutdown
exit
interface GigabitEthernet2
ip address 10.2.0.1 255.255.255.0
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 100.0.1.2
crypto isakmp policy 10
encryption aes 256
hash sha256
authentication pre-share
group 14
exit
crypto isakmp key K address 100.0.0.1
crypto ipsec transform-set TS esp-aes 256 esp-sha256-hmac
exit
access-list 101 permit ip 10.2.0.0 0.0.0.255 10.1.0.0 0.0.0.255
crypto map CM 10 ipsec-isakmp
set peer 100.0.0.1
set transform-set TS
match address 101
exit
interface GigabitEthernet1
crypto map CM
exit
FW
interface GigabitEthernet0/0
nameif inside
security-level 100
ip address 10.1.0.1 255.255.255.0
no shutdown
exit
interface GigabitEthernet0/1
nameif outside
security-level 0
ip address 100.0.0.1 255.255.255.0
no shutdown
exit
route outside 0.0.0.0 0.0.0.0 100.0.0.2
object network L
subnet 10.1.0.0 255.255.255.0
exit
object network R
subnet 10.2.0.0 255.255.255.0
exit
access-list VPN extended permit ip object L object R
crypto ikev1 policy 10
authentication pre-share
encryption aes-256
hash sha256
group 14
exit
crypto ikev1 enable outside
crypto ipsec ikev1 transform-set TS esp-aes-256 esp-sha256-hmac
crypto map CM 10 match address VPN
crypto map CM 10 set peer 100.0.1.1
crypto map CM 10 set ikev1 transform-set TS
crypto map CM interface outside
tunnel-group 100.0.1.1 type ipsec-l2l
tunnel-group 100.0.1.1 ipsec-attributes
ikev1 pre-shared-key K
exit
policy-map global_policy
class inspection_default
inspect icmp
exit
exit
Related labs
Where to start
The lessons are open to everyone, all guided labs are listed by track, and
plans explains what is free and what is not.
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.
Try the simulator in your browser, no sign-up