Troubleshooting
Multicast Routing and
Forwarding
Multicast Static Route
Failure
[SwitchC-Vlan-interface300] pim dm
[SwitchC-Vlan-interface300] quit
[SwitchC] interface vlan-interface 102
[SwitchC-Vlan-interface102] pim dm
[SwitchC-Vlan-interface102] quit
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.
Symptom
No dynamic routing protocol is enabled on the routers, and the physic status and
link layer status of interfaces are both up, but the multicast static route fails.
Troubleshooting Multicast Routing and Forwarding
713