Hello
While checking the tunnel status, it was confirmed that the tx error value steadily increased.
I wonder why you get these symptoms.
And is there a separate command that can only clear the corresponding error value?
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Txe error count can be caused by the following reasons:
- Attempting to send traffic when no IPsec SA has not been negotiated.
- Attempting to send traffic when there is no route to the gateway IP.
- Attempting to send traffic on an IPsec SA that is dead/expired.
- No memory available to add the IPsec header onto the egress packet.
The txe error can also count up if there are phase 2 selectors, and then try to ping a destination not allowed by the selector.
The txe error count will then increment by one for every ping.
Else, drops could be due to large size packets.
For more info please check this link:
IPsec VPN tunnel errors due to traffic no... - Fortinet Community
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1712 | |
1093 | |
752 | |
447 | |
231 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.