Whats the best way to connect cisco router with 2 isps to cisco route with 1 isp using…
- User
Whats the best way to connect cisco router with 2 isps to cisco route with 1 isp using ikev2
- Assistant
Connecting a Cisco router with dual ISPs to another Cisco router with a single ISP using IKEv2 VPN is a common redundancy and high availability design. It ensures that if one ISP goes down on the dual-homed (multi-ISP) router, VPN connectivity is maintained via the second ISP.
Goal:
Establish a site-to-site IKEv2/IPsec VPN between:
- Site A (Head Office): 1 Cisco router with 1 ISP.
- Site B (Branch Office): 1 Cisco router with 2 ISPs.
Ensure redundancy/failover between the ISPs at Site B.
✅ Recommended Method: IKEv2 with Redundant Tunnels
Set up two IKEv2 tunnels, one per ISP at Site B, both pointing to Site A.
Site A must be configured to accept connections from both public IPs of Site B.
🔧 High-Level Topology
Site A (Single ISP) Cisco Router A Public IP: A.A.A.A | | IKEv2/IPsec VPN | ISP 1 (B.B.B.B) Site B ----------------------------- ISP 2 (C.C.C.C) Cisco Router B
1. Configure Site B (Dual ISP) – Cisco Router
Create two separate IKEv2 tunnel profiles, one using each ISP interface.
Steps:
a) Define ISAKMP (IKEv2) policy:
crypto ikev2 policy 10 encryption aes-cbc-256 integrity sha256 group 14 prf sha256 lifetime 28800b) Define IKEv2 proposal/profile:
crypto ikev2 proposal IKEV2_PROPOSAL encryption aes-cbc-256 integrity sha256 group 14crypto ikev2 policy IKEV2_POLICY proposal IKEV2_PROPOSALcrypto ikev2 keyring KEYRING peer SITEA address A.A.A.A pre-shared-key <your_psk>crypto ikev2 profile IKEV2_PROFILE match identity remote address A.A.A.A 255.255.255.255 identity local address <local_public_ip_one_or_two> authentication remote pre-share authentication local pre-share keyring local KEYRINGCreate two profiles if needed for both ISP1 and ISP2 (or dynamically use one with different source interfaces).
c) IPsec transform set and profile:
crypto ipsec transform-set VPN-SET esp-aes 256 esp-sha256-hmac mode tunnelcrypto ipsec profile VPN-PROFILE set transform-set VPN-SET set ikev2-profile IKEV2_PROFILE
d) Create two Tunnel Interfaces (Tunnel0 and Tunnel1 for ISP1 and ISP2):
Tunnel through ISP1:
interface Tunnel0 ip address 10.0.0.1 255.255.255.252 tunnel source <ISP1_INTERFACE> tunnel destination A.A.A.A tunnel mode ipsec ipv4 tunnel protection ipsec profile VPN-PROFILETunnel through ISP2:
interface Tunnel1 ip address 10.0.1.1 255.255.255.252 tunnel source <ISP2_INTERFACE> tunnel destination A.A.A.A tunnel mode ipsec ipv4 tunnel protection ipsec profile VPN-PROFILE
2. Configure Site A (Single ISP)
You will configure VPN acceptance from both public IPs of Site B.
a) Same IKEv2 crypto setup as Site B.
b) Define keyring with both peer IPs:
crypto ikev2 keyring BRANCH_KEYRING peer SITEB1 address B.B.B.B pre-shared-key <your_psk> peer SITEB2 address C.C.C.C pre-shared-key <your_psk>c) IKEv2 profile to accept both:
crypto ikev2 profile IKEV2_PROFILE match identity remote address B.B.B.B 255.255.255.255 match identity remote address C.C.C.C 255.255.255.255 identity local address A.A.A.A authentication remote pre-share authentication local pre-share keyring local BRANCH_KEYRING
d) 2 Tunnel interfaces on Site A
Mirror Site B’s Tunnel IPs:
Tunnel for ISP1:
interface Tunnel0 ip address 10.0.0.2 255.255.255.252 tunnel source <WAN_INTERFACE> tunnel destination B.B.B.B tunnel mode ipsec ipv4 tunnel protection ipsec profile VPN-PROFILETunnel for ISP2:
interface Tunnel1 ip address 10.0.1.2 255.255.255.252 tunnel source <WAN_INTERFACE> tunnel destination C.C.C.C tunnel mode ipsec ipv4 tunnel protection ipsec profile VPN-PROFILE
3. Routing and Failover
Use static routes with tracking, EIGRP, or BGP over tunnels. For quick and simple redundancy, use tracked static routes:
ip sla 1 icmp-echo 10.0.0.2 source-interface Tunnel0 frequency 3 ip sla schedule 1 life forever start-time now track 1 ip sla 1 reachabilityip route 192.168.20.0 255.255.255.0 Tunnel0 track 1 ip route 192.168.20.0 255.255.255.0 Tunnel1Replace 192.168.20.0 with the remote LAN.
4. NAT Exemptions
Ensure you exclude tunnel traffic from NAT on both routers.
ip access-list extended VPN-TRAFFIC permit ip 192.168.10.0 0.0.0.255 192.168.20.0 0.0.0.255 ip nat inside source list VPN-TRAFFIC interface <ISP_INTERFACE> overload
✅ Summary
Feature Site A (Single ISP) Site B (Dual ISP) ISP Interfaces 1 2 Tunnel Interfaces 2 (one per ISP of Site B) 2 (one per ISP) IKEv2 Profiles 1 (matches both peers) 1 or 2 (per ISP) IP SLA / Failover Optional Recommended for failover NAT Exemption Yes Yes
If you’d like a working config example, feel free to tell me your actual private subnets and interfaces, and I’ll build a full config tailored to you.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.