ASA 5510 TO CISCO 3845 IPSEC VPN MM_WAIT_MSG2 / MM_NO_STATE
we are trying to establish IPsec VPN between two locations from ASA 5510 to Cisco 3845 and the setup is as follows:
The ASA receives a PPPoE dynamic public address from the Service provider A through a Cisco 1941 router set up as a bridge. All standard IPsec VPN policies ie interesting traffic, crypto maps etc are implemented on the ASA and the software version is 8.4(1). Existing users on the LAN also access a cloud based service on the Internet by means of dynamic NAT to the cloud service. The IPsec session is set up to peer to the remote site public IP which is provided by Service Provider B
The Cisco router is connected to the Service Provider B firewall through a local gateway. Service Provider B provides a Static IP address which is used as the peer IP address from the ASA. All IPsec policies are implemented on Cisco 3845 router which is in the private network. The Cisco 3845 is configured with a default route to the provider firewall using Private IP as the next hop. The Service Provider B also implement 1:1 NAT to translate incoming session requests to the public IP and also NAT Traversal.
The scenario is depicted as follows:
Customer LAN/WLAN -> ASA-> Bridge -> PPPoE (SP A) --------------------------(SP B) Firewall -> Default Gateway -> Cisco IOS 3845
Public IP Public IP +NAT+NAT-traversal VPN Policies
If a VPN tunnel is initiated by a ping from the Cisco 3845 end, the crypto isakmp sa output shows MM_NO_STATE
If a VPN tunnel is initiated by a ping from the ASA end the crypto ikev1 sa output shows MM_WAIT_MSG2.
The state above describes that both the devices have sent their IKE requests and as there is no response from the remote end, the state information is set to either MSG2 at ASA end or NO_STATE on the 3845.
The extract of the log capture on the ASA is as follows:
[IKEv1 DEBUG]IP = 22.214.171.124, IKE MM Initiator FSM error history (struct &0xade91ce0) <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
Jun 08 12:01:32 [IKEv1 DEBUG]IP = 126.96.36.199, IKE SA MM:98976544 terminating: flags 0x01000022, refcnt 0, tuncnt 0
and the IKE fails to establish. Sometimes can see "Duplicate packets" in the log messages.
Suspected problems may be due to
1) Routing related : From the ASA, can ping to the public IP of the SP B, but from Cisco 3845 we cannot ping to the public IP of ASA
2) ASA users are connected to a cloud based service on the Internet and advise needed if some kind of split tunneling is required for IPsec traffic
and any NAT or ACLs required to ensure that IPsec traffic is pushed out through the tunnel.
Currently, interesting traffic is configured to permit IP traffic from LAN A to LAN B and mirror image on the other end.
NAT and ACLs allow icmp inbound to the LAN/WLAN devices and management access is allowed in the ASA for this subnet.
3) ASA version is 8.4(1) is implemented with IKEv1 policies.
Let me know if you need detailed configs and i can send this through
ASA 5510 TO CISCO 3845 IPSEC VPN MM_WAIT_MSG2 / MM_NO_STATE
Thanks very much for your response and we have confirmed with the remote provider that UDP 500, 4500 and ESP 50 traffic is allowed for inbound as well as outbound on their firewalls and there seems to be no improvement.
We have tried this setup with another provider and we got IPsec tunnel come up without any problems. This time i am not sure if a firewall is located at the remote end, but tunnel comes up and seems to be working fine.
We will revert to the original provider and test again and here is the extract of the logs for the failed tests.
%ASA-5-752004: Tunnel Manager dispatching a KEY_ACQUIRE message to IKEv1. Map Tag = ABCD. Map Sequence Number = 10.
%ASA-7-715077: Pitcher: received a key acquire message, spi 0x0
%ASA-5-713041: IP = 188.8.131.52, IKE Initiator: New Phase 1, Intf NP Identity Ifc, IKE Peer X.X.X.X local Proxy Address X.X.X.X, remote Proxy Address X.X.X.X, Crypto map (ABCD)
%ASA-7-715046: IP = 184.108.40.206, constructing ISAKMP SA payload
%ASA-7-715046: IP = 220.127.116.11, constructing NAT-Traversal VID ver 02 payload
%ASA-7-715046: IP = 18.104.22.168, constructing NAT-Traversal VID ver 03 payload
%ASA-7-715046: IP = 22.214.171.124, constructing NAT-Traversal VID ver RFC payload
%ASA-7-715046: IP = 126.96.36.199, constructing Fragmentation VID + extended capabilities payload
%ASA-7-713236: IP = 188.8.131.52, IKE_DECODE SENDING Message (msgid=0) with payloads : HDR + SA (1) + VENDOR (13) + VENDOR (13) + VENDOR (13) + VENDOR (13) + NONE (0) total length : 168
%ASA-7-609001: Built local-host identity:184.108.40.206
%ASA-7-609001: Built local-host Outside:220.127.116.11
%ASA-7-715065: IP = 18.104.22.168, IKE MM Initiator FSM error history (struct &0xadef3480) , : 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
%ASA-7-713906: IP = 22.214.171.124, IKE SA MM:6c33e07d terminating: flags 0x01000022, refcnt 0, tuncnt 0
%ASA-7-713906: IP = 126.96.36.199, sending delete/delete with reason message
%ASA-4-752012: IKEv1 was unsuccessful at setting up a tunnel. Map Tag = MELSYD. Map Sequence Number = 10.
%ASA-3-752015: Tunnel Manager has failed to establish an L2L SA. All configured IKE versions failed to establish the tunnel. Map Tag= MELSYD. Map Sequence Number = 10.
%ASA-7-752002: Tunnel Manager Removed entry. Map Tag = ABCD. Map Sequence Number = 10
188.8.131.52 is the local IP on ASA and 184.108.40.206 is the remote IP on the SP firewall. From the ASA, i can ping to 210.x.x.x, but from the remote VPN router i cannot ping to 120.x.x.x (Firewall does NAT 1:1 translation)
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...