93[SwitchA-Vlan-interface200] quit[SwitchA] interface vlan-interface 102[SwitchA-Vlan-interface102] pim dm[SwitchA-Vlan-interface102] quit[SwitchA] interface vlan-interface 103[SwitchA-Vlan-interface103] pim dm[SwitchA-Vlan-interface103] quit# Enable IP multicast routing and PIM-DM on Switch C in the same way. (Details not shown.)# Use the display multicast rpf-info command to display the RPF route to Source on Switch B.[SwitchB] display multicast rpf-info 50.1.1.100RPF information about source 50.1.1.100:RPF interface: Vlan-interface102, RPF neighbor: 30.1.1.2Referenced route/mask: 50.1.1.0/24Referenced route type: igpRoute selection rule: preference-preferredLoad splitting rule: disableThe output shows that the current RPF route on Switch B is contributed by a unicast routing protocoland the RPF neighbor is Switch A.4. Configure a static multicast route on Switch B, specifying Switch C as its RPF neighbor on the routeto Source.[SwitchB] ip rpf-route-static 50.1.1.100 24 20.1.1.2Verifying the configuration# Display information about the RPF route to Source on Switch B.[SwitchB] display multicast rpf-info 50.1.1.100RPF information about source 50.1.1.100:RPF interface: Vlan-interface101, RPF neighbor: 20.1.1.2Referenced route/mask: 50.1.1.0/24Referenced route type: static multicastRoute selection rule: preference-preferredLoad splitting rule: disableThe output shows that the RPF route on Switch B has changed. It is now the configured static multicastroute, and the RPF neighbor is now Switch C.Creating an RPF routeNetwork requirementsPIM-DM runs in the network and all switches in the network support IP multicast. Switch B and Switch Crun OSPF, and have no unicast routes to Switch A. Typically, Receiver can receive the multicast data fromSource 1 in the OSPF domain.Perform the following configuration so that Receiver can receive multicast data from Source 2, which isoutside the OSPF domain.
