Advertisement

12.01.2008 at 02:02PM PST, ID: 23948219
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.2

help with Cisco site to site VPN: Error: All IPSec proposals found unacceptable

Asked by clearacid in Cisco PIX Firewall, Virtual Private Networking (VPN), IPSec Security Protocol

Tags: , ,

Guys,

I'm trying to setup this site to site vpn using the IPSEC VPN Wizard between an ASA5510 and an ASA5505 but I keep getting the same error.

Output from debug crypto ipsec / isakmp on ASA5510 when a PC on the ASA5505 firewall was trying to ping to a PC on the ASA5510 firewall

Dec 01 13:18:09 [IKEv1]: Group = 2.2.2.2, IP = 2.2.2.2, QM FSM error (P2 struct &0xd6306280, mess id 0xc9de71d2)!
Dec 01 13:18:09 [IKEv1]: Group = 2.2.2.2, IP = 2.2.2.2, Removing peer from correlator table failed, no match!
Dec 01 13:18:15 [IKEv1]: Group = 2.2.2.2, IP = 2.2.2.2, QM FSM error (P2 struct &0xd62fcc38, mess id 0xb8a57ff6)!
Dec 01 13:18:15 [IKEv1]: Group = 2.2.2.2, IP = 2.2.2.2, Removing peer from correlator table failed, no match!
Dec 01 13:18:20 [IKEv1]: Group = 2.2.2.2, IP = 2.2.2.2, QM FSM error (P2 struct &0xd62fcc38, mess id 0x9050819c)!
Dec 01 13:18:20 [IKEv1]: Group = 2.2.2.2, IP = 2.2.2.2, Removing peer from correlator table failed, no match!


Googling "QM FSM error" it tells me that there might be an ACL mismatch

-----------------------------------------------------

From ASA5510
Comparing the Start and the Run configurations this was what was entered:

access-list outside_1_cryptomap_1 extended permit ip 10.1.0.0 255.255.255.0 10.2.0.0 255.255.255.0
access-list inside_nat0_outbound extended permit ip 10.1.0.0 255.255.255.0 10.2.0.0 255.255.255.0
nat (inside) 0 access-list inside_nat0_outbound
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto map outside_map 1 match address outside_1_cryptomap_1
crypto map outside_map 1 set pfs
crypto map outside_map 1 set peer 2.2.2.2
crypto map outside_map 1 set transform-set ESP-3DES-SHA
crypto map outside_map interface outside
crypto isakmp enable outside
 authentication pre-share
 encryption 3des
 hash sha
 group 2
 lifetime 86400
tunnel-group 2.2.2.2 type ipsec-l2l
tunnel-group 2.2.2.2 ipsec-attributes
 pre-shared-key *************

From ASA5505
Comparing the Start and the Run configurations this was what was entered:

access-list outside_1_cryptomap extended permit ip 10.2.0.0 255.255.255.0 10.1.0.0 255.255.255.0
access-list inside_nat0_outbound extended permit ip 10.2.0.0 255.255.255.0 10.1.0.0 255.255.255.0
nat (inside) 0 access-list inside_nat0_outbound
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac

crypto map outside_map 1 match address outside_1_cryptomap

crypto map outside_map 1 set pfs group1

crypto map outside_map 1 set peer 1.1.1.1

crypto map outside_map 1 set transform-set ESP-3DES-SHA

crypto map outside_map interface outside

crypto isakmp enable outside

crypto isakmp policy 10

 authentication pre-share

 encryption 3des

 hash sha

 group 2
 lifetime 86400
tunnel-group 1.1.1.1 type ipsec-l2l

tunnel-group 1.1.1.1 ipsec-attributes

 pre-shared-key *************

-------------------------------------------------------

IP Address information:

ASA5510:
INSIDE: 10.1.0.0/24
OUTSIDE: 1.1.1.1

ASA5505:
INSIDE: 10.2.0.0/24
OUTSIDE: 2.2.2.2

This is setup is currently in our testing area.  I've verified communications (firewalls can ping each other).

When I attempt to ping from inside to the other network through the L2L I get the same error messages from both firewalls.

Start Free Trial
 
Loading Advertisement...
 
[+][-]12.01.2008 at 02:46PM PST, ID: 23073211

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]12.01.2008 at 06:17PM PST, ID: 23074096

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Cisco PIX Firewall, Virtual Private Networking (VPN), IPSec Security Protocol
Tags: Cisco, ASA Firewall, site to site vpn
Sign Up Now!
Solution Provided By: lrmoore
Participating Experts: 2
Solution Grade: A
 
 
[+][-]12.01.2008 at 07:08PM PST, ID: 23074267

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 7-day free trial to view this Author Comment or ask the Experts your question.

 
 
Loading Advertisement...
20081119-EE-VQP-49 - Hierarchy / EE_QW_2_20070628