Unlock Exclusive Benefits
Join Our Community Today!
Join our community and post in the forum to earn your exclusive Summer Badge! Become a member today!
LOGIN/REGISTER
CONTINUE AS A GUEST
- Support Forum
- Knowledge Base
- Customer Service
- Internal Article Nominations
- FortiGate
- FortiClient
- FortiADC
- FortiAIOps
- FortiAnalyzer
- FortiAP
- FortiAuthenticator
- FortiBridge
- FortiCache
- FortiCare Services
- FortiCarrier
- FortiCASB
- FortiConverter
- FortiCNP
- FortiDAST
- FortiData
- FortiDDoS
- FortiDB
- FortiDNS
- FortiDLP
- FortiDeceptor
- FortiDevice
- FortiDevSec
- FortiDirector
- FortiEdgeCloud
- FortiEDR
- FortiEndpoint
- FortiExtender
- FortiGate Cloud
- FortiGuard
- FortiGuest
- FortiHypervisor
- FortiInsight
- FortiIsolator
- FortiMail
- FortiManager
- FortiMonitor
- FortiNAC
- FortiNAC-F
- FortiNDR (on-premise)
- FortiNDRCloud
- FortiPAM
- FortiPhish
- FortiPortal
- FortiPresence
- FortiProxy
- FortiRecon
- FortiRecorder
- FortiSRA
- FortiSandbox
- FortiSASE
- FortiSASE Sovereign
- FortiScan
- FortiSIEM
- FortiSOAR
- FortiSwitch
- FortiTester
- FortiToken
- FortiVoice
- FortiWAN
- FortiWeb
- FortiAppSec Cloud
- Lacework
- Wireless Controller
- RMA Information and Announcements
- FortiCloud Products
- ZTNA
- 4D Documents
- Customer Service
- Community Groups
- Blogs
Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
- Fortinet Community
- Support Forum
- Dialup peer don`t connect to server when reconnect...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dialup peer don`t connect to server when reconnecting IPsec tunnel
Hello everyone,
I set up a Dialup IPSec tunnel between two FortiGates. The remote FortiGate connects to the server via an external LTE modem. Port forwarding is configured on the modem. If the connection is lost, the tunnel isn't automatically reestablished. Phase 1 appears to be established, but phase 2 isn't. After rebooting the remote Fortigate, the tunnel establishes itself automatically. However, after the connection is lost, it doesn't establish itself again. Where to look for the problem? Here's the debugging log:
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: created connection: 0x9764470 5 192.168.2.2->105.109.199.30:500.
ike V=root:0:VPN_Test_TSw1:348: initiator: aggressive mode is sending 1st message...
ike V=root:0:VPN_Test_TSw1:348: cookie f28a0d09e11de14b/0000000000000000
ike V=root:0:VPN_Test_TSw1:348: generate DH public value request queued
ike 0:VPN_Test_TSw1:348: out F28A0D09E11DE14B000000000000000001100400000000000000026E0400003C000000010000000100000030010100010000002801010000800B0001000C000400015
18080010007800E010080030001800200028004000E0A000104D73D37B5C846B47FA24CD69E10593530F9EF85CE13638F0357A734F01E0C49B4D78D7022041E6100B7AFEE52C1C3E0EA5B06E8319DBC628
B4B358623A389E993B70D73F79E30DD09F28FB04E937EB8B89EA553EE2C62F694CF4721B5BFF68926F39EB9487E8B4953486A210486287C08CE69320B5F3BB012F3F703CAB0A17549CC1DC327B5E46B08C
86528EE3EAA3F4367C21044031261E304D5FA1C937D2C838237607937F3B9C556BF7D45ADE47B231F030D2BE4E09C643F74EE2ADA0F853EE2B79600632E0989BC550D0702AF34536EED8167442200DE362
DF8C9B99B0F50C78E90CF08F5B74BBDDD81DB7F494DE14B4EF70E3ACEB1E926DC68F3B6EFD0ED05000024A7950136DECC5925100B1001CB2DAE342D1831A1E5D2B98A78FB9AF7C472F0150D00000E0B000
0005465737446470D0000144A131C81070358455C5728F20E95452F0D0000147D9419A65310CA6F2C179D9215529D560D000014CD60464335DF21F87CFDB2FC68B6A4480D00001490CB80913EBB696E086
381B5EC427B1F0D00001416F6CA16E4A4066D83821A0F0AEAA8620D0000144485152D18B6BBCD0BE8A8469579DDCC0D000014AFCAD71368A1F1C96B8696FC775701000D00001412F5F28C457168A9702D9
FE274CC02040D0000144048B7D56EBCE88525E7DE7F00D6C2D30D0000184048B7D56EBCE88525E7DE7F00D6C2D3C0000000000000148299031757A36082C6A621DE00000000
ike V=root:0:VPN_Test_TSw1:348: sent IKE msg (agg_i1send): 192.168.2.2:500->105.109.199.30:500, len=622, vrf=0, id=f28a0d09e11de14b/0000000000000000
ike V=root:0: comes 105.109.199.30:500->192.168.2.2:500,ifindex=5,vrf=0,len=576....
ike V=root:0: IKEv1 exchange=Aggressive id=f28a0d09e11de14b/d5eae735d8a51bc4 len=576 vrf=0
ike 0: in F28A0D09E11DE14BD5EAE735D8A51BC40110040000000000000002400400003C000000010000000100000030010100010000002801010000800B0001000C00040001518080010007800E0100
80030001800200028004000E0A0001046658D172AB99266DBC252654A4BE43590374E21F371470589776181EF50BEA188B6C1060FB136FFCD34352160C021141A4C64B4E0D065D19BEDD56EF99CDB69115
910F98B1216D9910EE9886BCAC47B46A0D0369FCC23B1A3D23EF7DC98AD8E099272F8F560B3DA676C9A3DEDC0C390B20C631BF928BC2CAE4C8A9A18E2579E4EA76C59FDCF60B639DBE6DB7707D561809E0
F2EE8FC0F448004B1FBF9ABD334D0F59270928C3AF7B1E6155232EA3AB1226BCE31F6C86444E29D8807538219A32BF4BB31AC8D0567D77AF807B582DBECE8D1496905543D6456BB85F9F0188768D593E51
BF113504482518A73D58577A5683C7A7D54B0B936D7FE28F0E22DC3C6905000014D2F76DBEABBD56997A627CFA994B59080800000C02000000526F6F740D000018AB43B27421D140CB6C996F5F991BBCF1
9A2EE690140000144A131C81070358455C5728F20E95452F140000184B8A47591332356A79D475825A10618498A0580F0D0000189B94C71424DF0C400387A04BA3B412B8657D79DD0D000014AFCAD71368
A1F1C96B8696FC775701000D00001412F5F28C457168A9702D9FE274CC02040D0000148299031757A36082C6A621DE000000000D0000144048B7D56EBCE88525E7DE7F00D6C2D3000000184048B7D56EBC
E88525E7DE7F00D6C2D3C0000000
ike V=root:0:VPN_Test_TSw1:348: VID RFC 3947 4A131C81070358455C5728F20E95452F
ike V=root:0:VPN_Test_TSw1:348: VID DPD AFCAD71368A1F1C96B8696FC77570100
ike V=root:0:VPN_Test_TSw1:348: DPD negotiated
ike V=root:0:VPN_Test_TSw1:348: VID CISCO-UNITY 12F5F28C457168A9702D9FE274CC0204
ike V=root:0:VPN_Test_TSw1:348: peer supports UNITY
ike V=root:0:VPN_Test_TSw1:348: VID FORTIGATE 8299031757A36082C6A621DE00000000
ike V=root:0:VPN_Test_TSw1:348: peer is FortiGate/FortiOS (v0 b0)
ike V=root:0:VPN_Test_TSw1:348: VID FRAGMENTATION 4048B7D56EBCE88525E7DE7F00D6C2D3
ike V=root:0:VPN_Test_TSw1:348: VID FRAGMENTATION 4048B7D56EBCE88525E7DE7F00D6C2D3C0000000
ike V=root:0:VPN_Test_TSw1:348: received peer identifier FQDN 'Root'
ike V=root:0:VPN_Test_TSw1:348: negotiation result
ike V=root:0:VPN_Test_TSw1:348: proposal id = 1:
ike V=root:0:VPN_Test_TSw1:348: protocol id = ISAKMP:
ike V=root:0:VPN_Test_TSw1:348: trans_id = KEY_IKE.
ike V=root:0:VPN_Test_TSw1:348: encapsulation = IKE/none
ike V=root:0:VPN_Test_TSw1:348: type=OAKLEY_ENCRYPT_ALG, val=AES_CBC, key-len=256
ike V=root:0:VPN_Test_TSw1:348: type=OAKLEY_HASH_ALG, val=SHA.
ike V=root:0:VPN_Test_TSw1:348: type=AUTH_METHOD, val=PRESHARED_KEY.
ike V=root:0:VPN_Test_TSw1:348: type=OAKLEY_GROUP, val=MODP2048.
ike V=root:0:VPN_Test_TSw1:348: ISAKMP SA lifetime=86400
ike V=root:0:VPN_Test_TSw1:348: received NAT-D payload type 20
ike V=root:0:VPN_Test_TSw1:348: received NAT-D payload type 20
ike V=root:0:VPN_Test_TSw1:348: selected NAT-T version: RFC 3947
ike V=root:0:VPN_Test_TSw1:348: NAT detected: ME
ike V=root:0:VPN_Test_TSw1:348: compute DH shared secret request queued
ike 0:VPN_Test_TSw1:348: ISAKMP SA f28a0d09e11de14b/d5eae735d8a51bc4 key 32:95B4470C719B24F5704BCEB350B100F30E7A7691128D6CDAF3DC5D26A7B26674
ike V=root:0:VPN_Test_TSw1:348: PSK authentication succeeded
ike V=root:0:VPN_Test_TSw1:348: authentication OK
ike V=root:0:VPN_Test_TSw1:348: NAT-T float port 4500
ike V=root:0:VPN_Test_TSw1:348: add INITIAL-CONTACT
ike 0:VPN_Test_TSw1:348: enc F28A0D09E11DE14BD5EAE735D8A51BC40810040100000000000000801400001808C0DBFF1126CDBF9CDC36DDAD2504C38F87DAC214000018F57590E70A8ED26752D23
3CE39973A818E6A8D090B0000182EEA10AF2A93A962B75725FCED62EE35FCB3785C0000001C0000000101106002F28A0D09E11DE14BD5EAE735D8A51BC4
ike 0:VPN_Test_TSw1:348: out F28A0D09E11DE14BD5EAE735D8A51BC408100401000000000000008CE840B1D5E9E961F05DFAC075F4B46BE47254720A844D2CC7EC0CFA327BD7B67C8193238BB9BD8
DB953525965879181282BCA5A7F18BC426F11FF6DA3502C05D0E20C30F35BC8B80ADA0480950E9F20B8966E9860AC2A176947C227381585651ABC4EAC041E02975833BCF5CB37BA2834
ike V=root:0:VPN_Test_TSw1:348: sent IKE msg (agg_i2send): 192.168.2.2:4500->105.109.199.30:4500, len=140, vrf=0, id=f28a0d09e11de14b/d5eae735d8a51bc4
ike V=root:0:VPN_Test_TSw1:348: established IKE SA f28a0d09e11de14b/d5eae735d8a51bc4
ike V=root:0:VPN_Test_TSw1:348: check peer route: if_addr4_rcvd=0, if_addr6_rcvd=0, mode_cfg=0
ike V=root:0:VPN_Test_TSw1:348: initiating mode-cfg pull from peer
ike V=root:0:VPN_Test_TSw1:348: mode-cfg request APPLICATION_VERSION
ike V=root:0:VPN_Test_TSw1:348: mode-cfg request INTERNAL_IP4_ADDRESS
ike V=root:0:VPN_Test_TSw1:348: mode-cfg request INTERNAL_IP4_NETMASK
ike V=root:0:VPN_Test_TSw1:348: mode-cfg request UNITY_SPLIT_INCLUDE
ike V=root:0:VPN_Test_TSw1:348: mode-cfg request UNITY_PFS
ike 0:VPN_Test_TSw1:348: enc F28A0D09E11DE14BD5EAE735D8A51BC408100601A7B1376B0000007C0E0000186DAB60911B0ED6B61EFDC52EF525D8BD21875F1C000000480100B1E90007002C466F7
27469476174652D3430462076372E342E382C6275696C64323739352C323530353233202847412E4D2900010000000200007004000070070000
ike 0:VPN_Test_TSw1:348: out F28A0D09E11DE14BD5EAE735D8A51BC408100601A7B1376B0000008C8EDDC8B0AEE4EAFC366AECD809ABD9100629EE4770278C255D141825C874C13EDF463E5897756
823B0729D122B3A0E278A064AA6BC173916EA82A63D98BD4608D195C94C5522AC31F992839E9A2F25785AD8B9A637BC992423363CE65DFF5FAD3872F34225FB5F64C51C73583C8874A4
ike V=root:0:VPN_Test_TSw1:348: sent IKE msg (cfg_send): 192.168.2.2:4500->105.109.199.30:4500, len=140, vrf=0, id=f28a0d09e11de14b/d5eae735d8a51bc4:a7b1376b
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: IPsec SA connect 5 192.168.2.2->105.109.199.30:4500
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: using existing connection
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: config found
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: IPsec SA connect 5 192.168.2.2->105.109.199.30:4500 negotiating
ike V=root:0:VPN_Test_TSw1:348: peer has not completed Configuration Method
ike V=root:0:VPN_Test_TSw1:348:VPN_Test_TSw1:1057: Mode Config pending, queuing quick-mode request
ike 0:VPN_Test_TSw1:348: out F28A0D09E11DE14BD5EAE735D8A51BC408100601A7B1376B0000008C8EDDC8B0AEE4EAFC366AECD809ABD9100629EE4770278C255D141825C874C13EDF463E5897756
823B0729D122B3A0E278A064AA6BC173916EA82A63D98BD4608D195C94C5522AC31F992839E9A2F25785AD8B9A637BC992423363CE65DFF5FAD3872F34225FB5F64C51C73583C8874A4
ike V=root:0:VPN_Test_TSw1:348: sent IKE msg (CFG_RETRANS): 192.168.2.2:4500->105.109.199.30:4500, len=140, vrf=0, id=f28a0d09e11de14b/d5eae735d8a51bc4:a7b1376b
ike V=root:0: comes 105.109.199.30:500->192.168.2.2:500,ifindex=5,vrf=0,len=544....
ike V=root:0: IKEv1 exchange=Aggressive id=f28a0d09e11de14b/d5eae735d8a51bc4 len=544 vrf=0
ike 0: in F28A0D09E11DE14BD5EAE735D8A51BC48410040000000000000002200000020400010100F28A0D09E11DE14BD5EAE735D8A51BC40110040000000000000002400400003C0000000100000001
00000030010100010000002801010000800B0001000C00040001518080010007800E010080030001800200028004000E0A0001046658D172AB99266DBC252654A4BE43590374E21F371470589776181EF5
0BEA188B6C1060FB136FFCD34352160C021141A4C64B4E0D065D19BEDD56EF99CDB69115910F98B1216D9910EE9886BCAC47B46A0D0369FCC23B1A3D23EF7DC98AD8E099272F8F560B3DA676C9A3DEDC0C
390B20C631BF928BC2CAE4C8A9A18E2579E4EA76C59FDCF60B639DBE6DB7707D561809E0F2EE8FC0F448004B1FBF9ABD334D0F59270928C3AF7B1E6155232EA3AB1226BCE31F6C86444E29D8807538219A
32BF4BB31AC8D0567D77AF807B582DBECE8D1496905543D6456BB85F9F0188768D593E51BF113504482518A73D58577A5683C7A7D54B0B936D7FE28F0E22DC3C6905000014D2F76DBEABBD56997A627CFA
994B59080800000C02000000526F6F740D000018AB43B27421D140CB6C996F5F991BBCF19A2EE690140000144A131C81070358455C5728F20E95452F140000184B8A47591332356A79D475825A10618498
A0580F0D0000189B94C71424DF0C400387A04BA3B412B8657D79DD0D000014AFCAD71368A1F1C96B8696FC775701000D00001412F5F28C457168A9702D9FE2
ike V=root:0:VPN_Test_TSw1:348: received fragment len 516 id 1 index 1 last 0
ike V=root:0: comes 105.109.199.30:500->192.168.2.2:500,ifindex=5,vrf=0,len=104....
ike V=root:0: IKEv1 exchange=Aggressive id=f28a0d09e11de14b/d5eae735d8a51bc4 len=104 vrf=0
ike 0: in F28A0D09E11DE14BD5EAE735D8A51BC48410040000000000000000680000004C0001020174CC02040D0000148299031757A36082C6A621DE000000000D0000144048B7D56EBCE88525E7DE7F
00D6C2D3000000184048B7D56EBCE88525E7DE7F00D6C2D3C0000000
ike V=root:0:VPN_Test_TSw1:348: received fragment len 76 id 1 index 2 last 1
ike V=root:0:VPN_Test_TSw1:348: frag ID 256 total fragments expected 2
ike V=root:0:VPN_Test_TSw1:348: retransmission, re-send last message
ike 0:VPN_Test_TSw1:348: out F28A0D09E11DE14BD5EAE735D8A51BC408100401000000000000008CE840B1D5E9E961F05DFAC075F4B46BE47254720A844D2CC7EC0CFA327BD7B67C8193238BB9BD8
DB953525965879181282BCA5A7F18BC426F11FF6DA3502C05D0E20C30F35BC8B80ADA0480950E9F20B8966E9860AC2A176947C227381585651ABC4EAC041E02975833BCF5CB37BA2834
ike V=root:0:VPN_Test_TSw1:348: sent IKE msg (retransmit): 192.168.2.2:4500->105.109.199.30:4500, len=140, vrf=0, id=f28a0d09e11de14b/d5eae735d8a51bc4
ike :shrank heap by 159744 bytes
ike 0:VPN_Test_TSw1:348: out F28A0D09E11DE14BD5EAE735D8A51BC408100601A7B1376B0000008C8EDDC8B0AEE4EAFC366AECD809ABD9100629EE4770278C255D141825C874C13EDF463E5897756
823B0729D122B3A0E278A064AA6BC173916EA82A63D98BD4608D195C94C5522AC31F992839E9A2F25785AD8B9A637BC992423363CE65DFF5FAD3872F34225FB5F64C51C73583C8874A4
ike V=root:0:VPN_Test_TSw1:348: sent IKE msg (CFG_RETRANS): 192.168.2.2:4500->105.109.199.30:4500, len=140, vrf=0, id=f28a0d09e11de14b/d5eae735d8a51bc4:a7b1376b
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: IPsec SA connect 5 192.168.2.2->105.109.199.30:4500
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: using existing connection
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: config found
ike V=root:0:VPN_Test_TSw1: request is on the queue
ike V=root:0: comes 105.109.199.30:500->192.168.2.2:500,ifindex=5,vrf=0,len=544....
ike V=root:0: IKEv1 exchange=Aggressive id=f28a0d09e11de14b/d5eae735d8a51bc4 len=544 vrf=0
ike 0: in F28A0D09E11DE14BD5EAE735D8A51BC48410040000000000000002200000020400020100F28A0D09E11DE14BD5EAE735D8A51BC40110040000000000000002400400003C0000000100000001
00000030010100010000002801010000800B0001000C00040001518080010007800E010080030001800200028004000E0A0001046658D172AB99266DBC252654A4BE43590374E21F371470589776181EF5
0BEA188B6C1060FB136FFCD34352160C021141A4C64B4E0D065D19BEDD56EF99CDB69115910F98B1216D9910EE9886BCAC47B46A0D0369FCC23B1A3D23EF7DC98AD8E099272F8F560B3DA676C9A3DEDC0C
390B20C631BF928BC2CAE4C8A9A18E2579E4EA76C59FDCF60B639DBE6DB7707D561809E0F2EE8FC0F448004B1FBF9ABD334D0F59270928C3AF7B1E6155232EA3AB1226BCE31F6C86444E29D8807538219A
32BF4BB31AC8D0567D77AF807B582DBECE8D1496905543D6456BB85F9F0188768D593E51BF113504482518A73D58577A5683C7A7D54B0B936D7FE28F0E22DC3C6905000014D2F76DBEABBD56997A627CFA
994B59080800000C02000000526F6F740D000018AB43B27421D140CB6C996F5F991BBCF19A2EE690140000144A131C81070358455C5728F20E95452F140000184B8A47591332356A79D475825A10618498
A0580F0D0000189B94C71424DF0C400387A04BA3B412B8657D79DD0D000014AFCAD71368A1F1C96B8696FC775701000D00001412F5F28C457168A9702D9FE2
ike V=root:0:VPN_Test_TSw1:348: received fragment len 516 id 2 index 1 last 0
ike V=root:0: comes 105.109.199.30:500->192.168.2.2:500,ifindex=5,vrf=0,len=104....
ike V=root:0: IKEv1 exchange=Aggressive id=f28a0d09e11de14b/d5eae735d8a51bc4 len=104 vrf=0
ike 0: in F28A0D09E11DE14BD5EAE735D8A51BC48410040000000000000000680000004C0002020174CC02040D0000148299031757A36082C6A621DE000000000D0000144048B7D56EBCE88525E7DE7F
00D6C2D3000000184048B7D56EBCE88525E7DE7F00D6C2D3C0000000
ike V=root:0:VPN_Test_TSw1:348: received fragment len 76 id 2 index 2 last 1
ike V=root:0:VPN_Test_TSw1:348: frag ID 512 total fragments expected 2
ike V=root:0:VPN_Test_TSw1:348: retransmission, re-send last message
ike 0:VPN_Test_TSw1:348: out F28A0D09E11DE14BD5EAE735D8A51BC408100401000000000000008CE840B1D5E9E961F05DFAC075F4B46BE47254720A844D2CC7EC0CFA327BD7B67C8193238BB9BD8
DB953525965879181282BCA5A7F18BC426F11FF6DA3502C05D0E20C30F35BC8B80ADA0480950E9F20B8966E9860AC2A176947C227381585651ABC4EAC041E02975833BCF5CB37BA2834
ike V=root:0:VPN_Test_TSw1:348: sent IKE msg (retransmit): 192.168.2.2:4500->105.109.199.30:4500, len=140, vrf=0, id=f28a0d09e11de14b/d5eae735d8a51bc4
ike V=root:0:VPN_Test_TSw1: NAT keep-alive 5 192.168.2.2->105.109.199.30:4500.
ike 0:VPN_Test_TSw1:348: out FF
ike V=root:0:VPN_Test_TSw1:348: sent IKE msg (keepalive): 192.168.2.2:4500->105.109.199.30:4500, len=1, vrf=0, id=ff00000000000000/5101000000000000
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: IPsec SA connect 5 192.168.2.2->105.109.199.30:4500
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: using existing connection
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: config found
ike V=root:0:VPN_Test_TSw1: request is on the queue
ike 0:VPN_Test_TSw1:348: out F28A0D09E11DE14BD5EAE735D8A51BC408100601A7B1376B0000008C8EDDC8B0AEE4EAFC366AECD809ABD9100629EE4770278C255D141825C874C13EDF463E5897756
823B0729D122B3A0E278A064AA6BC173916EA82A63D98BD4608D195C94C5522AC31F992839E9A2F25785AD8B9A637BC992423363CE65DFF5FAD3872F34225FB5F64C51C73583C8874A4
ike V=root:0:VPN_Test_TSw1:348: sent IKE msg (CFG_RETRANS): 192.168.2.2:4500->105.109.199.30:4500, len=140, vrf=0, id=f28a0d09e11de14b/d5eae735d8a51bc4:a7b1376b
ike :shrank heap by 135168 bytes
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: IPsec SA connect 5 192.168.2.2->105.109.199.30:4500
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: using existing connection
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: config found
ike V=root:0:VPN_Test_TSw1: request is on the queue
ike V=root:0:VPN_Test_TSw1: NAT keep-alive 5 192.168.2.2->105.109.199.30:4500.
ike 0:VPN_Test_TSw1:348: out FF
ike V=root:0:VPN_Test_TSw1:348: sent IKE msg (keepalive): 192.168.2.2:4500->105.109.199.30:4500, len=1, vrf=0, id=ff00000000000000/4100000000000000
ike V=root:0: comes 105.109.199.30:500->192.168.2.2:500,ifindex=5,vrf=0,len=544....
ike V=root:0: IKEv1 exchange=Aggressive id=f28a0d09e11de14b/d5eae735d8a51bc4 len=544 vrf=0
ike 0: in F28A0D09E11DE14BD5EAE735D8A51BC48410040000000000000002200000020400030100F28A0D09E11DE14BD5EAE735D8A51BC40110040000000000000002400400003C0000000100000001
00000030010100010000002801010000800B0001000C00040001518080010007800E010080030001800200028004000E0A0001046658D172AB99266DBC252654A4BE43590374E21F371470589776181EF5
0BEA188B6C1060FB136FFCD34352160C021141A4C64B4E0D065D19BEDD56EF99CDB69115910F98B1216D9910EE9886BCAC47B46A0D0369FCC23B1A3D23EF7DC98AD8E099272F8F560B3DA676C9A3DEDC0C
390B20C631BF928BC2CAE4C8A9A18E2579E4EA76C59FDCF60B639DBE6DB7707D561809E0F2EE8FC0F448004B1FBF9ABD334D0F59270928C3AF7B1E6155232EA3AB1226BCE31F6C86444E29D8807538219A
32BF4BB31AC8D0567D77AF807B582DBECE8D1496905543D6456BB85F9F0188768D593E51BF113504482518A73D58577A5683C7A7D54B0B936D7FE28F0E22DC3C6905000014D2F76DBEABBD56997A627CFA
994B59080800000C02000000526F6F740D000018AB43B27421D140CB6C996F5F991BBCF19A2EE690140000144A131C81070358455C5728F20E95452F140000184B8A47591332356A79D475825A10618498
A0580F0D0000189B94C71424DF0C400387A04BA3B412B8657D79DD0D000014AFCAD71368A1F1C96B8696FC775701000D00001412F5F28C457168A9702D9FE2
ike V=root:0:VPN_Test_TSw1:348: received fragment len 516 id 3 index 1 last 0
ike V=root:0: comes 105.109.199.30:500->192.168.2.2:500,ifindex=5,vrf=0,len=104....
ike V=root:0: IKEv1 exchange=Aggressive id=f28a0d09e11de14b/d5eae735d8a51bc4 len=104 vrf=0
ike 0: in F28A0D09E11DE14BD5EAE735D8A51BC48410040000000000000000680000004C0003020174CC02040D0000148299031757A36082C6A621DE000000000D0000144048B7D56EBCE88525E7DE7F
00D6C2D3000000184048B7D56EBCE88525E7DE7F00D6C2D3C0000000
ike V=root:0:VPN_Test_TSw1:348: received fragment len 76 id 3 index 2 last 1
ike V=root:0:VPN_Test_TSw1:348: frag ID 768 total fragments expected 2
ike V=root:0:VPN_Test_TSw1:348: retransmission, re-send last message
ike 0:VPN_Test_TSw1:348: out F28A0D09E11DE14BD5EAE735D8A51BC408100401000000000000008CE840B1D5E9E961F05DFAC075F4B46BE47254720A844D2CC7EC0CFA327BD7B67C8193238BB9BD8
DB953525965879181282BCA5A7F18BC426F11FF6DA3502C05D0E20C30F35BC8B80ADA0480950E9F20B8966E9860AC2A176947C227381585651ABC4EAC041E02975833BCF5CB37BA2834
ike V=root:0:VPN_Test_TSw1:348: sent IKE msg (retransmit): 192.168.2.2:4500->105.109.199.30:4500, len=140, vrf=0, id=f28a0d09e11de14b/d5eae735d8a51bc4
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: IPsec SA connect 5 192.168.2.2->105.109.199.30:4500
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: using existing connection
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: config found
ike V=root:0:VPN_Test_TSw1: request is on the queue
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: IPsec SA connect 5 192.168.2.2->105.109.199.30:4500
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: using existing connection
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: config found
ike V=root:0:VPN_Test_TSw1: request is on the queue
ike V=root:0:VPN_Test_TSw1: NAT keep-alive 5 192.168.2.2->105.109.199.30:4500.
ike 0:VPN_Test_TSw1:348: out FF
ike V=root:0:VPN_Test_TSw1:348: sent IKE msg (keepalive): 192.168.2.2:4500->105.109.199.30:4500, len=1, vrf=0, id=ff00000000000000/4100000000000000
ike 0:VPN_Test_TSw1:348: out F28A0D09E11DE14BD5EAE735D8A51BC408100601A7B1376B0000008C8EDDC8B0AEE4EAFC366AECD809ABD9100629EE4770278C255D141825C874C13EDF463E5897756
823B0729D122B3A0E278A064AA6BC173916EA82A63D98BD4608D195C94C5522AC31F992839E9A2F25785AD8B9A637BC992423363CE65DFF5FAD3872F34225FB5F64C51C73583C8874A4
ike V=root:0:VPN_Test_TSw1:348: sent IKE msg (CFG_RETRANS): 192.168.2.2:4500->105.109.199.30:4500, len=140, vrf=0, id=f28a0d09e11de14b/d5eae735d8a51bc4:a7b1376b
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: IPsec SA connect 5 192.168.2.2->105.109.199.30:4500
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: using existing connection
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: config found
ike V=root:0:VPN_Test_TSw1: request is on the queue
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: IPsec SA connect 5 192.168.2.2->105.109.199.30:4500
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: using existing connection
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: config found
ike V=root:0:VPN_Test_TSw1: request is on the queue
ike V=root:0:VPN_Test_TSw1: NAT keep-alive 5 192.168.2.2->105.109.199.30:4500.
ike 0:VPN_Test_TSw1:348: out FF
ike V=root:0:VPN_Test_TSw1:348: sent IKE msg (keepalive): 192.168.2.2:4500->105.109.199.30:4500, len=1, vrf=0, id=ff00000000000000/5101000000000000
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: IPsec SA connect 5 192.168.2.2->105.109.199.30:4500
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: using existing connection
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: config found
ike V=root:0:VPN_Test_TSw1: request is on the queue
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: IPsec SA connect 5 192.168.2.2->105.109.199.30:4500
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: using existing connection
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: config found
ike V=root:0:VPN_Test_TSw1: request is on the queue
ike V=root:0:VPN_Test_TSw1: NAT keep-alive 5 192.168.2.2->105.109.199.30:4500.
ike 0:VPN_Test_TSw1:348: out FF
ike V=root:0:VPN_Test_TSw1:348: sent IKE msg (keepalive): 192.168.2.2:4500->105.109.199.30:4500, len=1, vrf=0, id=ff00000000000000/a100000000000000
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: IPsec SA connect 5 192.168.2.2->105.109.199.30:4500
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: using existing connection
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: config found
ike V=root:0:VPN_Test_TSw1: request is on the queue
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: IPsec SA connect 5 192.168.2.2->105.109.199.30:4500
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: using existing connection
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: config found
ike V=root:0:VPN_Test_TSw1: request is on the queue
ike V=root:0:VPN_Test_TSw1: NAT keep-alive 5 192.168.2.2->105.109.199.30:4500.
ike 0:VPN_Test_TSw1:348: out FF
ike V=root:0:VPN_Test_TSw1:348: sent IKE msg (keepalive): 192.168.2.2:4500->105.109.199.30:4500, len=1, vrf=0, id=ff00000000000000/4100000000000000
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: IPsec SA connect 5 192.168.2.2->105.109.199.30:4500
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: using existing connection
ike V=root:0:VPN_Test_TSw1:VPN_Test_TSw1: config found
ike V=root:0:VPN_Test_TSw1: request is on the queue
ike V=root:0:VPN_Test_TSw1:348::1056: cfg-mode negotiation failed due to retry timeout
ike V=root:0:VPN_Test_TSw1:348: schedule delete of IKE SA f28a0d09e11de14b/d5eae735d8a51bc4
ike V=root:0:VPN_Test_TSw1:348: scheduled delete of IKE SA f28a0d09e11de14b/d5eae735d8a51bc4
ike V=root:0:VPN_Test_TSw1:348: send IKE SA delete f28a0d09e11de14b/d5eae735d8a51bc4
ike 0:VPN_Test_TSw1:348: enc F28A0D09E11DE14BD5EAE735D8A51BC4081005016D56EA00000000500C000018E15FA6A6BAE56070DB4899BF84F19278AE1F2B450000001C0000000101100001F28A0
D09E11DE14BD5EAE735D8A51BC4
ike 0:VPN_Test_TSw1:348: out F28A0D09E11DE14BD5EAE735D8A51BC4081005016D56EA000000005C8CC3C9FCE135981B9E5E3C803B368D80E28DBF01D2DFCCFAECF3AB25EB2BBDA8736A242845B1D
8C3B411637D5915377ABBDCB2FC34C074C3E7C05EC0E59CACDC
ike V=root:0:VPN_Test_TSw1:348: sent IKE msg (ISAKMP SA DELETE-NOTIFY): 192.168.2.2:4500->105.109.199.30:4500, len=92, vrf=0, id=f28a0d09e11de14b/d5eae735d8a51bc4
:6d56ea00
ike V=root:0:VPN_Test_TSw1: connection expiring due to phase1 down
ike V=root:0:VPN_Test_TSw1: going to be deleted
ike V=root:0:VPN_Test_TSw1: reset NAT-T
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @Borys_DE ,
You are getting peer has not completed Configuration Method error which means mode config is enabled on one peer but disabled on other.
please check the mode config settings ok both peers.
Nivedha Balasubramanian
Labels
-
FortiGate
10,670 -
FortiClient
2,174 -
FortiManager
896 -
5.2
687 -
FortiAnalyzer
683 -
5.4
638 -
FortiSwitch
590 -
FortiClient EMS
570 -
FortiAP
562 -
IPsec
424 -
6.0
416 -
SSL-VPN
386 -
FortiMail
374 -
5.6
362 -
FortiNAC
288 -
FortiWeb
253 -
6.2
251 -
FortiAuthenticator v5.5
234 -
SD-WAN
198 -
FortiAuthenticator
180 -
FortiGuard
160 -
5.0
152 -
Firewall policy
145 -
FortiGate-VM
134 -
6.4
128 -
FortiCloud Products
116 -
FortiToken
114 -
FortiSIEM
113 -
FortiGateCloud
112 -
Wireless Controller
95 -
Customer Service
88 -
High Availability
87 -
FortiProxy
78 -
ZTNA
77 -
Routing
75 -
SAML
74 -
Fortivoice
73 -
DNS
72 -
VLAN
72 -
FortiEDR
70 -
BGP
70 -
Authentication
69 -
FortiADC
68 -
Certificate
66 -
RADIUS
62 -
LDAP
61 -
fortilink
57 -
SSO
54 -
NAT
54 -
FortiSandbox
53 -
FortiExtender
52 -
4.0MR3
49 -
vdom
48 -
Interface
46 -
Application control
46 -
FortiDNS
43 -
Logging
41 -
Virtual IP
41 -
FortiGate v5.4
38 -
FortiSwitch v6.4
38 -
FortiPAM
37 -
SSL SSH inspection
36 -
FortiConnect
35 -
Web profile
35 -
Automation
33 -
FortiWAN
31 -
FortiConverter
30 -
FortiGate v5.2
28 -
Traffic shaping
26 -
API
26 -
Static route
26 -
SNMP
25 -
SSID
25 -
FortiSwitch v6.2
23 -
FortiPortal
23 -
Fortigate Cloud
23 -
System settings
22 -
WAN optimization
21 -
FortiMonitor
20 -
OSPF
20 -
Security profile
19 -
Web rating
19 -
FortiSoar
18 -
Web application firewall profile
18 -
IP address management - IPAM
18 -
FortiGate v5.0
16 -
FortiDDoS
16 -
Explicit proxy
16 -
FortiAP profile
16 -
Admin
15 -
IPS signature
15 -
Proxy policy
15 -
Intrusion prevention
15 -
FortiCASB
14 -
NAC policy
14 -
FortiManager v4.0
13 -
DNS filter
13 -
FortiManager v5.0
12 -
FortiDeceptor
12 -
users
12 -
Traffic shaping policy
12 -
Fabric connector
12 -
Port policy
12 -
FortiBridge
11 -
FortiRecorder
11 -
FortiAnalyzer v5.0
10 -
FortiWeb v5.0
10 -
Trunk
10 -
Traffic shaping profile
10 -
Authentication rule and scheme
10 -
Fortinet Engage Partner Program
10 -
FortiGate v4.0 MR3
9 -
RMA Information and Announcements
9 -
Antivirus profile
9 -
FortiCache
8 -
FortiToken Cloud
8 -
4.0
7 -
4.0MR2
7 -
Packet capture
7 -
Application signature
7 -
VoIP profile
7 -
Vulnerability Management
7 -
FortiScan
6 -
FortiCarrier
5 -
FortiNDR
5 -
FortiTester
5 -
DLP profile
5 -
DLP sensor
5 -
DoS policy
5 -
Email filter profile
5 -
Protocol option
5 -
TACACS
5 -
Cloud Management Security
5 -
3.6
4 -
FortiDirector
4 -
Internet service database
4 -
DLP Dictionary
4 -
Netflow
4 -
Replacement messages
4 -
SDN connector
4 -
Service
4 -
Multicast routing
4 -
FortiDB
3 -
FortiHypervisor
3 -
FortiAI
3 -
Kerberos
3 -
File filter
3 -
Multicast policy
3 -
FortiEdge Cloud
3 -
FortiInsight
2 -
Video Filter
2 -
Schedule
2 -
ICAP profile
2 -
Zone
2 -
Lacework
2 -
FortiGuest
2 -
4.0MR1
1 -
FortiManager-VM
1 -
FortiCWP
1 -
Subscription Renewal Policy
1 -
FortiSASE
1 -
Virtual wire pair
1 -
FortiEdge
1 -
FortiAIOps
1
Top Kudoed Authors
| User | Count |
|---|---|
| 2624 | |
| 1393 | |
| 804 | |
| 670 | |
| 455 |
Broad. Integrated. Automated.
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.
Security Research
Company
News & Articles
Copyright 2025 Fortinet, Inc. All Rights Reserved.