cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4931
Views
0
Helpful
5
Replies

Phase 1 completed, but why not phase 2? Configs included.

JonCommins
Level 1
Level 1

I have two ASAs.

The first one gets its WAN IP via DHCP. The second one is static. Therefore my aim is a dynamic tunnel.

Here is the configuration for the first: http://pastebin.com/raw.php?i=guGPmjEU
And the second: http://pastebin.com/raw.php?i=djsPsbsm

Inside subnet of the first ASA: 10.75.0.0/16
Inside subnet of the second ASA: 10.80.0.0/16

"crypto map PG_TUNNEL_MAP 11" in the first ASA config, is for the tunnel to the second (static) ASA.

And here is the debug output I see (debug crypto <isakmp/ipsec> 127) on the second ASA when I send interesting traffic from the first ASA:
http://pastebin.com/raw.php?i=MSTkJ379

How come phase 2 does not complete?

1 Accepted Solution

Accepted Solutions

The QM FSM error seems to be the failing point. That can be caused either by mismatch in proxy identities (those look ok) or transform set parameters.

For the latter, KAMLOOPS is using:

crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac

while VMON-ASA is using:

crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set pfs group1
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA ESP-3DES-MD5 ESP-DES-SHA ESP-DES-MD5

So you might try removing the pfs parameter in VMON-ASA's dynamic-map.

View solution in original post

5 Replies 5

Jon Marshall
Hall of Fame
Hall of Fame

From your second ASA configuration -

access-list PG_Tunnel extended permit ip object-group DM_INLINE_NETWORK_1 10.70.0.0 255.255.0.0

shouldn't it be "10.75.0.0 255.255.0.0" ?

Jon
 

No, because "crypto map ___ 21" on the second ASA references that access-list. And crypto map 21 is a static map. This tunnel we're discussing is dynamic. Any other ideas?

The QM FSM error seems to be the failing point. That can be caused either by mismatch in proxy identities (those look ok) or transform set parameters.

For the latter, KAMLOOPS is using:

crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac

while VMON-ASA is using:

crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set pfs group1
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA ESP-3DES-MD5 ESP-DES-SHA ESP-DES-MD5

So you might try removing the pfs parameter in VMON-ASA's dynamic-map.

I ran the following on VMON-ASA:

no crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set pfs group1

Then I sent some interesting traffic and the tunnel came up!

Thank you!!

 

You're welcome. Glad to hear it worked.

Thanks for the rating.