H3C Technologies H3C S7500E Series Switches - Manual (Page 103)

4-19
The configuration on Switch B is similar to that on Switch A. The specific configuration steps
are omitted here.
# Use the display multicast rpf-info command to view the RPF routes to Source 2 on Switch B
and Switch C.
[SwitchB] display multicast rpf-info 50.1.1.100
[SwitchC] display multicast rpf-info 50.1.1.100
No information is displayed. This means that no RPF route to Source 2 exists on Switch B and
Switch C.
3) Configure a multicast static route
# Configure a multicast static route on Switch B, specifying Switch A as its RPF neighbor on the
route to Source 2.
[SwitchB] ip rpf-route-static 50.1.1.100 24 30.1.1.2
# Configure a multicast static route on Switch C, specifying Switch B as its RPF neighbor on the
route to Source 2.
[SwitchC] 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 view the RPF routes to Source 2 on Switch B
and Switch C.
[SwitchB] display multicast rpf-info 50.1.1.100
RPF information about source 50.1.1.100:
RPF interface: Vlan-interface102, 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
[SwitchC] display multicast rpf-info 50.1.1.100
RPF information about source 50.1.1.100:
RPF interface: Vlan-interface101, 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 routes to Source 2 exist on Switch B and Switch C. The source is the
configured static route.
Multicast Forwarding over GRE Tunnels
Network requirements
z Multicast routing and PIM-DM are enabled on Switch A and Switch C. Switch B does not
support multicast.
z OSPF is running on Switch A, Switch B, and Switch C.
z Perform the following configurations so that Receiver can receive the multicast data from
Source.