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

# sk180669 - ClusterXL stops sending multicast PIM traffic after failover or a reboot

| Property | Value |
|----------|-------|
| Solution ID | sk180669 |
| Date Created | 2023-03-12 |
| Last Modified | 2025-03-03 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R81.20, R81.10 (EOS), R81 (EOS) |
| OS | Gaia |

## Symptoms

- * Cluster Member stops sending multicast traffic after a failover or reboot.

* Disabling then re-enabling the PIM interfaces using a clish command solves the issue until the next failover/reboot.

* Some PIM interfaces are not listed in */proc/net/ip_mr_vif*.

* Similar drops seen in fw ctl zdebug + drop \| grep x.x.x.x

  <br />

  *sim_pkt_send_drop_notification: (0,5) received drop, reason: Do routing (74), conn: \<x.x.x.x,XXXXX,y.y.y.y.y,YYYYY,17\>;*

  *sim_pkt_send_drop_notification: no track is needed for this drop - not sending a notificaion, conn: \<x.x.x.x,XXXXX,y.y.y.y.y,YYYYY,17\>;*

  and/or

  *prepare_cut_through: drop due to no multicast listeners, rc: 22 changing to =\> SIMPKT_IN_DROP, conn:\<x.x.x.x,XXXXX,y.y.y.y.y,YYYYY,17\>;*

## Cause

When PIM is enabled on an interface, a virtual interface is created and registered with the kernel.

To view all virtual interfaces that have multicast enabled, examine these files:

* For IPv4 multicast - */proc/net/ip_mr_vif*
* For IPv6 multicast - */proc/net/ip6_mr_vif*

All PIM enabled interfaces must be present in these files for multicast to function properly.

## Solution

This problem was fixed. The fix is included in:

* [Jumbo Hotfix Accumulator for R81.20](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.20/Default.htm) starting from Take 14
* [Jumbo Hotfix Accumulator for R81.10](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.10/Default.htm) starting from Take 95 (For SMB appliances the fix is included in R81.10.15 Build4076 and is available from the latest JHF.)
* [Jumbo Hotfix Accumulator for R81](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81/Default.htm) starting from Take 87
* [Jumbo Hotfix Accumulator for R80.40](https://sc1.checkpoint.com/documents/Jumbo_HFA/R80.40/Default.htm) starting from Take 198

If you choose not to upgrade, [Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a Hotfix for this issue.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing it.  
For faster resolution and verification, collect these files:

1. [CPinfo](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk92739) file from the Management Server involved in the case.
2. [CPinfo](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk92739) file from each Cluster Member involved in the case.

**Hotfix installation instructions:**   
Refer to [sk168597 - How to install a Hotfix](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk168597).

---

# 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