3Com Switch 7754, Configuration Manual

Page: 501 / 940

MSDP Configuration Example 501
# Configure an MSDP peer on Loopback0 on SwitchC.
[SwitchC] msdp
[SwitchC-msdp] originating-rp loopback0
[SwitchC-msdp] peer 2.2.2.2 connect-interface loopback0
[SwitchC-msdp] quit
# Configure an MSDP peer on Loopback0 on SwitchD.
[SwitchD] msdp
[SwitchD-msdp] originating-rp loopback0
[SwitchD-msdp] peer 1.1.1.1 connect-interface loopback0
[SwitchD-msdp] quit
# Carry out the display msdp brief command to view the MSDP peering
relationship established between switches. The MSDP peering relationship
established between Switch C and Switch D is displayed as follows:
[SwitchC] display msdp brief
MSDP Peer Brief Information
Peer’s Address State Up/Down time AS SA Count Reset Count
2.2.2.2 Up 00:10:17 ? 0 0
[SwitchD] display msdp brief
MSDP Peer Brief Information
Peer’s Address State Up/Down time AS SA Count Reset Count
1.1.1.1 Up 00:10:18 ? 0 0
Configuration Example
of a PIM Stub Domain
Network requirements
Two ISPs maintains their ASs, AS 100 and AS 200 respectively. OSPF is running
within each AS, and BGP is running between the two ASs. PIM-SM1 belongs to AS
100, while PIM-SM2 and PIM-SM3 belong to AS 200.
Each PIM-SM domain is a single-BSR-managed domain, each having 0 or 1
multicast source S and multiple receivers. OSPF runs within each domain to
provide unicast routes. PIM-SM2 and PIM-SM3 are both PIM stub domains, and
BGP or MBGP is not required between these two domains and PIM-SM1. Instead,
static RPF peers are configured to avoid RPF check on SA messages.
The respective Loopback0 of Switch C, Switch D and Switch F are configured as
the C-BSR and C-RP of the respective PIM-SM domain. The static RPF peers of
Switch C are Switch D and Switch F, while Switch C is the only RPF peer of Switch
D and Switch F. Any switch can receive the SA messages sent by its static RPF
peer(s) and permitted by the corresponding filtering policy.