On Junos and Junos Evolved platforms, when MOFRR (Multicast-only fast reroute) is enabled and PIM join state has RPF vector TLV (Reverse Path Forwarding Vector TLV) attached, RPD core will be generated and impact the service upon receiving PIM prune message

issue seen on the below topology where MOFRR is enabled on all the nodes and R3 has PIM join state (S,G) with RPF vector TLV. on R3 , ae42 is MOFRR backup and also it is a member of outgoing interface list (OIF). upon receiving PIM prune message for (S,G), cleaning process is not completed properly and RPD core will be generated

                              +------------------+                                       

                              |                  | P                                    

                  +------------ae47   R3      ae40-----------------+                    

                  |           |                  |                 |                    

                  |           |       ae42       |                 |                    

                  |           +--------+---------+               +-+------+             

              +---+---+                |B                        |  R3    +---- mcast src

   mcast+Rx---+ R1    |                |                         |        |             

              |       |                |                         +--+-----+             

              +---+---+                |B                           |                   

                  |            +-------+---------+                  |                   

                  |            |                 | P                |                   

                  +------------+                 +------------------+                   

                               |       R2        |                                       

                               |                 |                                       

                               +-----------------+   

On DUT:

>show pim joins extensive

Group: xx.xx.xx.xx

  Source: xx.xx.xx.xx

  Flags: sparse,spt

Active upstream interface: ae40.0

  Active upstream neighbor: xx.xx.xx.xx

  MoFRR Backup upstream interface: ae42.0 >>>>>>>>ae42 MOFRR backup

  MoFRR Backup upstream neighbor: xx.xx.xx.xx

  Upstream state: Join to Source

  Upstream rpf-vector: xx.xx.xx.xx >>>>>>>>>>>>>>>RPF vector attached

  Keepalive timeout: 

  Uptime: 5w2d 19:32:15 

  Downstream neighbors:

    Interface: ae42.0          >>>>>>>>ae42 member of OIF-list

      xx.xx.xx.xx State: Join Flags: S Timeout: 175

      Uptime: 5w2d 19:32:15 Time since last Join: 00:00:34

Interface: ae47.0         

      xx.xx.xx.xx State: Join Flags: S Timeout: 175

      Uptime: 5w2d 19:32:15 Time since last Join: 00:00:34

      rpf-vector: xx.xx.xx.xx

  Number of downstream interfaces: 2

  Number of downstream neighbors: 2

To check the rpd core file, execute the CLI command:

> show system core-dumps

customer needs to have the fix of PR1792886

OR

as workaround , customer needs to exclude PIM group (which has RPF vector) from MOFRR using the below policy

set policy-options policy-statement MOFRR-EXCLUDE term 10 from route-filter xx.xx.xx.xx/xx orlonger >>>>>>>>>>exclude the group address from MOFRR

set policy-options policy-statement MOFRR-EXCLUDE term 10 then reject

set policy-options policy-statement MOFRR-EXCLUDE term 20 then accept

set routing-options multicast stream-protection policy MOFRR-EXCLUDE