All things related to multicast

["Zenon Mousmoulas" <>]

Title: junos filtering msdp "reflector" originator

While investigating an issue with PIM register messages being dropped by our RP routers (due to misconfiguration), I noticed that some S,G state for local sources was mysteriously still present on the RP, even though register messages were being dropped. I then realized this state was triggered by MSDP SAs such as the following, which seem to be originated by some system in the UK. I can't think of a valid scenario where it could be an originator for what is certainly a foreign (in terms of a PIM domain) S,G. Such SAs are being accepted by the router -- I'm not sure at this stage if they should pass peer-rpf-check or not.

Group address   Source address  Peer address    Originator      Flags
233.21.32.32    62.217.124.105  62.40.124.89    194.82.152.254  Accept
233.21.32.234   62.217.124.105  62.40.124.89    194.82.152.254  Accept

Given these oddities about 194.82.152.254, which seems to act as a MSDP reflector (currently for up to 590 SAs), I wanted to see if I could drop such SAs in the MSDP import policy statement. However there doesn't seem to be a match condition for originator, at least not on JunOS 13.3. I wonder if there is any other way to do this?

Regards,
Z.