The ip rpf-route-static command configures a multicast static route.
The undo ip rpf-route-static command deletes a multicast static route.
By default, no multicast static route is configured.
ip rpf-route-static [ vpn-instance vpn-instance-name ] source-address { mask | mask-length } [ isis process-id | ospf process-id | rip process-id | bgp | static ] [ route-policy route-policy-name ] { interface-type interface-number | gateway-address } [ preference preference ] [ order order-number ]
undo ip rpf-route-static [ vpn-instance vpn-instance-name ] { source-address { mask | mask-length } [ isis process-id | ospf process-id | rip process-id | bgp | static ] [ route-policy route-policy-name ] | all }
| Parameter | Description | Value |
|---|---|---|
| vpn-instance vpn-instance-name | Specifies a VPN instance. vpn-instance-name specifies the name of the VPN instance. | The value must be an existing VPN instance name. |
| source-address | Specifies the address of a multicast source. | The address is in dotted decimal notation. |
| mask | Indicates the address mask of the multicast source. | The address mask is in dotted decimal notation. |
| mask-length | Specifies the mask length of the multicast source address. | The value is a decimal integer that ranges from 0 to 32. |
| isis process-id | Specifies that matched routes must be generated by the IS-IS protocol. process-id indicates the IS-IS process ID. | The value is a decimal integer that ranges from 1 to 65535. |
| ospf process-id | Specifies that matched routes must be generated by the OSPF protocol. process-id indicates the OSPF process ID. | The value is a decimal integer that ranges from 1 to 65535. |
| rip process-id | Specifies that matched routes must be generated by the RIP protocol. process-id indicates the RIP process ID. | The value is a decimal integer that ranges from 1 to 65535. |
| bgp | Specifies that matched routes must be generated by the BGP protocol. | - |
| static | Specifies that matched routes must be static routes. | - |
| route-policy route-policy-name | Indicates the matching rule of multicast static routes. route-policy-name specifies the name of a route matching rule. | The name is a string of 1 to 40 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
| interface-type interface-number | Specifies the type and the number of an interface, used to specify an interface. | - |
| gateway-address | Specifies the address of the gateway. | - |
| order order-number | Indicates the configuration order of routes in the same network segment. | The value is a decimal integer that ranges from 1 to 100. |
| preference preference | Indicates the preference of routes. The greater the value is, the lower the preference is. | The value is a decimal integer that ranges from 1 to 255. By default, it is 1. |
| all | Indicates all multicast static routes in the multicast static routing table. | - |
Usage Scenario
A multicast static route specifies an RPF interface or RPF neighbor for multicast packets from a specified multicast source. You can configure a multicast static route to:
Change an RPF route.
If you want an interface to receive multicast data packets from a specified multicast source but the interface is not the RPF interface for the multicast source, configure a multicast static route to specify this interface as the RPF interface for the multicast source. When the switch receives multicast data packets from the multicast source, it performs an RPF check using the configured RPF route. Packets sent from the source to the switch through other interfaces fail the RPF check.
Connect RPF routes.
If the unicast route on a network segment is incomplete, multicast packets cannot be forwarded due to the lack of an RPF route. For example, when two adjacent devices run different routing protocols and the routing protocols do not import routes from each other, packets cannot be forwarded between the two devices. In this case, you can configure RPF static routes on the devices. The devices can perform RPF checks using the specified RPF interfaces so that multicast packets can be forwarded successfully.
Precautions
If you specify a protocol type in the ip rpf-route-static command, the switch compares the configured multicast static route with the unicast routes of the specified protocol. If protocol types of the optimal unicast route and the multicast static route are different, the switch selects the optimal unicast route as the RPF route.
A multicast static route is identified by three elements: source-address { mask | mask-length }, protocol type, and route-policy-name. Two multicast static routes are considered different as long as one element has different values in the two routes. A maximum of eight multicast static routes can be configured on a network segment.
If the next-hop interface of a multicast static route is a P2P interface, you can specify the next-hop interface in the command. If the next-hop interface is a P2MP interface, you must specify the next-hop address.
A multicast static route may not take effect after you configure it using the ip rpf-route-static, because the specified interface is Down. After configuring a multicast static route, you are advised to run the display multicast routing-table static command to check whether the route is configured successfully and takes effect.