- 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 "Received notify: INVALID ID INFO" event log error?
12/20/2019 
1,323 People found this article helpful
217,116 Views
Description
The log shows "Received notify: INVALID_ID_INFO" on the initiator firewall.
Resolution
INVALID_ID_INFO can occur both in Phase 1 and in Phase 2 of building up a VPN tunnel.
In Phase 1
The SonicWall received notification that the Phase 1 ID is invalid.
This is most likely to happen on an Aggressive Mode request error. Check that aggressive mode is set in the SA of both SonicWalls.
On SonicOS Enhanced firmware, you can set local and peer (remote) IKE ID's according to IP address, domain name, email address or SonicWall identifier (UFI).
In case of a Main mode tunnel, this error can be seen when the appliance at one end is behind a NAT device. SonicWall UTM appliances use their WAN IP as IKE ID by default and are expecting the other side's public IP as remote IKE ID. On SonicOS enhanced firmware, you can reconfigure the Local / Peer IKE ID with the correct IP address, or specify another parameter such as domain name, email address or UFI.
In Phase 2
This is always a case whereby Local and Destination networks do not match on either side. Please ensure the VPN policies on both Units are configured with the correct Destination and Local networks.
TIP: For more detailed information regarding Site to Site Configuration, please refer to the following KB: Types of Site to Site VPN Scenarios and Configurations
Related Articles
- Bandwidth usage and tracking in SonicWall
- 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.
Categories
- Firewalls > SonicWall SuperMassive 9000 Series > Logging/Alerts
- Firewalls > SonicWall SuperMassive E10000 Series > Logging/Alerts
- Firewalls > TZ Series > Logging/Alerts
- Firewalls > NSa Series > Logging/Alerts
- Firewalls > NSv Series > Logging/Alerts
YES
NO