Note:
The BSR sends mapping messages to 224.0.0.13 (all-PIM-routers). This does notrequire dense mode support or a known RP
Sample Configuraiton
Task:
- Configure R1 loopback 0 as a multicast source of 239.1.1.1 group
- R2 uses PIM BSR to announce RP.
- R3 will be 239.1.1.1 receiver
Configuration
R2
ip pim bsr-candidate Loopback0 0
ip pim rp-candidate Loopback0
R3
interface FastEthernet0/0
ip address 192.168.2.2 255.255.255.0
ip pim sparse-mode
ip igmp join-group 239.1.1.1
duplex auto
speed auto
end
Verify Configuration
R3#sh ip pim rp mapping
PIM Group-to-RP Mappings
Group(s) 224.0.0.0/4
RP 2.2.2.2 (?), v2
Info source: 2.2.2.2 (?), via bootstrap, priority 0, holdtime 150
Uptime: 00:05:27, expires: 00:02:20
R3#sh ip mroute
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
(*, 239.1.1.1), 00:03:25/00:02:55, RP 2.2.2.2, flags: SJPCL
Incoming interface: FastEthernet0/0, RPF nbr 192.168.2.1
Outgoing interface list: Null
(*, 224.0.1.40), 00:09:36/00:01:57, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Sparse, 00:09:36/00:01:57
R1#ping 239.1.1.1 source loopback 0
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 239.1.1.1, timeout is 2 seconds:
Packet sent with a source address of 1.1.1.1
Reply to request 0 from 192.168.2.2, 144 ms
Reply to request 0 from 192.168.2.2, 468 ms
R1#
No comments:
Post a Comment