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

# sk107595 - PIM neighbor refresh is slow on Check Point Security Gateway / Cluster after neighbor PIM router failover

| Property | Value |
|----------|-------|
| Solution ID | sk107595 |
| Date Created | 2015-09-09 |
| Last Modified | 2023-03-22 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- PIM neighbor refresh is slow on Check Point Security Gateway / Cluster after neighbor PIM router failover:

* After failover of neighboring PIM router (after disconnecting a router link), multicast traffic is recovered after 6 seconds.
* After failback of neighboring PIM router (after reconnecting a router link), multicast traffic is recovered after 10-15 seconds.

## Cause

* When PIM upstream neighbor changes its GenID, it takes a long time to resume traffic due to tear down of join prune state for all groups associated.
* During transitional phase, high volume of multicast traffic causes MFC to register entries as orphans for prolonged period because parent protocol has not fully started.
* Some routers might not react well to unicast Join/Prune messages when upstream neighbor GenID changes.

## Solution

This problem was fixed. The fix is included in:

* [Check Point R80.10](http://supportcontent.checkpoint.com/solutions?id=sk111841)

Check Point recommends to always [upgrade to the most recent version](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=overview&product=184)

For **other [supported](http://www.checkpoint.com/support-services/support-life-cycle-policy/index.html) 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.

**Code was improved (for both PIM Dense Mode and PIM Sparse Mode):**

* \<S,G\> state will not be torn down just because upstream neighbor changed its GenID. State will be retained and refreshed by sending triggered Join/Prune control messages.
* The MFC orphan timeout was shortened to be 5 seconds in VRRP cluster.
* Instead of sending Join/Prune message to neighbor's unicast IP address when upstream neighbor's GenID changes, the Join/Prune message will be sent to ALL PIM ROUTER (224.0.0.13) as IP destination.

**Hotfix installation instructions:**

1. Hotfix has to be installed on ***machine running Gaia OS***.

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

   * Using CPUSE on Gaia OS:

     Refer to [sk92449: CPUSE - Gaia Software Updates (including Gaia Software Updates Agent)](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk92449#How to work with CPUSE):
     * Section "[(4-A-c)](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk92449#How to work with CPUSE - How to download and import a CPUSE package - Import instructions for Offline procedure - Gaia Portal)" / "[(4-A-d)](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk92449#How to work with CPUSE - How to download and import a CPUSE package - Import instructions for Offline procedure - Gaia Clish)" - refer to import instructions for *Offline procedure*
     * Section "[(4-B-a)](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk92449#How to work with CPUSE - How to install a CPUSE package - Installing a Hotfix package / Minor Version package)" - refer to installation instructions for *Hotfixes*

     **Note:** Reboot is required.
   * Using Legacy CLI on Gaia OS:

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

     2. Unpack and install the hotfix package:

        ***\[Expert@HostName:0\]# cd /some_path_to_fix/***   
        ***\[Expert@HostName:0\]# tar -zxvf SecurePlatform_\<HOTFIX_NAME\>.tgz***   
        ***\[Expert@HostName:0\]# ./SecurePlatform_\<HOTFIX_NAME\>***
        **Note:** The script will stop all of Check Point services (*cpstop*) - read the output on the screen.
     3. Reboot the machine.

---

# 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