- Products
- Network Security
- Threat Protection
- Secure Access Service Edge (SASE)
- Cloud Security
- Endpoint Security
- Email Security
- Secure Access
-
Wi-Fi 6 Access Points
SonicWall SonicWave 600 series access points provide always-on, always-secure connectivity for complex, multi-device environments.
Read More
- Solutions
- Industries
- Use Cases
- Solutions Widgets
- Solutions Content Widgets
Federal
Protect Federal Agencies and Networks with scalable, purpose-built cybersecurity solutions
- Solutions Image Widgets
-
- Partners
- SonicWall Partners
- Partner Resources
- Partner Widgets
- Custom HTML : Partners Content WIdgets
Partner Portal
Access to deal registration, MDF, sales and marketing tools, training and more
- Partners Image Widgets
-
- Support
- Support
- Resources
- Capture Labs
- Support Widget
- Custom HTML : Support Content WIdgets
Support Portal
Find answers to your questions by searching across our knowledge base, community, technical documentation and video tutorials
- Support Image Widgets
-
- COMPANY
- PROMOTIONS
- MANAGED SERVICES
- Contact Sales
-
- Menu
- Solutions
- Solutions Widgets
- Solutions Image Widgets
-
- Solutions Widgets
- Partners
- Partner Widgets
- Partners Image Widgets
-
- Partner Widgets
- Support
- Support Widget
- Support Image Widgets
-
- Support Widget
- Solutions
- Solutions Widgets
- Solutions Image Widgets
-
- Solutions Widgets
- Partners
- Partner Widgets
- Partners Image Widgets
-
- Partner Widgets
- Support
- Support Widget
- Support Image Widgets
-
- Support Widget
How to Solve - IKEV2 Out Of Memory Error In Logs
08/03/2020 
20 People found this article helpful
192,424 Views
Description
This article details the rare symptoms of IKEv2 Out of Memory error and how to resolve it.
Symptoms:
IKEv2 VPN Tunnel interfaces are not able to re-negotiate once SA lifetime expires. GUI Logs display IKEv2 Out of Memory error, a reboot is required to re-establish existing tunnel(s) once firewall runs out of memory. These symptoms are due to a misconfiguration caused by binding the VPN to an incorrect interface. The tunnel can never establish locally with this misconfiguration in place although the remote end of the tunnel may have hardware that shows the tunnel as up while the tunnel re-negotiates. After thousands of attempts to complete a successful phase one negotiation and the firewall has been left in this misconfigured state for an extended period of time the memory allocated for phase one negotiations will run out. The firewall can no longer process IKEv2 phase 1 negotiations in this condition until there is a restart or the misconfiguration is corrected.
Cause
The following conditions exist for this error:
1) VPN is bound to an incorrect interface for an extended period of time, more than one day.
2) The incorrect interface selected is not a WAN interface
3) The VPN tunnel has an all zero gateway (0.0.0.0) (Tunnel Interface)
4) More than one tunnel interface must exist, to impact other tunnel interface phase one negotiations.
Resolution
Check through any configured IKEv2 tunnel interface VPN and be sure the correct local WAN interface has been selected within the VPN tunnel configuration. There is no need to check tunnels known to be working as expected. A VPN tunnel can not establish when it has been bound to an incorrect interface so first check tunnels that were never active.
ISSUE ID:
215736
Related Articles
- How to force an update of the Security Services Signatures from the Firewall GUI
- Configure Guest VLAN in the TZ firewall, for guest users to access Internet only.
- How to Setup the SonicWave 600 series
Categories
- Firewalls > SonicWall SuperMassive E10000 Series
- Firewalls > NSa Series
- Firewalls > TZ Series
- Firewalls > NSsp Series
- Firewalls > SonicWall SuperMassive 9000 Series
YES
NO