Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Example: Configuring PIM SSM on a Network

The following example shows how PIM SSM is configured between a receiver and a source in the network illustrated in Figure 1.

Figure 1: Network on Which to Configure PIM SSM

1. Enable IGMPv3 on all host-facing interfaces, and disable IGMP on the fxp0.0 interface on Router 1.
   user@router1# set protocols igmp interface all version 3user@router1# set protocols igmp interface fxp0.0 disable

   Note: When you configure IGMPv3 on a router, hosts on interfaces configured with IGMPv2 cannot join the source tree.

2. After the configuration is committed, use the show configuration protocol igmp command to verify the IGMP protocol configuration.
   user@router1> show configuration protocol igmp
   [edit protocols igmp]

   interface all {version 3;}

   interface fxp0.0 {disable;}
3. Use the show igmp interface command to verify that IGMP interfaces are configured.
   user@router1> show igmp interface

   Interface      State    Querier      Timeout Version Groups
   fe-0/0/0.0     Up       198.58.3.245     213       3      0
   fe-0/0/1.0     Up       198.58.3.241     220       3      0
   fe-0/0/2.0     Up       198.58.3.237     218       3      0
   Configured Parameters:
   IGMP Query Interval (1/10 secs): 1250
   IGMP Query Response Interval (1/10 secs): 100
   IGMP Last Member Query Interval (1/10 secs): 10
   IGMP Robustness Count: 2
   Derived Parameters:
   IGMP Membership Timeout (1/10 secs): 2600
   IGMP Other Querier Present Timeout (1/10 secs): 2550
   

4. Use the show pim join extensive command to verify the PIM join state on Router 2 and Router 3 (the upstream routers).
   user@router2> show pim join extensive

   232.1.1.1       10.4.1.2                        sparse
        Upstream interface: fe-1/1/3.0
        Upstream State: Local Source
        Keepalive timeout: 209
        Downstream Neighbors:
           Interface: so-1/0/2.0
               10.10.71.1       State: Join   Flags: S    Timeout: 209
   

5. Use the show pim join extensive command to verify the PIM join state on Router 1 (the router connected to the receiver).
   user@router1> show pim join extensive

   232.1.1.1       10.4.1.2                        sparse
        Upstream interface: so-1/0/2.0
        Upstream State: Join to Source
        Keepalive timeout: 209
        Downstream Neighbors:
           Interface: fe-0/2/3.0
               10.3.1.1         State: Join   Flags: S    Timeout: Infinity
   

Note: IP version 6 (IPv6) multicast routers use the Multicast Listener Discovery (MLD) Protocol to manage the membership of hosts and routers in multicast groups and to learn which groups have interested listeners for each attached physical networks. Each routing device maintains a list of host multicast addresses that have listeners for each subnetwork, as well as a timer for each address. However, the routing device does not need to know the address of each listener—just the address of each host. The routing device provides addresses to the multicast routing protocol it uses, which ensures that multicast packets are delivered to all subnetworks where there are interested listeners. In this way, MLD is used as the transport for the Protocol Independent Multicast (PIM) Protocol. MLD is an integral part of IPv6 and must be enabled on all IPv6 routing devices and hosts that need to receive IP multicast traffic. The Junos OS supports MLD versions 1 and 2. Version 2 is supported for source-specific multicast (SSM) include and exclude modes.