IP Multicast · Topic 5 of 5

Multicast Policy, Scoping and Troubleshooting

JN0-650 study page on multicast scoping and routing policy on Junos, plus configuring and troubleshooting IGMP, PIM sparse mode and SSM with show commands.

  • 5 min
In a nutshell
  • Administrative scoping uses 239.0.0.0/8 with a boundary on an interface; TTL scoping is the older method.
  • Multicast policy uses policy-statement; source-address-filter matches the source.
  • IGMP uses group-policy; PIM uses import; the RP uses rp-register-policy; MSDP uses import and export.

What it is

Scoping limits how far a multicast group is forwarded, so internal traffic does not leak into other networks. Multicast policy controls who may join a group, which sources are allowed, and which RPs and messages are accepted.

This page also pulls the chapter together into a build and troubleshooting checklist.

Admin boundaryScope 239.0.0.0/8blocksGroup trafficStays insidepolicy filtersJoins and registersAccepted or rejected

How it works

Scoping

There are two classic ways to limit the reach of multicast.

MethodHow it works
TTL scopingSources set a small TTL, so the packet dies after a few hops; crude and hard to manage
Administrative scopingA boundary on an interface blocks a whole group range from crossing it

The IPv4 range for administrative scoping is 239.0.0.0/8. A boundary stops traffic for those groups, and the related PIM and IGMP messages, from crossing the interface:

set routing-options multicast scope PRIVATE prefix 239.0.0.0/8
set routing-options multicast scope PRIVATE interface ge-0/0/3.0
Exam tip

Put the scope on the edge link between your network and the neighbor. Traffic in 239.0.0.0/8 then stays inside, with no change to the sources.

Multicast routing policy

Policies use the same policy-statement syntax as unicast, with match conditions on the group and the source.

GoalWhere it is applied
Control which groups receivers can join through a routerprotocols igmp interface name group-policy
Filter PIM joins by group or sourceprotocols pim import
Filter which sources the RP accepts for Registerprotocols pim rp rp-register-policy
Filter MSDP Source Active messagesprotocols msdp import and export
set policy-options policy-statement ALLOW-GROUPS term 1 from route-filter 239.1.0.0/16 orlonger
set policy-options policy-statement ALLOW-GROUPS term 1 then accept
set policy-options policy-statement ALLOW-GROUPS term 2 then reject
set protocols igmp interface ge-0/0/2.0 group-policy ALLOW-GROUPS

For source based filtering use source-address-filter:

set policy-options policy-statement ONLY-SRC term 1 from route-filter 239.1.1.0/24 orlonger
set policy-options policy-statement ONLY-SRC term 1 from source-address-filter 10.1.1.10/32 exact
set policy-options policy-statement ONLY-SRC term 1 then accept
set policy-options policy-statement ONLY-SRC term 2 then reject

A multicast policy ends with an explicit reject when you want a whitelist. Without it, the default behavior of the protocol applies.

Build checklist for sparse mode

  1. Make unicast routing work, in both directions, between sources, RPs and receivers.
  2. Enable PIM sparse mode on every interface in the path, including the RP loopback.
  3. Define the RP: static on all routers, or bootstrap, or Auto-RP.
  4. Set IGMP version 3 where SSM receivers need it.
  5. For SSM, rely on 232.0.0.0/8 or add routing-options multicast ssm-groups.
  6. Add scoping and policy last, and then test.
set protocols pim rp static address 10.255.0.1
set protocols pim interface ge-0/0/1.0 mode sparse
set protocols pim interface ge-0/0/2.0 mode sparse
set protocols igmp interface ge-0/0/2.0 version 3

Show commands

QuestionCommand
PIM neighbors up on the right interfacesshow pim neighbors
PIM interfaces, modes and DRshow pim interfaces
Which RP serves the groupshow pim rps
Join and prune state and upstream neighborshow pim join extensive
Known sourcesshow pim source
Forwarding entries and interfacesshow multicast route
RPF interface for a sourceshow multicast rpf
Hosts that joinedshow igmp group
Active sources between RPsshow msdp source-active

Troubleshooting order

Receiver joined?show igmp groupyesPIM neighbors?show pim neighborsyesRP known?show pim rpsyesRPF ok?show multicast rpfyesForwarding?show multicast route
SymptomLikely cause
No IGMP groupHost not joining, wrong IGMP version, snooping dropping reports
Join stops at the last hop routerNo PIM neighbor toward the RP, or no route to the RP
RP shows as unknownRP not configured on that router, or bootstrap not received
Source not registeringSource not on a PIM interface, or the RP is unreachable
Entry exists but no trafficRPF failure, scope boundary, or policy rejecting the group
Traffic only on the first packetsRegister works but the source tree join fails
Watch out

A scope boundary and a group policy can both silently discard traffic that is otherwise perfect. Check them before assuming a routing fault.

Common mistakes

Setting TTL scoping and calling it a boundary. TTL only counts hops.

Applying a group policy and forgetting the final reject. The policy then allows more than intended.

Not including the loopback as a PIM interface. The RP cannot be reached by PIM.

Starting with policy. Make routing and PIM work first.

Reading only show pim join. Also check show multicast route for forwarding.

What to remember for the exam

  • Administrative scoping uses 239.0.0.0/8 with a boundary on an interface; TTL scoping is the older method.
  • Multicast policy uses policy-statement; source-address-filter matches the source.
  • IGMP uses group-policy; PIM uses import; the RP uses rp-register-policy; MSDP uses import and export.
  • Check in order: IGMP group, PIM neighbor, RP, RPF, forwarding.
  • Sparse mode needs unicast routing, PIM on all path interfaces, and an RP.
  • SSM needs IGMPv3 and the SSM range; there is no RP step.

Check yourself

  • How do you stop group 239.5.5.5 from leaving your network without touching the source?

    Configure an administrative scope for 239.0.0.0/8 with a boundary on the edge interface.

  • Where do you filter which groups hosts may join?

    In an IGMP group-policy applied to the interface.

  • A join is seen at the last hop router but no traffic arrives. Which check comes next?

    The route to the RP and the RPF interface, using show pim rps and show multicast rpf.

Topic 5 of 5 in IP Multicast

Test yourself on IP Multicast

The full Juniper JNCIP-ENT JN0-650 question bank has 858 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by Juniper. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.