235
Verifying the configuration
Use the display bgp peer command to display the BGP peering relationship between the switches. If the
command gives no output information on Switch A, it means that no BGP peering relationship has been
established between Switch A and Switch D, or between Switch A and Switch G.
When the multicast source in PIM-SM 1 (Source 1) and the multicast source in PIM-SM 2 (Source 2) send
multicast information, receivers in PIM-SM 1 and PIM-SM 3 can receive the multicast data. You can use
the display msdp brief command to display the brief information of MSDP peering relationship between
the switches. For example:
# Display brief MSDP peer information on Switch A.
[SwitchA] display msdp brief
MSDP Peer Brief Information of VPN-Instance: public net
Configured Up Listen Connect Shutdown Down
2 2 0 0 0 0
Peer's Address State Up/Down time AS SA Count Reset Count
10.110.3.2 Up 01:07:08 ? 8 0
10.110.6.2 Up 00:16:39 ? 13 0
# Display brief MSDP peer information on Switch D.
[SwitchD] display msdp brief
MSDP Peer Brief Information of VPN-Instance: public net
Configured Up Listen Connect Shutdown Down
1 1 0 0 0 0
Peer's Address State Up/Down time AS SA Count Reset Count
10.110.1.1 Up 01:07:09 ? 8 0
# Display brief MSDP peer information on Switch G.
[SwitchG] display msdp brief
MSDP Peer Brief Information of VPN-Instance: public net
Configured Up Listen Connect Shutdown Down
1 1 0 0 0 0
Peer's Address State Up/Down time AS SA Count Reset Count
10.110.2.1 Up 00:16:40 ? 13 0
Anycast RP configuration
Network requirements
As shown in Figure 64, the PIM-SM domain has multiple multicast sources and receivers. 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 message to their respective RPs that are the topologically nearest to them.
On Switch B and Switch D, configure the interface Loopback 10 as a C-BSR, and Loopback 20 as a C-RP.
To Next Page
Loading...
