H3C Technologies H3C SecPath F1000-E User Manual
Page 691
666
[RouterD-bgp] peer 10.110.4.1 as-number 100
[RouterD-bgp] import-route ospf 1
[RouterD-bgp] quit
# Redistribute BGP routing information into OSPF on Router A.
[RouterA] ospf 1
[RouterA-ospf-1] import-route bgp
[RouterA-ospf-1] quit
# Redistribute BGP routing information into OSPF on SecPath B.
[SecPathB] ospf 1
[SecPathB-ospf-1] import-route bgp
[SecPathB-ospf-1] quit
# Redistribute BGP routing information into OSPF on Router B.
[RouterB] ospf 1
[RouterB-ospf-1] import-route bgp
[RouterB-ospf-1] quit
# Redistribute BGP routing information into OSPF on Router D.
[RouterD] ospf 1
[RouterD-ospf-1] import-route bgp
[RouterD-ospf-1] quit
5.
Configure MSDP peers and static RPF peers:
# Configure SecPath B and SecPath C as the MSDP peers and static RPF peers of SecPath A.
[SecPathA] ip ip-prefix list-dg permit 10.110.0.0 16 greater-equal 16 less-equal 32
[SecPathA] msdp
[SecPathA-msdp] peer 10.110.3.2 connect-interface GigabitEthernet 0/1
[SecPathA-msdp] peer 10.110.6.2 connect-interface GigabitEthernet 0/2
[SecPathA-msdp] static-rpf-peer 10.110.3.2 rp-policy list-dg
[SecPathA-msdp] static-rpf-peer 10.110.6.2 rp-policy list-dg
[SecPathA-msdp] quit
# Configure SecPath A as the MSDP peer and static RPF peer of SecPath B.
[SecPathB] ip ip-prefix list-a permit 10.110.0.0 16 greater-equal 16 less-equal 32
[SecPathB] msdp
[SecPathB-msdp] peer 10.110.1.1 connect-interface pos 5/0
[SecPathB-msdp] static-rpf-peer 10.110.1.1 rp-policy list-a
[SecPathB-msdp] quit
# Configure SecPath A as the MSDP peer and static RPF peer of SecPath C.
[SecPathC] ip ip-prefix list-a permit 10.110.0.0 16 greater-equal 16 less-equal 32
[SecPathC] msdp
[SecPathC-msdp] peer 10.110.2.1 connect-interface GigabitEthernet 0/1
[SecPathC-msdp] static-rpf-peer 10.110.2.1 rp-policy list-a
[SecPathC-msdp] quit
6.
Verify the configuration:
Use the display bgp peer command to display BGP peering relationship between the firewalls.
SecPath A does not display any information, which means that no BGP peering relationship has
been established between SecPath A and SecPath B, or between SecPath A and SecPath C.
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.