What exactly causes "Removing peer from peer table failed, no match" on ASA

Unanswered Question
Jan 22nd, 2009


ASA1 <--> ASA2 VPN tunnel stable, works fine. One end has Internet issues and once resolved, the L2L tunnel took some time to establish. ASAs logging messages, "Removing peer from peer table failed, no match!". What exactly cause this issue ?

Thank you


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
fortis123 Fri, 01/23/2009 - 11:49

Hi Andrew,

Thanks for the reply.. but the l2L VPN has been in place from long time. The issue was observerved only when the interent has issues for some time recovered. IPs are inplace.

Nothing to do with Remote client session.



vdoisan Fri, 01/23/2009 - 13:44

same problem here b/n ASA and 1841s in hub/spokes config, caused by power or Internet outages.

I reestablish the connection via "clear crypto ipsec sa" command on the hub (ASA 5510), but I did not find a cause yet

m-ketchum Mon, 11/02/2009 - 15:04

Have you found a cause for this? I've seen the same too in a very similar setup.

darthnul Mon, 11/02/2009 - 16:57

This is pretty much a generic log that occurs after an IPSEC negotiation fails for just about any reason. Turn on debugging and look at the messages preceding this to find out why that particular negotiation failed. This message is generated by the cleanup routine that follows a failed negotiation. It can't find an entry in the table because the negotiation failed before it put an entry in the table.

Patrick0711 Mon, 11/02/2009 - 20:26

Run 'debug crypto isak 254' to find out what triggered this event.

Or configure a logging list to just capture vpn debugging messages.


This Discussion