> Source: [sk101911](https://support.checkpoint.com/results/sk/sk101911)

# sk101911 - IKE Phase 1 with DAIP device fails after IP address of DAIP device was changed

| Property | Value |
|----------|-------|
| Solution ID | sk101911 |
| Date Created | 2014-08-04 |
| Last Modified | 2025-12-22 |
| Technical Level | General |

## Symptoms

- IKE Phase 1 with DAIP device (e.g., Edge that receives IP address from DHCP server) fails after IP address of DAIP device was changed.

## Cause

DAIP device is able to negotiate the IKE Phase 1, but Security Gateway is not. Therefore, Security Gateway can not send "delete" command since it does not have IKE Phase 1. DAIP device drops "delete" command in clear since it can be DoS.

## Solution

This problem was fixed. The fix is included in:

* [Check Point R80.10](http://supportcontent.checkpoint.com/solutions?id=sk111841)
* [Check Point R77.30](http://supportcontent.checkpoint.com/solutions?id=sk104859)
* [Check Point R77.20 for 600 / 1100 / 1200R](http://supportcontent.checkpoint.com/solutions?id=sk105379)

**Code was improved:** Administrator can configure Security Gateway *not* to initiate IKE Phase 1 with DAIP device (only DAIP device will initiate Main Mode).

For **lower versions** , Check Point can supply a **Hotfix** . [Contact Check Point Support](http://www.checkpoint.com/services/contact/index.html) to get a Hotfix for this issue.  
A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.  
For faster resolution and verification, please collect [CPinfo files](http://supportcontent.checkpoint.com/solutions?id=sk92739) from the Security Management Server and Security Gateways involved in the case.

**Hotfix installation instructions:**

1. Hotfix has to be installed on **Security Gateway**.

   **Note:** In cluster environment, this procedure must be performed on all members of the cluster.   

2. Transfer the hotfix package to the machine (into some directory, e.g., `/some_path_to_fix/`).   

3. Unpack the hotfix package:

   **`[Expert@HostName]# cd /some_path_to_fix/`**   
   **`[Expert@HostName]# tar -zxvf fw1_wrapper_`*HOTFIX_NAME*`.tgz `**   

4. Install the hotfix:

   **`[Expert@HostName]# ./fw1_wrapper_`*HOTFIX_NAME***
   Note: The script will stop all of Check Point services (`cpstop`) - read the output on the screen.   

5. Reboot the machine.   

6. How to control the new behavior:

   * To enable the fix (by default, this fix is disabled):

     1. Set the new key "`no_P1_initiation_with_ROBO`" in Check Point Registry (*$CPDIR/registry/HKLM_registry.data* file):

        **`[Expert@Gateway]# ckp_regedit -a SOFTWARE/CheckPoint/VPN1 no_P1_initiation_with_ROBO -n 1`**   

     2. Restart Check Point services:

        **`[Expert@Gateway]# cpstop ; cpstart`**

     <br />

     <br />

   * To disable the fix:

     1. Remove the new key "`no_P1_initiation_with_ROBO`" from Check Point Registry (*$CPDIR/registry/HKLM_registry.data* file):

        **`[Expert@Gateway]# ckp_regedit -a SOFTWARE/CheckPoint/VPN1 no_P1_initiation_with_ROBO -n 0`**   

     2. Restart Check Point services:

        **`[Expert@Gateway]# cpstop ; cpstart`**

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content