The peer gateway sent a DELETE payload for the IPSEC SA. Causes and Solutions for an IPsec VPN Tunnel Is Down Alarm Reason for the IPsec VPN Tunnel Down Alarm Verify that the VPN session on the NSX Edge node where HA peer SR is in the Active state. Verify if the Admin Status in the IPsec VPN service configuration is disabled.Įnable the session to resolve this error. Status of the VPN service used for the session is not active.
Verify that the peer configuration has at least one of the gateways set to Initiator.Verify that the Connection Initiation Mode property in the session configuration is set to Responder.Resolve the error using the reason displayed in the session dump under Session_Config_Fail_Reason. The reason is listed in the session dump under Session_Config_Fail_Reason. The session configuration realization failed in NSX Edge due to some constraints or certain criteria. To debug the invalid SPI value, analyze the logs. To debug the invalid syntax, analyze the logs.Īn invalid SPI value was received in the IKE payload. IKE proposals or transforms are not formed correctly.Verify the connectivity to the remote gateway.To determine why the peer gateway sent a DELETE payload, examine the logs in the NSX Edge and on the peer gateway side. The peer gateway initiated a delete case. The IKE transform configuration in both the local and peer configuration file are inconsistent.Įnsure that the following properties are configured the same for both gateways. It must match exactly in both the VPN gateways. The Local ID value must be set as the Remote ID value in the peer VPN gateway.
Verify the Local ID and Remote ID values.Authentication of the IKE SA depends on the pre-shared key, Local ID, and Remote ID values. The IKE SA establishment between the VPN gateways failed due to a failure in authentication. Necessary Actions to Resolve the Alarm Message Causes and Solutions for an IPsec VPN Session Is Down Alarm Reason for the IPsec VPN Session Down Alarm
0 kommentar(er)
