Octet

The VPN shows up, but no traffic passes. How do you troubleshoot it?

Show the answer

Say this first

"Up" usually means the IKE SA is up. I check that IPsec SAs exist and read the encaps and decaps counters on both ends while sending test traffic. Encaps at zero means the traffic never reaches the encryption: routing, the crypto ACL or NAT exemption on the sending side. Encaps rising but the peer's decaps at zero means the packets die in transit: an ACL or ISP filter on ESP or UDP 4500. Decaps rising but no replies means the remote side: its NAT exemption, its route back, or a host firewall.

Go deeper

Commands, in order

Cisco IOS
show crypto session detail
show crypto ipsec sa peer 203.0.113.2
show ip route 10.2.0.0
show ip nat translations
show access-lists

Reading the counters for traffic from site 1 to site 2

R1 encapsR2 decapsR2 encapsR1 decapsWhere it breaks
00anyanyR1 never sends into the tunnel: route, crypto ACL, NAT
rising0anyanyin transit: ESP or UDP 4500 blocked
risingrising00R2 return path: NAT exemption, route back, crypto ACL
risingrisingrisingrisingtunnel works; look at hosts, inside firewalls, MTU

Test traffic from the right source

A ping from the router itself is sourced from the outside interface and does not match the crypto ACL. Use ping 10.2.0.10 source GigabitEthernet0/0/1.

With a VTI

Check that the route to the remote LAN points into Tunnel0, and look at the tunnel interface counters as well as the SA counters.

Traps

  • Testing with a plain ping from the router and concluding the tunnel is broken.
How did you do?Book 8.5 Example Systems