Using Ospf Routes For Multicast Rpf Checks - Juniper IGP - CONFIGURATION GUIDE V11.1.X Configuration Manual

mpls traffic-eng area
mpls traffic-eng router-id

Using OSPF Routes for Multicast RPF Checks

You can use the ip route-type or ipv6 route-type command to specify whether OSPF
routes are available for only unicast forwarding protocols or only multicast
reverse-path-forwarding (RPF) checks. Routes available for unicast forwarding appear
in the unicast view of the routing table, whereas routes available for multicast RPF
checks appear in the multicast view of the routing table.
To enable a multicast protocol and MPLS traffic engineering (TE) to interoperate on
a router running OSPF, use the mpls traffic-eng multicast-intact command.
ip route-type
ipv6 route-type
Use to enable SPF calculations to consider the IGP (OSPF) best paths as well as
the MPLS tunnel for forwarding traffic to the MPLS endpoint.
By default, the MPLS tunnel is always selected for traffic to the tunnel endpoint;
IGP paths are not considered. For traffic beyond the endpoint, the tunnel is
considered equally with any other path.
Example
host1(config-router)#mpls spf-use-any-best-path
Use the no version to disable the use of IGP best paths.
See mpls spf-use-any-best-path
Use to enable flooding of MPLS traffic engineering link information into the
specified OSPF area. Flooding is disabled by default.
Example
host1(config-router)#mpls traffic-eng area 0
Use the no version to disable flooding.
See mpls traffic-eng area
Use to specify a stable interface to be used as a router ID for MPLS traffic
engineering. Typically you specify a loopback interface to provide the greatest
stability, because this is flooded to all nodes. The interface acts as the destination
node for tunnels originating at other nodes.
Example
host1(config-router)#mpls traffic-eng router-id loopback 0
Use the no version to remove the interface as a router ID.
See mpls traffic-eng router-id
Chapter 5: Configuring OSPF
Using OSPF Routes for Multicast RPF Checks
291