zNetLaB › Guided labs › Security
Troubleshoot: ASA tunnel that never comes up
Security Advanced 5 devices 2 checked tasks 100 points Plan lab
Both ends of the ASA to IOS tunnel look complete, but LAN A cannot reach LAN B and phase 1 never finishes. Find the mismatch. 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
Both ends of the ASA to IOS tunnel look complete, but LAN A cannot reach LAN B and phase 1 never finishes. Find the mismatch.
Your role: a security engineer. Level: Advanced Done when: all 2 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 starts with addresses (G1 10.1.0.5/24) and static routes already configured. FW starts with addresses (G0/0 10.1.0.1/24, G0/1 100.0.0.1/24) and an ACL, IPsec already configured. I starts with addresses (G1 100.0.0.2/24, G2 100.0.1.2/24). RB starts with addresses (G1 100.0.1.1/24, G2 10.2.0.1/24) and static routes, IPsec, an ACL already configured. B starts with addresses (G1 10.2.0.5/24) and static routes already configured.
Known problems
The network worked and now does not: the scenario above says what users report. The cause is a configuration fault, not a cable. Find it with show commands (interfaces, routes, neighbours, running-config) before you change anything; fix only what is wrong.
Goals
LAN A reaches LAN B (60 pts) Phase 1 is MM_ACTIVE on the ASA (40 pts)
The activity, in order
LAN A reaches LAN B The ASA tunnel-group holds key K2, the router holds K. Set ikev1 pre-shared-key K under the tunnel-group ipsec-attributes.Why: Each goal is a state the lab can check on the running device. Verify with: ping 10.2.0.5 Phase 1 is MM_ACTIVE on the ASA With the keys equal, main mode completes.Why: Each goal is a state the lab can check on the running device. Verify with: show crypto ikev1 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
Both ends of the ASA to IOS tunnel look complete, but LAN A cannot reach LAN B and phase 1 never finishes. Find the mismatch.
What you will be able to do
LAN A reaches LAN B
Phase 1 is MM_ACTIVE on the ASA
The network
Catalyst 8000V, ASAv (simulated) — 5 devices in all, already cabled.
Gi1 10.1.0.5/24 Gi0/0 10.1.0.1/24 Gi0/1 100.0.0.1/24 Gi1 100.0.0.2/24 Gi2 100.0.1.2/24 Gi1 100.0.1.1/24 Gi2 10.2.0.1/24 Gi1 10.2.0.5/24 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
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
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 K2
exit
policy-map global_policy
class inspection_default
inspect icmp
exit
exit
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 60 On A: ping 10.2.0.5 must succeed.
2 Phase 1 is MM_ACTIVE on the ASA 40 On FW: show crypto ikev1 sa output matches MM_ACTIVE.
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:
FW
tunnel-group 100.0.1.1 ipsec-attributes
ikev1 pre-shared-key K
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