Lab - Configuring PIM Sparse-Mode Multicast Routing

Note!
All routers are running EIGRP protocol as well as multicast routing.

Topology

Pic. 1 - Topology Diagram.

Task 1
Multicast server is located on 10.1.234.0/24 subnet. It sends the multicast stream using 224.4.4.4 address. Enable multicast on all routers so that. R1 should be the Rendezvous Point (RP) in this network.

Solution 

Task 1

Multicast server is located on 10.1.234.0/24 subnet. It sends the multicast stream using 224.4.4.4 address. Enable multicast on all routers so that R1 should be the Rendezvous Point (RP) in this network.

All routers: 

!

ip pim rp-address 172.16.101.1

!

All routers similar to R1 below (all interfaces are sparse-mode)! 

R1 Configuration: 

!

interface Ethernet0/0
 ip address 10.1.51.1 255.255.255.0
 ip pim sparse-mode
!

interface Serial1/0
 ip address 10.1.123.1 255.255.255.0
 ip pim sparse-mode
 encapsulation frame-relay
 no ip split-horizon eigrp 100
 serial restart-delay 0
 frame-relay map ip 10.1.123.3 103 broadcast
 frame-relay map ip 10.1.123.2 102 broadcast
 no frame-relay inverse-arp

!

interface Serial1/1
 ip address 10.1.15.1 255.255.255.0
 ip pim sparse-mode
 serial restart-delay 0

!

Verification (here just R1, but done on all routers):

Pic. 2 - R1's Multicast-enabled Interfaces.

 

Pic. 3 - R's Multicast Neighbors.

All routers know which router is the RP. 

Pic. 3 - Routers Recognize RP (here: just R4).

 

In order to simulate the client on R6 'ip igmp join-group' command is used.

R6 Configuration:

!

interface Ethernet0/0
 ip address 10.1.56.6 255.255.255.0
 ip pim sparse-mode
 ip igmp join-group 224.4.4.4

!

 

R6 should register the group with RP (172.16.101.1). R5 receives the join 244.4.4.4 message and registers (*,G) entry (multicast) client. Then, DR registers this with R1 (RP). 

 

Pic. 5 - R5's Multicast Routing Table Entry for 224.4.4.4.

Pic. 6 - RP Registers 224.4.4.4 Client.

R4 is sending the traffic towards 224.4.4.4.

Pic. 7 - Ping Test.