Currently running ADVPN to connect our branches to our core. I've added ADVPN-BACKUP for branches which uses the 2nd ISP in our core. It connects fine and can access resources in the core. What it can't do is communicate with other sites that are on the primary. ie. ADVPN-MAIN cannot communicate with ADVPN-BACKUP and vice versa but both can communicate with the core just fine. I'd like to allow the branches to select either the main or backup based on latency so I need to get communication between the two of them. Is this a route or rule that I'm missing somewhere? I can post the relevant portions of the config if necessary.
Trace shows:
d=20085 trace_id=7263 func=resolve_ip_tuple_fast line=5746 msg="Find an existing session, id-20e29eb9, original direction"
id=20085 trace_id=7263 func=ipv4_fast_cb line=53 msg="enter fast path"
id=20085 trace_id=7263 func=ipsecdev_hard_start_xmit line=789 msg="enter IPsec interface-ADVPN"
id=20085 trace_id=7263 func=ipsecdev_hard_start_xmit line=854 msg="Failed to find IPsec Common: ADVPN"
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1688 | |
1087 | |
752 | |
446 | |
226 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.