Description

This article provides a basic example of the Multicast PIM sparse-dense mode configuration.

Symptoms

A basic example of the Multicast PIM sparse-dense mode configuration.

Solution

Network diagram :

Here it is assumed that the ge-0/0/1 interface of SRX-1 discovers the Auto-RP Message to  the ge-0/0/0 interface on SRX -2 [Auto-RP-Mapping Agent].


alt
 

SRX-1 configuration :

  1. Configure the interfaces on SRX-1:

    set interfaces ge-0/0/0 unit 0 family inet address 5.5.5.1/24
    set interfaces ge-0/0/1 unit 0 family inet address 10.10.10.1/24
  2. Enable PIM on the interfaces under the protocol hierarchy and specify the mode as dense. By default, IGMP v2 is enabled, when PIM is enabled on the interface:
    set protocols pim interface ge-0/0/0.0 mode sparse-dense
    set protocols pim interface ge-0/0/1.0 mode sparse-dense
  3. Configure the two multicast dense groups on all the routing devices ( 224.0.1.39 is used for announce messages and the 224.0.1.40 group is used for discovery messages):
    set protocols pim dense-groups 224.0.1.39/32
    set protocols pim dense-groups 224.0.1.40/32
  4. Configure the remaining routing devices in the PIM domain to discover the RP:
    set protocols pim rp auto-rp discovery

SRX-2 configuration :

  1. Configure the interfaces on SRX-1:
    set interfaces ge-0/0/0 unit 0 family inet address 10.10.10.2/24
  2. Enable PIM on the interfaces under the protocol hierarchy and specify the mode as dense. By default, IGMP v2 is enabled, when PIM is enabled on the interface:
    set protocols pim interface ge-0/0/0.0 mode sparse-dense
  3. Configure the two multicast dense groups on all the routing devices ( 224.0.1.39 is used for announce messages and the 224.0.1.40 group is used for discovery messages):
    set protocols pim dense-groups 224.0.1.39/32
    set protocols pim dense-groups 224.0.1.40/32
  4. Configure the auto-RP mapping agent (mapping on an RP allows the routing device to perform both the announcement and mapping functions):
    set protocols pim rp local address 10.10.10.2
  5. If the mapping agent is also a RP, configure the mapping agent as a local RP:
    set protocols pim rp auto-rp mapping
Verification :
root@SRX-1# run show pim rps
Oct 03 19:32:46
Instance: PIM.master
Address family INET
RP address Type    Holdtime Timeout Groups Group prefixes
10.10.10.2 auto-rp 150      135        0    224.0.0.0/4

Address family INET6



root@SRX-1# run show pim statistics |no-more
Oct 03 19:36:37

PIM Message type Received Sent Rx errors
V2 Hello 525 521 0
V2 Register 0 0 0
V2 Register Stop 0 0 0
V2 Join Prune 0 0 0
V2 Bootstrap 0 0 0
V2 Assert 0 0 0
V2 Graft 0 0 0
V2 Graft Ack 0 0 0
V2 Candidate RP 0 0 0
V1 Query 0 0 0
V1 Register 0 0 0
V1 Register Stop 0 0 0
V1 Join Prune 0 0 0
V1 RP Reachability 0 0 0
V1 Assert 0 0 0
V1 Graft 0 0 0
V1 Graft Ack 0 0 0
AutoRP Announce 0 0 0
AutoRP Mapping 23 0 0
AutoRP Unknown type 0
Anycast Register 0 0 0
Anycast Register Stop 0 0 0

Global Statistics

Hello dropped on neighbor policy 0
Unknown type 0
V1 Unknown type 0
Unknown Version 0
Neighbor unknown 0
Bad Length 0
Bad Checksum 0
Bad Receive If 0
Rx Bad Data 0
Rx Intf disabled 0
Rx V1 Require V2 0
Rx V2 Require V1 0
Rx Register not RP 0
Rx Register no route 0
Rx Register no decap if 0
Null Register Timeout 0
RP Filtered Source 0
Rx Unknown Reg Stop 0
Rx Join/Prune no state 0
Rx Join/Prune on upstream if 0
Rx Join/Prune messages dropped 0
Rx sparse join for dense group 0
Rx Graft/Graft Ack no state 0
Rx Graft on upstream if 0
Rx CRP not BSR 0
Rx BSR when BSR 0
Rx BSR not RPF if 0
Rx unknown hello opt 0
Rx data no state 0
Rx RP no state 0
Rx aggregate 0
Rx malformed packet 0
No RP 0
No register encap if 0
No route upstream 0
Nexthop Unusable 0
RP mismatch 0
RPF neighbor unknown 0
Rx Joins/Prunes filtered 0
Tx Joins/Prunes filtered 0
Embedded-RP invalid addr 0
Embedded-RP limit exceed 0
Embedded-RP added 0
Embedded-RP removed 0
Rx Register msgs filtering drop 0
Tx Register msgs filtering drop 0

For more details, refer to the technical documentation on  Configuring PIM Sparse-Dense Mode .

Troubleshooting :

Enable PIM traceoptions:

# set protocols pim traceoptions file PIM-trace
# set protocols pim flag all

Modification History

2020-07-24: Added tech doc link to Configuring PIM Sparse-Dense Mode.

Related Information