<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Cisco ASA — проблема IKEv2 SVTI]]></title><description><![CDATA[<p dir="auto">Здравствуйте! У меня возникла проблема с установкой второго туннеля IPSec с использованием STVI с Ikev2 на ASA. Опишу свою ситуацию: ![lab.jpg] У меня есть ASA с двумя внешними интерфейсами, как показано на рисунке. Я пытаюсь установить два VPN-туннеля с маршрутизатором vIOS2, используя IKEv2 и SVTI (route base vpn). Маршрутизатор имеет только один IP-адрес 50.50.50.1. Один туннель работает через Gi0/1 на ASA. Но второй (через Gi0/0 на ASA) не может быть установлен, даже если я использую те же команды. На маршрутизаторе посередине я настроил только интерфейсы для обеспечения связи между ASA и vIOS2. Вот моя конфигурация: ASA ciscoasa# sh run<br />
:<br />
ASA Version 9.8(4)41<br />
!<br />
hostname ciscoasa<br />
enable password $sha512$5000$FBjCoJZvSqJDyvXz9T5vug==$ak/p3gNIoXuwENUAXdRVGw== pbkdf2<br />
names<br />
no mac-address auto !<br />
interface GigabitEthernet0/0 nameif ISP2 security-level 100 ip address 200.200.200.1 255.255.255.0<br />
!<br />
interface GigabitEthernet0/1 nameif ISP1 security-level 100 ip address 100.100.100.1 255.255.255.0<br />
!<br />
interface Tunnel10 nameif TU-10 ip address 10.14.252.2 255.255.255.0 tunnel source interface ISP1 tunnel destination 50.50.50.1 tunnel mode ipsec ipv4 tunnel protection ipsec profile IPSEC_PROFILE<br />
!<br />
interface Tunnel20 nameif TU-20 ip address 10.14.253.2 255.255.255.0 tunnel source interface ISP2 tunnel destination 50.50.50.1 tunnel mode ipsec ipv4 tunnel protection ipsec profile IPSEC_PROFILE<br />
!<br />
ftp mode passive<br />
same-security-traffic permit intra-interface<br />
pager lines 23<br />
mtu ISP1 1500<br />
mtu ISP2 1500<br />
no failover<br />
no failover wait-disable<br />
icmp unreachable rate-limit 1 burst-size 1<br />
no asdm history enable<br />
arp timeout 14400<br />
no arp permit-nonconnected<br />
arp rate-limit 8192<br />
router bgp 65000 bgp log-neighbor-changes address-family ipv4 unicast neighbor 10.14.252.1 remote-as 65300 neighbor 10.14.252.1 activate no auto-summary no synchronization exit-address-family<br />
!<br />
route ISP1 0.0.0.0 0.0.0.0 100.100.100.2 1<br />
timeout xlate 3:00:00<br />
timeout pat-xlate 0:00:30<br />
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 sctp 0:02:00 icmp 0:00:02<br />
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00<br />
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00<br />
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute<br />
timeout tcp-proxy-reassembly 0:01:00<br />
timeout floating-conn 0:00:00<br />
timeout conn-holddown 0:00:15<br />
timeout igp stale-route 0:01:10<br />
user-identity default-domain LOCAL<br />
aaa authentication login-history<br />
no snmp-server location<br />
no snmp-server contact crypto ipsec ikev2 ipsec-proposal TSET protocol esp encryption aes-256 aes-192 protocol esp integrity sha-512 sha-384 sha-256<br />
crypto ipsec profile IPSEC_PROFILE set ikev2 ipsec-proposal TSET crypto ipsec security-association pmtu-aging infinite crypto ikev2 policy 5 encryption aes-256 integrity sha512 sha384 group 19 14 prf sha512 sha384 lifetime seconds 86400<br />
crypto ikev2 enable ISP1<br />
crypto ikev2 enable ISP2<br />
telnet timeout 5<br />
ssh stricthostkeycheck<br />
ssh timeout 5<br />
ssh key-exchange group dh-group1-sha1<br />
console timeout 0<br />
threat-detection basic-threat<br />
threat-detection statistics access-list<br />
no threat-detection statistics tcp-intercept<br />
group-policy VPN-GP internal<br />
group-policy VPN-GP attributes vpn-tunnel-protocol ikev2<br />
dynamic-access-policy-record DfltAccessPolicy<br />
tunnel-group 50.50.50.1 type ipsec-l2l<br />
tunnel-group 50.50.50.1 general-attributes default-group-policy VPN-GP<br />
tunnel-group 50.50.50.1 ipsec-attributes ikev2 remote-authentication pre-shared-key ***** ikev2 local-authentication pre-shared-key *****<br />
!<br />
class-map inspection_default match default-inspection-traffic<br />
!<br />
!<br />
policy-map type inspect dns preset_dns_map parameters message-length maximum client auto message-length maximum 512 no tcp-inspection<br />
policy-map global_policy class inspection_default inspect ip-options inspect netbios inspect rtsp inspect sunrpc inspect tftp inspect xdmcp inspect dns preset_dns_map inspect ftp inspect h323 h225 inspect h323 ras inspect rsh inspect esmtp inspect sqlnet inspect sip inspect skinny<br />
policy-map type inspect dns migrated_dns_map_2 parameters message-length maximum client auto message-length maximum 512 no tcp-inspection<br />
policy-map type inspect dns migrated_dns_map_1 parameters message-length maximum client auto message-length maximum 512 no tcp-inspection<br />
!<br />
service-policy global_policy global<br />
prompt hostname context<br />
no call-home reporting anonymous ciscoasa# vIOS2: Router#sh run<br />
Building configuration... Current configuration : 4639 bytes<br />
!<br />
! Last configuration change at 20:08:36 UTC Fri Aug 22 2025<br />
!<br />
version 15.7<br />
service timestamps debug datetime msec<br />
service timestamps log datetime msec<br />
no service password-encryption<br />
!<br />
hostname Router<br />
!<br />
boot-start-marker<br />
boot-end-marker<br />
!<br />
!<br />
!<br />
no aaa new-model<br />
!<br />
!<br />
ip cef<br />
no ipv6 cef<br />
!<br />
!<br />
crypto ikev2 proposal PROP-1 encryption aes-cbc-256 integrity sha512 sha384 group 19 14<br />
!<br />
crypto ikev2 policy IKEV2_POLICY proposal PROP-1<br />
!<br />
crypto ikev2 keyring KEYRING peer ALL address 0.0.0.0 0.0.0.0 pre-shared-key local Cisco1234 pre-shared-key remote Cisco1234 !<br />
!<br />
!<br />
crypto ikev2 profile ASA_VTI_PROFILE match identity remote address 100.100.100.1 255.255.255.255 identity local address 50.50.50.1 authentication remote pre-share authentication local pre-share keyring local KEYRING dpd 10 2 on-demand<br />
!<br />
crypto ikev2 profile ASA_VTI_PROFILE-2 match identity remote address 200.200.200.1 255.255.255.255 identity local address 50.50.50.1 authentication remote pre-share authentication local pre-share keyring local KEYRING dpd 10 2 on-demand<br />
!<br />
!<br />
!<br />
crypto ipsec transform-set TSET esp-aes 256 esp-sha512-hmac mode tunnel<br />
!<br />
crypto ipsec profile IPSEC_PROFILE set transform-set TSET set ikev2-profile ASA_VTI_PROFILE<br />
!<br />
crypto ipsec profile IPSEC_PROFILE-2 set transform-set TSET set ikev2-profile ASA_VTI_PROFILE-2<br />
!<br />
!<br />
!<br />
interface Tunnel10 ip address 10.14.252.1 255.255.255.0 tunnel source GigabitEthernet0/2 tunnel mode ipsec ipv4 tunnel destination 100.100.100.1 tunnel protection ipsec profile IPSEC_PROFILE<br />
!<br />
interface Tunnel20 ip address 10.14.253.1 255.255.255.0 tunnel source GigabitEthernet0/2 tunnel mode ipsec ipv4 tunnel destination 200.200.200.1 tunnel protection ipsec profile IPSEC_PROFILE-2<br />
!<br />
!<br />
interface GigabitEthernet0/2 ip address 50.50.50.1 255.255.255.0 duplex auto speed auto media-type rj45<br />
!<br />
!<br />
router bgp 65300 bgp log-neighbor-changes neighbor 10.14.252.2 remote-as 65000 ! address-family ipv4 neighbor 10.14.252.2 activate exit-address-family<br />
!<br />
ip forward-protocol nd<br />
!<br />
!<br />
no ip http server<br />
no ip http secure-server<br />
ip route 100.100.100.0 255.255.255.0 50.50.50.2<br />
ip route 200.200.200.0 255.255.255.0 50.50.50.2<br />
! end Router# Вывод ASA: show crypto ikev2 sa: ciscoasa# show crypto ikev2 sa IKEv2 SAs: Session-id:1, Status:UP-ACTIVE, IKE count:1, CHILD count:1 Tunnel-id Local Remote Status Role 11111205 100.100.100.1/500 50.50.50.1/500 READY INITIATOR Encr: AES-CBC, keysize: 256, Hash: SHA512, DH Grp:19, Auth sign: PSK, Auth verify: PSK Life/Active Time: 86400/4925 sec<br />
Child sa: local selector 0.0.0.0/0 - 255.255.255.255/65535 remote selector 0.0.0.0/0 - 255.255.255.255/65535 ESP spi in/out: 0x979c0704/0x2ed10494 Отладка Cisco ASA: ciscoasa# debug crypto ikev2 platform<br />
ciscoasa# IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: (81): Failed to receive the AUTH msg before the timer expired<br />
IKEv2-PROTO-1: (81):<br />
IKEv2-PROTO-1: (81): Auth exchange failed<br />
IKEv2-PROTO-1: (81): Auth exchange failed<br />
IKEv2-PLAT-1: NO IKEv2 ID<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
Failed to receive the AUTH msg before the timer expiredIKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: (80): Maximum number of retransmissions reached<br />
IKEv2-PROTO-1: (80):<br />
IKEv2-PROTO-1: (80): Initial exchange failed<br />
IKEv2-PROTO-1: (80): Initial exchange failed<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: (82): Failed to receive the AUTH msg before the timer expired<br />
IKEv2-PROTO-1: (82):<br />
IKEv2-PROTO-1: (82): Auth exchange failed<br />
IKEv2-PROTO-1: (82): Auth exchange failed<br />
IKEv2-PLAT-1: NO IKEv2 ID<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: Packet is a retransmission<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: Packet is a retransmission<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: Packet is a retransmission<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: Packet is a retransmission<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: (84): Failed to receive the AUTH msg before the timer expired<br />
IKEv2-PROTO-1: (84):<br />
IKEv2-PROTO-1: (84): Auth exchange failed<br />
IKEv2-PROTO-1: (84): Auth exchange failed<br />
IKEv2-PLAT-1: NO IKEv2 ID<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: (85): Failed to receive the AUTH msg before the timer expired<br />
IKEv2-PROTO-1: (85):<br />
IKEv2-PROTO-1: (85): Auth exchange failed<br />
IKEv2-PROTO-1: (85): Auth exchange failed<br />
IKEv2-PLAT-1: NO IKEv2 ID<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: (83): Maximum number of retransmissions reached<br />
IKEv2-PROTO-1: (83):<br />
IKEv2-PROTO-1: (83): Initial exchange failed<br />
IKEv2-PROTO-1: (83): Initial exchange failed<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: (86): Failed to receive the AUTH msg before the timer expired<br />
IKEv2-PROTO-1: (86):<br />
IKEv2-PROTO-1: (86): Auth exchange failed<br />
IKEv2-PROTO-1: (86): Auth exchange failed<br />
IKEv2-PLAT-1: NO IKEv2 ID<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: Packet is a retransmission<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: Packet is a retransmission<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: Packet is a retransmission<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: Packet is a retransmission<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: (88): Failed to receive the AUTH msg before the timer expired<br />
IKEv2-PROTO-1: (88):<br />
IKEv2-PROTO-1: (88): Auth exchange failed<br />
IKEv2-PROTO-1: (88): Auth exchange failed<br />
IKEv2-PLAT-1: NO IKEv2 ID<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1:<br />
IKEv2-PROTO-1: decrypt queuedIKEv2-PROTO-1: Asynchronous request queued<br />
IKEv2-PROTO-1: На ASA я вижу пакет, поступающий от маршрутизатора: ciscoasa# show capture cap1 174 packets captured 6: 20:10:05.739723 50.50.50.1.500 &gt; 200.200.200.1.500: udp 350 7: 20:11:06.382411 50.50.50.1.500 &gt; 200.200.200.1.500: udp 350 8: 20:11:08.372768 50.50.50.1.500 &gt; 200.200.200.1.500: udp 350 9: 20:11:12.049054 50.50.50.1.500 &gt; 200.200.200.1.500: udp 350 10: 20:11:19.902602 50.50.50.1.500 &gt; 200.200.200.1.500: udp 350 11: 20:11:34.855165 50.50.50.1.500 &gt; 200.200.200.1.500: udp 350 12: 20:12:05.874619 50.50.50.1.500 &gt; 200.200.200.1.500: udp 350 13: 20:13:03.844560 50.50.50.1.500 &gt; 200.200.200.1.500: udp 350 14: 20:14:07.601424 50.50.50.1.500 &gt; 200.200.200.1.500: udp 350 15: 20:14:09.416100 50.50.50.1.500 &gt; 200.200.200.1.500: udp 350 16: 20:14:13.375362 50.50.50.1.500 &gt; 200.200.200.1.500: udp 350 17: 20:14:20.878998 50.50.50.1.500 &gt; 200.200.200.1.500: udp 350 18: 20:14:36.066463 50.50.50.1.500 &gt; 200.200.200.1.500: udp 350 19: 20:15:06.633298 50.50.50.1.500 &gt; 200.200.200.1.500: udp 350 20: 20:16:04.577377 50.50.50.1.500 &gt; 200.200.200.1.500: udp 350 21: 20:17:08.808857 50.50.50.1.500 &gt; 200.200.200.1.500: udp 350 Таблица маршрутизации ASA: ciscoasa# show route Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, V - VPN i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route, + - replicated route<br />
Gateway of last resort is 100.100.100.2 to network 0.0.0.0 S* 0.0.0.0 0.0.0.0 [1/0] via 100.100.100.2, ISP1<br />
C 10.14.252.0 255.255.255.0 is directly connected, TU-10<br />
L 10.14.252.2 255.255.255.255 is directly connected, TU-10<br />
C 100.100.100.0 255.255.255.0 is directly connected, ISP1<br />
L 100.100.100.1 255.255.255.255 is directly connected, ISP1<br />
C 200.200.200.0 255.255.255.0 is directly connected, ISP2<br />
L 200.200.200.1 255.255.255.255 is directly connected, ISP2 Есть идеи, что произошло?</p>
<p dir="auto"><img src="/forum/uploads/files/cisco/2ff5a8dc6ed44d78eaf97ba12332fc3d813e3d1b.jpg" alt="" class=" img-fluid img-markdown" /></p>
]]></description><link>https://sla247.ru/forum/topic/2413/cisco-asa-проблема-ikev2-svti</link><generator>RSS for Node</generator><lastBuildDate>Fri, 15 May 2026 11:00:38 GMT</lastBuildDate><atom:link href="https://sla247.ru/forum/topic/2413.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 02 Mar 2026 12:42:59 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Cisco ASA — проблема IKEv2 SVTI on Mon, 02 Mar 2026 12:43:07 GMT]]></title><description><![CDATA[<p dir="auto">ciscoasa# show crypto ikev2 sa IKEv2 SAs: Session-id:3, Status:UP-ACTIVE, IKE count:1, CHILD count:1 Tunnel-id Local Remote Status Role<br />
349156077 200.200.200.1/500 50.50.50.1/500 READY INITIATOR Encr: AES-CBC, keysize: 256, Hash: SHA512, DH Grp:19, Auth sign: PSK, Auth verify: PSK Life/Active Time: 86400/12 sec<br />
Child sa: local selector 0.0.0.0/0 - 255.255.255.255/65535 remote selector 0.0.0.0/0 - 255.255.255.255/65535 ESP spi in/out: 0x39ddab5b/0x8caaeaef Второй туннель работает, основной не работает<br />
![<img src="https://sla247.ru/forum/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=bf4cb1bda7d" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:23px;width:auto;vertical-align:middle" title=":slightly_smiling_face:" alt="🙂" />]<br />
Так что проблема определенно в маршрутизации... но может быть, можно заставить обратный трафик проходить через интерфейс, откуда он приходит?</p>
<p dir="auto"><img src="/forum/uploads/files/cisco/01a0ccb0eaa8c8e75ff1c1ca16e03752af15251b.png" alt="" class=" img-fluid img-markdown" /></p>
]]></description><link>https://sla247.ru/forum/post/16936</link><guid isPermaLink="true">https://sla247.ru/forum/post/16936</guid><dc:creator><![CDATA[mikiNet]]></dc:creator><pubDate>Mon, 02 Mar 2026 12:43:07 GMT</pubDate></item><item><title><![CDATA[Reply to Cisco ASA — проблема IKEv2 SVTI on Mon, 02 Mar 2026 12:43:06 GMT]]></title><description><![CDATA[<p dir="auto">Я буду использовать BGP. Но основная проблема решена! Спасибо!</p>
]]></description><link>https://sla247.ru/forum/post/16935</link><guid isPermaLink="true">https://sla247.ru/forum/post/16935</guid><dc:creator><![CDATA[mikiNet]]></dc:creator><pubDate>Mon, 02 Mar 2026 12:43:06 GMT</pubDate></item><item><title><![CDATA[Reply to Cisco ASA — проблема IKEv2 SVTI on Mon, 02 Mar 2026 12:43:05 GMT]]></title><description><![CDATA[<p dir="auto">Ну, та же причина, по которой туннель 2 может вызвать падение трафика, а именно маршрутизация. Но сейчас мы решаем первую проблему, когда оба туннеля работают. Теперь нам нужно сделать так, чтобы трафик выходил и входил через один и тот же туннель, т. е. решить проблему асимметричной маршрутизации. Я предпочитаю использовать bgp и разделить сеть, подключенную к asa внутри Пусть первая часть проходит через vti1, а вторая — через vti2. MHM</p>
]]></description><link>https://sla247.ru/forum/post/16934</link><guid isPermaLink="true">https://sla247.ru/forum/post/16934</guid><dc:creator><![CDATA[MHM Cisco World]]></dc:creator><pubDate>Mon, 02 Mar 2026 12:43:05 GMT</pubDate></item><item><title><![CDATA[Reply to Cisco ASA — проблема IKEv2 SVTI on Mon, 02 Mar 2026 12:43:04 GMT]]></title><description><![CDATA[<p dir="auto">Что вы имеете в виду под «<br />
и падением трафика»? Я добавил второй статический маршрут по умолчанию, и сейчас оба туннеля работают.</p>
]]></description><link>https://sla247.ru/forum/post/16933</link><guid isPermaLink="true">https://sla247.ru/forum/post/16933</guid><dc:creator><![CDATA[mikiNet]]></dc:creator><pubDate>Mon, 02 Mar 2026 12:43:04 GMT</pubDate></item><item><title><![CDATA[Reply to Cisco ASA — проблема IKEv2 SVTI on Mon, 02 Mar 2026 12:43:03 GMT]]></title><description><![CDATA[<p dir="auto">Проверьте, удалив маршрут по умолчанию к isp1, и используйте новый маршрут к isp2. Вы увидите, что туннель 2 работает, а туннель 1 не работает. Примечание: при выполнении вышеуказанных действий необходимо очистить криптографическую безопасность в маршрутизаторе MHM</p>
]]></description><link>https://sla247.ru/forum/post/16932</link><guid isPermaLink="true">https://sla247.ru/forum/post/16932</guid><dc:creator><![CDATA[MHM Cisco World]]></dc:creator><pubDate>Mon, 02 Mar 2026 12:43:03 GMT</pubDate></item><item><title><![CDATA[Reply to Cisco ASA — проблема IKEv2 SVTI on Mon, 02 Mar 2026 12:43:02 GMT]]></title><description><![CDATA[<p dir="auto">Я тоже так думал, но предпочел спросить, может быть, кто-нибудь знает обходной путь... Я подумал, что, возможно, есть какая-то настройка, такая как IKE Peer Identification или что-то еще, которая четко отличает эти два туннеля друг от друга... хотя я думаю, что в данном случае речь идет в основном о проблеме маршрутизации.</p>
]]></description><link>https://sla247.ru/forum/post/16931</link><guid isPermaLink="true">https://sla247.ru/forum/post/16931</guid><dc:creator><![CDATA[mikiNet]]></dc:creator><pubDate>Mon, 02 Mar 2026 12:43:02 GMT</pubDate></item><item><title><![CDATA[Reply to Cisco ASA — проблема IKEv2 SVTI on Mon, 02 Mar 2026 12:43:01 GMT]]></title><description><![CDATA[<p dir="auto">Я не думаю, что это сработает, потому что Asa всегда использует ISP1 для достижения 50.50.50.1 MHM</p>
]]></description><link>https://sla247.ru/forum/post/16930</link><guid isPermaLink="true">https://sla247.ru/forum/post/16930</guid><dc:creator><![CDATA[MHM Cisco World]]></dc:creator><pubDate>Mon, 02 Mar 2026 12:43:01 GMT</pubDate></item><item><title><![CDATA[Reply to Cisco ASA — проблема IKEv2 SVTI on Mon, 02 Mar 2026 12:43:00 GMT]]></title><description><![CDATA[<p dir="auto">Обходной путь Используйте два маршрута по умолчанию, по одному через каждого интернет-провайдера, и отслеживайте как прохождение, так и потерю трафика. MHM</p>
]]></description><link>https://sla247.ru/forum/post/16929</link><guid isPermaLink="true">https://sla247.ru/forum/post/16929</guid><dc:creator><![CDATA[MHM Cisco World]]></dc:creator><pubDate>Mon, 02 Mar 2026 12:43:00 GMT</pubDate></item></channel></rss>