05-12-2016 01:04 AM - edited 02-21-2020 08:48 PM
Out of sudden IPSEC tunnel to remote site 202.68.211.20 is not connect. Previously is OK. There is no config changes.
IKE Phase 1 not even connect.
I do a debug, but i don't know what might be the error.
-----------------------------------------------------------------------------
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2016.05.12 15:19:36 =~=~=~=~=~=~=~=~=~=~=~=
May 12 12:06:50 [IKEv1 DEBUG]: Pitcher: received a key acquire message, spi 0x0
May 12 12:06:50 [IKEv1]: IP = 202.68.211.20, Queuing KEY-ACQUIRE messages to be processed when P1 SA is complete.
May 12 12:06:53 [IKEv1 DEBUG]: Pitcher: received a key acquire message, spi 0x0
May 12 12:06:53 [IKEv1]: IP = 202.68.211.20, Queuing KEY-ACQUIRE messages to be processed when P1 SA is complete.
May 12 12:06:54 [IKEv1 DEBUG]: IP = 202.68.211.20, IKE MM Initiator FSM error history (struct &0xd84aff40) <state>, <event>: MM_DONE, EV_ERROR-->MM_WAIT_MSG2, EV_RETRY-->MM_WAIT_MSG2, EV_TIMEOUT-->MM_WAIT_MSG2, NullEvent-->MM_SND_MSG1, EV_SND_MSG-->MM_SND_MSG1, EV_START_TMR-->MM_SND_MSG1, EV_RESEND_MSG-->MM_WAIT_MSG2, EV_RETRY
May 12 12:06:54 [IKEv1 DEBUG]: IP = 202.68.211.20, IKE SA MM:914f04ce terminating: flags 0x01000022, refcnt 0, tuncnt 0
May 12 12:06:54 [IKEv1 DEBUG]: IP = 202.68.211.20, sending delete/delete with reason message
May 12 12:06:59 [IKEv1 DEBUG]: Pitcher: received a key acquire message, spi 0x0
May 12 12:06:59 [IKEv1]: IP = 202.68.211.20, IKE Initiator: New Phase 1, Intf internal, IKE Peer 202.68.211.20 local Proxy Address 10.215.20.0, remote Proxy Address 10.210.0.0, Crypto map (VPN_map)
May 12 12:06:59 [IKEv1 DEBUG]: IP = 202.68.211.20, constructing ISAKMP SA payload
May 12 12:06:59 [IKEv1 DEBUG]: IP = 202.68.211.20, constructing Fragmentation VID + extended capabilities payload
May 12 12:06:59 [IKEv1]: IP = 202.68.211.20, IKE_DECODE SENDING Message (msgid=0) with payloads : HDR + SA (1) + VENDOR (13) + NONE (0) total length : 112
May 12 12:07:00 [IKEv1 DEBUG]: Pitcher: received a key acquire message, spi 0x0
May 12 12:07:00 [IKEv1]: IP = 202.68.211.20, Queuing KEY-ACQUIRE messages to be processed when P1 SA is complete.
May 12 12:07:03 [IKEv1 DEBUG]: Pitcher: received a key acquire message, spi 0x0
May 12 12:07:03 [IKEv1]: IP = 202.68.211.20, Queuing KEY-ACQUIRE messages to be processed when P1 SA is complete.
May 12 12:07:07 [IKEv1]: IP = 202.68.211.20, IKE_DECODE RESENDING Message (msgid=0) with payloads : HDR + SA (1) + VENDOR (13) + NONE (0) total length : 112
May 12 12:07:09 [IKEv1 DEBUG]: Pitcher: received a key acquire message, spi 0x0
May 12 12:07:09 [IKEv1]: IP = 202.68.211.20, Queuing KEY-ACQUIRE messages to be processed when P1 SA is complete.
May 12 12:07:15 [IKEv1]: IP = 202.68.211.20, IKE_DECODE RESENDING Message (msgid=0) with payloads : HDR + SA (1) + VENDOR (13) + NONE (0) total length : 112
May 12 12:07:23 [IKEv1]: IP = 202.68.211.20, IKE_DECODE RESENDING Message (msgid=0) with payloads : HDR + SA (1) + VENDOR (13) + NONE (0) total length : 112
May 12 12:07:31 [IKEv1 DEBUG]: IP = 202.68.211.20, IKE MM Initiator FSM error history (struct &0xd8457958) <state>, <event>: MM_DONE, EV_ERROR-->MM_WAIT_MSG2, EV_RETRY-->MM_WAIT_MSG2, EV_TIMEOUT-->MM_WAIT_MSG2, NullEvent-->MM_SND_MSG1, EV_SND_MSG-->MM_SND_MSG1, EV_START_TMR-->MM_SND_MSG1, EV_RESEND_MSG-->MM_WAIT_MSG2, EV_RETRY
May 12 12:07:31 [IKEv1 DEBUG]: IP = 202.68.211.20, IKE SA MM:be63ea64 terminating: flags 0x01000022, refcnt 0, tuncnt 0
May 12 12:07:31 [IKEv1 DEBUG]: IP = 202.68.211.20, sending delete/delete with reason message
May 12 12:07:37 [IKEv1 DEBUG]: Pitcher: received a key acquire message, spi 0x0
May 12 12:07:37 [IKEv1]: IP = 202.68.211.20, IKE Initiator: New Phase 1, Intf internal, IKE Peer 202.68.211.20 local Proxy Address 10.215.20.0, remote Proxy Address 10.210.0.0, Crypto map (VPN_map)
May 12 12:07:37 [IKEv1 DEBUG]: IP = 202.68.211.20, constructing ISAKMP SA payload
May 12 12:07:37 [IKEv1 DEBUG]: IP = 202.68.211.20, constructing Fragmentation VID + extended capabilities payload
May 12 12:07:37 [IKEv1]: IP = 202.68.211.20, IKE_DECODE SENDING Message (msgid=0) with payloads : HDR + SA (1) + VENDOR (13) + NONE (0) total length : 112
May 12 12:07:40 [IKEv1 DEBUG]: Pitcher: received a key acquire message, spi 0x0
May 12 12:07:40 [IKEv1]: IP = 202.68.211.20, Queuing KEY-ACQUIRE messages to be processed when P1 SA is complete.
May 12 12:07:45 [IKEv1]: IP = 202.68.211.20, IKE_DECODE RESENDING Message (msgid=0) with payloads : HDR + SA (1) + VENDOR (13) + NONE (0) total length : 112
May 12 12:07:46 [IKEv1 DEBUG]: Pitcher: received a key acquire message, spi 0x0
May 12 12:07:46 [IKEv1]: IP = 202.68.211.20, Queuing KEY-ACQUIRE messages to be processed when P1 SA is complete.
May 12 12:07:53 [IKEv1]: IP = 202.68.211.20, IKE_DECODE RESENDING Message (msgid=0) with payloads : HDR + SA (1) + VENDOR (13) + NONE (0) total length : 112
q
Solved! Go to Solution.
05-12-2016 01:10 AM
Hi,
It seems the tunnel is stuck at MSG_2.
Can you check if UDP 500 traffic is not blocked between the peers ?
Please check with your service provider.
Regards,
Aditya
Please rate helpful posts and mark correct answers.
05-12-2016 01:10 AM
Hi,
It seems the tunnel is stuck at MSG_2.
Can you check if UDP 500 traffic is not blocked between the peers ?
Please check with your service provider.
Regards,
Aditya
Please rate helpful posts and mark correct answers.
05-12-2016 01:15 AM
Both site no config changes, and the connection is disconnected.
Sure, i will make a call to the ISP.
Will update the finding
05-13-2016 09:58 PM
turn out it is ISP problem. Once reported, the check backend and the VPN connection is restored.
TQ
12-04-2019 11:37 AM
I'm facing the same problem too, we have the redundant VPN connections configured and when disconnecting the primary VPN connections redundant VPN connection goes to MM_WAITMSG2 state
12-04-2019 11:42 AM
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