February 02, 2014

Lab 32: PIM Accept-RP

Configure OSPF and pim sparse-mode on all routers. Configure R4's Ethernet0/0 interface to join multicast group 224.1.1.1 and 224.2.2.2:

interface Ethernet0/0
ip igmp join-group 224.1.1.1
ip igmp join-group 224.2.2.2

You can ping both multicast group addresses from R1:

R1#ping 224.1.1.1

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.1.1.1, timeout is 2 seconds:

Reply to request 0 from 34.0.0.4, 52 ms


R1#ping 224.2.2.2

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.2.2.2, timeout is 2 seconds:

Reply to request 0 from 34.0.0.4, 76 ms

Let's configure R3 to make 224.1.1.1 to be active:

access-list 5 permit 224.1.1.1
ip pim accept-rp 10.0.0.2 5

As a result, you can only ping 224.1.1.1 from R1:

R1#ping 224.1.1.1

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.1.1.1, timeout is 2 seconds:

Reply to request 0 from 34.0.0.4, 84 ms


R1#ping 224.2.2.2

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.2.2.2, timeout is 2 seconds:
.

This the mroute table of R2:

R2#show ip mroute 224.1.1.1
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.1.1.1), 00:29:30/00:02:34, RP 10.0.0.2, flags: S
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/1, Forward/Sparse, 00:29:30/00:02:34

R2#show ip mroute 224.2.2.2
Group 224.2.2.2 not found

# DOWNLOAD LAB 32 GNS3 FILE