Got it

IPSEC_INBOUND_SA_MISS

Created: Oct 23, 2020 07:14:57Latest reply: Oct 23, 2020 07:15:31 3063 1 0 0 0
  Rewarded HiCoins: 0 (problem resolved)

Hi all,

I found a lot of IPSEC_INBOUND_SA_MISS messages on AR. May I know the main cause of this message appearing?

xx.xx.10.2, SPI: 4864313, Protocal: esp) Oct 23 2020 01:04:07+00:00 DISJAYA-VPN-ROUTER %IPSEC/5/IPSEC_INBOUND_SA_MISS(l)[20152249]:Received an inbound sa miss message. (Source address: 10.81.36.189, Destination address:

xx.xx.10.2, SPI: 5533528, Protocal: esp) Oct 23 2020 01:04:07+00:00 DISJAYA-VPN-ROUTER %IPSEC/5/IPSEC_INBOUND_SA_MISS(l)[20152250]:Received an inbound sa miss message. (Source address: 172.27.195.20, Destination address:

xx.xx.28.78, SPI: 592408, Protocal: esp) Oct 23 2020 01:04:07+00:00 DISJAYA-VPN-ROUTER %IPSEC/5/IPSEC_INBOUND_SA_MISS(l)[20152251]:Received an inbound sa miss message. (Source address: 10.81.36.18, Destination address:

xx.xx.10.2, SPI: 14165513, Protocal: esp) Oct 23 2020 01:04:07+00:00 DISJAYA-VPN-ROUTER %IPSEC/5/IPSEC_INBOUND_SA_MISS(l)[20152252]:Received an inbound sa miss message. (Source address: 10.81.36.86, Destination address:

xx.xx.10.2, SPI: 6883249, Protocal: esp) Oct 23 2020 01:04:07+00:00 DISJAYA-VPN-ROUTER %IPSEC/5/IPSEC_INBOUND_SA_MISS(l)[20152253]:Received an inbound sa miss message. (Source address: 10.81.35.136, Destination address:

Featured Answers

Recommended answer

Popeye_Wang
Admin Created Oct 23, 2020 07:15:31

Hello,

The Possible Cause is that the device fails to decapsulate IPSec-encrypted packets received from its peer. 

Refer to  https://support.huawei.com/hedex/hdx.do?docid=EDOC1100007335&id=IPSec_5_IPSEC_INBOUND_SA_MISS&lang=en

When you operate the device, if the SA of the two sides is not deleted at the same time can also create a lot of such logs.

The log doesn't affect IPsec establishment, if the service is normal, you can ignore the log.

View more
  • x
  • convention:

All Answers

Hello,

The Possible Cause is that the device fails to decapsulate IPSec-encrypted packets received from its peer. 

Refer to  https://support.huawei.com/hedex/hdx.do?docid=EDOC1100007335&id=IPSec_5_IPSEC_INBOUND_SA_MISS&lang=en

When you operate the device, if the SA of the two sides is not deleted at the same time can also create a lot of such logs.

The log doesn't affect IPsec establishment, if the service is normal, you can ignore the log.

View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.