Multicast configuration¶
Multicast basic configuration¶
PIM receiver¶
The following example enables PIM on a receiver. A static Rendez-vous Point and
a 5 seconds interval for sending join and prune messages is configured. An host
sends IGMP queries on the eth0 interface for the 239.0.0.1 group.
vsr running config# vrf main
vsr running vrf main# interface physical eth0
vsr running physical eth0#! port pci-b0s4
vsr running physical eth0# ipv4 address 10.200.0.1/24
vsr running physical eth0# .. physical eth1
vsr running physical eth1#! port pci-b0s5
vsr running physical eth1# ipv4 address 10.125.0.2/24
vsr running physical eth1# / vrf main
vsr running vrf main# routing static
vsr running static# ipv4-route 1.1.1.1/32 next-hop 10.125.0.1
vsr running static# / vrf main
vsr running vrf main# routing pim
vsr running pim# enabled true
vsr running pim# static-rp rp-list 1.1.1.1
vsr running rp-list 1.1.1.1# .. ..
vsr running pim# join-prune-interval 5
vsr running pim# ..
vsr running routing# interface eth0
vsr running interface eth0# pim enabled true
vsr running interface eth0# igmp enabled true
vsr running interface eth0# .. interface eth1
vsr running interface eth1# pim enabled true
vsr running interface eth1#
To get information on the membership queries recorded on PIM, the below commands can help:
vsr running config> show pim local-membership
Interface Address Source Group Membership
eth0 10.200.0.2 * 239.0.0.1 INCLUDE
To get more information, about the PIM neighbors, the below command can help:
vsr running config> show pim neighbor
Interface Neighbor Uptime Holdtime DR Pri
eth1 10.125.0.1 04:04:18 00:01:26 1
To get more information, about the RP, the below command can help. The OIF
acronym stands for the outgoing interface list where the RP is known along with
the multicast group requested.
vsr running config> show pim rp-info
RP address group/prefix-list OIF I am RP Source
1.1.1.1 239.0.0.0/24 eth1 no Static
PIM Rendezvous Point¶
The RP configuration is similar to the former configuration, and does not need any IGMP configuration. The RP IP address is generally configured over a loopback interface, like the below configuration suggests:
vsr running config# vrf main
vsr running vrf main# interface loopback loop1
vsr running loopback loop1# ipv4 address 1.1.1.1/32
vsr running loopback loop1# .. physical eth0
vsr running physical eth0#! port pci-b0s4
vsr running physical eth0# ipv4 address 10.125.0.1/24
vsr running physical eth0# .. physical eth1
vsr running physical eth1#! port pci-b0s5
vsr running physical eth1# ipv4 address 10.100.0.1/24
vsr running physical eth1# / vrf main
vsr running vrf main# routing pim
vsr running pim# enabled true
vsr running pim# static-rp rp-list 1.1.1.1
vsr running rp-list 1.1.1.1# .. ..
vsr running pim# join-prune-interval 5
vsr running pim# ..
vsr running routing# interface eth0
vsr running interface eth0# pim enabled true
vsr running interface eth0# .. interface eth1
vsr running interface eth1# pim enabled true
vsr running interface eth1#
Use the below show command to dump the shared path tree built with the RP acting as the root of that tree:
vsr running config> show pim join
Interface Address Source Group State Uptime Expire Prune
eth0 10.125.0.1 * 239.0.0.1 JOIN 01:12:32 03:26 --:--
Note
A shared path tree is defined as a tuple source and group and can be written
as follows: (*, G). The requested source is marked with an asterisk, because
the join did not request a specific source address for the requested group.
PIM source specific multicast¶
When an IGMP version 3 query is initiated on the receiver side, then the source address of the multicast group is known. It is not necessary to configure an RP.
The below commands illustrates the (10.100.0.1, 239.0.0.1) shared path tree.
vsr running config> show pim join
Interface Address Source Group State Uptime Expire Prune
eth0 10.125.0.1 10.100.0.1 239.0.0.1 JOIN 01:12:32 03:26 --:--