Creating an rpf route, Network requirements – H3C Technologies H3C SecPath F1000-E User Manual
Page 27
13
[DeviceA] multicast routing-enable
[DeviceA] interface gigabitethernet 0/1
[DeviceA-GigabitEthernet0/1] pim dm
[DeviceA-GigabitEthernet0/1] quit
[DeviceA] interface gigabitethernet 0/2
[DeviceA-GigabitEthernet0/2] pim dm
[DeviceA-GigabitEthernet0/2] quit
[DeviceA] interface gigabitethernet 0/3
[DeviceA-GigabitEthernet0/3] pim dm
[DeviceA-GigabitEthernet0/3] quit
The configuration on Device C is similar to the configuration on Device A. The specific configuration steps
are omitted here.
# Use the display multicast rpf-info command to view the RPF route to Source on Device B.
[DeviceB] 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
As shown above, the current RPF route on Device B is contributed by a unicast routing protocol and the
RPF neighbor is Device A.
Step3
Configure a multicast static route
# Configure a multicast static route on Device B, specifying Device C as its RPF neighbor to Source.
[DeviceB] ip rpf-route-static 50.1.1.100 24 20.1.1.2
Step4
Verify the configuration
# Use the display multicast rpf-info command to view the information about the RPF route to Source
on Device B.
[DeviceB] 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
As shown above, the RPF route on Device B has changed. It is now the configured multicast static route,
and the RPF neighbor is now Device C.
Creating an RPF Route
Network requirements
•
PIM-DM runs in the network and all devices in the network support IP multicast.
•
Device B and Device C run OSPF, and have no unicast routes to Device A.
•
Typically, Receiver can receive the multicast data from Source 1 in the OSPF domain.