If you manage VPNs on Cisco Firepower (FTD) with FMC, you’ve probably seen this at least once:Phase 1 is up. Phase 2 is up. Users still can’t reach anything.That moment is why I always remind teams of one simple truth:An IPsec tunnel can be “UP” and still pass zero traffic.Here’s a short, practical way to troubleshoot (and explain) FTD/FMC IPsec issues without turning it into a 3-hour debate.1) Control-plane vs data-plane (the fastest mindset shift)IKE/IPsec status = control-plane (negotiation and security associations)Actual application traffic = data-plane (routing, NAT, policy, and MTU)When the tunnel shows up but traffic doesn’t, it’s usually a data-plane problem.2) The 5 most common “tunnel up, traffic dead” causes on FTD/FMC1) NAT exemption missing (the #1 culprit)If VPN traffic is getting PAT’d, the remote side often drops it or never returns it.On FMC, NAT rule order matters — the No-NAT for VPN must be placed correctly above general internet PAT.2) Interesting traffic / selectors mismatchOne side thinks the tunnel protects 10.10.0.0/16 ↔ 172.16.10.0/24, the other side expects something else.Result: SAs exist, but the wrong subnets are encrypted.3) Routing / return path issueYour packets enter the tunnel, but return traffic takes a different path (asymmetry). Stateful devices don’t forgive that for long.4) Access Control Policy not permitting the flowEven if VPN is configured correctly, traffic still has to be allowed by the ACP. If logging isn’t enabled, it can look like “nothing is happening,” which wastes time.5) MTU/MSS problems (apps fail, pings lie)IPsec adds overhead. You may see some basic connectivity work while web apps, RDP, or large transfers fail. When “small works, big doesn’t,” MTU/MSS is a strong suspect.3) My “incident update” line (saves time and arguments)When people ask for an update, I keep it crisp:“Tunnel established; validating NAT exemption, selectors, routing/return path, ACP permit/logging, and MTU for the protected networks.”It signals you’re not guessing — you’re narrowing the failure domain.4) A quick example you’ve probably lived throughSymptom: Tunnel shows UP, but users can’t reach internal apps.Everyone says: “Firewall is blocking.”Turns out:VPN traffic was matching a general PAT rule instead of a No-NAT exemption.Fix the NAT order → traffic immediately starts working.Same tunnel, same peer, same crypto — completely different outcome.Closing thoughtIf you’re supporting IPsec on FTD/FMC, don’t let “UP” fool you.Treat VPN troubleshooting like this:First prove the tunnel. Then prove the flow.If you have your own “first thing you check” on FTD (NAT order, ACP logging, routing, selectors, MTU), share it — those habits are what keep incidents short.
View more