Multicast - PIM Sparse Mode with Static RP

Overview

PIM sparse mode uses the concept of a rendezvous point to centralize the registration of sources and receivers as well as create a shared tree for initial multicast traffic once a sources begins sending traffic.

Today's lab will be focused on basic configuration of sparse mode and static configuration of a central rendezvous point and the verification of the configuration and that its working properly.

Concepts tested

• Multicast PIM sparse mode configuration
• Static RP configuration
• Verification

Topology

Lab Tasks

• Enable PIM sparse-mode on the paths between the source and destination hosts
• Configure R4 as a static RP
• for testing have the reciver join the group 231.0.0.1 and the ping the group from the source host

GNS3 configuration file, requires IOS v15 for the 7200 router: Link


Solution

R2:

R2(config)#ip multicast-routing
R2(config)#ip pim rp-address 4.4.4.4
R2(config)#int g0/0
R2(config-if)#ip pim sparse-mode
R2(config-if)#int s2/0
R2(config-if)#ip pim sparse-mode

R3:

R3(config)#ip multicast-routing

R3(config)#ip pim rp-address 4.4.4.4

R3(config)#int g0/0

R3(config-if)#ip pim sparse-mode

R3(config-if)#int g1/0

R3(config-if)#ip pim sparse-mode

R4:

R4(config)#ip multicast-routing

R4(config)#ip pim rp-address 4.4.4.4

R4(config)#int g0/0

R4(config-if)#ip pim sparse-mode

R4(config-if)#int g1/0

R4(config-if)#ip pim sparse-mode

R4(config-if)#int g2/0

R4(config-if)#ip pim sparse-mode

Source:

Source(config)#ip multicast-routing

Source(config)#int g0/0

Source(config-if)#ip pim sparse-mode

Receiver:

Receiver(config)#ip multicast-routing

Receiver(config)#int g0/0

Receiver(config-if)#ip pim sparse-mode

Receiver(config-if)#ip igmp join-group 231.0.0.1

Verification

R4#sh ip mroute 231.0.0.1

(*, 231.0.0.1), 00:01:54/00:02:34, RP 4.4.4.4, flags: S

  Incoming interface: Null, RPF nbr 0.0.0.0

  Outgoing interface list:

    GigabitEthernet1/0, Forward/Sparse, 00:01:54/00:02:34

R3#sh ip mroute 231.0.0.1

(*, 231.0.0.1), 00:02:31/00:02:23, RP 4.4.4.4, flags: SJC

  Incoming interface: GigabitEthernet1/0, RPF nbr 120.0.34.4

  Outgoing interface list:

    GigabitEthernet0/0, Forward/Sparse, 00:02:31/00:02:23

R2:

R2#sh ip mroute 231.0.0.1

(*, 231.0.0.1), 00:03:05/00:02:47, RP 4.4.4.4, flags: SP

  Incoming interface: GigabitEthernet0/0, RPF nbr 120.0.0.3

  Outgoing interface list: Null

R2#sh ip pim rp mapping

PIM Group-to-RP Mappings

Group(s): 224.0.0.0/4, Static

    RP: 4.4.4.4 (?)

R3#sh ip pim rp mapping

PIM Group-to-RP Mappings

Group(s): 224.0.0.0/4, Static

    RP: 4.4.4.4 (?)

R4 Debug:

*Nov 16 17:29:33.182: PIM(0): Adding register decap tunnel (Tunnel1) as accepting interface of (120.0.45.5, 231.0.0.1).

*Nov 16 17:29:33.198: PIM(0): Removing register decap tunnel (Tunnel1) as accepting interface of (120.0.45.5, 231.0.0.1).

*Nov 16 17:29:33.202: PIM(0): Installing GigabitEthernet2/0 as accepting interface for (120.0.45.5, 231.0.0.1).

*Nov 16 17:29:33.206: PIM(0): Insert (120.0.45.5,231.0.0.1) join in nbr 120.0.45.5's queue

*Nov 16 17:29:33.210: PIM(0): Building Join/Prune packet for nbr 120.0.45.5

*Nov 16 17:29:33.210: PIM(0):  Adding v2 (120.0.45.5/32, 231.0.0.1), S-bit Join

R4#

*Nov 16 17:29:33.214: PIM(0): Send v2 join/prune to 120.0.45.5 (GigabitEthernet2/0)

*Nov 16 17:29:33.294: PIM(0): Received v2 Join/Prune on GigabitEthernet1/0 from 120.0.34.3, to us

*Nov 16 17:29:33.298: PIM(0): Join-list: (120.0.45.5/32, 231.0.0.1), S-bit set

*Nov 16 17:29:33.302: PIM(0): Update GigabitEthernet1/0/120.0.34.3 to (120.0.45.5, 231.0.0.1), Forward state, by PIM SG Join

*Nov 16 17:29:33.466: PIM(0): Send RP-reachability for 231.0.0.1 on GigabitEthernet1/0

Source:

Source#ping 231.0.0.1 rep 1000

Type escape sequence to abort.

Sending 1000, 100-byte ICMP Echos to 231.0.0.1, timeout is 2 seconds:

Reply to request 0 from 120.0.0.1, 208 ms

Reply to request 1 from 120.0.0.1, 100 ms

Reply to request 2 from 120.0.0.1, 112 ms

Reply to request 3 from 120.0.0.1, 112 ms

Reply to request 4 from 120.0.0.1, 104 ms