Creating an rpf route, Network requirements – H3C Technologies H3C SecPath F1000-E User Manual
Page 596
571
[SecPathA-GigabitEthernet0/1] quit
[SecPathA] interface GigabitEthernet 0/2
[SecPathA-GigabitEthernet0/2] pim dm
[SecPathA-GigabitEthernet0/2] quit
[SecPathA] interface GigabitEthernet 0/3
[SecPathA-GigabitEthernet0/3] pim dm
[SecPathA-GigabitEthernet0/3] quit
The configuration on SecPath C is similar. (Details not shown.)
# Use the display multicast rpf-info command to display the RPF route to Source on SecPath B.
[SecPathB] display multicast rpf-info 50.1.1.100
RPF information about source 50.1.1.100:
RPF interface: GigabitEthernet0/3, RPF neighbor: 30.1.1.2
Referenced route/mask: 50.1.1.0/24
Referenced route type: igp
Route selection rule: preference-preferred
Load splitting rule: disable
The output shows that the current RPF route on SecPath B is contributed by a unicast routing
protocol and the RPF neighbor is SecPath A.
3.
Configure a static multicast route:
# Configure a static multicast route on SecPath B, specifying SecPath C as its RPF neighbor to
Source.
[SecPathB] ip rpf-route-static 50.1.1.100 24 20.1.1.2
4.
Verify the configuration:
# Use the display multicast rpf-info command to display information about the RPF route to Source
on SecPath B.
[SecPathB] display multicast rpf-info 50.1.1.100
RPF information about source 50.1.1.100:
RPF interface: GigabitEthernet0/2, RPF neighbor: 20.1.1.2
Referenced route/mask: 50.1.1.0/24
Referenced route type: multicast static
Route selection rule: preference-preferred
Load splitting rule: disable
The output shows that the RPF route on SecPath B has changed. It is now the configured static
multicast route, and the RPF neighbor is now SecPath C.
Creating an RPF route
Network requirements
PIM-DM runs in the network and all routers in the network support IP multicast.
SecPath B and SecPath C run OSPF, and have no unicast routes to SecPath A.
Typically, Receiver can receive the multicast data from Source 1 in the OSPF domain.
Perform the following configuration so that Receiver can receive multicast data from Source 2, which is
outside the OSPF domain.