87
[SwitchB] display multicast rpf-info 50.1.1.100
[SwitchC] display multicast rpf-info 50.1.1.100
No information is displayed, because no RPF route to the source 2 exists on Switch B or Switch
C.
5.
Configure a static multicast route:
# Configure a static multicast route on Switch B, and specify 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 static multicast route on Switch C, and specify Switch B as its RPF neighbor on
the route to Source 2.
[SwitchC] ip rpf-route-static 10.1.1.100 24 20.1.1.2
Verifying the configuration
# Display the RPF routes to the 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
The output shows that the RPF routes to Source 2 exist on Switch B and Switch C. The routes are
the configured static routes.
Multicast forwarding over a GRE tunnel
Network requirements
As shown in
:
•
Multicast routing and PIM-DM are enabled on Switch A and Switch C.
•
Switch B does not support multicast.
•
OSPF is running on Switch A, Switch B, and Switch C.
Configure the switches so that the receiver can receive the multicast data from Source.
