February 02, 2014

Lab 33: PIM Auto-RP

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

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

Let's confire R2 and R5 as auto-rp and permit only multicast groups 224.1.1.1 and 224.2.2.2:

ip access-list standard ACL1
permit 224.1.1.1
permit 224.2.2.2
deny 224.3.3.3

ip pim send-rp-announce Loopback0 scope 10 group-list ACL1

Let's confire R3 as mapping agent:

ip pim send-rp-discovery Loopback0 scope 10

As a result, you can only ping 224.1.1.1 and 224.2.2.2:

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, 92 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, 108 ms

You cannot ping 224.3.3.3:

R1#ping 224.3.3.3

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

This is R3's rp mapping output:

R3#sh ip pim rp mapping
PIM Group-to-RP Mappings
This system is an RP-mapping agent (Loopback0)

Group(s) 224.1.1.1/32
RP 10.0.0.5 (?), v2v1
Info source: 10.0.0.5 (?), elected via Auto-RP
Uptime: 00:09:52, expires: 00:02:11
RP 10.0.0.2 (?), v2v1
Info source: 10.0.0.2 (?), via Auto-RP
Uptime: 00:17:41, expires: 00:02:26
Group(s) 224.2.2.2/32
RP 10.0.0.5 (?), v2v1
Info source: 10.0.0.5 (?), elected via Auto-RP
Uptime: 00:09:52, expires: 00:02:14
RP 10.0.0.2 (?), v2v1
Info source: 10.0.0.2 (?), via Auto-RP
Uptime: 00:17:41, expires: 00:02:26
Group(s) (-)224.3.3.3/32
RP 10.0.0.5 (?), v2v1
Info source: 10.0.0.5 (?), elected via Auto-RP
Uptime: 00:09:52, expires: 00:02:10
RP 10.0.0.2 (?), v2v1
Info source: 10.0.0.2 (?), via Auto-RP
Uptime: 00:17:41, expires: 00:02:27

# DOWNLOAD LAB 33 GNS3 FILE