H3C Technologies H3C SecPath F1000-E - Manual (Page 598)

573
# Use the display multicast rpf-info command to display information about the RPF route to Source
2 on SecPath B and SecPath C.
[SecPathB] display multicast rpf-info 50.1.1.100
[SecPathC] display multicast rpf-info 50.1.1.100
No information is displayed. This means that no RPF route to Source 2 exists on SecPath B and
SecPath C.
3. Configure a static multicast route:
# Configure a static multicast route on SecPath B, specifying SecPath A as its RPF neighbor on the
route to Source 2.
[SecPathB] ip rpf-route-static 50.1.1.100 24 30.1.1.2
# Configure a static multicast route on SecPath C, specifying SecPath B as its RPF neighbor on the
route to Source 2.
[SecPathC] 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 routes to Source
2 on SecPath B and SecPath C.
[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: multicast static
Route selection rule: preference-preferred
Load splitting rule: disable
[SecPathC] 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 routes to Source 2 exist on SecPath B and SecPath C. The source for
these RPF routes is the configured static multicast route.
Multicast forwarding over GRE tunnels
Network requirements
Multicast routing and PIM-DM are enabled on SecPath A and SecPath C. SecPath B does not support
multicast. OSPF runs on SecPath A, SecPath B, and SecPath C.
Configure a GRE tunnel so that Receiver can receive the multicast data from Source.