181
# On Switch G, configure Switch A as the MSDP peer and static RPF peer.
[SwitchG] ip prefix-list list-a permit 10.110.0.0 16 greater-equal 16 less-equal 32
[SwitchG] msdp
[SwitchG-msdp] peer 10.110.2.1 connect-interface vlan-interface 106
[SwitchG-msdp] static-rpf-peer 10.110.2.1 rp-policy list-a
[SwitchG-msdp] quit
Verifying the configuration
# Display the BGP peering relationships on Switch A.
[SwitchA] display bgp peer
No information is output, because no BGP peering relationship has been established between
Switch A and Switch D, or between Switch A and Switch G. This means that the unicast topology is
not changed.
# Display brief information about MSDP peers on Switch A.
[SwitchA] display msdp brief
Configured Established Listen Connect Shutdown Disabled
2 2 0 0 0 0
Peer address State Up/Down time AS SA count Reset count
10.110.3.2 Established 01:07:08 ? 8 0
10.110.6.2 Established 00:16:39 ? 13 0
# Display brief information about MSDP peers on Switch D.
[SwitchD] display msdp brief
Configured Established Listen Connect Shutdown Disabled
1 1 0 0 0 0
Peer address State Up/Down time AS SA count Reset count
10.110.1.1 Established 01:07:09 ? 8 0
# Display brief information about MSDP peers on Switch G.
[SwitchG] display msdp brief
Configured Established Listen Connect Shutdown Disabled
1 1 0 0 0 0
Peer address State Up/Down time AS SA count Reset count
10.110.2.1 Established 00:16:40 ? 13 0
# Verify that receivers in PIM-SM 1 and PIM-SM 3 can receive the multicast data from Source 1 and
Source 2 to a multicast group. (Details not shown.)
Anycast RP configuration
Network requirements
As shown in
, OSPF runs within the domain to provide unicast routes.
Configure the Anycast RP application so that the receiver-side DRs and the source-side DRs can
initiate a join process to their respective RPs that are topologically closest to them.
Configure the router IDs of Switch B and Switch D as 1.1.1.1 and 2.2.2.2, respectively. Set up an
MSDP peering relationship between Switch B and Switch D.