07-17-2024 04:26 AM
I have two remote FTD managed by FMC and I have two ISPs in each side and I created 4 IPSec connections in each side to failover them by BGP, they work fine until one of ISP goes down and IPSec gets down, but after ISP gets up IPSec not get up, it stays down for a long time in troubleshoot menu there are error Tunnel Manager has failed to establish an L2L SA. All configured IKE versions failed to establish the tunnel. Map Tag= __vti-crypto-map-Tunnel1-0-1. Map Sequence Number = 65280,
IPSec gets up after random long time, I tried to log in CLI and type clear crypto ipsec sa peer <ip address> but it is useless, can you help me?
07-17-2024 04:37 AM
Four IPSec ?
That I think wrong
You need only two IPSec'
One for each ISP if it failed then failover to other ISP IPsec.
MHM
07-17-2024 04:40 AM
Site A ISP A - Site B ISP A
Site A ISP A - Site B ISP B
Site A ISP B - Site B ISP A
Site A ISP B - Site B ISP B
07-17-2024 05:18 AM
no need these two tunnels
Site A ISP A - Site B ISP B
Site A ISP B - Site B ISP A
MHM
07-17-2024 08:23 PM
Ok anyway problem is not in creating second VPN as backup or other VTI, problem is in not going up VPN after ISP gets down up
07-20-2024 04:41 AM
Sorry I was some busy last days
from cisco doc.
""You can deploy the backup tunnel in the following scenarios:
Both peers having service provider redundancy backup. In this case, there are two physical interfaces, acting as the tunnel sources for the two VTIs of the peers.
Only one of the peers having service provider redundancy backup. In this case, there is an interface backup on only one side of the peer and on the other end, there is only one tunnel source interface.""
check below for VPN topology from FMC
node A and node B both have backup VTI config it for the second ISP
config default route with IP SLA toward primary ISP
config defualt route with different distance for the secondary ISP
MHM
07-17-2024 04:38 AM
M.
07-17-2024 04:46 AM
Didn't find any information about my case
07-18-2024 02:50 AM
@sherali mamatkarimov, 4 tunnels won't work due to CSCvo13642. This is a well-known limitation. Simplify your configuration to 2 tunnels as suggested by @MHM Cisco World and re-test collecting relevant "show" outputs when both tunnels are up and running, then when ISP1 goes down and then when it goes up again. This should include routing tables, IKEv2 and IPSec states, interface states, etc. If the tunnel over ISP1 doesn't come up, collect IKEv2 and IPSec debugs.
07-19-2024 03:11 AM
I left only 2 tunnels but status of one of them is unknown, in routing table I can't see directly connected VTI interface
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide