218
routing information displayed on Switch B with that displayed on Switch D, you can see that Switch D
acts now as the RP for Source 2 and Host B.
# Display PIM routing information on Switch B.
[SwitchB] display pim routing-table
No information is output on Switch B.
# Display PIM routing information on Switch D.
[SwitchD] display pim routing-table
VPN-Instance: public net
Total 1 (*, G) entry; 1 (S, G) entry
(*, 225.1.1.1)
RP: 10.1.1.1 (local)
Protocol: pim-sm, Flag: WC
UpTime: 00:12:07
Upstream interface: Register
Upstream neighbor: NULL
RPF prime neighbor: NULL
Downstream interface(s) information:
Total number of downstreams: 1
1: Vlan-interface200
Protocol: igmp, UpTime: 00:12:07, Expires: -
(10.110.6.100, 225.1.1.1)
RP: 10.1.1.1 (local)
Protocol: pim-sm, Flag: SPT 2MSDP ACT
UpTime: 00:40:22
Upstream interface: Vlan-interface104
Upstream neighbor: 10.110.4.2
RPF prime neighbor: 10.110.4.2
Downstream interface(s) information:
Total number of downstreams: 1
1: Vlan-interface200
Protocol: pim-sm, UpTime: - , Expires: -
SA message filtering configuration
Network requirements
As shown in
:
•
Three PIM-SM domains exist in the network, and OSPF runs within and among the domains to
provide unicast routing.
•
Source 1 sends multicast data to multicast groups 225.1.1.0/30 and 226.1.1.0/30, and Source 2
sends multicast data to multicast group 227.1.1.0/30.
Perform the following tasks to meet the requirements:
•
Configure respective Loopback 0 of Switch A, Switch C and Switch D as a C-BSR and C-RP in
the respective PIM-SM domain.
•
Set up an MSDP peering relationship between Switch A and Switch C and between Switch C
and Switch D.
