Is QOS causing IPSEC replay errors?

Answered Question
Feb 7th, 2007

Should there be a "service-policy" command on the outbound interface when using the "qos pre-classify" under the crypto map?

I have several point-to-point links that use both the qos pre-classify and the service-policy on the interface, and all those links generate %CRYPTO-4-PKT_REPLAY_ERR errors under load.

Other links that only encrypt are not getting the %CRYPTO-4-PKT_REPLAY_ERR errors under load.

The documentation for QOS and VPN:

Only states to use the "qos pre-classify" ???

I believe the packets are going through the QOS process twice. Once before encryption, and then again afterward resulting in the resequencing.

I have this problem too.
0 votes
Correct Answer by kaachary about 9 years 7 months ago


IPSec replay error can also be caused due to a smaller replay window size. You might wanna try in creasing the replay window size.



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
david.chandler Thu, 02/08/2007 - 03:42

Another possibility is that the "qos pre-classify" is just maintaining the orginal packets class after it encrypts. This would mean that the encrypted packets are going through QOS after encryption. (reordering) Many of the documents state the QOS will be done before the encryption, but if that is true I wouldn't be getting replay errors.


This Discussion